- ntg-context - Mailing Lists

definetypeface usage
by dr. Hans van der Meer 05 Jul '04

05 Jul '04

Trying to findout how ConTeXt's font mechanism works, I come to following question: From the brochure "Fonts in Context" (mfonts.pdf) I have picked up the notion that exercising a call to \definetypeface gets fonts in working order (see the examples there on font specifiers "funny" and "whow", for example, and the resulting typeface collection). Also in file type-exa.tex there is a typescript [postscript] where \definetypeface is exercised, seemingly to bring a matched series of times, helvetica and courier into existence. However, the usage of the postscript fonts via \setupbodyfont[pos] seems to be completely unconnected with this script (I traced the typescript checking). Neither can I find somany calls to \definetypeface (and its derivatives \dodefinetypeface and \dododefinetypeface); it seems they are barely used in the code. So, the questions are: - Does \setupbodyfont[pos] results in the scaled font set as given in type-exa? - Or does \definetypeface belong to an alternative/obsolete font definition scheme, totally unrelated to the definitions called up in the scripts in type-pre.tex, type-syn.tex, and other friends? - In preparing font scripts, can I therefore totally ignore \definetypeface or will that be disastrous for the result? If somebody would be so kind to enlighten me... Hans van der Meer

1 0

Known nath bugs?
by SebastianSturm＠t-online.de 05 Jul '04

05 Jul '04

