ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Context against XSL
Date: Fri, 01 Oct 2004 11:25:32 +0200	[thread overview]
Message-ID: <415D228C.90905@wxs.nl> (raw)
In-Reply-To: <20041001085220.26813ea0.taco@elvenkind.com>

Taco Hoekwater wrote:

> Hans Hagen <pragma@wxs.nl> wrote:
> 
> 
>>I'm on and off implementing an fo engine (foxet) and run into fuzziness 
>>with regards to the specs (a bad omen is that that there i could not 
>>find a good manual and the ones i have are made up rather poorly, which 
>>indicated that we're not so much dealing with high end typesetting, but 
>>with regular batchprocessing of not too complex documents).
> 
>  
> The longer one has to read in the XSL-FO specification, the more one 
> resents having to do so. If you are lookiing for a road towards creating 
> pdf documents, then ConTeXt is like an actual freeway with perhaps a few 
> potholes and missing roadsigns, where XSL-FO is a set of directions on how 
> to create a jungle road, written down by a civil engineer with terrible
> handwriting mirroring a quite chaotic mind who nonetheless insists on 
> doing everything "the right way"(tm). 

you're right! unfortunately those engineers can ride on the back of the 
horse with xml painted all over it, which makes it good by principle for 
those who pay them; an interesting aspect of this is that while xml 
opens many roads, the tendensy is towards taking one road; there is 
probably some thinking behind this that we suddenly can solve all 
problems for ever and do with one road.

btw, as with much xml related things: much of what is around as 
'standard' is actually just a reversed engineered application interface, 
or worse: serving as an interface to different applications which makes 
it fuzzy; take xsl: there are a lot of dupplicate attributes just to 
serve css; this is strange because the whole idea behind xslt (which is 
mostly ok) is that one can transform, so there is no need for those 
duplicates. The engineer serves to many masters.

apart from the specs, fo lacks a real proper box model: (like css, there 
is no real way to do for instance vertical alignment comparable with 
tex's fill's); it somehow started from the wrong angle;  and then .. how 
about math, chemistry, etc -) a long road ahead

> Various people have been busy trying to build that road according to the 
> specifications, and some of the toll (payfare) roads are in fact reasonably 
> close. I'm speaking with a certain fondness in my voice really, because I 
> am also busy implementing a (commercial) fo engine using ConTeXt.

-)

comparisons between the not-taco engines show big differences (also in 
price) and as soon as extensions start coming into the picture, the 
'acclaimed advantage of fo' disappears. Some peeople pay five digit 
numbers for engines where formulas has to be included as graphic.

I sometimes wonder if it makes sense to cook up an alternative model on 
top of context -)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2004-10-01  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 14:43 Dirar Bougatef
2004-09-30 19:06 ` Hans Hagen
2004-09-30 20:53   ` Dirar Bougatef
2004-09-30 22:35     ` Hans Hagen
2004-10-01  6:52   ` Taco Hoekwater
2004-10-01  9:25     ` Hans Hagen [this message]
2004-10-01 10:53       ` Nikolai Weibull
2004-10-01 17:18         ` Matt Gushee

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=415D228C.90905@wxs.nl \
    --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).