Fileinstall 3.5.0 added handling of .config file with an expanded syntax for configuration files allowing proper handling of arrays, etc. A great feature.
There is one thing that appears to be handled improperly though - if the values in the key/value pairs have spaces in them, the files are written back with backslash escapes for the spaces.
What is the justification for that?
The effect is that the file is different from the original - which is quite a pain for automated installation with files generated from templates. The fake changes become a maintenance nightmare.
It appears that escaping of spaces can be harmlessly removed, and perhaps should not be a part of the feature...