Home » Mailing list archives » git » 2007 » July » 17

Character set for the HTML documentation

Previous thread: [PATCH 3/3] builtin-fetch: fail when fetching refs fails by Johannes Schindelin on Tuesday, July 17, 2007 - 6:50 pm. (1 message)

Next thread: Empty directories... by David Kastrup on Tuesday, July 17, 2007 - 8:13 pm. (32 messages)
[view original message]
From: H. Peter Anvin <hpa@...>
To: Junio C Hamano <junkio@...>, Git Mailing List <git@...>
Subject: Character set for the HTML documentation
Date: Tuesday, July 17, 2007 - 7:31 pm

The fact that browsers behave this way is of course a bug, but it's a

common one.  Can we switch the documentation over to UTF-8, this is 2007

after all...?


	-hpa

-
[view original message]
From: Geoff Richards <qef@...>
To: Git Mailing List <git@...>
Subject: Re: Character set for the HTML documentation
Date: Wednesday, July 18, 2007 - 1:26 am

Unfortunately, it's not a bug.  The correct thing for a browser to do is

give the 'Content-Type' HTTP header priority over the <meta> element.

It's defined in an RFC somewhere.


Best thing to do is tell Apache (or whatever) not to send the HTTP

header ("AddDefaultCharset off"), and make sure all the HTML has a

correct <meta> element specifying the encoding.


And yes, putting everything in UTF-8 unless you've got a specific reason

not to is probably going to make life simpler as well.


HTH,

   geoff

-
[view original message]
From: Junio C Hamano <gitster@...>
To: H. Peter Anvin <hpa@...>
Cc: Git Mailing List <git@...>
Subject: Re: Character set for the HTML documentation
Date: Tuesday, July 17, 2007 - 10:02 pm

By all means, yes.


I do not think we particularly wanted to use 8859-1, but nothing

in Documentation/ tells the asciidoc toolchain that the document

should come out in UTF-8 either.


-
Previous thread: [PATCH 3/3] builtin-fetch: fail when fetching refs fails by Johannes Schindelin on Tuesday, July 17, 2007 - 6:50 pm. (1 message)

Next thread: Empty directories... by David Kastrup on Tuesday, July 17, 2007 - 8:13 pm. (32 messages)