- ntg-context - NTG Mailing Lists

counter reseting at every heading
by Peter Schorsch 18 May '12

18 May '12

Hi, I realized yesterday that my counter for the module does not reset itself as before. What I need is a counter that resets after each heading (chapter, section, subsection, subsubsection and so on). This is what I know about counter reseting at the moment: \definecounter[ParagraphNumber][prefix=no,way=bysection] - way=bychapter: reseting counter at every chapter (default) - way=bysection: reseting counter at every section (not at chapters) - way={bychapter,bysection,bysubsection,bysubsubsection}: does not work \setuphead[chapter,section,subsection,subsubsection][after={\resetcounter[ParagraphNumber]}] does work but it messes with the distance between heading and normal text. What is the correct/best way to make the counter reseting every heading without messing around? Thanks P.

3 2

imposition 2UP = empty pages
by Henning Hraban Ramm 18 May '12

18 May '12

Hi there, like in January (see mail by Mari), the latest beta produces only empty pages with 2UP imposition schema; others work (tested 2SIDE and 2DOWN). e.g. \setuppapersize [A5][A4,landscape] \setuppagenumbering [alternative=doublesided,location=footer] \setuplayout [margin=0pt,width=fit] \setupbackgrounds [text][text][background=screen,backgroundscreen=0.7] \setupcolors [state=start] \setuplayout [location=middle,marking=on] \setuparranging [2UP] %[2*2*4,doublesided] \startbuffer[Fakepage] \strut \blank[force] \midaligned{2UP} \vfill \midaligned{This is page \recurselevel} \vfill \stopbuffer \setupheadertexts[\CONTEXT] \starttext \dorecurse{16}{\getbuffer[Fakepage]\page} \stoptext Greetlings, Hraban --- http://www.fiee.net/texnique/ http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer)

3 10

ConTeXt colours in TikZ
by Marco 18 May '12

18 May '12

Hi everybody, I don't get context colours working in tikz. There were several issues on the mailing list in the past and the solution always seems to be some kind of hack. But none of the hacks work (with a current context). Example: \usemodule [tikz] \definecolor [darkblue] [b=.2] \starttext \starttikzpicture % works \fill [blue] (0,0) circle(1); % fails % \fill [darkblue] (0,0) circle(1); \stoptikzpicture \stoptext I get the following error: Runaway argument? 0 0 0.2 rg 0 0 0.2 RG\pgf@stop {darkblue}\else \edef \pgf@marshal {\noexpand \ETC. ! File ended while scanning use of \pgfutil@context@parse@gray. system > tex > error on line 0 in file : File ended while scanning use of \pgfutil@conte xt@parse@gray ... <empty file> <inserted text> \par Marco

3 4

Luatex crash on \endinput \end
by Aditya Mahajan 18 May '12

18 May '12

