Idris Samawi Hamid wrote:
Dear Hans, Taco, Chof, and all,
Just installed 051130, and I am happy to report that, so far anyway, dvipdfmx
map files work fine-)
good, thanks for testing
Hans
___
ntg-context mailing list
ntg-context@ntg.nl
Dear Hans and the rest of the gang,
This is just a friendly reminder for the next ConTeXt version. There is a bug
in the ctxtools.
Consider the original-public-lm.map. Lines such as
cmbsy10 cmbsy10
cmbsy5 cmbsy5
cmbsy6 cmbsy7
should become either
cmbsy10 default cmbsy10
cmbsy5 default
Dear gang,
Old style encoding fails with dvipdfmx in the following file (no error
message):
test-os=
%output=dvipdfmx
\usetypescript [modern][\defaultencoding]
\usetypescript [map] [latin-modern-os] [\defaultencoding]
\setupbodyfont [modern]
\starttext
123456789
\stoptext
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
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
Jin-Hwan Cho wrote:
On Aug 19, 2005, at 4:14 PM, Hans Hagen wrote:
i dunno about updmap, never used it; currently i load map files
automatically in dvipdfmx (i could get the mapline special working)
i didn't know the exact dvipdfmx mapfile syntax -)
we can add a slant as follows:
Jin-Hwan Cho wrote:
On Aug 19, 2005, at 7:19 AM, Hans Hagen wrote:
ctxtools --dpxmapfiles --force texmf ctxtools --dpxmapfiles --force
texmf-local ctxtools --dpxmapfiles --force texmf-fonts
will generate them, don't forget to mktexlsr
btw, (new)texexec will automatically run dvipdfmx
On Aug 19, 2005, at 4:14 PM, Hans Hagen wrote:
i dunno about updmap, never used it; currently i load map files
automatically in dvipdfmx (i could get the mapline special working)
i didn't know the exact dvipdfmx mapfile syntax -)
we can add a slant as follows:
encoding = if line =~
Dear crew,
Ok, I've got things working so far on the upgrade; the engine path works and I
can use one command for both aleph and pdfetex; hooray!
but...
Default dvipdfmx configuration is not right. Consider the following three
scenarios:
1.
==test-upgrade.tex
%
During processing, I get
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
Idris Samawi Hamid wrote:
Dear crew,
Ok, I've got things working so far on the upgrade; the engine path works and I
can use one command for both aleph and pdfetex; hooray!
but...
Default dvipdfmx configuration is not right. Consider the following three
scenarios:
ctxtools --dpxmapfiles
On Aug 19, 2005, at 7:19 AM, Hans Hagen wrote:
ctxtools --dpxmapfiles --force texmf ctxtools --dpxmapfiles --force
texmf-local ctxtools --dpxmapfiles --force texmf-fonts
will generate them, don't forget to mktexlsr
btw, (new)texexec will automatically run dvipdfmx
ctxtools does not make
Dear folks,
The dvips/dvipdfmx problem is not limited to aleph in the latest ConTeXt:
===test-3==
\setupoutput[dvi]
\starttext
abc
\stoptext
===
gives
===
$dvipdfmx test3
test3.dvi - test3.pdf
[1** Fatal error: Could not
13 matches
Mail list logo
