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

Hi Martin,

thank you for returning back to the issue!

Meanwhile I've thought a lot about "labor division" in the case of

Perhaps it would be best if the manual style cleaning (as described on 
would become one of the duties of the author, who prepares the published
files (but the list of their duties is already quite long now) and
preparation of the files in the Cleaned directory by running the script
(once a guide is published) would be a task for somebody else (me for
now). I think that it should not be among the author's duties, since I
think that running a python script on Windows for a non-developer is not
an easy task (I would, e. g. install the Windows-for-Linux subsystem and
install Ubuntu there :D ).

If we agree to add the  "Cleaned" directory (in my text below I
suggested "Prepared for translation", but "Cleaned is perhaps better), I
would create it in the 7.0 version of the Calc guide and Math guide,
which are already published, and do both the manual and script cleaning.


On 12/21/20 3:37 PM, Martin Srebotnjak wrote:
Just reminding of this suggestion by Milos from August 2020.


Lp, m.

V V čet., 6. avg. 2020 ob 14:39 je oseba Olivier Hallot <> napisala:

Forwarding to the documentation mailing list

Important topic.

-------- Mensagem encaminhada --------
Assunto: [libreoffice-l10n] Suggestion for workflow modification : a new
directory "Prepared for translation" with "cleaned" files
Data: Thu, 6 Aug 2020 14:30:14 +0200
De: Milos Sramek <>
Para: Libreoffice ln10 <>


document 'cleaning' has been mentioned recently in several threads. It
is a necessary step for subsequent translation of the guides to
different languages. As it  is currently done 'on request', I suggest to
add cleaning as a compulsory step to the workflow (described here:

Currently I put the cleaned files here:
Probably nobody knows about them.

What is cleaning about:

For translation we use the OmegaT tool, which extracts strings for
translation directly from the document's xml. This means that the
character formatting tags are visible for her/him (tags in OmegaT are
abbreviated to <f0>...</f0> or similar). Usually there are too many
useless tags (tags seem to remain in the code forever, even if
formatting is removed), which complicates the translation process (too
many tags, words split by tags to pieces etc). In cleaning all direct
character formatting is removed (by a python script) which decreases the
amount of tags to the necessary minimum.

My suggestion:

Add an additional step in the workflow after "Published" (after it in
order to not to change to current authoring workflow) by adding a new
directory "Prepared for translation". From there (1) a translator would
take documents for translation and (2) these documents would be used to
start a new version of the given Guide.

Who will do that:

I volunteer to take care of the cleaning process. I will also create a
guide, how to do that and also will place the script to the nextcloud,
so that eventually somebody else can do that. As a part of the cleaning
process one has to visually check the documents and change eventual
direct formatting to the an appropriate character style.

thanks for consideration



email & jabber:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:

Olivier Hallot
LibreOffice Documentation Coordinator
Comunidade LibreOffice
Rio de Janeiro - Brasil - Local Time: UTC-03:00

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:

email & jabber:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


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.