ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XSL-FO to PDF?
Date: Wed, 10 Nov 2010 06:32:09 -0500	[thread overview]
Message-ID: <AANLkTin_t4nbF7iMkqUM79PpcCax=Opbc_cj1d3jVMWX@mail.gmail.com> (raw)
In-Reply-To: <4CD9E470.1000708@wxs.nl>


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

On Tue, Nov 9, 2010 at 7:16 PM, Hans Hagen <pragma@wxs.nl> wrote:

> On 10-11-2010 12:22, Peter Davis wrote:
>
>> Is there some recent information on using XML, and specifically XSL-FO,
>> with
>> ConTeXt?  The pages on the contextgarden wiki appear to be 5 years old or
>> more, and even the archive of this list seem pretty sparse on recent
>> information.
>>
>> I'm trying to find the most direct route from XSL-FO to PS or PDF. I'll be
>> generating hundreds or thousands of XSL-FO documents, and would like to
>> process them.
>>
>
> there was never much interest in FO and usually such code only gets better
> when it's used; I have it on my todo list to rewrite the mkii specific FO
> processing code in mkiv as it can be done more efficient etc etc but there
> is not that much incentive ... in projects that I'm involved in we normally
> go directly from xml to pdf simply because it's faster, gives better results
> and takes less coding than going the fo-route; and as FO is not that much
> fun, I'd either need a project or see it as a challenge (btw, it's not that
> big a deal to rewrite the mkii code to mkiv)
>
> Hans
>


Thanks, Hans.  I can certainly understand that FO has not gotten much
attention.  In our case, though, this is the XML format we're starting with.
 It's not a matter of converting other xml to FO.  I'd be happy to look at
the mkii code, but considering that I'm brand spanking new to ConTeXt, I
don't expect to make any great strides there for a while.

Is it possible to put a setup inside an xmlsetup?  For example, if the xml
specifies a page size, can I put a setup for that inside the xmlsetup that
handles that element?

Thank you,
-pd

[-- Attachment #1.2: Type: text/html, Size: 2222 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-10 11:32 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 [this message]
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
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='AANLkTin_t4nbF7iMkqUM79PpcCax=Opbc_cj1d3jVMWX@mail.gmail.com' \
    --to=pfd@pfdstudio.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).