Summary: Special msgid to let translators control
capitalisation, etc
                 Project: Freeciv
            Submitted by: jtn
            Submitted on: Sat 17 Sep 2016 03:01:29 PM BST
                Category: None
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: 2.6.0, 3.0.0
 Contains string changes: Yes



Patch #3028 hardcoded a behaviour in the Freeciv code that the Finnish locale
triggers certain messages to have their initial letter capitalised.

We could remove the hardcoding and let other translators opt in to this by
having a special msgid in whose msgstr translators can specify which such
magic behaviours they want. Freeciv would read this and act on it, instead of
looking at the locale name.

#. TRANS: not a regular string; controls special localization behaviors.
#. This is a comma-separated set of tokens that enable special
#. handling of strings. The values you can currently specify are:
#.  - autocap: uppercase first letter of notify messages
#.  - inflector: enable language engine that automatically solves 
#.    all problems of highly inflected languages (to be implemented)
#. If left blank or set to "-", standard behavior will be used.
msgid "?L10N_CONTROL:"
msgstr "autocap"

Is there some reason why this would be a terrible idea?

Other thoughts:
* Place it at the top of core .po files
* Make sure there's a non-empty value that means "do nothing", so that it
doesn't keep showing up in fuzzies
* I considered including the list of possible options in the msgid, so
translators get to know when there's a new one, but that means that the
behaviour gets turned off in the meantime. An alternative approach would be to
have a new msgid per option rather than a comma-separated string (I think I
prefer this, on reflection).


Reply to this item at:


  Message sent via/by Gna!

Freeciv-dev mailing list

Reply via email to