>The simple answer is to take transcode() out of DOMString. >[Take out print() and println() while you're at it.] A string >class should just be a container for char or wchar_t. Transcoding >and printing are functions to be applied to containers. >You might want to consider moving >to wstring in place of DOMString. (You knew that was coming ;-)) > That would be fine with me; however, many other people would probably agree. We put in transcode() due to people who don't want to do Unicode beating us up about having to do the transcoding themselves (and hence having to have some external mechanism for doing so, since we don't expose ours.) So taking it out at this point would probably get us into far worse trouble probably. ---------------------------------------- Dean Roddey Software Weenie IBM Center for Java Technology - Silicon Valley [EMAIL PROTECTED]
- xalan-c Problem with Xerces initialization Robert_Weir
- Re: xalan-c Problem with Xerces initialization roddey
- Re: xalan-c Problem with Xerces initializati... Andy Heninger
- Re: xalan-c Problem with Xerces initialization Robert_Weir
- Re: xalan-c Problem with Xerces initializati... Andy Heninger
- Re: xalan-c Problem with Xerces initialization roddey
- RE: xalan-c Problem with Xerces initialization Gregorio, Joe
- Xerces and Schema problem? Michel Goossens
- Re: xalan-c Problem with Xerces initializati... Andy Heninger
- Re: xalan-c Problem with Xerces initialization roddey
- Re: xalan-c Problem with Xerces initialization roddey
- RE: xalan-c Problem with Xerces initialization Arnold, Curt
- Re: xalan-c Problem with Xerces initializati... Andy Heninger
- RE: xalan-c Problem with Xerces initialization roddey
- RE: xalan-c Problem with Xerces initialization Robert_Weir
- Re: xalan-c Problem with Xerces initialization Scott Boag/CAM/Lotus
- RE: xalan-c Problem with Xerces initialization Arnold, Curt