May 2005 - ntg-context - NTG Mailing Lists

RE: [NTG-context] Capitalized headings
by Ville Voipio 04 May '05

04 May '05

> The bad news is that now I have a lot more questions concerning the It really seems that I do... I played around with the capitalization commands and got some interesting results. My test file is (works in live.contextgarden.net if required): --- \enableregime[il1] \starttext abcABCåäöÅÄÖ \cap{abcABCåäöÅÄÖ} \uppercased{abcABCåäöÅÄÖ} \WORD{abcABCåäöÅÄÖ} \uppercase{abcABCåäöÅÄÖ} \stoptext --- So, the test string is: abcABC\aumlaut\aring\oumlaut\Aumlaut\Aring\Oumlaut (just in case it does not display correctly). It gives: \cap -> ABCABCÅÄÖÅÄÖ (in \tfx size), just as expected \uppercased -> ABCABCåäöÅÄÖ (ABC's in \tfx, rest untouched) \WORD -> ABCABCÅÄÖxxx (where xxx's are gibberish) \uppercase -> ABCABCÅÄÖxxx The plain TeX \uppercase seems to be known for its nasty behaviour with anything else than US characters. \WORD seems to be a thin wrapper around it, so similar behaviour is to be expected. \uppercased makes interesting things, as it does uppercase the abc's well but does not touch the accented characters in any way. Only \cap seems to do exactly what it should. --- Things become even stranger, when the regime is switched to UTF-8. Then \WORD and \uppercase give some errors and refuse to compile. \uppercased and \cap work as described above. --- As \uppercase is a plain TeX macro, fixing it is not a good choice, especially because it is known to be bad. However, if \WORD could be built on \cap but without the font size changing, it would work fine. The odd behaviour of \uppercased (and the reasons to use it instead of the other choices) remains unclear to me. - Ville

2 1

RE: [NTG-context] Capitalized headings
by Ville Voipio 03 May '05

03 May '05

> However, this is a workaround, another way of attacking it (it can be > better, too, stylistically, as you can change the font independently): > \setuphead [title] [textcommand=\uppercase] And that works, thanks! --- The bad news is that now I have a lot more questions concerning the heading formatting. There are several parameters which can be used: style textstyle textcommand numberstyle numbercommand This is how I understand those (please, correct me when I am wrong). Let us assume we have a chapter heading saying "Chapter 1. Title" in the following examples: style=\bf -> {\bf Chapter 1.}{\bf Title} textstyle=\bf -> {Chapter 1.}{\bf Title} numberstyle=\bf -> {\bf Chapter 1.}{\bf Title} If I got it right this far, then I think I get these. The relevant parts of the heading are prepended with the given commands (whatever they then may be). But this mechanism does work only with the commands which change the style from that point onwards (e.g., \it, \tfx). What about the commands which take the text as a parameter (such as \cap{text})? And what are textcommand and numbercommand? I tried playing a bit with them. For example, \it or \bf can be put either as textstyle=\it or textcommand=\it. On the other hand, the \uppercase can be used only with textstyle. So, there is a difference as the name suggests (my initial guess was that the difference is exactly what I ask above, but doesn't seem to be so). Where on Earth is \uppercase explained? I tried looking for it in the manual -- in vain. I found some references to \uppercased which seems to be another beast. Thank you for your patience. If the stuff is not explained in other places, I can Wiki it once I understand it. - Ville

1 0

Supress chapter number in sections
by Randall Skelton 03 May '05

03 May '05

I've fiddled with almost every parameter in sethead but cannot seem to find the correct one. I'd like to suppress the chapter numbers in a relatively large document such that numbering of sections, tables, figures and equations begins at 1 instead of 1.1. Is there a simple way to do this? Here are how my chapters and sections are currently defined: \def\MyChapterText#1{\leftaligned{#1}} \setuphead[Topic,chapter] [textcommand=\MyChapterText, textstyle={\switchtobodyfont[Titling,20pt]\sc}, color=black, number=no, page=right, continue=no, header=empty, distance=0pt, before=\vbox to 3cm\bgroup, after=\vss\egroup] \def\MySectionText#1{\switchtobodyfont[12pt]\sc\lowercase{#1}} \setuphead[Subject, section] [textcommand=\MySectionText, style={\sc}, color=black, before={\blank[2*big]}, after={\blank[2*big]}] Many thanks, Randall

1 0

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 03 May '05

03 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 03 May '05

03 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 03 May '05

03 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 03 May '05

03 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