On Monday 06 June 2005 15:57, Greg Thomas wrote:
> On Mon, 6 Jun 2005 12:36:36 +0200, Nicolas Goutte <email@example.com>
> >I would be nice if Subversion would have a svn:text property to tweak it
> >independently (even if perhaps its default would be "look at the mime
> > type").
> Regardless of the setting of the application/xml or text/xml mime type
> discussion held elsewhere, this strikes me as an incredibly sensible
> idea (though I'll turn it on it's head and suggest svn:binary
> Currently, the determination of whether or not files are binary is a
> bit arbitrary - a file is considered binary if it has a svn:mime-type
> other than text/*, image/x-xbitmap or image/x-xpixmap.
> A simple svn:binary flag set if needed automatically when a file is
> added (cf application/octet-stream) should make the whole thing a lot
> simpler - it will also solve the problem of more exceptions being
> added to the current list.
That is perhaps a good solution for migrating from CVS. Just map -kb to
svn:binary (But that would be a hint for the cvs2svn tool.)
The third posibility is to store the encoding and have a dummy encoding for
binary. That would help Subversion to help merging in the right encoding (to
follow my example of UTF-16 or UTF-32).
> For example, the XML files of OpenOffice documents are application/* -
> yet they are XML and therefore (presumably) text. No doubt they too
> should be added to the "not svn:mime-type=text/* but still text" list.
> This list could grow and grow, but a simple svn:binary flag solves the
> problem once.
No, sorry, by default OOo's files (even in the OASIS file format) are zipped,
so they are in fact binaries.
(Both OOo file formats have a flat version too but it is seldom used.)
> [dev list added, as no doubt there are other issues I've missed]
Have a nice day!
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Jun 6 18:54:46 2005