[mapserver-dev] Double backslashes in Windows UNC pathnames should be escaped by the mapfile writer.

[Tamas Szekeres]

Thomas,

Thanks for looking into this. I've tested your changes and it looks fine
for me. I'm not sure we should delay the release process just because of
this, beta3 is not necessarily required I think.

Best regards,

Tamas



2013/9/1 thomas bonfort <thomas.bonfort at gmail.com>

> Tamas,
> I've transformed your issue into a pull request that writes double
> backslashes when a backslash is found. It's applied to all string
> writing operations as I see no reason as to why this should only be
> limited to CONNECTION and DATA.
> I'll let you apply it once you've tested it. If we had any mapscript
> testers this should probably warrant for a beta3 rather than an RC,
> however as I feel this is not the case, going for a beta3 would only
> delay our release. thoughts?
>
> --
> thomas
>
> On 30 August 2013 12:51, Tamas Szekeres <szekerest at gmail.com> wrote:
> > Devs,
> >
> > I've added issue 4747 regarding to the UNC pathnames on Windows which is
> not
> > handled correctly by the mapfile writer. Actually the double backslashes
> are
> > written directly to the file (without escaping) while the parser reads
> only
> > one backslash in this case. Do you think it could be fixed by simply
> > replacing the backslashes with double backslashes when writing the file
> (for
> > example in the CONNECTION and DATA sections)?
> >
> > Best regards,
> >
> > Tamas
> >
> > _______________________________________________
> > mapserver-dev mailing list
> > mapserver-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20130901/c1598a4a/attachment.html>