October 2015 - ntg-context - NTG Mailing Lists

Re: [NTG-context] Hanging punctuation misalignment in footnotes
by Wolfgang Schuster 29 Mar '16

29 Mar '16

Am 22.02.2014 um 01:25 schrieb Jan Tosovsky <j.tosovsky(a)email.cz>: > 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 There are two things which prevent the protrusion of the opening quote at the begin of the paragraph. One of these can be avoided with a change in the setup for footnotes but not the other without destroying the layout of the footnote text. One problem is the way how context places the footnote number in front of the text, by default context uses the \llap command to move the number into the left margin but this prevents also the protrusion of the opening quote. You can avoid this problem when you change the footnote setup to \setupnotation[footnote][alternative=margin]. <example> \definefontfeature[default][default][expansion=quality,protrusion=quality] \setupbodyfont[modern] \setupalign[hanging] \showframe[text][text] \starttext »Text« \noindent\hbox to 0pt{}»Text« \noindent\hbox to 0pt{\hss}»Text« \stoptext </example> The second problem which prevents the opening quote to protrude are the struts which are added by context at the begin and end of the footnote content and there is no way to disable them because they are needed to have proper spacing between the individual footnote texts on the same page. <example> \definefontfeature[default][default][expansion=quality,protrusion=quality] \setupbodyfont[modern] \setupalign[hanging] \showframe[text][text] \starttext »Text« \strut »Text« \stoptext </example> In the example below where I took care of these two problems (don’t take care of \begstrut in this way in your real document because it will cause many problems, it’s just for educational purpose) to show you this is what caused the unwanted output. <example> \definefontfeature[default][default][expansion=quality,protrusion=quality] \setupbodyfont[modern] \setupalign[hanging] \showframe[text][text] \setupnotation[footnote][alternative=margin,align=hanging] \starttext \let\begstrut\relax First Footnote.\footnote{»\input{ward}«} Second Footnote.\footnote{»\input{ward}«} \stoptext </example> Wolfgang

2 1

metafun
by Herbert Voss 24 Mar '16

24 Mar '16

It is a hard job to understand how all works ... I tried to create the first example of the documentation "Page 257 Anchors and layers", but failed with mkii and iv. The page is created, but without the graphical elements. Not using \startbuffer--\stopbuffer makes no difference. MTXrun | current version: 2010.07.30 11:35 Herbert \starttext \section {Anchors and layers} \startbuffer[a] \setMPpositiongraphic{X-1}{mypos:arrow}{to=X-2} \setMPpositiongraphic{X-2}{mypos:arrow}{to=X-3} \stopbuffer \startbuffer[b] In a previous section we saw that some \hpos {X-1} {words} were \hpos {X-2} {circled} and connected by an \hpos {X-3} {arrow}. As with most things in \CONTEXT, marking these words is separated from declaring what to do with those words. This paragraph is keyed in as: \stopbuffer \getbuffer[a,b] \stoptext

5 5

Re: [NTG-context] Protrusion cancellation by index term
by Hans Hagen 21 Mar '16

21 Mar '16

On 2/22/2014 2:38 PM, Jan Tosovsky wrote: > 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. well, think of it like this: [something]<text>[something else] with [something] being bound to < ... so that is then the boundary of the word, not < ... i might know a solution (but such -major- changes have to fit into my schedule) 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

Setting expansion depth limit for metapost
by Michal Suszko 18 Feb '16

18 Feb '16

I'm preparing quite long presentation -- nearly 3000 sides, 900 figures (500 distinct PNG files). I'm using ConTeXt MkIV installed using minimals (2010.03.12 19:49). Recently I'm hitting MetaPost capacity limit on expansion depth: !mplib : mp terminal: ! MetaPost capacity exceeded, sorry [expansion depth=10000]. Increasing expand_depth in texmf.cnf and regenerating formats with context --make doesn't help. expansion depth is still at 10000 in error message. texmf.cnf in texmf-local I've changed is reported by context as first one in log line starting with "mkiv lua stats : used config path" What am I missing? Michal

3 5

Supported architectures for minimals (any ppc users out there?)
by Mojca Miklavec 06 Feb '16

06 Feb '16

Hi, I would suggest dropping support for linux-ppc for the ConTeXt distribution unless somebody objects. I'm surprised about the number of ppc users on Mac (and would be curious to get more off-list feedback from those still using it). TeX Live planned to drop support this year, but it seems that it's staying for now. We are currently cross-compiling the binaries, but at the moment both luajittex and metapost compilations seem to be broken. We also don't seem to have any kfreebsd or sparc-solaris users, but as long as their builders enjoy supplying the binaries, that's fine by me ;) On the other hand I need to sit down one day and fix support for cygwin. I'm sorry that this didn't happen yet. Mojca

2 3

Overfull boxes using m-cweb
by Edwin Wisse 27 Jan '16

27 Jan '16

Hello, I am running into overfull boxes when including a weaved cweb file into a context document. The original reference to the cwebmac.tex file (the plain TeX macro) is commented out and replaced by \usemodule[cweb]. The cweb macros appear to expand something into \*11ptmmmt* which seems to have something to do with it. Is there anyone here with experience and deep (Con)TeX(t) knowledge who understands what is happening? Regards, Edwin ----------------------------------part of my log file------------------------------------------------ Overfull \hbox (6.4885pt too wide) in paragraph at lines 3--13 \*11ptmmmr* for the ap-pli-ca-tion de-vel-op-ment mod-ule. This is a small ap-p li-ca-tion which loads file \hbox(7.63889+2.13889)x398.33858 .\*11ptmmmr* f .\*11ptmmmr* o .\*11ptmmmr* r .\glue(\spaceskip) 3.66628 .\*11ptmmmr* t .etc. Overfull \hbox (8.38132pt too wide) in paragraph at lines 3--13 \*11ptmmmr* with point and line da-ta and dis-plays it in a win-dow. It pro-vid es a us-er in-ter-face al- \hbox(7.63889+2.13889)x398.33858 .\*11ptmmmr* w .\*11ptmmmr* i .\*11ptmmmr* t .\*11ptmmmr* h .\glue(\spaceskip) 3.66628 .etc.

