Bazaar

want configuration option for filesystem encoding

Bug #538925 reported by Martin Pool
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar
Won't Fix
Medium
Unassigned

Bug Description

We get many bugs <https://bugs.edge.launchpad.net/bzr/+bugs?field.tag=unicode> caused to bzr not being able to read or write a particular filename because it's not valid in the user's filesystem encoding, which is typically ascii in these cases. It might be nice if there was a bzr setting we could easily suggest people set to override this: getfsencoding() is defined in a complicated way inside site.py.

Tags: unicode
Revision history for this message
Martin Packman (gz) wrote :

I can't think of any situation where the right fix to tell someone having trouble would be to leave their system with a bogus configuration and add something to bazaar.conf instead.

However, being able to fixup files that aren't in the current encoding in a semi-automated way might be a nice feature.

Revision history for this message
Martin Packman (gz) wrote :

I think the short story of PYTHONFSENCODING provides good rationale for why this is a bad idea:

<http://mail.python.org/pipermail/python-dev/2010-October/104758.html>

The easy setting people can use as an override is called LC_ALL.

Changed in bzr:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.