Re:typeseting XML

[Petr Ferdus <pferdus@vertigo.fme.vutbr.cz>]

> \defineXMLsingular [backslash]  {$\backslash$}
> having in XML doc an  empty element <backslash/>, with no success (no
> error either, it was just silently discarded). 
Sorry for bothering, there was a mistake on my side. This setup of course
typesets backslash, just my script was converting to elements everything
but backslashes...

Anyway I have another question. There was a note on direct XML processing
(texexec --env=yourenvironemntfile yourfile.xml) which works partly for me.
I can't force source document translation. I used to have in tex source 
files line like:
%interface=en output=pdf texttranslate=cp1250cs
When I try direct XML processing and have such line in my environment
file, it seems to ignore such directive (I guess, because it produces dvi
file without explicit command line switch). What could be done to inform
context about XML source encoding? (command line swich like
--translate-file=cp1250cs, process instruction or specifying  used
encoding directly in XML source does not seem to help as well) Any input
would be appreciated.

If I can have one more question, I would like see some hints, how to
implement separate handling of XML elements,  based on the value in
key="value" pairs. So if there is an element <p style="a"> what would
process p's separately for every value of style key. Is there some
shareable knowledge? (I can't figure it out with the aid of "example"
manual)
Thanks.

Peter Ferdus