> The LCP transcoder is now completely generic. It is implemented > strictly in terms of the virtual transcoder interface. As such, > any XMLTranscoder can be passed in as the transcoder to fullfill > the LCP transcoding
Looking at the documentation for XMLLCPTranscoder and XMLTranscoder, and at MacOSUnicodeConverter.cpp/hpp, I don't see any relationship between XMLLCPTranscoder and XMLTranscoder. Also, why are their interfaces so different? Adam Heinz Senior Software Developer Exstream Software --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]