Definitions and Considerations

Internationalization is the process of designing a software program from the ground up so that it can be localized without modifications to the executable code. * It is the first critical step in producing a software application for global markets. Internationalizing an application allows it to support different character sets and cultural standards such as date, time, number, and currency formats.

Localization is the process of modifying a software product to conform to the expectations of a given user community. * Localization involves translation, layout modification, and preparation of the application for a specific market.

Because many companies don't understand the importance of internationalization, they often ignore it during initial development. And because many companies are unaware of the distinction between internationalization and localization, they don't schedule internationalization into their localization plan. Both situations create frustration-increasing development costs significantly and slowing time to market.

* Richard Gillam, 'Developing Global Applications in Java,' page 6 in seventeenth International Unicode Conference.

Localization and internationalization projects are complex. Real Idea has compiled a list of important considerations for any enterprise embarking on such projects.

1. Why is senior management buy-in important?
Senior management buy-in helps these groups become aware of the vital importance and complex processes involved in software localization and internationalization. It also contributes to the morale of enterprise staff assigned to the project and to the project's ultimate success.

2. Why is it important to define project scope and create a schedule at the beginning of a project?
Defining project scope and creating a schedule will help you in resource planning and will assist colleagues and vendors to work with you efficiently. It is important to define project scope and create a schedule for English and international versions of the product.

3. Why is it important to know whether the code and tools have been internationalized?
Because of a lack of multi-byte support, many testing procedures can't be performed until the software code and tools are internationalized-leading to postponement of the project or quality problems in the localize product. If you determine that the code and tools have not been internationalized, it is important to work with an internationalization expert.

4. Should I use different vendors for different languages or one vendor for all languages?
Generally, using fewer vendors saves time and increases efficiency. If, however, your company has a number of ongoing projects, it may be more effective to use different vendors for different languages.

5. What criteria are important in selecting a vendor?
The most important criteria are quality of work, reliability, and experience. Price is also important but should not be at the top of your list. Speak to colleagues who have done similar projects and speak to several vendor-provided references. You may then want to evaluate the vendor's performance on a small 'test' project.

6. What should I provide to potential bidders?
Your RFQ should contain the information necessary for your vendor to derive a project plan, schedule, and initial quotation. Visit our Questions for Enterprise Localization and Internationalization Project Managers for tips on creating your RFQ.

7. What should I expect after issuing an RFQ?
You will normally receive a project plan, schedule, and quotation from each vendor. In particular, you should receive the vendor's estimated schedule based on the timeframe you have outlined and the vendor's resource availability.

8. What materials will the selected vendor require for a localization project?
You should provide a glossary, a translation style guide, translation memory, test cases, a localization kit, and the necessary specification sheets for tools and desktop publishing ( DTP).

9. What is the best way to check on the vendor's progress?
Stay in close contact with your vendor and thoroughly review weekly progress reports. Carefully monitoring the progress of the project will allow you to address and resolve issues before they become serious problems. It is also important to involve your internal QA resources in localization and internationalization projects.

10. What is the biggest problem associated with localization and internationalization projects?
Ineffective communication. Open communication is the key to the success of any project-allowing you and your vendor to set expectations, clarify misunderstanding, and act on correct assumptions.

Real Idea has discovered that enterprise localization and internationalization managers maintain good communication with vendors but fail to keep internal support groups adequately informed-negatively impacting areas such as version control and tool development. Good internal communication can prevent problems that slow project progress and increase costs.

These questions are helpful in preparing your Request for Quotation (RFQ).

Localization

1. What type of software application product do you plan to localize?
2. What are the target languages for the project?
3. What operating systems will the localized product run on?
4. When do you plan to release your localized product?
5. Do you have U.S. product materials ready for localization? If not, when will you receive them from your U.S. product development team?
6. If your product is under development and planned for worldwide simultaneous shipment, do you have product milestones for your U.S. and localized versions?
7. What is the estimated localization project budget?
8. Have you localized this product previously? If so, can the vendor leverage your previous localized version?
9. Do you have the translation memories for your previous localized version? What kind of translation memory tool did your previous version use?
10. Do you have a glossary (or terminology list) for your English source materials and target languages?
11. What is the scope of the localization project?
12. What components do you plan to localize? (software resource files, online Help, HTML or XML files, or printed documentation)
13. Do your English source materials have graphics file? If so, how many are there and what file format(s) are they in?
14. Do you need your vendor to perform screen captures on the localized version?
15. Do you have word and page counts for your English source materials?
16. Do you need special tools to edit source materials? If yes, are those tools supported in the target languages?
17. Do you need your vendor to build or compile software source files or online Help files after localization?
18. Do you need your vendor to test and repair software source files and online Help files after localization?
19. Do you need your vendor to leverage online Help or Web files from/to printed documentation? If so, which tool do you use? Can this tool handle the target languages?
20. Do you have a process for leveraging this task?
21. In what file format is your printed documentation?
22. Which DTP tool did you use for English printed documentation?
23. Can this DTP tool handle your target languages?
24. What is the expected final output for printed documentation after localization (Film, PostScript or PDF)?

Internationalization

1. What type of software application do you plan to internationalize?
2. Which operating systems does the product run on?
3. To which target operating systems do you want to port your product?
4. When do you plan to release your product to the global market?
5. Are you planning worldwide simultaneous shipment of your U.S. and international versions?
6. Have your U.S. developers addressed internationalization considerations when they designed or developed the U.S. product? If no, then do you plan to develop an internationalization functional specification that outlines considerations such as:
    - Multi-byte input and output handling
    - Culture-specific features like country date and time formats and unique cultural behaviors
7. Do you have a product functional specification for your U.S. version?
8. Have you attempted to run the U.S. product on your target language platforms? If so, what was the result?
9. Which programming language did you use to develop your U.S. product?
10. What other types of software development tools did you use in building the U.S. product?
11. Did you use any third party or public domain library APIs to build your U.S. product? If so, which ones? Do they support your target language platforms? Is technical support available for them?
12. Do you have specific standards for your quality assurance testing procedures?
13. Do you have testing specifications, a test plan, outlines, or scripts for the U.S. version of the application?
14. Did you use an automated testing tool to build your automated test scripts? If so, which tool did you use? Does it support your target language platforms?
15. Do you have a standard Software Problem Report format that you want your vendor to use?
16. Do you have major milestones for internationalization engineering and functional testing tasks? Do you have a build schedule for your product?
17. Will your vendor be able to use your U.S. bug database? If not, what is your plan to handle your vendor's bug reports?
18. Do you want your vendor to perform onsite or offsite internalization services, and why?
19. Do you plan to maintain a single code base (U.S. and international versions)? If so, have you factored in the time for the code merging process?

Multi-Language Web Management

As global e-commerce continues to expand, companies' websites have become strategically important. Furthermore, given the nature of the Internet, many companies have found that they must host websites in the languages of their target markets.

When an English version of a website changes, all other versions of the site should change simultaneously. Change involves not only translating new content but also ensuring cultural appropriateness-a labor-intensive task. Assigning one person to the international site maintenance duties, as some companies do, is generally neither effective nor efficient.

Real Idea localization consultants provide expert multi-language Web management services. We assemble updated files, localize appropriately, and carefully review each language environment.