Remember that the System.Text.Encoder object saves state between calls to Encoder.GetBytes(Char[], int, int, Byte[], int, bool). When the application is done with a stream of data, it should set the flush parameter to true in the last call to GetBytes to make sure that the state information is flushed and that the encoded bytes are properly terminated. With this setting, the encoder ignores invalid bytes at the end of the data block, such as unmatched surrogates or incomplete combining sequences, and clears the internal buffer.

To calculate the exact buffer size that GetBytes requires to store the resulting characters, the application should use Encoder.GetByteCount(Char[], int, int, bool).

If GetBytes is called with flush set to false, the encoder stores trailing bytes at the end of the data block in an internal buffer and uses them in the next encoding operation. The application should call GetByteCount on a block of data immediately before calling GetBytes on the same block, so that any trailing characters from the previous block are included in the calculation.

If your application is to convert many segments of an input stream, consider using the Encoder.Convert(Char[], int, int, Byte[], int, int, bool, Int32@, Int32@, Boolean@) method. Encoder.GetBytes(Char[], int, int, Byte[], int, bool) will throw an exception if the output buffer isn't large enough, but Encoder.Convert(Char[], int, int, Byte[], int, int, bool, Int32@, Int32@, Boolean@) will fill as much space as possible and return the chars read and bytes written. Also see the Encoding.GetBytes(Char[], int, int, Byte[], int) topic for more comments.