2014-02-20 21:25 GMT+02:00 khagaroth <email@example.com>:
On Thu, Feb 20, 2014 at 5:00 PM, Cor Nouws <firstname.lastname@example.org> wrote:
The idea is that the people that work in pootle, having to translate
dialogs that are sometimes strange to them, can look at how it was
before the conversion to ui.
A much better idea would be if someone actually converted the current
strings to the new format, so that we don't have to retranslate tons of
stuff just because of minor changes like a different accelerator character.
+ a million!!!
Before 4.2, I was pretty frustrated by having to retranslate previously
translated strings, because "~" had been changed into "_", thereby creating
some 6000 (IIRC) "untranslated" words. Sometimes TM helped, but with one or
two-word strings, there were often several alternatives, so I had to chase
the previous translation down in my 4.1 installation.
Btw, Andras & Cloph already wrote a script for automatically migrating help
translations, I suppose that could be reused (or used as reference, at
least) for UI as well. I can't find the thread on list-archive for some
reason, but look for "autofix for helpIDs in libo_help in progress (was:
Automatic translations and no suggestions in Pootle)" in your own email
(around 27 Nov 2013).
the Estonian team
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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