Hi all,
As you may have read in the minutes of the ESC call, Olivier reported an
issue with the help files and translation for 5.2:
+ Many strings are the same content but with xml tags placed differently
+ same visual result
+ issues with translators ahead, must find support for a
script to fix this
=> need a script to undo this; or un-fuzzy-them.
and I reacted to that:
* l10n (Sophie)
+ will ask on the l10n list wrt. scripting
+ developer support appreciated.
+ how urgent is it ?
+ since 5.2 is due in August - so plenty.
+ is it only po files, or UI files too ? (JanI)
+ only help files; for pt_BR: 57k new words to review.
+ can compare 5.1 vs. master dbs (JanI)
AI: + unwind / script changes here (Christian)
So to make it more explicit, is there among our group somebody able to
write a script that will remove fuzzy strings when it's only and xml tag
that has been moved?
Thanks in advance :)
Cheers
Sophie
--
Sophie Gautier sophie.gautier@documentfoundation.org
GSM: +33683901545
IRC: sophi
Co-founder - Release coordinator
The Document Foundation
--
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
- [libreoffice-l10n] many fuzzy strings due to xlm tags move in 5.2 help files · Sophie
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.