On Wed, 2015-01-28 at 10:20 +0100, Stephan Bergmann wrote: > On 01/19/2015 11:03 AM, Sophie wrote: > > - if there is a way to script changes, script them otherwise wait until > > there is a script available to commit them > > I am not sure I understand you here (to me, the "otherwise" part reads: > "if there is no way to script changes, wait until there is a script > available," which would not make sense). > > When talking about (developer-side) scripting, is it actually OK to > commit modifications to the translations in the translations git > sub-repo? My understanding was that such modifications would be > overwritten by the next "import commit" (as typically done by Andras, > AFAIU from some Pootle database).
This has always been a clear as mud to me as to what the *current* translation workflow is and how as a developer I can fix a translation. e.g. in the past changing the "Letter" size translation in Spanish to "Oficio" instead of the literal translation was a pain. And right now I want to fix a gadzillion Indic translations short-cuts to ascii chars and not characters that only available via IM. What I want to do is to commit to the translations git repo and forget about it. Does that work ? C. _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
