Well, unless I've missed one, all exposed API calls that return Strings are first converted into "Max"-type Strings, rather than what was previously going on - which was that I simply did a String.fromCString(byte ptr) call - fine if the text is ASCII only.
In my current tests, the Max libxml mod is now happily converting text of 170+ languages and displaying them correctly in a ListBox. (on both Mac and Linux, with, I assume Win32 also, once I get my App working correctly there). ... and before anyone asks, you need to have all the correct fonts installed for most of these to work. For example, on Windows, I had to install a 7+meg chinese font to get that text displaying properly. (it seems to be pre-installed on my Mac and FC5 installations)
Also, any exposed API that takes a String as a parameter should now be converted from Max String to UTF-8 String - which is what libxml appears to expect.
I've successfully opened, edited, and saved XML in Max that contains all kinds of native language script.
Btw, if you find any missing API that you think important.. please let me know.
I was surprised I'd missed xmlGetLineNo()... ;-)
In my current tests, the Max libxml mod is now happily converting text of 170+ languages and displaying them correctly in a ListBox. (on both Mac and Linux, with, I assume Win32 also, once I get my App working correctly there). ... and before anyone asks, you need to have all the correct fonts installed for most of these to work. For example, on Windows, I had to install a 7+meg chinese font to get that text displaying properly. (it seems to be pre-installed on my Mac and FC5 installations)
Also, any exposed API that takes a String as a parameter should now be converted from Max String to UTF-8 String - which is what libxml appears to expect.
I've successfully opened, edited, and saved XML in Max that contains all kinds of native language script.
Btw, if you find any missing API that you think important.. please let me know.
I was surprised I'd missed xmlGetLineNo()... ;-)