2011/6/27 Michael Meeks <michael.meeks@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@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.
Cheers,
Andras
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.