Some unicode is getting mangled in commit messages. Example: $ rlog gentoo-x86/app-accessibility/brltty/ChangeLog,v Fix building with recent glibc wrt #339846 by Diego E. Pettenò. $ git show 7e1a335bb4316ef762faa89b164298afa9a4486f Fix building with recent glibc wrt #339846 by Diego E. Pettenò.
This issue still exists in the latest bundle: git show 0e19e14ecb4481d22fb8595415941e0a5bbe9e4a Fix building with recent glibc wrt #339846 by Diego E. Pettenò.
Is that only 'some unicode' or all of non-ascii characters?
(In reply to comment #2) > Is that only 'some unicode' or all of non-ascii characters? Not sure. I'll see if I can spot any patterns. My current list has a ton of false positives in it and I'm weeding those out. I should know more tomorrow as I think I figured out where those are coming from and am reprocessing the cvs tree.
(In reply to comment #2) > Is that only 'some unicode' or all of non-ascii characters? Skimming through the list of messages it appears to be characters found in names, but those are the main places where unicode occurs in the first place. I'm only looking at messages that didn't match between cvs and git, so I can't speak to any unicode characters that convert correctly. Some examples: | 6026e2e2acef7ec80d5ac335a8a6833294f41149 | Rename USE="sound" to USE="libcanberra" wrt #354585 by Ulrich Müller. | cef8389f40eb7ca8a0c1f1b759ce5d94b8d2e8f8 | Create /etc/X11/Sessions/Xfce4 here now that sta rtxfce4 is here too by MichaÅ Górny | b908201d821125c1af3be227419d0d02103fd786 | Fix translation issues noticed with at least xdg-user-dirs wrt #360853 as reported by Martin Jürgens. Patch is from upstream #4746 by Mark Trompell. | 0d4922072593e703aa8bc5449642b11f24699b9a | Backport upstream patch to include Chromium (or Google Chrome) in the preferred browsers list wrt #388853 by Michael Mol and PaweÅ Hajdan, Jr. | 8e26ebf3398f3ca8daf08181f232a9823e7913d4 | Fixed when compiled with cairo-3. Thanks to Francisco José Cañizares Santofimia <telefrancisco@lycos.es>; bug #80977. | 4d87b58ae56f3024458bc66f9b1e3f95ca3dd7a4 | Marked stable on AMD64 based on arch testing by Agostino "ago" Sarubbo in bug #380421 filed by ChÃ-Thanh Christopher Nguyá» n.
The config change worked - confirmed issue not present in run2. I spotted one or two odd unicode characters, but they were present in cvs as well (likely typos).