- changed status to open
ASCII chars not un-escaped with Encoding Conversion Step
Issue #318
resolved
Original issue 318 created by @ysavourel on 2013-03-05T16:42:49.000Z:
Some ASCII characters seem to not been un-escaped by the Encoding Conversion step when going to UTF-8
See http://tech.groups.yahoo.com/group/okapitools/message/3579
Comments (3)
-
Account Deleted -
Account Deleted Comment 2. originally posted by @ysavourel on 2013-08-17T14:21:20.000Z:
This was closed at https://code.google.com/p/okapi/source/detail?r=a13b57d25796
-
- changed status to resolved
Fixed in latest okapi
- Log in to comment
Comment 1. originally posted by @ysavourel on 2013-08-17T13:29:07.000Z:
It seems the conversion code skips the ASCII characters:
if ( value < 128 ) {
// Unknown pattern or ASCII values: Keep it as it
// (so <, &, ", etc.. stay escaped)
tmp.append(m.group());
}
I guess we were playing it safe.
But we can be more specific and preserve only '<', '&', '>', ''' and '"' and convert all other ASCII.