On Tue, Oct 23, 2012 at 7:51 PM, Erik Moeller
<erik@wikimedia.org> wrote:
Overall these changes are awesome and ULS is coming along beautifully,
but I agree with Timo on the upper/lower case issue.
> Sentence context is different from title/list view, in the latter it should
> be ucfirst'ed unconditionally (like we do in interwiki lists), whether to
> use the ucfirst algorithm of the interface language or the language name is
> another but it should be ucfirst.
+1. Please use sentence case in lists to make them scannable and
aesthetically pleasing :).
Similarly, I don't see why "français" should be lower-case in the menu
after the language is selected. Every other menu item in the UI has
the first letter capitalized, regardless of in-sentence word case.
It's great you like the interaction improvements.
I'm not a linguist, so I relied in the 466 language names defined there. There are probably bugs in the data, and also rarities that may seem bugs to our eyes but are not according to each language writing rules (some scripts do not even have capitals). By filling bugs for the detected problems, the info will probably arrive to the Language Engineering team members with more information to determine the nature of each specific case.
Pau
The data there is correct. In French, for example, they don't capitalise (their) language name in sentences. These are rules similar to for example how in German nouns are capitalised in the middle of a Sentence, but we don't capitalise those Words in English.
So, just like we don't capitalise nouns in English (like they do in German), the French don't capitalise language names (like we do in English).
In order to store and use that information, the language names on themselves are stored the way they should be used in a sentence. However when used at the start of a title, sentence or in a list, then other rules apply. For instance all sentences start with a capital letter in English (in German and French, too), even if the first word is a word that wouldn't be capitalised otherwise.
Back to the issue at hand, it appears as though this isn't a resolved issue after all. The bug report I opened was closed[1] by Siebrand as invalid...
-- Krinkle