ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Example ConTeXt document: PS output
Date: Mon, 12 Jul 2010 10:58:44 +0200	[thread overview]
Message-ID: <4C3AD944.7070002@wxs.nl> (raw)
In-Reply-To: <AANLkTilFk81V-GKtGeilZUvSGXTO1qrQlHc8QVD5cSpk@mail.gmail.com>

On 11-7-2010 7:39, luigi scarso wrote:
> 2010/7/11 Ivo Solnický<ivo.solnicky@gmail.com>:
>>>
>>> Now (not addressed to Mojca), please don't be a smartarse and tell me
>>> (again) that this is all volunteer work and to send in patches, a new
>>> Device Independent file definition and implementation for Unicode.
>>> I'm full of admiration for you guys with the giant IQs who have
>>> created ConTeXt in tea breaks and at night, never taken a second of
>>> time from the employer, publishing house or university or hairdressing
>>> salon proprietor that pays you.  But I don't pretend to be in that
>>> class.  I'm just a mental midget.  And I have other things to do.  It
>>> ain't my project.  Something else is.
>>>
>>
>> Maybe LuaLaTeX should work for you.
> But even so there is a dvi-to-ps step to do,
> which is pratically the same of pdf-to-ps
> in context mkiv.

one of the reasons behind pdf is that it takes the programming language 
out of ps which means (1) better portability, (2) faster rendering

in addition to that pdf provides a couple of goodies irrelevant to 
printers (annotations and such)

dvi as outputformat is fine, but you then need to inject extra code for 
each (fundamentally) different backend

tex + specials -> dvi -> ps -> pdf
tex + specials -> dvi -> pdf
tex + literals -> pdf (pdftex)

now, as ps is seldom needed as final format it makes no sense generate 
it (and going from pdf -> ps is easy)

using specials (inlined code) is no fun but has alway sbeen supported in 
mkii (spec-* files) using an intermediate layer

in mkiv we have

tex -> pdf

so no specials and hardly any literals at the tex which is much cleaner; 
of course there can be more backends but a ps one is unlikely

although in principle mkiv could be made to provide dvi to be fed in 
some backend driver i see no advantage in that

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2010-07-12  8:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 15:46 Michael Talbot-Wilson
2010-07-09 16:06 ` luigi scarso
2010-07-09 18:49   ` Vedran Miletić
2010-07-10  2:46     ` Michael Talbot-Wilson
2010-07-10  3:30       ` luigi scarso
2010-07-10  3:32       ` Michael Talbot-Wilson
2010-07-10  3:37         ` luigi scarso
2010-07-10  5:46           ` Michael Talbot-Wilson
2010-07-10  6:42             ` Taco Hoekwater
2010-07-10 14:28             ` Martin Schröder
2010-07-10 22:07         ` Aditya Mahajan
2010-07-10 12:34 ` Peter Münster
2010-07-10 21:42 ` Mojca Miklavec
2010-07-10 22:21   ` Martin Schröder
2010-07-11 11:25     ` Vnpenguin
2010-07-11 16:43     ` Michael Talbot-Wilson
2010-07-11 17:28       ` Ivo Solnický
2010-07-11 17:39         ` luigi scarso
2010-07-11 20:37           ` Henning Hraban Ramm
2010-07-11 20:53             ` Khaled Hosny
2010-07-11 21:25               ` Henning Hraban Ramm
2010-07-12  8:58           ` Hans Hagen [this message]

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=4C3AD944.7070002@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).