Dirk wrote:
From SVN manual "For example, if a file's svn:mime-type property is
set to a non-text MIME type (generally, something that doesn't begin
with text/, though there are exceptions), Subversion will assume that
the file contains binary—that is, not human-readable—data."
(http://svnbook.red-bean.com/nightly/en/svn.advanced.props.file-portability.html#svn.advanced.props.special.mime-type)
I checked the manual and came to the same conclusion. I have change
the auto_props code to first set the mime-type based on the binary
flag and then check for auto properties. So if the mime-type is
overwritten by the auto_props, we will loose application/octer-stream
in favor of a better description.
Yes, that should be the behavior we use.
Since I don't have much experiences with properties, I was wondering,
whether it is possible to have multiple mime-types. E.g. I dealing a
lot with PDF files but i'm interested in rendered images of the PDF
file. So I would assign a "image/PDF" mime-type instead of
"application/PDF". But both views of it a correct, so having both
wouldn't be totally wrong.
It really comes down to how the clients decide to use it. As far as
Subversion cares, it just matters that it doesn't begin with "text/".
You may want to ask that list whether multiple mime-types is OK and what
the behavior is in that case.
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
