If your organization deploys Microsoft Dynamics GP, formerly also known as Great Plains Dynamics, as its Corporate ERP system, and you are expanding internationally, we would like to give you some ideas about Great Plainstranslation to foreign language and implementation internationally. You should look at GP from two positions: first, interface translation and local characters entering and saving, and second - making your foreign subsidiary ERP application compliant to hosting country business regulations and practices (also referred as localization):
1.Which languages could be supported' There are the restrictions of ASCII table compliance. If your language is not ASCII compliant and requires Unicode characters support - we do not recommend GP, as its technology layer - Microsoft Dexterity doesn't support Unicode directly, at least at this time and in foreseeable future. Unicode typically means hieroglyphs: Chinese, Japanese, Korean. The rest of the World, including such languages as Arabic, Russian, Dari, Persian, Ukrainian, Latvian, Portuguese could be translated and supported
2.Translation technologies. We recommend you to review two methods. First method is based on Great Plains Dexterity, where you open Dynamics.dic in Dex and then export string resources to convenient file format (Excel, for instance), make required translation and then distribute customized Dynamics dictionary to your users. Second method is when you are exporting strings from Dynamics dictionary, translate them and finally import them into Forms dictionary (if you plan to have modified reports, you need to import strings associated with reporting into Reports.dic). This second method requires Customization Site Enabler license, however in our opinion it is preferred, as you do not have to expose your users to bug fixing cycle. Dexterity is more powerful and flexible, however it may require additional programming and debugging
