Unicode comment strings doesn't handled correctly in "move" API calls to bitcoind. #2127

issue HandleX opened this issue on December 24, 2012

HandleX commented at 1:29 PM on December 24, 2012: none

OS: Windows Server 2008 R2. Call method: HTTP JSON RPC. Stringification method: JSON.stringify().

When I execute "move" bitcoin API (handled by bitcoind.exe), some comment string characters supported correctly, some not.

As an example: I've executed "move" API with comment "฿иткоин", where first letter is unofficial unicode bitcoin sign, and others are russian characters. Then I've executed "listtransactions" API call, I've received comment string distorted: "฿иu0082коин". As we can see, some characters correct, some not.

I use bitcoind as an online wallet on my site. Transaction comments can be useful there, so I want to have correct JSON RPC unicode support in bitcoind.
laanwj added the label Wallet on May 28, 2014
laanwj removed the label Priority Medium on May 28, 2014
laanwj added the label Priority Low on May 28, 2014
laanwj commented at 1:04 PM on January 29, 2016: member

I wonder how this changed with the switch from json_spirit to univalue in 0.12.

I don't think it is completely fixed: there's one known issue with utf-8 handling at least: https://github.com/jgarzik/univalue/issues/16
laanwj commented at 10:08 AM on June 16, 2016: member

Closed by #7892
laanwj closed this on Jun 16, 2016
MarcoFalke locked this on Sep 8, 2021

Contributors

Labels