git rejects gcc errors...

Paul Eggert eggert@cs.ucla.edu
Fri Oct 30 19:27:36 GMT 2020


On 10/30/20 11:52 AM, DJ Delorie via Libc-alpha wrote:
> Given how much gcc's error output is evolving towards "more readable"
> and away from "mostly ascii", can we revisit this git commit rule?
> 
> And why are we dealing with ISO-8859-15 at all, and not UTF-8 ?

Indeed, the glibc source should use UTF-8 except for the few files where other 
encodings make sense, e.g., iconvdata/testdata/*. I realize several files use 
older encodings and it'll be a bit of work to convert them and this is not high 
priority. (I can volunteer to do timezone/southamerica, which was converted to 
UTF-8 long ago upstream. :-)


More information about the Libc-alpha mailing list