Hi, The following causes luatex to crash (it is harmless, but still...) echo '\\endinput \\end' | context --pipe gives: *** glibc detected *** luatex: double free or corruption (fasttop): 0x0aef00e8 *** ======= Backtrace: ========= /lib/libc.so.6(+0x725f2)[0xb75f05f2] luatex(luacstring_close+0x7b)[0x810153b] luatex(end_file_reading+0xd8)[0x80b0858] luatex[0x80d88e7] luatex[0x80d75d4] luatex(get_next+0x5d)[0x80d8cfd] luatex(get_x_token+0x15)[0x80acc35] luatex(main_control+0x48)[0x80b4328] luatex(main_body+0x21d)[0x80b1ebd] luatex(main+0x20)[0x8090d40] /lib/libc.so.6(__libc_start_main+0xf3)[0xb7597483] ======= Memory map: ======== 08048000-08464000 r-xp 00000000 08:03 810362 /opt/context-minimals/texmf-linux/bin/luatex 08464000-084d2000 rw-p 0041c000 08:03 810362 /opt/context-minimals/texmf-linux/bin/luatex 084d2000-0878d000 rw-p 00000000 00:00 0 09838000-0af96000 rw-p 00000000 00:00 0 [heap] b5554000-b5ae4000 rw-p 00000000 00:00 0 b5b46000-b5c27000 rw-p 00000000 00:00 0 b5e45000-b6006000 rw-p 00000000 00:00 0 b60a4000-b60c0000 r-xp 00000000 08:03 1006974 /usr/lib/libgcc_s.so.1 b60c0000-b60c1000 rw-p 0001b000 08:03 1006974 /usr/lib/libgcc_s.so.1 b60e7000-b72de000 rw-p 00000000 00:00 0 b72df000-b73b7000 rw-p 00000000 00:00 0 b73b7000-b757c000 r--p 00000000 08:03 1856687 /usr/lib/locale/locale-archive b757c000-b757e000 rw-p 00000000 00:00 0 b757e000-b7719000 r-xp 00000000 08:03 1479914 /lib/libc-2.15.so b7719000-b771b000 r--p 0019b000 08:03 1479914 /lib/libc-2.15.so b771b000-b771c000 rw-p 0019d000 08:03 1479914 /lib/libc-2.15.so b771c000-b771f000 rw-p 00000000 00:00 0 b771f000-b7749000 r-xp 00000000 08:03 1479882 /lib/libm-2.15.so b7749000-b774a000 r--p 00029000 08:03 1479882 /lib/libm-2.15.so b774a000-b774b000 rw-p 0002a000 08:03 1479882 /lib/libm-2.15.so b774b000-b774e000 r-xp 00000000 08:03 1479881 /lib/libdl-2.15.so b774e000-b774f000 r--p 00002000 08:03 1479881 /lib/libdl-2.15.so b774f000-b7750000 rw-p 00003000 08:03 1479881 /lib/libdl-2.15.so b7773000-b7777000 rw-p 00000000 00:00 0 b7777000-b7778000 r-xp 00000000 00:00 0 [vdso] b7778000-b7798000 r-xp 00000000 08:03 1479958 /lib/ld-2.15.so b7798000-b7799000 r--p 0001f000 08:03 1479958 /lib/ld-2.15.so b7799000-b779a000 rw-p 00020000 08:03 1479958 /lib/ld-2.15.so bfeeb000-bff0d000 rw-p 00000000 00:00 0 [stack] Aditya

5 11

Most portable font name
by Philipp Gesang 18 May '12

18 May '12

Hi all, tl;dr: by which name to refer to a font. I was about to recommend (tomorrow; context: an introductory LaTeX course) *the* way of referring to a font by its name. As we all know, the same font (as in file) usually comes with a variety of possible denominations. “otfinfo -i” on a *file name* results in a list of *full name*, *Postscript name*, *unique id*, etc., which all might have some valid purpose. I have come across answers to assignments that made me wonder “How on earth did E get that to work on Eir system?”. There’s some background info [1] on the Fontforge pages but it doesn’t really answer my question: Which identifier is least likely to break things and at the same time most portable between both frontends (Fontspec, Simplefonts, typescripts) and platforms (Win/Linux/Mac)? For some time now I myself settled for the Postscript name as it never caused problems in typescripts and it’s got no spaces. The filename might be the most explicit one, but oftentimes contains spaces which I *always* replace with underscores prior to installing a font; also case insensitive filesystems might cause trouble. Also, some fonts have weird file naming schemes (e.g. CMU and the Paratype fonts), so extra comments may be required to support legibility of the resulting code. The typescripts that come with Context use both (“name:” and “file:”) but I have no clue why exactly which method was chosen over the other in what case. The fontspec documentation (and the Simplefonts module and our course so far) conforms to the WYSIWYG tradition of purportedly more human-readable, spaced identifiers, e.g. “TeX Gyre Bonum Bold”. (Cf. [1]: “FullName is designed to be read by humans”.) So I judged that my preferred choice might not be as good as I think. I got cold feet and am about to remove the slide where I recommend the PS name (I can do that later anyways). Is there -- apart from personal opinions -- some valid reason to prefer one name over the other *in general*? Thanks for any advice and opinions. Philipp [1] http://fontforge.sourceforge.net/fontinfo.html#Names

3 5

Lists and alternative=command
by Rogers, Michael K 17 May '12

17 May '12

