bugGNU 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

Submitted by:  None
Submitted on:  Sat 03 Jan 2009 01:00:37 AM UTC  
 
Category:  End-user / runtime Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  Bruno Haible <haible>
Open/Closed:  Closed

Sat 24 Jan 2009 11:51:08 PM UTC, comment #3:

> some utilities such as grep are locale-dependent (ISO-8859-1
> is useful e.g. if one has ISO-8859-1 text files). So, one may
> need ISO-8859-1 locales, at least under some occasions.


This is a convincing argument. I'm adding support for the
non-UTF-8 locales to config.charset on 2009-01-24.

Bruno Haible <haible>
Project AdministratorIn charge of this item.
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).

Also note that UTF-8 support under Mac OS X is broken (cooked mode doesn't work correctly, some POSIX functions related to Unicode are buggy...). And some utilities such as grep are locale-dependent (ISO-8859-1 is useful e.g. if one has ISO-8859-1 text files). So, one may need ISO-8859-1 locales, at least under some occasions.

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
with encodings other than UTF-8. But these locales cannot
work satisfactorily for the user, because the encoding uses
for filenames MUST be UTF-8. See
http://lists.apple.com/archives/unix-porting/2002/Aug/msg00089.html
and
http://x0.dk/MacOS-X/SystemOverview.pdf
section "The File System > File Encodings and Fonts".

If filenames are in UTF-8, and a user attempts to use a locale
in another encoding, such as ISO-8859-1, results will not
be satisfactory.

What is the use that you want to make of these locales?

IMO, Apple simply forgot to remove these locale files.

Bruno Haible <haible>
Project AdministratorIn charge of this item.
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.

[*] http://groups.google.com/group/gnu.utils.bug/browse_thread/thread/a48b04706c598369

FYI, here are the bug reports related to this problem in MacPorts (they can give information on what's going on):

Anonymous

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by haible (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-11-27 haible CategoryNone => End-user / runtime
    2009-01-24 haible StatusNot a Bug => Fixed
    2009-01-18 haible StatusNone => Not a Bug
        Assigned toNone => haible
        Open/ClosedOpen => Closed

    Back to the top


    Powered by Savane 3.3