Arch Linux

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

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.

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.

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. :)