Date: Sat, 21 Apr 2012 09:10:03 -0500 (CDT) From: Lars Eighner <lars@larseighner.com> To: =?ISO-8859-15?Q?Erik_N=F8rgaard?= <norgaard@locolomo.org> Cc: freebsd-questions@freebsd.org Subject: Re: converting UTF-8 to HTML Message-ID: <alpine.BSF.2.00.1204210909450.5338@abbf.6qbyyneqvnyhc.pbz> In-Reply-To: <4F9278A2.1020301@locolomo.org> References: <20120421055823.GA6788@tinyCurrent> <4F9253D7.7010609@locolomo.org> <4F9278A2.1020301@locolomo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --21774345-667095436-1335017363=:5338 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sat, 21 Apr 2012, Erik N=F8rgaard wrote: > When characters show up wrong in the users browser it's usually because t= he=20 > browser is set to use a non-UTF-8 charset by default such as windows-1252= ,=20 > the web server sends the charset=3Dascii in the http header and there is = no or=20 > incorrect meta tag to resolve the problem. Non UTF-8 charsets are a lefto= ver=20 > from last millenia that we sometimes still choke on .. sorry the rant ;) UTF-8 is a waste of storage for most people and is incompatiple with text-mode tools: it's simple another bid to make it impossible to run without a GUI. --=20 Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 --21774345-667095436-1335017363=:5338--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1204210909450.5338>