Follow-up Comment #8, bug #63332 (project groff):
Hi Dave,
[comment #7 comment #7:]
> I'll reply more fully later, but I want to address one point now:
>
> [comment #5 comment #5:]
> > > This means the other "t" conditionals in fallbacks.tmac also
> > > don't do what was intended.
> >
> > I don't think that's true.
>
> It's easy enough to demonstrate: pick a definition where > Weirdly, even
adding the line ".if t .tm troff mode" to that file prints "troff mode" on
stderr when groff is run with -Tascii. I presume this is because tmac/troffrc
loads fallbacks.tmac before loading the device-specific .tmac file.
Right. The device description file doesn't say whether it's a "troff" or
"nroff" device; instead a request does that.
> This means the other "t" conditionals in fallbacks.tmac also don't do
what was intended.
fallbacks.tmac makes a distinction based on the n/t mode, such as:
>
> .ie t .fchar \[u2012] \v'-.3m'\l'\w"\0"u\[ru]'\v'+.3m'\" figure dash
> .el .fchar \[u2012] \-
>
>
> $ echo '3\[u2012]4' | groff -Tascii | cat -s
> 3_4
>
>
> Were this working as designed, we'd see a hyphen in the output rather than
an underscore.
Ah, I see what you mean. We were both saying true things but somehow I
managed to infer an incorrect one from you. On re-reading, I'm not sure how.
> > > Weirdly, even adding the line ".if t .tm troff mode" to that file prints
"troff mode" on stderr when groff is run with -Tascii. I presume this is
because tmac/troffrc loads fallbacks.tmac before loading the device-specific
.tmac file.
> > Right. The device description file doesn't say whether it's a "troff" or
"nroff" device; instead a request does that.
> > > This means the other "t" conditionals in fallbacks.tmac also don't do
what was intended.
I concur.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63332>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
