Message-ID: <443225BB.5030806@route-add.net>
Date: Tue, 04 Apr 2006 09:52:27 +0200
From: Alessandro Selli <dhatarattha@route-add.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.0.1) Gecko/20060201 SeaMonkey/1.0
MIME-Version: 1.0
To: gopher@complete.org
Subject: [gopher] Re: Handling of ISO-8859-* character sets
References: <442FB7C2.8000004@route-add.net>
 <20060403220315.M96004@aaronjangel.us>
In-Reply-To: <20060403220315.M96004@aaronjangel.us>
Content-type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

Aaron J. Angel wrote:
> 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.

   I take this implies that a Gopher menu is to be considered a selector.


-- 
Alessandro Selli
Tel: 340.839.73.05
http://alessandro.route-add.net