May 2009 - ntg-context - NTG Mailing Lists

Does or will bib module use ris format?
by Wei-Wei Guo 16 May '09

16 May '09

Hi Taco, I searched in mailing list and found that you had been considering using risx as the internal bib format? Did you do it in t-bib? And as I understand, you are writing a new bib module with Lua. What will the internal format of the new bib module be? I'm using RefDB, whose internal bib format is ris, and am thinking about combining RefDB with ConTeXt. Best wishes, Wei-Wei

2 1

mptopdf does not work with filenametemplate
by Nicola 16 May '09

16 May '09

Given the following source file foo.mp: beginfig(0); filenametemplate "foo.eps"; endfig; end; running 'mptopdf foo.mp' results in: MPtoPDF 1.3.3 : no filename matches foo (because it is looking for foo.0, of course). I've read that 'filenametemplate' is going to be deprecated in favor of 'outputtemplate': will mptopdf be compatible with that command? Or is mptopdf also going to be replaced by something else (sorry, I'm not following the recent developments very closely)? Nicola

1 0

Font features switching
by Vyatcheslav Yatskovsky 16 May '09

16 May '09

Hello, I'm still curious about using font features. For example, I want to have one typescript with slashed zero, and another with normal one. But using either typescript (see commented lines) results in slashed zeroes. What s wrong? \definefontfeature[zero][default][zero=yes] \starttypescript [serif] [MinionPro] \definefontsynonym [Serif][file:MinionPro-Regular][features=zero] \stoptypescript \starttypescript [MinionPro+zero] \definetypeface [MinionPro][rm][serif][MinionPro][features=zero] \stoptypescript \starttypescript [MinionPro] \definetypeface [MinionPro][rm][serif][MinionPro][features=default] \stoptypescript %\usetypescript[MinionPro+zero] %\usetypescript[MinionPro] \setupbodyfont[MinionPro,16pt] \starttext This zero test. 000. \stoptext Best, Vyatcheslav

2 1

Re: [NTG-context] PDF sizes
by Taco Hoekwater 16 May '09

16 May '09

Hi, ntg-context-bounces(a)ntg.nl wrote: > > From: Mohamed Bana <mbana.lists(a)googlemail.com> > Date: Fri, 15 May 2009 19:51:31 +0100 > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > > > Hi all, > > why is the PDF generated from luatex so much smaller in size? When I > compile slightly larger documents the difference is quite noticeable, > e.g., 300 KB for pdftex and 56 KB for the same document. > > -rw-r--r-- 1 mbana mbana 13K 2009-05-15 19:48 luasize.pdf > -rw-r--r-- 1 mbana mbana 56K 2009-05-15 19:39 pdfsize.pdf Because mkiv+luatex treats the fonts differently. If you compare the fonts in the pdf documents, you'll see this difference: [taco@ntg tmp]$ pdffonts luasize.pdf name type emb sub uni object ID ------------------------------------ ------------ --- --- --- --------- CLWCAI+LMMono10-Regular CID Type 0C yes yes yes 4 0 FRSDEY+MinionPro-Regular CID Type 0C yes yes yes 5 0 [taco@ntg tmp]$ pdffonts pdfsize.pdf name type emb sub uni object ID ------------------------------------ ------------ --- --- --- --------- TPEDRB+LMMono10-Regular Type 1 yes yes yes 4 0 QCXLWN+WarnockPro-Regular Type 1 yes yes yes 5 0 The 'CID Type 0' vs 'Type 1' is about encoding (2bytes vs 1byte); the key to the different sizes is the 'C' in the type category. In the luatex case, the fonts are internally converted to the newer 'Type 1 CFF' font format, which is much more compact than 'oldfashioned' Type 1. IIRC, dvipdfmx uses 'Type 1C' (1byte CFF), so that should also be smaller than pdftex. Best wishes, Taco

1 0

Re: [NTG-context] bugs in math engine?
by Patrick Gundlach 16 May '09

16 May '09

