[JBDP] In reply to Dean Roddy: > I would like to go on the record as saying that I'm very much against > this > proposal, nothing personal. [JBDP] Fair enough.
> I believe that the simplicity and maintainability of the current > architecture is more important. The work to make the parser core > conditionally do Unicode or ASCII is more than I'm willing to stomach. [JBDP] Well, since I have zero idea how much work it would be to define XMLCh as char and use "UTF8J"-encoded characters and no idea as to the strength of your stomach I cannot judge. Naively one might hope that typedeffing XMLCh to char and tweaking the transcoders to output UTF8J instead of UTF16 would be all that it would take but usually it's the last 5% of extra tweaks that take the time and cause all the bugs... > For those few people who need to do so, transcoding from Unicode to local > code page is trivial. [JBDP] I don't know how many people have compilers and libraries (including legacy libraries, whether home-grown or thirds party) that support character-style and string-style operations on unsigned shorts so I don't know how "few" the people are who will be inconvenienced. > It would be far, far, far more trivial for you to put > a transcoding event handler layer over our events which transcode into > local buffers and then pass these on, so that the client code only ever > sees whatever form it wants to. [JBDP] Well, it's is trivial for me and I have no idea now non-trivial it would be for Xerces. But as I said it is clumsy and inefficient, leading to memory allocation every time a string is accessed. We do have a crude wrapper class that returns converts every DOMString to a standard string. ...but having everybody design and implement their own wrapper classes is hardly ideal. > The original intent when I designed the system was that XMLCh would float > to wchar_t. [JBDP] This would obviously be a big improvement. Firstly because wchar_t is distinct from unsigned short and secondly because it is much more likely that the libraries that people have support string-like operations on wchar_t -- even if legacy code doesn't. I'll stick to the wrappers! -- jP -- This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE GROUP, CREDIT SUISSE FIRST BOSTON, and each of their subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity.
