0x18 is ^X, the ASCII control code for CANCEL. Seems to be working as designed. ;-)
No more seriously though, it sure looks like a bug. 0x18 is a perfectly legal UTF-8 encoding of the unicode character U+0018. Every US-ASCII character is encoded as itself in UTF-8 and the first 128 Unicode code points are exactly US-ASCII. // Ben On Mon, Jun 24, 2013 at 7:30 PM, olli hauer <oha...@gmx.de> wrote: > svnsync 1.8.0 fails if there is a non-printable characters in the commit > message > > Error message: > svnsync: E000022: Safe data 'MFC r251249, r251251, r251252, r' was > followed by non-ASCII byte 24: unable to convert to/from UTF-8 > > No issue with svnsync 1.7.10 (neon based) > > Parts of the file (synced with svnsync 1.7.10) > > $> cat $repo/db/revprops/251/251614 > ... > MFC r251249, r251251, r251252, r2512, r251254 and r251515: > > > $> more $repo/db/revprops/251/251614 > ... > MFC r251249, r251251, r251252, r^X2512, r251254 and r251515: > > > $> hexdump -C $repo/db/revprops/251/251614 > ... > 00000070 31 2c 20 72 32 35 31 32 35 32 2c 20 72 18 32 35 |1, r251252, > r.25| > > Culprit is the hex(18) sign. > > > -- > olli >