• Technology of adding a new language and producing language pack.
• Localizing so many XML files with huge size of strings.

The first section is possible only by Microsoft official tools, but the second one simply is translating more than 50 Resource files which include thousands strings, can be translated by 2 experts during 3 months. But some important points should be mentioned for section 2 which I listed here.

Any word selected for an original term must be unique and repeat everywhere

Otherwise, not only users would be confused, but the software will not work properly. For example if you use a term in Workflow infrastructure and different term in user interface, system will encounter some problems to perform the related workflows. Also recovery is disaster or impossible most of the time. We localized SharePoint in different steps, and then spend sufficient time to use it practically for discovering and removing eventual errors or improper words and phrases. After all of these we start the next step and translating another part. So it is not recommended to translate and type this product with 2 experts in 3 months!

Using standard glossary of Microsoft for localizing SharePoint

It is important to use same terminology and standard glossary of Microsoft that will be used to create Persian Language Pack for 2007 Microsoft Office Systems. Because of it, we have endeavor after making this synchronization. The existent glossary approved by Microsoft in Dubai office does not have desired quality, whereas it contains many Arabic phrases!

Localization based on application of pages

In our method, localizing pages and applications and templates is based on cognition of page's concept and usage. Although this method takes more time to get result, but the result is guaranteed as a high quality product. So our product has implemented practically in our projects since 2006, even before releasing the final version and Arabic Language Pack by Microsoft and it's still under development after 2 years!

 No WORD by WORD translating

His is common method of translating but not recommended for a the critical application platform like SharePoint, because there is some parts in this technology that are not known and in use, although we have experienced it practically during 6 years. So the best to do is to leave some parts we don’t know without translating. Of course these parts are not related to the user interface but in administrative parts.
Conceptual localization considering user interface
The principal parts of user interface must be translated so attentively. Phrases should be selected according to their meaning and usage. You should attend to the elegancy and proportion of phrase length, interface output or delete some words because of it, or maybe use Latin word or an Icon instead. This process is developing during the practical projects.

Add Persian Language Localewith as Microsoft standards

Most of the companies, who have started to localize the software, are changing the English language or Arabic one, via 1033 or 1025 Locale, while you should add 1065 LCID which is related to Persian Language. Following this method is more significant when a new product would be created base on this language. Obviously the products based on a language do not work on another language. So this is very important to add 1065 Locale as Microsoft’s standard for other languages.