GNU gettext - Bugs: bug #25235, gettext provides a buggy...
You are not allowed to post comments on this tracker with your current authentication level.
bug #25235: gettext provides a buggy charset.alias for Mac OS X
Submitter: | None | ||
Submitted: | Sat 03 Jan 2009 01:00:37 AM UTC | ||
Category: | End-user / runtime | Severity: | 3 - Normal |
Item Group: | None | Status: | Fix Released |
Privacy: | Public | Assigned to: | haible |
Open/Closed: | Closed |
Sat 24 Jan 2009 11:51:08 PM UTC, comment #3: |
Bruno Haible <haible> |
Mon 19 Jan 2009 02:48:17 AM UTC, comment #2: I don't use filenames with non-ASCII characters, so that non-UTF-8 locales are fine. Anyway filename encoding under Mac OS X is not compatible with Linux (so that anyone who wants to work with both OS and share files won't use accented characters).
|
Anonymous |
Sun 18 Jan 2009 08:30:48 PM UTC, comment #1: It is true that MacOS X 10.[3-5] comes with some locales
|
Bruno Haible <haible> |
Sat 03 Jan 2009 01:00:37 AM UTC, original submission:
A number of GNU utilities installs a buggy charset.alias for Mac OS X: the effect is that any charset is regarded as UTF-8, so that messages are output in UTF-8 whatever the locale is. As gettext is the source of this file[*], the problem must be fixed here.
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-01-04 | haible | Status | Fixed | Fix Released | |
2016-11-27 | haible | Category | None | End-user / runtime | |
2009-01-24 | haible | Status | Not a Bug | Fixed | |
2009-01-18 | haible | Status | None | Not a Bug | |
Assigned to | None | haible | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-d3ae.
Corresponding source code
This is a convincing argument. I'm adding support for the
non-UTF-8 locales to config.charset on 2009-01-24.