[tex-k] [tex-live] xdvi problems with empty glyph

[Paul Vojta]

On Tue, Oct 10, 2006 at 07:44:45AM +0200, Werner LEMBERG wrote:
> 
> > >   xdvi-xaw.bin: Warning: Character 0 is mapped to .notdef
> > >                 in font gbsnu30 (page 1), replacing by whitespace.
> > 
> > > Glyph 0 in virtual font gbsnlp01 maps to glyph 0 in real font gbsnu30.
> > > This is indeed an empty glyph which is identical to `.notdef';
> > 
> > I couldn't reproduce this problem (I dont' have TeXLive available and
> > tried to install the CJK package manually but failed)
> 
> Ok, attached is a small tar bundle `xdvi-problem' (I've stripped the
> font gbsnu30 to the bare minimum of holding just two glyphs, `.notdef'
> and `uni3000').  Just do
> 
>   TEXMF=path/to/xdvi-problem/texmf xdvi xdvi-problem.dvi
> 
> and you should get the incorrect warning message.
> 
> > - I didn't quite understand this part of your report:
> > 
> > > however, it is called `uni3000' (using the built-in encoding vector).
> > > Somehow the mapping is screwed up.
> 
> Well, xdvi is talking about the .notdef glyph, but this glyph isn't
> referenced at all -- glyph uni3000 exists in the font!
> 
> > Or is this a whitespace character that is erroneously reported as
> > .notdef?
> 
> Yep.


I don't know about xdvi's use of t1lib (that is specific to xdvik, not
plain xdvi), but I've been playing with adding freetype2 support to xdvi,
and I also get an error with freetype2.  What happens is it returns error
code 6 (invalid argument) when I call FT_Load_Glyph() for the character.

So, I think it's either the font or t1lib/freetype2.

--Paul Vojta, vojta at math.berkeley.edu