Hi Mathias, > [...] I tried to use IndexableBinaryStringTools to re-encode my 11 byte > array. The size was increased to 7 characters (= 14 bytes) > which is still a gain of more than 50 percent compared to the UTF8 > encoding. BTW: I found no sample how to use the > IndexableBinaryStringTools class except in the unit tests.
IndexableBinaryStringTools will eventually be deprecated and then dropped, in favor of native indexable/searchable binary terms. More work is required before these are possible, though. Well-maintained unit tests are not a bad way to describe functionality... > I assume that the char[] returned form IndexableBinaryStringTools.encode > is encoded in UTF-8 again and then stored. At some point > the information is lost and cannot be recovered. Can you give an example? This should not happen. Steve
