Hi Oliver,

At 2025-05-12T12:32:18+0200, Oliver Corff via GNU roff typesetting
system discussion wrote:
> for the first time, I am experimenting with the html output features
> of groff.
> 
> When attempting to compile the attached document (which is compiled
> without problem when using any other -T option)

I can't reproduce that.  When I use stock groff 1.23.0, I get two
errors.

$ ~/groff-1.23.0/bin/groff -k /tmp/TA_html.ms >| /tmp/TA_html.ps
s.tmac:/tmp/TA_html.ms:21: error: automatically terminating display
s.tmac:/tmp/TA_html.ms:28: error: .DE without .DS, .ID, .CD, .LD, .RD, or .BD

...but those shouldn't ruin the rendered document.

> by saying
> 
> $ groff -k -Thtml TA_html.ms > test.html
> 
> The generated html file test.html displays a lot of garbage.

I'm not sure I can reproduce that.  I get a brief recognizable document,
but it appears to have too few word breaks even for German language
text.

And diagnostic output is _copious_.  I get _lots_ of messages like this:

troff:/tmp/TA_html.ms:18: warning [p 1, 0.2i]: cannot break line
...
troff:/tmp/TA_html.ms:35: warning [p 1, 0.4i, div 'toc*div', 0.0i]: cannot 
break line

Because of the way grohtml works, I also get every diagnostic message
twice.

Comparing PostScript and HTML output, it looks almost as if inter-word
spacing was completely defeated, which explains the overset lines and
lack of work breaks.  Apart from that admittedly major defect, things
look fine.

Since they're short, I'm attaching both of these output files.

> I'm afraid I am missing some basic information here.

I wonder what version of groff you are using, and I am concerned that we
are not getting similar results.

> I even managed to crash groff (core dump) with longer input files to
> be typeset with the ms macro set.

I definitely want more information about this.  Please send me a
reproducing specimen for the crasher--privately if necessary.  Please
include the command line you used and the output of "groff --version".

If this core dump problem lingers in groff Git, I would like to resolve
it before releasing 1.24.0.

Regards,
Branden

Attachment: signature.asc
Description: PGP signature

Reply via email to