From: slash <slash.9fans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ext2srv understands only 7bit ASCII file names?
Date: Thu, 13 Oct 2011 10:28:33 -0400 [thread overview]
Message-ID: <CAEaiYYx=tOjWiQnAhxUWsAdaSDQOyKrCRaCHYJ3=d3gGqBdnhw@mail.gmail.com> (raw)
In-Reply-To: <bc8908d972fc7e53949ad90a7a0388fd@chula.quanstro.net>
> 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.
Thank you. So now I know ext2srv is not doing any file name conversion. Good.
Say I wanted to add the following capability to trfs: convert latin-1
ä and ö into their utf equivalents. I guess I would just follow the
example of whitespace handling etc in trfs.c and recompile. Now, where
is the latin-1 code table again...
next prev parent reply other threads:[~2011-10-13 14:28 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
2011-10-13 14:28 ` slash [this message]
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='CAEaiYYx=tOjWiQnAhxUWsAdaSDQOyKrCRaCHYJ3=d3gGqBdnhw@mail.gmail.com' \
--to=slash.9fans@gmail.com \
--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).