ntg-context March 2007

ntg-context@ntg.nl

62 participants
118 discussions

Trouble with \usemodule[tikz]
by M.guravage 29 Mar '07

29 Mar '07

I recently experienced problems with TikZ after upgrading from ConTeXt - 2007.01.23 to 2007.03.19. Instead of looking at the differences between the two releases, I moved my original minimal ConTeXt distribution out of the way and re-installed the latest justtext.zip and linuxtex.zip. To this I added my own texmf-project tree which contains TikZ, and remade the formats. TeX stops at the first TikZ command complaining that it cannot find the tikz module: system : module tikz not found ! Undefined control sequence. l.6 \starttikzpicture I have checked the obvious like the TEXMFPROJECT environment variable and the ls-R files, but everything appears correct. Indeed, everything did run correctly with ConTeXt - 2007.01.23 and pdfTeX-1.40.1. I would be grateful if someone could suggest how I can track down this problem? Cheers, Michael PS: Here is a minimal example. % interface=en output=pdftex \usemodule [tikz] \starttext \input tufte \starttikzpicture \draw (-1.5,0) -- (1.5,0); \draw (0,-1.5) -- (0,1.5); \stoptikzpicture \stoptext % finis

2 1

using Make for documents
by Sanjoy Mahajan 29 Mar '07

29 Mar '07

At the recent User Meeting, a few people were interested in how to use make to maintain complex documents. Here is version 0 of a step-by-step explanation: <http://www.inference.phy.cam.ac.uk/sanjoy/teaching/tex/> Comments welcome! The URL may change. I'll eventually put it on the wiki, or (since I prefer the GPL to the GFDL) put a link to it from the wiki once it's stable. -Sanjoy `A nation of slaves is always prepared to applaud the clemency of their master who, in the abuse of absolute power, does not proceed to the last extremes of injustice and oppression.' (Gibbon)

2 2

Does \Level2Command work?
by Steffen Wolfrum 29 Mar '07

29 Mar '07

Hi, in one of Luigi's "Grid-keeping table"-mail I saw the term "\setbox100". I didn't try that code, don't know what it means. But it gave me the idea: is it actually possible to use numbers in defining command's names? Something like this ... \setuphead[Level2] [header=empty,page=yes,numbercommand=\Level2Command,align=middle,alternative=paragraph,style=\Level2Style,before={\strut\blank[42pt]},after={\blank[12pt]}] \setuphead[Level3] [header=empty,page=yes,numbercommand=\Level3Command,align=middle,alternative=paragraph,style=\Level3Style,before={\strut\blank[42pt]},after={\blank[12pt]}] ... looks much clearer than using the numbers written out in letters. Steffen

4 3

HZ and DVI
by Peter Münster 29 Mar '07

29 Mar '07

Hello, now I see, that my problem with HZ is only in DVI mode, PDFs are ok. Here my test file: \usetypescript[serif,sans,mono][handling][highquality] \setupalign[hanging,hz] \usetypescript[modern-base][\defaultencoding] \setupbodyfont[modern] \starttext \input tufte \stoptext And here the errors: This is dvips(k) 5.96 Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2007.01.08:1425' -> test.ps kpathsea: Running mktexpk --mfmode ljfzzz --bdpi 1200 --mag 1+240/1200 --dpi 1440 ec-lmr10+15 mktexpk: don't know how to create bitmap font for ec-lmr10+15. kpathsea: Appending font creation commands to missfont.log. dvips: Font ec-lmr10+15 not found, characters will be left blank. dvips: Can't open font metric file ec-lmr10+15.tfm dvips: I will use cmr10.tfm instead, so expect bad output. dvips: Checksum mismatch in ec-lmr10+15 kpathsea: Running mktexpk --mfmode ljfzzz --bdpi 1200 --mag 1+240/1200 --dpi 1440 ec-lmr10+20 mktexpk: don't know how to create bitmap font for ec-lmr10+20. dvips: Font ec-lmr10+20 not found, characters will be left blank. dvips: Can't open font metric file ec-lmr10+20.tfm dvips: I will use cmr10.tfm instead, so expect bad output. dvips: Checksum mismatch in ec-lmr10+20 kpathsea: Running mktexpk --mfmode ljfzzz --bdpi 1200 --mag 1+240/1200 --dpi 1440 ec-lmr10-10 mktexpk: don't know how to create bitmap font for ec-lmr10-10. dvips: Font ec-lmr10-10 not found, characters will be left blank. dvips: Can't open font metric file ec-lmr10-10.tfm dvips: I will use cmr10.tfm instead, so expect bad output. dvips: Checksum mismatch in ec-lmr10-10 kpathsea: Running mktexpk --mfmode ljfzzz --bdpi 1200 --mag 1+240/1200 --dpi 1440 ec-lmr10-15 mktexpk: don't know how to create bitmap font for ec-lmr10-15. dvips: Font ec-lmr10-15 not found, characters will be left blank. dvips: Can't open font metric file ec-lmr10-15.tfm dvips: I will use cmr10.tfm instead, so expect bad output. dvips: Checksum mismatch in ec-lmr10-15 kpathsea: Running mktexpk --mfmode ljfzzz --bdpi 1200 --mag 1+240/1200 --dpi 1440 ec-lmr10-20 mktexpk: don't know how to create bitmap font for ec-lmr10-20. dvips: Font ec-lmr10-20 not found, characters will be left blank. dvips: Can't open font metric file ec-lmr10-20.tfm dvips: I will use cmr10.tfm instead, so expect bad output. dvips: Checksum mismatch in ec-lmr10-20 <tex.pro><lm-ec.enc><texps.pro>. <lmr10.pfb>[1] TeXExec | runtime: 11.250944 Can anybody help please? Cheers, Peter -- http://pmrb.free.fr/contact/

