registry team mailing list archive

[Bug Watch Updater <268812@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 12 comments from the remote bug at
http://bugs.freedesktop.org/show_bug.cgi?id=17493.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-09-08T18:58:34+00:00 Ryan Lortie wrote:

1) take the attached .fo file
2) run it through apache fop to get the attached .pdf file
3) open it in evince, kpdf and xpdf to get the attached .png file
4) note that xpdf is the expected result and the one that agrees with acrobat reader

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/0

------------------------------------------------------------------------
On 2008-09-08T18:59:03+00:00 Ryan Lortie wrote:

Created an attachment (id=18764)
fo file

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/1

------------------------------------------------------------------------
On 2008-09-08T18:59:49+00:00 Ryan Lortie wrote:

Created an attachment (id=18765)
pdf file

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/2

------------------------------------------------------------------------
On 2008-09-08T19:00:10+00:00 Ryan Lortie wrote:

Created an attachment (id=18766)
png file

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/3

------------------------------------------------------------------------
On 2008-09-10T13:34:29+00:00 Tsdgeos wrote:

I've no idea of which poppler version you are using, but anyways, this
is not a bug.

The PDF has Courier NOT embedded in the file, so when rendering we have
to ask the system for a font named Courier and draw what it gives us.

We are using Fontconfig for that and using poppler 0.9.0 i get the
"correct" answer (n022003l.pfb), so if it does not for you, either
update your poppler or fix your fontconfig to give the correct font when
asking for Courier.

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/4

------------------------------------------------------------------------
On 2008-09-10T19:19:44+00:00 Ryan Lortie wrote:

Some more information I managed to dig up (this seems to be the source
of the problem):

desrt@moonpix:~$ fc-match Courier
n022003l.pfb: "Nimbus Mono L" "Regular"
desrt@moonpix:~$ fc-match Courier:spacing=0
n022024l.pfb: "Nimbus Mono L" "Bold Oblique"

Behdad says he can reproduce this so I'm reopening and reassigning.

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/5

------------------------------------------------------------------------
On 2008-12-28T02:25:22+00:00 Freedesktop wrote:

For some reason the Nimbus Mono L Bold Oblique is not getting any
spacing value detected for it, and that happens to better match 0 than
the spacing=100 in the rest of them.  Investigating.

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/10

------------------------------------------------------------------------
On 2008-12-28T02:29:03+00:00 Freedesktop wrote:

In fact the question is why does fontconfig detect spacing=100 (FC_MONO)
for the three of them.

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/11

------------------------------------------------------------------------
On 2008-12-28T02:32:09+00:00 Freedesktop wrote:

Sorry.  It's Mono after all, so detecting spacing=100 is correct.  It
fails for Bold Oblique version though.

Another question I guess is, why does poppler request for spacing=0
instead of leaving that pattern field empty?

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/12

------------------------------------------------------------------------
On 2008-12-28T02:50:42+00:00 Freedesktop wrote:

Glyph 227 of Nimbus Mono L Bold Oblique has a width much wider than the
rest of the glyphs in the font (740 vs 600), so the font is detected as
having proportional spacing, not mono spacing.

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/13

------------------------------------------------------------------------
On 2008-12-28T03:01:24+00:00 Freedesktop wrote:

No idea if there's any upstream for urw-fonts.  Reported to Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=478332

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/14

------------------------------------------------------------------------
On 2008-12-28T03:07:32+00:00 Freedesktop wrote:

Actually this was fixed in poppler earlier this year.  Poppler now
doesn't set spacing unless it wants to ask for mono.  Dupping.

*** This bug has been marked as a duplicate of bug 14883 ***

Reply at: https://bugs.launchpad.net/fontconfig/+bug/268812/comments/15


** Changed in: fontconfig
       Status: Invalid => Unknown

** Changed in: fontconfig
   Importance: Unknown => Medium

** Bug watch added: Red Hat Bugzilla #478332
   https://bugzilla.redhat.com/show_bug.cgi?id=478332

-- 
fc-match Courier:spacing=0 ⇒ n022024l.pfb: "Nimbus Mono L" "Bold Oblique"
https://bugs.launchpad.net/bugs/268812
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Fontconfig.