4 4

disabling ligatures in selected words
by Thomas A. Schmitz 12 Jan '16

12 Jan '16

Hi, in German typography, ligatures are disabled at boundaries between what used to be independent words (Wortfugen). Thusly, in a correct German text, you'd find Anflug (with fl-ligature) but Auf|lage (without ligature). I know that I can prevent a ligature with something like Auf\/lage or even Auf|*|lage. However, I typeset from xml and would much rather have a general solution so I can leave my generated xml files alone. Something like a list where I could list "ligature exceptions" the way we have a file with hyphenation exceptions. Is anything like this possible? Thanks Thomas

4 4

goto
by Meer, Hans van der 28 Nov '15

28 Nov '15

I would like to be able to go directly to a local document by an interaction statement. The \goto command seems to be meant for this. However, the descriptions in the command reference and the Wiki do not explain all of its parameters: In \goto{1}{2}[3] parameters 1 and 2 are marked CONTEXT and 3 is marked REFERENCE. I could find parameter {1} typeset in the text and [3] as the reference in for example a \placefigure. What is {2} supposed to do? \goto{}Something}[] does not places Something to find. I tried to effect the jump to a document on my system with \goto{local-doc}[/Volumes/Users/myhome/Documents/myfigure.jpg] but this does not works as I hoped. How to? Hans van der Meer

2 1

\placeinitial not working
by Alan Bowen 03 Nov '15

03 Nov '15

\placeinitial used to work but now does not with the latest beta. Try the example from http://wiki.contextgarden.net/Initials. \setupinitial[color=red,font=Bold sa 4,distance=3pt,state=start,n=3] \starttext \placeinitial \input knuth \stoptext Alan

4 7

New btx code problem with quote protrusion, redux
by Rik Kabel 02 Nov '15

02 Nov '15

At Wolfgang’s request, a new thread for this subject. I have cleaned up the example from the July 5 posting, but the problems are the same as shown there. In July Alan suggested that there might a bug here, but nothing has been done to address it since then. Wolfgang suggested (http://www.mail-archive.com/ntg-context%40ntg.nl/msg35580.html) that method=font is required for proper protrusion handling for quotations. 1. When \setupdelimitedtext[quotation][method=font] is present /and //there is //no citation//in a footnote within a startquotation block and a bibliography is produced/, compilation proceeds normally. 2. When \setupdelimitedtext[quotation][method=font] is present /and //there is a citation//in a footnote within a startquotation block and a bibliography is produced,/ the compilation complains of a missing right curly. When allowed to continue to completion the protrusion for the opening quotation marks does not match the protrusion for similar marks not produced through \startquotation. Citations in footnotes outside quotation blocks are not a problem. Without a bibliography (\placelistofpublications) 3. When \setupdelimitedtext[quotation][method=font] is present, the [right] option of \startblockquotation is treated as text within the quotation. This can be resolved by adding “leftmargin=” to the \setupdelimitedtext[quotation] command (but that complicates matters when you want other alignments). Similarly, the [left] and [middle] options are ignored as options and appear as text. 4. When “method=font” is not present, protrusion for block quotations (\startblockquotation … \stopblockquotation) is greater than and not aligned with other protrusion. 5. When “method=font” is not present, protrusion for non-block quotations (\quotation{…}) is not done at all. 6. With the older bibliography system, footnotes in citations in quotation blocks do not cause a halt in compilation. 7. With the older bibliography system, item 3 is still a problem, that is, method=font appears to be inimical to the left, right, and middle options for \startblockquotation without regard to the bibliography system in use. \showframe \definefontfeature [default][protrusion=quality] \setupalign [hz,hanging] % The next line should allow \startquotation to protrude quotes properly \setupdelimitedtext[quotation][method=font] %================== % For testing with old regime, enable next and disable following %\setupbibtex[database=sample.bib] % requires sample.bib in current directory %------------------ % For testing with new regime, disable above and enable following \definebtxdataset [sample] % finds and uses distribution sample.bib \usebtxdataset [sample.bib] %================== \starttext \startparagraph There is a citation in the footnote to this standard paragraph\footnote{This footnote has a citation \cite[Eijkhout1991].} \stopparagraph \startparagraph \startquotation[right] There is a citation in the footnote to this block quotation\footnote{This footnote has a citation \cite[hh2010a].} \stopquotation \stopparagraph \startparagraph \startquotation[right] There is no citation in the footnote to this block quotation\footnote{This footnote has no citation.} \stopquotation \stopparagraph \startparagraph \quotation{There is a citation in the footnote to this non-block quotation paragraph\footnote{This footnote has a citation \cite[Eijkhout1991].}} \stopparagraph \startparagraph \quotation{There is no citation in the footnote to this non-block quotation paragraph\footnote{This footnote has no citation.}} \stopparagraph \startparagraph “There is a citation in the footnote to this standard paragraph\footnote{This footnote has a citation \cite[Eijkhout1991].}” \stopparagraph \startparagraph “There is no citation in the footnote to this standard paragraph\footnote{This footnote has no citation.}” \stopparagraph \blank[big] %================== % For testing with old regime, enable next and disable following %\placepublications %------------------ % For testing with new regime, disable above and enable following \placelistofpublications %================== \stoptext -- Rik

3 5