Follow-up Comment #10, bug#59962 (group groff):
[comment #8 comment #8:]
> You are probably right. Po4a emits:
> po4a::man: This page includes another file with '.mso'. Do not forget to
translate this file ('pic.tmac').
> But this "other file" ('pic.tmac') does not appear.
Ah, pointing to .mso is
On Sun, Jan 14, 2024 at 05:23:28PM -0500, G. Branden Robinson wrote:
> Subject: [bug #64285] [troff] \D't' (set line thickness) drawing command
> alters drawing position
>
> Update of bug#64285 (group groff):
> ...
> > If you think fixing a crazy (but well known and documented)
> > "feature" is m
Follow-up Comment #9, bug#59962 (group groff):
[comment #8 comment #8:]
> The new macro is a great idea and I agree that it will be
> picked up properly very slowly. Is it a GNU extension and
> which minimum requirement is attached to it?
The .MR man macro originated as an extension in Plan 9 tro
Follow-up Comment #14, bug#64285 (group groff):
[comment #12 comment #12:]
> If you think fixing a crazy (but well known and documented) "feature"
> is more important than maintaining 30 years of groff compatibility,
I wrote a response to this point as well, then realized I was only repeating
my
Update of bug#64285 (group groff):
Status: Need Info => None
Assigned to:deri => gbranden
___
Follow-up Comment #13:
[comment #12 comment #1
Follow-up Comment #26, bug#63074 (group groff):
In my seat-of-the-pants example, I committed the same crime I complained of:
lack of input validation. My point might be easier to understand if I add it
in.
.nr refno 1
.de DEFREF
. nr refno +1
. if !\A'\\$1' \
.ab bogus tag '\\$1' in refer
Follow-up Comment #25, bug#63074 (group groff):
[comment #24 comment #24:]
> Bug #64484 is marked as fixed.
Right, but I believe there was a relationship nevertheless.
> I already have a reliable way to pass byte sequences in device control
commands, .stringhex.
Okay. But it didn't do anything
Follow-up Comment #12, bug#64285 (group groff):
[comment #10 comment #10:]
> I see very little difference between PS and PDF output for your input
exhibit in comment #9, using bleeding-edge _groff_.
I agree.
> Regarding the topic at issue, I propose that the first and second paragraphs
should l
Follow-up Comment #24, bug#63074 (group groff):
Bug #64484 is marked as fixed. I already have a reliable way to pass byte
sequences in device control commands, .stringhex. This bug was previously
named "warning messages when using special characters in TITLE or AUTHOR" and
the attached cyrillic.pd
Update of bug#62471 (group groff):
Status: Fixed => In Progress
Open/Closed: Closed => Open
___
Follow-up Comment #10:
Ah, but consider this.
Update of bug#63074 (group groff):
Depends on: => bugs #64484
___
Follow-up Comment #23:
Adding dependency on bug #64484, because to achieve the aim of this ticket, a
reliable means of tran
Follow-up Comment #8, bug#59962 (group groff):
Hello Dave,
sorry for having missed Brandens reply (and thus the delay in responding).
#1
I think we discussed this already, I sill think this is not correct, but it
does not make sense to discuss this further
#2
Thanks for the explanation.
a) cons
12 matches
Mail list logo
