On Thu, 18 Nov 2004 17:22:50 +0100, Uwe Zeisberger <[EMAIL PROTECTED]> wrote:
> Below comes a log and a patch. I assume, that apr_xlate_conv_buffer > should convert inbuf and assume, that the strings ends then. Else its > use in test/testxlate.c is not appropriate. it was assumed that the application does not have the knowledge to guarantee that complete characters are always passed to apr_xlate_conv_buffer(); instead, we only assume that the complete stream of data passed by the application over multiple calls to apr_xlate_conv_buffer() ends with a complete character (or app gets the INCOMPLETE return code on last call and realizes there is a problem since there is no more input data which could complete the character) it is a big burden on the application to know when a character ends or am I misunderstanding you?
