- ntg-context - Mailing Lists

\framed[height=broad] vs \framed[height=fit]
by Aditya Mahajan 21 Apr '10

21 Apr '10

Hi, I was updating the wiki page on \framed and realized that I do not know the difference between height=broad|fit in \framed. Reading pack-rul suggests that both should behave similarly. The following example from pack-rul also shows no difference. \starttext \bgroup \showstruts \dontcomplain \startlinecorrection \halign{#\enskip&#\enskip&#\enskip&#\enskip&#\enskip&#\cr \framed[width=.2\hsize, height=.2\hsize, align=] {a\par b\par c}& \framed[width=.2\hsize, height=broad, align=] {a\par b\par c}& \framed[width=.2\hsize, height=fit, align=] {a\par b\par c}& \framed[width=fit, height=.2\hsize, align=] {a\par b\par c}& \framed[width=fit, height=broad, align=] {a\par b\par c}& \framed[width=fit, height=fit, align=] {a\par b\par c}\cr \noalign{\vskip1em} \framed[width=.2\hsize, height=.2\hsize, align=yes] {a\par b\par c}& \framed[width=.2\hsize, height=broad, align=yes] {a\par b\par c}& \framed[width=.2\hsize, height=fit, align=yes] {a\par b\par c}& \framed[width=fit, height=.2\hsize, align=yes] {a\par b\par c}& \framed[width=fit, height=broad, align=yes] {a\par b\par c}& \framed[width=fit, height=fit, align=yes] {a\par b\par c}\cr \noalign{\vskip1em} \framed[width=.2\hsize, height=.2\hsize, align=right] {a\par b\par c}& \framed[width=.2\hsize, height=broad, align=right] {a\par b\par c}& \framed[width=.2\hsize, height=fit, align=right] {a\par b\par c}& \framed[width=fit, height=.2\hsize, align=right] {a\par b\par c}& \framed[width=fit, height=broad, align=right] {a\par b\par c}& \framed[width=fit, height=fit, align=right] {a\par b\par c}\cr \noalign{\vskip1em} \framed[width=.2\hsize, height=.2\hsize, align=left] {a\par b\par c}& \framed[width=.2\hsize, height=broad, align=left] {a\par b\par c}& \framed[width=.2\hsize, height=fit, align=left] {a\par b\par c}& \framed[width=fit, height=.2\hsize, align=left] {a\par b\par c}& \framed[width=fit, height=broad, align=left] {a\par b\par c}& \framed[width=fit, height=fit, align=left] {a\par b\par c}\cr \noalign{\vskip1em} \framed[width=.2\hsize, height=.2\hsize, align=middle] {a\par b\par c}& \framed[width=.2\hsize, height=broad, align=middle] {a\par b\par c}& \framed[width=.2\hsize, height=fit, align=middle] {a\par b\par c}& \framed[width=fit, height=.2\hsize, align=middle] {a\par b\par c}& \framed[width=fit, height=broad, align=middle] {a\par b\par c}& \framed[width=fit, height=fit, align=middle] {a\par b\par c}\cr} \stoplinecorrection \blank[2*big] \egroup \stoptext Is there a difference between the two? If not, why do we have two values then? Aditya

2 1

\setuptyping[numbering=line] don't emit line numbers
by Hongwen Qiu 21 Apr '10

21 Apr '10

$ context --version MTXrun | current version: 2010.04.16 21:08 $ luatex --version This is LuaTeX, Version beta-0.60.0-2010040422 I found that \setuptyping[numbering=line] no longer produces line numbers any more. So are there something changed, or just it's ought to be ok?

1 0

Re: [NTG-context] [pdftex] Problem: testing MkIV on pdftex-t manual source
by Wolfgang Schuster 21 Apr '10

21 Apr '10

Am 20.04.10 05:09, schrieb Richard Chan: > I'm new to all this stuff - does MkIV build the pdftex manual? > > I ran into this problem running ConTeXt minimals on the pdftex 1.4 > manual sources > context --mode=screen --result=TESTING pdftex-t: > > nh > l.689 \PDFTEX\ is maintained by \THANH > , Martin Schr\"oder, Hans Hagen, > Taco > ? > > I could build the manual using texexec. > Can you replace in the s-abr-01.tex file which is in the same folder as the manual the defintion for \THANH with this one \def\THANH{H\agrave n Th\ecircumflexacute\ Th\agrave n} % Hàn Thế Thành Wolfgang

3 2

packed itemize and beforehead
by Honza Pohanka 20 Apr '10

20 Apr '10

Following construction does not work for me. \setupitemize[each][packed][beforehead={}] Is there any possibility to suppress the vertical space around \head in packed itemize? (latest MKII) greetings Jan -- Tato zpráva byla vytvořena převratným poštovním klientem Opery: http://www.opera.com/mail/

1 0

Page headers & drop capitals not working but pagenumbering is
by Tom 20 Apr '10

20 Apr '10

The following code numbers the pages as I desired and the TOC lists those page numbers. However, it is not doing two things as I desire and would appreciate it if someone could indicate precisely which lines of code need to be corrected. In the front matter, page headers should be on the recto of the TOC (page vi) and pages 2 and 3 of the introduction. Page headers seem to be operating correctly in the body of the book. \placeinitial is not creating drop capitals on the first page of each chapter in the body of the text. Example code follows: %figure on left - chapter number and title on right \def\MyChapterCommandM#1#2% #1 is number, #2 is text {\startfiguretext[left]{none} {\externalfigure[flowers][width=.2\textwidth]} {\framed[frame=off,align=middle,width=broad] {\switchtobodyfont[15pt] #1\\\blank[small] #2}} \stopfiguretext} %no figure on left - chapter number and title on right \def\MyFrontMatterCommand#1#2% #1 is number, #2 is text {\framed[frame=off,align=middle,width=broad] {\switchtobodyfont[15pt] #1\\\blank[small] #2}} %eliminate headers on blank page at end of chapter \definepagebreak[mychapterpagebreak][yes,header,right] %put pagenumber on bottom of first page of chapter \definetext[chapter][footer][pagenumber] \setuphead[chapter][header=high,footer=chapter,page=mychapterpagebreak] \setuphead[title][header=high,footer=chapter,page=mychapterpagebreak] %turn off putting naked page numbers on pages \setuppagenumbering[location=] \setupsectionblock[bodypart][page=chapter] \setupsectionblock[frontpart][page=chapter] \startsectionblockenvironment[frontpart] \setuphead[title] [command=\MyFrontMatterCommand,textstyle=\ss\bf,number=no, header=empty,footer=chapter,page=mychapterpagebreak, after=\vskip 0.5in] \setuphead[chapter] [command=\MyFrontMatterCommand,textstyle=\ss\bf,number=no, header=empty,footer=chapter,page=mychapterpagebreak, numbercommand=\ss\bf\em\tfd,after=\vskip 0.5in,before=\vskip 1.0in \placeinitial %comment out this line to eliminate drop capitals ] \setupheadertexts[chapter] [chapter][pagenumber][pagenumber][chapter Example] \setupheadertexts[title] [title][pagenumber][pagenumber][title] \setuppagenumbering[alternative=doublesided] %\setupheader[state=stop] \stopsectionblockenvironment \startsectionblockenvironment[bodypart] \setuppagenumbering[alternative=doublesided] \setupheadertexts [chapter][pagenumber][pagenumber][Content Example] \setuphead[chapter] [command=\MyChapterCommandM,textstyle=\ss\bf, header=empty,footer=chapter,page=mychapterpagebreak, numbercommand=\ss\bf\em\tfd,after=\vskip 0.5in,before=\vskip 1.0in\placeinitial] %comment out this line to eliminate drop capitals \stopsectionblockenvironment \startsectionblockenvironment[appendix] \setupsectionblock[appendix][page=appendicespagebreak] \stopsectionblockenvironment \starttext \startfrontmatter Some random text to occupy front matter pages. \blank[medium] \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \page[right] \setuppagenumbering[state=start,alternative=doublesided,conversion=romannume rals,location=] \setupheader[state=start] \title{Contents} \placecontent[alternative=c,criterium=all] \blank[medium] Random text added to push TOC onto a second page to test page headers. \blank[medium] \input knuth \input knuth \input knuth \input knuth \chapter{Preface} \input knuth \page[right] %switch from lower case Roman numerals to Arabic numbers \setuppagenumbering[state=start,alternative=doublesided,conversion=numbers] \setuppagenumber[state=start,number=1] \setuphead[chapter] [command=\MyChapterCommandM,textstyle=\ss\bf,number=no, header=empty,footer=chapter,page=mychapterpagebreak, numbercommand=\ss\bf\em\tfd,after=\vskip 0.5in,before=\vskip 1.0in \placeinitial %comment out this line to eliminate drop capitals ] \chapter{Introduction} \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \stopfrontmatter \startbodymatter \chapter{Chapter One} \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \input knuth \chapter{Chapter Two} \input knuth \chapter{Chapter Three} \input knuth \page \stopbodymatter \startappendices \stopappendices \page[stop] \stoptext Tom Benjey 717-258-9733 voice 717-243-0074 fax Twitter: @TomBenjey

1 0

table, setuptable, TWO
by R. Bastian 20 Apr '10

20 Apr '10

Hello, in the following example (context iv): 1. \setuptable[rulethickness=0.04em] does not work 2. i wish that \NC 1 \NC \NC WOULD be something like \NC \TWO \center{1} \NC ? ----------------------------------------------------- \enableregime[utf] \setupindenting[yes, 3mm] \setupwhitespace[6mm] \mainlanguage[fr] \setupbodyfont[sansserif, 12pt] \definepapersize[monpapier][width=210mm, height=297mm] \definebodyfont[10pt][tt][bf=cmbtt10] \setuplines[space=on] \setupheadertexts[chapter] \setuppagenumbering[alternative=doublesided,location={footer,inleft}, command=\inframed] \language[fr] \setuphead[chapter][page=no, textstyle=cap, numberstyle=bold, after={\blank\hrule\blank}] \setuphead[title][after={\blank\hrule\blank}] \starttext \setupinterlinespace[line=1.1ex] [...] \subject{Sequences} {\setupinterlinespace[line=3ex]\midaligned \setuptable[rulethickness=0.04em] % <===================== \starttable[|r|r|r|l|r|r|r|r|r|r|r|r|] \HL \NC n \NC \bf temps \NC \bf min:sec \NC \bf genre \NC 1 \NC \NC 2 \NC \NC 3 \NC \NC 4 \NC \SR % <====== \HL \NC 0\NC 0\NC 0: 0\NC venter1 \NC 1\NC 9 \NC 1 \NC 9 \NC 1 \NC 9 \NC 1\NC 9 \FR \NC 1\NC 80\NC 1:20\NC ad lib.\NC \NC \NC \NC \NC \NC \NC \NC \MR \NC 21\NC 1180\NC 19:40\NC FIN \NC \LR \stoptable } \stoptext -- René Bastian www.pythoneon.org www.musiques-rb.org http://www.soundsurvey.org.uk/

2 3

LuaTeX beta-0.60.0 on Mac OS X Tiger (was: Latest beta...)
by Mojca Miklavec 20 Apr '10

20 Apr '10

Dear Mac users, according to the latest findings it seems that natively compiled LuaTeX still works on Mac OS X Tiger, but the cross-compiled one (compiled on 64-bit Mac OS X Snow Leopard) won't work on Tiger since the version beta-0.60.0. However, users report that it still runs perfectly fine on Leopard. Michael has sent me a new binary compiled on PPC; any user of Tiger on Intel (Willi?) that would like to use the new beta should sent me his own binary. But in any case it would be great if somebody would figure out the reason why the new LuaTeX fails to work on older macs. Before we were first able to cross-compile, Arthur had to suggest quite some changes in LuaTeX source, so maybe some of newly added libraries or some configuration started messing up things recently. Based on some assumptions: - there are not too many Mac OS X 10.4 machines around - there are not too many testers of the latest-and-greatest LuaTeX version (apart from ConTeXt community) - if there appears to be a combination of both, users will either stick to some older TeX or at least they will compile luatex on their own (again, apart from ConTeXt community) I expect that there will probably not be much more feedback about the problem, but it would be really really great to fix it. I have no access to Tiger at the moment. I hope that Dick will be able to provide some more feedback once he comes to it. Until that is resolved: if osx-intel/osx-ppc users want to have a working version of minimals, you'll have to provide luatex version on your own. Mojca On Wed, Apr 14, 2010 at 05:40, Michael Green wrote: > Mojca Miklavec writes: >> >> On Tue, Apr 6, 2010 at 21:24, Willi Egger wrote: >> > I just updated the latest beta in a completely new tree: >> > >> > I get now the following message: >> > >> > .../lua60/tex/texmf-osx-intel/bin/context: line 2: 1634 Bus error >> > mtxrun --script context "$@" >> [snip] >> This might as well be a mac-intel-only luatex-related problem >> (something for Taco in any case), but I cannot reproduce it yet. >> >> Mojca >> ___________________________________________________________________________________ > > I hit a similar problem on a ppc mac. So it's probably not an intel-only > thing. > The .firstsetup script crashes. It worked fine through at least March 23, > for what it's worth. > Here's a transcript > I have a crash log too, if that would help. > sudo ./first-setup.sh > receiving file list ... done > bin/ > bin/mtx-update.lua > bin/mtxrun > bin/texlua > wrote 18489 bytes read 4918220 bytes 229614.37 bytes/sec > total size is 6550101 speedup is 1.33 > MTXrun | fileio: variable 'SELFAUTOLOC' set to > '/Users/michaelgreen/Applications/context/bin' > MTXrun | fileio: variable 'SELFAUTODIR' set to > '/Users/michaelgreen/Applications/context' > MTXrun | fileio: variable 'SELFAUTOPARENT' set to > '/Users/michaelgreen/Applications' > MTXrun | fileio: variable 'TEXMFCNF' set to > '{$SELFAUTODIR,$SELFAUTOPARENT}{,{/share,}/texmf{- > local,.local,}/web2c}' > MTXrun | fileio: no cnf files found (TEXMFCNF may not be set/known) > MTXrun | using script: ./bin/mtx-update.lua > MTXrun | state: loaded > MTXrun | update: start > ./first-setup.sh: line 69: 5194 Bus error mtxrun --verbose > --script ./bin/mtx-update.lua -- > update --make --force --engine=all --context=beta --texroot=$PWD/tex $@

2 3

Grid typesetting, colums and vertical spacing
by Jan Pohanka 20 Apr '10

20 Apr '10

Hello, I'm trying to typeset on the grid, but I also need to reduce vertical spacing around headings. Unfortunately when i specify the 'before/after' setting for head, grid typesetting fails. Is there any option to make \blank more flexible? (I'm using MKII) example: \setupoutput[pdftex] \setuppapersize[A4,landscape][A4,landscape] \setuplayout[backspace=0.5cm,topspace=0.5cm,top=0cm,footer=0.5cm, width=middle,height=middle,margin=0cm,header=0cm] \setupbodyfont[10pt] \mainlanguage[cz] \enableregime[utf8] \setuppagenumbering[location=] \setuphead[section][style={\bf}] \setuphead[section][before={\blank[halfline,flexible]}] % not working well % \setuphead[section][after={\blank[halfline,flexible]}] % not working well \starttext \setuplayout[grid=yes] \showgrid \definecolumnset[my][n=4,distance=1.2em,balance=yes] % balance not work \startcolumnset[my] \section{Pokus} \input knuth \input knuth \subsection{Pokus 2} \input knuth \input knuth \input knuth \subsection{Pokus 3} \input knuth \stopcolumnset \stoptext greetings Jan -- Ing. Jan Pohanka Department of Measurement Faculty of Electrical Engineering Czech Technical University Technická 2, 16627 Praha 6 tel. 224352058 email: pohanj1(a)fel.cvut.cz

