offapi/com/sun/star/util/XStringEscape.idl 1.8: "Strings that already conform to
the naming conventions should be left unchanged or minimally modified."

This documentation is confusing at best, and leads to broken functionality in
the worst case.  Assume that some escaping scheme is to escape "/" as "//" and
leave all other characters unchanged.  If, under that scheme, the documentation
is interpreted in a way that escapeString("//")="//" instead of
escapeString("//")="////", then escapeString cannot be used in general, as it
would map the different inputs "/" and "//" to the same output ("//").

When fixing the documentation, also check whether there are any implementations
of XStringEscape in the OOo code base that are broken.