I'd love help with this: I have list that uses alternative=command, and it stopped working when I switched from last year's TeXLive context to a recent beta. I've minimized the problem to this example: \definelist [MyList] \define[3]\MyListEntry{:#1:#2:#3:} \setuplist [MyList] [alternative=command,command=\MyListEntry] \starttext \writetolist[MyList]{First}{Second} \placelist[MyList] \stoptext It generates the following error three times, once per argument in \MyListEntry, I suppose. ConTeXt ver: 2012.05.14 16:00 MKIV fmt: 2012.5.16 int: english/english ... ! Argument of \MyListEntry has an extra }. system > tex > error on line 11 in file foo1789.tex: Argument of ... 1 \definelist [MyList] 2 \define[3]\MyListEntry{:#1:#2:#3:} 3 \setuplist [MyList] [alternative=command,command=\MyListEntry] 4 \starttext 5 \writetolist[MyList]{First}{Second} 6 \placelist[MyList] 7 \stoptext <inserted text> \par <to be read again> } \12>:79>:command ...ernativeparameter \c!command } \ifx \p_command \empty [\c... \strc_lists_apply_renderingsetup ...nderingsetup } \relax \the \t_lists_every... \strclistsentryprocess ... \fi \fi \fi \endcsname \dostoptagged \listextrapa... l.11 {} ... l.7 \stoptext Thanks, Michael ________________________________ This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments).

2 2

Testing TeX Live 2012
by Mojca Miklavec 17 May '12

17 May '12

Dear ConTeXt users, TeX Live 2012 is going to be released soon. After the first successful year of ConTeXt in TeX Live, it would be great to get enough testers before the release (to make sure that it works flawlessly) and to get rid of as many bugs as possible. See http://tug.org/texlive/pretest.html for links and instructions. You could try wget http://ctan.ijs.si/mirror/tlpretest/install-tl-unx.tar.gz tar xvzf install-tl-unx.tar.gz cd install-tl-<every-day-a-different-name> ./install-tl -gui -repository http://ctan.ijs.si/mirror/tlpretest and install a ConTeXt scheme for example. (Alternatively you can first fetch all the packages to local disk.) Then just add the binary path to your PATH and feel free to play. Mac users can also try MacTeX 2012 from tlpretest (with some extra care), but you first need to update to get the latest ConTeXt. Mojca (The version of ConTeXt is the same as latest beta, so any bugs fixed in beta can just as well proliferate to TeX Live.)

4 10

Re: [NTG-context] thinrules
by Wolfgang Schuster 17 May '12

17 May '12

Am 17.05.2012 um 18:09 schrieb Meer, H. van der: > Thanks, > > From your answer I understand that collapsing the preceding vertical space is impossible with \thinrules. \thinrule adds \strut at the begin of the rule which results in vertical space above and below. Wolfgang

1 0

Local modules not found
by Rogers, Michael K 17 May '12

17 May '12

Hi, I upgraded to the latest beta from the 2011 stable version for the first time. Now my local modules are not found. Having searched the wiki and the mailing list, I can find no help. Any ideas? Error messages: \usemodule[homework-fmt] --> resolvers > modules > not found: 'homework-fmt' \input homework-fmt --> ! I can't find file `homework-fmt'. Here is a snippet from "context --generate" that might indicate the problem (/Users/mike/Library/texmf contains my tex modules : resolvers | methods | resolver: method=generators, how=uri, scheme=file, argument=/Users/mike/Library/texmf resolvers | expansions | scanning path '/Users/mike/Library/texmf', branch '/Users/mike/Library/texmf' resolvers | expansions | 266 files found on 20 directories with 58 uppercase remappings resolvers | resolving | resolvers | resolving | not saving runtime tree '/Users/mike/Library/texmf' Thanks! Michael [Background: I started learning ConTeXt last winter using the 2011 TeXLive version and TeXShop (I've a Mac). Now the semester is over, I'm trying to update to a more recent ConTeXt. First I got TeXLive 2012 pre-release, but TeXShop still used last year's ConTeXt. So I followed the wiki instructions for getting the latest beta. Eventually I found a directory name was different and now TeXShop uses the latest beta. The latest beta is in a separate directory tree from TeXLive, which I set up 6 months ago or so from instructions on the wiki for running Mark IV.] ________________________________ This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments).

3 3

thinrules
by Meer, H. van der 17 May '12

17 May '12

Macro \thinrules places vertical whitespace before the first of its lines. I would like to get rid of that one, but have no success in doint that. Usage is: \par\thinrules[..]\par Howto? H van der Meer

2 1