Hi, > We (Patrick, Mojca, and I) have discussed hosting a git repo on the > garden. I do not think it was implemented. I am Ccing Patrick and > Mojca, and maybe they can shed more light on the status of git server > on the garden. It is not implemented (yet). If someone can give me a strategy (pseudo code welcome) which alpha/beta/stable to put into the repository this should be quite easy to do. Patrick -- ConTeXt wiki and more: http://contextgarden.net

2 2

tlig doesn't work with mode=node
by Khaled Hosny 16 May '09

16 May '09

In the last beta, 'tlig' font feature doesn't work with 'mode=node' anymore, that is I can't use it with Arabic: \definefontfeature[default][default][mode=node] \usetypescript[palatino] \setupbodyfont[palatino] \starttext - -- --- \stoptext I'm not sure since when it was broken, but it has been working few betas ago. Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer

1 0

mtxrun problem
by Henning Hraban Ramm 15 May '09

15 May '09

As far as I skimmed the discussions of the last days, this didn't show up yet: In my LilyPond module I call the programm like so: \def\LP{mtxrun --ifchanged="\lily!filename.tmp" --exec bin:lilypond - dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts -ddelete- intermediate-files "\lily!filename.tmp"} \def\PDF{texmfstart --ifchanged="\lily!filename.eps" pstopdf "\lily! filename.eps"} \executesystemcommand{\LP} \executesystemcommand{\PDF} The former definition results in this call: mtxrun --ifchanged="c_whatshallwedo-lilypond-1.tmp" --exec bin:lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts - ddelete-intermediate-files "c_whatshallwedo-lilypond-1.tmp" The .tmp file exists and contains the right LilyPond code. But I get an error like this from the LP call: ############################################################ .../texmf/tex/texmf-osx-intel/bin/mtxrun:1953: attempt to call field 'HEXsum' (a nil value) ############################################################ Line 1953 is: return md5.HEXsum(data) Looks like a bug in mtxrun to me - or in Lua's md5 module. http://www.keplerproject.org/md5/manual.html#lua_api says, there'd be only "sum" and "sumhexa" methods. Replacing "HEXsum" with "sum" works, "sumhexa" gives the same error as above. The PDF call gives: MTXrun | file 'c_whatshallwedo-lilypond-1.eps' is unchanged Even if the .eps file doesn't exist at all. There are no .md5 files like before. I guess that's right? Greetlings from Lake Constance! Hraban --- http://www.fiee.net/texnique/ http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer)

1 0

definelabe in latest beta(s)
by Thomas A. Schmitz 15 May '09

15 May '09

Hi, the \definelabel command does not work any more in the latest betas. Here's a minimal document: \definelabel[SlideNumber][headstyle=normal,way=bytext] \starttext \incrementSlideNumber \nextSlideNumber \stoptext Works fine with the older version I have here 2009.03.30 18:28 and fails with the latest beta: ! Undefined control sequence. l.5 \incrementSlideNumber \nextSlideNumber All best Thomas

1 0

Font features
by Vyatcheslav Yatskovsky 15 May '09

15 May '09

Hello, I also have a question about font features. Minion Pro has old style numerals. How to display them, provided that I enabled this feature? In the following test script, I get ordinary numbers, no old style. \starttypescript [serif] [MinionPro] \definefontsynonym [Serif][MinionPro-Regular.otf][features=onum] \stoptypescript \starttypescript [MinionPro] \definetypeface [MinionPro][rm][serif][MinionPro][features=onum] \stoptypescript \usetypescript[MinionPro] \setupbodyfont[MinionPro,16pt] \starttext This is bla bla bla 1234567890. \stoptext Regards, Vyatcheslav

5 4

beta (14.05.2009,16:44): PDF layer
by Peter Rolf 15 May '09

15 May '09

Hi, as already mentioned there is a problem with PDF layer... or with the way I use them. This is an old example, so it's maybe outdated. Both marks produce non valid PDF here. \setupcolors[state=start] \setupinteraction[state=start] \pdfcompresslevel0 \defineproperty[layerA][layer][title={layer_A},state=start] \starttext \startproperty[layerA] text %\framed[width=160mm,height=120mm]{\tooltip{A text with...{a tooltip}}% \stopproperty \stoptext Peter

1 0