From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: MkIV and DVI output
Date: Mon, 14 Apr 2008 11:06:36 +0200 [thread overview]
Message-ID: <115224fb0804140206o23d84c84ia094acb586799800@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00804130601p79ede46i1a4ee106d8dac67f@mail.gmail.com>
On Sun, Apr 13, 2008 at 3:01 PM, Mojca Miklavec
<mojca.miklavec.lists@gmail.com> wrote:
> On Fri, Apr 11, 2008 at 11:45 AM, Hans Hagen wrote:
> > Wolfgang Schuster wrote:
> > > Hi,
> > >
> > > is it possible to produce DVI files with Mark IV.
> > >
> > > I tried a simple file like
> > >
> > > \starttext
> > > text
> > > \stoptext
> > >
> > > with the command texexec --lua --backend=dvipdfm filename
> >
> > no, at quite some places i've hardcoded a pdftex backend
> >
> > at some point i will redo the backends, but i wonder if it really makes
> > sense to support dvi any longer; i'd rather prepare for future formats
>
> Hello Wolfgang (and others),
>
> I don't know if anyone has noticed it, but XeTeX "doesn't support" dvi
> format either. It can create some intermediate format (xdv), but it's
> rather useless - I don't know any software that can work with it. And
> even if LuaTeX would support dvi, you still need to write support for
> fonts in DVI previewers. (DVI=DeVice Independent - something that
> would definitely not be true any more with OpenType fonts; or rather -
> is not even true any more at this moment with dozens of PS specials)
Hi Mojca,
I know xdv is only a intermediate format in XeTeX and xdv2pdf and
xdvipdfmx are able to convert it into PDF format. I used always only the
pdftex backend for ConTeXt and used dvi only to play with a few macro
files where I needed it because they used PostScript to draw lines ...
I have also no dvi viewer on my system and I'm inable to take a look
at the output in dvi format.
I tried to play only a little bit with MkIV and dvi but I never wanted to
use it in real live, I tried only something what is at the moment only
possible with dvi output.
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2008-04-14 9:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 9:28 Wolfgang Schuster
2008-04-11 9:45 ` Hans Hagen
2008-04-11 14:34 ` luigi scarso
2008-04-11 14:55 ` Martin Schröder
2008-04-11 23:20 ` luigi scarso
2008-04-11 15:24 ` Olivier Guéry
2008-04-11 16:04 ` Taco Hoekwater
2008-04-12 7:16 ` Hans Hagen
2008-04-12 10:43 ` Olivier Guéry
2008-04-11 15:36 ` Hans Hagen
2008-04-11 16:10 ` luigi scarso
2008-04-12 7:13 ` Hans Hagen
2008-04-13 13:01 ` Mojca Miklavec
2008-04-14 9:06 ` Wolfgang Schuster [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=115224fb0804140206o23d84c84ia094acb586799800@mail.gmail.com \
--to=schuster.wolfgang@googlemail.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).