Hi Daf,

Today at 18:34, Dafydd Harries wrote:

> Is this problem only with Nimbus Mono? Perhaps you could provide a
> screenshot with a font that isn't broken for comparison purposes.

Yes, this is a problem only with Nimbus Mono, and only with Oblique,
Bold and Oblique Bold.  I've checked Debian gsfonts-8.14+v8.11-0.1,
and the problem exists there as well.

It's correct in Valek's fonts, as you can see here:

  http://kvota.net/fonts/urwcyr/nimbus-mono-side-by-side.png

Top fontforge view shows the font from your package, bottom is the one
from gnome.ru 1.0.7-pre39 tarball (I use this one only because I'm
lazy to download newer one, not because there's something wrong in
later releases).

So, this is entirely independent of the current bug, as Steve already
pointed out.  I think this is as bad as these missing/incorrect glyphs
(Russians would probably argue that it's even worse ;), but it is
nevertheless independent.

>> Also, Nimbus Sans Regular and Regular Condensed look exactly the same
>> for me (this could be due to some font fields not being set fully,
>> but I'm not sure).
>> 
>> Similarly, URW Bookman L Light gives me Demi Bold variant.  For URW
>> Gothic L, Book looks like Demi, and Demi Oblique looks like Book
>> Oblique.  Also, URW Palladio L Roman actually displays bold, just what
>> Century Schoolbook L Roman does as well.
>> 
>> All this is tested using gedit.
>
> It might conceivably be a problem with fonts being cached in some way.

This persisted after reboot and fc-cache -f.  fc-match[1] gives
correct file pointers:

$ fc-match "urw palladio l" 
URWPalladioL-Roma.pfb: "URW Palladio L" "Roman"
$ fc-match "urw palladio l:bold" 
URWPalladioL-Bold.pfb: "URW Palladio L" "Bold"

(These are links in /var/lib/defoma/... correctly pointing to
/usr/share/fonts/type1/gsfonts.)

[1] http://cvs.freedesktop.org/fontconfig/fontconfig/fc-match/
gcc -o fc-match `pkg-config --cflags --libs fontconfig` fc-match.c

> Could you see if you have these problems with the latest package in
> Debian? It would be useful to know whetehr these are regressions I've
> introduced or not.

No, it seems this is not your fault.  It happens just the same with
previous Debian package.  FWIW, this seems to be a problem with all
type1 and some truetype fonts generated with FontForge (of those that
I have, those are Computer Modern Unicode, your set of gsfonts,
Caslon*.ttf by George Williams).

Anyway, not related to this bug either.

Cheers,
Danilo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to