From: Renaud AUBIN <aubin@nibua-r.org>
To: ntg-context@ntg.nl
Subject: Re: XSL-FO to PDF?
Date: Sun, 14 Nov 2010 23:48:44 +0100 [thread overview]
Message-ID: <4CE0674C.6030509@nibua-r.org> (raw)
In-Reply-To: <AANLkTimm5Q-gU=P65s=o5Dgt1HZRg2SaHcwFimcyzNuJ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2700 bytes --]
XSLT is fully adapted to XML/XML(fo or other target schema) since it was
the design basis…
My experience is:
− good xslt is (relatively) easy to design as soon as you master the
underlying data model
− xsltproc is REALLY REALLY fast for xslt 1 processing
− if you want something smarter, go for java with saxon/xerces, which is
performant too…
I'm the devil's advocate but what's your need to use ConTeXt. I have not
read all your threads but if you just need:
− to produce pdfs from xml data
− without advanced typesettings
you could use xslt to produce DocBook 5 xml file, include them using
<xi:include href="./data/stuff.xml"/>, configure your layout with an
intermediate xslt + Fo xml config…
Once more, it depends on your original ecosystem and constraints…
If you provide a use case, I should provide a sample if you don't need
it within a couple of hours (but a couple of days)…
Best regards,
Renaud
Le 14/11/2010 22:36, Peter Davis a écrit :
> On Sun, Nov 14, 2010 at 4:31 PM, Hans Hagen <pragma@wxs.nl> wrote:
>
>
>> On 13-11-2010 4:14, Peter Davis wrote:
>>
>>
>>> On 11/13/10 6:03 AM, Renaud AUBIN wrote:
>>>
>>>
>>>> Uh ? Give FOP a try… http://xmlgraphics.apache.org/fop/1.0/index.html
>>>> Could you describe your target chain ? XML → FO → PDF ?
>>>>
>>>>
>>> Actually, I could write some XSLT to convert the XSL-FO into TeX or
>>> ConTeXt. But I was thinking it might be beneficial to use ConTeXt to
>>> process the XML (XSL-FO) directly ... get it all under one roof, so to
>>> speak.
>>>
>>>
>> faster too
>>
>
> Interesting point. I initially assumed it would be faster to do all my XML
> processing in ConTeXt, but it occurred to me that perhaps using XSLT to or
> even home-grown XML processing, I could generate a stream of TeX that could
> be processed while I'm still producing it. So one process might be looking
> at successive data records and generating TeX for the various pages, and
> another process could be simultaneously running TeX to typeset those pages.
>
>
> Plausible?
>
> Thank you.
>
> -pd
>
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 4048 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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:[~2010-11-14 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 23:22 Peter Davis
2010-11-09 23:56 ` luigi scarso
2010-11-10 11:28 ` Peter Davis
2010-11-10 0:16 ` Hans Hagen
2010-11-10 11:32 ` Peter Davis
2010-11-13 11:03 ` Renaud AUBIN
2010-11-13 15:14 ` Peter Davis
2010-11-14 21:31 ` Hans Hagen
2010-11-14 21:36 ` Peter Davis
2010-11-14 22:48 ` Renaud AUBIN [this message]
2010-11-14 23:17 ` Peter Davis
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=4CE0674C.6030509@nibua-r.org \
--to=aubin@nibua-r.org \
--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).