Re: Rss produced by git is not valid xml?

From: Josef Weidendorfer <josef.weidendorfer@gmx.de>
Date: Nov 18, 2005, 20:51 UTC
Message-ID: <200511182151.56161.Josef.Weidendorfer@gmx.de>
In-Reply-To: <437E3971.3060803@zytor.com>

On Friday 18 November 2005 21:28, H. Peter Anvin wrote:

Show 12 quoted lines

> I think the point is: what do you do with the data?  If it *looks* like 
> valid UTF-8, you pretty much have to assume it is; if it's not (it 
> contains invalid UTF-8 sequences), what do you do?  There are only a 
> small handful of alternatives, and none are really good:
> 
> 	- Reject it (it's kind of too late, should have been done at
> 	  checkin)
> 	- Show them as SUBSTITUTE characters (U+FFFD).
> 	- Show them as Latin-1 or Windows-1252
> 	- Provide a complex configuration mechanism
> 
> I think Kay is going with the second option.

In the case of the Linux kernel, UTF-8 of course is the way to go. As you can not reject already commited objects, the second option seems the best way.

But I think it would be better to have a config option specifying the prefered encoding for commit comments in a project. Something like

	core.commit-encoding = Latin-1

gitweb should use this.

Josef