From: Pierre Boulet <Pierre.Boulet@lifl.fr>
To: "Jun P.FURUSE" <Jun.Furuse@inria.fr>
Cc: luther@dpt-info.u-strasbg.fr, remy@morgon.inria.fr,
willb@cs.wisc.edu, caml-list@inria.fr, advi-bugs@inria.fr
Subject: Re: [Caml-list] ActiveDVI and fullscreen?
Date: 04 Mar 2002 11:37:52 +0100 [thread overview]
Message-ID: <1015238272.21698.15.camel@caffreys.lifl.fr> (raw)
In-Reply-To: <20020304.111326.730549239.Jun.Furuse@inria.fr>
> > but it may well be that this problem persist, as i was not able to view one of
> > my dvi files). The report was about problems when previewing dvi files which
> > contain postscript fonts (Times), and not finfing them (noting that xdvi
> > shows them without problem).
> >
> > Is this the normal behavior, or is something wrong about it.
>
> Sorry. Currently, ADVI can handle pk-fonts only. Postscript fonts are
> not supported. They can be easily supported, if someone writes a
> rasterizer of postscript fonts...
gsftopk does the job and is called by xdvi to generate the pk fonts.
IMHO, what needs to be written is a decoder for virtual fonts and to
generate the right call to gsftopk.
--
Pierre.Boulet@lifl.fr - http://www.lifl.fr/~boulet
Toute technologie suffisamment avancée est
indiscernable de la magie. -- Arthur C. Clarke
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-03-04 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 22:05 Will Benton
2002-03-01 7:38 ` Didier Remy
2002-03-04 9:49 ` Sven
2002-03-04 10:11 ` Pierre Boulet
2002-03-04 10:13 ` Jun P.FURUSE
2002-03-04 10:36 ` Sven
2002-03-04 11:18 ` Achim Blumensath
2002-03-04 10:37 ` Pierre Boulet [this message]
2002-03-01 15:49 Roberto Di Cosmo
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=1015238272.21698.15.camel@caffreys.lifl.fr \
--to=pierre.boulet@lifl.fr \
--cc=Jun.Furuse@inria.fr \
--cc=advi-bugs@inria.fr \
--cc=caml-list@inria.fr \
--cc=luther@dpt-info.u-strasbg.fr \
--cc=remy@morgon.inria.fr \
--cc=willb@cs.wisc.edu \
/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).