Update of bug #67837 (group groff):
Status: None => Need Info
Assigned to: None => barx
Summary: Document flag interaction of character class and
individual character => document flag interaction of character class and
individual character
_______________________________________________________
Follow-up Comment #1:
I think before I can document this interaction intelligently, I need to
understand it. Can you deploy the newly enhanced `pchar` request against bug
#67571?
I'm wondering if maybe the "lazy" character-flag ORing that Werner introduced
as an optimization is going awry. The enhanced `pchar` request now
distinguishes flags "inherent" to the character from those absorbed via class
membership.
$ ~/groff-HEAD/bin/nroff -mja
.pchar \C'[CJKprepunct]'
character class '[CJKprepunct]'
defined at: file name: "/home/branden/src/GIT/groff/build/../tmac/ja.tmac",
line number: 32
contains code points: U+002C U+003A U+003B U+003E U+007D U+3001 U+3002
U+FF0C U+FF0E U+30FB U+FF1A U+FF1B U+FF1F U+FF01 U+FF09 U+3015 U+FF3D U+FF5D
U+300D U+300F U+3011 U+3041 U+3043 U+3045 U+3047 U+3049 U+3063 U+3083 U+3085
U+3087 U+30FC U+30A1 U+30A3 U+30A5 U+30A7 U+30A9 U+30C3 U+30E3 U+30E5 U+30E7
flags: 128 (prohibits break before)
.pchar ,
character ','
is not translated
does not have a macro
special translation: 0
hyphenation code: 0
inherent flags: 0 (none)
effective flags: 128 (prohibits break before)
asciify code: 0
ASCII code: 44
Unicode mapping: U+002C
is found
is transparently translatable
is not translatable as input
mode: normal
Maybe this ticket should _depend_ on bug #67571, but I don't suppose I'll know
for sure until understanding is achieved.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67837>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
