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



This is something I already explained you. You know that Jean-Baptiste
and me are coordinating together either directly or on the French QA
list. The workflow is not documented in French, but in English on the
wiki. Jean-Baptiste translate online on Pootle, while I translate
offline using OmegaT or editing the .po files when I'll grep for
corrections.

ok and when you translate offline then, you don't have any problems as I described, ie Pottle 
saying a string is fuzzy whereas it is processed? Any new contrib could do the work with 
Jean-Baptiste and you I suppose?

I don't find the wiki page again and do not remember all the explanations, all the more as when you 
did the process was changing because translation was being integrated in the code directly or 
something like that. So I would be glad to have it again to see how a contrib could help JB and you.

Thanks 

Regards 



Cheers
Sophie
-- 
Sophie Gautier sophie.gautier@documentfoundation.org
GSM: +33683901545
IRC: sophi
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


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.