NAV 2013 R2 new language translation

Konrad_SECKonrad_SEC Member Posts: 10
edited 2015-09-22 in NAV Three Tier
Hi,
I have a concern regarding adding a new language translation to the RTC. I haven't found The Microsoft whitepapers regarding NAV 2013. The only available RTC translation whitepapers regard NAV 2009 but the same rules seem to apply for later versions as well.

So – one the key files of interest is “Microsoft.Dynamics.Nav.Language.resources.dll” located in “…Microsoft Dynamics NAV\71\RoleTailored Client\xx-Xx” folder (where xx-Xx stands for the particular language). According the Microsoft whitepapers this file should be translated and its public key token registered in Table 2000000069 - Client Add-in. That’s fine and so far works. However the problem is that such a translation doesn’t actually translate everything. Some parts of the RTC remain not translated. The example is “Home” item on starting page of the RoleCenter. Despite the above DLL library contains the “Home” item translation, the RTC keeps displaying the English description of “Home” item. I investigated the issue and found the reason is because the “Home” item translation comes from the other file (of the same name) “Microsoft.Dynamics.Nav.Language.resources.dll” located in server location “…\Microsoft Dynamics NAV\71\Service\xx-Xx folder”.
Both “Microsoft.Dynamics.Nav.Language.resources.dll” files have similar structure and both have “Home” item translation however RTC client keeps taking translation not from “RTC” location but from “Server” location. It wouldn’t be any problem to make translation of the “server” file but according Microsoft Whitepapers translation is only possible to RTC DLL files.
I have made also the following test to reassure my concept is correct. I used two language modules provided by Microsoft – French and German. I installed them both. Then I copied the entire content of the French “…Microsoft Dynamics NAV\71\Service\ fr-FR” into the “…Microsoft Dynamics NAV\71\Service\de-DE” folder. All to be sure I use the official Microsoft sealed files and to make sure the languages I use are different. The result is following – part of the RTC is in German, part in French, eg. “Home” item – French (server located DLL file),

The main menu bar is in French (RTC DLL file)

but when we select language change …

then we get German dialog window (RTC DLL file)
Of course we could translate the Server DLL file however according Microsoft white papers we must not attempt to translate.dll files as these files are digitally signed by Microsoft and any attempt to modify these files could cause the software to stop working. I tested if that is correct. I reassembled and assembled the server located DLL file and signed with a new strong name and it is true. The system doesn’t want to read the DLL server located library having different public key than 31bf3856ad364e35.
Does anyone have the idea how to fix the above and it is really true the server located DLL file cannot be some other way translated into the destined language?

Comments

  • danielleedaniellee Member Posts: 6
    You may find the details about the translation of NAV 2013 in the file "NAV2013 Readiness - Whitepaper - PLLP Translations.docx". It can be find in partner source as a part of PartnerTranslationsKit.
    In topic "DEPLOY - CREATE AND DEPLOY SATELLITE ASSEMBLIES", you may find that the change of "Microsoft.Dynamics.Nav.Language.dll" (Microsoft.Dynamics.Nav.Language.resource.dll) is required for 3 kinds of client.
  • Konrad_SECKonrad_SEC Member Posts: 10
    Thanks a lot. My problem seems to be solved and the reason for that was that I couldn't find the proper Whitepapers.
    For all who might be interested - the Whitepapers and the translation toolkit for NAV 7.0 works fine. The translation tool creates msi installers. All DLL libraries have been created by the translation toolkit (including Server DLL library). All you need is to register RTC DLL public token key so as RTC can read it. Server DLL library works fine despite it is signed by different key than Microsofts' original one but it is still signed by the keygen included within the translation tool. But I am not sure if the DLL library signature matters. Perhaps my problem was not a key but structure - somehow destroyed during testing (instead of using translation tools).
  • dmc-dkdmc-dk Member Posts: 42
    By the way, there is a new PLLP toolkit for NAV 2013 R2 available for download from the Partner Source:

    https://mbs.microsoft.com/partnersource/support/selfsupport/productreleases/msdnav2013r2downloadpage.htm

    Best regards,
    DMC
  • mircenmircen Member Posts: 8
    Hello Konrad,
    im very new in navision and i work like a sysadmin so please if you can help me

    i have the same problem now, the problem appear after i instaled the new hotfix Build 38655 for nav2009r2, before that the translation worked, now the translation appear less than a second and then convert to english,

    The situation is the same like your posted picture, home and departments are not translated

    i wrote about this on http://dynamicsuser.net/forums/p/85928/469459.aspx

    there is a video with the problem

    You mention about register the public token for the dll file, can you tell me how can i do it,
    I dont use the translation toolkit we translation manualy

    Thanks in advance
Sign In or Register to comment.