On Mon, Jun 24, 2013 at 09:47:17PM +0200, Ben Smith-Mannschott wrote:
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
Daniel Shahaf wrote on Tue, Jun 25, 2013 at 13:50:58 +:
On Mon, Jun 24, 2013 at 09:47:17PM +0200, Ben Smith-Mannschott wrote:
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
Daniel Shahaf wrote on Tue, Jun 25, 2013 at 16:55:24 +0300:
Daniel Shahaf wrote on Tue, Jun 25, 2013 at 13:50:58 +:
On Mon, Jun 24, 2013 at 09:47:17PM +0200, Ben Smith-Mannschott wrote:
0x18 is ^X, the ASCII control code for CANCEL. Seems to be working as
designed. ;-)
No more
On 2013-06-25 16:02, Daniel Shahaf wrote:
Daniel Shahaf wrote on Tue, Jun 25, 2013 at 16:55:24 +0300:
Daniel Shahaf wrote on Tue, Jun 25, 2013 at 13:50:58 +:
On Mon, Jun 24, 2013 at 09:47:17PM +0200, Ben Smith-Mannschott wrote:
0x18 is ^X, the ASCII control code for CANCEL. Seems to be
olli hauer wrote on Tue, Jun 25, 2013 at 17:06:35 +0200:
On 2013-06-25 16:02, Daniel Shahaf wrote:
Daniel Shahaf wrote on Tue, Jun 25, 2013 at 16:55:24 +0300:
Daniel Shahaf wrote on Tue, Jun 25, 2013 at 13:50:58 +:
On Mon, Jun 24, 2013 at 09:47:17PM +0200, Ben Smith-Mannschott wrote:
On 2013-06-26 01:05, Daniel Shahaf wrote:
olli hauer wrote on Tue, Jun 25, 2013 at 17:06:35 +0200:
On 2013-06-25 16:02, Daniel Shahaf wrote:
Daniel Shahaf wrote on Tue, Jun 25, 2013 at 16:55:24 +0300:
Daniel Shahaf wrote on Tue, Jun 25, 2013 at 13:50:58 +:
On Mon, Jun 24, 2013 at
svnsync 1.8.0 fails if there is a non-printable characters in the commit message
Error message:
svnsync: E22: 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
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
