From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/31339 Path: news.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Problems mapping Xml into ConTeXt Date: Thu, 12 Oct 2006 08:53:45 +0200 Message-ID: <452DE679.2040406@wxs.nl> References: Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1160636060 16064 80.91.229.2 (12 Oct 2006 06:54:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 12 Oct 2006 06:54:20 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Thu Oct 12 08:54:16 2006 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by ciao.gmane.org with esmtp (Exim 4.43) id 1GXuSJ-0004E2-8g for gctc-ntg-context-518@m.gmane.org; Thu, 12 Oct 2006 08:54:11 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 53FED1FDD3; Thu, 12 Oct 2006 08:54:10 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27432-01; Thu, 12 Oct 2006 08:54:01 +0200 (CEST) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id B24691FDD4; Thu, 12 Oct 2006 08:53:58 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id C9EFF1FDD4 for ; Thu, 12 Oct 2006 08:53:54 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 24910-02 for ; Thu, 12 Oct 2006 08:53:48 +0200 (CEST) Original-Received: from mail.pragma-ade.net (dsl-083-247-100-017.solcon.nl [83.247.100.17]) by ronja.ntg.nl (Postfix) with SMTP id 4DA071FDD3 for ; Thu, 12 Oct 2006 08:53:47 +0200 (CEST) Original-Received: from [10.100.1.104] (unverified [10.100.1.104]) by controller-1 (SurgeMail 3.7b8) with ESMTP id 12521 for ; Thu, 12 Oct 2006 08:53:45 +0200 User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) Original-To: mailing list for ConTeXt users In-Reply-To: X-Server: High Performance Mail Server - http://surgemail.com r=-274017400 X-Authenticated-User: hagen@controller-1 X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.7 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl X-Virus-Scanned: amavisd-new at ntg.nl Xref: news.gmane.org gmane.comp.tex.context:31339 Archived-At: Michael Wigston wrote: > > Hans Hagen wrote: > > Michael Wigston wrote: > > > 1. This def of does nothing ... > > > \defineXMLgrouped [u] \underbar > > > > > \defineXMLargument[u]{\underbar} > > > > underbar is not a font switch but a macro that takes an argument > > Hans, > > Thanks, that works fine with \underbar, as well as \underbars, > \overstrike, \overstrikes, \low, \high and \lohi. > > You mentioned that \underbar (and presumably the others I mentioned > above) are macros taking arguments e.g. \acommand{...}. However > presumably something like \midaligned{...} is also a macro requiring > an argument, but this works as a \defineXMLgrouped and as a > \defineXMLargument - why does it work with both? the macro ones do manipulate their argument, for instance, underbar is not a font charateristic or color switch or so i.e. not a real attribute; esp using setups will make your style look better (look into x-fo for instance, forget about the dirty tricks there, but it's pretty clean; mapping values and so save many macro definitions > > The manual "XML in ConTeXt" very briefly sketched over these XML > commands and I can see great potential to use them directly on XML to > generate ConTeXt for PDF rather than the XSLT/XSL-FO route which seems > to be gaining momentum in much of the industry. I don't suppose there > is another more detailed document which elaborates on the XML > commands, and how you may determine which of these is most appropriate > for what kind of ConTeXt command mapping? you can take a look into the x-* files which show quite some mappings; indeed direct mapping is often more convenient than transformations; future versions of context will also offer more manipulation possibilities > > > Also at the moment a non-mapped element seems to automatically type > out its contents as straight text - is there a way to override this > behaviour and specify this as an error? (This is rather like the Ruby > duck-typing approach - if an XML element is mapped, process it, else > it is an error). \startXMLignore \stopXMLignore in xtag-pre you can see: \defineXMLenvironment [\s!default] \defaultXMLelement \defaultXMLelement \defineXMLsingular [\s!default] \defaultXMLelement % \def\defaultXMLelement % {\iftraceXMLelements[\currentXMLfullidentifier]\fi} \def\defaultXMLelement {\iftraceXMLelements{\infofont<\currentXMLfullidentifier>}\fi} %D We can use the default handler to implement automatic %D element hiding. Beware: this overloads the tracer. \def\startXMLignore{\dododefineXMLignore \s!default} \def\stopXMLignore {\dododefineXMLprocess\s!default} so you can play with the default handlers Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------