Hi,
On Mar 24, 2010, at 10:45 AM, Antoine Toulme wrote:
It looks ok to me here:
http://github.com/apache/buildr/blob/trunk/CHANGELOG
I also see the character correctly in Textmate.
Where and how do you see this problem ?
I see it on http://buildr.apache.org/CHANGELOG .
It looks like the file is UTF-8 encoded, but that server is ending it
without the charset parameter on content-type:
$ curl -I http://buildr.apache.org/CHANGELOG
HTTP/1.1 200 OK
Date: Wed, 24 Mar 2010 15:48:12 GMT
Server: Apache/2.2.12 (Unix) mod_ssl/2.2.12 OpenSSL/0.9.7d mod_wsgi/
3.2 Python/2.6.5rc2
Last-Modified: Tue, 08 Dec 2009 22:54:40 GMT
ETag: "2180f9b-db49-47a3f7584ac00"
Accept-Ranges: bytes
Content-Length: 56137
Content-Type: text/plain
The default charset for HTTP is ISO-8859-1 (RFC2068, section 3.7.1),
so a browser is going to misinterpret any high-bit / multibyte
characters. I presume this would have to be fixed by configuring
apache. I don't know if you can do charset overrides using .htaccess
(or if apache.org even allows that).
Rhett
Thanks!
Antoine
On Wed, Mar 24, 2010 at 02:14, Peter Schröder <[email protected]> wrote:
just a sidenote, the changelog (http://buildr.apache.org/CHANGELOG)
has an
encoding issue :-)
"Peter Schröder" --> thats not my name!
