From: Vladimir Prus (ghost_at_[hidden])
Date: 2001-09-26 07:33:24
I have uploaded a file containing code conversion facets for UTF8 and UCS2 --
files Daryle uploaded don't address this aspect.
- UCS2 should be big-endian, but little-endian is also common. How
little-endian can be handled? Would it be possible to guess what encoding a
file uses by looking at leading 0xFFFE and store that information in
conversion state. Any hidden problems here?
- Seems like it's planned to have unicode support via some typedefs and
specializations. It find that having all the functionality available via
whar_t on systems where it's reasonably defined would be nice. Of cause, it
won't be portable, but wchar_t, wstring, wifsstream &c, are just more
familiar to most persons.
-- Regards, Vladimir
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk