Welcome to Universal Dialog

Typical Localization Activities

Our localization process is the proven way to transport all the meaning and flavor of your original work to all new audiences

photo-faq

Translation of all natural language strings that can be displayed or printed; Adding locale specific features such as spelling, hyphenation and grammar checking. This can also include additional locale specific functionality to the core application; Selecting the proper notational and other conventions for the target locale; Adjusting objects containing natural language strings such as menus, dialog boxes, buttons, etc. The expansion which occurs when translating the natural language strings often causes visual corruption of these objects (or truncation of the strings); For example, expansion for the English-Spanish or English-Portuguese language pair is 30% on average, but can be much higher for short strings Managing changes to the original application in order to reflect these changes in the localized versions; Testing the localized software on the target platform. For Asian languages there is a stronger need to test core functionality; this is also true in such areas as word-wrapping, keyboard input, handling of wide characters, etc. Therefore, test expenses are much higher than for ISO8859-1 (Latin 1) internationalization and localization.

Formatting requirements:

Different regions in the world use very different notational conventions for writing time, date, numbers, currency, etc. Time is represented by both a 12-hour clock and a 24-hour clock. The separators can be period or colon. Date has many representations: sequence of month, day and year; different separators; different calendars (lunar, Gregorian); different abbreviated names for the months, etc. Number representations differ in separators: decimal separator or radix character; Thousands separator; List separator Currency units and presentation differ greatly from country to country.

Localizing Web Site:

Given the explosive growth in e-commerce, localizing your website means smoother and more effective communication with potential customers in foreign markets. Website localization is a complex process requiring specialist knowledge. As well as being highly skilled translators, members of our web team are well versed in HTML, scripting languages, art localization and functionality testing. Through our technology and tools, whether for images, animations or for websites constructed with sophisticated techniques, such as PHP, PERL, ASP, JSP, XML, JAVA and PXE, you will get just what you want.

Website localization involves several steps:

Reviewing current site against the needs and expectations of your target audience Translating all text (including embedded graphics) Modifying or altering images to avoid negative cultural biases Reengineering site architecture to ensure proper functionality on various platforms and levels of technical/telecommunications infrastructure Testing completed site against parameters established during initial review Formalizing procedures for future global content development and release

Software Interface:

The software resource files are usually the first to be localized. When provided, glossaries from previous versions of the software are used and updated with new terms. Otherwise, new project glossaries are generated from the resource files with the aid of term extraction software. The glossary maintenance process sometimes continues even after the resources localization. When this is the case, all changes are tracked and applied to the other components of the project, typically the help and documentation files. Then, the software is re-built with all its localized resources and elements, using the same build environment and tools as the source language version. The localized software is thoroughly tested, dialog boxes and other interface elements are resized as needed, and any key assignment conflicts are corrected.

Online Help System:

The source help files are prepared for translation by means of a translation memory software tool. Besides allowing the use of approved translations from previous versions or related projects, this valuable tool also ensure style and terminology consistency throughout the translation process. In order to eliminate the risks of corrupting the original formatting and styles of the help RTF files, the translators and reviewers do not work on the original RTF files. During the preparation stage, alternate files are generated, including all the contents and a look that resembles the original document formatting, but with delimited fields for source and target strings, and comments. Besides preventing inadvertent changes to the document formatting, this process also frees the linguistic team from not-so-steep learning curves and the hassle of working in an unfamiliar environment. Separate files are created for the topic titles and keywords, avoiding the risky and tough task of editing them as footnotes and allowing the use of the same translation memory tool mentioned above. When the translation of the RTF files is done, the translated text strings are transferred back to the original files, localized graphics and artwork (if any) are inserted and the help system is recompiled. Thorough tests are performed in order to ensure the help functionality is preserved (although the jumps and links are inherently left intact during the translation/editing phase).

Documentation:

The translations of the software documentation follow roughly the same procedures as the help files. The doc files are prepared for translation by the translation memory tool and, to avoid accidental changes to the document formatting (styles, templates, layout, etc.), the linguistic team do not work on the original files, but on alternate files generated by the software tool. When the translation is completed, the translated text strings are transferred to the original files, retaining all the source formatting. Where applicable, formatting changes are applied. Then, localized pictures and artwork (if any) are inserted and the documentation goes to the final DTP stage. Finally, a thorough editing/proof-reading of the final documentation is performed in order to ensure everything is correct.