Dear All,
I am using XFCE on F18. Unfortunately, the accented characters in the file names are not shown correctly on Thunar, as well as on Terminal. Is there some workaround?
Thanks in advance,
Paul
On Sat, 2013-03-16 at 10:17 +0000, Paul Smith wrote:
I am using XFCE on F18. Unfortunately, the accented characters in the file names are not shown correctly on Thunar, as well as on Terminal. Is there some workaround?
Post the output of running the locale command (as the user you're logged in as). My guess is that you're not using the write character encoding (usually, UTF8, these days).
On Sun, Mar 17, 2013 at 6:33 AM, Tim ignored_mailbox@yahoo.com.au wrote:
I am using XFCE on F18. Unfortunately, the accented characters in the file names are not shown correctly on Thunar, as well as on Terminal. Is there some workaround?
Post the output of running the locale command (as the user you're logged in as). My guess is that you're not using the write character encoding (usually, UTF8, these days).
Thanks, Tim. My locale command produces the following:
$ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= $
Paul
On Sun, 2013-03-17 at 08:46 +0000, Paul Smith wrote:
My locale command produces the following:
$ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= $
Looks normal, to me. Looking at another reply in this thread, makes me wonder if the files were originally written using that locale before you imported them, or something was happening to them during the import.
UTF8 has been the default for a very long time, I can't recall how old it'd have to be before something else was.
What file system were they stored in? They haven't been through a Windows file system, or through Samba?
On 03/16/2013 11:17 AM, Paul Smith wrote:
Dear All,
I am using XFCE on F18. Unfortunately, the accented characters in the file names are not shown correctly on Thunar, as well as on Terminal. Is there some workaround?
Open a terminal and cd to a writeable directory of your choice (which you can access with Thunar).
Reproduce these commands and see if your results are different:
$ perl -e 'print "\xe2\x82\xac\n"' €
(this is a UTF8 euro sign printed in the terminal)
$ perl -e 'print "\xe2\x82\xac\n"'|wc -m 2
(this is confirmation that the system knows it's a euro and a linefeed)
$ perl -e 'print "touch \xe2\x82\xac\n"'|sh
(this is to create a file with a euro name, now check what is shown in Thunar)
Let me know what you get.
On Sun, Mar 17, 2013 at 10:55 AM, Roberto Ragusa mail@robertoragusa.it wrote:
I am using XFCE on F18. Unfortunately, the accented characters in the file names are not shown correctly on Thunar, as well as on Terminal. Is there some workaround?
Open a terminal and cd to a writeable directory of your choice (which you can access with Thunar).
Reproduce these commands and see if your results are different:
$ perl -e 'print "\xe2\x82\xac\n"' €
(this is a UTF8 euro sign printed in the terminal)
$ perl -e 'print "\xe2\x82\xac\n"'|wc -m 2
(this is confirmation that the system knows it's a euro and a linefeed)
$ perl -e 'print "touch \xe2\x82\xac\n"'|sh
(this is to create a file with a euro name, now check what is shown in Thunar)
Let me know what you get.
Thanks, Roberto. I get everything correct, likewise what you get. The problem occurs with directories that I brought in from previous Fedora installations. For example, I get the following in Thunar:
Estat�stica (invalid encoding)
Paul
On 17.03.2013 15:42, Paul Smith wrote:
On Sun, Mar 17, 2013 at 10:55 AM, Roberto Ragusa mail@robertoragusa.it wrote:
...
Thanks, Roberto. I get everything correct, likewise what you get. The problem occurs with directories that I brought in from previous Fedora installations. For example, I get the following in Thunar:
Estat�stica (invalid encoding)
yum info convmv fuse-convmvfs yum install convmv fuse-convmvfs man convmv less /usr/share/doc/fuse-convmvfs-0.2.6/README
poma
On 03/17/2013 04:13 PM, poma wrote:
On 17.03.2013 15:42, Paul Smith wrote:
On Sun, Mar 17, 2013 at 10:55 AM, Roberto Ragusa mail@robertoragusa.it wrote:
...
Thanks, Roberto. I get everything correct, likewise what you get. The problem occurs with directories that I brought in from previous Fedora installations. For example, I get the following in Thunar:
Estat�stica (invalid encoding)
yum info convmv fuse-convmvfs yum install convmv fuse-convmvfs man convmv less /usr/share/doc/fuse-convmvfs-0.2.6/README
This is the right suggestion.
Try this:
ls -l /yourdir |iconv -f iso88591 -t utf8
and check if your filenames show up ok. If not, try with cp1252 instead of iso88591.
After you have discovered your previous encoding, use the convmv command to rename the files.
Do not run convmv if you are not sure the source encoding (-f) is right, you can make things more messy than they are. Use the iconv trick to verify before running convmv.
(Let me guess, your files have been moved through a FAT filesystem, e.g. usb key?)
On Sun, Mar 17, 2013 at 5:55 PM, Roberto Ragusa mail@robertoragusa.it wrote:
Thanks, Roberto. I get everything correct, likewise what you get. The problem occurs with directories that I brought in from previous Fedora installations. For example, I get the following in Thunar:
Estat�stica (invalid encoding)
yum info convmv fuse-convmvfs yum install convmv fuse-convmvfs man convmv less /usr/share/doc/fuse-convmvfs-0.2.6/README
This is the right suggestion.
Try this:
ls -l /yourdir |iconv -f iso88591 -t utf8
and check if your filenames show up ok. If not, try with cp1252 instead of iso88591.
After you have discovered your previous encoding, use the convmv command to rename the files.
Do not run convmv if you are not sure the source encoding (-f) is right, you can make things more messy than they are. Use the iconv trick to verify before running convmv.
(Let me guess, your files have been moved through a FAT filesystem, e.g. usb key?)
Thanks for all replies. Indeed, the mentioned directory was created originally on a MS Windows machine and copied afterwards to a Linux system.
I hope to be able to convert the original filename encoding to a more Linux friendly one with convmv.
Paul
-
Paul Smith -
poma -
Roberto Ragusa -
Tim