From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/4693 Path: main.gmane.org!not-for-mail From: Petr Ferdus Newsgroups: gmane.comp.tex.context Subject: Re:typeseting XML Date: Fri, 18 May 2001 16:33:49 +0200 (CEST) Sender: owner-ntg-context@let.uu.nl Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1035395336 27832 80.91.224.250 (23 Oct 2002 17:48:56 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:48:56 +0000 (UTC) Original-To: ntg-context@ntg.nl In-Reply-To: Xref: main.gmane.org gmane.comp.tex.context:4693 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:4693 > \defineXMLsingular [backslash] {$\backslash$} > having in XML doc an empty element , 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

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