Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Suppose a Spanish team-mate writes a class with like TipoNotificación. Note the special characters like ú, ó, etc.
Beyond the coding project normalization, what kind of troubles could I face?
That should be a reason enough to exclude non-ascii characters in identifiers:
As for your original question, I don’t think there’s any significant overhead. As already stated, strings are internally stored in UTF-16. However filenames (including class filenames) in JAR files are encoded in UTF-8, which means the JVM reads one extra byte for each non-ascii character at load time. Since Spanish has at most one diacritic per word, you can expect an average of one or two additional bytes per class. There’s no way you could notice it even in the most limited hardware environments.