Comments on Jigtenmig - Classical Tibetan Language Blog: Issues with ACIP to Unicode Conversion and MacOSX

I found the same thing as you when using Jskad.jar...

2008-05-12T20:47:00.000-07:00

I found the same thing as you when using Jskad.jar, but I did manage to get readable unicode from a ACIP file in a two step process.

First go to:
Tools→Launch Converter...→ACIP to Wylie (Text->Text)→Convert

Second:
Close the converter dialogue and open the text file that was produced by the converter and select all and copy then paste into Jskad.

Third:
Select all in Jskad, then:
Tools→Convert All→Convert Tibetan Machine Web (non-Unicode) to Unicode.

Fourth:
Select All→Copy and paste into a text file. Save the file (make sure that the encoding is UTF) and you have a Unicode file.

It's a little clumsy, but not too bad, I think.

*Except that the Unicode stackings are far from perfect - at least in Windows. I still haven't tried with Linux. (I left a message about this at http://jigtenmig.blogspot.com/2008/03/tibetan-unicode-fonts-and-this-blog.html)

Thanks. I tried both the tested version of Jskad a...

2008-03-28T14:32:00.000-07:00

Thanks. I tried both the tested version of Jskad as well as last night's build. I suspect that the file header needs some specific information that this is a unicode 16 or UTF-8 file, but I'm no expert on Unicode files.

Maybe someone from the Jskad team is reading this...

Uh-oh, I just tested to see for myself and got the...

2008-03-28T13:57:00.000-07:00

Uh-oh, I just tested to see for myself and got the same gibberish. ACIP>Unicode used to work fine. It doesn't seem like Leopard would have messed up a good thing, but I don't know what else has changed since then. I tried numerous different plain text encodings via TextEdit, but the all had different problems when converted.

That's really a shame. I was banking on ACIP>Uni on a Mac. I'll keep searching for a solution.