[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #62923] [gropdf] glyph aliases in in font description files not par
From: |
G. Branden Robinson |
Subject: |
[bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly |
Date: |
Tue, 23 Aug 2022 14:28:06 -0400 (EDT) |
Update of bug #62923 (project groff):
Status: Need Info => Fixed
Assigned to: None => deri
Open/Closed: Open => Closed
Planned Release: None => 1.23.0
_______________________________________________________
Follow-up Comment #11:
Hi Deri,
[comment #10 comment #10:]
> I'm not sure what extra information you require, I fixed and closed the
original bug, confirmed by the submitter.
>
> Then a second bug was raised about the misalignment of the square root
extension bar. It has a tenuous link to aliased glyphs because the XITSMR font
has a glyph sqrtex but eqn has a hardcoded name for the bar glyph of
radicalex. I have done my analysis of the problem and confirmed that it
affects grops as well as gropdf with identical (wrong) output. Since this has
nothing to do with a bug in gropdf, I have removed myself from the
assignation.
>
> Hopefully you can check the analysis I have already done and do your own
analysis.
Thanks, this largely clears things up for me. Sounds like it might be a bug
in eqn, then.
Per _groff_char_(7) from Git HEAD:
In AT&T troff, \(rn (“root en extender”) served as the horizontal
extension of the radical (square root) sign, \(sr, and was drawn
at the maximum height of the typeface’s bounding box; this
enabled the special character to double as an overline (see
subsection “Rules and lines” above). A contemporary font’s
radical sign might not ascend to such an extreme. In groff, you
can instead use \[radicalex] to continue the radical sign \[sr];
these special characters are intended for use with text fonts.
\[sqrt] and \[sqrtex] are their counterparts with mathematical
spacing.
It seems like eqn should always be using \[sqrtex] to extend radical signs.
...but it's a separate issue, and I (or someone else) can file it. For this
ticket, I think you should keep the credit for the swift fix. :)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62923>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [bug #62923] Broken aliases in PDF font description file, (continued)
- [bug #62923] Broken aliases in PDF font description file, Deri James, 2022/08/19
- [bug #62923] Broken aliases in PDF font description file, anonymous, 2022/08/20
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, G. Branden Robinson, 2022/08/20
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, G. Branden Robinson, 2022/08/20
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, Nikita Ivanov, 2022/08/20
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, G. Branden Robinson, 2022/08/20
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, Deri James, 2022/08/20
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, G. Branden Robinson, 2022/08/23
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, G. Branden Robinson, 2022/08/23
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, Deri James, 2022/08/23
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly,
G. Branden Robinson <=
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, G. Branden Robinson, 2022/08/24
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, Deri James, 2022/08/24
- [bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly, Deri James, 2022/08/25