dev-context November 2005

dev-context@ntg.nl

6 participants
15 discussions

[Fwd: Re: [NTG-context] Where is \typescriptthree documented?]
by Taco Hoekwater 08 Dec '05

08 Dec '05

Patrick, Perhaps it is easiest if you start simple that 'api' subdivision in texshow-web first. Than i can start adding stuff at any time I have a minute or so to spare. Creating a big preprocessed cont-api.xml file is unlikely for (at least) the next month. Cheers, Taco Forwarded message from Hans: > David Arnold wrote: > >> All, >> >> I don't understand \typescriptthree. Where is it documented? What >> does it mean? > > > I'm not sure that it is documented, but it is the value of the > third argument of \starttypescript, and it valid until \stoptypescipt. > If the actual argument was a list, then context will loop over each > item in the list, each time with the next value in \typescriptthree. > > Similar commands are available for \typescriptone and \typescripttwo. taco: this is probably something for the api documentations, isn't it? (i forgot how we're goint to organize that -) Hans _______________________________________________ ntg-context mailing list ntg-context(a)ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

2 2

Re: [dev-context] Compiled pdfetex
by Duncan Hothersall 30 Nov '05

30 Nov '05

>> I'm happy to put it up on a server here somewhere and link to it from >> the wiki if that's the preferred option. >> > sounds ok to me; i can always pick it up then (a bit low on time today) > > Hans Okay. Link to http://www.capdm.com/public/context/ added to wiki Duncan

2 1

Compiled pdfetex
by Duncan Hothersall 30 Nov '05

30 Nov '05

Ref the thread on the main list: I have compiled pdfetex on my glibc2.3.2 machine and it works for me - can someone check that this works on a newer machine too? Below URL (not permanent) should point to a zip containing pdfetex and pdfetex.pool. http://people.capdm.com/dh/home/pdfetex1-30-4-linked-to-glibc2-3-2.zip Many thanks, Duncan

2 2

ConTeXt GUI & Sample documents
by Adam Lindsay 22 Nov '05

22 Nov '05

Hello Syndicate, Jérôme Laurens, maker of iTeXMac, is being *very* ambitious for his 2.0 version, and he contacted me for some ideas/contributions on the ConTeXt side of things. First, he wanted some sample documents and/or templates. Since every iTeXMac document is actually a directory, and it is project-based, I was wondering if there were any folks who had good examples using products/ environments. Yes, I'm keeping my eye on the released manuals. :) Secondly, he asked which texexec were the best to expose in the GUI. I came up with this list off the top of my head: --mode= --usemodule= --xmlfilter= --environment= --batch --once --runs= (The engine switches will probably be set on a project level, he said, and --pdfarrange and the like would probably be exposed in another GUI helper.) Is there anything else really compelling to expose in a GUI? Hans, he also has the ability to point at different source trees on a preference and project basis. I will look at the minimal trees, to see what needs to be done to support them within his framework. Mac users can take a look at the rough but promising project here: <http://sourceforge.net/project/showfiles.php? group_id=58056&package_id=53754> (currently iTeXMac2 preview8) -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

2 1

adobekb problem
by Taco Hoekwater 21 Nov '05

21 Nov '05

Hi, This has taken me a while to realise, but the following way to use the psnfss fonts is broken: \usetypescript[adobekb][ec] \usetypescript[palatino][ec] \switchtobodyfont[palatino] You need to load the map file for 8r, because the metrics in EC encoding are virtual fonts. There is a map file for EC metrics, but that is absolutely useless for these virtual fonts. The easiest way of doing that is: \usetypescript[adobekb][8r,ec] \usetypescript[palatino][ec] Previously, this stuff used to work because context-base.map and pdftex.map contained all of the map files, including the 8r one, but now that context-base.map is gone, manual loading of 8r is needed. Bye, Taco

2 6

[Fwd: Re: [pracjourn-prod] Postcards]
by Hans Hagen 18 Nov '05

18 Nov '05

Hi, a funny link Interesting note on Knuth and the web http://lists.xml.org/archives/xml-dev/200509/msg00153.html . Hans

1 0

\showskips bug
by Taco Hoekwater 17 Nov '05

17 Nov '05

This one is cute if you want to benchmark your computer: \showskips \starttext Hello! \stoptext Never stops generating pages Taco

4 9

pdfetex 1.30.4 binaries for linux-64
by Taco Hoekwater 17 Nov '05

17 Nov '05

I compiled 1.30.4 this morning on our amd64 machine: http://tex.aanhet.net/temp/pdfetex-linux-64.zip Cheers, Taco

1 0

\sqrt in expansions bug
by Taco Hoekwater 16 Nov '05

16 Nov '05

Hi, Macros that use \doifnextcharelse should all be defined as \unexpanded, to prevent errors like: \expanded{$\sqrt 2$} Also affected are: \decrement \increment maybe there are others, but these were easy to spot because they were single-line \def's. The \sqrt is painful, because it is likely to appear in \write-s Cheers, Taco

2 1

Re: [NTG-context] font problems again
by Adam Lindsay 15 Nov '05

15 Nov '05

[changed to dev-context] Hans Hagen said this at Mon, 14 Nov 2005 00:07:44 +0100: >lucida is a special case -) > >because i used lucida a lot, those definitions ended up in the core, but >when i bought more and more fonts, i finally decided to move the lucida >defs to the type-buy.tex typescript because that;s where they belong > >you can add the line: > > \usetypescriptfile[type-buy] > >to the cont-sys.tex file, but best is (because it's a document property) >to say in you document (or style): > >\usetypescriptfile[type-buy] % loads commercial font definitions >\usetypescript[lucida][texnansi] % defines a lucida typeface >\setupbodyfont[lucida,12pt] % enables the typeface defined as >'lucida' That reminds me, Hans. The PCTeX edition of Lucida are floating around. I've done some preliminary typescripts, and they seem to fit in well. I need to track down some issues with obscure math characters (making them match CM math), figuring out if the discrepancy is in the current math- lbr definitions, or in changes with the new fonts. Other than that, what should the definitions be called? \starttypescript[lucidanew]? doing an override in type-dis? Cheers, adam -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

dev-context November 2005