- ntg-context - Mailing Lists

Re: [NTG-context] Empty page without header, footer, pagenumber
by "H. Özoguz" 02 Oct '13

02 Oct '13

> \setuppagenumbering[alternative=doublesided] > > \starttext > > \input knuth > > \page[empty] % empty page > > \input knuth > > \page[yes,right] %move to right page but keep header and footer > > \input knuth > > \page[yes,header,footer,right] % move to right page and remove header and footer > > \input knuth > > \stoptext > > Wolfgang Thanks Wolfgang, but its not so easy. I knew this commands, but that is, what I meant with this problems I had. In a large document often empty pages (but with numbers) appear infront of a new part, or chapter, because this new part has to be set on a odd page, for example. And so I have always to deactivate all things, and activate them after this empty page again, exactly with these commands above. That is, why I had the pseudo-algorithm idea, that context should just look after, which pages are empty, and to clear everything on them (or: to not set anything on them, if there is no text). That would give perfect result with only one single command, without switching all the way. Huseyin

1 0

Empty page without header, footer, pagenumber
by "H. Özoguz" 02 Oct '13

02 Oct '13

Hi there, since long time I always use hacks and complicate uses of \setuppagenumbering[location=] and \startfrontmatter \stopfrontmatter in different places of my documents, which habe often sideeffects and make problems. All this just for realizing a very simple rule: If the page is empty (no text), then it should be "totally empty", that is: No header, no footer, no pagenumber. But apart from this, do nothing – do not change effects of partnumerings (like \frontmatter does), or anything else. That is all I need. Is that easy to realize without on/off-commands, which makes confusing in a large document? Thanks. Huseyin

2 1

Re: [NTG-context] No page break between chapter-title and section-title in TOC
by "H. Özoguz" 02 Oct '13

02 Oct '13

This one is still open, is there maybe a workaround to prevent page-breaks in the TOC between chapter- and sections-titles (or part- and chaptertitles). And in general: Where can I find documentation about designing and aligning the titles for the TOC (not in the text). I am only interested in line-breaks (at the moment). Huseyin

2 1

Fwd: Re: outer floats on doublesided pages UNSOLVED
by Hans Hagen 02 Oct '13

02 Oct '13

btw ... uppercasing in the subject triggers a delay in response -------- Original Message -------- Subject: Re: [NTG-context] outer floats on doublesided pages UNSOLVED Date: Tue, 01 Oct 2013 22:34:02 +0200 From: Hans Hagen <pragma(a)wxs.nl> To: Tim Steenvoorden <tim.steenvoorden(a)gmail.com> On 10/1/2013 11:46 AM, Tim Steenvoorden wrote: > Hi Hans, > > Is it possible to fix the "inouter" and "ininner" directives too? > "inright" and "inleft" work as expected. afaik \setuppagenumbering [alternative=doublesided] \setuplayout [backspace=5cm, width=middle] \starttext \dorecurse{4}{ \placefigure[left] {left} {\framed[height=1cm,width=4cm]{}} test \placefigure[right] {right}{\framed[height=1cm,width=4cm]{}} test \placefigure[inner] {inner}{\framed[height=1cm,width=4cm]{}} test \placefigure[outer] {outer}{\framed[height=1cm,width=4cm]{}} test \placefigure[leftmargin] {left} {\framed[height=1cm,width=4cm]{}} test \placefigure[rightmargin]{right}{\framed[height=1cm,width=4cm]{}} test \placefigure[innermargin]{inner}{\framed[height=1cm,width=4cm]{}} test \placefigure[outermargin]{outer}{\framed[height=1cm,width=4cm]{}} test \page } \stoptext works ok ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Automatically loading the page state, LoadPageState
by Marco Patzer 01 Oct '13

01 Oct '13

Hi, I wonder if it's necessary to manually load the MetaPost variables using LoadPageState. Some of them are static and do not require an update on each page, e.g. NOfPages, but many of them might change on each page, e.g. OnOddPage, PageNumber, TextWidth. Forgetting to use LoadPageState easily results in perfectly valid code producing wrong results, which might not be hard to spot. Example: \setuplayout [width=10cm] \showframe \starttext \startMPcode fill unitsquare xyscaled (\the\textwidth, 2cm); \stopMPcode \startMPcode fill unitsquare xyscaled (TextWidth, 2cm); \stopMPcode \startMPcode LoadPageState; fill unitsquare xyscaled (TextWidth, 2cm); \stopMPcode \stoptext I assume it's too inefficient to load the page state automatically for each graphic. However, loading the page state automatically is simple: \startMPinitializations LoadPageState; \stopMPinitializations Marco

