March 2014 - ntg-context - NTG Mailing Lists

\rm in math mode should give text roman
by Sanjoy Mahajan 10 Mar '14

10 Mar '14

I don't think it's right that \rm in math mode means \mathrm. Or, at least, plain.tex assumes that \rm gives text roman, e.g. from plain.tex (line 1067), \def\arctan{\mathop{\rm arctan}\nolimits} Thus, the following example has the "arctan" text in Euler math. This problem doesn't occur with Latin Modern or with Palatino, because somehow (I'm not quite sure how) they have \rm inside math meaning text roman. \usetypescriptfile[euler] \definetypeface [mainface] [rm] [serif] [pagella][default] \definetypeface [mainface] [ss] [sans] [modern] [default] [rscale=1.075] \definetypeface [mainface] [tt] [mono] [dejavu] [default] [rscale=0.9] \definetypeface [mainface] [mm] [math] [pagellaovereuler][default] \appendtoks \rm \to \everymathematics \setupmathematics[lcgreek=normal, ucgreek=normal] \setupbodyfont[mainface] \starttext \startformula \arctan x \stopformula \stoptext

1 0

vertically align to the bottom
by Pablo Rodriguez 10 Mar '14

10 Mar '14

Dear list, I have the following sample: \starttext \startstandardmakeup This text should be placed at the bottom. \stopstandardmakeup \stoptext Which is the option to align the makeup to the bottom? Many thanks for your help, Pablo -- http://www.ousia.tk

2 2

[***SPAM***] ConTeXt Daily Build
by hwitloc＠gmail.com 10 Mar '14

10 Mar '14

