Closed zhanglong2005 closed 8 years ago
liblognorm can't correct encode original chinese unide. like this example:
input text: otspc,10.2.240.72,20160613233647,zhanglon张g,0A02F04898F4F3E6574C635798DD5B5BA3B57A2FFB
rules: rule=:abc
output.txt: { "originalmsg": "otspc,10.2.240.72,20160613233647,zhanglon\u00E50.0g,0A02F04898F4F3E6574C635798DD5B5BA3B57A2FFB"}
you can see that the chinese character:张 is encode to \u00E50.0,this is not the correct unicode,the correct unicode is \u5f20.
I thinks this is a libfastjson bug.But i am not sure that.
Yes, this is libfastjson bug, which is fixed in 0.99.3.
Thanks Rainer...
liblognorm can't correct encode original chinese unide. like this example:
input text: otspc,10.2.240.72,20160613233647,zhanglon张g,0A02F04898F4F3E6574C635798DD5B5BA3B57A2FFB
rules: rule=:abc
output.txt: { "originalmsg": "otspc,10.2.240.72,20160613233647,zhanglon\u00E50.0g,0A02F04898F4F3E6574C635798DD5B5BA3B57A2FFB"}
you can see that the chinese character:张 is encode to \u00E50.0,this is not the correct unicode,the correct unicode is \u5f20.
I thinks this is a libfastjson bug.But i am not sure that.