Re: [gopher] CAPS capability: ServerDefaultCharset

[Mateusz Viste <mateusz@viste.fr>]

Fine for me. I was liking the 'ServerDefaultCharset' term, as it's more 
generic (the client doesn't have to know whether any 'encoding' takes 
place or not, just the end result matters), but the token's name is so 
slight a detail that I am fine with anything.

Mateusz



On 01/04/2015 01:34 AM, James Mills wrote:
> On Sun, Jan 4, 2015 at 10:12 AM, Cameron Kaiser <spectre@floodgap.com
> <mailto:spectre@floodgap.com>> wrote:
>
>     I think this is a very sound proposal and I would be willing to
>     support it.
>
>
> Can we call the parameter ServerDefaultEncoding though?
> It is the "encoding" the server uses to "encode" the data.
> Not necessarily the charset of the original data.
>
> cheers
> James
>
>
> James Mills / prologic
>
> E: prologic@shortcircuit.net.au <mailto:prologic@shortcircuit.net.au>
> W: prologic.shortcircuit.net.au <http://prologic.shortcircuit.net.au>
>
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project

_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project