On Sun, Jun 27, 2004 at 06:11:38PM -0400, Joey Hess wrote:
> Alastair McKinstry wrote:
> > I suspect that the arabic shaping code is re-writing the strings and
> > using characters
> > that were not present in the original string. iso-scan saves space by
> > removing all
> > glyphs from unifont.bgf that were not present in the original string; if
> > the code
> > assumes all glyphs are present, it could crash ...
> iso-scan is part of the initrd, so its template strings participate in
> font reduction like those of any other udeb.
Yes, if the absence of glyphs can cause crashes, the most likely source
of trouble is that some sequence in the iso-scan main menu string is
shaped to a code point that's missing from
installer/build/needed-characters/ar. This *should* have been a
complete list of all characters generated by the shaping code, but it's
not impossible that I missed one.
On Sun, Jun 27, 2004 at 06:11:38PM -0400, Joey Hess wrote:
> Alastair McKinstry wrote:
> > I suspect that the arabic shaping code is re-writing the strings and
> > using characters
> > that were not present in the original string. iso-scan saves space by
> > removing all
> > glyphs from unifont.bgf that were not present in the original string; if
> > the code
> > assumes all glyphs are present, it could crash ...
> iso-scan is part of the initrd, so its template strings participate in
> font reduction like those of any other udeb.
Yes, if the absence of glyphs can cause crashes, the most likely source build/needed- characters/ ar. This *should* have been a
of trouble is that some sequence in the iso-scan main menu string is
shaped to a code point that's missing from
installer/
complete list of all characters generated by the shaping code, but it's
not impossible that I missed one.
--
Steve Langasek
postmodern programmer