Hello all, is there a list of know nath bugs somewhere on the web? I tried to find one using Google, but unfortunately without success. The reason I'm asking this is that I'm encountering some problems with the module and would like to know if they are common or if it's related to my configuration. First of all, using the units module together with nath doesn't seem to work - for instance, $1\Micro\Coulomb$ works as expected without nath, but produces the error message "Please don't say \def cs{...}, say \def\cs{...}" when used together with nath. I also thought that delimiters like ( or [ should automatically adjust to the formula they contain, but (\sum_{something} \frac{something}{something}) only produces standard parentheses. Commands like \lbrace or \lbrack work as expected, though. If these problems are unknown, I can post a small example file and my logfile. Best regards, Sebastian

4 15

was: Configuration SciTE under Linux
by Willi Egger 05 Jul '04

05 Jul '04

Hi, yesterday I posted my problems configuring SciTE under Linux. Thanks to the tip of Hraban I came to the following solution: In the SciTEUser.porperties file setup the paths to the perl and ruby scripts. Do not forget the slash at the end of the line. path.context.rubyscripts=/usr/local/tex/texmf-local/scripts/context/ruby/ path.context.perlscripts=/usr/local/tex/texmf-local/scripts/context/perl/ In the context.properties file change the menu issues as follows: name.context.concheck=ruby $(path.context.rubyscripts)concheck.rb name.context.texexec=perl $(path.context.perlscripts)texexec.pl --autopdf name.context.texshow=perl $(path.context.perlscripts)texshow.pl name.context.texutil=perl $(path.context.perlscripts)texutil.pl name.context.examplap=ruby $(path.context.rubyscripts)texmfstart.rb --file=examplap.pdf --program=context --browser name.context.showcase=ruby $(path.context.rubyscripts)texmfstart.rb --file=showcase.pdf --program=contextname.context.concheck=ruby $(path.context.rubyscripts)concheck.rb So may be that there is still a better solution to this. Any comment is welcome. Kind regards Willi

1 0

About \seeregister
by Nikolai Weibull 05 Jul '04

05 Jul '04

Hi, I have a question about \seeregister: It seems that the definition in cont-enp.pdf would want you to write \seeindex{DFA}{finite automaton+deterministic} if you have had \index{finite automaton+deterministic} already, but instead you're fourced to write it as \seeindex{DFA}{deterministic finite automaton} for it to come out sort of right. Is this how I'm supposed to be using \seeregister? nikolai -- ::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka ::: ::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden ::: ::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 ::: main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

1 0

Configuration of SciTE under Linux
by Willi Egger 04 Jul '04

04 Jul '04

Dear Contexters As a bit of a newby on the Linux platform I can't get running everything as wanted. One of the problems I have is, that I am unable to compile a TeX source from within SciTE. I got the context.properties and the SciTEUsers.properties in my home directory. The other porperties files were copied into the SciTE directory. In SciteUsers.properties I have set the path to the location where the scripts are: path.context.rubyscripts=/usr/local/tex/texmf-local/scripts/context/ruby path.context.perlscripts=/usr/local/tex/texmf-local/scripts/context/perl nevertheless the scripts are not found. I get the following error in SciTE: texexec --autopdf --pdf test.tex sh: line 1: texexec: command not found >Exit code: 127 On the other hand, running texexec test from the console does result in the expected test.pdf file. Is there anyone who has a clue how to solve this? Kind regards Willi

2 1

Configuration of SciTE under Linux
by Willi Egger 04 Jul '04

04 Jul '04

Dear Contexters As a bit of a newby on the Linux platform I can't get running everything as wanted. One of the problems I have is, that I am unable to compile a TeX source from within SciTE. I got the context.properties and the SciTEUsers.properties in my home directory. The other porperties files were copied into the SciTE directory. In SciteUsers.properties I have set the path to the location where the scripts are: path.context.rubyscripts=/usr/local/tex/texmf-local/scripts/context/ruby path.context.perlscripts=/usr/local/tex/texmf-local/scripts/context/perl nevertheless the scripts are not found. I get the following error in SciTE: texexec --autopdf --pdf test.tex sh: line 1: texexec: command not found >Exit code: 127 On the other hand, running texexec test from the console does result in the expected test.pdf file. Is there anyone who has a clue how to solve this? Kind regards Willi

1 0

typescript question
by dr. Hans van der Meer 04 Jul '04

04 Jul '04

There is something I don't understand about the typescript business (using ConText version june 30, 2004): By calling \setupbodyfont[lbr] the following script (referred to als typescript number-1) in type-buy.tex (lines 161-170) is executed: \starttypescript [lbr] \usetypescript [serif,sans,mono,math,calligraphy,handwriting] [lucida] [name,special,\defaultencoding] \usetypescript [serif,sans,mono,math,calligraphy,handwriting] [default] [size] \usemathcollection[lbr] \usetypescript [all] [lucida] [\defaultencoding] \stoptypescript Also I have defined somewhere else a typescript (number-2): \starttypescript [Times] ... \stoptypescript WITHOUT the line "...[all]..." in typescript number-1 all goes well, lucida fonts result in the product. However, WITH the line "...[all]..." in typescript number-1 there is found the following match, as can be seen in the log (by setting \tracetypescriptstrue): >>> fonts : enter [Times] [] [] >>> fonts : check [all] [lucida] [texnansi] >>> fonts : matched Now that seems strange to me. I might be misunderstanding the typescript search mechanism, but why does it turn out that the search key [lucida] is ignored? Here it seems that after the [all] the following search keys are ignored, reducing the check to [all][][]; but why then bother giving these 2nd and 3rd key at all? But even if this behaviour is implied by giving the first search key as [all], it leads to wrong results. Because now the typescript number-2 is executed too, working havoc to the font setup. Is there someone who can enlighten me on these matters? Thanks in advance. Hans van der Meer

1 0

tables
by dr. Hans van der Meer 02 Jul '04

02 Jul '04

Does someone knows where there is information on the table environment in ConTeXt? I have read the intro on ConTeXt and the pamphlets from the Pragma-site on tabulate and btable, but there seem to be a lot more options than can be found in these; I encountered something like \AR etc. whose effects I could not figure out with some tests. Also there is some mention of Wichura's manual. Is this somewhere to be found on the internet? Thanks in advance. Hans van der Meer

2 2

math-lbr
by dr. Hans van der Meer 01 Jul '04

01 Jul '04

Hi Hans, I get the impression that in math-lbr.tex the codes for blacktriangleleft and -right are interchanged. Having F0 where it should be F1 and vice versa. Imho it should be left = F0 and right = F1. Hans van der Meer

1 0

bug in layers
by Hans Hagen 01 Jul '04

01 Jul '04

Hi, If you think that in the current version layers are using too many resources, you're right and may patch: \def\checkproperty[#1]% {\bgroup \def\currentproperty{#1}% \csname\??py\s!check\currentproperty\endcsname \egroup} Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1