ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XSL-FO to PDF?
Date: Sun, 14 Nov 2010 16:36:06 -0500	[thread overview]
Message-ID: <AANLkTimm5Q-gU=P65s=o5Dgt1HZRg2SaHcwFimcyzNuJ@mail.gmail.com> (raw)
In-Reply-To: <4CE0553A.7020605@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1070 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 1712 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
___________________________________________________________________________________

  reply	other threads:[~2010-11-14 21:36 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 [this message]
2010-11-14 22:48         ` Renaud AUBIN
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='AANLkTimm5Q-gU=P65s=o5Dgt1HZRg2SaHcwFimcyzNuJ@mail.gmail.com' \
    --to=pfd@pfdstudio.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).