Help with the Navision Localization Workbench tool

mshubaly
Member Posts: 7
I have a few questions! :oops:
I have currently been asked to help with the translation of our application from English to Spanish and I have never used the Navision Localization Workbench (NLW) before this...
My role is to get to the Spanish Translators exactly what they need in order to effectively translate our field names, Caption MLs, etc. and they will also be using the NLW tool although do not have experience with it either.
This is the situation:
We already had an earlier version of our application translated into Spanish so I exported it out into a .flm file and imported that into our current version.
1) I set the [Tools->Language] to Spanish(Tradtional Sort)
2) Then I exported [Object Designer->Tools->Translate->Export->.txt file] from our application in MBS-Navision for each object type (IE: all the tables were in one export)
3) I opened up the NLW tool and created a separate project for each type of object and imported the text file once the project was created.
4) I then [File->Import->Translated File] and selected the same text file so it would register the already translated fields and caption MLs, etc.
So now I have projects with both 'Translated' and 'Not Translated' Status Texts.
I don't know if this is the correct way to use the NLW.
Do I export the original text file from the application as a Spanish FLM file? or should it be an English FLM file?
basically I need to translate the delta between the older version and the newer version.
does anyone have any advice?
documentation?
process in place for using the NLW successfully?
Thanks,
Meg
I have currently been asked to help with the translation of our application from English to Spanish and I have never used the Navision Localization Workbench (NLW) before this...
My role is to get to the Spanish Translators exactly what they need in order to effectively translate our field names, Caption MLs, etc. and they will also be using the NLW tool although do not have experience with it either.
This is the situation:
We already had an earlier version of our application translated into Spanish so I exported it out into a .flm file and imported that into our current version.
1) I set the [Tools->Language] to Spanish(Tradtional Sort)
2) Then I exported [Object Designer->Tools->Translate->Export->.txt file] from our application in MBS-Navision for each object type (IE: all the tables were in one export)
3) I opened up the NLW tool and created a separate project for each type of object and imported the text file once the project was created.
4) I then [File->Import->Translated File] and selected the same text file so it would register the already translated fields and caption MLs, etc.
So now I have projects with both 'Translated' and 'Not Translated' Status Texts.
I don't know if this is the correct way to use the NLW.
Do I export the original text file from the application as a Spanish FLM file? or should it be an English FLM file?
basically I need to translate the delta between the older version and the newer version.
does anyone have any advice?
documentation?
process in place for using the NLW successfully?
Thanks,
Meg
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions