ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mica Semrick <mica@silentumbrella.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Experience with DITA XML or XSL/FO
Date: Thu, 22 May 2014 16:30:45 -0700	[thread overview]
Message-ID: <260ffc8a-2dfb-4cdd-881b-0305ef4c70b7@email.android.com> (raw)
In-Reply-To: <537E84F4.5090101@wxs.nl>

Hi Hans,

Thanks for your reply. I found my way to foxet, but never got it working. I've written several mapping files for XML with good results, but DITA is a bit of a different beast. 

DITA is geared towards technical writing, and its main features are defined content types, a mechanism for controlled reuse below the file level, a modular structure, and built in extensibility of its XML vocabulary. It comes with its own toolkit that filters out and pulls in content and it uses FOP to produce PDF (hence my mention of FO). Since the toolkit must process the XML to resolve linked content and remove content, it is not recommended to directly typeset the XML like you could do with DocBook. I see a few ways to achieve what I want, which is a PDF produced my ConTeXt: target a merged XML file that the dita toolkit has produced, produce a concatenated HTML file and typeset that, or typeset the fo file before FOP gets to it. Of those approaches, the first seems like the best idea,
  but I wanted to query the list before proceeding.

Thanks for your time.

Best,
Mica
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2014-05-22 23:30 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 [this message]
2014-05-23  7:15     ` Hans Hagen
2014-05-23 17:39 ` Jan Tosovsky
     [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=260ffc8a-2dfb-4cdd-881b-0305ef4c70b7@email.android.com \
    --to=mica@silentumbrella.com \
    --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).