Roger Leigh dixit:
From my reading of the standards a UTF-8 C locale would be required
to behave identically to the existing ASCII C locale:
• will consider all byte sequences valid
I think it wouldn’t (since UTF-8 mbrtowc/wcrtomb don’t work
this way, and it can’t be done with “just” the POSIX
On Sun, Jan 09, 2011 at 10:21:50PM +, Thorsten Glaser wrote:
Roger Leigh dixit:
From my reading of the standards a UTF-8 C locale would be required
to behave identically to the existing ASCII C locale:
• will consider all byte sequences valid
I think it wouldn’t (since UTF-8
Roger Leigh dixit:
I think the all byte sequences valid applies mainly to narrow
character I/O. i.e. printf/puts etc. won't alter, drop or otherwise
mangle any non 7-bit-ASCII codes. i.e. I think the intent was to
ensure 8-bit cleanliness in a 7-bit locale. This naturally extends
to UTF-8.
On Sat, Nov 27, 2010 at 01:23:29PM +0200, Kalle Olavi Niemitalo wrote:
Josselin Mouette j...@debian.org writes:
I think wheezy would be a good time to finally ditch non-UTF8 locales.
IIRC, we made the switch to UTF8 by default in etch (and we were already
way too late in doing that),
On Sun, Nov 28, 2010 at 05:21:33PM +, Thorsten Glaser wrote:
Fun to be reading this. Me like ;-)
Anyway. With my Debian hat on, the C/POSIX locales must not use
UTF-8 as encoding, because otherwise, all kind of hell breaks
loose (consider running 'tr u x' on a binary or other legacy
On 11/12/2010 06:47, Kalle Olavi Niemitalo wrote:
Vincent Danjean vdanj...@debian.org writes:
For example, I've lots of old text data in latin1. Some of them are on
non-rewritable media. Being able to see them with
LC_CTYPE=fr_FR less toto.txt is very convenient.
less does not convert
Vincent Danjean vdanj...@debian.org writes:
For example, I've lots of old text data in latin1. Some of them are on
non-rewritable media. Being able to see them with
LC_CTYPE=fr_FR less toto.txt is very convenient.
less does not convert the characters to UTF-8 for display, so you
also need a
On 04/12/2010 00:15, Aurelien Jarno wrote:
Hi,
On Thu, Nov 18, 2010 at 02:07:37PM +0100, Josselin Mouette wrote:
Package: locales
Version: 2.11.2-7
Severity: wishlist
Hi,
I think wheezy would be a good time to finally ditch non-UTF8 locales.
IIRC, we made the switch to UTF8 by
Hi,
On Thu, Nov 18, 2010 at 02:07:37PM +0100, Josselin Mouette wrote:
Package: locales
Version: 2.11.2-7
Severity: wishlist
Hi,
I think wheezy would be a good time to finally ditch non-UTF8 locales.
IIRC, we made the switch to UTF8 by default in etch (and we were already
way too
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Hi!
Fun to be reading this. Me like ;-)
Anyway. With my Debian hat on, the C/POSIX locales must not use
UTF-8 as encoding, because otherwise, all kind of hell breaks
loose (consider running 'tr u x' on a binary or other legacy
encoded text file,
Josselin Mouette j...@debian.org writes:
I think wheezy would be a good time to finally ditch non-UTF8 locales.
IIRC, we made the switch to UTF8 by default in etch (and we were already
way too late in doing that), and supporting non-UTF8 stuff becomes
harder and harder, at least for
Package: locales
Version: 2.11.2-7
Severity: wishlist
Hi,
I think wheezy would be a good time to finally ditch non-UTF8 locales.
IIRC, we made the switch to UTF8 by default in etch (and we were already
way too late in doing that), and supporting non-UTF8 stuff becomes
harder and harder, at
12 matches
Mail list logo
