PROTECTED]
Subject: RE: SunShine-InsertTransformer: encoding problem
--- Carsten Ziegeler [EMAIL PROTECTED] wrote:
Alex Romayev wrote:
This is currently hard coded into the
transformer(!)
which
means you can't do anything against it...
The InsertTransformer has been merged
--- Carsten Ziegeler [EMAIL PROTECTED] wrote:
Alex Romayev wrote:
This is currently hard coded into the
transformer(!)
which
means you can't do anything against it...
The InsertTransformer has been merged with the
SourceWritingTransformer
in 2.1-dev - the
Sorry for the re-post, but there have been some mail
problems on Friday when I posted it and I haven't
heard from anyone since then. I'm still struggling
with both problems, so any help would be greatly
appreciated.
Alex
--- Alex Romayev [EMAIL PROTECTED] wrote:
Sorry the C is supposed to read
Alex Romayev wrote:
Hi,
I'm trying my way around SunShine and running into
2
problems:
1) I have an existing XML file with UTF-8
encoding.
I
use InsertTransformer to add a new record. It
does
so
correctly, but changes the file encoding to
ISO-8859-1
--- Carsten Ziegeler [EMAIL PROTECTED] wrote:
Alex Romayev wrote:
Hi,
I'm trying my way around SunShine and running
into
2
problems:
1) I have an existing XML file with UTF-8
encoding.
I
use InsertTransformer to add a new record. It
does
so
Alex Romayev wrote:
This is currently hard coded into the transformer(!)
which
means you can't do anything against it...
The InsertTransformer has been merged with the
SourceWritingTransformer
in 2.1-dev - the SourceWritingTransformer can be
configured
to what encoding should be
Sorry the C is supposed to read as (I'm separating
with spaces) # 1 0 5 7 ;, the browser displays it
as a letter C.
--- Alex Romayev [EMAIL PROTECTED] wrote:
Hi,
I'm trying my way around SunShine and running into 2
problems:
1) I have an existing XML file with UTF-8 encoding.
I
use