While emerging gnome-base/bonobo I got thousands of lines like these: Malformed UTF-8 character (byte 0xfe) in pattern match (m//) at ../../xml-i18n-merge line 364, <PO_FILE> line 23699. Malformed UTF-8 character (byte 0xfe) in pattern match (m//) at ../../xml-i18n-merge line 364, <PO_FILE> line 23699. Malformed UTF-8 character (unexpected non-continuation byte 0x22, immediately after start byte 0xed) in pattern match (m//) at ../../xml-i18n-merge line 364, <PO_FILE> line 23699. Malformed UTF-8 character (unexpected non-continuation byte 0x22, immediately after start byte 0xed) in pattern match (m//) at ../../xml-i18n-merge line 364, <PO_FILE> line 23699. The emerge completes successefuly(?) inspite of the errors. Is this just cosmetic? Reproducible: Always Steps to Reproduce: 1. export LC_CTYPE=pt_PT.UTF-8 2. emerge bonobo Actual Results: Expected Results: I'm using an UTF-8 locale (pt_PT.UTF-8).
Created attachment 24533 [details, diff] Hardcode LC_CTYPE=C so users with UTF-8 charset don't get error messages during build. After searching bugs.gentoo.org I found one similar bug (#22058) reported against apache. Can we use the same approach here?
we could to stay on the safe side. afaik some gnome devs are on UTF-8 locale as well, can this problem be confirmed ?
no conformation, no further reports. for now i'm gonna close this as an incident, since we're not officially utf-8 powered anyway
