August 2005 - ntg-context - NTG Mailing Lists

ConTeXt in MikTeX distribution
by jjgod 21 Aug '05

21 Aug '05

Hello, I've just updated my MikTeX distribution, which use a 2005-07-12 version of context package. Since then MikTeX could not generate the cont-en format file, when I use texexec --make en, it reports TeX capacity not enough, so I have to modify the localtexmf/miktex/config/miktex.ini file, change |trie_op_size from 2048 to 4096. The second problem is about texfont. When texfont installing Type1 fonts, it use '-p' option of afm2tfm to collect some infomation, but it seems in the afm2tfm source code of MikTeX, -p only works when libkpathsea enabled, otherwise afm2tfm will crash. (without kpathsea support, afm2tfm will only looking for .enc in current directory instead of the directory configured in miktex.ini. Some users in this mail-list may have reported this problem). Current afm2tfm executable file from MikTeX was compiled without libkpathsea support, so when texfont tries to || my $command = "afm2tfm \"$file\" -p texnansi.enc texfont.tfm"; afm2tfm crashed and texfont failed to collect infomation into the $cleanfont variable. So I suggest the maintainer of context avoid using the -p option, it seems ||afm2tfm \"$file\" texfont.tfm| | does the same job in this piece of code. Another problem is that some font vendor distribute their font files in captial letters, such as BIRKA___.PFB, it cause the copy_files routine in texfont.pl failed to copy those pfb files to correct texmf directory. Regards, jjgod. |

4 5

dvipdfmx
by Idris Samawi Hamid 21 Aug '05

21 Aug '05

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================ % output=dvipdfmx \starttext Test \stoptext ============================================== gives ============================================== texexec test-upgrade TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005 fixing engine variable : pdfetex executable : pdfetex format : cont-en inputfile : test-upgrade output : dvipdfmx interface : en current mode : none TeX run : 1 This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2c 7.5.3) : test-upgrade.dvi -> test-upgrade.pdf [1 ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: rsfs7 rsfs5 <rs fs7.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-base.map", line =3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: ec-lmb10 LMRomanDemi10-Regular <ec-lm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="ec-public-lm.map", line= 1. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: ucrb8t NimbusMonL-Bold <ec.e nc <ucrb8a.pfb ** WARNING ** -- Reading fontmap file stopped at: file="ec-base.map", line=3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: lasy5 LASY5 <lasy5.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-ams-base.map", line=1. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: cmb10 CMB10 <cmrm.enc <lmb10. pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-public-lm.map", line=68. ** WARNING ** Could not locate a virual/physical font for TFM "ec-lmr12". ** WARNING ** There are no valid font mapping entry.... ** ERROR ** Cannot continue... Output file removed. ============================================== 2. Now if I use the following DVIPDFMX.EXE -f context-base.map.dvipdfmx test-upgrade I get a pdf file but still =============================================== C:\docs\Projects\Introislam\test>DVIPDFMX.EXE -f context-base.map.dvipdfmx test -upgrade test-upgrade.dvi -> test-upgrade.pdf [1 ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: rsfs7 rsfs5 <rs fs7.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-base.map", line =3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: ec-lmb10 LMRomanDemi10-Regular <ec-lm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="ec-public-lm.map", line= 1. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: ucrb8t NimbusMonL-Bold <ec.e nc <ucrb8a.pfb ** WARNING ** -- Reading fontmap file stopped at: file="ec-base.map", line=3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: lasy5 LASY5 <lasy5.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-ams-base.map", line=1. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: cmb10 CMB10 <cmrm.enc <lmb10. pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-public-lm.map", line=68. ] 2927 bytes written =============================================== 3. Finally, even compiling a total arabic document with no lmr at all gives me an ok arabic pdf, but I still get =============================================== testarabic.dvi -> testarabic.pdf [1 ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: rsfs7 rsfs5 <rs fs7.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-base.map", line =3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: ec-lmb10 LMRomanDemi10-Regular <ec-lm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="ec-public-lm.map", line= 1. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: ucrb8t NimbusMonL-Bold <ec.e nc <ucrb8a.pfb ** WARNING ** -- Reading fontmap file stopped at: file="ec-base.map", line=3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: qcrb <qcr.enc <qcrb.pfb ** WARNING ** -- Reading fontmap file stopped at: file="qx-base.map", line=3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: ucrr8v VnNimbusMonL-Regu "T5Encoding ReEncodeFont" <t5.enc <ucrr8v.pfb ** WARNING ** -- Reading fontmap file stopped at: file="t5-base.map", line=3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: ucrb8r NimbusMonL-Bold <8r.e nc <ucrb8a.pfb ** WARNING ** -- Reading fontmap file stopped at: file="8r-base.map", line=3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: lasy5 LASY5 <lasy5.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-ams-base.map", line=1. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: euex10 EUEX10 <euex10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-ams-euler.map", line=1. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: cmb10 CMB10 <cmrm.enc <lmb10. pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-public-lm.map", line=68. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: texnansi-lmb10 LMRomanDemi10-Regula r <texnansi-lm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="texnansi-public-lm.map", line=1. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: qx-lmb10 LMRomanDemi10-Regular <qx-lm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="qx-public-lm.map", line= 1. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: vnb10 LMRomanDemi10-Regular <t5-lm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="t5-public-lm.map", line= 3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: plb10 LMRomanDemi10-Regular <plrm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="pl0-public-lm.map", line =3. ** WARNING ** This .map file looks like using dvips format. ** WARNING ** -- Current input buffer is: csb10 LMRomanDemi10-Regular <csrm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="il2-public-lm.map", line =3. ] 3151 bytes written =============================================== Advice please-) Best Idris ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

