[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Regarding LSR translation work

From: Jean-Charles Malahieude
Subject: Re: Regarding LSR translation work
Date: Tue, 17 Apr 2012 19:18:06 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1

Le 17/04/2012 11:46, Francisco Vila disait :
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

   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 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.

And you then have to run again the merry-go-round!

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.

This might as well solve this unfortunate problem we have regarding the impossibility to link to Snippets, and why not allow to have it translated (most of its content being already translated when in other manuals).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]