Follow-up Comment #29, bug #63018 (group groff): Dave.
I think the implied question is: When it is a separate make target (bug #65698), if we wish to retain the epsilon kerns the make target must either re-apply the shell script after the font generation, or these "gold" AFMs should have the extra kerns added once before we pour aspic on them. The make targe then gets run whenever afmtodit, the maps, or the encoding files, are altered. As far as I can tell the "slant" parameter does nothing for composite (e.g. a glyph plus an accent glyph on top of each other) placement. What it does do is affect both italic correction factors and the subscript correction, i.e. when a font switches from roman to italic for example. Branden. You piqued my curiosity about Hungarian umlauts, so I took a peak at the list archives. :-) There are two issues with Gergő's predicament. His package was built with no URW fonts whatsoever, even though the required fonts are sitting in /usr/share/fonts/Type1/ as can be seen in the list of files supplied to Alex. I know this because the pdf he supplied had absolutely no embedded fonts in it, so if you cast your mind back to the games played with the URW font detection during configure, he has the setup where only the base 14 pdf fonts would be available (without warnings about missing fonts). The placement of the umlauts is because the standard fonts lack the four individual glyphs, so groff sends a composite:- wx font 5 TR f5 h13750 Ca" to wh13750 Ca" tO wh13750 Ca" tu wh13750 Ca" tU Where the U- foundry fonts have separate glyphs:- wx font 42 U-TR f42 h13750 Cu006F_030B wh41250 Cu004F_030B wh53460 Cu0075_030B wh41250 Cu0055_030B In the attached pdf you can see that in the U- fonts the height of the umlaut is fitted to the height of the letter, since the glyph is custom designed. It is always better to use a single glyph rather than composing a compose. I did send him some information how to access those URW fonts by just replacing the TR, TI... With 4 custom versions, but it was just an email, since I am no longer on the list, so it may get filed as "junk". Also, because of the big pointsize, it is easier to see what is happening. In TI and TBI you can see the umlaut is slightly shifted to the right, this has nothing to do with "slant" it is just an artifact of the probable transformation applied to TR to arrive at TI when the font was designed. (file #56036) _______________________________________________________ Additional Item Attachment: File name: umlautTimes.pdf Size: 27KiB <https://file.savannah.gnu.org/file/umlautTimes.pdf?file_id=56036> AGPL NOTICE These attachments are served by Savane. You can download the corresponding source code of Savane at https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-0329bc976c56c39d462c6cc5223a9b3c843a6486.tar.gz _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?63018> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/