Where are there instructions for using the daily build, newest Context code? [ Is this the same as the standalone version that I've heard of? ] Thanks

2 1

how to make a \lambdabar (like \hbar)
by Sanjoy Mahajan 10 Mar '14

10 Mar '14

\hbar is used a lot in physics. Once in a while, one also uses \lambdabar to mean \lambda/2\pi. It's Unicode description is 'LATIN SMALL LETTER LAMBDA WITH STROKE' (U+019B). I've been using this hack \def\lambdabar{\lambda\kern-1ex\raise0.65ex\hbox{-}} But it's not beautiful. Is there a better way to get a lambdabar into (or from) the math fonts? I tried \def\lambdabar {\Umathchar "0"0"00019B } by analogy with the definition of \hbar in luatex-math.tex, but it produces a blank space. There must be no entry for it in the regular (or Palatino) math fonts. For reference, the following thread had a discussion about \hbar <http://www.ntg.nl/pipermail/ntg-context/2013/070810.html> and \hbar works well (using MkIV 2014.02.14). -Sanjoy

2 2

Re: [NTG-context] Problem using the new buildin simplefont \definefontfamily with OTF fonts
by 罗晨星 09 Mar '14

09 Mar '14

Well with \definefontfamily[mainface][serif][Minion Pro][opticalsize=yes] It does work. But I just wonder why some people could omit this option? Is there a bug? Will this be omitted in later distributions? Results has been attached, 4 complete build result for you to analyze. 南京大学现代工程与应用科学学院 2013级罗晨星 Luo Chenxing ————————————— chenxing.luo(a)gmail.com 2014-03-10 10:23 GMT+08:00 Wolfgang Schuster <schuster.wolfgang(a)gmail.com>: > > Am 10.03.2014 um 02:05 schrieb Wolfgang Schuster < > schuster.wolfgang(a)gmail.com>: > > > Hi, > > > > can you run the attached file and show me the resulting pdf file? > > Can you also try what happens when you enable optical sizes! > > \definefontfamily[mainface][serif][Minion Pro][opticalsize=yes] > > \setupbodyfont[mainface] > > \starttext > Hello World! > \stoptext > > Wolfgang

1 1

Problem using the new buildin simplefont \definefontfamily with OTF fonts
by 罗晨星 09 Mar '14

09 Mar '14

I am using Ubuntu 13.10 with ConTeXt daily build and LuaTeX daily build. My ConTeXt version is 2014.02.14 17:07, LuaTeX version beta-0.78.3 (TeX Live 2014/dev/Debian) (rev 4850) . While there are some problems with using the newly added feature of build-in support of simplefonts. I was using something like \definefontfamily[mainface][serif][Kepler] \setupbodyfont[mainface] \starttext Hello World! \stoptext It would end up with using Latin Modern font. The log is like this: system > 'cont-new.mkiv' loaded (/usr/share/texmf/tex/context/base/cont-new.mkiv) system > files > jobname '003', input './003', result '003' fonts > latin modern fonts are not preloaded languages > language 'en' is active (/home/alan/tex/test/003.tex fonts > preloading latin modern fonts (math) {/usr/share/texmf/fonts/map/dvips/lm/lm-math.map}{/usr/share/texmf/fonts/map/dvips/lm/lm-rm.map}{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map} fonts > 'fallback modern mm 12pt' is loaded fonts > preloading latin modern fonts (mono) fonts > 'fallback modern tt 12pt' is loaded fonts > defining > font with asked name 'unknown' is not found using lookup 'file' fonts > defining > unknown font 'unknown', loading aborted fonts > defining > unable to define 'unknown' as 'mainface-12pt-rm-tf-0--0' backend > xmp > using file '/usr/share/texmf/tex/context/base/lpdf-pdx.xml' However, when I use something like Times New Roman (TTF), Utopia (TTF), Georgia(TTF), FZShuSong-Z01 (TTF Chinese font) it would be working all right, fonts applied, no error reported. But like in the example, Kepler (OTF), Minion Pro (OTF), Utopia Std (OTF) would failed to be applied. It is as if it would fail every OTF font. When I am using some font in the legacy simplefonts module mode, something like: \usemodule[simplefonts] \setmainfont[Kepler] \starttext Hello World! \stoptext Would be working alright. Logged as below: fonts > latin modern fonts are not preloaded languages > language 'en' is active (/home/alan/tex/test/003.tex resolvers > modules > 'simplefonts' is loaded (/usr/share/texmf/tex/context/third/simplefonts/t-simplefonts.mkiv loading > ConTeXt User Module / Simplefonts <+ /usr/share/texmf/tex/context/third/simplefonts/t-simplefonts.lua>){/usr/share/texmf/fonts/map/dvips/lm/lm-math.map}{/usr/share/texmf/fonts/map/dvips/lm/lm-rm.map}{/usr/share/texmf/fonts/map/pdftex/context/mkiv-base.map} backend > xmp > using file '/usr/share/texmf/tex/context/base/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1 ) )</home/alan/.fonts/KeplerStd-Subh.otf> So what's the problem? Is there anything I should look into? If it is a problem with TeXLive how can I use the ConTeXt Standalone without conflict with the previous installed TeXLive (Since I am also using LaTeX) ? Regards. 南京大学现代工程与应用科学学院 2013级罗晨星 Luo Chenxing ————————————— chenxing.luo(a)gmail.com

2 2

Customize register format
by Thangalin 09 Mar '14

09 Mar '14

Hi, I am trying to reproduce the following register layout: http://i.imgur.com/qXSK2VM.png Entries include a section name, page number, author, and author URL; the entries are formatted fairly differently from a standard index. So far I have: \setupinteraction[state=start,] \define\Punctuate{\color[black]{\normal.}} \define[2]\href{\begingroup\goto{\color[blue]{#1}}[url(#2)]\endgroup} \define[1]\TextCommand{\item\currentregisterpageuserdata{title}, } \define[1]\PageCommand{#1\Punctuate{} {\href{\currentregisterpageuserdata{author}}{\currentregisterpageuserdata{authorurl}}}\Punctuate\stopitemize} % #1 - Author; #2 - Author URL; #3 - Section title \define[3]\PhotographerIndexEntry{% \setregisterentry[PhotographerIndex][entries={#1}][ title={#3}, author={#1}, authorurl={#2}, ]{} } \defineregister[PhotographerIndex][ n=1, indicator=no, textcommand=\TextCommand, pagecommand=\PageCommand, distance=\zeropoint, before={\startitemize[packed,nowhite]}, ] \setuphead[section][aftersection=\page,] \starttext \startsection[title={Maguro}] Text \PhotographerIndexEntry{Kenji Fujimoto}{http://bit.ly/1fNWF0Y}{Maguro} \stopsection \startsection[title={Unagi}] Text \PhotographerIndexEntry{Kenji Fujimoto}{http://bit.ly/1fNWF0Y}{Unagi} \stopsection \placePhotographerIndex \stoptext This fails because values for "entries={#1}" must be unique. How can I customize the registers to resemble the given layout? (Aside, the section title is repeated twice -- is there a way to remove the duplication? I tried \namedstructurevariable, but couldn't figure out how to get the expanded value.) Thank you.

1 0

Broken bibliographies in 2014-03-07 beta
by Rik 09 Mar '14

09 Mar '14

Bibliographies are no longer generated. MWE is the example code at http://wiki.contextgarden.net/Bibliography_mkiv, which no longer generates an output file and shows the following in the blg file: I found no \citation commands---while reading file cite.aux I found no \bibdata command---while reading file cite.aux I found no \bibstyle command---while reading file cite.aux You've used 0 entries,... With the stable version, the same section reads: Database file #1: sample.bib You've used 4 entries, -- Rik

1 0

new beta
by Hans Hagen 07 Mar '14

07 Mar '14

Hi, I uploaded a new beta. Apart from the usual 'improvements' and a few 'fulfilled wishes' the main difference is in some optimized register generation code: in the crited project we're dealing with tens of thousands of different index entries and that gave problems with luajittex (first of all a memory issue due to limitations in luajit, after that a 20 fold slowdown thanks to poor hashing) but Luigi and I were able to sort that out. If you use luajittex and run into memory issues (indicated by the inability to load the tuc file) you can say \setupregister[index][referencemethod=forward] given that you never place an index before the entries are defined. If you use luajittex and it's way too slow, then wait till the updated binaries are released. (Or just use luatex). Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 4

Re: [NTG-context] [Index] Indenting long primaries after secondaries
by Jan Tosovsky 07 Mar '14

07 Mar '14

On 2014-02-26 Jan Tosovsky wrote: > > when a long primary is preceded with the secondary or tertiary > index entry, the second line is not indented as usual, see > the following example: > > \setupregister[balance=no] > \starttext > \index{primary+secondary+tertiary} > \index[primary long]{\dorecurse{5}{primary long }} > \index[primary longer]{\dorecurse{5}{primary longer }} % but this is Ok > \input{tufte} > \completeindex > \stoptext > I've tested this in new beta and the issue is still there... Jan

1 0