Indeed.
In terms of an Add-On: The changed objects should be merged into the localised version of NAV, to be able to use that Add-On in a certain country. When merged, the Add-On also takes in count the law-restrictions of that country.
And off course translation of the objects is necessary. There is a toolkit for this.
marginal comment:
There is also something like the "localisation workbench" ... but no support from Microsoft whatsoever ... and afaik ... nobody knows how it works.
Well, for Navision, to me, the localization work usually contains two parts. Shell localization and objects localization and both of them can be done by Navision Localization Workbench.
For Shell localization you can always achieve that by translating the fin.etx which cantains the shell error message and tools menu with NWL. And also the fin.stx which I don't know what it is used for but we can enable DBCS in this one.
For objects localization all you have to do is exporting the Caption ML file into txt file and use Navision Localization Workbench to translate them.
Well, for Navision, to me, the localization work usually contains two parts. Shell localization and objects localization and both of them can be done by Navision Localization Workbench.
For Shell localization you can always achieve that by translating the fin.etx which cantains the shell error message and tools menu with NWL. And also the fin.stx which I don't know what it is used for but we can enable DBCS in this one.
For objects localization all you have to do is exporting the Caption ML file into txt file and use Navision Localization Workbench to translate them.
And (I think) you forgot the part to merge the objects into the standard, localised version of NAV.
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
In terms of an Add-On: The changed objects should be merged into the localised version of NAV, to be able to use that Add-On in a certain country. When merged, the Add-On also takes in count the law-restrictions of that country.
And off course translation of the objects is necessary. There is a toolkit for this.
marginal comment:
There is also something like the "localisation workbench" ... but no support from Microsoft whatsoever ... and afaik ... nobody knows how it works.
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
For Shell localization you can always achieve that by translating the fin.etx which cantains the shell error message and tools menu with NWL. And also the fin.stx which I don't know what it is used for but we can enable DBCS in this one.
For objects localization all you have to do is exporting the Caption ML file into txt file and use Navision Localization Workbench to translate them.
MCP - MBS Navision
jle@naviworld.com
And (I think) you forgot the part to merge the objects into the standard, localised version of NAV.
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
both
https://mbs.microsoft.com/partnersource/worldwide/belux/downloads/releases/
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog