Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Nav 2016 stx file
Ekin
Member Posts: 28
Hello,
We are having problems with our stx file, we are translating the file. When I look at the stx files of 2013 r2 or 2009, I see that the file has been saved as ANSI and sealed by Microsoft.
We have the translation of stx file as 3 encoding types (msDos,Unicode,ANSI). ANSI fully translated but not the special characters. ANSI file have (s,i,o,g) instead of our special characters(ş,ı,ö,ğ). MSDos encoded file have "?" instead of our special characters. On the other hand, Unicode file have our special characters but I am not able import the stx file to Localization workbench.
When I import the stx file (msDos) to Localization Workbench, for example, a word "Açıklama" becomes "Aciklama" its not taking the special characters we use in our language. Same goes for Unicode. It corrupts the special characters "ı,ş" both goes to "?" character. However, I tried to change the encoding of correct file (Unicode to Ansi) then I checked the file, when i open it it seems correct but when i import it to the Localization Workbench, all special characters still changes to "?" character. Also, when I import the old fin.stx file (2013r2 - 2009) to Localization Workbench, I see that special characters are okay. Is there any other way for correctly importing the stx file to Localization Workbench without corrupting the characters?
We are having problems with our stx file, we are translating the file. When I look at the stx files of 2013 r2 or 2009, I see that the file has been saved as ANSI and sealed by Microsoft.
We have the translation of stx file as 3 encoding types (msDos,Unicode,ANSI). ANSI fully translated but not the special characters. ANSI file have (s,i,o,g) instead of our special characters(ş,ı,ö,ğ). MSDos encoded file have "?" instead of our special characters. On the other hand, Unicode file have our special characters but I am not able import the stx file to Localization workbench.
When I import the stx file (msDos) to Localization Workbench, for example, a word "Açıklama" becomes "Aciklama" its not taking the special characters we use in our language. Same goes for Unicode. It corrupts the special characters "ı,ş" both goes to "?" character. However, I tried to change the encoding of correct file (Unicode to Ansi) then I checked the file, when i open it it seems correct but when i import it to the Localization Workbench, all special characters still changes to "?" character. Also, when I import the old fin.stx file (2013r2 - 2009) to Localization Workbench, I see that special characters are okay. Is there any other way for correctly importing the stx file to Localization Workbench without corrupting the characters?
0
Answers