New rule: language style about doc-linter-rules

[SebastianZ]

For reference, in the closed issue I mentioned some more cases related to the style guide:

• Latin abbreviations should be correctly abbreviated and used.
• Use sentence-style capitalization for keyboard shortcuts.
• Use proper hyphenation for "email", "re-" and "co-".
• Correctly format dates and numbers. (Though the rule about setting a comma only on five-digit numbers looks strange to me.)

Sebastian

[MatonAnthony]

Hi @SebastianZ,

Latin abbreviations should be correctly abbreviated and used.

I can make the full term triggers an ERROR and ask for the abbreviated but I don't have any way to check if it's properly used.

Use sentence-style capitalization for keyboard shortcuts.
Use proper hyphenation for "email", "re-" and "co-".

Ok, I'll implement those two in the opened PR before merging.

Correctly format dates and numbers. (Though the rule about setting a comma only on five-digit numbers looks strange to me.)

Parsing Dates and especially more likely to be formatted in a ton of different ways seems complicated to me.

[SebastianZ]

Latin abbreviations should be correctly abbreviated and used.

I can make the full term triggers an ERROR and ask for the abbreviated but I don't have any way to check if it's properly used.

Point here is that if abbreviations are used, they must be used correctly. Writers are not forced to used them, though.

So, for example, "e.g." must be written with dots but no space between them, followed by a comma and expressions using them need to be surrounded by parentheses.
Having said that, I wonder why the style guide says that separating them by comma is wrong. So, personally I'd not mark that as an error.

Correctly format dates and numbers. (Though the rule about setting a comma only on five-digit numbers looks strange to me.)

Parsing Dates and especially more likely to be formatted in a ton of different ways seems complicated to me.

You're right about that, but we may restrict the recognition to the ones mentioned in the style guide, which should be the most common erroneous writings. For example, dates formatted like "February 24th, 2006" are easily recognized via /[a-z]{3,}\s+\d{1,2}(?:st|nd|rd|th),?\s+\d{4}/. But, of course, the complete check might get a bit complicated.

Sebastian