Hi Branden
On Sat, 1 Jul 2023, G. Branden Robinson wrote:
The new system won't really work because it uses \n[%] which is not
what I want to get as a page number. I want \nP because I reset it to
zero after the abstract.
Isn't this the "heading mark"-based indexing that groff mm already
sup
On Sat, 1 Jul 2023, Oliver Corff wrote:
Hi Damian,
in the document itself. I still hit a problem with
.SK
.ce
INDEX
.SP 2
.2C
.so myindex
.1C
where I get an extra blank page but I can easily trash that.
Because
.TC
comes after the .1C, there w
Hi Damian,
in the document itself. I still hit a problem with
.SK
.ce
INDEX
.SP 2
.2C
.so myindex
.1C
where I get an extra blank page but I can easily trash that.
The manual groff_mm(7) says:
1C [1] Begin one-column processing. A 1 as an argument disables the
Hi Branden,
On Sat, 1 Jul 2023, G. Branden Robinson wrote:
More precisely, it forces "-mm" to be the first "-m" argument.
Correct.
contrib/mm/mmroff.pl:
# mmroff should always have -mm, but not twice
@ARGV = grep(!/^-mm$/, @ARGV);
my $check_macro = "groff -rRef=1 -z -mm @ARGV";
my $ru
At 2023-07-01T14:55:31+1000, Damian McGuckin wrote:
> Sorted.
>
> The new system won't really work because it uses \n[%] which is not
> what I want to get as a page number. I want \nP because I reset it to
> zero after the abstract.
Isn't this the "heading mark"-based indexing that groff mm alrea
Hi Damian,
At 2023-07-01T11:51:44+1000, Damian McGuckin wrote:
> mmroff is broken. It assumes that '-mm' is the first argument to
> 'groff'
More precisely, it forces "-mm" to be the first "-m" argument.
contrib/mm/mmroff.pl:
# mmroff should always have -mm, but not twice
@ARGV = grep(!/^-mm$
The grohtml man page (as of a Sep 19, 2020 commit) has this item under
Bugs, quoted here in its entirety:
"grohtml does not truly support hyphenation, but you can fool it into
hyphenating long input lines, which can appear in HTML output with a
hyphenated word followed by a space but no line break
