Collection right now does not support any strings other than ASCII. There is nothing in the code that was preventing the use of UTF 8 or other characters in the string. As long as it is NULL terminated everything should work. However I recently was working on the JSON serialization and realized that logic of escaping characters in the string would depend of the type of the string.
That would mean that we need to add a new type of stings and process them accordingly. The impact and scope yet has to to be investigated.
Fields changed
component: SSSD => libcollection
I think you should just treat string in an opaque way. utf8 is ascii7 compatible. So just make sure you never touch chars with the first bit set and you are done. This will make the code utf8 compatible and even ascii7 code pages compatible w/o the need to treat anything in any special way.
The only case where you'd need special code is if you need to change string case or do case insensitive comparison of non-ascii7 strings. I do not think you have this need currently.
rhbz: => 0
milestone: Tools Backlog => Tools 2.0
Metadata Update from @dpal: - Issue set to the milestone: Tools 2.0
It looks JSON serialization was never implemented and the reasoning behind this RFE isn't valid anymore. Please reopen if disagree.
Metadata Update from @atikhonov: - Custom field component adjusted to None (was: libcollection) - Custom field patch reset (from 0) - Custom field selected adjusted to None - Custom field testsupdated reset (from 0) - Custom field type adjusted to None (was: enhancement) - Custom field version adjusted to None (was: 1.8.1) - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.