On 02/21/2012 05:15 PM, Thilo Goetz wrote:
On 21/02/12 16:15, Jens Grivolla wrote:
On 02/21/2012 04:08 PM, Thilo Goetz wrote:
On 21/02/12 15:59, Jens Grivolla wrote:
it appears that InlineXMLCasConsumer depends on the system locale for
some internal transformations. The output appears to be wr
On 21/02/12 16:15, Jens Grivolla wrote:
> On 02/21/2012 04:08 PM, Thilo Goetz wrote:
>> On 21/02/12 15:59, Jens Grivolla wrote:
>>> it appears that InlineXMLCasConsumer depends on the system locale for
>>> some internal transformations. The output appears to be written in UTF8
>>> (outStream.write(
On 02/21/2012 04:08 PM, Thilo Goetz wrote:
On 21/02/12 15:59, Jens Grivolla wrote:
it appears that InlineXMLCasConsumer depends on the system locale for
some internal transformations. The output appears to be written in UTF8
(outStream.write(xmlAnnotations.getBytes("UTF-8"));) but when used on a
On 21/02/12 15:59, Jens Grivolla wrote:
> Hi,
>
> it appears that InlineXMLCasConsumer depends on the system locale for
> some internal transformations. The output appears to be written in UTF8
> (outStream.write(xmlAnnotations.getBytes("UTF-8"));) but when used on a
> machine with a locale of ASC
Hi,
it appears that InlineXMLCasConsumer depends on the system locale for
some internal transformations. The output appears to be written in UTF8
(outStream.write(xmlAnnotations.getBytes("UTF-8"));) but when used on a
machine with a locale of ASCII all accented characters get broken.
I suspe
