So, Miloš,

this is probably the place with your updated script odtcleant:
https://github.com/milossramek/translation-scripts/tree/master/odtclean

Lp, m.

V V pet., 18. dec. 2020 ob 09:42 je oseba Milos Sramek <
sramek.mi...@gmail.com> napisala:

> Hi,
> I have a new version - I'll put it on github, so that there is a well
> defined place to find it.
> m
>
> On 12/17/20 8:55 PM, Olivier Hallot wrote:
> > Hi Milos, All
> >
> > Em 17/12/2020 16:41, Milos Sramek escreveu:
> >> Hi,
> >>
> >> I suggest to include file cleaning in the workflow. In cleaning one
> >> removes direct formatting, which is necessary for translation. Currently
> >> I do that after a guide is published - the cleaned files can be found
> >> here:
> >>
> >>
> https://nextcloud.documentfoundation.org/index.php/apps/files?dir=/Shared/SK%20community/Cleaned
> >>
> >> The current problem is that nobody knows about them and a new version of
> >> a guide starts from an uncleaned version in the Published and thus I
> >> have to repeat the laborious manual cleaning part again an again.
> > BTW, last time I tried odtclean.py in my Linux box it failed, something
> > related to python version. Actually, is it still of use?
> >
> >> My suggestion is to add another step after step 7 in the "How to publish
> >> a chapter" section (page 15, 2 - Producing LO Guides.odt): a "Cleaned"
> >> directory, the contents of which will then be used to start a next
> >> version of the guide. I will then produce the cleaned files.
> >>
> > I think the cleaned files should be the published files. In other words,
> > only publish cleaned files.
> >
> > Olivier
> >
>
> --
> email & jabber: sramek.mi...@gmail.com
>
>

-- 
To unsubscribe e-mail to: documentation+unsubscr...@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/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

Reply via email to