Not to mention that the UTF16TextConverter also handles characters
outside the BMP.

2006/8/5, John M McIntosh <johnmci at smalltalkconsulting.com>:
> Actually the correct question is what the target character set is for
> the conversion since I was under the
> assumption that one wanted UTF-32 as a result.
>
> So COM is UTF16? Or some special Windows encoding?
>
> UTF16 can be either Big E or Little E and you can supply a Byte Order
> Mark that helps resolve what it is.
> When building the UTF16 converter you can specify these details.
>
> On 4-Aug-06, at 2:00 PM, nicolas cellier wrote:
>
> > Obviously, Squeak WideString have 32 bits characters while Windows
> > (and other
> > OS i presume) have 16bits characters, and yes, OS byte ordering
> > does matter.
> --
> ========================================================================
> ===
> John M. McIntosh <johnmci at smalltalkconsulting.com>
> Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
> ========================================================================
> ===
>
>
>
>