Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Apr 2012 09:10:03 -0500 (CDT)
From:      Lars Eighner <>
To:        =?ISO-8859-15?Q?Erik_N=F8rgaard?= <>
Subject:   Re: converting UTF-8 to HTML
Message-ID:  <alpine.BSF.2.00.1204210909450.5338@abbf.6qbyyneqvnyhc.pbz>
In-Reply-To: <>
References:  <20120421055823.GA6788@tinyCurrent> <> <>

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.

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=
> browser is set to use a non-UTF-8 charset by default such as windows-1252=
> 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=
> 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.

Lars Eighner
8800 N IH35 APT 1191 AUSTIN TX 78753-5266

Want to link to this message? Use this URL: <>