#169 Internationalization checks

Check (274)
Ed Burnette

It would be nice if the tool would check for
interntionalization violations such as:

  • use of string literals
  • use of character constants
  • string concatenation
  • unsafe methods like Date.toString()
  • locale sensitive methods

Comments like //$NON-NLS-1$
(that's one used by Eclipse) could be added to supress
the violations on a line by line (or string-by-string) basis
for those cases where it's ok to do what you're doing (for
example strings that shouldn't be in a properties file).


  • Tony

    Tony - 2008-02-19

    Logged In: YES
    Originator: NO

    It would be nice to also check the usage of encodings (which ties in with internationalization, although this might be better as a separate check)

    It would be nice to check:
    - use of String.toBytes() or new String(byte[]), without specifying an encoding
    - use of a Reader/Writer without specifying an encoding
    - use of Properties.load(inputStream) rather than reader, as the former uses a fixed encoding (not the default)

    It would be useful to be able to specify the encoding that should be used in these methods too.

  • Roman Ivanov

    Roman Ivanov - 2015-10-22
    • status: open --> closed
    • Group: --> Future

Log in to post a comment.