Andras Timar píše v Po 04. 04. 2011 v 10:54 +0200:
Hi Petr,
2011.03.23. 20:01 keltezéssel, Petr Mladek írta:
, but I filed a bug
(http://bugs.locamotion.org/show_bug.cgi?id=1883) because I think it
is easier to do the language fallback with translate-toolkit, than to
fix fdo#35067 and fdo#35068.
well, we need to support also system traslate-toolkit; The question is
whether to add strict dependency on the new version or make the feature
optional; I think that the strict dependency might be more safe but...
The second patch at http://bugs.locamotion.org/show_bug.cgi?id=1883
actually works so the bug has been resolved. Translation-toolkit 1.9
will contain it.
Cool
We need this patch, i.e. the --skipsource switch. Otherwise there will
be regressions in localizations (fdo#35067 and fdo#35068 - originally
fdo#33189).
I don't know how to handle this, maybe we can wait for the
translation-toolkit 1.9 release, then require version >= 1.9 for system
translate-toolkit.
I have added the patch to the libreoffice-3-4 branch, see
http://cgit.freedesktop.org/libreoffice/libs-extern/commit/?h=libreoffice-3-4&id=f909227b9e10aeeb0041d31f998236411d653d6b
Are you going to add a strict dependency on this feature? In this case,
it would be great to improve the configure option for the system
translate-toolkit. I could do it if you want.
Best Regards,
Petr
Context
- Re: [Libreoffice] l10n based on PO files (continued)
Re: [Libreoffice] l10n based on PO files · Petr Mladek
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.