Microsoft Dynamics GP Developing for Dynamics GP
A blog dedicated to the Microsoft Dynamics GP Developer & Consultant community
 
Welcome to MSDN Blogs Sign in | Join | Help

Developing for Dynamics GP

by David Musgrave (Australia) and the Microsoft Dynamics GP Developer Support Team (USA)

News

  • Please use the Blog Feedback? - Contact Us link at the top of the page to email questions relating to the blog itself.

    If you wish to ask a technical question, please use the links below to ask on the Newsgroups. If you ask on the Newsgroups, others in the community can respond and the answers are available for everyone in the future.

    Please do not use comments on pages and posts to ask questions unrelated to the topic on that page or post.



    Dates of Interest:

    11-Jul-2008: Blog Created by David Musgrave.
    10-Oct-2008: First Post by Scott Stephenson.
    04-Nov-2008: First Post by Dave Dusek.
    11-Nov-2008: First Post by Beth Gardner.
    28-Nov-2008: First Post by Chris Roehrich.
    30-Dec-2008: First Post by Patrick Roth.
    24-Feb-2009: First Post by Greg Willson.
    22-Apr-2009: First Post by David Clauson.
    04-May-2009: First Post by Ryan Wigestrand.
    19-Jun-2009: First Post by Dawn Langlie.
    03-Jul-2009: First Post by Emily Halvorson.
    23-Sep-2009: Created Twitter account with blog feed.
    20-Nov-2009: First Post by Alice Newsam.



    WorldMaps Statistics since
    24-Feb-2009:




    Click for WorldMaps Stumbler



    Translator Tool:




    Social Networking

    Follow David Musgrave and the blog on:

    David Musgrave on Twitter

    David Musgrave on LinkedIn


    Disclaimer

    This blog is provided "AS IS" with no warranties, and confers no rights.

    The links in this blog may lead to third-party Web sites. Microsoft provides third-party resources to help you find customer service and/or technical support resources. Information at these sites may change without notice. Microsoft is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.

Contents

Favourite Posts

Blog Links

Newsgroups Links

Resources Links

Dexterity and Double Byte Languages

David MeegoFrom 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.

Languages such as French, Spanish and German etc. can use extended character such as ç è é ê Ö.

Languages such as Hebrew, Arabic, Thai and Vietnamese can use an entire extended alphabet, but they are all still single byte languages. A single byte language only needs an 8 bit value (0-255) to represent a character. Use of these character sets while handled by Dexterity is still not supported by Microsoft.

So what about Chinese, Japanese or Korean characters? These languages are double byte languages that require 16 bits (0-65535) to represent a single character.

Dexterity does not support double byte languages. This is mentioned in the Knowledge Base (KB) article Double Byte Languages (KB 864986) Secure Link. While the article says double byte is being evaluated, I doubt it will ever happen.  Microsoft has other Dynamics products which already support double byte, and adding support to Dynamics GP is not on the wish list.


Now that the official response has been given….

I have heard of Microsoft Dynamics GP being used in countries that are not supported.  They are not supported because Microsoft has not performed any localisation for that country and so many of the local taxation and legal requirements are not met without futher customisation by the partner or customer.  Usually these installs are based on the US English installation and are not translated.

However, I have also heard that double byte characters are being entered into the non-key string fields, such as descriptions, names and addresses. While Dexterity cannot truly handle double byte characters, it can work with some issues.  For example: delete or backspace must be pressed twice to remove both bytes of a double byte character.

Note: These systems using languages other than those released by Microsoft are running in an unsupported environment.  Microsoft support can only provide support for an issue if that issue can be replicated in a system that is in a supported environment.


Back in the days of version 6.00, a team in the Asia Pacific region started a "proof of concept" project to see whether it would be possible to have a Chinese version of Dynamics GP.  The project was stopped as there were too many issues with trying to use double byte languages when Dexterity was never designed to handle double byte.  The project was able to use the translation tool with a product called RichWin to create a Chinese interface.  Below is a screenshot of a translated window (can you guess which one? .. No cheating if you read Chinese.):

Chinese Window

Before you ask me where you can obtain a Chinese version of Microsoft Dynamics GP, this screenshot is all I have.  The project is long gone and no Chinese version exists. 

David

Posted: Monday, February 23, 2009 9:00 AM by David Musgrave

Comments

Jen said:

Chequebook Maintenance :) and no I cannot read Chinese!

# February 23, 2009 8:21 AM

Jivtesh said:

David, I love this series!

And that's the CHECKBOOK Maintenance Window :)

# February 23, 2009 8:24 AM

David Musgrave said:

Well Done, Jen and Jivtesh.

Jen wins by 3 minutes. :-)

David

# February 23, 2009 6:20 PM

David Musgrave said:

# February 23, 2009 10:56 PM

rushiparna said:

Hi David,

We have been able to convert the UI of Microsoft Dynamics GP 10.00 in multiple languages.

All these without any Dexterity Tool or even without touching the source code. All externally using our our unique ScriptMagic - zero code change L10N solution.

Please do feel free to write to me at rushi.rajendra@imgpoint.com

I can send to you the screen shots or even a copy for evaluation.

Look forward.

http://www.imgpoint.com/

# February 27, 2009 4:42 AM

Tim said:

We did something similar on version 8 using an add on to windows (a licensed product that i don't recall) where we simply modified forms and reports to use the language set.  it seemed to get us around the double byte thing.  SQL would also actually store and return the values in Chinese as well.  i believe we used the Big 8 character set.  we only modified certain objects so it wasn't a complete translation but it worked.  

# March 3, 2009 6:40 PM
Leave a Comment

(required) 

(required) 

(optional)

(required) 

  
Enter Code Here: Required

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Page view tracker