[bug #65322] [troff] chopping box diversions can crash the formatter

Update of bug #65322 (group groff): Status: Unreproducible => None ___ Follow-up Comment #6: See bug #66653 for a new reproducer which also fails in 1.23.0 (and probably 1.22.4)

[bug #66653] .asciify odd behaviour / adding pdf features to ms

Follow-up Comment #3, bug #66653 (group groff): [comment #2 comment #2:] > testing with any other ms documents you have would be appreciated I have none, sorry, or I'd try it on them. > The warning you get running it.trf is because it is a UTF-8 > document, so it needs preconv as well. Ah, yes,

[bug #65967] [docs] Say "input" instead of "input file" where appropriate

Follow-up Comment #11, bug #65967 (group groff): Right, it's just text about the .nx request. But the points raised in comment #3 and comment #7 show that accurate wording that reflects all possible cases is not entirely straightforward, and I need to test some edge cases to see how they even beh

[bug #65954] [troff] next-generation alignment and adjustment control

Follow-up Comment #3, bug #65954 (group groff): On the email discussion list, onf posted a new proposal and a patch to implement it in neatroff (http://lists.gnu.org/r/groff/2025-01/msg00041.html) so that interested parties can try out the modified syntax in a working troff.

[bug #66653] .asciify odd behaviour / adding pdf features to ms

Follow-up Comment #6, bug #66653 (group groff): [comment #5 comment #5:] > To see the second issue you have to run it with ms.ms, D'oh! I'm illiterate. That is indeed the filename in the command you pasted in comment #2. So much for me "trying to mimic your test as closely as possible"!

[bug #65322] [troff] chopping box diversions can crash the formatter

Follow-up Comment #7, bug #65322 (group groff): [comment #6 comment #6:] > See bug #66653 for a new reproducer which also fails in 1.23.0 > (and probably 1.22.4) Specifically the instructions in comment 2 there show how to reproduce the problem using the attached pdfms.tmac. I only needed the se

[bug #63635] [troff] support `hydefault` register or similar

Follow-up Comment #8, bug #63635 (group groff): Noticed the "Fixed" too late. ___ Reply to this item at: ___ Message sent via Savannah https://savannah.

[bug #66653] .asciify odd behaviour / adding pdf features to ms

Follow-up Comment #5, bug #66653 (group groff): The warning:- troff:it.trf:7: warning: special character 'u260E' not defined Occurs if I run 1.23.0. You may remember a "wish" to allow Dingbats glyphs to be accessed using \[u] notation rather than just \N'nnn'. I believe that is now in curren

[bug #66653] .asciify odd behaviour / adding pdf features to ms

Follow-up Comment #4, bug #66653 (group groff): [comment #2 comment #2:] > The two problems can only be seen by making an amendment to pdfms.tmac. I'm still unable to provoke the assertion failure, whether I make both changes to pdfms.tmac, or only the second one. $ cat pdfms.tmac .nr PDFHREF.VI

[bug #63635] [troff] support `hydefault` register or similar

Follow-up Comment #7, bug #63635 (group groff): A patch I've recently submitted to neatroff might be relevant here. In essence, my proposal was this: - add env-local register `.hy1`, default value is 1 - `hy` request with non-zero argument sets `.hy1` - `hy` without argument sets hyphentation mode

[bug #65954] [troff] next-generation alignment and adjustment control

Follow-up Comment #4, bug #65954 (group groff): [comment #3 comment #3:] > On the email discussion list, onf posted a new proposal and a patch to > implement it in neatroff (http://lists.gnu.org/r/groff/2025-01/msg00041.html) > so that interested parties can try out the modified syntax in a workin

[bug #65954] [troff] next-generation alignment and adjustment control

Follow-up Comment #5, bug #65954 (group groff): [comment #4 comment #4:] > [comment #3 comment #3:] > Additionally, request `cl` is added [...] s/cl/al/ ___ Reply to this item at: ___

[bug #63635] [troff] support `hydefault` register or similar

Follow-up Comment #9, bug #63635 (group groff): [comment #7 comment #7:] > A patch I've recently submitted to neatroff might be relevant here. Neatroff's maintainer can of course make his own call about this, but I would prefer to see patches to other roffs that mimic enhancements to groff use th