XML to paper publishing with manual intervention

My paper “XML to paper publishing with manual intervention” is accepted for XATA 2010 (XML: Aplicações e Tecnologias Associadas), 19 and 20 May, Vila do Conde, Portugal. Abstract:

Existing tools consider XML to paper conversion as one black box step and provide control only through predefined options. With this approach, tuning the layout of output documents is a burdensome task.

The paper advocates a new workflow for XML to paper conversion, in which a separate step allows the user to fine control the layout. The changes made by the user are remembered and later can be automatically re-applied during publishing an updated version of the document.

A possible technical implementation for the workflow is suggested. TeX is used as a typesetting engine. XML to TeX conversion is made using XSLT and TeXML. The management of changes is performed by diff and patch tools.

3 Responses to “XML to paper publishing with manual intervention”

  1. chadnick Says:

    Hi olpa,

    i don’t know if the blog was intended to be a place for general questions concerning TeXML. I stop it, when I’m told.

    First of all I’d like to know if TeXML development is still alive?
    In addition I’d like to know if there is an elegant way to define this command in TeXML.

    \renewcommand {\familydefault} {\sfdefault}

    most important is to have no spaces arround \familydefault and \sfdefault.
    my solution is to use this construction.


    but I would prefer something like this

    -> latex
    \renewcommand { \familydefault } { \sfdefault }

    (does not work for me because of the spaces which are always added for commands)



  2. olpa Says:

    There was a lot of spam in the mailling list, therefore I closed it. At the moment, I recommend to send me e-mails. I answer in less then 24h.

    1) Starting with the technical question:

    For me, the following works (typeset with underscores instead of spaces):

    __<cmd name="renewcommand">
    ____<parm><cmd name="familydefault" gr="0"/></parm>
    ____<parm><cmd name="sfdefault" gr="0"/></parm>

    After TeXMLing:


    I use version 2.0.2. Please check if you really have real spaces (character code 32) in XML, and not unbreakable spaces (code 0xa0).

    2) TeXML is bad for generating document preambles. I recommend to put settings to a sty-file. If you need however to create a preamble, I highly recommend to use the as-is output, without escaping:

    <TeXML escape="0">\renewcommand{\familydefault}{\sfdefault}</TeXML>

    3) TeXML development

    As an XML format, TeXML is finished.

    The hidden TeXML development is reference stylesheets for DocBook and DITA. Something, what man can adapt to own xml structure. Unfortunately, I can’t follow the recommendation “worse is better” and release what I have now. Instead, I want to improve my codebase thanks to experience (TeXML is used in industry) and thanks to new useful features of LaTeX3.

  3. chadnick Says:

    i go on here, because my observation could be interesting for others too.
    first of all, thanx for quick answer and the infos which really helped me a lot.

    I also use version 2.0.2. and I have non-breaking spaces as last element in a line. If i write the whole command in a single line and the texml it it works as you describe. The non-breaking spaces are inserted at the end of the line by eclipse which is use as xml edits. I ‘ll have to investigate the reason for this behaviour.

    All in all the hint concerning the spaces was very helpful and a I can go on without any distrust into TeXML functionality.


Leave a Reply