<div dir="ltr">Well .. theoretically you could use UTF-8 BOM to mark UTF-8 files on per-document basis. But implementing detection of this into existing clients is of course not always an option. In my opinion - using UTF-8 as default encoding is good compromise. RFC compliant clients will still work and english only text will be displayed as expected. For other languages having an option to display accented characters in some clients (UTF-8 enabled ones) is still better than not being able to display them at all.<div><br></div><div>cheers</div><div>Matjaz</div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-03 12:13 GMT+01:00 Mateusz Viste <span dir="ltr"><<a href="mailto:mateusz@viste.fr" target="_blank">mateusz@viste.fr</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 01/03/2015 11:46 AM, James Mills wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Or does a Client query a Gopherd for CAPS<br>
and if it sees "Encoding: utf-8" assumes *all*<br>
content it receives from *that* Gopherd is<br>
encoded in UTF-8?<br>
</blockquote>
<br></span>
That's what I was suggesting, yes.<br>
<br>
One could argue that a single server might contain a plethora of documents, each of which would be encoded in a specific charset, and that's certainly a possibility. But in practice, I have always seen servers saying (in human language, mainly on their root page) "this server is serving content in utf-8", and rarely or never "this specific document is encoded in xyz".<br>
<br>
But still, the CAPS capability I was suggesting was about a "default" encoding, that is, "if not specified otherwise, assume everything on this server is encoded in this encoding". That way, if one day there is a mechanism that allows to specify the charset on a per-document basis, both won't collide (although I doubt such specific mechanism will appear, but of course one can never be sure of the future).<br>
<br>
Currently, gopher clients are supposed to assume ISO Latin 1, as per RFC 1436. The ServerDefaultCharset CAPS setting I was suggesting in my message from 31st of December, 2014, was simply a way to overload that RFC charset.<br>
<br>
Mateusz<br>
<br>
<br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
On Sat, Jan 3, 2015 at 8:38 PM, Mateusz Viste <<a href="mailto:mateusz@viste.fr" target="_blank">mateusz@viste.fr</a><br></span><span class="">
<mailto:<a href="mailto:mateusz@viste.fr" target="_blank">mateusz@viste.fr</a>>> wrote:<br>
<br>
On 01/03/2015 11:27 AM, James Mills wrote:<br>
<br>
Mis-rendered correct (which is what I meant)<br>
but the client "won't break".<br>
<br>
<br>
That's correct.<br>
<br>
What's what I meant by "degrade".<br>
<br>
<br>
Sure, but that's hardly 'graceful'. And doesn't have anything to do<br>
with ISO-8859-1. Which doesn't mean I am opposed to UTF-8 usage in<br>
the gopherspace, on the contrary, I'm 100% for it. But it's<br>
important to keep in mind the exact impact it will have on legacy<br>
clients.<br>
<br>
*I think* a Gopher server that splits out UTF_8 encoded data to<br>
a Client<br>
that doesn't support UTF-8 encoding will still display the<br>
content (just<br>
not any codepoint higher than 255)?<br>
<br>
<br>
Only low-ascii will be rendered correctly, that is anything above<br>
code point 127 will be scrambled.<br>
<br>
Here's an example:<br>
<br></span>
gopher://<a href="http://gopher.viste.fr/0/__docs/other/Little%2520Big%__2520Adventure%2520-%__2520Soluce%2520du%2520jeu%__2520%2528french%2529.txt" target="_blank">gopher.viste.fr/0/__<u></u>docs/other/Little%2520Big%__<u></u>2520Adventure%2520-%__<u></u>2520Soluce%2520du%2520jeu%__<u></u>2520%2528french%2529.txt</a><br>
<<a href="http://gopher.viste.fr/0/docs/other/Little%2520Big%2520Adventure%2520-%2520Soluce%2520du%2520jeu%2520%2528french%2529.txt" target="_blank">http://gopher.viste.fr/0/<u></u>docs/other/Little%2520Big%<u></u>2520Adventure%2520-%<u></u>2520Soluce%2520du%2520jeu%<u></u>2520%2528french%2529.txt</a>><span class=""><br>
<br>
Same thing here (but on a polish document):<br>
<br></span>
gopher://<a href="http://gopher.viste.fr/0/__docs/opowiadania%2520%__2528polish%2529/sendbajt.txt" target="_blank">gopher.viste.fr/0/__<u></u>docs/opowiadania%2520%__<u></u>2528polish%2529/sendbajt.txt</a><br>
<<a href="http://gopher.viste.fr/0/docs/opowiadania%2520%2528polish%2529/sendbajt.txt" target="_blank">http://gopher.viste.fr/0/<u></u>docs/opowiadania%2520%<u></u>2528polish%2529/sendbajt.txt</a>><span class=""><br>
<br>
When I open these documents with Overbite, all french or polish<br>
diacritics are broken (until I set my browser manually to UTF-8).<br>
<br>
Of course there are thousands of such examples across the gopherspace.<br>
<br>
Mateusz<br>
<br>
<br></span><span class="">
______________________________<u></u>___________________<br>
Gopher-Project mailing list<br>
Gopher-Project@lists.alioth.__<a href="http://debian.org" target="_blank"><u></u>debian.org</a><br>
<mailto:<a href="mailto:Gopher-Project@lists.alioth.debian.org" target="_blank">Gopher-Project@lists.<u></u>alioth.debian.org</a>><br>
<a href="http://lists.alioth.debian." target="_blank">http://lists.alioth.debian.</a>__<u></u>org/cgi-bin/mailman/listinfo/_<u></u>_gopher-project<br>
<<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.<u></u>org/cgi-bin/mailman/listinfo/<u></u>gopher-project</a>><br>
<br>
<br>
<br>
<br></span><span class="">
______________________________<u></u>_________________<br>
Gopher-Project mailing list<br>
<a href="mailto:Gopher-Project@lists.alioth.debian.org" target="_blank">Gopher-Project@lists.alioth.<u></u>debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.<u></u>org/cgi-bin/mailman/listinfo/<u></u>gopher-project</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<u></u>_________________<br>
Gopher-Project mailing list<br>
<a href="mailto:Gopher-Project@lists.alioth.debian.org" target="_blank">Gopher-Project@lists.alioth.<u></u>debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.<u></u>org/cgi-bin/mailman/listinfo/<u></u>gopher-project</a><br>
</div></div></blockquote></div><br></div>