Since the mapserver parser changes the double backslashes to a single slash the reverse operation should take place when writing the mapfile. Currently if we do subsequent load and write operations on the same mapfile we may get invalid file locatons in the mapfiles.
For exampe if we have "\myserver\myshare\Maps\myfile.shp" in the DATA section loading and then saving the file will results: "\myserver\myshare\Maps\myfile.shp". When loading the map back again we will get "\myserver\myshare\Maps\myfile.shp" which is an invalid file location causing run time issues.
I think backslashes should be replaced with double backslashes every time when saving the file at least in the CONNECTION, DATA, SHAPEPATH, FONTSET, SYMBOLSET sections.
escape backslashes in mapfile string writer (#4747)
Looks like we require similar handling for the CONFIG section (writeHashTableInline). Some config options mas also contain filenames with backslashes which should also be escaped.
Escape backslashes in the mapfile string writer (#4747)