[Libreoffice] l10n process for help content (WAS: [PATCH] Update help fdo#31652)
timar74 at gmail.com
Mon Jun 27 03:23:14 PDT 2011
2011/6/27 Michael Meeks <michael.meeks at novell.com>:
> On Sun, 2011-06-26 at 18:57 +0700, Korrawit Pruegsanusak wrote:
>> On Fri, Jun 24, 2011 at 19:47, Caolán McNamara <caolanm at redhat.com> wrote:
>> > Seems nuts to me that its better to keep translations of incorrect help
>> > content in sync than to have at least some of them right, but *shrug*,
>> > whatever's easiest to manage.
>> Currently there are many help contents that obsolete or inaccurate.
>> But wrt the string freeze, we couldn't release the fix of them
>> (because they all must happen in master), and user have to wait for
>> the next 3.x major release to have them correct, which is every
>> too-long six months.
> Right - that is a pain, we'd like the stable branch to improve wrt.
> translations too - but of course we don't want un-translated English
> texts showing up either.
> I wonder if there is an analog of the patch situation, whereby we can
> back-port a set of string translations to all languages from master ?
The "master copy" of translations is with each l10n team and is not in
git or Pootle. That means we can back-port or fix anything in git or
Pootle, but translators can overwrite it with an older copy. So the
real challenge it to have something fixed at the translators' master
copy, which could be in Pootle, or a in a custom l10n system, or in
files on translator's hard disk etc.
More information about the LibreOffice