From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ext2srv understands only 7bit ASCII file names?
Date: Thu, 13 Oct 2011 09:20:55 -0400 [thread overview]
Message-ID: <bc8908d972fc7e53949ad90a7a0388fd@chula.quanstro.net> (raw)
In-Reply-To: <201110131337.48830.dexen.devries@gmail.com>
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
next prev parent reply other threads:[~2011-10-13 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 11:15 slash
2011-10-13 11:37 ` dexen deVries
2011-10-13 13:20 ` erik quanstrom [this message]
2011-10-13 14:28 ` slash
2011-10-13 15:20 ` Russ Cox
2011-10-13 15:25 ` slash.9fans
2011-10-13 15:30 ` erik quanstrom
2011-10-16 13:19 ` slash
2011-10-13 13:22 ` Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bc8908d972fc7e53949ad90a7a0388fd@chula.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).