Jump to content

SPBytes

Members
  • Content Count

    5
  • Joined

  • Last visited

  • Days Won

    1

SPBytes last won the day on March 9

SPBytes had the most liked content!

Community Reputation

4 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This is a separate issue. The file passing as "UTF-8 without signature" gets recognized as ASCII but still works for Chinese and Russian, not for Arabic.
  2. One thing I didn't notice before, the library will only accept UTF-8 without signature. When a file is ran through with this encoding the file is accepted as an ASCII string through 'readUnicodeFileJKI_Simple_Localization.vi'. This works for Chinese and Russian, not for Arabic. If I try any other form of Unicode file encoding on the json file, the file will go through 'unicodeStringtoASCIIJKI_Simple_Localization.vi' that uses the WideCharToMultiByte function. It will however fail at 'JKI JSON Serilization.lvlib:Unflatten From String.vi'
  3. As an update, I have been applying the file directly to the unicodeStringtoASCIIJKI_Simple_Localization.vi. Arabic gets translated to ASCII correctly as shown in the screenshots. Maybe a kernel32.dll function needs to be updated. Hopefully I find something and I will post it on this thread.
  4. I have had success with Chinese and Russian. I am applying the same method for Arabic that is outlined in the documentation that you linked. The Windows locale setting for Chinese(Simplified) works for both Russian and Chinese. When I apply any Arabic setting I get the screenshot above. I have tried different Unicode file encoding methods and applied them directly to the Read Unicode File vi but always got the same strings for Arabic. I attached my vi and json file. Dictionary.JSON Language Selection.vi
  5. Is there a way to make this tool compatible with Arabic?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.