From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Cc: "gip.bilotta" <gip.bilotta@iol.it>
Subject: RE: dvipdfmx old-style bug
Date: Mon, 5 Sep 2005 16:57:51 -0600 [thread overview]
Message-ID: <431EF5A3@webmail.colostate.edu> (raw)
workaround:
In cont-sys.tex, change
\loadmapfile[original-public-lm.map]
\loadmapfile[texnansi-public-lm.map]
to
\loadmapfile[original-public-lm.map]
\loadmapfile[texnansi-os-public-lm.map]
\loadmapfile[texnansi-public-lm.map]
Then old-style lm will always be loaded first.
[if you use other than texnansi make analogous changes]
A perhaps drastic workaround but it works for now (reasonable default for the
humanities anyway)...
Best
Idris
======================================================
======================================================
Dear fellows knights of the TeX Table,
I think I have found the source of the problem:
There is a difference between the way aleph and the way pdfetex handle
resetting the map file list:
=========test-os==============
% output=dvipdfmx
% tex=aleph output=dvipdfmx
\loadmapfile[texnansi-os-public-lm.map]
\usetypescript [modern][\defaultencoding]
\usetypescript [map] [latin-modern-os] [\defaultencoding]
\setupbodyfont [modern]
\starttext
123456789
\stoptext
============================
If we just declare
% output=dvipdfmx
then the maps get reset as follows:
=========================
systems : begin file test-os at line 8
fonts : resetting map file list
fonts : using map file: original-base
fonts : using map file: ec-public-lm
fonts : using map file: ec-base
fonts : using map file: original-ams-base
fonts : using map file: original-public-lm
fonts : using map file: texnansi-os-public-lm
fonts : using map file: texnansi-base
fonts : using map file: texnansi-public-lm
==========================
texnansi-os-public-lm gets read _before_ texnansi-public-lm.
But if we declare
% tex=aleph output=dvipdfmx
then the maps get reset as follows:
==========================
fonts : resetting map file list
fonts : using map file: original-base
fonts : using map file: ec-public-lm
fonts : using map file: ec-base
fonts : using map file: texnansi-base
fonts : using map file: qx-base
fonts : using map file: t5-base
fonts : using map file: 8r-base
fonts : using map file: original-ams-base
fonts : using map file: original-ams-euler
fonts : using map file: original-public-lm
fonts : using map file: texnansi-public-lm
fonts : using map file: qx-public-lm
fonts : using map file: t5-public-lm
fonts : using map file: pl0-public-lm
fonts : using map file: il2-public-lm
fonts : using map file: texnansi-os-public-lm
==========================
Note that texnansi-os-public-lm is read last, and _afte_r texnansi-public-lm.
Is this why dvipdfmx does not work for
% tex=aleph output=dvipdfmx
?
NOTE: if we comment out
\loadmapfile[texnansi-os-public-lm.map]
then upon declaring
% output=dvipdfmx
pdfetex will read texnansi-os-public-lm last. I think this is an overall bug
in the latest ConTeXt.
Thus it appears that
\loadmapfile[texnansi-os-public-lm.map]
works for pdfetex (in dvi mode) but not for aleph. Is this because the etex in
aleph is too old?
In the meantime, is there a workaround so that aleph will load
texnansi-os-public-lm.map first?
Best
Idris
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-09-05 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 22:57 Idris Samawi Hamid [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-05 22:38 Idris Samawi Hamid
2005-09-05 21:07 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=431EF5A3@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--cc=gip.bilotta@iol.it \
--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).