From: "luigi scarso" <luigi.scarso@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: "Announcing: XPSTeX" . A joke. Really ?
Date: Fri, 13 Apr 2007 11:01:37 +0200 [thread overview]
Message-ID: <fe8d59da0704130201m234fb72fg67186d847b0b3413@mail.gmail.com> (raw)
ok, it's a joke
http://article.gmane.org/gmane.comp.tex.pdftex/3404
(but the best is
http://www.google.com/tisp/
)
But my question is:
Will be "easy" in luatex to implement a new output format
(dvi,pdf,xps,<<my-xml>>,<<my-bin-format>>)
driven by command line ?
Actually
$>texmfstart texexec --pdf a.tex ==> a.pdf
$>texmfstart texexec a.tex ==> a.dvi
ie, tex=>pdf or tex=>dvi
because pdftex has two native output format.
Of course one can use workflows tex=>dvi=>ps=>pdf
tex=>dvi=>html by external tools,
or one can write a tex macro that write on file whatever one wants,
but it's not what I mean.
luigi
next reply other threads:[~2007-04-13 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 9:01 luigi scarso [this message]
2007-04-13 11:23 ` Hans Hagen
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=fe8d59da0704130201m234fb72fg67186d847b0b3413@mail.gmail.com \
--to=luigi.scarso@gmail.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).