Update of bug #66653 (group groff):

                  Status:               Need Info => In Progress
             Assigned to:                    deri => gbranden
                 Summary: [PATCH] [troff] .asciify odd behaviour / adding pdf
features to ms => [troff] .asciify odd behaviour

    _______________________________________________________

Follow-up Comment #27:

An interesting wrinkle with this.

Some composite characters[1] stick the combining character first, and some
don't.


$ cat src/roff/groff/tests/asciify-composite-nodes-correctly.sh
#!/bin/sh
#
# Copyright 2025 G. Branden Robinson
#
# This file is part of groff.
#
# groff is free software; you can redistribute it and/or modify it under
# the terms of the GNU General Public License as published by the Free
# Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# groff is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
# for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.

groff="${abs_top_builddir:-.}/test-groff"

input='.
.ec @
.box DIV
@[u0106] @[u015E]
.br
.box
.asciify DIV
.DIV
.'

output=$(printf "%s\n" "$input" | "$groff" -T ps -a)
echo "$output"
echo "$output" | grep -qx 'C<aa> S<ac>'

# vim:set autoindent expandtab shiftwidth=2 tabstop=2 textwidth=72:
$ cd build
$ ../src/roff/groff/tests/asciify-composite-nodes-correctly.sh
<beginning of page>
C<aa> <ac>S


I don't quite have this licked, but I think I'm close.

I propose reducing the scope of this ticket to this composite character
problem, and following up with the new PDF features for _ms_ in a new ticket,
since this one's approaching 30 comments.

Updating ticket properties on the assumption my proposal's okay.

[1] in the general sense--unfortunately GNU troff internally abuses this term
to mean "any user-defined character, including fallback character definitions
arising from macro files or contrived via "uniuni.cpp", which no user is
likely to know about


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66653>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to