@chaffjs/lang-en 0.42.0 → 0.44.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/lexicons/action-due-label.yaml +1 -1
- package/lexicons/any-year-marker.yaml +2 -0
- package/lexicons/benefit-label.yaml +26 -0
- package/lexicons/closing-cliche.yaml +16 -0
- package/lexicons/defined-term-partitive.yaml +14 -0
- package/lexicons/ordinal-word.yaml +33 -0
- package/lexicons/output-lead-in.yaml +12 -0
- package/lexicons/request-instruction.yaml +12 -0
- package/lexicons/screen-label-noun.yaml +20 -0
- package/lexicons/stance-adverb.yaml +17 -0
- package/lexicons/summed-counter.yaml +14 -0
- package/lexicons/superlative-condition.yaml +10 -0
- package/lexicons/vague-word-term-of-art.yaml +3 -0
- package/package.json +1 -1
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# Words that mark an action item's deadline. A table column headed by one alone holds deadlines; in a list item, the date right after one (due Oct 3) is the deadline (due-before-issue).
|
|
1
|
+
# Words that mark an action item's deadline. A table column headed by one alone holds deadlines; in a list item, the date right after one (due Oct 3) is the deadline (due-before-issue). Such a column's dates are not a schedule (date-order).
|
|
2
2
|
id: action-due-label
|
|
3
3
|
language: en
|
|
4
4
|
entries:
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
# Words that open a bold list label stating a gain (- **More timely:** …, - **Less work:** …). bold-label-list counts such
|
|
2
|
+
# an item as a claim, with the bold lead sentences. Matched in lower case as the label's first word, with words after it.
|
|
3
|
+
# Left out: lower, higher, greater, which name things (Lower bound, Higher education, Greater London).
|
|
4
|
+
id: benefit-label
|
|
5
|
+
language: en
|
|
6
|
+
entries:
|
|
7
|
+
- pattern: more
|
|
8
|
+
position: before
|
|
9
|
+
- pattern: less
|
|
10
|
+
position: before
|
|
11
|
+
- pattern: better
|
|
12
|
+
position: before
|
|
13
|
+
- pattern: fewer
|
|
14
|
+
position: before
|
|
15
|
+
- pattern: faster
|
|
16
|
+
position: before
|
|
17
|
+
- pattern: easier
|
|
18
|
+
position: before
|
|
19
|
+
- pattern: simpler
|
|
20
|
+
position: before
|
|
21
|
+
- pattern: cheaper
|
|
22
|
+
position: before
|
|
23
|
+
- pattern: improved
|
|
24
|
+
position: before
|
|
25
|
+
- pattern: reduced
|
|
26
|
+
position: before
|
|
@@ -21,6 +21,11 @@ entries:
|
|
|
21
21
|
# "happy to discuss" and "apologize for any inconvenience" are email-stock-courtesy's, which counts them stacked.
|
|
22
22
|
- pattern: prompt attention to this matter
|
|
23
23
|
- pattern: would welcome any feedback
|
|
24
|
+
# A proposal's last line offering to talk it over. In an email it is email-stock-courtesy's, which counts it stacked.
|
|
25
|
+
- pattern: happy to discuss any
|
|
26
|
+
genres: [business/proposal]
|
|
27
|
+
- pattern: happy to answer any
|
|
28
|
+
genres: [business/proposal]
|
|
24
29
|
# A chirpy last wish in an email (Wishing you all a restful holiday season!, Thanks, and enjoy the long weekend!).
|
|
25
30
|
# Only in emails: a blog's "enjoy the wilderness!" is its subject, not a send-off.
|
|
26
31
|
- pattern: Wishing
|
|
@@ -32,3 +37,14 @@ entries:
|
|
|
32
37
|
- pattern: "!"
|
|
33
38
|
group: end:wish
|
|
34
39
|
genres: [business/email]
|
|
40
|
+
# A courtesy in an email's closing ("feel free to reach out") is ordinary politeness alone; beside another stock
|
|
41
|
+
# closing (a chirpy wish) the closing is a stack of stock lines, and it counts too.
|
|
42
|
+
- pattern: feel free to
|
|
43
|
+
group: stacked
|
|
44
|
+
genres: [business/email]
|
|
45
|
+
- pattern: don't hesitate to
|
|
46
|
+
group: stacked
|
|
47
|
+
genres: [business/email]
|
|
48
|
+
- pattern: do not hesitate to
|
|
49
|
+
group: stacked
|
|
50
|
+
genres: [business/email]
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
# Words that pick some out of a kind with "of" and a determiner: "some of these terms", "many of the services". A defined
|
|
2
|
+
# term names one thing or one set ("Terms" is this agreement); some of them are items of the ordinary kind, so
|
|
3
|
+
# defined-term-form reads the lower-case word after these as the ordinary word. "all of" and "each of" take the whole
|
|
4
|
+
# defined set and are not here.
|
|
5
|
+
id: defined-term-partitive
|
|
6
|
+
language: en
|
|
7
|
+
entries:
|
|
8
|
+
- pattern: some
|
|
9
|
+
- pattern: any
|
|
10
|
+
- pattern: many
|
|
11
|
+
- pattern: most
|
|
12
|
+
- pattern: several
|
|
13
|
+
- pattern: few
|
|
14
|
+
- pattern: one
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
# The ordinal numbers written as words. outside-announced-list does not take a run of them as a name: "Fourteenth and
|
|
2
|
+
# Fifteenth Edition … Sixteenth Edition" is an edition history counted on, not a list of named editions.
|
|
3
|
+
id: ordinal-word
|
|
4
|
+
language: en
|
|
5
|
+
entries:
|
|
6
|
+
- pattern: first
|
|
7
|
+
- pattern: second
|
|
8
|
+
- pattern: third
|
|
9
|
+
- pattern: fourth
|
|
10
|
+
- pattern: fifth
|
|
11
|
+
- pattern: sixth
|
|
12
|
+
- pattern: seventh
|
|
13
|
+
- pattern: eighth
|
|
14
|
+
- pattern: ninth
|
|
15
|
+
- pattern: tenth
|
|
16
|
+
- pattern: eleventh
|
|
17
|
+
- pattern: twelfth
|
|
18
|
+
- pattern: thirteenth
|
|
19
|
+
- pattern: fourteenth
|
|
20
|
+
- pattern: fifteenth
|
|
21
|
+
- pattern: sixteenth
|
|
22
|
+
- pattern: seventeenth
|
|
23
|
+
- pattern: eighteenth
|
|
24
|
+
- pattern: nineteenth
|
|
25
|
+
- pattern: twentieth
|
|
26
|
+
- pattern: thirtieth
|
|
27
|
+
- pattern: fortieth
|
|
28
|
+
- pattern: fiftieth
|
|
29
|
+
- pattern: sixtieth
|
|
30
|
+
- pattern: seventieth
|
|
31
|
+
- pattern: eightieth
|
|
32
|
+
- pattern: ninetieth
|
|
33
|
+
- pattern: hundredth
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
# Words of a lead-in that says the block after it is what a program shows, not code: "we'd expect to see:", "The output
|
|
2
|
+
# is:". code-fence-language-mix does not ask such a block for a language: plain output is in none.
|
|
3
|
+
id: output-lead-in
|
|
4
|
+
language: en
|
|
5
|
+
entries:
|
|
6
|
+
- pattern: expect to see
|
|
7
|
+
- pattern: you will see
|
|
8
|
+
- pattern: you'll see
|
|
9
|
+
- pattern: should see
|
|
10
|
+
- pattern: output
|
|
11
|
+
- pattern: prints
|
|
12
|
+
- pattern: displays
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
# The writer asking to be told how to do something ("Could you let me know how to send the boots back?"). The reader's answer
|
|
2
|
+
# is the writer's next step, not a task to finish by a date. "whether" and "what" are left out: "let me know whether you can
|
|
3
|
+
# attend" asks for a decision.
|
|
4
|
+
id: request-instruction
|
|
5
|
+
language: en
|
|
6
|
+
entries:
|
|
7
|
+
- pattern: how to
|
|
8
|
+
- pattern: where to
|
|
9
|
+
- pattern: how i can
|
|
10
|
+
- pattern: how i should
|
|
11
|
+
- pattern: how we can
|
|
12
|
+
- pattern: how we should
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Nouns that name a thing on a screen or in a workflow by the label it shows: "in SUBMIT TO APPROVER status", "the SAVE AND
|
|
2
|
+
# CLOSE button". all-caps-shouting does not report a capital run a sentence names that way: it quotes the label in the
|
|
3
|
+
# capitals the screen shows, it does not raise its voice.
|
|
4
|
+
id: screen-label-noun
|
|
5
|
+
language: en
|
|
6
|
+
entries:
|
|
7
|
+
- pattern: status
|
|
8
|
+
- pattern: button
|
|
9
|
+
- pattern: field
|
|
10
|
+
- pattern: tab
|
|
11
|
+
- pattern: menu
|
|
12
|
+
- pattern: screen
|
|
13
|
+
- pattern: option
|
|
14
|
+
- pattern: mode
|
|
15
|
+
- pattern: state
|
|
16
|
+
- pattern: stage
|
|
17
|
+
- pattern: column
|
|
18
|
+
- pattern: link
|
|
19
|
+
- pattern: box
|
|
20
|
+
- pattern: setting
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
# -ly adverbs that say how sure or how frank the writer is, not how something is done (adverb-overuse).
|
|
2
|
+
# "It probably should have been an email" has no verb to fold "probably" into, so they are not counted.
|
|
3
|
+
# Boosters (certainly, obviously, really) are left out: they prop up a claim the way a manner adverb props up a verb.
|
|
4
|
+
id: stance-adverb
|
|
5
|
+
language: en
|
|
6
|
+
entries:
|
|
7
|
+
- pattern: actually
|
|
8
|
+
- pattern: apparently
|
|
9
|
+
- pattern: arguably
|
|
10
|
+
- pattern: evidently
|
|
11
|
+
- pattern: frankly
|
|
12
|
+
- pattern: honestly
|
|
13
|
+
- pattern: hopefully
|
|
14
|
+
- pattern: possibly
|
|
15
|
+
- pattern: presumably
|
|
16
|
+
- pattern: probably
|
|
17
|
+
- pattern: supposedly
|
|
@@ -3,6 +3,20 @@
|
|
|
3
3
|
id: summed-counter
|
|
4
4
|
language: en
|
|
5
5
|
entries:
|
|
6
|
+
- pattern: items
|
|
7
|
+
group: item
|
|
8
|
+
- pattern: item
|
|
9
|
+
group: item
|
|
10
|
+
- pattern: people
|
|
11
|
+
group: person
|
|
12
|
+
- pattern: persons
|
|
13
|
+
group: person
|
|
14
|
+
- pattern: person
|
|
15
|
+
group: person
|
|
16
|
+
- pattern: documents
|
|
17
|
+
group: document
|
|
18
|
+
- pattern: document
|
|
19
|
+
group: document
|
|
6
20
|
- pattern: credits
|
|
7
21
|
group: credit
|
|
8
22
|
- pattern: credit
|
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
# Words that open a condition: a superlative inside it is supposed, not claimed ("If spreadsheet formulas are the most
|
|
2
|
+
# prolific government code, …"). They stand before the superlative in the same clause, no comma between.
|
|
3
|
+
# unqualified-superlative does not report a superlative they open.
|
|
4
|
+
id: superlative-condition
|
|
5
|
+
language: en
|
|
6
|
+
entries:
|
|
7
|
+
- pattern: if
|
|
8
|
+
- pattern: suppose
|
|
9
|
+
- pattern: supposing
|
|
10
|
+
- pattern: assuming
|