Hello,
This is just a heads-up that LibreOffice Online UI pot was updated in
Pootle today.
Oops, I see that there is a new master branch now and the ~28,000 words that I have already
translated in 5.3 but must click through again in 5.4 just got doubled…
Please, can someone merge my recent work in the Bulgarian translation of 5.3 into 5.4 and Master?
I translate via Pootle and at some point a big chunk of new strings got introduced in parallel in
5.3 and then-master. I continued working in 5.3, hoping that what I do will get integrated into
master but now I would need to re-translate all those strings not once, but twice (and also
translate twice everything new that is common between 5.4 and the new master, etc.).
When a new master gets branched from a not-fully translated previous branch, effectively doubling
all untranslated entries, shouldn’t later the work done on those entries in the older branch be
transferred by default before the next branching which multiplies the empty entries yet again
(while in the original branch, there already are translations for them)?
It’s 4 am here, so I hope the above still makes sense. :)
TIA,
Mihail Balabanov
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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
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.