Complete.Org: Mailing Lists: Archives: gopher: April 2006:
[gopher] Re: Handling of ISO-8859-* character sets

[gopher] Re: Handling of ISO-8859-* character sets

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Handling of ISO-8859-* character sets
From: "Aaron J. Angel" <thatoneguy@xxxxxxxxxxxxxx>
Date: Mon, 3 Apr 2006 17:06:29 -0500
Reply-to: gopher@xxxxxxxxxxxx

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@xxxxxxxxxxxxxx>
Tel: +1 270 339 3759

[Prev in Thread] Current Thread [Next in Thread]