![](https://secure.gravatar.com/avatar/6af53106eba96baffa28cca99fbd221f.jpg?s=120&d=mm&r=g)
Bruce D'Arcus (bdarcus@fastmail.fm) wrote:
As was already explained (a few times):
You customize output just as you customize ANY ConTeXt output. There's no need for a tex output file.
Ahh.. It seems that we have communication breakdown. When I say "*.tex" I mean ConTeXT input file, not TeX file and what I would like is that DocBookInConTeXt module produce valid ConTeXt file which is the result of applying mapping from DocBook to ConTeXt, ie. physical file not on-the-fly converting. The whole meaning of using ConTeXt (or LaTeX) is to avoid direct TeX typesetting and makes process easier, so I definitely never though about TeX output file. And the question remains: how to customize output when the translation is done internally? Sincerely, Gour ps. It seems I'm too stupid at the moment to understand the issue :-(( -- Gour gour@mail.inet.hr Registered Linux User #278493