Received: with ECARTIS (v1.0.0; list gopher); Mon, 03 Apr 2006 17:07:15 -0500 (CDT) Received: from nakhbi.aaronjangel.us ([216.154.216.13]) by glockenspiel.complete.org with esmtps (with TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (No TLS peer certificate) (Exim 4.50) id 1FQXCY-0002gE-PV for gopher@complete.org; Mon, 03 Apr 2006 17:07:14 -0500 Received: from www.aaronjangel.us (nakhbi.aaronjangel.us [127.0.0.1]) by nakhbi.aaronjangel.us (8.12.10/8.12.10) with ESMTP id k33M6Tja009858 for <gopher@complete.org>; Mon, 3 Apr 2006 18:06:29 -0400 From: "Aaron J. Angel" <thatoneguy@aaronjangel.us> To: gopher@complete.org Subject: [gopher] Re: Handling of ISO-8859-* character sets Date: Mon, 3 Apr 2006 17:06:29 -0500 Message-Id: <20060403220315.M96004@aaronjangel.us> In-Reply-To: <442FB7C2.8000004@route-add.net> References: <442FB7C2.8000004@route-add.net> X-Mailer: Open WebMail 2.40 20040816 X-OriginatingIP: 12.8.236.10 (aja) MIME-Version: 1.0 Content-type: text/plain; charset=utf-8 X-Spam-Status: No (score 0.1): FORGED_RCVD_HELO=0.05 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Mon, 03 Apr 2006 17:07:14 -0500 Content-Transfer-Encoding: 8bit X-archive-position: 1270 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: thatoneguy@aaronjangel.us Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-Id: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

On Sun, 02 Apr 2006 13:38:42 +0200, Alessandro Selli wrote > Hello, > Before I run the risk of making a fool of myself and open a bug > report that should not be opened, I need to know if someone of you > can and is willing to give me an idea on how are ISO-8859 character > sets handled in gopher menus. I think their correct display is left > to the client, the server and the protocol do not take in account > any particular character set, right? I'm wondering this because I > noticed that Seamonkey 1.0

The Gopher RFC says selector names are of type UNASCII, that is: ASCII not including tabs, CR-LFs, or NULs.

-- Aaron J. Angel <aja@aaronjangel.us> Tel: +1 270 339 3759 Web: www.aaronjangel.us