April 2014 - 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

(again) bug with bidi direction and \about references
by Pablo Rodriguez 12 Aug '15

12 Aug '15

Hi Hans, sorry for telling again, but I’m afraid that the following sample shows a serious buggy interaction between \setupdirections[bidi=on] and \about references. \setupdirections[bidi=on] \starttext \section[sectionone]{Section one} As said in \dorecurse{5} {\about[sectionone]\footnote{Body reference misplaced.}, } \stoptext Both \about and footnote references in body are misplaced. It would be great, if you could fix this. Many thanks for your help, Pablo -- http://www.ousia.tk

4 6

Critical editions with ConTeXt
by MANUEL GONZALEZ SUAREZ 24 Jul '15

24 Jul '15

9 19

next beta
by Hans Hagen 16 Apr '15

16 Apr '15

Hi The next beta will have this (I needed it for a manual): \starttext \starttabulate[||CL{darkred}|CM{darkgreen}CT{white}|CR{darkblue}||] \NC first \NC left \NC middle \NC right \NC last \NC \NR \NC first \NC \color[white]{left} \NC middle \NC \color[white]{right} \NC last \NC \NR \NC first \NC left \NC middle \NC right \NC last \NC \NR \stoptabulate \stoptext i.e. we already had CL CM and CR, so CT is new .. should be wikified. 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 -----------------------------------------------------------------

6 10

Steps in presentation
by pol stra 03 Jan '15

03 Jan '15

Hello, I tried to use some steps in a presentation. In the following conversation http://www.mail-archive.com/ntg-context@ntg.nl/msg53524.html, Wolfgang says that we can use the pre-60 module. So I tried this snippet: \usemodule[pre-stepwise] \starttext \StartSteps \startitemize \item one \FlushStep \item two \FlushStep \item three \FlushStep \stopitemize \StopSteps \stoptext But it does not compile: ConTeXt ver: 2012.09.11 20:36 MKIV fmt: 2012.9.12 int: english/english system > cont-new.mkiv loaded (/opt/context-minimals/texmf-context/tex/context/base/cont-new.mkiv system > beware: some patches loaded from cont-new.mkiv ) fonts > latin modern fonts are not preloaded languages > language en is active (pre60.tex resolvers > modules > loaded: 'pre-stepwise' (/opt/context-minimals/texmf-context/tex/context/base/s-pre-60.mkiv fonts > beware: no fonts are loaded yet, using 'lm mono' in box (/opt/context-minimals/texmf-context/tex/context/base/java-imp-stp.mkiv) interactions > javascripts > loaded: library 'stp' metapost > loaded: library 'nav' (/opt/context-minimals/texmf-context/tex/context/base/meta-imp-nav.mkiv)){/opt/context-minimals/texmf-fonts/fonts/map/pdftex/context/mkiv-base.map} fonts > preloading latin modern fonts (second stage) fonts > typescripts > unknown: library 'loc' {/opt/context-minimals/texmf-fonts/fonts/map/dvips/lm/lm-math.map}{/opt/context-minimals/texmf-fonts/fonts/map/dvips/lm/lm-rm.map} fonts > virtual math > unable to resolve name mapsfromchar fonts > fallback modern rm 12pt is loaded !LuaTeX error: There should have been a lua <node> here, not an object with type string! ==> Fatal error occurred, no output PDF file produced! Is there something broken in recent release of conteXt? By the way It seems there is no Rawsteps module anymore but it still is in the wiki. Is there is something like a bugtracker for conteXt, in order to signal when a feature is not working or outdated and signal when it is back (or definitly depreciate)? (it would be a complementary tool for the mailing list)

2 1