Dynamic Language Translation Services - Made Simple
!
In 12 universal languages:
The Dynamic Language Translation Service (DLTS) is a sophisticated toolkit
for implementing real-time language translation for web-based content.
The DLTS technology combines the popular features of Java Server Pages (JSP)
and the JSP Standard Template Library (JSTL) with online language translation to rapidly deliver
international support for web applications. DLTS automatically translates the content
for each user based upon the international location of the client browser.
DLTS builds and maintains re-usable Translation Dictionaries to meet the high-performance demands
of robust applications. The DLTS Translation Dictionary uses the Extensible Markup Language (XML)
format to deliver flexibility to content providers for editing and customization.
These translations are maintained for the life-cycle of the application.
Installing the DLTS toolkit is easy and modifying existing applications is simple.
To demonstrate the ease in which DLTS can be implemented the "MailReader" example web application,
distributed with the Struts framework, was updated with the DLTS toolkit following the instructions
in the User's Guide in less than 15 minutes. The new international version can be examined by selecting the Struts-Example tab.
The "Transdoc" sample application for document management was also updated with the DLTS toolkit.
The new international version of that application can be examined by selecting the Transdoc Example tab.
This is the familiar MailReader sample application enhanced with Dynamic Language Translation Service (DLTS)
technology and deployed as an international web application. It now provides translated content in real-time for many well known languages.
IFRAMEs
This is the Transdoc sample application for document management enhanced with Dynamic Language Translation Service (DLTS)
technology.
IFRAMEs
User's Guide
Installing the DLTS toolkit for Struts is easy and modifying the existing application is simple.
Download and Import the DLTS distribution JAR file.
Replace the
struts-bean.tld
and the
struts-html.tld
files with the DLTS versions.
Copy the
xlate-services.tld
file to the taglib directory.
Modify the home page
(index.jsp)
to include the following logic (part 1):
Copy and insert these lines after the last
taglib
entry in the home page.
<!-- INFOBASE Technologies - DLTS --> <!-- START: com.infobase_tech.xlate.usermods.HomePageMods-1 --> <!-- Home page modifications for Dynamic Language Translation Services --> <!-- Copy and insert these lines after the last taglib entry in the home page -->
Continue - Modify the home page
(index.jsp)
to include the language selection drop-down (part 2):
Copy and insert these lines after the
<body> html
statement.
<!-- INFOBASE Technologies - DLTS --> <!-- START: com.infobase_tech.xlate.usermods.HomePageMods-2 --> <!-- Home page modifications for Dynamic Language Translation Services --> <!-- Copy and insert these lines after the <body html statement -->
Convert any HTML pages to JSP files and update the struts-config.xml
file accordingly. (part 1):
Copy and insert these lines at the beggining of the new JSP file and remove any UTF-8 specifications.
<!-- INFOBASE Technologies - DLTS --> <!-- START: com.infobase_tech.xlate.usermods.HtmlToJsp-1 --> <!-- Web page modifications for Dynamic Language Translation Services --> <!-- Copy and insert these lines at the beggining of the html file -->
Continue - Convert HTML page to JSP file (part 2):
Copy and insert these lines at the end of the new JSP file.
<!-- INFOBASE Technologies - DLTS --> <!-- START: com.infobase_tech.xlate.usermods.HtmlToJsp-2 --> <!-- Web page modifications for Dynamic Language Translation Services --> <!-- Copy and insert these lines at the end of the html file -->
Re-build the project and then deploy as an international web application with real-time
multi-language support.
Remember that Chinese, Japanese, Korean, Russian and Greek languages often require special character sets
and fonts be installed to enable web browsers to properly display the content.
Technical Information
The DLTS Translation Dictionary uses the Extensible Markup Language (XML)
format to deliver flexibility to content providers for editing, customization and database
portability. Here is an example of the generated XML file.
<entry> <phrase> Now available in 12 different languages! </phrase> <translation> Maintenant disponible dans 12 langues différentes ! </translation> </entry>
<entry> <phrase> Dynamic Language Translation Services - Made Simple </phrase> <translation> Services De Traduction Dynamiques De Langue - Rendus Simples </translation> </entry>
</TranslationDictionary>
Translation Testing
To check a specific translation:
Select the languages.
Enter the input text.
Click "Translate"
DLTS Downloads
The DLTS v1.3 Trial Package supports the English, French and German languages and
is available for downloading and testing.
Download DLTS JAR File
Note that web browsers need to have the encoding for Chinese, Japanese, Korean, Russian and Greek languages enabled if those languages are to be supported by DLTS.
The list of available languages for the Microsoft Internet Explorer can be obtained by
clicking on the "View" menu selection followed by "Encoding" then "More" ... the Windows operating system CD is requested during installation
For additional information on Microsoft Multilingual User Interfaces (MUI) and Input Method Editors (IME)
please visit the Microsoft Live Search website.
DLTS Questions and Answers ...
Q.
What does DLTS cost and is technical support is provided?
Which other languages will DLTS support in future releases?
A.
DLTS uses Translation Dictionaries, which can be customized to contain the originating phrase
and translation for any set of languages. See the Technical Information tab for an example.
Q.
Why does the UTF-8 encoding have to be removed from the HTML files when converting to JSP and DLTS?
A.
An internal java component, which reads the web page text for rendering, has abnormally terminated when this encoding
specification has been made. Removing the UTF-8 specification from the header is the workaround.