I have bought a new computer. When I connect an USB harddisk formatted with the ext4 filesystem to it all accentuated characters in filenames turn up as question marks (?). The filenames show up correctly on the old computer. Is there any option I can add to /etc/fstab in order to make the filenames to show up correctly?
It is not very likely that this has anything to do with the age of the computer. It most probaly depends on the software used. Thus please tell us what version of openSUSE yoy are running on both systems. And also which desktop you are using.
On 2013-08-08 18:06, Per 68 wrote:
>
> I have bought a new computer. When I connect an USB harddisk formatted
> with the ext4 filesystem to it all accentuated characters in filenames
> turn up as question marks (?). The filenames show up correctly on the
> old computer. Is there any option I can add to /etc/fstab in order to
> make the filenames to show up correctly?
What is running on that new computer?
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
The most likely cause is that the older computer was using a different default character set from the newer one. If this is the case, you may have to edit them manually.
I found a utility called convmv that does the conversions automatically for me. It only takes care of the filenames and not the contents of the files. Luckily I don’t seem to have any text files with accentuated characters in them. Another way to fix the problem would be to mount the hard drive on the old computer, make a tarball of the entire drive and untar it on the new computer. Unfortunately there’s not enough room on the hard drive to have both the files and the tar file. My old computer uses iso-8859-15 and my new computer uses UTF-8. I was hoping for a mount option like iocharset/codepage that’s available for FAT filesystems.
For that you have to read
man mount
I did a short glance through it, but the iocharset= parameter does not show up for ext2/3/4 file systems. But I guess you can read that yourself.
On 2013-08-10 09:56, hcvv wrote:
>
> I did a short glance through it, but the iocharset= parameter does not
> show up for ext2/3/4 file systems. But I guess you can read that
> yourself.
Unless he is not really using ext4, or the old computer system was
compiled differently :-??
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Linux is (of course) smarter than me… I only had to change locale from sv_SE.UTF8 to sv_SE. A day you learn something new is a good day.
Well, that may help for the moment, but keeping stuck at non UTF-8 is not a good idea for a future that is already there IMHO.
On 2013-08-10 19:16, Per 68 wrote:
>
> Linux is (of course) smarter than me… I only had to change locale from
> sv_SE.UTF8 to sv_SE. A day you learn something new is a good day.
That can be very problematic, openSUSE is designed to use UTF-8.
You said that tarring the files on the old computer, untarring on the
new, would work, but that you don’t have the space. But you could
transfer from one computer to another across the network, perhaps with
NTFS, or via ssh with fish in konqueror or midnight commander.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)