Re: Launch Services Issue/Question - two apps using same file extensions
Re: Launch Services Issue/Question - two apps using same file extensions
- Subject: Re: Launch Services Issue/Question - two apps using same file extensions
- From: Jeffrey Walton <email@hidden>
- Date: Tue, 09 Jul 2013 17:08:24 -0400
On Tue, Jul 9, 2013 at 4:25 PM, Dan Korn <email@hidden> wrote:
>
> On Jul 5, 2013, at 6:13 PM, Stephen Kay <email@hidden> wrote:
>
>> on 7/5/13 6:38 PM, Quincey Morris at email@hidden
>> wrote:
>>
>>> On Jul 5, 2013, at 14:22 , Stephen Kay <email@hidden> wrote:
>>>
>>>> It's a shame that there used to be a perfectly workable method for doing
>>>> this that no longer works, with no real replacement.
>>>
>>> If you'll excuse some editorializing, I'd suggest that it was "perfectly
>>> workable" only within a pure Mac ecosystem. In the past, there was always a
>>> problem trying to preserve the non-HFS metadata when moving files to or
>>> through (e.g.) a Windows system. The problem with *that* was the perception
>>> that Mac files were "broken" and not safe to interchange. That led to a
>>> perception that the Mac was laughable. The current overly-simple way that
>>> extensions are used was perhaps a slight over-reaction to this perception, but
>>> there we are.
>
> Right. Using Apple-specific resource forks and creator codes was fine back when you were in a Mac-only ecosystem. But it's not just Windows that broke this paradigm.
Microsoft does have alternate data streams, which allow it to interop
somewhat with HFS (http://support.microsoft.com/kb/105763). I'm not
sure what Linux provides, though.
Jeff
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden