In message <Marcel-1.53-1116172929-f7fpErr@xxxxxxxxxxxxxxxxxxxxxx> Chris Evans <chris@xxxxxxxxxxxxxxx> wrote: > On Fri 16 Nov, Alan Adams wrote: >> > thanks veru informative. >> Not directly relevant here, but if we start trying out schemes to >> store all RISC OS allowed characters on a Windows filesystem, we need >> to make sure that the result will be usable when accessed >> >> from Windows >>>From RISCOS using SMB >> from RISC OS using NFS >> from RISC OS using HostFS. >> >> Some of these are issues which cause the regular discussions about >> "notypes", which improves some of these at the expense of others. >> >> Using NFS onto a Linux filesystem doesn't have these problems because >> Linux allows everything which RISC OS does. > Are you sure? > The NSLU2 uses linux ext3 format by default but in addition to the problem > Paul Vigay had with C++ on his, I have heard that part of the RISC OS > version of Firefox has a file with a rouge character that causes > problems! I should have said "I haven't found anything it can't handle." Hving said that, my VMS background makes me fairly conservative when naming files. > Chris Evans -- Alan Adams, from Northamptonshire alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx http://www.nckc.org.uk/ --- To alter your preferences or leave the group, visit //www.freelists.org/list/iyonix-support Other info via //www.freelists.org/webpage/iyonix-support