Extended chars not escaped in skeleton for XML filter

[Former user]

Original [issue 53](https://code.google.com/p/okapi/issues/detail?id=53) created by @ysavourel on 2009-04-09T12:58:40.000Z:

If the output encoding is not supporting some extended chars. They are not escaped in the skeleton parts. This is because the skeleton does not know what output encoding to use and cannot guess. - one solution would be to always escape, but in many case this result in un-necessary escaped chars. - another solution is to somehow flag the skelton parts with extended chars and have to encoder go through those parts when writing out the output.

[Former user]

Comment [1.](https://code.google.com/p/okapi/issues/detail?id=53#c1) originally posted by @ysavourel on 2009-06-08T15:17:43.000Z:

Workaround: set the output encoding to UTF-8 or another encoding that supports the characters in the file.

[Jim Hargrave (OLD)]

EncoderContext can now be used by the encoder when it is processing SKELETON. However the most files are going to be UTF-8 so this is probably a non-issue.