You can clone with
HTTPS or Subversion.
Buffer doesn't support UCS2-BE encoding.
I was going to write a patch for it, but I saw that this part is written in C and I'm not a C programmer.
It would be great to have this encoding in the core. It's a widely used encoding (e.g. SMPP protocol uses ucs2-be to encode unicode messages)
No, sorry. If we say yes to this, we'll have to say yes to the myriad other encodings too.
Have a look at https://github.com/bnoordhuis/node-iconv
I need this issue solved also, because of minecraft protocol requiring ucs2 big endian encoded strings.
If i write a patch and submit it, you're ok with it? It can be another encoding option: 'ucs2-be'.
@razorg: Sorry but no, for the reason mentioned above.
@razorg - Because v8 supports only little endian for UCS2, it is necessary to change byte order before reading and after writing a string from/to a buffer. It is possible in the user land. This is the reason why Node core does not support UCS2-BE.