On Fri, 04 Jul 2008, Dag-Erling Smørgrav wrote:
> Sorry about the late reply - I'm used to being Cc:ed on replies to
> mailing list threads in which I participate, so I didn't notice your
> followup right away.
OK, I'll CC you. My preference is that I not be CC'd on replies to mailing
lists.
> Alan Barrett <apb_at_cequrux.com> writes:
> > I really don't like the idea of having two conflicting ways of
> > specifying the same information. One way (in svn:mine-type) should be
> > enough.
>
> - svn:charset is easier to handle for applications that need just the
> charset, not the media type (incorrectly referred to as mime type)
Yes, it would be easier, if this were being designed from scratch. But
it's not being designed from scratch.
You say that writing an application to parse a new svn:charset property
is easier than writing an application to extract charset information
from svn:mime-type, and I agree, but I claim that that's not a fair
comparision. A fair comparison would be between the status quo where
charset information can appear only in svn:mime-type, and a future in
which it's unknown whether charset information apears in svn:mime-type
or in svn:charset or both, so a future application would have to parse
them both, check for consistency, and raise an error if they are
inconsistent.
> - The full MIME Content-Type parameter syntax is unwieldy. It allows a
> variety of quoting and comment styles. [...]
> How far do you want to go to support the complete syntax?
That's up to the appliction author.
I don't want to get into a long debate about this, and I am not a svn
developer, but I did want to correct what I saw as a misunderstanding of
my position.
--apb (Alan Barrett)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-04 14:22:55 CEST