[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Quriky utf-8, BOM and svn:eol-style

From: William A. Rowe, Jr. <wrowe_at_rowe-clan.net>
Date: 2007-08-27 06:32:28 CEST

I'd like to float an idea for a new feature to svn:eol-style native.
We understand 'native' to mean a local representation of text, and
many repositories do not retain the BOM (they might use an svnmailer,
or svn:mime-type to represent the encoding).

If the local utf-8 (or someday, utf-16le or utf-16be) file adds a
byte order mark, and the svn:eol-style is native, and the repository
copy contains no such mark, and they use a (new optional) config flag;

[miscellany]
bom-style-native = yes

could we kindly keep their BOM data to their local machine, and strip
it from the committed file?

If the remote file includes the BOM, of course we would want to retain
it. (Does this mean re-adding it if a local edit strips it out? Good
question to discuss.)

We've had allot of trouble with the same file maintained across various
platforms, and (for example) notepad/windows users pollute our repos
with their local byte order marks. We'd like to see this behavior die :)

Comments?

Bill

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 27 06:29:51 2007

This is an archived mail posted to the Subversion Dev mailing list.