Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: How Rockbox generates Unicode file name?

Re: How Rockbox generates Unicode file name?

From: Tat Tang <tat_tang_at_yahoo.com>
Date: Sun, 28 Mar 2004 06:47:33 -0800 (PST)

> No. We use the long name only. However, we strip
> the most significant 8 bits.

Err...not in my world ;)

> Simple. Our code only supports Latin-1, and
> expects the most significant
> byte to be 0x00. We have no real support
> for unicode.

So if I read this correctly, there is a mixture of
Unicode and non-Unicode filenames. A non-Unicode
filename is recognised when the most significant byte
is 0x00, hence the default clause in the unicode2iso
function.

Without this default clause, Rockbox would regard a
native character string as Unicode and try to convert
it to iso resulting in garbled filenames.

Luckily enough (or perhaps by design), Chinese
character sets never introduce 0x00 (or any Ascii
control character into the byte stream).

Tat..


__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html
_______________________________________________
http://cool.haxx.se/mailman/listinfo/rockbox
Received on 2004-03-28

Page was last modified "Sat May 23 08:12:40 2020" The Rockbox Crew