Re: [gopher] CAPS capability: ServerDefaultCharset
On 01/03/2015 12:33 PM, James Mills wrote:
> Well a Gopherd could use the BOM marker right?
>
> This way a Gopherd could read the file, decode it
> and reencode using the DefaultEncoding CAPS configuration?
The idea was rather to set the CAPS ServerDefaultCharset on servers that
already serve utf-8. Ie. it doesn't change anything server-side, only
provides a way for the system administrator to let the world know that
the server provides utf-8 content by default.
Of course one could imagine a server that recodes everything on the fly,
when files are physically stored in another charset, but's that would
rather be a special feature of the server (and IMHO, an unnecessary one,
since it makes more sense to directly store the content in utf-8 anyway).
Mateusz
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Reply to: