[gopher] Gopher RFC propositions

[Damien Carol]

Bradley said right.

The RFC 1436 define a grammar for '0' type transactions.

In this grammar you can see that all data given by the server must be
US-ASCII (without <CR><LF>)

Data given for Menu '1' items are the same.

In fact, RFC stay close to US-ASCII. There no UTF-8 or Latin-1 in gopher
1.0 RFC.

2012/5/18 Kim Holviala <kim at holviala.com>

> On Fri, 18 May 2012, 13:54:29 EEST, Bradley D. Thornton
> <Bradley at NorthTech.US> wrote:
>
> > > * what do about teh US-ASCII vs. Latin-1 vs. UTF-8 issue?
> >
> > I found this here:
> http://man7.org/linux/man-pages/man7/url.7.html#gopher
> >
> > selector is the Gopher selector string.   In the Gopher protocol, Gopher
> > selector strings are a sequence of octets which may contain any octets
> > except 09 hexadecimal (US-ASCII HT or tab), 0A hexadecimal (US-ASCII
> > character LF), and 0D (US-ASCII character CR).
>
> The selector is not a human-readable string, nor something that usually
> has to be typed. Hence - no one really cares.
>
> What I was talking about was content - browser-visible strings in menus
> and the actual content type 0 docs.
>
> - Kim
>
>
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>



-- 
Damien CAROL
gopher://dams.zapto.org/1/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/gopher-project/attachments/20120518/a8cbca95/attachment.html>