2012/11/19 Stefan Bellon <[email protected]>:
> This seems to me an inconsistency. Either support all allowed filenames
> per OS and skip them on OSes that cannot support them, or go with the
> set of filenames that all OSes can support (at least the mainstream
> ones).
>
> But being able to add str"i"ng.h but not str\i\ng.h seems strange to me.
Agreed. I tried it in cygwin, and there I can add files with special
characters just fine. But cygwin uses a trick to accomplish that:
<http://cygwin.com/cygwin-ug-net/using-specialnames.html>
So, a solution could be, when checking out files on Windows which
contain invalid characters there, translate those characters to
characters in the range U+F000 - U+F0FF.
This way, files with quotes can be inserted in fossil just fine. When
using the cygwin shell, everything works fine. When using another
shell, the filename might look strange (it looks like: "string.h")
but apart from that everything could be made to work fine.
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
