ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Experience with DITA XML or XSL/FO
Date: Fri, 23 May 2014 19:39:59 +0200	[thread overview]
Message-ID: <15556.9000672132$1400866820@news.gmane.org> (raw)
In-Reply-To: <63c0dc5e-1664-48e2-ab8e-c44fa4ab48d8@email.android.com>

On 2014-05-22 Mica Semrick wrote:
> 
> I've been contemplating making a ConTeXt output or parser for DITA XML
> and was wondering if anyone has worked with DITA and ConTeXt before? If
> you have and could offer any advice and/code, that would be most
> helpful!

What is your real use case? A typical XML based workflow involves XSL-FO ->
PDF route using FO processor (Antenna House, XEP, FOP etc). 

Anyway, there are several ways. If you are not locked to DITA yet, I would
strongly recommend switching to DocBook instead :-) You get similar single
source solution with the semantically rich vocabulary that allows you to
produce all typical outputs. Moreover, there is a special project dedicated
to DocBook to ConTeXt conversion 'dbcontext'
http://dblatex.sourceforge.net/releases/download.html although I had to
tweak it for my recent project to ensure compatibility with current ConTeXt
version (MkIV).

This XSLT way is most natural for XML processing, but I understand that
writing XSLT transformation is discouraging for many people.

Regards, Jan






___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2014-05-23 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 17:11 Mica Semrick
2014-05-22 23:15 ` Hans Hagen
2014-05-22 23:30   ` Mica Semrick
2014-05-23  7:15     ` Hans Hagen
2014-05-23 17:39 ` Jan Tosovsky [this message]
     [not found] ` <01c301cf76ae$04f20270$0ed60750$@tosovsky@email.cz>
2014-05-23 18:06   ` Hans Hagen
2014-05-25  8:15   ` Mica Semrick
2014-05-25 20:26     ` Jan Tosovsky
     [not found]     ` <009c01cf7857$977e5300$c67af900$@tosovsky@email.cz>
2014-05-26  6:50       ` Mica Semrick

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='15556.9000672132$1400866820@news.gmane.org' \
    --to=j.tosovsky@email.cz \
    --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).