From owner-freebsd-questions@FreeBSD.ORG Sat Apr 21 14:11:01 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 684AC106566B for ; Sat, 21 Apr 2012 14:11:01 +0000 (UTC) (envelope-from lars@larseighner.com) Received: from mail.team1internet.com (mail.team1internet.com [216.110.13.10]) by mx1.freebsd.org (Postfix) with ESMTP id 43C188FC0C for ; Sat, 21 Apr 2012 14:11:01 +0000 (UTC) Received: from larseighner.com (unknown [216.110.13.86]) by mail.team1internet.com (Postfix) with SMTP id 3BF6916B4D7; Sat, 21 Apr 2012 09:10:54 -0500 (CDT) Received: by larseighner.com (nbSMTP-1.00) for uid 1001 lars@larseighner.com; Sat, 21 Apr 2012 09:10:04 -0500 (CDT) Date: Sat, 21 Apr 2012 09:10:03 -0500 (CDT) From: Lars Eighner X-X-Sender: lars@noos.6dollardialup.com To: =?ISO-8859-15?Q?Erik_N=F8rgaard?= In-Reply-To: <4F9278A2.1020301@locolomo.org> Message-ID: References: <20120421055823.GA6788@tinyCurrent> <4F9253D7.7010609@locolomo.org> <4F9278A2.1020301@locolomo.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="21774345-667095436-1335017363=:5338" Cc: freebsd-questions@freebsd.org Subject: Re: converting UTF-8 to HTML X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Apr 2012 14:11:01 -0000 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--