From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <6f11ef4bee3c85f037f0f21e5a06d478@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Acme Edit/tcs and different character sets
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri,  7 Sep 2007 13:04:34 -0400
In-Reply-To: <7359f0490709070930k4be2bda8o317a3b4d201c6ef1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: bb0b57ca-ead2-11e9-9d60-3106f5b1d025

> Acme treats all text as UTF-8. If the input text was ms-kanji, it won't
> be UTF-8 and when acme reads it, it will end up full of encoding errors
> - represented in UTF-8. Running that UTF-8 text back through
> tcs -f ms-kanji will produce gibberish.
>
> You need to use tcs on the raw files before putting them into the editor
> (or almost any other Plan 9 tool).
>
> -rob

one of the best decisions made in plan 9 is to have
one character set.  there are a few downsides, but
plan 9 doesn't need locals and the tools may be ignorant
of other character sets.

gnu grep is a good example of why locals are a bad idea.

- erik