[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Need Help with .htm file in CVS.
From: |
Maninder Singh\(SDG\) |
Subject: |
RE: Need Help with .htm file in CVS. |
Date: |
Mon, 29 Aug 2005 17:28:54 +0530 |
Hi Russ/ All,
Thanks for the immediate help. That was really helpful.
However, there is still one query in my mind; as it says that copying
the Mac file to a PC results in the loss of the resoource fork. But we
haven't checked out the file on a PC. We've just checked-in the .htm
file with the correct info through MacCVS client into CVS (running on
Suse Linux) and later checking-out the same file on the same Mac changes
it's Creator / TYPE fields. Is the PC interface that you specified,
specifically the Windows platform (which in this case does not come in
the picture), or is it any machine other than a MAC machine?
Thanks again for the help.
Regards,
Maninder Singh
Member-SDG(SCM)
-----Original Message-----
From: Russ Sherk [mailto:address@hidden
Sent: Saturday, August 27, 2005 7:15 PM
To: Maninder Singh(SDG)
Cc: Pierre Asselin; address@hidden
Subject: Re: Need Help with .htm file in CVS.
On 8/27/05, Maninder Singh(SDG) <address@hidden> wrote:
> These fields are visible in the Resorcerer (MAC OS X) under the "File
> Info" option of the File Menu.
>
Interesting Mac feature. Anyhow, from what I have read, it appears that
the info you describe is not by default stored _in_ the file:
"Once a Mac file is copied to the PC, the resource fork, type and
creator information are lost unless the file is encoded with MacBinary
or a similar format (HQX, SIT, etc.) that saves the Mac specific data
with the file. This way the file can exist on a single fork machine (PC,
UNIX) or be telecommunicated and decoded at the other end with all Mac
information intact." --
(http://www.dtidata.com/mac_data_recovery.htm)
This would indicate that "TEXT"/"MSIE" is the default application
associated with .html files on that machine.
So the solution would probably be to encode the type/creator info in the
file itself. I have no idea how this would affect the portability of
the file (to PC, *NIX etc.).
Hope this helps,
--Russ