2 1

Re: [NTG-context] \define...
by Vyatcheslav Yatskovsky 20 Apr '10

20 Apr '10

"Curiouser and curiouser!" cried Alice. :) > > context has two different versions of \define, there is one in > syst-ext.mkii/syst-aux.mkiv > which has no parameters but prevents you from overwriting a existing > command (there \redefine > with allows this) and another one in core-sys.mkii/mkiv which replace > the first one and has > support for parameters but replace on the other side the old definition > (you get only the > terminal message) > > the question is, which behavious is correct, replace the old macro or > keep it, in my > opinion \define should leave the old definition untouced and \redefine > should be used > in this case (but we need a version with parameters) -- Best Regards, Vyatcheslav Yatskovsky

1 0

Re: [NTG-context] Pagenumbering
by Wolfgang Werners-Lucchini 20 Apr '10

20 Apr '10

Hallo Wolfgang! > >> \starttext > >> \startfrontmatter > >> > >> \completecontent[alternative=c] > >> > >> \setuppagenumbering[state=start,alternative=doublesided,conversion=romannumerals] > >> > >> ... > >> > >> \setuppagenumbering[state=start,alternative=doublesided,conversion=numbers] > >> \setuppagenumber[state=start,number=1] > >> > >> \stopfrontmatter > >> > >> \startbodymatter > >> > >> ... > >> > >> \stopappendices > >> > >> \stoptext > >> > > This example doesn't produce roman numerals with > > > http://www.ntg.nl/pipermail/ntg-context/2009/043296.html I can see, that this is working, but I do not understand why this complicated way is necessary nor can I understand why the above is not working. Is the normal(?) behaviour broken and the solution in your url a workaround? These are the context things which are very frustrating for a normal user and one may come to the conclusion that only the enlightend guru can use this system. Wolfgang

1 0