ntg-context December 2013

ntg-context@ntg.nl

43 participants
90 discussions

footer page number on first page of section: doesn't appear
by Lars Huttar 05 Dec '13

05 Dec '13

Hi, Based on our reading of http://wiki.contextgarden.net/FO_Page_Layout#First_Page we have the following MWE, which we want to put a page number in the footer on the first page only: \definetext[footerpagenumber][footer][pagenumber] \setuphead[section][header=empty,footer=footerpagenumber,number=no,align={middle,nothyphenated,verytolerant},style=ssbf] \starttext \section{My Own Section} \dorecurse{15}{ \input knuth \par } \stoptext Unfortunately, no page number shows up. If we add \setuppagenumbering[location=footer] before the \starttext, we get the page numbering we want, but it's on every page, not just the first. Is there something wrong with our setuphead? Thanks, Lars

3 4

a way to implement \testcolumn in mixedcolumns
by Lars Huttar 05 Dec '13

05 Dec '13

Hello, On this list I've been advised that mixedcolumns is the latest and greatest implementation of columns; the one to use. We have switched over from columnsets to mixedcolumns, and have been very pleased with the column balancing (for some reason we couldn't get column balancing to work in columnsets). However one thing we do miss from columnsets is the control over widows & orphans in two ways: \testcolumn, and \setupcolumnsetlines. \testcolumn[n] allowed us to do a conditional column break, so when we were about to start a new subsection heading, we could prevent it being an orphan at the bottom of the column; and when starting a paragraph with a hangaround graphic framed flushright and bottom, we could similarly use \testcolumn to prevent the graphic from hanging down into the footer (which is what sometimes happened otherwise). So I'm wondering, is there some way to achieve the equivalent of \testcolumn in mixedcolumns? Is it theoretically impossible to implement this in mixedcolumns because the required information (how many lines are left in the current column) is not yet known? Or could that information be gleaned from somewhere? I see in page-brk.mkiv the following definition for \testcolumn: \def\testcolumn {\dodoubleempty\page_tests_columns_test} \def\page_tests_columns_test[#1][#2]% {\endgraf \ifdim\pagegoal<\maxdimen \ifdim\pagetotal<\pagegoal \d_page_tests_test\dimexpr \pagegoal -\pagetotal \ifdim\lastskip<\parskip+\parskip\fi \ifsecondargument+#2\fi \relax \getrawnoflines\d_page_tests_test % (raw) \ifnum#1>\noflines \column \fi \else \penalty-\plustenthousand % (untested) \fi \fi} I'm not a low-level TeX programmer, and I don't understand a lot of this, but it looks like \getrawnoflines\d_page_tests_test puts the number of remaining lines into \noflines Any suggestions are appreciated. (And I should have a MWE soon.) Lars

3 11

Re: [NTG-context] [***SPAM***] OT: Generating Command reference from source code
by Wolfgang Schuster 04 Dec '13

04 Dec '13

Am 04.12.2013 um 20:11 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: > On 2013-12-04 Wolfgang Schuster wrote: >> Am 04.12.2013 um 18:56 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: >>> On 2013-12-04 Hans Hagen wrote: >>>> >>>> there is a (somewhat incomplete) reference definition in xml format >>>> so your (b) is in principle covered; >>> >>> where is it stored? >> >> The english interface is stored in the file cont-en.xml, the path for >> the file on my system is >> >> /Users/wolf/context/beta/tex/texmf- >> context/tex/context/interface/cont-en.xml >> >> A PDF with all commands from the files is available here: >> http://pragma-ade.com/show-man-10.htm > > Thanks. Interesting to see what can be found on my PC :-) You can produce the PDF yourself with "context --global x-set-12.mkiv“. > Unfortunately there isn't even minimal description what the particular > command does :-( The file shows only the syntax of the command, when you want a description of the command you have to writer this yourself. To show which keys and values are available for each command you can load a single one of them from the big file. > And what is the purpose of those localized versions? ConTeXt has a multilingual interface where you can use dutch, french etc. command names, e.g. \starttext … \stoptext is written as \starttekst … \stoptekst when you use the dutch interface. Wolfgang

1 0

Re: [NTG-context] [***SPAM***] OT: Generating Command reference from source code
by Wolfgang Schuster 04 Dec '13

04 Dec '13

