Tom Walker <[EMAIL PROTECTED]> wrote:

> >I have now observed a new filename issue. !Sunfish mount files, which are
> >saved in !Boot.Choices.Users.Single.Sunfish.mountsave are not being
> >translated correctly. 
> >An example file is "192?168?0?1/mnt/Drive2?fat16", a reproduction of how 
> >the filename looks in ROS . 
> >It looks as though the filenames aren't correct on Linux (transferred by
> >!Sunfish) but I can't be sure about that, only that the names look 
> >different.
> >See attached screenshot from Linux.  
> >HostFS only sees filenames as "16", "192", "192", "t/acer?d", and much
> >gibberish. 
> >I note your final comment above, and provide this for your info.
> 
> Ah. Anyone have any ideas how that should be translated?

This is partly due to the way Sunfish translates filenames; it uses ? as
an escape character. Therefore when the file was copied the ?16 got
translated to ASCII 22 which is a control character. If HostFS does not
translate the control character, then when it gets to RISC OS it is
treated as the filename terminator.
Other than Sunfish, I'm not aware of any filing systems that try (or
indeed need) to cope with this, so I suggest using the same scheme as
Sunfish. The source code is available from my website if you want to see
exactly what translation it does.


Alex

-- 
Alex Waugh                                           [EMAIL PROTECTED]

PHP, Roots, Subversion, WebJames and more from http://www.alexwaugh.com/

_______________________________________________
Rpcemu mailing list
[email protected]
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu

Reply via email to