Navision Localization Workbench

Comments

• Cem_Karaer Member Posts: 281

  2007-03-28

  Help, help, help...! ](*,)

  Cem Karaer @ Pargesoft
  Dynamics NAV Developer since 2005

  0
• Cem_Karaer Member Posts: 281

  2007-03-29

  OK, I see that nobody is interested in NLW. Here is another question . I saw in a forum that Navision .stx files can only be edited by MS because a checksum is added to it. Is it true?

  Cem Karaer @ Pargesoft
  Dynamics NAV Developer since 2005

  0
• DenSter Member Posts: 8,307

  2007-03-29

  It's not that we're not interested, I just don't think many people know much about it. I've had some questions about it myself a while ago and nobody could help me either....

  Daniel Rimmelzwaan
  RIS Plus, LLC

  0
• ayhan06 Member Posts: 210

  2007-03-29

  i think you'd better use translation file (.txt file) that is exported from nav. nlw works well with .txt files. i have never used .stx files but i know that .txt translation files are simple and there is no file sum-check while importing into NAV.
  
  you asked if there is another localization software...in the partnersource, search for "localizaton studio" or "locstudio".. there will be an email address for partner to request that software.also local MS Dynamics team will help you obtain this software because they have it as well (if i am not wrong)..

  0
• andrejsm Member Posts: 122

  2007-03-30

  NLW are used to translate txt files. But we translate addon's and some functionality parts, but not whole NAV, usually.
  If I understand correctly, cemkaraer wants to localize :shock: all NAV.
  There are number of words like properties names, dates e.c. in the STX file. We can open STX in notepad, and translate resources. But NAV calculate Checksum and that's why only Microsoft can translate STX file.

  Andrejs Muraskins

  0
• Cem_Karaer Member Posts: 281

  2007-04-03

  The real problem is the following:
  1. We copied .stx and .etx files of 3.70 TR into the client folder of 3.60 W1 in order to make our customer work in a pseudo-localized version of 3.60 (objects are already translated, that is to say, NAV objects have their own Captions in Turkish).
  
  2. Eveything works all-right until our customer changes the language from English to Turkish and restarts in SQL option. The error is below
  

  ---

  Microsoft Business Solutions-Navision

  ---

  Metin dönüşümünde hata oluştu (93-331 numaralı metin .stx dosyasında mevcut değil).
  
  İç hata: 47-1
  

  ---

  OK

  ---

  
  Unfortunately the error is also Turkish because the current language of NAV is Turkish.
  
  3. We used NLW to create a new .stx with no success because the .stx file created the NLW yields a checksum error.
  
  4. I finally concluded that the real problem is trying to change something I should NOT try to.
  
  If my conclusions are true, I will not insist to solve it using NLW.

  Cem Karaer @ Pargesoft
  Dynamics NAV Developer since 2005

  0
• gupi Member Posts: 3

  2007-05-07

  Why you can not upgrade the NAV client to 3.70. Than you can use the standard .stx file for Turkey from this release.
  
  You wrote that you have Turkish ML-captions in your 3.60 database. Otherwise you could import the .flm file from 3.70.
  BUT you should check these standard translations with the NLW tool.
  Especially (the number of) option values and page names.
  This can be done by the NLW report "Warnings".
  
  Our experience with NLW is different. It's a very helpful tool to translate the individual part of a project into a new language. But we only worked with creating a ".txt export" from NLW and "Translate - Import" into NAV and in reverse order.
  We never created a .stx file - and I think it's not possible as you noticed by yourself.

  0