Date: prev next · Thread: first prev next last
2017 Archives by date, by thread · List index


Thanks, this looks promissing,
I could work with this.



On Thu, Dec 14, 2017 at 1:08 PM, Christian Lohmaier <
cloph@documentfoundation.org> wrote:

Hi *,

Am 13.12.2017 um 19:37 schrieb Berend Ytsma:
I don't see any difference,
The only thing i see is that there is now 1 suggestion.

Hmm. For some reason pot2po run separately does manage to get the
translation, although it fails when using pomerge2 with the "use pot2po"
switch.. Strange.
(and in fact even stranger that it still managed to add back 155565
strings nevertheless...)

I'm now running a pot2po-only script, that should fill in the gaps (but
will flag ~all strings it finds as fuzzy, so removing the fuzzy marker
still is an excercise for another script)

ciao
Christian

--
Christian Lohmaier, Release Engineer
Tel: +49 30 5557992-60 | IRC: cloph on Freenode
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: http://www.documentfoundation.org/imprint



-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://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.