From: "Daniel C. Sobral" <d...@newsguy.com> Subject: Re: kern/5038: FreeBSD can't read MS Joliet CDs. Date: Thu, 15 Apr 1999 02:40:58 +0900
dcs> > 2. Only Page 00 Unicode is shown (for Joliet CDs). dcs> ... dcs> > Note. dcs> > Byung's patch passes Unicode transparently. dcs> > So CJK filenames are shown if terminals do Unicodes well. dcs> dcs> Do you mean that your patch shows only page 00, but Byung's patch dcs> passes Unicode directly? My patch: * character in page 00 is converted to ASCII(+ISO-8859-1) * character in other pages is replaced by '?' Byung's patch: * character in page 00 is converted to ASCII(+ISO-8859-1) * character in other pages is passed as is For example, suppose to be a file on Joliet CD, which filename is encoded as [ 0041 0042 0043 2525 3030 3535 ] in Unicode. The kernel applied my patch shows it to userland via readdir(2) as (41)(42)(43)(3F)(3F)(3F) ... "abc???" The kernel applied Byung's patch shows it as (41)(42)(43)(25)(25)(30)(30)(35)(35) ... "abc%%0055" Byung reported, > With this patch, I was able to see long file names and > non-english characters(such as korean&chinese) so i believe it > does support unicode as long as your locale is set correctly. But with my locale 'ja_JP.EUC' (which is the major in Japan on *BSD box), these strings make no sense. To see filenames which contain Japanese characters, kernel should convert it to EUC(JP). Another possible answer is encoding to UTF-8, however, I don't know UTF-8 terminal compliant with Japanese. -- Motomichi Matsuzaki <mz...@e-mail.ne.jp> Dept. of Biological Science, Fuculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
