This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Should glibc provide a builtin C.UTF-8 locale?
- From: Andreas Schwab <schwab at linux-m68k dot org>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: keld at keldix dot com, Rich Felker <dalias at libc dot org>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 13 Feb 2015 10:23:14 +0100
- Subject: Re: Should glibc provide a builtin C.UTF-8 locale?
- Authentication-results: sourceware.org; auth=none
- References: <54DB8243 dot 3050903 at redhat dot com> <20150211235304 dot GA20330 at www5 dot open-std dot org> <20150212023923 dot GP23507 at brightrain dot aerifal dot cx> <20150212063839 dot GA10787 at www5 dot open-std dot org> <20150212151509 dot GQ23507 at brightrain dot aerifal dot cx> <20150212192544 dot GA19724 at www5 dot open-std dot org> <54DD0DCD dot 8010004 at redhat dot com>
"Carlos O'Donell" <carlos@redhat.com> writes:
> glibc/catgets/open_catalog.c:
> 216 (struct catalog_obj *) __mmap (NULL, st.st_size, PROT_READ,
> 217 MAP_FILE|MAP_COPY, fd, 0);
That's for X/Open style msg files, which nobody is using. You need to
look at intl/loadmsgcat.c.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."