groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #62955] [PATCH] [grops] \(va fallback character overrides glyph


From: G. Branden Robinson
Subject: Re: [bug #62955] [PATCH] [grops] \(va fallback character overrides glyph available in S font]
Date: Tue, 13 Sep 2022 03:35:17 -0500

If anyone objects to this, please speak up soon or be prepared to wait
for groff (1.23)++ to revert it.

Also, if someone can better recollect what I'm trying to remember about
fonts with distinct serif and non-serif copyright signs and similar,
please throw some light on it.

Regards,
Branden

----- Forwarded message from "G. Branden Robinson" <INVALID.NOREPLY@gnu.org> 
-----

Date: Tue, 13 Sep 2022 04:28:47 -0400 (EDT)
From: "G. Branden Robinson" <INVALID.NOREPLY@gnu.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>, Nikita Ivanov
 <nikita.vyach.ivanov@gmail.com>, Deri James <deri@chuzzlewit.myzen.co.uk>,
 bug-groff@gnu.org
Subject: [bug #62955] [PATCH] [grops] \(va fallback character overrides glyph
 available in S font

Update of bug #62955 (project groff):

                  Status:                    None => Confirmed              
         Planned Release:                    None => 1.23.0                 
                 Summary: [grops] \(va fallback character overrides glyph
available in S font => [PATCH] [grops] \(va fallback character overrides glyph
available in S font

    _______________________________________________________

Follow-up Comment #4:

Adding "[PATCH]" annotation.


diff --git a/tmac/ps.tmac b/tmac/ps.tmac
index 8b796e376..0f512b42a 100644
--- a/tmac/ps.tmac
+++ b/tmac/ps.tmac
@@ -51,9 +51,9 @@
 .
 .char \[ru] \D'l .5m 0'
 .
-.fchar \[va] \o'\[ua]\[da]'
-.fchar \[ci] \v'-.25m'\h'.05m'\D'c .5m'\h'.05m'\v'.25m'
-.fchar \[sq] \h'.05m'\D'l .5m 0'\D'l 0 -.5m'\D'l -.5m 0'\D'l 0 .5m'\h'.55m'
+.schar \[va] \o'\[ua]\[da]'
+.schar \[ci] \v'-.25m'\h'.05m'\D'c .5m'\h'.05m'\v'.25m'
+.schar \[sq] \h'.05m'\D'l .5m 0'\D'l 0 -.5m'\D'l -.5m 0'\D'l 0 .5m'\h'.55m'
 .fchar \[Fi] f\[fi]
 .fchar \[Fl] f\[fl]
 .fchar \[ff] ff
@@ -61,15 +61,15 @@
 .fchar \[fl] fl
 .fchar \[ij] ij
 .fchar \[IJ] IJ
-.fchar \[tm] \s-3\v'-.3m'TM\v'+.3m'\s+3
+.schar \[tm] \s-3\v'-.3m'TM\v'+.3m'\s+3
 .
-.fchar \[<<] <\h'-.2m'<
-.fchar \[>>] >\h'-.2m'>
-.fchar \[|=] \v'.075m'\Z'\[mi]'\v'-.15m'\[ap]\v'.075m'
-.fchar \[nc] \v'.1m'\Z'\h'.15m'\F[T]\f[R]/'\v'-.1m'\[sp]
-.fchar \[ne] \v'.07m'\Z'\h'.13m'\F[T]\f[R]/'\v'-.07m'\[==]
-.fchar \[-h] \F[T]\f[I]\v'-.53m'\Z'\h'.05m'\D'l .3m 0''\v'.53m'h
-.fchar \[hbar] \[-h]
+.schar \[<<] <\h'-.2m'<
+.schar \[>>] >\h'-.2m'>
+.schar \[|=] \v'.075m'\Z'\[mi]'\v'-.15m'\[ap]\v'.075m'
+.schar \[nc] \v'.1m'\Z'\h'.15m'\F[T]\f[R]/'\v'-.1m'\[sp]
+.schar \[ne] \v'.07m'\Z'\h'.13m'\F[T]\f[R]/'\v'-.07m'\[==]
+.schar \[-h] \F[T]\f[I]\v'-.53m'\Z'\h'.05m'\D'l .3m 0''\v'.53m'h
+.schar \[hbar] \[-h]
 .
 .de ps-achar
 .  \" Note that character definitions are always interpreted with


These changes look sensible to me.  Potential frustration may await for the
few of these that are letterlike and therefore, one might argue, susceptible
to text styling.

This affects only a few of these, as I see it.

\[tm]
\[-h]
\[hbar]

...and that's really only two, since the last is an alias for \[-h].

In principle, one could argue that the trade mark sign and h-bar should be
styled as the surrounding text is.  I can't remember now where I read it, but
apparently there is some precedent, _not_ in Unicode, for digital fonts to
make available distinct serif and non-serif versions of the trade mark,
copyright, and/or registered signs.

I think the argument is weaker for the h-bar since it is particularized to
mathematical typography and seldom seen in an upright shape.

However, I am inclined to accept this patch as-is.  A document author who
feels passionately about the renderings of these glyphs being styled
differently can always write their own `char` requests to get what they want.

If no one raises any objections I plan to incorporate this patch for groff
1.23.  Thanks, Nikita!


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62955>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/


----- End forwarded message -----

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]