Bug 3528

Summary: Add GIOP 1.4 support which has other behaviour for ucs2/ucs4
Product: TAO Reporter: Johnny Willemsen <jwillemsen>
Component: ORBAssignee: DOC Center Support List (internal) <tao-support>
Status: NEW ---    
Severity: enhancement    
Priority: P3    
Version: 1.6.6   
Hardware: All   
OS: Windows NT   

Description Johnny Willemsen 2008-12-08 16:52:18 CST 
For GIOP 1.1, 1.2, and 1.3, UCS-2 and UCS-4 should be encoded using the endianess of the GIOP message, for backward
compatibility.
For GIOP 1.4, the byte order rules for UCS-2 and UCS-4 are the same as for UTF-16.
UTF-16LE and UTF-16BE, from IANA codeset registry, have their own endianess definition. Thus these should be
encoded using the endianess specified by their endianness definition.
Comment 1 Johnny Willemsen 2013-08-12 07:15:08 CDT 
GIOP 1.3 extends what is legal when using typecode indirection, this is not supported in TAO also