This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi!locale -k CATEGORY_LIST make them more readable.
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.
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?
P.S.: It is not like I would start working on this tomorrow. However, I have wondered about this long enough to ask. :-)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |