Invalid characters in file name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
Step 1 :
I got file names with invalid encoding (mainly from an Ooooold Mac)
In nautilus, it is displayed as
Ch 03 _ jud�o-christian
But an ls command displays :
Ch 03 _ jud?o-christian
(Without the "codage non valide" mention)
Step 2 :
In Nautilus, I renamed the file just by correcting the invalid character :
The result is :
Ch 03 _ judéo-christian
And the ls command issues :
Ch 03 _ judéo-christian
So I had originally an invalid file without any mention of it in command line, and I end with a correctly encoded filename with the mention "codage non valide"
I wish a more consistent behaviour by not writing back the string " (codage non valide)" to the file name after correction,
or by writing the string " (codage non valide)" to the file name on detection of the invalid coding.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.
ProcVersionSign
Uname: Linux 3.13.0-68-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 15 08:09:53 2015
GsettingsChanges:
b'org.
b'org.
b'org.
InstallationDate: Installed on 2014-05-24 (539 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in nautilus (Ubuntu): | |
importance: | Undecided → Low |