Hans Hagen wrote:
> Michael Wigston wrote:
> > 1. This def of <u> 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 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?
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).
Michael
NOTICE
This e-mail and any attachments are intended for the addressee(s) only and may be confidential. They may contain legally privileged or copyright material. You should not read, copy, use or disclose them without authorisation. If you are not the intended recipient please contact the sender as soon as possible by return e-mail and then please delete both messages. This notice should not be removed.
_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
