Update of bug #67570 (group groff):
Summary: [troff] "cflags 1" sometimes ignored when used on a
class => [troff] `cflags` request ignored when used on a class
_______________________________________________________
Follow-up Comment #9:
So...ah...it would appear that the GNU _troff_ feature of applying character
flags to a character class...uh...doesn't work, and I have to imagine that it
either never did or has been broken for a long, long time.
Or maybe only two months (now three and a half?), given what you said.
> The below examples compare behavior of groff 1.23 and a current groff build.
> The problem only came into groff in the last two months, but I no longer have
> that two-months-ago build for direct comparison.
$ ./build/test-groff -mja
/home/branden/src/GIT/groff/build/../tmac/ja.tmac: warning: font TR may lack
coverage of Japanese script
.pchar \C'[CJKnormal]'
character class '[CJKnormal]'
defined at: file name: "/home/branden/src/GIT/groff/build/../tmac/ja.tmac",
line number: 44
contains ranges: U+3041-U+3096 U+3096 U+30A0-U+30FF U+30FF U+4E00-U+9FFF
U+9FFF
contains nested classes: (none)
.pchar \[u3041]
special character 'u3041'
is not translated
does not have a macro
special translation: 0
hyphenation code: 0
flags: 0 (none)
asciify code: 0
ASCII code: 0
Unicode mapping: U+3041
is found
is transparently translatable
is not translatable as input
mode: normal
$ sed -n '44,+1p' tmac/ja.tmac
.class [CJKnormal] \
\[u3041]-\[u3096] \[u30A0]-\[u30FF] \[u4E00]-\[u9FFF]
I'll go back to the dawn of the `pchar` feature and see if it exposes the
problem.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67570>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
