[XERCESC-1663] IconvGNU and IconvFBSD based transcoders assume UCS-2 as XMLCh encoding

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 3.0.0
• Component/s: Utilities
• Environment: any
• Assignee: Alberto Massari
• Reporter: Boris Kolpackov
• Created: 31/Dec/06 15:11
• Updated: 12/Mar/18 03:01
• Resolved: 11/Mar/08 08:47

Description

I was studying the code in IconvGNU and IconvFBSD transcoders and it appears that they assume UCS-2 is the encoding for XMLCh when it's actually UTF-16. I believe this can result in the loss of data.

The encoding that is used for XMLCh is stored in the fUnicodeCP variable which is initialized in the Iconv

{GNU,FBSD}TransServices c-tor. The initialization code just tries all encodings from the gIconv{GNU,FBSD}

Encodings array which for GNU contains only UCS-2 and for FreeBSD contains UCS-2 and UCS-4 encodings.

I tried to add a UTF-16LE to this array (as a first item) and it works fine for GNU (I double checked that UTF-16LE ends up in fUnicodeCP). Does anybody knows what's going on here? Should we add UTF-16 to these arrays?