You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by bu...@apache.org on 2003/02/04 23:08:17 UTC
DO NOT REPLY [Bug 16784] New: -
Obsolete documentation on XMLTranscoder
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: xerces-c-dev@xml.apache.org
ReportedBy: zhangpy@hotmail.com
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: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org