Mozilla (Java) .properties file support is non-conformant about translate

[okulev]

Created [attachment 13](http://bugs.locamotion.org/attachment.cgi?id=13)

Fixed escaping of .properties files

[davidfraser]

Note that Mozilla .properties files already differ from Java properties files in
the exact escaped unicode characters they support…
Mozilla supports \u or \U followed by up to 4 valid hexademical characters (it
will handle 1, 2, or 3 and stop at the first non-hexadecimal character).
The java spec requires \u followed by exactly 4 hexadecimal characters:
http://java.sun.com/docs/books/jls/second_edition/html/lexical.doc.html#100850

Also I think trying to change Mozilla’s handling of properties files is
something that should be left till after Firefox/Thunderbird 1.5 if it is done
at all…

[okulev]

Yes, Mozilla .properties already differ from Java .properties but I still think
that it’s better if Java syntax is used for output and recognized as input so
that there are no surprises when processing with other tools.

[okulev]

Created [attachment 31](http://bugs.locamotion.org/attachment.cgi?id=31)

Updated patch for CVS HEAD

This is the same patch but it applies to CVS HEAD without offsets.

[dwaynebailey]

The .properties handling as we have it is designed to manage .properties as they
are used in Mozilla. We want to conform to their idiosyncrosies not to the Java
standard. Therefore. I’m closing this bug.

If there are specific properties bugs that prevent us performing a complete
roundtrip for a Mozilla properties files then please report those as separate bugs.

There is a need to have a Java conformant .properties handling storage module so
that we can handle those correctly. I will raise a separate bug for that.

[dwaynebailey]

bug #114 deals with Java .properties conformance