On Jan 5, 2008, at 8:14 AM, Jacek Laskowski wrote:
On Jan 5, 2008 1:20 PM, Daniel S. Haischt <[EMAIL PROTECTED]
> wrote:
Again I think this is a pure Eclipse issue if not reported different
by someone else who tries to open the files in IntelliJ for example
and experiences the same exact issue.
I'm working with Eclipse, NetBeans and IntelliJ recently and none's
reported troubles opening the files so I think you're right. Thanks
Daniel for the report as I wouldn't figure that out myself.
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.
Regardless, even if we can explain it that doesn't make it gone, it
still needs to be fixed. The only fix I see is to yank the keywords
if svn is going mix character encodings on us. Could be just
TortiseSVN, but still.
Any other thoughts or proposed solutions?
-David