2 5

metafonts
by Hans Hagen 01 Oct '13

01 Oct '13

Hi, Another new feature (side effect of ctx meeting): %D \module %D [ file=demo-symbols.mp, %D version=2013.09.06, %D title=\CONTEXT\ \METAPOST\ graphics, %D subtitle=demo font, %D author=Hans Hagen, %D date=\currentdate, %D copyright={PRAGMA ADE \& \CONTEXT\ Development Team}] %C %C This module is part of the \CONTEXT\ macro||package and is %C therefore copyrighted by \PRAGMA. See mreadme.pdf for %C details. passvariable("fontname","demo-symbols") ; passvariable("fontversion","1.004") ; beginglyph(9754,2,4,0) ; % high voltage interim ahlength := 1 ; drawarrow (1,4) -- (0,2) -- (2,3) -- (1,0) withcolor darkred ; endglyph ; \starttext \definemetafont[demo-symbols][demo-symbols.mp] \startbuffer watch this: {\demo\char"261A} \stopbuffer \definefont[demo][demo@demo-symbols] \getbuffer \blank \definefont[demo][demo@demo-symbols at \the\dimexpr3\exheight] \getbuffer \blank \definefont[demo][demo@demo-symbols at \the\dimexpr4\exheight] \getbuffer \blank \stoptext ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

outer floats on doublesided pages
by R. Ermers 01 Oct '13

01 Oct '13

Dear all, I have problems with the placement of floats. I need them to be placed in the outer edge of the text, but Context puts them in the middle of the page. The outer, inner, outeredge, inneredge, commands do not work. Right and left do work. Preferably the criterium option should also work, e.g. criterium=0.67. A minimal test file is attached. Try it out with a dummy, or with cow picture, or with any other picture of your liking. I updated my context installation today to a bèta version. The version is: 2013.08.30 02.05. All help is welcome! Many thanks in advance, Robert %%%%%%%%%%%%%%%%%% \setuppapersize[A4][A4] \setuppagenumbering[alternative=doublesided,location=footer] \definefloat[edgefigure][figure] \setupfloat [edgefigure] [leftmargindistance=-\outercombitotal, rightmargindistance=-\outercombitotal, default={outer,none,low,high}] \setupcaption[edgefigure][number=no] \useexternalfigure[cow][./cow.pdf] \starttext \startsection[title={insight},reference=insight] \placeedgefigure[][]{}{\framed[frame=off]{\externalfigure[cow][scale=150]}} When the first volume of Donald Knuth's The Art of Computer Programming was published in 1969, it was typeset using hot metal type set by a Monotype Corporation typecaster with a hot metal typesetting machine from the 19th century which produced a "good classic style" appreciated by Knuth. When the second edition of the second volume was published, in 1976, the whole book had to be typeset again because the Monotype technology had been largely replaced by photographic techniques, and the original fonts were no longer available.[4] When Knuth received the galley proofs of the new book on 30 March 1977, he found them awful.[5] Around that time, Knuth saw for the first time the output of a high-quality digital typesetting system, and became interested in digital typography. The disappointing galley proofs gave him the final motivation to solve the problem at hand once and for all by designing his own typesetting system. On 13 May 1977, he wrote a memo to himself describing the basic features of TeX.[6] \placeedgefigure[][]{}{\framed[frame=off]{\externalfigure[cow][scale=150]}} He planned to finish it on his sabbatical in 1978, but as it happened the language was not frozen until 1989, more than ten years later. Guy Steele happened to be at Stanford during the summer of 1978, when Knuth was developing his first version of TeX. When Steele returned to MIT that autumn, he rewrote TeX's I/O to run under the ITS operating system. The first version of TeX was written in the SAIL programming language to run on a PDP-10 under Stanford's WAITS operating system. For later versions of TeX, Knuth invented the concept of literate programming, a way of producing compilable source code and cross-linked documentation typeset in TeX from the same original file. The language used is called WEB and produces programs in DEC PDP-10 Pascal. \placeedgefigure[][]{}{\framed[frame=off]{\externalfigure[cow][scale=150]}} When the first volume of Donald Knuth's The Art of Computer Programming was published in 1969, it was typeset using hot metal type set by a Monotype Corporation typecaster with a hot metal typesetting machine from the 19th century which produced a "good classic style" appreciated by Knuth. When the second edition of the second volume was published, in 1976, the whole book had to be typeset again because the Monotype technology had been largely replaced by photographic techniques, and the original fonts were no longer available.[4] When Knuth received the galley proofs of the new book on 30 March 1977, he found them awful.[5] Around that time, Knuth saw for the first time the output of a high-quality digital typesetting system, and became interested in digital typography. The disappointing galley proofs gave him the final motivation to solve the problem at hand once and for all by designing his own typesetting system. On 13 May 1977, he wrote a memo to himself describing the basic features of TeX.[6] He planned to finish it on his sabbatical in 1978, but as it happened the language was not frozen until 1989, more than ten years later. Guy Steele happened to be at Stanford during the summer of 1978, when Knuth was developing his first version of TeX. When Steele returned to MIT that autumn, he rewrote TeX's I/O to run under the ITS operating system. The first version of TeX was written in the SAIL programming language to run on a PDP-10 under Stanford's WAITS operating system. For later versions of TeX, Knuth invented the concept of literate programming, a way of producing compilable source code and cross-linked documentation typeset in TeX from the same original file. The language used is called WEB and produces programs in DEC PDP-10 Pascal. \stopsection \stoptext ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ______________________________________________________________________________________________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

6 13

Breaks in TOC
by "H. Özoguz" 01 Oct '13

01 Oct '13

Hi there, two questions about formatting the TOC or the titles in the TOC: 1. How to formate the titles different in the text and in the TOC respectively? I only mean line breaks. E.g., see this minexample: \starttext \completecontent \startsection[ title={Eine sehr, sehr lange Überschrift, die auf jeden Fall irgendeine Art von Formatierung benötigt}, label={Eine sehr, sehr lange Überschrift,\\die auf jeden Fall irgendeine Art von Formatierung benötigt}, marking={Eine sehr, sehr lange Überschrift,\\die auf jeden Fall irgendeine Art von Formatierung benötigt}] \stoptext That does not work, label and marking are the wrong keys for setting the TOC-Title, which have no effect on the title in the toc, which one is the correct key? 2. How to prevent page-breaks after some title in the TOC? E.g. I have a chapter title in the toc, and after chapter-titles there should be no immediate page-break. So I would need something like \testpage[10], but for the toc. How to do this? Thanks again. Huseyin

1 0

question about linespace adjustment
by Lars Huttar 30 Sep '13

30 Sep '13

Hello, I'm working through the reference manual trying to understand how things work in regard to fonts. I'll be submitting clarifications and elaborations to the manual in an attempt to help other non-experts to grasp the design of ConTeXt. There's a point that's confusing to me in section 5.5, Line spacing. On page 108 of the manual it says "Linespacing alters when a new bodyfont is used or when linespacing is deﬁned explicitly by \setupinterlinespace (which is explained later)" But on the next page it says, "When you make a font switch the linespacing is adapted when you give the command \setupinterlinespace without any setup parameters and also when you add the key reset, for example..." So here's why I'm confused. When you change fonts, (a) does linespacing get changed automatically, or (b) do you have to say \setupinterlinespace? If (a), then why does the second quote above seem to say you need \setupinterlinespace to make it happen? If (b), then isn't the first quote above inaccurate? Is there a distinction being drawn here between "when a new bodyfont is used" and "when you make a font switch", or are those just variant phrasings for what is intended to mean the same thing? Thanks for your help, Lars

4 13

beta
by Hans Hagen 30 Sep '13

30 Sep '13

Hi, I uploaded a new beta (still catching up from last week). The core now has the simplefonts-turned-fontselector code included but only those present last week have the edge of knowing how to use it unless WS decides to reveal its secrets and/or LS undiscloses it by posting source code. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0