[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#171344: xdvi sometimes uses wrong-size bitmaps



I have observed this phenomenon as well. Some experimenting shows me
that it is probably not T1 encoding that triggers the bug, but the
use of scaleable PostScript fonts. This LaTeX source produces a .dvi
that exhibits the problem:

\documentclass{article}
\usepackage{charter}
\begin{document}
\shipout\hbox{\textsc{aA}}
\end{document}

The DVI file is

begin 644 foo.dvi
M]P(!@Y+`'#L``````^@;(%1E6"!O=71P=70@,C`P,RXP-2XR-#HR,S`XBP``
M``$```````````````````````````````````````````````#_____GP;8
M3/,/`P9CC``*````"@````=B8VAR8S=TNF%!C/@````J`8.2P!P[``````/H
M``;83``,?_@````!\P\#!F.,``H````*````!V)C:')C-W3Y````=@+?W]_?
`
end

which should be small enough to throw at a debugger.

More data: The problem is not restricted to small caps. It surfaced
for me in a document where xdvi insists on rendering \footnotesize
text with \normalsize bitmaps (but still the correct \footnotesize
spacing). In that case the problem disappears when I run the dvi file
though dviselect '*', which renumbers the font table but is otherwise
a no-op. This indicates that the problem is not tied to virtual fonts.

I use tetex-bin version 1.0.7+20011202-8

-- 
Henning Makholm       "`Update' isn't a bad word; in the right setting it is
                 useful. In the wrong setting, though, it is destructive..."



Reply to: