Re: ITS IG Teleconference on Tuesday Apr-28-2009 At 15:00 UTC/GMT

Hi all,

Thanks Yves for your answers, is there a list of editors capable of
supporting, or supporting ITS markup? I guess it also means the Schema
or DTD used supports the ITS markup too.

Concerning packages for localization that highlight modified parts, with
context, I must say I have no idea how that is made, can you recommend a
simple source of information about that?

Many thanks,

Camille.

Yves Savourel wrote:
> Hi Camille,
>
>
>   
>> The idea is not to provide in the tool a user interface aimed at 
>> translators directly, but rather gateways for translation tools 
>> used by translators to access the content, translate it, update 
>> it, etc. For you people expert in such translation systems 
>> (translation memory, computer aided translation, automatic...) 
>> what form should take that gateway in your opinion? What 
>> communication protocol, what formats, what features?
>>     
>
> First, obviously, you would make sure the editor used to create your content allows the use of ITS markup, so terms,
> non-translatable parts, localization notes, etc. can be integrated or marked up in the document. Just that would be a big step
> toward helping the localization process.
>
> Then, I assume you would want to have some kind of diffing and versioning mechanisms that allows the system to know what parts have
> changed since last time you did a translation. This way you can generate packages for localization. XLIFF is probably your best bet
> now: most big open-source or commercial tools support it or are in the way of supporting it. You would want to provide full context
> if possible, so the translators can see the parts they have to localize in their content.
>
> Just providing those pieces will get you a long way toward a much easier localization process.
>
> Hope this helps,
> -yves
>
>