3 5

Dense Encoding - Comments wanted
by Adam Lindsay 21 Aug '05

21 Aug '05

Hi all, On Hans's suggestion, I've been working on a "dense" character encoding that does away with combining accents and extraneous symbol-like characters in favor of fully accented characters. <http://homepage.mac.com/atl/tex/dense.pdf> This encoding is sort of based on the EC encoding, but adds (to the best of my knowledge) support for Romanian, Maltese, Welsh, Lithuanian, and Latvian. The punctuation that I kept was "typographic" in nature, that would fall within a normal text flow, especially those affected by ligatures and/or kerns. The typographic symbols were left out, including monetary symbols. I reckon these could be called as symbols from another encoding. The general intent here is to have strong support for (latin script) modern European languages, in the context of Unicode input. I concentrate on letters, in order to give as good kerning as possible with a 256 character subset. The letters are fully composed, to help hyphenation within TeX. Note that the encoding can't handle general transliteration or other "academic" uses. So with those goals in mind, does anyone notice their favorite *letter* missing? Is there essential punctuation missing? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl(a)comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

4 6

mswincontext and dvipdfmx bug
by Idris Samawi Hamid 21 Aug '05

21 Aug '05

Dear gang, I need your help. If anyone is using a recent mswincontext.zip, could you check the dvipdfmx executable with the attached test, spec, and eps file. The problem here is that dvipdfmx freezes when processing fig-test.dvi. I'm trying to determine if this is due to a misconfiguration on my part or whether this is a mswincontext problem. I HOPE it's an mswincontext problem because I have no idea where the misconfiguration can be. Note the modified spec-dpx file. Just place it in the working directory (per ChoF's instructions). I appreciate anyone's help: this is critical because I have a late journal issue that depends on the aleph-dvipfmx cycle. Thnx in advance and all the Best Idris >===== Original Message From Jin-Hwan Cho <chofchof(a)ktug.or.kr> ===== >In my platform Mac OS X, your fig-test.dvi had no problem. I've >tested it >with DVIPDFMX-20050201, 20050627, 20050815. All three versions had no >problem. ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

1 0

[st]cedilla vs. [st]commaaccent
by Mojca Miklavec 21 Aug '05

21 Aug '05

Hello, After Hans/Taco succesfully fixed the \dstroke problem (and it already seemed that I will stop annoying for a while ;), I noticed another strange behaviour after the discussion on tex-font mailing list. (Adam: the discussion seems to have brought some benefit after all :) Can someone take a look into the difference between [st]cedilla and [st]commaaccent? I have a strange feeling that something is wrong in the way ConTeXt renders them. \tcedilla, \scedilla both expand into what should be \tcommaaccent and \scommaaccent. The four definitions in enco-def.tex are OK: \definecharacter Scedilla {\buildtextcedilla S} \definecharacter scedilla {\buildtextcedilla s} \definecharacter Tcedilla {\buildtextcedilla T} \definecharacter tcedilla {\buildtextcedilla t} ... but they are lost somewhere. I don't know where they turn into "commaaccent"-ed ones if texnansi encoding is used (in ec endoding they are present and (wrongly?) mapped to [st]commaaccent). But these four definitions are probably strange: \definecharacter scommaaccent {s\quoteright} \definecharacter Scommaaccent {S\quoteright} \definecharacter tcommaaccent {t\quoteright} \definecharacter Tcommaaccent {T\quoteright} Is there a good way to render (=fake) them properly? If yes (I think they are properly faked at some place already, at least in texnansi if nowhere else), than also kcommaaccent, lcommaaccent, ncommaaccent and rcommaaccent can be added to these four definitions (gkommaaccent seems to be slightly different). One question arises however. In Unicode reference it states that tcedilla is a deprecated glyph in Romanian and that tcommaaccent should be used instead. It seems that ConTeXt does exactly that at the moment (Adobe screwed up in their glyph list anyway), but in my opinion \tcedilla should stand for "t with cedilla" no matter what is deprecated and what not. Let's not repeat the Adobe's mistake! It should be documented somewhere (in the wiki?) that if someone insists in automatically mapping tcedilla to tcommaaccent, this can be done in a few lines, but this should not be the default behaviour. We can perhaps map \c{t} or "t to tcedilla if needed instead? (I may be wrong here - I'm ignorant in this field.) This *does* "break backward compatibility" in a way, the documents using tcedilla/scedilla/... won't be the same any more if files are fixed, but I don't believe that anyone wants to follow the way thing are solved in LaTeX and ask the users to use \twithrealcedilla or something similar instead. I tried to figure out if any language uses "tcedilla" and I didn't find any useful information about that yet (except, if I understood correctly, sometimes in Romanian->English transliterations). So I ask myself: why do cp1250 and iso latin2 have tcedilla instead of tcommaaccent if nobody uses the first one??? Btw: in anco-ans.tex, \textcedilla maps to character 184 "instead of" character 24. With \definetypeface[antykwa][rm][serif][antykwa-torunska][default][encoding=texnansi] \setupbodyfont[antykwa] this fails because texnansi-antt.enc has a .notdef at slot 184 (perhaps this .enc file could be "fixed" as well, if I may call that "fixing"). It would be great if someone from Romania or Turkey would be reading that and could say a word about it. All the information I have are the (fuzzy) standards, full of mistakes, which "cannot easily be fixed". Mojca

