From: Dalyoung <haksan@mac.com>
Subject: Re: some patches
Date: Tue, 16 May 2006 20:10:28 +0900 [thread overview]
Message-ID: <28500B95-972B-490E-8C87-A655893B01ED@mac.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 872 bytes --]
>
for xetex you really need to update because the backend driver has
changed to xpdfmx
Hans
Dear Hans,
Thank you for the reply.
I'll upgrade to the latest version soon.
By the way, I noticed one thing in the process of XeTeX-ConTeXt.
In the previous version before may, "texexec --xtx file.tex" run and
made file.xdv, and then finally produced file.pdf.
But in the current version "texmfstart texexec --xetex file.tex" run
and file.tuo - file.dvi - file.pdf are produced in the log file but
file.pdf is not produced in the folder. "texexec --xtx file.tex"
also produced pdf via *.tuo - *.dvi - *.pdf but figures in pdf format
are appeared as blank space.
Doesn't ConTeXt-XeTeX use *.xdv anymore?
I'd like to upgrade from the beginning, TeX+ConTeXt update + XeTeX
and test the same file.
It makes me a little bit nervous.
Thank you again.
Dalyoung
[-- Attachment #1.2: Type: text/html, Size: 4175 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2006-05-16 11:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 11:10 Dalyoung [this message]
2006-05-16 17:15 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2006-05-16 4:33 Dalyoung Jeong
2006-05-16 7:47 ` Hans Hagen
2006-05-15 15:34 Dalyoung
2006-05-15 16:03 ` Hans Hagen
2006-05-15 7:23 Hans Hagen
2006-05-15 7:29 ` Gilles Pérez-Lambert
2006-05-15 7:45 ` Sanjoy Mahajan
2006-05-15 8:25 ` Maurice Diamantini
2006-05-15 8:59 ` Hans Hagen
2006-05-15 9:58 ` Taco Hoekwater
2006-05-15 15:31 ` Gerben Wierda
2006-05-15 23:21 ` frantisek holop
2006-05-16 7:41 ` 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=28500B95-972B-490E-8C87-A655893B01ED@mac.com \
--to=haksan@mac.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).