|
Boost : |
From: williamkempf_at_[hidden]
Date: 2001-09-25 15:59:04
--- In boost_at_y..., dietmar_kuehl_at_y... wrote:
> Hi,
> Daryle Walker wrote:
> > I realized the Unicode problem this morning. I'll come up with a
> > prototype Unicode solution to put up in the vault. (It shouldn't
> > go into any XML sub-library since it would be needed for other
> > things, like C++ parsing.)
>
> I'm probably dense but can anybody please tell me what problem you
> are talking off at all? 'std::basic_filebuf' internally uses a
> code conversion facet which is intended to convert an external
> encoding into an internal representation. For example, a
> 'std::wistream' can read UTF-8, UTF-16, ..., at least if appropriate
> code conversion facets are available. If they aren't shipped by the
> vendor, they may be provided by the user.
You hit on the problem with your last sentence. The standard gave us
the ground work, but none of the needed final products. I'm also not
aware of any implementations that go that extra mile to give us the
necessary code conversion facets. That's precisely what's needed in
Boost, IMHO.
> I can understand that there is problem if your library vendor does
> not ship UTF-8, UTF-16, ... code conversion facets and these might
> have a place in the Boost library. However, since nobody mentioned
> code conversion facets before, I fear something really bad is going
> to happen if people try addressing this problem...
Well, since I was the first to post on this issue I should have made
it clear that what's needed is the appropriate facets, but I just
assumed that was obvious. In retrospect you're quite right that it
isn't necessarily obvious to everyone. My bad.
Bill Kempf
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk