From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Shunsaku Hirata <sh74@jcom.home.ne.jp>
Subject: RE: dvipdfmx bug
Date: Sat, 20 Aug 2005 10:30:23 -0600 [thread overview]
Message-ID: <430B001C@webmail.colostate.edu> (raw)
Hi ChoF,
>===== Original Message From Jin-Hwan Cho <chofchof@ktug.or.kr> =====
>One solution might be change the file as follows:
>
>1. Comment out the line 119 as follows:
>
>%\definefileinsertion{dpx}{eps}{\handlepdfimage} % unstable
>
>2. After the line 119 put the following codes.
>
>\def\handleepsimage#1#2#3#4#5#6#7#8#9%
> {\PointsToWholeBigPoints{#7}\width
> \PointsToWholeBigPoints{#8}\height
> \special
> {PSfile="#1"\space
> llx=\EPSllx\space lly=\EPSlly\space
> urx=\EPSurx\space ury=\EPSury\space
> rwi=\width0\space rhi=\height0}}
>
>\definefileinsertion{dpx}{eps}{\handleepsimage}
I did this, regenerated the formats, but it still does not work. My dvipdfmx
comes from mswincontext 16-08-05, but checking the properties of the dvipdfmx
executable indicates that it was created on 08-03-05. Maybe it's too old.
Anyway, hopefully someone can help with an up-to-date executable!
Best
Idris
>
>Another solution is to update spec-dpx.tex and DVIPDFMx if you can
>compile
>it by yourself.
>
>1. Download http://project.ktug.or.kr/dvipdfmx/snapshot/current/
>dvipdfmx-20050815.tar.gz
>
>2. You can download the updated spec-dpx.tex at
>
>http://project.ktug.or.kr/dvipdfmx/contrib/context/spec-dpx.tex
>
>3. Compile dvipdfmx-20050815. Note that the updated spec-dpx.tex works
> with DVIPDFMx version 20050815 or later.
>
>Best, ChoF.
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-08-20 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 16:30 Idris Samawi Hamid [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-20 15:47 Idris Samawi Hamid
2005-08-20 15:42 Idris Samawi Hamid
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=430B001C@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--cc=ntg-context@ntg.nl \
--cc=sh74@jcom.home.ne.jp \
/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).