Am 04.12.2013 um 18:56 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: > On 2013-12-04 Hans Hagen wrote: >> On 12/3/2013 10:59 PM, Jan Tosovsky wrote: >>> >>> Supposing that ... >>> a) every .mkiv file is enhanced by 'package' annotation >>> b) every public command/macro contains a description with the list of >>> all available params (sensible subset of JavaDoc annotations) >>> >>> .... I can imagine to extract this info and: >>> >>> A) build the static command reference website with all the hyperlinks >>> B) eventually generate PDF variant of the same >>> C) export it into the form which can be imported into the WIKI (with >>> read-only mode) >>> >>> If every change of behaviour was reflected immediately in the >>> description, if any newly added parameter was added into the parameter >>> list, the main goal would be achieved. >> >> there is a (somewhat incomplete) reference definition in xml format so >> your (b) is in principle covered; > > where is it stored? The english interface is stored in the file cont-en.xml, the path for the file on my system is /Users/wolf/context/beta/tex/texmf-context/tex/context/interface/cont-en.xml A PDF with all commands from the files is available here: http://pragma-ade.com/show-man-10.htm Wolfgang

2 1

Re: [NTG-context] [***SPAM***] OT: Generating Command reference from source code
by Hans Hagen 04 Dec '13

04 Dec '13

