#1 Different encodings

[Tomasz Baran]

hi,
is there a posibility to support different document
encodings by maki? I figured that placing a character
in an encoding different than utf-8 causes an error...
while using 4xslt from the command line doesn't.

It would be pretty handy to declare an encoding right
in the xml pi like: <?xml version="1.0"
encoding="iso-8859-2"?> for the server to recognize it
and use it to transform the document.

tomasz

[Samuel Brauer]

Logged In: YES
user_id=165785

Thanks for pointing this out. To help me fix this, please
send me an example iso-8859-2 encoded XML file to test with.
Also, please show me what the rule in your configuration
file looks like.

[Tomasz Baran]

Logged In: YES
user_id=179667

Sorry for the delay in answering... had a break from the
computer for a few days.

Here is a sample xml file with its dtd and stylesheet. The
xsl could be simpler, but I cut it from a larger piece. I
hope this will help you further.

[Tomasz Baran]

example xml with ISO-8859-2 encoding

[Samuel Brauer]

Logged In: YES
user_id=165785

Tomas,
Please try the current code in CVS. I just commited some
code that seems to be able to handle your iso-8859-2 data
correctly. Let me know if it works for you.

- Sam

[Tomasz Baran]

new example for encoding

[Tomasz Baran]

Logged In: YES
user_id=179667

Sam,
I tried the new cvs snapshot for the implemented encoding
issue :) But there is still a combination which I can't go
over...
Everything seems to work just fine for the encoding as long
as you use it in one place, that is either in the xml file
(and leave the xsl without ISO-8859-2 characters), or in the
xsl stylesheet (leaving the xml file clean of ISO-8859-2)

The deadly combination is an ISO 8859-2 encoded xml
processed by a stylesheet with ISO-8859-2 characters.

I attach an archive with files I used for testing. The
request.xml logicsheet is called and processed in the
configuration file, but it has no influence on the process
weather you call it or not (and if the encoding declared).

tomasz

[Samuel Brauer]

output from 2001-11-26 files

[Samuel Brauer]

Logged In: YES
user_id=165785

I finally got around to testing with your new files. At
first, I got an error because your rule (in bee-conf.xml)
was malformed XML:
<process / -->
should be:
<process />

After changing that the page seems to work (at least, I
don't get any exceptions). I'm going to attach a copy of
the output files I get. Since I don't recognize the
ISO-8859-2 characters I don't know if the output is right or
not ;) Please let me know. The file is "output.tgz".