Re: UCS data encoding in localedata

[Mike Frysinger <vapier at gentoo dot org>]

On Friday 06 April 2012 04:18:27 Petr Baudis wrote:
>   Does anyone know the technical reason for using the explicit <U0000>
> UCS encoding in localedata instead of some sane approach like UTF8
> encoded data? I can think of only historical reasons due to the lack
> of support in tools (OS, editors, VCS, ...) in the past, however I
> believe that by now, using UTF8 should be fairly safe.

http://sourceware.org/ml/libc-alpha/2003-04/msg00043.html

>   For me, even with the show-ucs-data tool, deadling with localedata
> files is quite onerous.  Can anyone share any other tricks they use
> when dealing with localedata?  Would there be any resistance to moving
> to UTF8?

seems like we could treat it the same way we already do with "configure" and 
"configure.in".  the .in files could be UTF8, and we'd have simple tools to 
"generate" the non-.in files which we'd also commit to git.

btw, what's with cc-ing libc-announce ?
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.