URL: <https://savannah.gnu.org/bugs/?67711>
Summary: [troff] `pchar` request reports stale character
properties
Group: GNU roff
Submitter: gbranden
Submitted: Sun 16 Nov 2025 09:09:13 PM UTC
Category: Core
Severity: 3 - Normal
Item Group: Incorrect behaviour
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Sun 16 Nov 2025 09:09:13 PM UTC By: G. Branden Robinson <gbranden>
Background: bug #67571
Based on a reproducer of Dave's. I'm getting correct formatter _behavior_ but
when I inquire about a character's properties, I am being lied to. Why?
$ cat EXPERIMENTS/67571c.groff
.br
.class [EOS] :
.cflags 1 \C'[EOS]'
.pchar :
I:
fold.
.pl \n[nl]u
$ nroff EXPERIMENTS/67571c.groff
character ':'
is not translated
does not have a macro
special translation: 0
hyphenation code: 0
flags: 0 (none)
asciify code: 0
ASCII code: 58
Unicode mapping: U+003A
is found
is transparently translatable
is not translatable as input
mode: normal
I: fold.
We've successfully made `:` and end-of-sentence character. See the two spaces
after it? So why isn't `pchar` telling us the truth?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67711>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
