Well technically there is some sort of precedent to this, since
CharsetEncoder/Decoder operate on CharBuffers which are just utf-16
encoded strings. So charsets already may produce a single output code
*unit* for multiple input code units (UTF-32, which may output 1 code
unit for 2 UTF-16 input code units / chars). Of course, consuming
multiple code points would be new but code points aren't really part of
the CharBuffer api.
- Jonas
On 05/02/2018 05:29 PM, Weijun Wang wrote:
On May 2, 2018, at 4:35 PM, Jonas Konrad <m...@yawk.at> wrote:
"0a0b0c".getBytes(HexCharset.getInstance()) = new byte[] { 0x0a, 0x0b, 0x0c }
new String(new byte[] { 0x0a, 0x0b, 0x0c }, HexCharset.getInstance()) = "0a0b0c"
Normally a charset is to encode a string to byte[], but here you can actually
decoding a string to byte[]. This would lead to quite some concept differences.
For example, we can say if a char is encodable for a charset, but for the HEX "charset",
you will have to say what combination of chars is "encodable".
--Max
