Chinese Language Pack for Dynamics NAV (Navision)

Overview
Recently, we started a branch in Taiwan. One of the reasons, amongst other reasons, I started this branch is because it’s country where I was born. So in a way, I feel a little obligated to help the companies in my home country to be more efficient and enjoy the benefits in what Dynamics NAV has to offer.

There are many lessons learned in terms of starting a company in a different country; the local culture and views on technology, how to speak and appeal to the local management, etc. I’m sure I’ll blog about in a future article. For now, I want to share with you guys the many challenges when doing translation in Dynamics NAV (Navision).

One of the Technical Challenges
When selling into a local market, one of the things that is mandatory is whether you have the local language pack. As you know, Dynamics NAV is a software that’s utilized all over the world. Microsoft also supports languages for many countries out of the box.

Unfortunately, the Chinese language pack is not one of them. This means we had to create our own.

The Process
The process involves creating caption for all the fields, errors, messages, reports, etc.

There are 3 main parts for creating translations that works in Dynamics NAV.
1. Translate the platform by translating the resource file for each DLL file.
2. Translate all the captions by adding a new language into captionML in each object
3. Localize development environment by translating .stx and .etx files. These 2 files have to be sent to the Microsoft regional office and sealed by Microsoft. (Only required if you want the Development Environment to be in Chinese as well)

Fortunately, Microsoft provides tools that allow you to make your own localization. In our case, we did this for the Chinese language. The step by step instruction on how to do this is explained here. Basically download the PLLP (Partner Localization and Translation Licensing Program) and follow the instructions very carefully:
http://blogs.msdn.com/b/nav/archive/2013/11/15/microsoft-dynamics-nav-2013-r2-pllp-toolkit-released.aspx

You will spend most efforts on translate all the captions. However, this part can be accelerated a little bit by exporting all the captions in txt file. Once you translate all the exported captions with A1033 code (English label) to the corresponding language code (e.g. A1028 represents Chinese Traditional), import the txt file back to NAV. Then it’s done!

Introducing the Chinese Language Pack for Dynamics NAV 2013 R2
As you will see, we did this for Traditional Chinese, but the nice thing about this is that it can be easily translated to Simplified Chinese.

Here are the results:

Chinese Dynamics NAV Selection

Chinese Dynamics NAV Selection

Chinese Dynamics NAV Role Center

Chinese Dynamics NAV Role Center

Chinese Dynamics NAV Departments

Chinese Dynamics NAV Departments

Chinese Dynamics NAV Customer Card

Chinese Dynamics NAV Customer Card

 

Leave a comment ?

19 Comments.

  1. Good Job Alex Chow and good luck for your new job.

  2. Well, I still have my current job. I would say this is additional responsibility that’s quite exciting for me.

  3. That was quite a massive job — to translate all the captions…
    am impressed to see the screens in Chinese. *thumbs up*

  4. HI Alex,
    Are you selling the Chinese traditional language pack for Dynamics NAV 2013 R2?

    I have a client interested in this

    thank-you
    Raymond

  5. Hi Alex,

    We have a customer in Vancouver that requires the Chinese translation. Would you be interested in reselling the language pack?

  6. Hi Alex,

    Nice blog, well said.

    I tried to translate NAV2013 R2 to Chinese using the translation toolkit but some words are still in English. I tried to export the object and replace the ENU to ZHH but when I import it goes back to ENU in the CaptionML property. Do I need to change the regional setting for this? thanks you

  7. Hi Alex,

    I don’t suppose you’ve also done this of NAV 2015? I have a customer who may also be considering this as an option…

    Thanks,

    Paul

  8. Yep, it’s available.

  9. Giancarlo Zavala

    Hi Alex, how would this work for report printouts?
    We have an implementation that requires certain warehouse and purchase printouts to be displayed in Chinese.
    Would this be possible using captionML in NAV 2015?

  10. Yes, the contents on the report comes from the Caption ML property. However, you have to specify the language as Chinese first.

    If this is a one off thing, it may be easier to just put the translation into the report.

  11. Is the language pack also available for NAV2009 R2?

    We have issues processing xml imports containing Chinese characters using the NAS.

  12. Unfortunately, it’s only available from NAV2013 forward.

    Regarding the issue with XML import with Chinese character, you may have to contact your solution center on this. We have no problems importing XML or txt files with Chinese characters.

  13. Hi Alex,

    Is it possible to load the Chinese language pack in an AU database?

  14. Yes, you can load it in any localized database. However, the localized content won’t have the translated language.

  15. Hi Alex,

    I’m wondering why you preferred your own development rather than purchasing almost official LP from Tectura Taiwan.

    Thanks.

  16. We tried. But they refuse to sell to partners. Basically, if you want this language pack, you needed to be their customer of record. I believe this blocks any new partners that may want to help out businesses in the Chinese market. By making this available, I’m hoping that more customers and partners will want to enter the Chinese market so NAV can be a dominate force in Asia as well.

    I’m not a fan of a business model where you keep the customer hostage. Everyone loses in this situation.

  17. Thank you Alex. I did not know they sell to the customers only. Appreciate your sharing.

    I agree – it’s far from ideal.

Leave a Comment


NOTE - You can use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>