Welocalize Summer Newsletter

Summer 2005

The Path of Localization

Personnel News

 

          

 

 

                 Flash: Pre-localization
      

                 Tech Tip

 

 


Willem Stoeller Featured in

Client Side News Magazine

Excerpt Below. For the full article, please contact willem.stoeller@welocalize.com

CSN is pleased to offer another insightful and useful article from Willem Stoeller, a former professor of localization principles. Willem is now a VP at Welocalize. However, he still frequently teaches localization topics at the Localization Institute, Localization World, the CSN Expo, and LISA. In this article, Willem addresses the first two questions in the standard "path of localization."

THE PATH OF LOCALIZATION

The path of localization consists in addressing the following questions:

• Is my organization ready for global software?

• Is my software ready for localization?

• Which of the localization activities should I outsource?

• Which vendors should I use?

• How do I optimally manage the localization process?

• What are the major pitfalls in localization?

IS MY SOFTWARE READY FOR LOCALIZATION?

A corporate globalization strategy provides you with specific localization requirements for each product-market pair. Nowadays, few companies apply the same localization requirements to all products and markets. In order to optimize the use of a localization budget, it is necessary in the early stages of product definition to define requirements for each product-market pair in terms of the following:

• Components to be localized – Core software, install, help, documentation, licenses, etc.

• Degree of localization – Beyond mere translation, there are varying degrees of cultural adaptation. The target user profile and the intended features of the software should drive this.

• Release dates -- Simultaneous release might be a necessity for a web-based application, while a two-month lag might be acceptable for a technical application with a relatively long product lifecycle. These localization requirements in turn drive the internationalization requirements for the software.

 


Tech Tip

Producing Edited Video, Integrating in Flash

 

In Camtasia, produce AVIs with the same frame rate as the Flash file (usually 12 fps).  Colors should be set to Automatic.  Other settings should be left as default unless otherwise specified.

 

Be careful when sending videos produced in Camtasia to users on another system – Camtasia’s codec must be installed on their system if they are to view the AVI properly.

 

 

 

 

 

Quarterly Summary

I am happy to report that our record growth trend has continued.  Q2 2005 marked our 14th consecutive quarter of growth.

We achieved a 27% increase in total revenue over the first half of 2004. 

We also won the largest contract in the company’s history during Q2!

Thank you for a great quarter.

 

E. Smith Yewell

President & CEO

smith.yewell@welocalize.com

 

 

Personnel News

 

We welcome Dana Barras to our Sales team as a Business Development Manager!

 

Dana brings a wealth of experience to our company having been a professional translator and a localization manager on the client side.  Here is the introduction to an article Dana recently wrote in Client Side News Magazine.

Having spent considerable time as both vendor and client in our evolving GILT industry, I’ve observed two themes fundamental to each viewpoint:

1. Solid translation output comes as a result of mastering a delicate calibrated balance among cost, quality, and turnaround time constraints.

2. The GILT industry delivers its services through an appropriate combination of the universal business construct—people, process, and technology.

For the full article, please contact Dana at dana.barras@welocalize.com.

 

 

 

 

 

Flash Pre-localization: String Translation, Externalization

 

By Butch Pfremmer

Vice President, eLearning Practice

butch.pfremmer@welocalize.com

 

 

Text strings in Flash are found in text boxes.  Text boxes can be static, meaning the text may not be dynamically changed; or dynamic, meaning the text that can be changed with the proper ActionScript; and input, meaning the user can enter text in the text field.  Text boxes can appear anywhere in a Flash application, and often the localization engineer's job is to hunt for embedded static text boxes and swap the strings they contain for localized strings.

 

If the task of searching for strings is too large, or there are many locales into which the application is to be translated, it may be necessary to change all text elements to dynamic text and externalize the strings to an XML or other file format.

 

An important part of pre-localization is the conversion of all text elements in the application to symbols that can be found in the library.  Text boxes hidden in the application outside the library are difficult to find in a complex Flash file.  In the library, text boxes should be placed in folders or grouped with symbols using some clear rubric to avoid confusion; either using a naming convention or content-relevant folder system.  Text boxes can then be manipulated with little effort simply by looking for them in the relevant library location.

 

Externalization

 

Externalizing embedded strings in a Flash file requires changing the text field in which each string occurs to Dynamic type text in the Properties panel and assigning the string a unique identifying variable.

 

After making the text dynamic, build a source XML file in the original language.  Each dynamic text variable will correspond with a node in the XML file.  The XML code will look like the following sample:

 

<?xml version="1.0"?>

      <parentNode>

            <childNode name="varName" value="A localized string" />

      </parentNode>

</xml>

 

The file must be saved in the Unicode format in order to support international character sets.

 

The ActionScript to load an XML file into a Flash movie can take many forms and may be located in any frame of a Flash movie.  In the interest of simplicity, put the XML loading and node assignments in one of the first frames of the Flash file (or the main Flash file, if the application is composed of more than one SWF or EXE). 

 

For most practical purposes, XML node values have no maximum byte length, though loading large XML documents in Flash may represent processing overhead that the application designer should take into consideration.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Welocalize US West
144 NW Overton St
.

Suite 125
Portland OR 97209
Phone: +1.503.274.2211
Toll Free: +1.800.370.9515

 

Welocalize US East
241 East 4th St.

Suite 207
Frederick MD 21701
Phone: +1.301.668.0330
Toll Free: +1.800.370.9515

 

Welocalize Europe
Nell-Breuning-Allee 10
66115 Saarbrücken GERMANY
Phone: +49.681/99294-0

 

Welocalize Japan

498 Kada
Wakayama-shi
Wakayama, Japan
Tel: 81-80-5326-1194



 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Thank you for reading.
(You can click here to Unsubscribe)

 

© Copyright 2005 Welocalize, Inc.