Don Cragun wrote:
>>
>>
>>> > > > What happens if a Windows client creates a new file
>>> containing the
>>> > > > 0x00f8 character? Does that:
>>> > > >
>>> > > > (a) fail, because a file name on UNIX can't possibly have a
>>> '/' in
>>> > > > it, and no file system should accept it.
>>>
>>> If I read the spec correctly this would never happen. 0x00f8 is a
>>> Latin small letter o with stroke; not a '/' (AKA solidus or virgule)
>>> character. Whether or not catia=true, an o with stroke character
>>> will not be translated to '/'.
>>
>> Actually, this is exactly what happens.
>>
>> If Windows were to use the o-with-stroke character and "catia" were
>> set on the file system, then the file name would be translated by the
>> Solaris server to have '/' in it, and the call would then fail.
>
> I didn't get that from reading the spec. It thought it talked about
> translating CATIA version 4 (which runs only on UNIX systems) filenames
> to CATIA version 5 (which run both on UNIX and Windows systems)
> filenames. I don't remember anything about translating the other way
> around. (Since the OpenSolaris ARC site is off-line for a day, I can't
> verify it now.)
Yes, the translation has to go both ways.
For example, if the Windows client does a directory listing the filenames
received from the filesystem are translated by the Solaris CIFS server to
v5 format in the response sent back to the windows client. When
the Windows client sends a filenames in a request to the Solaris CIFS
server
the filename is translated to v4 format before accessing the filesystem.
So the CATIA v4 filenames in the file system on the Solaris server appear
as CATIA v5 filenames on the Windows client.
