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

Re: "200 OK" error caused by non-ASCII characters?

From: Dag-Erling Smørgrav <des_at_des.no>
Date: Sun, 18 Oct 2009 23:52:19 +0200

Stefan Sperling <stsp_at_elego.de> writes:
> Dag-Erling Smørgrav <des_at_des.no> writes:
> > Won't work - 'propget svn:log' doesn't return the real log message:
> Well, it is legal UTF-8 :)

For what it's worth...

> Can you try with file:// access?

No difference.

> Maybe the log message has not even been stored correctly?

It is definitely stored as ISO8859-1, I checked the db (fsfs).

> Are you sure it was correct latin1 when it exited your editor,


> and that you were running with a latin1 locale so that the svn client
> would auto-convert the data from latin1 to UTF-8?

I'm 100% positive that I used a ISO8859-1 locale at the time (7+ ago),
and 100% positive that it's stored as ISO8859-1 in the db.

I didn't switch to a UTF-8 locale until around 2006.

I've never committed over http:, always over file: or svn+ssh:.


Dag-Erling Smørgrav - des_at_des.no
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-18 23:53:00 CEST

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