From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <bc8908d972fc7e53949ad90a7a0388fd@chula.quanstro.net>
References: <CAEaiYYwJXaF6JApbYXg5nGBuy2ArDBCbgPYW9cmNu176n4f1qQ@mail.gmail.com>
	<201110131337.48830.dexen.devries@gmail.com>
	<bc8908d972fc7e53949ad90a7a0388fd@chula.quanstro.net>
Date: Thu, 13 Oct 2011 10:28:33 -0400
Message-ID: <CAEaiYYx=tOjWiQnAhxUWsAdaSDQOyKrCRaCHYJ3=d3gGqBdnhw@mail.gmail.com>
From: slash <slash.9fans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] ext2srv understands only 7bit ASCII file names?
Topicbox-Message-UUID: 37636e1c-ead7-11e9-9d60-3106f5b1d025

> if you know what the charset on disk is, you could probablly hack ext2fs
> into translating names. =A0or (less hacky) you could write a transliterat=
ing fs,
> or add this to trfs' duties.

Thank you. So now I know ext2srv is not doing any file name conversion. Goo=
d.

Say I wanted to add the following capability to trfs: convert latin-1
=E4 and =F6 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...