On Jan 5, 2008 10:59 PM, David Blevins <[EMAIL PROTECTED]> wrote: > I don't think it's it. The user complained that his *maven* build > failed and that he had non-UTF8 characters in the part where svn > substitutes the keywords. The xml files clearly state > encoding="UTF-8" and his svn client is adding non-UTF8 characters when > it edits the file while adding the keywords making it unparsable, I'd > guess, by any valid xml parser who listens to the 'encoding' attribute.
Yes, you're right. I remember it was with bg_BG locale when an xml file with UTF-8 contained some unparsable letters. How could it be that svn changes the keywords that other projects don't sufer from it too? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
