From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt ML <ntg-context@ntg.nl>
Subject: Re: XSL-FO
Date: Fri, 28 Dec 2001 10:55:41 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20011228104722.03ee6ae8@server-1> (raw)
In-Reply-To: <20011227171201.GA1641@localhost>
At 05:12 PM 12/27/2001 +0000, Marco Kuhlmann wrote:
> Hi all.
>
>Has anyone any experience with XSL-FO? Is it a standard that is
>far enough to be used in preparing print layouts? For example,
>does it have the same expressivity as ConTeXt? Would it be
>possible and meaningful to implement a ConTeXt backend for
>formatting objects? There are programs like passivetex; how
>easy would it be to implement something similar in ConTeXt?
>
>Any hints would be appreciated.
(also see berends reply)
afaik formatting object is like putting boxes together;
xml -> (with xslt) xml-fo -> tex -> pdf
in many cases (esp when dealing with documents) the xml-fo stage is not
needed at all;
so far i never ran into an fo, but i may some day as part of a doc (i can
imagine that for instance sub apps spit out fo's); in that case an extended
version of \framed is probably enough to implement it; when the moment is
there, i will probably cook up such an extended framed, but it's low on my
list of priorities [but you may expect much more xml support next year in
context]
taco may have more to say about this since he's working with fo's
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-12-28 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 17:12 XSL-FO Marco Kuhlmann
2001-12-27 18:01 ` XSL-FO Berend de Boer
2001-12-28 9:55 ` Hans Hagen [this message]
2001-12-30 12:03 ` XSL-FO Simon Pepping
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=5.1.0.14.1.20011228104722.03ee6ae8@server-1 \
--to=pragma@wxs.nl \
--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).