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]

Re: [PATCH] Use Unicode code points for country_isbn


On Tue, 21 Jul 2015, Keld Simonsen wrote:

> It would mean that you cannot use the locale sources for crosscompiling 
> when using some different character sets on the hosting and the target 
> machines. Eg if you are making embedded systems on IOS or Windows or 
> other utf16 machines for an utf8 target, or making stuff for android. Or 
> the other way round if you are omn an utf8 host and generate locales for 
> a utf16 target such as a utf16 embedded system or an iphone or ipad 
> system.

On the build system on which glibc is built, we can always assume that the 
glibc sources are the exact sequences of octets provided by the glibc 
project, not converted into another character set and without any 
conversions of line endings.  Furthermore, on any system using glibc and 
executing tools such as localedef with the installed locale source files, 
it can be assumed that those source files are the files shipped with 
glibc, not those files after conversion into another character set.  Use 
of glibc source files after conversion into another character set is 
outside the scope of the glibc project - glibc is not expected to build 
with such converted source files.

Now, it's true that the installed localedef utility should be usable in 
locale A to generate locale B, for any pair (A, B) of installed locales - 
rather than only being able to generate locales as part of the glibc build 
/ install process.  If localedef interprets locale sources in the 
character set of the locale in which it runs, that may mean the installed 
locale sources do need to be in ASCII.  How does localedef determine the 
character set in which to interpret the textual locale source files?

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]