Timeline for How to use Special Chars in Java/Eclipse
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2013 at 9:51 | comment | added | Piotr Findeisen | +1; To avoid looking up each character's code point, one can use AnyEdit eclipse plugin. See my answer for details. | |
| Feb 3, 2012 at 15:05 | comment | added | Shishir Shetty | You are just plain Awesome dude | |
| Nov 17, 2008 at 20:37 | vote | accept | Burkhard | ||
| Oct 14, 2008 at 21:05 | history | edited | Joe Lencioni | CC BY-SA 2.5 | added list of requested unicode escape sequences |
| Oct 14, 2008 at 13:12 | comment | added | McDowell | Java source files are treated as the OS encoding by default (some 8bit CP on Windows; UTF8 on Linux). Not writing ASCII means you need to ensure that devs know about it before they compile and risks introducing bugs if they do not. I18N stuff should be in properties files (UTF8 by definition). | |
| Oct 14, 2008 at 12:02 | comment | added | Cowan | I would argue that the first option is preferable because anyone who uses any encoding other than UTF-8 (certainly anyone who uses a country-specific encoding) for their source files needs help. :) | |
| Oct 14, 2008 at 11:03 | comment | added | McDowell | I would argue that the second option is preferable because it makes the file more portable between different source encodings. It depends where the characters are of course (String literals? Comments? READMEs?). | |
| Oct 14, 2008 at 10:49 | history | answered | Joe Lencioni | CC BY-SA 2.5 |