November 2011 - ntg-context - NTG Mailing Lists

Migrating from old ConTeXt to new
by Gerben Wierda 13 Nov '11

13 Nov '11

Hello folks, I have been putting this off for years, but I think somewhere the coming months I'll want to migrate from my current ConTeXt setup to the most recent one so that when I encounter typesetting/ConTeXt problems, I will be asking for solutions in the current actively maintained environments. When I compile a book project, it currently looks like this: > texexec --pdf --mode=editor ../products/prd_book.tex > MTXrun | kpse fallback with progname 'context' initialized in 0.047062 seconds > TeXExec | processing document '../products/prd_book.tex' > TeXExec | no ctx file found > TeXExec | tex processing method: context > TeXExec | TeX run 1 > TeXExec | writing option file prd_book.top > TeXExec | using randomseed 1038 > TeXExec | tex engine: pdftex > TeXExec | tex format: cont-en > This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) > restricted \write18 enabled. > (/usr/local/texlive/2010/texmf/web2c/natural.tcx) > entering extended mode > (../products/prd_book.tex > > ConTeXt ver: 2010.05.24 13:05 MKII fmt: 2010.7.21 int: english/english As I understand, I need to setup a different way to run tex. (BTW, I'm going to migrate to MacTeX 2011 first) Important for me is the use of Optima, which is now done in an environment file. Will this still work? > % Bypassing type-gtamacfonts.tex > \starttypescript [sans,serif] [optima] [texnansi,ec] > \definefontsynonym [Optima-Regular] [\typescriptthree-OptimaRegular] > [encoding=\typescriptthree] > \definefontsynonym [Optima-Italic] [\typescriptthree-OptimaItalic] > [encoding=\typescriptthree] > \definefontsynonym [Optima-Bold] [\typescriptthree-OptimaBold] > [encoding=\typescriptthree] > \definefontsynonym [Optima-BoldItalic] [\typescriptthree-OptimaBoldItalic] > [encoding=\typescriptthree] > \definefontsynonym [Optima-ExtraBlack] [\typescriptthree-OptimaExtraBlack] > [encoding=\typescriptthree] > \stoptypescript > \starttypescript [sans,serif] [optima] [name] > \setups [font:fallback:\typescriptone] > \definefontsynonym [\typescriptprefix\typescriptone] [Optima-Regular] > \definefontsynonym [\typescriptprefix\typescriptone Italic] [Optima-Italic] > \definefontsynonym [\typescriptprefix\typescriptone Bold] [Optima-Bold] > \definefontsynonym [\typescriptprefix\typescriptone BoldItalic] > [Optima-BoldItalic] > \definefontsynonym [\typescriptprefix\typescriptone Black] [Optima-ExtraBlack] > \stoptypescript > \definetypeface[allsans][rm][serif][optima][default][encoding=texnansi] > \definetypeface[allsans][ss][sans][optima][default][encoding=texnansi] > \loadmapfile [gtamacfonts.map] > \setupbodyfont[allsans,12pt] Yours, G

2 1

(long) footnotes in column sets messed up
by Stefan Müller 13 Nov '11

13 Nov '11

Hi folks, please consider the following example. \starttext \startcolumnset[n=2] \dorecurse{4}{\input knuth\footnote{Some footnote which is not wrapped correctly and has a bad number}} \stoptext The footnotes are very messed-up (overlapping, numbers all in left column). Is there a better way to place such footnotes in column sets? Am I doing something wrong? I'm using 20111028 22:32 MKIV. Thank you very much in advance! Stefan

1 1

missing --delete flags in mtx-update.lua
by pmlists＠free.fr 13 Nov '11

13 Nov '11

Hello, When running first-setup.sh, some of the rsync commands are missing the --delete flag: /opt/context/tex/texmf-context: ok /opt/context/tex/texmf-linux-64: no --delete flag /opt/context/tex/texmf: ok /opt/context/tex/texmf-modules: no --delete flag -- Peter

1 0

idea: Module to automatically extract and insert information from Wikipedia
by Paul Menzel 13 Nov '11

13 Nov '11

Dear ConTeXt folks, just now I thought of the following and I am wondering if there exists already a solution. Writing a text which includes people I want to add information about these peoples as footnotes. The first sentence in a Wikipedia article is most of the time good enough for that. A macro `\infofromwikipedia{Donald Knuth}` would be nice which gets the first sentence of the article and puts an item into the bibliography. There is even an API to access articles [2]. Besides coding that up I see the following problems. 1. The output [3] needs to be converted to ConTeXt. 2. An Internet connection would be necessary. But that is just a note and not a problem. Thanks, Paul [1] https://en.wikipedia.org/wiki/Donald_Knuth [2] http://www.mediawiki.org/wiki/API [3] http://www.mediawiki.org/wiki/API:Data_formats#Output

