Project

General

Profile

Bug #481

regression: audacious does not respect filesystem locale

Added by Ariadne Conill about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Major
Assignee:
-
Category:
libaudcore
Target version:
3.6
Start date:
November 20, 2014
Due date:
% Done:

100%

Estimated time:
Affects version:
3.6

Description

Files with non-ascii filenames are not loading for me right now on neither Mac or FreeBSD.

Locale settings are the same on both machines and are:

kaniini@Circe % locale
LANG="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL=

Possible cause is f27227bf2462fb14dd4c7b577305728021e4ded8, will bisect later today.

History

#1 Updated by John Lindgren about 10 years ago

See if this commit helps at all:
https://github.com/audacious-media-player/audacious/commit/cc85a9db4fe5855895a1de1d495152b461ed674c

Although, there should not have been a problem if the system locale is really UTF-8 and the filesystem is also UTF-8 (or correctly mounted so that the OS will convert from UTF-8 to the filesystem's native encoding). In that case Audacious does no character set conversions at all, so there is not really any way to mess things up.

#2 Updated by Ariadne Conill about 10 years ago

Now adding directories is broken...

#3 Updated by Ariadne Conill about 10 years ago

However, UTF-8 is working correct now.

I wonder if the locale is different when launched as an app bundle on Mac. FreeBSD seems to have funky locale handling which appears to be orthogonal.

#4 Updated by John Lindgren about 10 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

#5 Updated by John Lindgren about 10 years ago

William Pitcock wrote:

Now adding directories is broken...

For the record, as discussed on IRC, this was caused only by audacious-plugins needing to be recompiled.

Also available in: Atom PDF