Character Encoding URIs
If a URI constructed by mlcp contains special characters that are not allowed in URIs, mlcp automatically encodes them. This applies to the special characters <space>, %, ? or #. For example, foo bar.xml becomes foo%20bar.xml.
If you supply a URI or URI component, you are responsible for ensuring the result is a legitimate URI. No automatic encoding takes place. This applies to -output_uri_replace, -output_uri_prefix, and -output_uri_suffix. The changes implied by these options are applied after mlcp encodes the default URI.
When mlcp exports documents from the database to the file system such that the output directory and/or file names are derived from the document URI, the special symbols are decoded. That is, foo%bar.xml becomes foo bar.xml when exported. For details, see How URI Decoding Affects Output File Names.