Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Standard OS X Compression format

On 18/11/01 2:52 am, "Markus Hitter" <email@hidden> wrote:

> Am Samstag den, 17. November 2001, um 18:19, schrieb Finlay Dobbie:
>
>> On Saturday, November 17, 2001, at 02:52 pm, Ondra Cada wrote:
>>
>>> The reason is simple -- to make the archive easily and without
>>> confusion
>>> useable worldwide. Should you try to unpack archive of your
>>> design on, say,
>>> Linux, you'll get a pretty mess. OTOH, should you unpack there
>>> "mine", you'll
>>> get only some trash in /tmp, where it does not matter, and the
>>> real files
>>> will be unpacked without any nonsense around.
>>
>> I'd prefer ._file, personally.
>
> Me, too. Unfortunately, Howard decided the other way.

My honest sticking point on this is that Finder implements using ._* support
on non-forked filesystems, and automatically handles creating/destroying
these correctly when handled on them. So either deciding that ._* should be
supported, or that Finder needs to be changed to support the "standard"
method, seems to be the way forward on this particular issue.

Is Finder right or wrong? Does Finder plan on supporting other mechanisms?
Can someone from Apple comment on future or present Finder behavior with
regard to the way resource forks are handled on non-forked Fses?

:plur,
Greg

References: 
 >Re: Standard OS X Compression format (From: Markus Hitter <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.