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.
See:
http://www.ryanlowe.ca/blog/archives/001328_default_file_encoding_issues.php
He had the same issue - which is files checked into the SCM are NOT
UTF-8 encoded but on Linux the default encoding for Eclipse is UTF-8
and thus Eclipse tries to open them as UTF-8 encoded files.
This yields a -> Syntax error on token "Invalid Character"
If I interpreter Mohammad correct, he tries to execute javac from within
Eclipse and I think cause Eclipse uses the UTF-8 encoding on Linux, the
encoding being used by javac is forced to UTF-8 as well. Thus the error.
Thoughts ?
David Blevins wrote:
On Jan 2, 2008, at 12:04 PM, Dain Sundstrom wrote:
On Dec 31, 2007, at 3:19 PM, David Blevins wrote:
On Dec 31, 2007, at 11:56 AM, Mohammad Nour El-Din wrote:
Hi Folks...
I've just checked out the latest code, used the eclipse mavne plugin to
import the src code as Eclipse projects, surprised that most some
projects
are not built successfully because of some java files which could
not be
read in UTF-8 character encoding mode, I solved the problem by
opening and
Saving as the files in the UTF-8 character encoding, but I need some
explanation here y that happened and why not with all files ???
Someone complained about this recently as well.
http://www.nabble.com/RE%3A-newbie-questions-p14294655.html
From the description in that email it seems like setting the
"svn:keywords" on the files has lead to encoding issues.
I don't know if there's a way to keep the svn:keywords and avoid the
encoding issues.
I'm not a big fan of the keywords anyway, so if you want to drop them,
I'm for it.
I'd prefer to give Jacek a chance to resolve the encoding issue before
we yank them. Jacek, you have any idea what's going on?
-David
