Hi,
Von: Rimas Kudelis
Gesendet: 27.12.10 15:10 Uhr
Are you sure? There were plenty of placeholders in the file exported by
Sophie. To me, it looks like most of the problem is actually in Pootle
itself, because it simply ignores XML tags in the translatable string.
The problem might look "simple" - but afaik, all (but one) free translation
editors share the same problem.
Pootle has the problem, I'd bet virtaal (based on the same toolkit) has the
same problem. Wordforge Editor removes the inline tags (just tested). OLTE
removes them (spent some days on trying to find a solution, but it woult mean
a major redesign of the internal translation handling in the editor).
Afaik, only Lokalize handles inlines correctly. I did not check other
tools like OmegaT yet.
So after all, for document translation XLIFF is the better (because more rich)
file format, but it lacks the tools :(
regards,
André
--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***
Context
- Re: [libreoffice-l10n] Translating ODF files on Pootle · Andre Schnabel
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.