Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42701 - [gsfonts] Incomplete fonts.dir and fonts.scale

Attached to Project: Arch Linux
Opened by SATO Tatsuya (tattsan) - Friday, 07 November 2014, 04:50 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 19 November 2014, 21:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
mkfontdir and mkfontscale generate incomplete lists for gsfonts package.
fonts.dir and fonts.scale lack n021003l.pfb and n021023l.pfb.

Additional info:
* package version: gsfonts 20130917-1
This task depends upon

Closed by  Gaetan Bisson (vesath)
Wednesday, 19 November 2014, 21:37 GMT
Reason for closing:  Upstream
Comment by SATO Tatsuya (tattsan) - Friday, 07 November 2014, 09:03 GMT
mkfontscale assigns same name for n021003l.pfb and n021004l.pfb, so n021003l.pfb is removed from fonts.scale.
Using pfb2pfa utility, I checked weights of the fonts.

As for the previous version (gsfonts-1.0.7pre44-4), weights are defined as follows:

grep Weight n021003l.pfa
/Weight (Regular) readonly def
grep Weight n021004l.pfa
/Weight (Bold) readonly def

but current vesion (gsfonts-20130917-1):

grep Weight n021003l.pfa
/Weight (Regular) readonly def
grep Weight n021004l.pfa
/Weight (Medium) readonly def
Comment by Gaetan Bisson (vesath) - Monday, 10 November 2014, 23:58 GMT
Can you suggest some way for us to fix this in our PKGBUILD? We simply ship the upstream files and then run mkfontscale on them, again from upstream xorg-mkfontscale, so I am not sure how we could "fix" this problem.
Comment by SATO Tatsuya (tattsan) - Tuesday, 11 November 2014, 07:54 GMT
When I met this problem, I thought upstream distribution of gsfonts should be fixed.
So I post this report as a gsfonts package problem.

But It may be rather mkfontscale which should be fixed.
Mkfontscale assign 'medium' as WEIGHT_NAME XLFD field, both for Medium and Regular Weights of Type1 fonts.
On the other hand, X11 document says:

> 3.1.2.3. WEIGHT_NAME Field
> WEIGHT_NAME is a string that identifies the font's typographic weight, that is, the nominal
> blackness of the font, according to the FOUNDRY's judgment.
(snip)

The string in this field is determined by the FOUNDRY's judgment.
So mkfontscale should NOT regularize the string based on something like X11 convention,
and mkfontscale should distinguish different weights like Regular and Medium.

Could you report this problem to upstream?

I have no good idea to work around this problem via our gsfonts' PKGBULD.
Weights can be altered by using t1utils (t1ascii, t1binary) and sed, but it is not ARCH WAY.
Comment by Gaetan Bisson (vesath) - Tuesday, 11 November 2014, 19:03 GMT
I would be much happier if you reported this problem upstream, since you found and diagnosed it entirely yourself. I am just a humble packager. :)

Loading...