Hebrew Software Localization

Hebrew software localization is the process of adapting the language, appearance, and functionality of a software application for Israel. Hebrew software localization projects should be executed by experienced teams of localization professionals who work in conjunction with your software development group, ensuring that best practices for global software development are followed.

To make your software relevant for Israel, all of its components should be localized. This includes the user interface, online help, databases, graphics, and documentation. It is important that all components are correctly localized and rigorously tested to ensure the resulting Hebrew software is linguistically, culturally, cosmetically, and functionally correct.

A Hebrew localization company should have solid experience and a comprehensive localization methodology, which includes at a minimum:

1. Hebrew localization kit review, analysis, and preparation.
2. Hebrew glossary and terminology development.
3. Hebrew cultural correctness assessment.
4. Hebrew translation, editing, and proofreading of the user interface, help, and documentation content.
5. Hebrew graphics localization, dialog resizing, and screen capturing.
6. Hebrew software build capability.
7. Hebrew online quality assurance.
8. Hebrew usability, localization, and functionality testing.
9. Client review and approval.

You will need to provide your localization company with the following information, collectively referred to as a "Hebrew Localization Kit." This information allows the localization company to analyze your software and to determine its Hebrew localization requirements. The kit includes:

1. All files in your development environment, specifically resource files (for example, RC, RC2, DLG, H, HH, CPP, EXE, DLL, and graphic file formats).
2. All documentation source files (for example, FrameMaker or Word).
3. All online help source files (for example, graphics, RTF, VBS, HTML, CNT/HHX/HHC).
4. Reference material (glossaries, past translations, style guides, etc.).
5. File names and types, including an explanation of each file's purpose.
6. The name and version of development, documentation, and online help authoring tools.
7. The location (directories/files) of any hard-coded literals which are in the user interface.
8. Original files of any third-party applications/components used.
9. Detailed build instructions (if applicable).
10. Test plan and test scripts (if applicable).