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: Sun, 25 May 2014 01:15:15 -0700 [thread overview]
Message-ID: <20140525081515.GA3700@trystero> (raw)
In-Reply-To: <01c301cf76ae$04f20270$0ed60750$@tosovsky@email.cz>
Hi Jan,
>What is your real use case? A typical XML based workflow involves XSL-FO ->
>PDF route using FO processor (Antenna House, XEP, FOP etc).
I'm looking to use DITA to publish a literary journal. The journal will contain contributions from multiple authors. I also want to publish works by single authors. I won't make enough (or any) money to justify the very expensive license for Antenna House or XEP, thus they are not really an option. I find FOP to be really sub par.
My basic work flow would have to be DITA XML > DITA OpenToolkit (build process) > ??? > ConTeXt > PDF, where ??? could be some Toolkit XML output, XHTML, HTML5, FO.
>Anyway, there are several ways. If you are not locked to DITA yet, I would
>strongly recommend switching to DocBook instead :-)
The DocBook vocabulary does not fit my needs. TEI is much closer to what I want, but I'm already familiar with DITA.
>This XSLT way is most natural for XML processing, but I understand that
>writing XSLT transformation is discouraging for many people.
Yes, I'm generally OK with working with XSLT. DITA has a build system, called the DITA OpenToolkit that is build with Ant, a bit of java, and XSLT. You can see the toolkit here: http://dita-ot.github.io/
The Toolkit already supports PDF output via FOP, but as I said, FOP leaves quite a bit to be desired.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-05-25 8:15 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
[not found] ` <01c301cf76ae$04f20270$0ed60750$@tosovsky@email.cz>
2014-05-23 18:06 ` Hans Hagen
2014-05-25 8:15 ` Mica Semrick [this message]
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=20140525081515.GA3700@trystero \
--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).