Vincent Lefevre wrote:
> > I hardcoded the contents of charset.alias for glibc systems, so as to
> > avoid such conflicts for RPM and Debian packaging tools. Shall I do
> > the same for MacOS X? It will resolve the problem with the conflict,
> > but users will then not be able to customize the file
Vincent Lefevre wrote:
> > > I've just reported a bug against gettext:
> > >
> > > https://savannah.gnu.org/bugs/index.php?25235
> >
> > See my response there. In summary, locales with an encoding other than
> > UTF-8 are not supported by MacOS X because filenames MUST be in UTF-8 on
> > this p
On 2009-01-18 21:41:37 +0100, Bruno Haible wrote:
> Hello Vincent,
>
> You brought up two different issues:
> 1) The fact that config.charset for MacOS X recognizes only UTF-8 locales.
> 2) The conflicts when packaging software sees a charset.alias file that
>belongs to different packages.
>
Hello Vincent,
You brought up two different issues:
1) The fact that config.charset for MacOS X recognizes only UTF-8 locales.
2) The conflicts when packaging software sees a charset.alias file that
belongs to different packages.
Ad 1)
Vincent Lefevre wrote:
> > You are better off filing this
Hi,
On 2008-11-14 21:11:56 -0700, Eric Blake wrote:
> You are better off filing this report against gettext, which is the
> source of this file, and/or gnulib, which ships the latest version
> of this file even in packages (such as m4) that have not yet
> undergone the I18n conversion to use gette
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Vincent Lefevre on 11/14/2008 7:12 PM:
Hello Vincent, and thanks for the report.
> A number of utilities, including bison, m4 and findutils, install a
> charset.alias file under Mac OS X, and this breaks the locale system
> (any locale i