5 4

No colons with pxmath fonts
by Andreas Harder 13 Nov '11

13 Nov '11

Hi, there is (still) no colon if one uses the pxmath fonts. By the way, \setupTEXpage causes an error (Undefined control sequence). \setupbodyfont[palatino] % no colon % \setupbodyfont[asana] % OK % \setupTEXpage[offset=1ex] % error \startTEXpage % [offset=1ex] % OK $a$:\,$b$\par $a\colon b$ \stopTEXpage Regards Andreas

2 1

more table trouble ...
by Idris Samawi Hamid ادريس سماوي حامد 12 Nov '11

12 Nov '11

Dear gang, Here's another table that worked fine in MkII but not MkIV: ================= \starttext \starttable[|l|l|] \VL test \VL \LOW{test} \VL\FR \DL \DC \DR \stoptable \stoptext ================= ! Use of \DL doesn't match its definition. system > tex > error on line 4 in file taqwa-ibadah-test.tex: Use of ... 1 \starttext 2 \starttable[|l|l|] 3 \VL test \VL \LOW{test} \VL\FR 4 >> \DL \DC \DR 5 \stoptable 6 \stoptext 7 l.4 \DL \DC \DR ===================== Please advise! Best wishes Idris -- Professor Idris Samawi Hamid, Editor-in-Chief International Journal of Shīʿī Studies Department of Philosophy Colorado State University Fort Collins, CO 80523

2 2

empty lines messing with margins (in duplex mode)
by Peter Schorsch 12 Nov '11

12 Nov '11

Hi, I am not sure but maybe it is a bug: in duplex documents empty lines causing a mess with the margins on every second page. Following lines create a fine pdf documents and all margins are set correctly in the pdf file: ... \ininner{X X X X X X X X X X X X}\inouter{M M M M M M M M M M M M }\input tufte \ininner{X X X X X X X X X X X X}\inouter{M M M M M M M M M M M M }\input tufte \ininner{X X X X X X X X X X X X}\inouter{M M M M M M M M M M M M }\input tufte ... But as soon I add between every two lines an empty line the margin on every second page are corrupted. I am using the context version 2011.11.08. I attached example files to reproduce and show the problem: duplex-margin-with-empty-lines.tex > problem occurs duplex-margin-without-empty-lines.tex > no problem Can anyone approve this problem? Or did I something totally stupid to get this result? I attached a jpg that shows the problem.

2 1

Parameters in \definecolor
by Marcin Borkowski 12 Nov '11

12 Nov '11

Hi all, the manual (the "current draft") says that possible parameters for \definecolor are: r,g,b, c,m,y,k, s, h,t,a,p,e While the first three (rgb), the second four (cmyk) and the third one (s) are pretty obvious for me - rgb, cmyk and greys, I suppose - I'm wondering what is the use of the others? Also, do I get it correctly that if I give all r,g,b,c,m,y,k and s, I will define the same colorname for rgb, cmyk and grey documents, so that \setupcolors[cmyk=no], \setupcolors[rgb=no] and \setupcolors[reduction=yes] (or something similar) will choose only the rgb/cmyk/s components and ignore the others? Best, -- Marcin Borkowski

4 7

"doublesided=no" ignored on \startstandardmakeup with the latest beta
by Marco Pessotto 12 Nov '11

12 Nov '11

Hi! See the next minimal example (copied from "Layout in Context"): %%%% \setuppagenumbering[alternative=doublesided] \starttext \startstandardmakeup[doublesided=no] ...the front \stopstandardmakeup \startstandardmakeup[page=no] ...the back \stopstandardmakeup \stoptext %%%% The manual says it should generate 2 pages with no page number. With current (2011.05.18) this indeed happens. With the latest beta I have 4 pages: ...the front [1] ...the back [empty page] I guess there's a bug somewhere. Best wishes -- Marco

2 4

Simplefonts: Font scaling problem
by Christian 12 Nov '11

12 Nov '11

Good evening! I want to scale a font loaded via the simplefonts so sans and serif have the same x-height. But as soon as I use a font size larger than 12pt, the scaling is somehow off or ignored. Example: \usemodule[simplefonts] \setupsimplefonts[expansion=quality, protrusion=quality] \setmainfont[Times New Roman] \setsansfont[Arial][scale=0.863] \starttext \setupbodyfont[6pt] 06pt serif xx{\ss xx sans}\\ %fine \setupbodyfont[12pt] 12pt serif xx{\ss xx sans}\\ %fine, too \setupbodyfont[14pt] 14pt serif xx{\ss xx sans}\\ %here it starts to be off \setupbodyfont[16pt] 16pt serif xx{\ss xx sans}\\ \stoptext What is up with that?

3 5