11 20

Semi-verbatim
by John R. Culleton 27 Mar '07

27 Mar '07

I have a situation where I wish to import a file and have the line endings and the spaces honored as in \typefile. But I want any font changes (e.g. \it) honored as well. I tried the plain TeX commands \obeylines and \obeyspaces. The line endings and typeface changes were honored but the spaces were not. Is there a convenient way to do this? I can preprocess the file through e.g. sed to patch in \crlf and hard spaces but this seems a bit clumsy. BTW this is text in columns. The length of every line is limited to 45 characters. -- John Culleton Able Indexing and Typesetting Precision typesetting (tm) at reasonable cost. Satisfaction guaranteed. http://wexfordpress.com

2 1

gray scale conversion of colored text
by Peter Rolf 27 Mar '07

27 Mar '07

Hi, I currently have a problem with the conversion of some mp graphics into gray scale. The mp graphics themself look great, but *text is always converted to black*, regardless of its real color. Is there a way to fix this? Peter

2 3

Long heading alignment
by Paul Schalck 26 Mar '07

26 Mar '07

Hello! First, I want to thank you all. It's my first post here, but I've read many of your emails before, and I've already found a lot of solutions for my problems in there. I'm using Context intensely since several months (before, I was Latex) and at the moment, I'm setting my first big document (400 pages, very boring) with it. My issue: I have a little problem with headings I can't solve by my own. It's rather simple: I would like to align headings that span across multiple lines on the left margin, like this: a) This is (not really) a very, very, very loooooooooooooooong title and not that way: a) This is (not really) a very, very, very loooooooooooooooong title The use of (\setuphead[section][command=\MySectionCommand] disables the standard alignment mechanism. I wonder if there is a simpler way to achieve this. Any ideas? Thank you very much! Scheeni Grieß (it's Alsatian German) Paul _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 1

capitals in heads
by Jörg Hagmann 26 Mar '07

26 Mar '07

I hope (I am sure) the meeting was a success. And I hope that you are still willing to answer a simple question: How can I get capitals in a head? The following didn't work: \setuphead[subsection][style=cap] %aborts compilation. (But "slanted" works) I also unsuccessfully tried "style=\cap" (or \kap etc.), "command= \cap" etc. (But style=\sc works. I don't want small caps, though). I also tried concocting my own \def, again without success. Thanks for your help, Jörg

3 5

background example
by Patrick Gundlach 26 Mar '07

26 Mar '07

Hi, just if you are interested in a very old example on using backgrounds: http://dl.contextgarden.net/examples/page.pdf http://dl.contextgarden.net/examples/page.tex Please tell me if I'm using old syntax, so I can update the example. Patrick -- ConTeXt wiki and more: http://contextgarden.net

1 0

warning: XeTeX & broken typescripts (please wait with upgrading)
by Mojca Miklavec 26 Mar '07

26 Mar '07

Hello, While waiting for the train in Köln (just back from one of the best ConTeXt meetings ever ;), I decided to post this warning/explanation to the mailing list (before Hans gets back and blocks my account ;) For those who rely on (complex) XeTeX typescripts, please don't upgrade ConTeXt as long as you have a working version (if not, you can download and extract an older zip from https://foundry.supelec.fr/frs/?group_id=14). Hans is currently working on a high-level user interface for typescripts in luatex, and the old behaviour has been slightly broken, mostly due to the fact that if one wants to support fonts that are not installed, the bracket notation has to be used, which doesn't fit well into the model (one would need to specify fonts in constructs such as [{{'[fontname]'}}]). Without rewriting some basic routins, the font definition would look really strange that way. Currently the format builds OK (it was completely broken for some time, but now you can at least work with it again), you can still select fonts with constructs like \font\a='TestFont/BI:mapping=tex-text' \a and you can also define synonyms like (I hope that I got it right this time) \definefontsynonym[MyFont][name:RealFontName][encoding=uc] % encoding will go (has gone?) away but typescripts don't really work the way that worked once. XeTeX typescripts have been relatively primitive so far: the syntax like \definefontsynonym [DidotItalic] ['Didot/I:mapping=tex-text:+dliga'] [encoding=uc] is not the best possible ansd will most probably not be supported any more. Instead, one would probably write something similar to \definefontsynonym [DidotItalic] [name:Didot] [features=dliga] % mapping=tex-text might be default but that's not the final word about it yet. Sadly Adam Lindsay (who created the whole machinery) doesn't have much time to work with ConTeXt, and I'm not really a TeXacker (if anyone else is willing to help, any help would be more than wellcome). I don't want to force too much the fix (it's better to have it implemented properly and to wait some more), although I hope that it won't take too much time to have it finished. I was silently hoping that Hans will finish the luatex OpenType support before the whole machinery could be backported to XeTeX, but sadly it was (unintentionally) broken before a good replacement could be provided. I would like to ask the ConTeXt-XeTeX users for understanding. I cross-posted that message, but in case that you would need to reply for some reason, please do so on the ConTeXt mailing list, not on the XeTeX one, since XeTeX itself has really nothing to do with the subject (apart from the slightly unfortunate syntax for selecting uninstalled OpenType font). Mojca

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context March 2007