Menu/Command capitalization

[Nicolás Alvarez]

> On Jan 8, 2016, at 08:51, Jaroslaw Staniek <staniek at kde.org> wrote:
> 
>> On 8 January 2016 at 00:28, Pino Toscano <pino at kde.org> wrote:
>> Hi,
>> 
>> In data giovedì 7 gennaio 2016 22:42:18, Jaroslaw Staniek ha scritto:
>>> Not too long ago MS Windows has moved from "Title Capitalization" to
>>> "Sentence capitalization" for menus and commands:
>>> https://msdn.microsoft.com/en-us/library/dn742392.aspx
>>> 
>>> What can we do and should we do something about this?
>> 
>> Nothing IMHO -- see below.
>> 
>>> - For everyone else perhaps it's better to offer something officially
>>> or else some people would fork translations or avoid using KDE's code.
>> 
>> You don't need to fork anything, just provide a "translation" on top of
>> the untranslated strings.
> 
> Thanks for the notes, Pino.
> That was not the exact question. What I mean is who provides the translation.
> If not KDE, then the whole thing can only be forked unspecified number
> of times. In extreme case, if "Foo Bar" is replaced with "Foo bar" _in
> the code_, then also the code is also forked. Not good.
> 
> Regarding the number of locales, I see things do not look that bad: we
> have en_US == C and en_GB only.
> Please correct me here.
> 
> My idea is to provide extra English translations that are variants of
> the originals but with sentence capitalization.
> Ideally that would be the two extra:
> - en_GBS (based on en_GB)
> - en_USS (based on en_US)
> 
> (S suffix == Sentence)
> 
> I believe both can be largely generated on demand.

The part after the underscore is the territory. What territory is GBS?

You probably want something like en_US at sentence. Feel free to bikeshed the variant name to use, but the locale name syntax is standardized to be language[_territory][.charset][@variant].

-- 
Nicolás