On Oct 2, 2007, at 6:55 PM, Steve Sisak wrote:
> Passé or not, I still need to support Mac OS resource forks, types
> and creators (those are on their way back) and other Mac OS file
> metadata.
Yeah, I was afraid of that. Had to ask, you know.
> But if you cast the problem as "support for general MIME type
> decoding", that has general usefulness. Supporting Mac OS files
> attributes is just a test case.
Hey, I like that "requirements judo"! I agree it puts the key parts
of the change into somewhere useful to all platforms (I'm real
paranoid about non-Mac developers breaking our Mac-o-syncracies -
nothing personal, just an abiding sense of fragility).
> The MIME types for Mac OS file encodings have been set in stone for
> at least a decade (maybe 2).
>
> Matt has proposed file:appledouble for the property which contains
> the AppleDouble header file (associate with a given data file) --
> the format of the contents has been defined since A/UX. Unless
> there are major objections from someone, it's fine with me.
Why isn't the standard name for this property "svn:mime-type"? I
think there are official standard MIME types for AppleDouble and -
Single (multipart/appledouble and application/applefile,
respectively), so anything with that MIME type could, by a Mac
client, be exploded into the "real" file on checkout, and glommed
back up on checkin, right?
(Mental note about non-Macophilic file systems, like UFS, on Mac
platforms....)
-==-
Jack Repenning
jackrepenning@tigris.org
Project Owner
SCPlugin
http://scplugin.tigris.org
"Subversion for the rest of OS X"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 3 04:50:41 2007