<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On 12 Jul 2015, at 20:39, Mateusz Viste <<a href="mailto:mateusz@viste.fr" class="">mateusz@viste.fr</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class="">On 12/07/2015 17:06, Cameron Kaiser wrote:<br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""> - New CAPS token: 'ServerDefaultEncoding',<br class=""></blockquote><br class="">What is the value set for this?<br class=""></blockquote><br class="">I think it all started with my question/suggestion on the list, in late 2014:<br class=""><br class=""><a href="http://comments.gmane.org/gmane.network.gopher.general/4929" class="">http://comments.gmane.org/gmane.network.gopher.general/4929</a><br class=""></div></blockquote><div><br class=""></div><div>Yep, I think that was it - the date matches my git commit:</div><div><br class=""></div><div><div>commit 6e9f108ac19d1791e4fa4a5e9f95bc4c730703b3</div><div>Author: Kim Holviala <<a href="mailto:kim@holviala.com" class="">kim@holviala.com</a>></div><div>Date: Sun Jan 4 08:42:11 2015 +0200</div><div><br class=""></div><div> Added ServerDefaultEncoding to automatic caps.txt</div></div><div><br class=""></div><blockquote type="cite" class=""><div class="">I actually implemented it in Motsognir back then as "ServerDefaultCharset", but haven't released publicly. Then, Kim implemented a slightly different variant named "ServerDefaultEncoding", so I adapted Motsognir to avoid having too many different gopher implementations in the wild.<br class=""></div></blockquote><div><br class=""></div><div>I’m willing to change that if needed, but to be honest both of the above are just fine.</div><div><br class=""></div><div>Mine’s better, though :D</div><br class=""><blockquote type="cite" class=""><div class="">Personally I use "UTF-8" as the value (as is Kim, apparently). I think a good rule would be to expect the same things that can be present in a content-encoding 'charset' HTTP header.<br class=""></div></blockquote><div><br class=""></div><div>My install of Gophernicus has been configured to convert all text to US-ASCII on the fly so the client should never see anything else - hence my use of US-ASCII as the default encoding in caps.txt.</div><div><br class=""></div><div><br class=""></div><div><br class=""></div><div>- Kim</div><div><br class=""></div></div></body></html>