Jens Seidel schreef:
> On Wed, Sep 17, 2008 at 10:01:56AM -0400, Mark Phippard wrote:
>> On Wed, Sep 17, 2008 at 9:59 AM, Hendrik Maryns
>> <qwizv9b02_at_sneakemail.com> wrote:
>>> Second question: is it useful to enter more specific MIME types then the
>>> generic application/octet-stream? Does it make any difference anywhere
>>> if it says image/png or application/x-tex? The latter might be
>>> problematic, I suppose, since it doesn't say 'text', although a TeX file
>>> is text only and should not be excluded from contextual merge.
>> If there is a MIME type, and it is not text/* then the file will not
>> support contextual merging and is treated as binary. The main purpose
>
> Even if svn:eol-style = native is set?
I don’t think that’s possible:
The svn:mime-type property, when set to a value that does not indicate
textual file contents, can cause some unexpected behaviors with respect
to other properties. For example, since the idea of line endings (and
therefore, line-ending conversion) makes no sense when applied to
nontextual files, Subversion will prevent you from setting the
svn:eol-style property on such files.
from
http://svnbook.red-bean.com/en/1.5/svn.advanced.props.file-portability.html#id469279
My main fear is that I would give a TeX file the mime type
application/x-tex, but Subversion would then treat it as a binary file.
Actually also C and Java files (and I think all other programming
language source files) have a MIME-type starting with application/
H.
--
Hendrik Maryns
http://tcl.sfs.uni-tuebingen.de/~hendrik/
==================
Ask smart questions, get good answers:
http://www.catb.org/~esr/faqs/smart-questions.html
Received on 2008-09-17 16:40:42 CEST