I suggested adding more mime-type values to be recognised as
text: application/xml-dtd, application/xml and
application/*+xml.
First, sorry for not noticing past discussions on this subject.
My excuse is that I didn't read the mailing list search tool's
instructions carefully enough, and did not use the quotes when
searching for "mime-type" thus getting "mime" but not "type".
Sorry, again.
Second, some background. I posted my original message after one
of my colleagues explained very, very plainly what he thought of
our version control system which wouldn't let him use svn blame
(more precisely, the TortoiseSVN equivalent) on a DTD. I didn't
know why at that stage, being fairly new to Subversion (we've
been using it for only two months). When I worked out that the
reason was because SVN thought it was not text, his opinion
became even plainer.
An XML DTD is often, but not always, prepared with a text editor
or a syntax-aware text editor. Exactly the same claim can be
made about, say, a C++ source file. If SVN presents C++ source
as text, shouldn't it do the same for application/xml-dtd? The
argument is weaker for application/xml, which is more likely to
be edited with a specialized program, but is often text.
I like Paul Koning's suggestion to make the presence of the
svn:eol-style property define a file as text. If that worked, I
would be using it. And thank you to Karl Fogel for adding this
thread to
http://subversion.tigris.org/issues/show_bug.cgi?id=1002.
- Mark Irving
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-05 18:09:43 CET