Re: Regarding LSR translation work

[Federico Bruni]

Hi Francisco,

thanks for bringing this to the attention of developers!

Il 17/04/2012 11:46, Francisco Vila ha scritto:
> Hello all,
> As you know, we translators are constantly aware of how much pendant
> work we have, thanks to 'make check-translation'. For example, right
> now
>
>    cd Documentation
>    make ISOLANG=es check-translation | wc -l
>
> gives ten thousand lines as result, most of them from
> Documentation/snippets/.  The annoying thing is, 99 percent of this
> output is not relevant, yet it has to be reviewed by hand.


The list of files is given by:

make ISOLANG=es check-translation | grep 'diff git'

Well, looking at this output I'm so happy that I've not translated as 
much as you did :-)

> The wrong
> concept involved in our LSR translation-checking process is that any
> translators' work counts as pendant work for others. This is so
> because we have translations to all languages mixed in the same files
> which, if they change, count as, well, modified files. This is a loop
> and leads to absurdity. I do a local makelsr and commit a huge patch,
> only to mark all snippets/* as outdated for the rest of translators,
> which in turn can only fix this with a huge patch.
>
> I'd like to propose an issue aimed to fix it. In my opinion, English
> text for snippets should be kept apart with no translations in the
> same files. If code for the snippet is in the same file,
> check-translation should be smart enough to ignore it. Doc build
> process could take originals from there, and take translations from
> where they currently are, namely<ll>/texidocs.

Another solution could be keeping the current structure and changing 
only check-translation.py so that, when looking at the files in 
Documentation/snippets, it should check only the changes inside texidoc 
= "" and doctitle = "" strings.