This is the main operation used when converting data.
It is to be called multiple times in a loop, and each time it will do some work, i.e. producing some output (in
consuming some input (from
inbuf) or both. If its not possible to do any work an error is returned.
Note that a single call may not consume all input (or any input at all). Also a call may produce output even if given no input, due to state stored in the converter producing output.
If any data was either produced or consumed, and then an error happens, then only the successful conversion is reported and the error is returned on the next call.
A full conversion loop involves calling this method repeatedly, each time giving it new input and space output space. When there is no more
input data after the data in
inbuf, the flag g_converter_input_at_end must be set. The loop will
be (unless some error happens) returning g_converter_converted each time until all data is consumed and all
output is produced, then g_converter_finished is returned instead. Note, that
g_converter_finished may be returned even if g_converter_input_at_end is not set, for instance in a
decompression converter where the end of data is detectable from the data (and there might even be other data after the end of the compressed
When some data has successfully been converted
bytes_read and is set to the number of bytes read from
bytes_written is set to indicate how many bytes was written to
outbuf. If there are more data to output or consume (
i.e. unless the g_converter_input_at_end is specified) then g_converter_converted
is returned, and if no more data is to be output then g_converter_finished is returned.
On error g_converter_error is returned and throws is set accordingly. Some errors need special handling:
g_io_error_no_space is returned if there is not enough space to write the resulting converted data, the
application should call the function again with a larger
outbuf to continue.
g_io_error_partial_input is returned if there is not enough input to fully determine what the conversion
should produce, and the g_converter_input_at_end flag is not set. This happens for example with an incomplete
multibyte sequence when converting text, or when a regexp matches up to the end of the input (and may match further input). It may also happen
inbuf.length is zero and there is no more data to produce.
When this happens the application should read more input and then call the function again. If further input shows that there is no more data call the function again with the same data but with the g_converter_input_at_end flag set. This may cause the conversion to finish as e.g. in the regexp match case (or, to fail again with g_io_error_partial_input in e.g. a charset conversion where the input is actually partial).
After convert has returned g_converter_finished the converter object is in an invalid state where its not allowed to call convert anymore. At this time you can only free the object or call reset to reset it to the initial state.
If the flag g_converter_flush is set then conversion is modified to try to write out all internal state to the output. The application has to call the function multiple times with the flag set, and when the available input has been consumed and all internal state has been produced then g_converter_flushed (or g_converter_finished if really at the end) is returned instead of g_converter_converted. This is somewhat similar to what happens at the end of the input stream, but done in the middle of the data.
This has different meanings for different conversions. For instance in a compression converter it would mean that we flush all the compression state into output such that if you uncompress the compressed data you get back all the input data. Doing this may make the final file larger due to padding though. Another example is a regexp conversion, where if you at the end of the flushed data have a match, but there is also a potential longer match. In the non-flushed case we would ask for more input, but when flushing we treat this as the end of input and do the match.
Flushing is not always possible (like if a charset converter flushes at a partial multibyte sequence). Converters are supposed to try to produce as much output as possible and then return an error (typically g_io_error_partial_input).
the buffer containing the data to convert.
a buffer to write converted data in.
a ConverterFlags controlling the conversion details
will be set to the number of bytes read from
will be set to the number of bytes written to
the number of bytes in
the number of bytes in
a ConverterResult, g_converter_error on error.