Follow-up Comment #10, bug #67570 (group groff): Weird.
$ git describe
1.23.0-2953-g40f7ca3da
$ ./build/test-groff -mja
japanese.tmac: warning: font TR may lack coverage of Japanese script
.pchar \C'[CJKnormal]'
special character "[CJKnormal]"
is not translated
does not have a macro
special translation: 0
hyphenation code: 0
flags: 512
ASCII code: 0
asciify code: 0
is found
is transparently translatable
is not translatable as input
mode: normal
.pchar \[u3041]
special character "u3041"
is not translated
does not have a macro
special translation: 0
hyphenation code: 0
flags: 0
ASCII code: 0
asciify code: 0
is found
is transparently translatable
is not translatable as input
mode: normal
But weird is good, because I see two things to dig into.
1. Back in March, at the birth of `pchar`, the **correct** character flags
were reported for the `[CJKnormal]` character class, even if that class was
misidentified as a special character in debugging output. That change can be
bisected.
2. The wrong character flags are reported for the U+3041 character itself.
Unclear if that's because it was already broken, or because the reporting was
incorrect.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67570>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
