- ntg-context - NTG Mailing Lists

solutions and problems
by Xan 23 Feb '14

23 Feb '14

Hi, Just a question about blocks... I consulted the manual, but I'm in trouble: I have this definitions: % the exercise \defineenumeration [exercici] [alternative=serried,text={\startcolor[darkblue]Exercici\stopcolor},stopper={.\space},left={\bgroup},right={\egroup},width=fit,headstyle=\ss,distance=0.25em,width=fit] \defineenumeration[resposta][headstyle=\ss,text={Solucions},width=fit,alternative=serried] \defineblock[resposta] % the answer \hideblocks[resposta] And in my text, I have: \startexercici \beginresposta \resposta Exercici 2 (Solucions: \startitemize[a,text] \item D, \item I, \item D, \item No té relació, \item D, \item D, \item No té relació, \item No té relació, \item D.\stopitemize) \par \endresposta \stopexercici ... \startmode[solucions] \subject{Respostes} %Answers \selectblocks[resposta][criterium=section] \stopmode ... Is there any way that the answers (resposta) has the same number as the 'exercici' in which it belongs to? If not, I have to put "Solutions of exercici 2" in my 'resposta' Thank you very much

6 12

how to set the CropBox in MkIV?
by Sanjoy Mahajan 23 Feb '14

23 Feb '14

