|
Thanks, I will have a look.
Regards
Jonathan
Personal Email
Business Email
----- Original Message -----
Sent: Wednesday, December 11, 2002 6:11
PM
Subject: RE: [stellation-res] String
Internationalization
Hi Jonathan,
I'm sorry for the delay in answering. Here
you have the XLIFF DTD and tomorrow I will send you the TMX
DTD.
Regards,
Rodolfo
On Thu, 2002-12-05 at 10:49, Jonathan
Gossage wrote:
-----Original
Message-----
From: stellation-res-admin@xxxxxxxxxxxxxxx
[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Rodolfo
M.Raya
Sent: December 5, 2002 4:29 PM
To:
stellation-res@xxxxxxxxxxxxxxx
Subject: RE: [stellation-res]
String Internationalization
On Thu, 2002-12-05 at 07:02, Jonathan Gossage wrote:
> >-----Original Message-----
> >From: stellation-res-admin@xxxxxxxxxxxxxxx
> >[
mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Rodolfo M.Raya
> >Sent: December 5, 2002 12:24 PM
> >To: stellation-res@xxxxxxxxxxxxxxx
> >Subject: Re: [stellation-res] String Internationalization
> >
> >
> >On Tue, 2002-12-03 at 10:43, Jonathan Gossage wrote:
> >> > May I suggest that you store strings in an XML file?. Maybe using
> >> something like:
> >> >
> >> > <resource id="filemenu">
> >> > <string xml:lang="en-us">File</string>
> >> > <string xml:lang="es">Archivos</string>
> >> > <string xml:lang="fr">Fichier</string>
> >> > </resource>
> >> >
> >> > This can help in the future with the localization process.
> >> >
> >> > Regards,
> >> > Rodolfo
> >> >
> >> > --
> >> I am reluctant to use XML for the internal persistent storage
> >because of
> >> performance issues. Management of localized strings has been
> >identified by
> >> the Eclipse team as a performance problem area so I was
> >planning to use an
> >> optimized internal persistent layout. I think that the import/export
> >> facilities should be capable of putting the internal storage into XML
> >> format. In fact I would make this an extension point so that
> >different XML
> >> layouts could be generated to meet the needs of different tools.
> >
> >Hi Jonathan,
> >
> >If you provide the extension points to export/import strings then we can
> >write the tools to handle XML formats. Don't worry about this.
> >
> >Regards,
> >Rodolfo
> >--
One of the issues that I see here when exporting to external tools will be
in dealing with strings that are made up of fragments where some of the
fragments are text that needs to be translated and other fragments are data
to be converted to string format for final presentation. Typically this is
done programmatically, but to get good translations for this kind of thing
the external tools will need to be able to reconstruct and present the final
string to the translator so that correct grammatical and usage conventions
will be observed in the final product.
A similar issue will be where different gramatical forms (e.g. word plurals)
will be required depending on the values of data inserted into the string.
Any XML formats that we come up with should be capable of describing these
relatively complex requirements. The real problem may occur if the external
tools do not have the power to handle such situations. Hi
Jonathan,
Usually the text is converted to XML format and divided
in "segments" before translation. A segment can be one string or just part
of it.
Translation tools deal with segments of text and
professional translators must reconstruct the context and provide the
right localization.
The standard XML formats used in translations
are TMX and XLIFF. Both formats contemplate all the necessary stuff. If
you are interested in the subject, I can send you the DTDs that describe
TMX and XLIFF.
Regards,
Rodolfo
Yes, I would definitely like to see them. It may make a difference
in the internal structures and support code if I structure things with the
export need in mind.
Regards
Jonathan
Personal
Email
jgossage@xxxxxxxx
Business Email
jonathan@xxxxxxxxxxxxxx
|
