jtlocalize should validate .strings file format and warn about errors #2
Description
Currently, if there's a problem in a .strings file, like illegal character for encoding, or entries that aren't in the "key" = "value"; format, it will simply be ignored.
The reason is that we use a regular expression to extract all entries, but simply ignore all the entries which don't match the regex.
This can be a big pain when working with translators, who sometimes make mistakes (such as not closing quotation, forgetting a semicolon, etc.)
Expected behavior is that we'll log a warning about bad entries in the file or illegal characters.