Re: [Inkscape-devel] Minion font problem
On 3/21/07, Vladimir Savic <vlada@...1658...> wrote:
I own Adobe FontFolio 8.0 and have strange problems with Minion font family. Those fonts render correctly with GIMP and Scribus, but not Inkscape.
Are you observing the various font style issues (e.g. bugs 904962 and 1448618)? I only have the Minion styles that come with Acrobat (regular, italic, bold, and bold italic), but they seem to work fine. On the other hand, fonts that contain "special" styles; including Jaja, Gill Sans MT Pro, and DejaVu Sans, don't behave properly.
On Thursday 22 March 2007 16:25:20 Jed Frechette wrote:
On 3/21/07, Vladimir Savic <vlada@...1658...> wrote:
I own Adobe FontFolio 8.0 and have strange problems with Minion font family. Those fonts render correctly with GIMP and Scribus, but not Inkscape.
Are you observing the various font style issues (e.g. bugs 904962 and 1448618)? I only have the Minion styles that come with Acrobat (regular, italic, bold, and bold italic), but they seem to work fine. On the other hand, fonts that contain "special" styles; including Jaja, Gill Sans MT Pro, and DejaVu Sans, don't behave properly.
Hmmm.. "Behave properly"?! That varies inside Inkscape itself, therefore I consider this to be Inkscape bug (not pango or whatever might be related)... Read my description about drop-down menu and Font selector dialog differences.
I know Inkscape has longstanding font bugs in the tracker.
Thank you, Vlada
On Thursday 22 March 2007 4:06 am, Vladimir Savic wrote:
On Thursday 22 March 2007 16:25:20 Jed Frechette wrote:
On 3/21/07, Vladimir Savic <vlada@...1658...> wrote:
I own Adobe FontFolio 8.0 and have strange problems with Minion font family. Those fonts render correctly with GIMP and Scribus, but not Inkscape.
Are you observing the various font style issues (e.g. bugs 904962 and 1448618)? I only have the Minion styles that come with Acrobat (regular, italic, bold, and bold italic), but they seem to work fine. On the other hand, fonts that contain "special" styles; including Jaja, Gill Sans MT Pro, and DejaVu Sans, don't behave properly.
Hmmm.. "Behave properly"?! That varies inside Inkscape itself, therefore I consider this to be Inkscape bug...
Agreed, I should have said Inkscape doesn't behave properly. For example with Gill Sans if I select the Medium style the font-weight gets set to bold. Similarly, if I select the Book style Condensed actually gets used. In my case, using the toolbar has the same, incorrect, effect as using the font dialog. Sorry I wasn't more clear earlier.
On Thursday 22 March 2007 4:05 am, Vladimir Savic wrote:
Using Font selector dialog brings the mess! Fonts are listed there too. First to appear is "Jaja" with numerous faces in the right positioned selector box. Bold face appears, what, about 10-15 times but doesn't change a thing when being clicked on. The same about Medium, Book, Light, Black, and so on. Something is deffinitely wrong here...
That's pretty much exactly what I see too.
Best,
Hmmm.. "Behave properly"?! That varies inside Inkscape itself, therefore I consider this to be Inkscape bug...
Agreed, I should have said Inkscape doesn't behave properly. For example with Gill Sans if I select the Medium style the font-weight gets set to bold. Similarly, if I select the Book style Condensed actually gets used. In my case, using the toolbar has the same, incorrect, effect as using the font dialog. Sorry I wasn't more clear earlier.
Yes, there's been a bug about this around for a while. Right now Inkscape only really undestands 4 variants. Everything else is matched to those in some way.
Pango and fontconfig now support preferred family/style names so a large family can be under one single name with many variants. But Pango has a bug with one of the 10 possible weights, also there's an issue with exotic variants if they share width and stretch with a more generic variant. You can see that with Thin with ExtraLight, and Contour with Regular.
In a perfect world, users should see one family name, with each variants being listed and properly selectable and applicable. This means throwing the current 4 variant limit code from Inkscape and relying on Pango for the rest. That would already fix most of it. Then the rest is a Pango bug.
Cheers,
Denis Moyogo Jacquerye
participants (3)
-
Denis Jacquerye
-
Jed Frechette
-
Vladimir Savic