Uniencode fails on some chars
rbarber at yhb.att.ne.jp
Tue Apr 29 08:05:01 EDT 2003
You are right about these characters. I used the moji palette to get the
codes that I reported. I guess the problem I see is that uniencode just
stops at that point rather than skipping it and moving on. Maybe my hope
that it would at least ignore it and continue is unrealistic.
BTW did you ever get a response to the difference between SJIS utf-8, and
> I think these are only Windows special characters.
> We cannot show many of special characters by using Unicode.
> Open MOJI palette of Kotoeri (form Kotoeri menu)
> and see SJIS 8640. There are no characters of unicode, even SJIS.
> You can show SJIS 8642 by HIRAGINO font, but not in Osaka.
> This page may help too.
> Kenji Kojima
> On 2003.Apr.29, at 12:30 AM, Ron wrote:
>> Just for the record in case this trips up someone else. I ran into a
>> with converting some files with uniencode. Once I read in the text I
>> set the unicodetext of fld 1 to uniencode(thetext,Japanese)
>> The conversion works fine except for some unusual chars. The chars
>> that my
>> text used were the 'mm' and 'cm' as single chars. The data was
>> prepared on a Windows machine so these special chars do not map
>> correctly to
>> Osaka but will show up with a font like 'ChyuGothicTai'. (this latter
>> problem is not RR, but mac/win)
>> JIS code: 2B21 and 2B23
>> SJIS : 8640 and 8642
>> UTF8: 339C and 339D
>> I imagine that whole set of chars will give problems.
>> The problem is that uniencode stops encoding at that char and does not
>> return the remaining data.
>> OS 9.2.2 RR 2.0 b2
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the use-livecode