[Sugar-devel] [PATCH] sl#2815: Localization fixes.
silbe at activitycentral.com
Tue Jan 31 07:38:23 EST 2012
Excerpts from David Mason's message of 2012-01-31 03:16:14 +0100:
David, I'm assuming you replied in private accidentally, so I'm bringing
the thread back on-list.
> > Similar to your previous patch , gettext already flags this as a
> > format string. As this particular example is a bit more complicated,
> > I'm less averse to accepting the patch, but I'd still prefer a solution
> > that tells translators how to properly handle them without requiring us to
> > mention that for each and every format string in the code.
> We've just implemented a validator in zanata's translation editor that will warn translators when there is any change in printf style variables. I based it on the validator in translation toolkit, and I believe a similar validator is also available in pootle. Having translators performing translations through Zanata (www.zanata.org) or Pootle, or use translation toolkit or running msgmerge with appropriate options, could make handling of variables in translations a lot cleaner.
Sugar Labs already uses a Pootle instance , which Chris (who
requested the changes discussed in this thread) maintains.
Chris, what are the exact cases where format strings are troublesome? Is
it with translators using translation tools outside of Pootle (which
tools exactly?) or when translating inside Pootle?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 490 bytes
Desc: not available
More information about the Sugar-devel