Rockbox mail archiveSubject: Re: Extended charsets
Re: Extended charsets
From: Greg Haerr <greg_at_censoft.com>
Date: Tue, 25 Jun 2002 09:25:28 -0700
> All Unicode
> strings use 16-bit unicode 2.0 (ISO/IEC 10646-1:1993, UCS-2). Unicode
> must begin with the Unicode BOM ($FF FE or $FE FF) to identify the byte
OK. This means that the ID3 strings if found in Unicode will
need to be converted to UTF-8. (Of course, this will be useless
unless a Unicode font is also loaded).
> > 2. Support converting any freely-available BDF font (from any X
> > distribution) for use in rockbox.
> That sounds awfully cool! I'm not sure exactly how useful that is though,
> most of those fonts will be too big... ;-)
Most fonts are quite small, since the internal representation is
basically a monochrome bitmap. For the larger fonts,
such as chinese, this could be a problem, but we might be
able to use sparse arrays for the unicode char indices. Of course,
this is if anyone cares...
> Such symbols are already used now, but they are not part of any charset.
> can use simple bitmaps/icons.
Great, I didn't realize this.
> > There is some issue with regards to character height, however.
> You mean in your code or in the current code? Currently we only support 16
> pixels high charsets (and incidently, that's the largest font we have
> really can't see the need for much larger fonts either...
In the current code, we might want to support font heights that are
different than 16. Certainly the new font drawing code won't have
a problem with this. This would allow a larger/smaller font for those
might want it. The UI code should automatically adjust based on the
loaded font height.
Received on 2002-06-25