[tei-council] Re: roma, documentation, i18n

[Sebastian Rahtz]

Christian Wittern wrote:

>My stab at this would be to maintain the stuff in a stripped down ODD
>file, one per target language, which has a <elementSpec> for each
>element, in change mode and the only change is to provide the <desc>
>or <gloss> elements in the target language.  You could easily generate
>such a beast and pull in the current english one for reference, if
>desired.
>  
>
this coincides nicely with a conversation I had with Lou on Friday,
where we came to the same conclusion. One advantage is that
if the changes are written as a genuine ODD file, the person
working on it can generate test schemas and documentation locally.
However, for general use, we periodically merge all the separate I18N
files into the main P5 source, and enhance the processors to
do the right thing with multple <desc> and <gloss>

>These files should then be kept on SF in the I18N module. 
>  
>
yes, this sounds good, to let someone else pick up just the translations
and work
on them.

of course, we have the perpetual problem that when a new element is added,
or the <desc> is altered in the English original, we have to bring all
the translations
into sync.

dont forget attributes, and vallists, by the way


-- 
Sebastian Rahtz      
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

OSS Watch: JISC Open Source Advisory Service
http://www.oss-watch.ac.uk