This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
One of our community’s MVP, Mohammad Daoud, is giving us a preview of the Arabic version of Microsoft Dynamics GP he has created.
He has used Modifier and Report Writer to update all the messages and strings in the dictionaries, which leaves the original application dictionaries unchanged.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Translating Dexterity Applications Series.
The final topic in the series is one that was added later after I was asked about how to handle translated applications when writing customizations.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Translating Dexterity Applications Series.
After a chat with Mariano Gomez, who was directly responsible for the creation of the first Spanish version of Microsoft Dynamics GP, I realized that I had not yet covered some additional areas that will need translation. This post will try to cover the other areas you need to consider.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Translating Dexterity Applications Series.
During the course of this series we have discussed how you can change terminology, or even the entire language of a Dexterity application. We have discussed flipping the windows for languages that read from right to left. We have also discussed using languages which have different character sets.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Translating Dexterity Applications Series.
So now we know how to translate the language, which is fine for a “western” language, but what about languages that are read from right to left rather than left to right; languages such as Hebrew and Arabic.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Translating Dexterity Applications Series.
Now that we understand how to write the Dexterity code to allow it to be easily translated and also work in a multi-lingual system. The next step is actually translating the strings and messages.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Translating Dexterity Applications Series.
With large international companies using Microsoft Dynamics GP in multiple countries, we are seeing the need to be able to run more than one language of the application on the same system.
Even if an application can be easily translated, you may still encounter problems when you run the application in multiple languages on the same system. This type of environment is called a multi-lingual system and it required another set of “Best Practice” rules.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Translating Dexterity Applications Series.
When Great Plains Software worked on translating the Dynamics product into multiple languages they came across a number of problems. Even though Dexterity was designed to allow easy translation, the international team found that developers needed to follow certain “Best Practices” to truly have a translatable application.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
From the Translating Dexterity Applications Series.
When Great Plains Software decided to update their text based Great Plains Accounting (GPA) software for the graphical user interface (GUI) world of Windows and Macintosh, they found that a suitable development environment did not exist and so decided to develop their own. Hence we have Dexterity.
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
After a number of questions about translation recently, I have decided to focus on Dexterity’s multi-lingual and translation capabilities for the next couple of weeks.