Re: Idea: each FAQ as its own xml file

Le 17 août 2004, à 16:59, BABA Yoshihiko a écrit :

>
> On 2004/08/17, at 23:40, Michèle Garoche wrote:
>
>>>>>>> I just looked at our translations of the Fink FAQ, and it looks 
>>>>>>> like
>>>>>>> some languages have fallen behind. In trying to sort it all out, 
>>>>>>> I
>>>>>>> became frustrated with the current source (.xml) file layout: 
>>>>>>> each FAQ
>>>>>>> entry is really a self-contained item that may be changed (or 
>>>>>>> added or
>>>>>>> removed), but we only have a single source file for the whole
>>>>>>> FAQ. Would it be better to have each as a separate file (which 
>>>>>>> the
>>>>>>> build system joins together)? That way when committing a change, 
>>>>>>> it is
>>>>>>> clear which FAQ item was updated and one could note that "this
>>>>>>> corresponds to english rev 1.38" to make it easy to keep things 
>>>>>>> in
>>>>>>> sync. This cannot be done now, because a single new revision 
>>>>>>> could
>>>>>>> involve many changed FAQs. It might be easy for some to be 
>>>>>>> translated
>>>>>>> quickly, but not others, but keeping track of corresponding 
>>>>>>> revision
>>>>>>> numbers requires knowing that they are all done.
>>>>>>
>>>>>> And how do you deal with faq referring to another faq, when one 
>>>>>> of them
>>>>>> is removed or renamed or merged if you split the faq in chunks?
>>>>>
>>>>> Same way we do now: by <chapter> and <faqentry> "name=" attribute.
>>>>>
>>>>>> The problem is not faq, the problem is to find people who can 
>>>>>> spend as
>>>>>> many time as it is required within a short delay to translate the 
>>>>>> whole
>>>>>> thing (not only faq).
>>>>>
>>>>> Exactly. That's I proposed this...to make it easier to see what 
>>>>> needs
>>>>> to be done, and make the task seem less intimidating (small units,
>>>>> instead of a giant file). It seems easier to organize 
>>>>> "this-language
>>>>> now corresponds to the current that-language" than to keep track of
>>>>> which "[translate] ..." emails have been dealt with.
>>>> For me, it makes the things a lot more complicated, so much files 
>>>> to deal with, and it is not so complicated to translate by chunks 
>>>> as I did. This way you know exactly what you do.
>>>>
>>>> I just say, if I may say something, I'm completely against it.
>>>
>>> I understand the complexity.  But, that doesn't solve the problem: 
>>> FAQ's in other languages don't match the English FAQ.
>> As far as I know, French FAQ matches the English one, unless I've 
>> missed something, which is not to be excluded of course.
>>
>> If others do not match the English FAQ, that is probably due to the 
>> lack of cvs updating systematically the tree before starting to 
>> translate one small chunk and before commiting this same small chunk, 
>> to be sure to catch the latest FAQ and also to the lack of forwarding 
>> systematically the cvs commit to the mailing list, and to update 
>> immediately the part which has already been translated and has 
>> changed in the English FAQ.
>
> Not only because of CVS problems.  It may be because other languages 
> have no translator.  And, as I belive, that is what Daniel is talking 
> about.
I don't understand here. If languages have no translator, there is no 
translation and I don't see how then there can be discrepancies between 
English and English.

If this is for calling new translators, then that is not by splitting 
the files that the problem could be solved, but more by making calls on 
native forums to invite people to join the translation team and answer 
the newcomers a bit more reactively and accurately than it has be done 
previously.

And to see what it is to be done, it's not too complicated to simply 
copy what I've done which encompass the files to be translated and 
always have a trace of what is currently on the works, what is finished 
and what is to be done, or any other sort of database/listing/table/cvs 
or the like... which reflects the works at any time, there are enough 
software on Mac or Unix that allows such things and then either put the 
result on a website or send it regularly on the mailing list. Anyway 
with this amount of translation works to do and in the perspective of a 
real team, you cannot simply jump into any file and translate it, a 
strong organization is needed.

Michèle
<http://micmacfr.homeunix.org>