Sebb, On 9/26/13 1:13 PM, sebb wrote: > On 25 September 2013 17:02, Konstantin Preißer <kpreis...@apache.org> wrote: >> Mark, >> >>> -----Original Message----- >>> From: Mark Thomas [mailto:ma...@apache.org] >>> Sent: Wednesday, September 25, 2013 5:54 PM >> >>> I'd say yes. Property files are a 'special' case: >>> http://stackoverflow.com/questions/4659929/how-to-use-utf-8-in- >>> resource-properties-with-resourcebundle >> >> OK, thank you for the clarification. >> >>> It doesn't bother me but I'm only one committer. I think this falls >>> under the category if someone cares enough about the commit e-mails >>> using UTF-8 then they need to work with infra to make that happen. I'm >>> happy with things as they are. > > There is a property that can be used to change the encoding used by > the SVN mailer, for example: > > svn:mime-type text/xml; charset=utf-8 > > Make sure this agrees with the contents and any xml encoding attribute.
The irony of the above is that text/xml implies that the file contains an XML processing instruction (i.e. <?xml?>) which properly contains ... a character encoding attribute, making the "charset" attribute of the mime-type both superfluous and - in some cases - dangerous in cases of disagreement. I am -0 for setting mime-type for XML files to something including a character set because there's no enforcement of that character set anywhere at all. -chris
signature.asc
Description: OpenPGP digital signature
