Am 22.09.2005 um 12:02 schrieb Ryan Schmidt:
> On Sep 22, 2005, at 02:26, Dave Camp wrote:
>
>> The best option is to stop using Icon\r files. Move to one of the
>> modern data fork only formats that have been around for years.
>>
>>
>
> I really don't think there's any alternative. I encourage you to
> try it now. Go into your Applications folder and Get Info on
> Address Book, click the icon, and copy. Now Get Info on the
> Applications folder, click the icon, and Paste. A file named Icon\r
> is created in the Applications folder, its data fork is empty, and
> its resource fork contains an icns resource ID -16455.
>
Yes. That's the way this "strange" file is created. It's beyond the
control of the user.
But I've tested another thing which makes me wonder why Subversion
can't handle it, but maybe I'm to naive:
- I can copy (command line: cp -R ..) the folder -- including its icon
- I can tar the folder (tar -xzf ...) und untar it -- including its icon
So, why can't I simply "svn import" the folder including its icon.
Sure.. this is a very user centric point of view ;)
I've written a small Java app (zipping/unzipping a folder with an
icon) testing what Java is doing with Icon-Files. The result is what
the experts here probably have expected: The Icon\r file is added to
the zip and extracted. But: After extracting, the icon file is
present but no icon is shown. I think that's the data and resource
fork problem.
I think I'd have to ask the Apple guys to come up with a solution for
this :(
Jens
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 22 15:12:03 2005