Hi, Peter Howkins wrote: > On Tue, Feb 28, 2006 at 10:18:59AM +0000, Daniel Clarke wrote: > > I was wondering whether it was a good idea to add to the pathname > > conversion code a case for spaces, linux real space <=> riscos > > pseudo space. Otherwise, filenames with spaces become inaccessible > > in riscos; well, versions less than 4 I guess. > > In hostfs? Sounds a good idea.
Wouldn't two transformations, one for Host -> RISC OS, f(), and the other RO -> Host, g(), that mean f(g(f(g(foo)))) == foo be best. Otherwise, I'd have a file with ASCII 32 in its name under Linux, that would appear as ISO-8859-1 160 under RISC OS, I'd then save that, creating a file with ISO-8859-1 160 along the original Linux file, and then how would the two files appear under RO? Wouldn't they clash? Even if the ISO-8859-1 160 under RO turns back into ASCII 32 that still doesn't stop there being two files that clash. I expect it's already a solved problem and we should do whatever NFS under RO did. Probably some sort of `any character outside allowable RO ones gets escaped' scheme. Cheers, Ralph. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel
