Le mardi 5 mars 2013 01:16:52, Bill Allombert a écrit :
> On Tue, Mar 05, 2013 at 12:06:06AM +, Roger Leigh wrote:
> > We have defaulted to UTF-8 locales for over a decade now. Unless
> > there are compelling reasons not to use UTF-8 locales, maybe we
> > could perhaps consider retiring them a
On Tue, Mar 05, 2013 at 10:17:58AM +0100, Thomas Preud'homme wrote:
> Le mardi 5 mars 2013 01:16:52, Bill Allombert a écrit :
> > On Tue, Mar 05, 2013 at 12:06:06AM +, Roger Leigh wrote:
> > > We have defaulted to UTF-8 locales for over a decade now. Unless
> > > there are compelling reasons n
On Tue, Mar 05, 2013 at 10:45:35AM +, Roger Leigh wrote:
> Which locales don't currently have charsets mapping to Unicode?
>
> Could we remove the non-UTF-8 locales which /do/ have complete
> UTF-8 coverage and replace them with aliases? That would at least
> achieve the transition for the va
Roger Leigh writes:
> Could we remove the non-UTF-8 locales which /do/ have complete UTF-8
> coverage and replace them with aliases? That would at least achieve the
> transition for the vast majority of locales.
I don't think this is a good idea. There are a lot of legacy ISO 8859-1
or KOI8-R
Le Sat, Mar 02, 2013 at 04:38:49PM +0100, Guillem Jover a écrit :
>
> I'd second something like this, but I'd first like us to consider if
> we really want any non-ASCII characters in filenames. Currently on sid
> there does not appear to be many such filenames (64 from my check, if
> that's not b
Charles Plessy writes:
> * There are names that look rather arbitrary and replaceable
>with ASCII alternatives if needed. For instance in python-pyramid,
>usr/lib/python2.6/dist-packages/pyramid/tests/fixtures/static/héhé.html
At least some of these (for things located in a directory n
6 matches
Mail list logo
