- ntg-context - NTG Mailing Lists

Re: Pb compiling s-pre-61.tex
by olivier Turlier 03 May '05

03 May '05

Hi, I've felt into same pb's trying to compile s-pre-61.tex directly from it's original source. As far I can see (just to the surface of the screen in fact) it's related to a specific font installed at Pragma, not available for everyone as is. if I replace or uncomment : \usetypescriptfile[type-ghz] \definetypeface[mainface][ss][sans][optima-nova][default][encoding=\defaultencoding] \setupbodyfont[mainface,ss,18pt] and put such general font switch like : \usetypescript [modern][\defaultencoding] \setupbodyfont[modern,ss,11pt] it compile without pbs. Your installation seems rather old Cordialement -- Olivier TURLIER Formation & Métiers CRP La Rouguière 101 Bd des libérateurs 13367 MARSEILLE cedex 11 tel : 04 91 18 56 00 fax : 04 91 45 14 48

3 2

Changing Title Font in \completecontent
by Randall Skelton 02 May '05

02 May '05

Is there a way to change the title font being used for a table of contents page being displayed by \completecontent? My original thought was to use the same layout as a regular chapter: \chapter{Table of Contents} \placecontents but after reading the manuals a few times, I realized this was doomed to fail. Using \completecontent, I'd like to be able to have 'Contents' or 'Table of Contents' written with my standard \setuphead[chapter] definition. As it stands, \completecontent generates a single roman 'Contents' at the top of the page while all my other titles are offset in position, aligned right, and in small caps... Any ideas? Many thanks, Randall

1 0

Capitalized headings
by Ville Voipio 02 May '05

02 May '05

I've been trying to make capitalized (uppercase) headings with little success. I'd like to have the titles simply capitalized as with \cap or \WORD. A minimal example: --- \setuphead[title][style=WORD] \starttext \title{This is a title} The title should be \cap{capitalized} or \WORD{capitalized}. \stoptext --- What should I give as the style? I have tried the following: style=WORD -> no effect style=Caps -> no effect style=uppercased -> no effect style=CAP -> no effect style=Cap -> no effect style=cap -> error style=kap -> error style=smallcaps -> small caps (when the font supports) It is interesting to get an error message for the "style=cap", because this is one of the listed options in the definition of \setuphead in the manual. What did a do wrong? - Ville

2 1

startsectionblockenvironment bug?
by Stuart Jansen 02 May '05

02 May '05

My understanding is that the following code should produce two chapter pages with a page number at the top, followed by an index page without a page number. That is not what happens. Am I correct that this is a bug? Is there a bugzilla or something similar where I should be reporting the problem? \startsectionblockenvironment[backpart] \setuppagenumbering[state=stop] \stopsectionblockenvironment \setupsectionblock[bodypart][page=no] % avoid generation of an extra \setupsectionblock[backpart][page=no] % page at the end of the doc \startbodymatter \chapter{foo} \section{bar} \index{bar} \section{baz} \chapter{qux} \section{quux} \index{quux} \section{corge} \stopbodymatter \startbackmatter \page \placeindex \stopbackmatter -- Stuart Jansen <sjansen(a)gurulabs.com> Guru Labs, L.C.

1 0

setuppagenumbering way=chapter and indexes
by Stuart Jansen 02 May '05

02 May '05

I'd like to reset the page number with each chapter and prepend the chapter number to the page number. Something like Chapter One Foo 1-1 Bar 1-2 Chapter Two Baz 2-1 Qux 2-3 Now here's where it gets complicated: I also need to generate an index using this same numbering. Index B Bar 1-2,2-1 Q Qux 1-1,2-3 I've played with many different approaches and can achieve 85% functionality, but generating the index is turning out to be killer. Any suggestions? Better yet, does anyone already have example code doing this? -- Stuart Jansen <sjansen(a)gurulabs.com> Guru Labs, L.C.

1 0

Two hyphens do not give en dash
by Ville Voipio 02 May '05

02 May '05

I installed a new font (Gentium, TrueType). Everything went relatively smoothly except for one thing: When I type -- I really get two hyphens instead of the expected en dash. I have been able to work around this by using UTF regime and typing the en dash into the source file. However, it would be easier to use -- and ---. What should I do? (Yeah, I know, forget it and be happy that the UTF works :) TIA, - Ville

2 1

RE: [NTG-context] TEXMFMAIN problem in gwTeX (font installation)
by Ville Voipio 02 May '05

02 May '05

