The specification is written in English
Every node of the specification is written in English, and so is everything generated from the nodes. A quotation, such as a name from the code or a text the system shows its users, keeps the language of what it quotes.
A specification that mixes two languages, in its nodes or in what is generated from them and read in their place, loses the line between what it states and what is an aside.
The language is English because a project's guidelines include the SpecSheriff guidelines, which a project takes as they are written and never changes (§s-bsya3febm6u64ab), and those are written in English: a project's own nodes in another language would mix two languages in one specification. English is also the language the readers of a specification are likeliest to share.
A quotation must match what it quotes letter for letter, and, standing apart from the words around it, it does not blur what the node states.
The links it makes
The decisions taken on it
- Problem
The rule named English, a choice one project made for its readers, which another project's readers need not share.
- Ruling
The owner: the specification is written in one language, English being recommended and holding where a project's own guidelines name no other; the SpecSheriff guidelines themselves are written in English.
- Problem
The rule let a project's owner name another language for the specification and required everything generated from its nodes to be in it, while a project's guidelines include the SpecSheriff guidelines, written in English, and no field held the language named for a tool to write in it the words it adds to what it generates, such as the labels of the export and of the map; and the one language held a node's quotations too, though a name from the code or a text the system shows its users may be in another.
- Ruling
The owner: everything of SpecSheriff is in English, every project's specification included; a quotation keeps the language of what it quotes.