From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 13 Oct 2011 09:20:55 -0400 To: 9fans@9fans.net Message-ID: In-Reply-To: <201110131337.48830.dexen.devries@gmail.com> References: <201110131337.48830.dexen.devries@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [9fans] ext2srv understands only 7bit ASCII file names? Topicbox-Message-UUID: 3747c888-ead7-11e9-9d60-3106f5b1d025 On Thu Oct 13 07:38:54 EDT 2011, dexen.devries@gmail.com wrote: > On Thursday 13 of October 2011 13:15:57 slash wrote: > > I have some files on an external ext2 drive that have whitespace and > > umlauts (ä, ö) in them. trfs took care of the whitespace. But ext2srv > > presents umlauts as a question mark symbol (�) and won't let me access > > the file (error: file does not exist). > > i believe -- but i am not sure! -- that linux stores and reads names on > ext2/3/4 without any conversion between filesystem and I/O syscalls like > open(). if you have iso8859-1 or similar single-byte locale on linux, your > ext2 contains iso8859-1 encoded filenames. correct. if you know what the charset on disk is, you could probablly hack ext2fs into translating names. or (less hacky) you could write a transliterating fs, or add this to trfs' duties. i don't know if this i helpful, but if you use p9p tools you will always get utf8, without any oddness. it used to be easier because the system tools weren't trying so hard to break utf-8. it used to just all work. ymmv with a utf-8 locale. i found it messed up some scripts because the beauty of locale is that you just can't count on the format of anything. - erik