1 0

setuplist
by Olivier 21 Aug '05

21 Aug '05

Hi, Does anyone know about a way to "reset" the state in a combined list. Let me illustrate with an example: \setuplist[chapter][alternative=f,margin=0cm,distance=0cm,before=,after=] \setuplist[section][alternative=b,style=bold,width=5mm,margin=0mm,distance=0mm] \setuplist[subsection][alternative=c,style=normal,margin=5mm,width=7mm,distance=2mm] \chapter{A} % not indented in toc \section{1} \subsection{a} \section{2} \chapter{B} % indented as a section in toc \section{1} \subsection{a} \chapter{C} % indented as a subsection Thanks, Olivier

1 1

RE: dvipdfmx bug
by Idris Samawi Hamid 20 Aug '05

20 Aug '05

Hi ChoF, >===== Original Message From Jin-Hwan Cho <chofchof(a)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

1 0

RE: dvipdfmx bug
by Idris Samawi Hamid 20 Aug '05

20 Aug '05

Dear Knights of the TeX Table, If there is anyone out there who can compile the latest dvipdfmx for windows and post it/send it to me I would be very grateful! 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

1 0

RE: dvipdfmx bug
by Idris Samawi Hamid 20 Aug '05

20 Aug '05

Thank you, ChoF, for your quick reply. I do not know how to compile dvipdfmx so I will try your changes to spec-dpx.tex. Maybe Fabrice can compile the latest dvipdfmx for windows? Question: how do I determine the version number of my dvipdfmx? My present one came from the context distribution of 16-08-05? All the best Idris >===== Original Message From Jin-Hwan Cho <chofchof(a)ktug.or.kr> ===== >On Aug 20, 2005, at 12:03 PM, Idris Samawi Hamid wrote: > >> I'm presently editing the latest issue of my academic journal, >> which depends >> on the aleph-dvipdfmx cycle (used for the last three issues). >> Unfortunately, >> the latest dvipdfmx (from the latest ConTeXt distribution) freezes >> on figures. >> Enclosed is a sample file, the figure (eps), and the dvi file. > >It's the problem of spec-dpx.tex in the ConTeXt distribution. > >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} > >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

1 0

RE: [NTG-context] changing from oldstyle to upright
by Idris Samawi Hamid 20 Aug '05

20 Aug '05

>===== Original Message From Taco Hoekwater <taco(a)elvenkind.com> ===== >> Switching to oldstyle is easy: >> But how do I locally switch back to upright? Declaring > >I don't think you can, actually. There are no metric files >for oldstyle in the latin modern distribution, only an encoding >vector (and .map). So once a map/encoding is defined for a given font/tfm set it cannot be changed by declaring another map; interesting. >The reverse of the old oldstyle trick should work though: > > \def\liningfigures#1{\mathematics{#1}} Yes! I should have thought of that! As always, thnx a million! Best Idris ============================ Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

1 0