DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16784>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16784 Obsolete documentation on XMLTranscoder Summary: Obsolete documentation on XMLTranscoder Product: Xerces-C++ Version: 2.1.0 Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Documentation AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In the constructors for transcoders, such as XMLUTF8Transcoder, there is a block size parameter. According to the comments in the header file, this parameter limits the maximum size of data that can be converted by one call to transcodeFrom or transcodeTo. My experience (with the latest nightly build) is that is not so - the blocksize is irrelevant (except for possible performance implications). Provided I code the right maximum size in the call to transcodeTo or TranscodeFrom, then even with a blockSize of 4 bytes specified in the constructor, all is OK. -- Colin Paul Adams Preston Lancashire --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
