Browse Prior Art Database

An Extensible Approach for Isolating Translatable Resources of a Preexisting XML Documents in Language-specific Sub-documents (Files)

IP.com Disclosure Number: IPCOM000012405D
Original Publication Date: 2003-May-05
Included in the Prior Art Database: 2003-May-05
Document File: 2 page(s) / 56K

Publishing Venue

IBM

Abstract

Globalizing Software Applications often requires the translation of XML documents (Files). Due to the fact that translated resources are an inherent part of the XML model definition, translatable resources(text) are almost always mixed with non-Translatable resources (logical resources that are constant and not affected by translation) within the XML markup language. This represents a major translation challenge as it is not possible for translation tools to properly recognize translatable material within an XML Textual object. In the standard translation process, the XML files are written in one specific language, usually English, and then sent to translation services centers. The translators then reproduce the document in other languages by copying the original and replacing each translatable element with the appropriate translations (This process is usually handled by translation tools) . It has been always problematic for the translator to determine which elements to translate? One solution has always been to heavily comment the source to specifically indicate which attributes/text is translatable. But this approach is certainly error prone and laborious. The approach also presents a maintenance nightmare as each time a Translatable XML file is edited by the Translators non-Translatable information gets translatable and unnecessary functional problems/defects are created.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 75% of the total text.

Page 1 of 2

  An Extensible Approach for Isolating Translatable Resources of a Preexisting XML Documents in Language-specific Sub-documents (Files)

Our proposed approach attempts to resolve the Isolation problem by carrying out the following main tasks:

1. Use a special key to flag translatable elements/attributes in the preexisting XML documents(files).

2. Extract the translatable resources of the XML document as follows:

A. Recognize the elements/attributes that are translatable by recognizing the special prefix (example: $$$_).

B. Separate an existing translatable XML document into one main non-translatable intermediary document and one language-specific(translatable) subdocument (file). This step is structure indepdent (i.e the Isolation process does not depend on the structure of the XML document).


3. Process the generated translation-friendly sub-document separately - send it to Translation Services Centers.

4. After translation, merge the translated XML sub-document with the intermediary XML document to generate the final translated XML document.

(The approach is in short: Flag translatable attributes/text by prefixing them with a special key and write a tool to extract all translatable attributes/text (flagged by the special key "$$$_") into one translatable XML file and one intermediary file (original file + Key) and later on merge the translated XML file with the intermediary file to get the final translated file).

|

XML file1

  Translatable attributes are prefixed wit...