What is the MkIV/LuaTeX way to set the CropBox? In MkII/PDFTeX, I used \pdfpagesattr = {/CropBox [54 72 558 720]} With MkIV, I've tried \pdfcompresslevel 0 \pdfbackendsetpagesattribute{CropBox}{[54 72 558 720]} \starttext \input knuth \stoptext but that set the CropBox as a string, and didn't override the A4 setting: <</Type/Pages /CropBox ([54 72 558 720])/Count 1/Kids[16 0 R]>> I also tried \pdfcompresslevel 0 \startluacode local box = lpdf.array{54, 72, 558, 720} lpdf.addtopagesattributes("CropBox",box) \stopluacode \starttext \input knuth \stoptext and that produced an improved line in the Pages object: <</Type/Pages /CropBox [ 54 72 558 720 ]/Count 1/Kids[16 0 R]>> but the actual cropbox for the page is unchanged (A4), probably because the page object itself (object #16) overrides the CropBox with this: /CropBox [ 0.0000 0.0000 595.2756 841.8898 ] (This is all with the 2014.02.14 beta.) Regards, -Sanjoy

1 0

Font affects columnar list layout
by Thangalin 23 Feb '14

23 Feb '14

Hi, Been struggling with this issue: 1. Source test.tex: http://pastebin.com/raw.php?i=hPVmkATT 2. Chivo: https://www.google.com/fonts/specimen/Chivo 3. Gentium Basic: http://www.google.com/fonts/specimen/Gentium+Basic 4. Install fonts. 5. Run: context test.tex Looks fine. 1. Uncomment: %\setupbodyfont[TestFont] 2. Run: context.tex 3. View results: http://i.imgur.com/zttXyKA.png The columnar content has shifted from the left column to the right column. This can be addressed: 1. Uncomment: %before={\vskip-.5em}, 2. Run: context.tex 3. View results: http://i.imgur.com/OsUgiAy.png Works for two lines, but when additional content is added: 1. Uncomment: %\ingredient{1}{pkg}{applewood-smoked bacon}... 2. Run: context.tex 3. View results: http://i.imgur.com/4fjbWHv.png Several lines have disappeared completely, regardless of font. The lines can be made visible again, but then the situation reverts to shifting the content from the left column to the right column when there are only a couple of items in the list. I've tried grid=strut; grid=,; grid=verytolerant; and grid=stretch. Using a two-column setup, is there a way to reduce the amount of space? The best result I can achieve without losing any content contains too much extraneous whitespace: http://i.imgur.com/A3RhnjS.png Thank you!

2 2

\doifemptyelse
by Pablo Rodriguez 23 Feb '14

23 Feb '14

Dear list, I have the following sample: \starttext \chapter{Chapter} .\doifemptyelse{\getmarking[section][current]} {\getmarking[chapter][current]} {\getmarking[section][current]}. \section{Section} .\doifemptyelse{\getmarking[section][current]} {\getmarking[chapter][current]} {\getmarking[section][current]}. \stoptext I must be missing something extremely basic, because I think that the first condiitonal occurs when \getmarking[section][current] is empty (dots have nothing in between). How can I make the first conditional work? Many thanks for your help, Pablo -- http://www.ousia.tk

3 6

Re: [NTG-context] Protrusion cancellation by index term
by Jan Tosovsky 22 Feb '14

22 Feb '14

On 2014-02-22 Jan Tosovsky wrote: > > when a punctuated phrase appears at the beginning of the line, it is > not protruded correctly when preceded by an index term. > > ... \index{foo}>Bar< ... > > A minimal example is available at > http://drifted.in/other/sample.tex > > I cannot place the space character between these two parts (which > helps) as I sometimes need to join this and the previous phrase with > the non-breaking space. > It is more serious issue than expected. Consider next two variants: (1) sentence, \index{primary}>Primary< (2) sentence,\index{primary} >Primary< When the line is broken after a comma: ad 1) starting guillemet is not protruded ad 2) ending comma is not protruded When \index is surrounded by spaces from both sides, the space is rendered at the beginning of the next line (resulting in 'indenting'). :-S I'd be grateful for ignoring any non document content preceding punctuation to avoid its influence on protrusion. Thanks, Jan

1 0

Re: [NTG-context] Paragraph - the last line handling
by Jan Tosovsky 22 Feb '14

22 Feb '14

On 2014-02-19 Jan Tosovsky wrote: > On 2013-11-23 Hans Hagen wrote: > > On 11/23/2013 2:43 PM, Jan Tosovsky wrote: > > > On 2013-11-23 Hans Hagen wrote: > > >> On 11/22/2013 11:07 PM, Jan Tosovsky wrote: > > >>> > > >>> in my document there are lot of cases when the last line in the > > >>> paragraph has a very narrow gap on the right. > > >> > > >> \hsize 15.4cm > > >> > > >> \input tufte > > >> > > >> \parfillskip30pt plus 1 fill \input tufte > > > > > > Wow, exactly! Thanks a lot. > > > > > > Sorry for a dumb question, but is there any way how to use it > > > globally for all paragraphs in my document? > > > > no, as i need to think of a decent interface to that (so remind me in > > a few months) > > When this gap (parfillskip) is set in the beginning of the document, it > is shared for all paragraphs within the document. I was not aware of that. > I've found while this setting in the beginning of the document is applied to all paragraphs, it is not shared in footnotes. I am fixing it by repeating this command at the beginning of every footnote, but I am curious why footnotes are handled differently. Is it possible to set this behavïour for footnotes globally only once? Thanks, Jan

1 0

Obscure math/color "bug" (namespace clash)
by Alan BRASLAU 22 Feb '14

22 Feb '14

Hello, I came across the following obscure math/color namespace clash: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \definecolor [tan] [h=d2b48c] % Taken from \setupcolor [x11] \starttext $\tan θ$ \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% One solution would be to give precedence in math mode to the standard mathematical tokens (here \tan). Another solution would be simply to avoid the use of "tan" (as a color). In colo-imp-x11.mkiv it could be renamed "tan0" (there is already tan1, tan2, tan3). This is somewhat unfortunate as "tan" is a standard X11 color name. On the other hand, one would like to be able to use colors in math mode as well... So I propose the following patch: 121c121 < \definecolor [tan0] [h=d2b48c] % ! namespace clash with $\tan$ --- > \definecolor [tan] [h=d2b48c] Alan

2 1

Re: [NTG-context] Hanging punctuation misalignment in footnotes
by Hans Hagen 22 Feb '14

22 Feb '14

On 2/22/2014 1:25 AM, Jan Tosovsky wrote: > On 2014-02-22 Jan Tosovsky wrote: >> >> when hanging in footnotes is enabled and the starting character is a >> punctuation, it is not protruded. However, the same character in the >> footnote body works fine. When both cases are close each other, it >> looks weird, see the screenshot: >> >> http://drifted.in/other/footnote_alignment.png >> >> Would it be possible make this behaviour uniform - either do not >> protrude it >> on the starting (left) edge or protrude it everywhere? >> > > A minimal example is available at > http://drifted.in/other/sample.tex > > (those guillemets would be lost here in the mailing list) > > Tested in the current beta on Windows (it requires Palatino Linotype font). Hard to solve that one fast .. basically all that gets bound to a next characters makes that next character not protrude. This is not something the engine can solve as it doesn't know what it deals with (so the current behaviour is as it should be). Maybe in a future version of context I can deal with it (as I know how to do it, but that doesn't help much now). 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 -----------------------------------------------------------------

2 1

Protrusion cancellation by index term
by Jan Tosovsky 22 Feb '14

22 Feb '14

Dear All, when a punctuated phrase appears at the beginning of the line, it is not protruded correctly when preceded by an index term. ... \index{foo}>Bar< ... A minimal example is available at http://drifted.in/other/sample.tex I cannot place the space character between these two parts (which helps) as I sometimes need to join this and the previous phrase with the non-breaking space. Any idea how to fix this? Thanks, Jan

1 0

Re: [NTG-context] Hanging punctuation misalignment in footnotes
by Jan Tosovsky 22 Feb '14

22 Feb '14

On 2014-02-22 Jan Tosovsky wrote: > > when hanging in footnotes is enabled and the starting character is a > punctuation, it is not protruded. However, the same character in the > footnote body works fine. When both cases are close each other, it > looks weird, see the screenshot: > > http://drifted.in/other/footnote_alignment.png > > Would it be possible make this behaviour uniform - either do not > protrude it > on the starting (left) edge or protrude it everywhere? > A minimal example is available at http://drifted.in/other/sample.tex (those guillemets would be lost here in the mailing list) Tested in the current beta on Windows (it requires Palatino Linotype font). Jan

1 0