From: "Gopher-Project" <gopher-project-bounces+rachael=telefisk.org@lists.alioth.debian.org> Date: Sat Jan 3 12:34:34 2015 Subject: Re: [gopher] GopherMole - a gopher media crawler --===============0804871178372251304== Content-Type: multipart/alternative; boundary=20cf30266982f095a7050bbdd410 --20cf30266982f095a7050bbdd410 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, Jan 3, 2015 at 9:29 PM, Matja=C5=BE Me=C5=A1njak <matjaz85@gmail.co= m> wrote: > 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 wor= k > 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. > 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? cheers James James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au --20cf30266982f095a7050bbdd410 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">= On Sat, Jan 3, 2015 at 9:29 PM, Matja=C5=BE Me=C5=A1njak <span dir=3D"ltr">= <<a href=3D"mailto:matjaz85@gmail.com" target=3D"_blank">matjaz85@gmail.= com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar= gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"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 enc= oding is good compromise. RFC compliant clients will still work and english= only text will be displayed as expected. For other languages having an opt= ion to display accented characters in some clients (UTF-8 enabled ones) is = still better than not being able to display them at all.<div></div></div></= blockquote></div><br>Well a Gopherd could use the BOM marker right?</div><d= iv class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">This way a Go= pherd could read the file, decode it</div><div class=3D"gmail_extra">and re= encode using the DefaultEncoding CAPS configuration?</div><div class=3D"gma= il_extra"><br></div><div class=3D"gmail_extra">cheers</div><div class=3D"gm= ail_extra">James<br><br clear=3D"all"><div><div class=3D"gmail_signature"><= span style=3D"border-collapse:collapse;color:rgb(136,136,136);font-size:13p= x"><br><font face=3D"arial, sans-serif">James Mills / prologic</font><br><b= r><font face=3D"arial, sans-serif"></font><font face=3D"'courier new= 9;, monospace">E:=C2=A0<a href=3D"mailto:prologic@shortcircuit.net.au" styl= e=3D"color:rgb(0,0,204)" target=3D"_blank">prologic@shortcircuit.net.au</a>= </font></span><div><span style=3D"font-family:'courier new',monospa= ce;color:rgb(136,136,136);font-size:13px">W:=C2=A0</span><a href=3D"http://= prologic.shortcircuit.net.au" style=3D"font-family:'courier new',mo= nospace;font-size:13px;color:rgb(0,0,204)" target=3D"_blank">prologic.short= circuit.net.au</a><br></div></div></div> </div></div> --20cf30266982f095a7050bbdd410-- --===============0804871178372251304== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project --===============0804871178372251304==-- (DIR) Followup: Re: [gopher] GopherMole - a gopher media crawler