FreeBSD refuses to mount ext2 partitions with the iocharset=utf8 and utf8 options. The consequence are not only wrongly displayed file names. It causes difficulties accessing files: f.i. VLC media player refuses to open such files.
Responsible Changed From-To: freebsd-bugs->freebsd-fs Over to maintainer(s).
On 2009-02-16, Elmar Stellnberger wrote: > >Class: sw-bug > FreeBSD refuses to mount ext2 partitions with the iocharset=utf8 and > utf8 options. The consequence are not only wrongly displayed file > names. I don't think this is a bug. For me FreeBSD ext2fs works fine with UTF-8 encoded file names providing that you have configured locale settings correctly. Do you expect "iocharset=utf8" and "utf8" mount options to convert file names to some other encoding? AFAIK even Linux doesn't support such options for ext2. -- Jaakko
Basically I would expect the utf8 file system option to convert from utf8 to whatever charset is selected by default at the moment. I will have to have another look on how to enable utf8 on FreeBSD. Previously consulted web resources have not worked as expected. Nevertheless if enabling utf8 as default charset is all I need to do in order to view and access these files correctly that should be fine for me. thx for any further hint. On 2009-02-16, Elmar Stellnberger wrote: >> > >Class: sw-bug >> > > FreeBSD refuses to mount ext2 partitions with the iocharset=utf8 and > > utf8 options. The consequence are not only wrongly displayed file > > names. > I don't think this is a bug. For me FreeBSD ext2fs works fine with UTF-8 encoded file names providing that you have configured locale settings correctly. Do you expect "iocharset=utf8" and "utf8" mount options to convert file names to some other encoding? AFAIK even Linux doesn't support such options for ext2. -- Jaakko
Interestingly LC_ALL=en_US.UTF-8 works well with xterm, but with xterm only. All other apps from the ports tree like VLC or any KDE app like konsole or konqueror do not support utf-8. Perhaps we should reassign this bug to the ports project. Or do you think about a kernel charset conversion for filenames(iocharset=utf8) as an additional option? Jaakko Heinonen wrote: > On 2009-02-16, Elmar Stellnberger wrote: > >>> Class: sw-bug >>> > > >> FreeBSD refuses to mount ext2 partitions with the iocharset=utf8 and >> utf8 options. The consequence are not only wrongly displayed file >> names. >> > > I don't think this is a bug. For me FreeBSD ext2fs works fine with UTF-8 > encoded file names providing that you have configured locale settings > correctly. > > Do you expect "iocharset=utf8" and "utf8" mount options to convert > file names to some other encoding? AFAIK even Linux doesn't support such > options for ext2. > >
State Changed From-To: open->closed Close, this was a misconfiguration rather than a bug.