Hi Peter,
At 2024-02-19T12:39:53-0500, Peter Schaffter wrote:
> Your minimal file renders fine on my system without -Kutf8 *and* I
> recently encountered a file with a single accented character where
> passing -Kutf8 had no effect (I had to introduce the character
> "silently" in an unused
Update of bug#64233 (group groff):
Severity: 3 - Normal => 1 - Wish
Item Group: Warning/Suspicious behaviour => Feature change
Status:None => Fixed
Assigned to:
At 2024-02-19T22:12:53-0500, Douglas McIlroy wrote:
> > The question is whether or not man macros can be expanded
> > to their groff equivalents.
>
> If you'd consider a preprocessor based on groff, there's a
> notionally simple way to get a copy of the input with macros
> and strings expanded:
> The question is whether or not man macros can be expanded
> to their groff equivalents.
If you'd consider a preprocessor based on groff, there's a
notionally simple way to get a copy of the input with macros
and strings expanded: Provide a groff option that has the
side effect of sending
On Sun, 18 Feb 2024 17:14:37 -0600
"G. Branden Robinson" wrote:
> > For example, would a man(7) parser need to recognize groff(7)
> > requests?
>
> Ingo Schwarze is well placed to answer that,
Looking at it more closely, perhaps I see what concerns you. It's not
parsing the man page. It's
On Mon, Feb 19, 2024, Samuel Stoddard wrote:
> Hi! I'm having a problem using the .RECTO_VERSO macro, namely that for all
> of the verso pages the left margin is about 3 inches more than it should
> be, and the page content is shifted off the physical dimensions of the
> page.
Update to the
Hi! I'm having a problem using the .RECTO_VERSO macro, namely that for all
of the verso pages the left margin is about 3 inches more than it should
be, and the page content is shifted off the physical dimensions of the
page. I don't know if this is actually about margins, though -- it might
be
Follow-up Comment #3, bug#65246 (group groff):
This fix addresses one of the complaints of bug #58036.
Also, to add to the fix's NEWS item's sentence "The download file for grops
shipped by groff has long used tabs rather than spaces for field separation":
fortunately, so have the "download"
Robert --
On Mon, Feb 19, 2024, Robert Goulding via wrote:
> I have been trying to figure this out all morning! I have a handout with
> the word "kataskeuê" in it. Every time I try to compile it (groff -Tpdf -k
> -ms) I get the warning: warning: special character 'u0053_0326' not defined
> (Same
A, thank you so much (I needed to RTFM!) - R.
On Mon, Feb 19, 2024 at 12:44 PM G. Branden Robinson <
g.branden.robin...@gmail.com> wrote:
> Hi Robert,
>
> At 2024-02-19T12:40:16-0500, Robert Goulding via wrote:
> > To answer my own question: It seems that preconv is not guessing the
> >
Hi Robert,
At 2024-02-19T12:40:16-0500, Robert Goulding via wrote:
> To answer my own question: It seems that preconv is not guessing the
> correct encoding from the file with a single word in it. If I specify
> -K utf-8 everything works OK.
>
> preconv -v reports: GNU preconv (groff) version
To answer my own question: It seems that preconv is not guessing the
correct encoding from the file with a single word in it. If I specify -K
utf-8 everything works OK.
preconv -v reports: GNU preconv (groff) version 1.23.0 with iconv support
and with uchardet support
Is this an expected
I have been trying to figure this out all morning! I have a handout with
the word "kataskeuê" in it. Every time I try to compile it (groff -Tpdf -k
-ms) I get the warning: warning: special character 'u0053_0326' not defined
(Same if I go the ps2pdf route)
Try and compile this minimal file
.LP
13 matches
Mail list logo