On 12/3/2013 10:59 PM, Jan Tosovsky wrote: > Dear All, > > in another thread I was dreaming ... to have always the complete and up to > date command/macro reference with basic descriptions and list all of the > parameter/options... > > 'Spoiled' by goodies offered by various Java APIs (based on > http://en.wikipedia.org/wiki/Javadoc ) I am missing this a lot. > > Example of the result: > http://docs.oracle.com/javase/7/docs/api/index.html?overview-summary.html > > In Java there is the following structure (simplified): > 1) 'packages' defining the hierarchy > 2) 'classes' defining objects > 3) 'properties' and 'methods' for every particular 'class' > > I've roughly scanned the ConTeXt source structure and bringing the following > idea: > > 1) There is no 'packages' counterpart in ConTeXt, but it would be handy to > think of any logical structure to group commands to logical groups (even > nested). Maybe the filename title prefix could be taken as a starting point > for this. > 2) 'classes' = all individual .mkiv files > 3) 'methods' = all public \def, \define etc in mkiv files (+maybe other > contructs I am not aware) > > Supposing that ... > a) every .mkiv file is enhanced by 'package' annotation > b) every public command/macro contains a description with the list of all > available params > (sensible subset of JavaDoc annotations) > > .... I can imagine to extract this info and: > > A) build the static command reference website with all the hyperlinks > B) eventually generate PDF variant of the same > C) export it into the form which can be imported into the WIKI (with > read-only mode) > > If every change of behaviour was reflected immediately in the description, > if any newly added parameter was added into the parameter list, the main > goal would be achieved. keep in mind that quite some functionality is the result of user requests and for a while can be in flux and i consider it then the users responsibility to wrap up on the wiki (for completely new mechanisms i often write a dedicated manual or an article for a user group journal) > But I understand there is lot of to do in the beginning... with disputable > effect in the end. > > I can help with some coding, transforming ... > > Jan > > Btw, would it be sufficient to scan texmf-context\tex\context\base\*.mkiv > files or there are other parts somewhere else? There are approx 500 files > now. It is huge number, but finite :-) there is a (somewhat incomplete) reference definition in xml format so your (b) is in principle covered; these definitions used to be in the source (more than a decade ago) but i moved them out because some functionality is stepwise provided (not in one place) and also because many commands are generated (you will not find their names by interpreting the source) the problem with tex (and therefore context) is that we are dealing with quite some interaction between unpredictable user input, macro (expansions), tex-internals, resources like fonts, patterns and whatever, etc. and this is why you often need to play with mechanisms: small test files and see how it looks (tex is a visual tool) it's often not as simple as "you feed it this" end "get back that" for documentation several methods are used: - examples in the test suite - some explanation in the source - explanations on the wiki - dedicated manuals - articles by users (+examples) although i sometimes run into impressive auto-documented documentation for languages or os commands, in practice i find myself looking for examples and/or experimenting and/or going into sources 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 -----------------------------------------------------------------

3 3

[***SPAM***] OT: Generating Command reference from source code
by Jan Tosovsky 03 Dec '13

03 Dec '13

Dear All, in another thread I was dreaming ... to have always the complete and up to date command/macro reference with basic descriptions and list all of the parameter/options... 'Spoiled' by goodies offered by various Java APIs (based on http://en.wikipedia.org/wiki/Javadoc ) I am missing this a lot. Example of the result: http://docs.oracle.com/javase/7/docs/api/index.html?overview-summary.html In Java there is the following structure (simplified): 1) 'packages' defining the hierarchy 2) 'classes' defining objects 3) 'properties' and 'methods' for every particular 'class' I've roughly scanned the ConTeXt source structure and bringing the following idea: 1) There is no 'packages' counterpart in ConTeXt, but it would be handy to think of any logical structure to group commands to logical groups (even nested). Maybe the filename title prefix could be taken as a starting point for this. 2) 'classes' = all individual .mkiv files 3) 'methods' = all public \def, \define etc in mkiv files (+maybe other contructs I am not aware) Supposing that ... a) every .mkiv file is enhanced by 'package' annotation b) every public command/macro contains a description with the list of all available params (sensible subset of JavaDoc annotations) ... I can imagine to extract this info and: A) build the static command reference website with all the hyperlinks B) eventually generate PDF variant of the same C) export it into the form which can be imported into the WIKI (with read-only mode) If every change of behaviour was reflected immediately in the description, if any newly added parameter was added into the parameter list, the main goal would be achieved. But I understand there is lot of to do in the beginning... with disputable effect in the end. I can help with some coding, transforming ... Jan Btw, would it be sufficient to scan texmf-context\tex\context\base\*.mkiv files or there are other parts somewhere else? There are approx 500 files now. It is huge number, but finite :-)

1 0

(critical edition) Examples of bib files
by luigi scarso 03 Dec '13

03 Dec '13

We are currently seeing the part of bibliography and we are looking for real examples in utf. You can post the examples on this ml, or send me privately. -- luigi

1 0

vertical square root upstroke (instead of having a slant)
by Sanjoy Mahajan 03 Dec '13

03 Dec '13

With the following minimal file on MkIV (2013.05.28 00:36 MKIV current), the upstroke of the square root is vertical instead of having the usual slant toward the right. With MkII it has the usual slant. I see this problem only with certain arrangements of variables (that recur often in my book chapter on springs and piano strings). For example, it goes away after changing the "\rho" to a "b". \starttext \startformula \sqrt{Tb^2\over \rho}. \stopformula \stoptext I know that the big math symbols are constructed differently in MkIV and MkII. Does the example above show an intended difference? -- -Sanjoy

2 2

Re: [NTG-context] Keeping titles together with the following text when grid is on
by Hans Hagen 03 Dec '13

03 Dec '13

On 12/2/2013 9:02 PM, Jan Tosovsky wrote: > On 2013-12-02 "H. Özoguz" wrote: >> On 2013-12-01 Jan Tosovsky wrote: >>> >>> when grid is on, orphan and widows have to be eliminated using > additional >>> penalty settings. Whereas it works fine for body text, section titles > are >>> still sometimes left at the bottom of the page. >> >> this is not the same question as handling orphan and widows - because >> you surely do not want some titles with only 2-3 lines of body text >> after them. >> >> I always use "\testpage[x]" to handle those issues, see your example >> with testpage: >> >> \setuphead[section][before={\testpage[8]\blank}] \blank[samepage,big] > Thanks, it works! Another magic command not documented anywhere in the > ConTeXt Guide or Wiki... > > I was looking for any alternative for XSL-FO's keep-with-next="always". This > is a different approach, but it doesn't matter. > > Btw, I still don't understand why keeping the title and text behaves > differently when grid is on... > > Jan > > ___________________________________________________________________________________ > 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 > ___________________________________________________________________________________ > -- ----------------------------------------------------------------- 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

Command for the caption location inside \startplacefigure
by Géry Ogam 03 Dec '13

03 Dec '13

Hello, What is the option to specify the CAPTION location in \startplacefigure (I already now that you can do it from \setupcaption)? I thought the first argument of 'location' was for the FIGURE location, and the second one for the CAPTION location, but the second one has no effect: \startplacefigure[location={left, top}, title=A cow] \externalfigure[cow] \stopplacefigure Best regards.

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context December 2013