is utf-8 the standard filename encoding?

Zygmunt Bazyli Krynicki zygmunt.krynicki at
Thu Dec 22 10:45:05 UTC 2011

As a command-not-found maintainer I can tell you that 90% of the bugs are encoding related. Just last week I've noticed that screen on oneiric happily produces incorrect multibyte sequences for the same keystrokes that work correctly under the same terminal emulator. The number of people running with the utterly broken C (ASCII) locale is staggering. Another cause of bugs is people redirecting/piping output to a pager. In vanilla python app that does i18n that simply crashes all the time (streams have ASCII encodings in that case). Yet another problem is sys.argv encoding. And people ssh-ing to their ubuntu server boxes with putty that defaults to windows legacy encoding depending on windows locale (Latin-1, Latin-2, etc)

There is no end to this mess.

Wysłane z iPhone'a

Dnia 21 gru 2011 o godz. 19:26 Martin Packman <martin.packman at> napisał(a):

> On 21/12/2011, Steve Langasek <steve.langasek at> wrote:
>> Regardless of any other issues, this is either an Ubuntu bug or a very
>> strange local misconfiguration.  /etc/pam.d/cron is set up to pull in
>> /etc/default/locale by default, and on an Ubuntu system, barring extreme
>> measures on the part of the system admin, my understanding is that this
>> should always define a UTF-8 locale.
> Bazaar had a number of etckeeper related bugs along these lines from
> users on 11.10 and only one of these has a suspect locale setting:
> Likely the defaults are correct, but there still seems to be no
> shortage of people who end up with 'ANSI_X3.4-1968' in some
> circumstances anyway.
> Martin
> -- 
> ubuntu-devel mailing list
> ubuntu-devel at
> Modify settings or unsubscribe at:

More information about the ubuntu-devel mailing list