> Just for my understanding. Does texfont.pl only > read in TEXMFMAIN or does it also write (can it > be a search path or does it require for TEXMFMAIN > to be just one directory)? texfont.pl checks several places. By a very quick look at the sources, it looks for the following: TEXMFMAIN TEXMFLOCAL TEXMFEXTRA TEXMFFONTS It does not look for TEXMFTE, but by specifying the switch --rootlist, it can be given a list of trees, which it then browses through. Ok, it might be useful to add a few here, such as TEXMFTE (for us gwTeX users), but maybe that's an endless road. But the real problem is really in a font installation script which explicitly overrides the default settings and gives a wrong tree. --- The problem is easy to pinpoint into type-tfm.dat. Unfortunately, just removing the explicit definitions does not seem to solve the problem. The non-standard root seems to be difficult to be told to the system. For encodings, texfont.pl can be force-fed a value which is passed to all scripts in a batch file (using a special --en=? switch). However, no such mechanism exists for other parameters (such as the --ro). Tweaking the TEXMFFONTS to point to TEXMFTE is one possibility, but then the fonts will also be installed into TEXMFFONTS instead of TEXMFLOCAL. Ideally, it would be nice to be able to tell the script that the source fonts are in TEXMFWHATEVER and they are going into TEXMFSOMETHINGELSE. I haven't been able to figure out how to achieve that without tailoring the batch file. - Ville

1 0

Re: FW: [NTG-context] install help
by Skip Collins 02 May '05

02 May '05

> if you download the latest alpha release, the engine subpath stuff > should work; if not, run: Please pardon my tedious questions. I have tried doing what you suggest, but I must be doing something wrong. I downloaded the alpha cont-tmf.zip. Then I unzipped it into an empty ~/texmf. Then I ran texhash and saw that it updated ~/texmf/ls-R. > ctxtools --make --all (ruby script) To invoke ctxtools, I ran ruby ~/texmf/scripts/context/ruby/ctxtools.rb --make --all Nothing happened except the following output: CtxTools | version 1.2.2 - 2004/2005 - PRAGMA ADE/POD CtxTools | --bbeditinterface generate bbedit syntax files [--pipe] CtxTools | --contextversion report context version CtxTools | --documentation generate documentation file [--type=] [filename]CtxTools | --jeditinterface generate jedit syntax files [--pipe] CtxTools | --patternfiles generate pattern files [languagecode|all] CtxTools | --purgefiles remove temporary files [--all] [basename] CtxTools | --rawinterface generate raw syntax files [--pipe] CtxTools | --sciteinterface generate scite syntax files [--pipe] CtxTools | --touchcontextfile update context version CtxTools | --translateinterface generate interface files (xml) [nl de ..] Inovking texexec on my tex file in either of the following incantations results in an error: perl ~/texmf/scripts/context/perl/texexec.pl --pdf myfile.tex /usr/TeX/bin/i386-linux/texexec --pdf myfile.tex This is a summary of all `failed' messages and warnings: `pdfetex -ini -jobname=cont-en -progname=context -8bit *cont-en.ini' failed warning: kpathsea: mktexpk output `! I can't read pdfetex.pool; bad path?' instead of a filename. Sorry, I can't find the format `cont-en.fmt'; will try `context.fmt'. kpathsea: Running mktexfmt context.fmt fmtutil: no info for format `context'. I can't find the format file `context.fmt'! So perhaps there are some other steps I am missing? Do I need to move updated scripts into /usr/TeX/bin/i386-linux ? Skip

1 0

TEXMFMAIN problem in gwTeX (font installation)
by Ville Voipio 02 May '05

02 May '05

I have spent some very interesting time trying to install the TeXlive fonts by using texfont type-tmf.dat. What happened was that a lot of complaints about "unknown subpath ../afm/public/urw" were given even though the path should have been there. This is a known problem, has been on several mailing lists, as well. After a lot of thinking it became clear that texfont was really unable to find any font files. By browsing through the texfont.pl, the reason became evident: In gwTeX the root variables are: TEXMFMAIN = /usr/local/teTeX/share/texmf TEXMFTE = /usr/local/teTeX/share/texmf.tetex The problem here is that all the TeXlive fonts (and almost everthing else) is really in the TEXMFTE tree. My quick'n'dirty was to make new file type-tmf-gwtex.dat by replacing all occurrences of TEXMFMAIN by TEXMFTE. Running that one in batch mode works fine. Problem solved -- this time. But the solution is not a beautiful one. Could someone suggest something cleaner? Or has this been solved already (I tried googling after the answer without success)? - Ville

4 6

volunteers wanted
by h h extern 02 May '05

02 May '05

Hi, The polish font gurus did it again: two more complete digitized fonts (latin, vietnamese, greek, cyrillic and math are covered); so ... the question is "who is prepared to look into the encoding part of greek and cyrillic" or more precise: with what encoding tfms should the font be shipped (the context friendly <encoding>-name scheme is used) 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 -----------------------------------------------------------------

4 3