Alternate fonts can look bad

Bug #165872 reported by Bug Importer
0
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Low
bbyak

Bug Description

I have a "professional" PostScript font (Poetica) that has
alternate ampersands as well as other subtypes of fonts.
However, fontconfig lists them as having the same name, but
different "Styles." Now Inkscape is the only X application that
handles this even remotely right (I assume due to the work
against bug #904962), so the list of styles shows up correctly.
However, the width of the fonts is really messed up. I've
attached a screenshot so you can see the difference. I would
have added this report to #904962, but I couldn't figure out how
to attach a file to an old report.

The upper text is chosen as PoeticaAnd with style Supp
Ampersands (which I added to a fonts.cache-1 in my fonts
folder by hand, a trick I need for every other program). This
looks right.

The lower text is chosen as Poetica with Supp Ampersands.
You can see that it is suboptimally rendered. :)

Two other points:
  The "Roman Small Capitals" style works as expected.
  The "Chancery I" style is not displayed (so I added the
PoeticaR name), Instead the mangled "Supp Ampersands" is
displayed.

I'm not sure if the first one works because it's the first one, or
maybe because the name has "Roman" in it. I haven't tried
installing the Regular font.

Also, I get the same behavior when I disable my fonts-cache
hack, so it's not that.

Plus, I would like to say that I think that inkscape is an
incredible program. Once these font issues are sorted out, I'm
going to point to the way it's done here as "the" way to do it. It's
definately the closest!

Tags: fonts
Revision history for this message
Bug Importer (bug-importer) wrote :
Revision history for this message
Bug Importer (bug-importer) wrote :

I forgot to mention the version. I'm using 0.39.

Revision history for this message
Bug Importer (bug-importer) wrote :

Thanks for the report. I think we did all we could for
proper Pango rendering, so I suspect the reason for the
remaining problems is the limitations of CSS which cannot
handle fancy styles (its repertoire of styles is very
limited). I have a plan to augment CSS in Inkscape with our
own custom property that would store the true name of the
style, for precise matching of arbitrary fonts. I hope to
get to it somewhere in the 0.40 cycle.

Revision history for this message
Ryan Lerch (ryanlerch) wrote :

Thank you for taking the time to report this bug and helping to make Inkscape better. You reported this bug a long while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Inkscape release? Thanks in advance.

Changed in inkscape:
status: New → Incomplete
Ryan Lerch (ryanlerch)
Changed in inkscape:
assignee: buliabyak-users → buliabyak
Revision history for this message
imigital (imigital) wrote :

STATUS CHANGED: from Incomplete to Invalid

CLOSED as out of date.
Bug Triage: older than 1 month with no reply

Changed in inkscape:
status: Incomplete → Invalid
su_v (suv-lp)
tags: added: fonts
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.