From: "R. Ermers" <r.ermers@hccnet.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: DocBook in ConTeXt - any new ideas?
Date: Fri, 3 Jun 2011 17:43:09 +0200 [thread overview]
Message-ID: <D8AA4B5F-9995-469B-A466-055DD0AE3133@hccnet.nl> (raw)
In-Reply-To: <4DE7F098.2040408@wxs.nl>
I tried typesetting docbook with Context, it can be done, I but got stuck on the cals tables and some other things. Cals tables can be processed, albeit as separate documents only - not as part of the docbook file - and then imported as pdf files. This was too cumbersome for me, and does not agree with the tex philosophy. I therefore gave up.
For some reason finetuning of, for example, the positioning of graphics, and headers as widows is more difficult than in a context document, at least I got this impression.
Robert
Op 2 jun 2011, om 22:20 heeft Hans Hagen het volgende geschreven:
> On 2-6-2011 7:17, Bruce wrote:
>> Hans Hagen<pragma<at> wxs.nl> writes:
>>
>>>
>>> On 2-6-2011 12:53, Piotr Kopszak wrote:
>>>> Many thanks for your reply! I would certainly go this way having a
>>>> couple of months or a year perspective. Besides I'm eager to try
>>>> finally the new way mkIV deals with xml. But realistically, preparing
>>>> and testing a mapping of even a subset of DocBook is a question of at
>>>> least a couple of personmonths if not worse. Sadly, I'm not in a
>>>> position to that now.
>>>
>>> Months? I never had a reason for doing a docbook mapping but a couple of
>>> hours should get you a start. Th eonly reason why I'd look into docbook
>>> is if I'd need in in a project. (I'd happily spent a few well paid
>>> months on it then.)
>>>
>>> You probably don't need all of docbook, so you could start with some
>>> simple tests. The mkii docbook stuff you mentioned definitely is doing a
>>> small subset.
>>
>> I never understand why you would try to typeset XML directly in ConTeXt?
>> Why not just convert the DocBook to ConTeXt source using XSLT (or if the
>> docs are simpler, use markdown with pandoc and you can easily get ConTeXt
>> and HTML from the same source)?
>
> (1) because xslt mappings can become pretty unreadable
> (2) because you still need to make a file (and define environments)
> (3) because it then create another depencency and intermediate processing stage
> (4) because sometimes it makes sense to let the typesetting engine make decisions
> (5) because in mkiv one can apply lua functions to xml content
> (6) ...
>
> anyhow, the whole idea of xml is that it can be processed by whatever machinery (and using xslt and/or xsl-fo for everything kin dof contradicts that)
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
> | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-06-03 15:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 9:39 Piotr Kopszak
2011-06-02 10:20 ` Thomas Schmitz
2011-06-02 10:53 ` Piotr Kopszak
2011-06-02 12:03 ` Hans Hagen
2011-06-02 17:17 ` Bruce
2011-06-02 20:20 ` Hans Hagen
2011-06-03 15:43 ` R. Ermers [this message]
2011-06-03 16:28 ` Hans Hagen
2011-06-04 8:21 ` R. Ermers
2011-06-04 9:06 ` Hans Hagen
2011-06-04 9:57 ` R. Ermers
2011-06-04 12:24 ` Aditya Mahajan
2011-06-04 13:25 ` R. Ermers
2011-06-05 10:46 ` Hans Hagen
2011-06-02 11:58 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D8AA4B5F-9995-469B-A466-055DD0AE3133@hccnet.nl \
--to=r.ermers@hccnet.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).