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>
MIME-Version: 1.0
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

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