i18n: Starting Chinese Translation of Mercurial
mg at daimi.au.dk
Sun Jan 25 07:31:42 CST 2009
Mads Kiilerich <mads at kiilerich.com> writes:
> In an internal project we unfortunately couldn't extract translation
> strings by static program analysis. Instead we had to extract the
> strings on runtime, writing to a file when the translation engine met
> an unknown string. That had the advantage of getting the most commonly
> seen - and thus most important - messages extracted and translated
> Perhaps the Mercurial i18n engine could be extended with an option to
> do something similar, keeping track of how often each message
> translation is actually used. Sorting the messages by that frequency
> when translating would help translators to get started and focus on
> the most "important" strings, make it "cheaper" to get good coverage,
> and make it easier to establish a consistent terminology.
> Just an idea - I hope it could be seen as a way to improve i18n ;-)
It's a good idea, and I have already tried making mercurial.i18n.gettext
count the number of messages it translates. Unfortunately there are a
lot of messages that are translated without being used: the _(...)
entries in mercurial.commands.table and in the extensions cmdtable's
Even with no extensions enabled this results in about 250 strings being
translated on every startup.
VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20090125/1bf51be2/attachment.pgp
More information about the Mercurial-devel