Sign In/My Account | View Cart  
advertisement

Article:
 Translating XML Documents with xml:tm
Subject: xml:tm approved as a LISA OSCAR Standard
Date: 2006-07-26 01:26:39
From: Andrzej Zydron

xml:tm as been approved on 17th July 2006 by the LISA OSCAR Steering Committee for public comment prior to final ratification as a standard. XML-INTL has provided the driving force and technical architecture for this critical Localization Industry Standard. The xml:tm standard was developed by XML-INTL and donated to LISA OSCAR for consideration as an OSCAR standard. "This is a great day for the XML and localization communities. xml:tm provides a radical new way of approaching the authoring and localization of XML documents. It is a perfect companion standard to DITA (Darwin Information Technology Architecture)" stated XML-INTL CTO Andrzej Zydroń.


xml:tm is the vendor-neutral open XML standard for embedding text memory within an XML document. xml:tm leverages the namespace syntax of XML to embed text memory information within the XML document itself. xml:tm provides a radical new approach to the task of authoring and translating XML documents. To learn more about xml:tm, please visit the LISA OSCAR xml:tm page - http://www.lisa.org/standards/xmltm/


Previous Message Previous Message   Next Message Next Message


Titles Only Titles Only Newest First
  • xml:tm approved as a LISA OSCAR Standard
    2008-03-12 16:10:47 T2aki

    I am frustrated by a limitation in a Translation Management System we are about to use to translate DITA XML files. The TMS doesn't allow translators to add or remove in-line DITA tags, like "uicontrol", used in the source. All languages have to have the same number of these tags as English. This is the idea.
    For example, if the source reads "Click <uicontrol>OK</uicontrol>", then your translation must have one uicontrol tag, not two. Well, normally this is fine.
    But, especially when translating into Japanese, in which you need to add different or localized information, this limitation causes troubles. This limitation might work well to make translations consistent or to verify tag structures in translation. There might be a workaround but the limitation itself is against the localization idea, I think.
    Ah, what do you think about this limitation?


Sponsored By: