Comment # 21
on bug 11372
from Peter Wu
(In reply to Graham Bloice from comment #18)
> > > So a gui user will be "OK", although the path looks odd in Windows, but a
> > > command line user on Windows is in some difficulty.
> >
> > Perhaps we should, instead, store it in the native format, with backslashes
> > escaped, and make sure that everything *else* that enters a pathname escapes
> > it as necessary?
>
> I was wondering why the uat code needs to unescape things at all? Why would
> you want to put "control" characters into a uat record?
In case you have field values in your UAT that contain a comma or other
syntactis sugar. The UAT code is needed for (de)serialization. I've just added
a patch. Can you test it?
You are receiving this mail because:
- You are watching all bug changes.