ntg-context July 2015

ntg-context@ntg.nl

46 participants
109 discussions

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

Forms and JavaScript
by Henning Hraban Ramm 07 Oct '15

07 Oct '15

Hello, while trying to create some interactive forms using latest beta (MkIV), I found that JavaScripts are only then copied into the PDF, if there’s a \goto referencing a JS function. According to the old widgets manual I thought I could set default values of fields calling JS functions or variables as [JS(MyFunc)], but that doesn’t work. \starttext \setupinteraction [state=start] \startJSpreamble{formtest} % this JS code is only copied to the PDF if the \goto below is uncommented! var d = new Date(); var df = this.getField("Datum"); var CurDate = util.printd("dd.mm.yyyy", d); df.value = CurDate; function toggleField(){ var f = this.getField("Datum"); f.display = ! f.display; } \stopJSpreamble %\goto{toggle}[JS(toggleField)] \blank \setupfield[MMshortString][reset,horizontal][height=5mm, width=50mm, frame=off, bottomframe=on] \definefield[Datum][line][MMshortString][][JS(CurDate)] % JS(CurDate) ends up verbatim in the field Date: \field[Datum] \stoptext Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer)

3 6

(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

Selectively supressing ligatures
by juh 11 Aug '15

11 Aug '15

Hi, I use the package "selnoligs.sty" in LuaLaTeX to selectively suppress ligatures. >From the selnolig package description: "The selnolig package suppresses typographic ligatures selectively, i.e., based on predefined search patterns. The search patterns focus on ligatures deemed inappropriate because they span morpheme boundaries. For example, the word shelfful, which is mentioned in the TEXbook as a word for which the ff ligature might be inappropriate, is automatically typeset as shelfful rather than as shelfful." This works with LuaLaTeX: \documentclass{article} \usepackage{fontspec} \usepackage[ngerman]{selnolig} \begin{document} Auflage (no ligature) Abfluss (ligature) Auffahrt (no ligature) Schiffe (ligature) \end{document} How can I achieve the same in ConTeXt? This does not work: \mainlanguage[de] \starttext \language[de] Auflage Abfluss Auffahrt Schiffe \stoptext TIA juh

3 7

Linenumering inside floats
by Aditya Mahajan 04 Aug '15

04 Aug '15

Hi, I am forwarding a feature request for the t-vim module: https://github.com/adityam/filter/issues/21 Is there a way to enable line numbering inside floats: \definefloat[sourcecode][sourcecodes] \startbuffer \startlinenumbering \input tufte \stoplinenumbering \stopbuffer \starttext \startplacesourcecode \getbuffer \stopplacesourcecode \getbuffer \stoptext Thanks, Aditya

2 4

r2l alignment and linenumbering conflict?
by talazem＠fastmail.fm 04 Aug '15

04 Aug '15

There seems to be some limitation (or bug) in right-to-left (r2l) alignment, when used alongside linenumbering. Consider the following: > \setuppapersize[A6] > \starttext \showframe > > \section{Incorrect} > \startlinenumbering > \startalignment[r2l] > Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque molestie dictum quam non congue. Integer ut dolor vel mi vestibulum molestie vel et nulla. > \stopalignment > \stoplinenumbering > > \section{Correct} > \startalignment[r2l] > Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque molestie dictum quam non congue. Integer ut dolor vel mi vestibulum molestie vel et nulla. > \stopalignment > > \stoptext The RTL alignment works correctly on its own. However, when you introduce another factor — here, linenumbers — the RTL alignment is ignored. Perhaps this linked to the problem with of RTL footnotes being discussed here: gmane.comp.tex.context/92113 <http://article.gmane.org/gmane.comp.tex.context/92113>? Best wishes, Talal

6 24

Re: [NTG-context] footnotes when using RtL (Arabic)
by talazem＠fastmail.fm 03 Aug '15

03 Aug '15

I’m reviving this old thread, as the problem appears to still exist. Consider the following: > \starttext \showframe > > \definenote[afootnote][rule={on,right},paragraph=no] > > \startalignment[r2l] > Testing.\afootnote{This is footnote one.} > Testing testing.\afootnote{This is footnote two.} > Testing testing testing.\afootnote{This is footnote three.} > \stopalignment > > \stoptext In the output (r2l.pdf), the text runs from right to left as it should, and the footnote reference numbers are in the right margin, as they should be. However, if we switch the option “paragraph” to “yes”, the entire frame no longer runs r2l (see the output in r2l-yes.pdf). What I want is for the text to read as follows: > .eerht etontoof si sihT 3 .owt etontoof si sihT 2 .eno etontoof si sihT 1 where the entire frame begins at the right margin, such that the first footnote number (1) is in the right margin, instead of in the left margin as it is in r2l-yes.pdf. To say it another way, the entire footnote frame should be r2l, regardless of its contents, perhaps (as Idris wrote to me) through some hard direction switch for the entire frame. Best wishes, Talal

5 23

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context July 2015