Summary Statement of Work (SOW): Our team of engineers review all the factors listed above, collaborate with the appropriate persons in your organization, understand the release timeline requirement, and produce a statement of work.

1. The applicable globalization task line items.
2. An estimate in terms of time and cost.
3. The tentative milestones for completion of tasks to meet your timelines.

We are able to scale up the number of people assigned to your project based on your timeline and release requirements, and this number is reflected in the costs estimated.

Detailed Design Strategy: In addition to the summary SOW, many additional tasks are undertaken to provide an enhanced design and implementation strategy document.

1. An in-depth review of the code is performed.
2. The application development and test environment is set up.
3. Many I18n-specific code changes are injected into the application to get a more hands-on feel for the current application I18n state.
4. A design document is prepared with problem descriptions and solution snippets for the various I18n issues discovered.

Text Storage Issues (unchangeable or incorrect in the UI due to their hard coded nature)

1. Hard-coded strings that are displayed to the user
2. Ambiguous text created by concatenations of multiple fragments
3. Messages used multiple times, but just slightly different in case or exactness
4. Collation & Sorting of Text
5. Menu Accelerator & Shortcut Keys
6. Fixed User Interface Layout (disallows bidirectional languages, truncation of text display)
7. String comparisons and decisions based on user inputted text

Data Format Issues (due to hard coded formats oblivious of the locale/culture)

1. Date Format (Weekdays, Short vs Long formats, etc.)
2. Time Format (24-hour formats, am/pm indicators, etc.)
3. Number Format (use of comma vs periods for separators)
4. Currency Symbol and Format
5. Personal Name components and Address components

RESULT: The internationalized application will be able to:

1. Support mock translations, and allow one or more pseudo-locales to be selected by the user
2. Have all user-visible text and images external to the application source files
3. Integrate with the locale to format date, time, number, and currencies
4. Support the appropriate Unicode or other encoding used by the locale
5. Preparation of a Localization Kit - a centralized package of all externalized UI text and other textual resources such as images, help files, manuals, release notes, packaging boxes and collateral.

Translation (T9n) involves the preparation of a translation kit (tkit) sent to native translators for lingusitic conversion.

1. Translation Kit: Processing all the text in a Translation tool such as WorldServer or Passolo to produce a canonical spurce language agnostic format of text for each required language pair. Example, English → French, or English → Japanese language pairs for storing translations from English to French/Japanese.
2. Linguistic Conversion: Native translation of source language text to destination language pair by translators and lingusitic reviewers.
3. Native Translations: Native speakers, professionals, specialized translators, experienced in the industry of the source text are sensitive to the complexities of translation are selected for providing native translations.
4. Build Integration: Reverse the translated kit back to original resource format, and include in the source build and packaging process.

Layout issues result in garbled and truncated text in the user interface, and even loss of functionality.

1. Application behavior issues due to dependency on text in some buried logic.
2. Truncation due to long translations for short source language strings.
3. Encoding support issues resulting in translated strings showing up as garbled UI text.
4. Adapting UI design and layout to properly display translated text. Example, form display needs to use right-aligned name and left-aligned value fields.

Adaptation issues require knowledge of locale-specific conventions beyond the textual language difference.

1. Converting to local units (such as currencies and units of measure).
2. Adapting colloquial dialect, graphics and colors to make sense in target markets.
3. Using proper locale-specific formats for date and time, addresses, and phone numbers.
4. Addressing local regulations and legal requirements.
5. Converting pieces of technical communication.

RESULT: The localized application will be able to:

1. Show the entire UI properly localized in a particular language.
2. Allow tkit exchanges easily with translation vendors.
3. Integrate translations easily and seamlessly back into the application infrastructure.