Nelson Bolyard wrote:
Jean-Marc Desperrier wrote:
I wonder if it's correctly documented somewhere that
PORT_UCS2_UTF8Conversion in NSS means UCS2 Little Endian, while the
UCS2 based types in the Mozilla context have a platform dependent byte
order.
No, that wouldn't be correctly documented anywhere.
The UCS2 side of PORT_UCS2_UTF8Conversion always consumes/produces
Big Endian UCS2. This is because all UCS2 as used in certificates is
always big endian.
Should I add a comment about this to our secport.h header file?
Is Big Endian chosen because it is the network byte order?
Wan-Teh
_______________________________________________
mozilla-crypto mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-crypto
