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

Re: problem with mutated vowel in log-message-contents

From: Stephen Connolly <stephen.alan.connolly_at_gmail.com>
Date: Fri, 18 Feb 2011 14:01:52 +0000

unix shell scripting could solved it for you

for rev in $(svn log ... | sed -n -e "..."); do svn ps --revprop svn:log
"$(svn pg svn:log -r $rev | sed -e "s/oldstring/newstring/g;")" ... ; done

I leave the ...'s as an exercise to tgeur reader

- Stephen

Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
On 18 Feb 2011 13:16, "Thomas STEININGER" <tsteininger_at_racon-linz.at> wrote:
> i need a tip to solve my problem with log-messages in our
> subversion-repository. (see the mail-conversation with the tortoisesvn
> team below).
> there are message that contain mutated vowel and i need to find all them
> and correct them.
> f.e. i want to replace 'übergabe' by 'uebergabe' or if this is to
> difficult only by '_bergabe'.
> can anybode give me tips / commands to do that or probably there is an
> tool (because the problem was already solved for another user)?
> thanks for help
> -thomas
> Mails with TortoiseSvn-Team:
>>>>> Hello i have an really *big problem *using tortoise-svn.
>>>>> The same problem has - by the way - eclipse-subversive with
>>>>> javahl-connector, but not with svnkit-connector.
>>>>> if i try to show the logs of ein entry/file/.. in tortoisesvn where
> the
>>>>> log-messages contain a mutated vowel (german: deutscher umlaut)
>>>>> then it brings an failure msg:
>>>>> and then it shows
>>>>> instead of the messages.
>>>>> can anybody help?
>>>>> Thomas
>>>>log messages must be in utf8 encoding. That's a requirement of the svn
>>>>library. If they're not, then anything can happen. For example if you
>>>>access the repository with http(s), then those messages have to be sent
>>>>in an xml response, and non-utf8 strings result in invalid xml.
>>>>When you commit with TSVN, TSVN ensures the encoding. But it might be
>>>>that other svn clients have a bug and don't properly encode the log
>>>>messages. In that case you have to fix the repository on the server
>>>>directly using the command line tools (svnadmin).
>>>we already want to correct the log-messages, but we did not find an way
> to
>>>get all the log messages with failures and then to correct them.
>>>is there a known way - a tip to help us?
>>You have to ask for help with this on the Subversion users list. This is
>>an issue with the server/repository, not with TSVN and you'll get much
>>more help about this over there.
> Der Austausch von Nachrichten mit o.a. Absender via e-mail dient
ausschließlich Informationszwecken. Rechtsgeschäftliche Erklärungen dürfen
über dieses Medium nicht ausgetauscht werden.
> Correspondence with a.m. sender via e-mail is only for information
purposes. This medium is not to be used for the exchange of legally-binding
Received on 2011-02-18 15:02:31 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.