June 2015 - ntg-context - NTG Mailing Lists

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

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

Bleeding pictures as floats?
by Henning Hraban Ramm 30 Jul '15

30 Jul '15

Hi, I hope BachoTeX was a success! Is it possible to use the float placing mechanisms for pictures that go beyond the type area or even beyond the page? In the book I’m typesetting, most pictures need to fill the whole width of the page (i.e. plus 3mm bleed), but not all cover a full page. I don’t know how to tell \externalfigure or \placefloat a negative offset. Or can I use layers with floats? Of course the text should flow around the pictures. BTW, what does the „object“ key of \setupexternalfigures do? Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer)

2 6

Line wrapping inconsistency with tolerance, alignment and framed
by Christoph Reller 24 Jul '15

24 Jul '15

Hi, I have an (admittedly carefully crafted) example, see below. My question: Why is the line wrapping different for this case within a framed and outside of a framed? How can I control the amount of space left on a line before breaking the line within and without a framed consistently? Any insight is welcome. Christoph MWE: \setuptolerance[horizontal,stretch,verytolerant] \defineframed[myframe][align=flushleft,frame=off,offset=0pt] \starttext \def\super{supercalifragilisticexpialidoc} \startalignment[flushleft] \unhyphenated{\super\ + \super\ + \super\ + \super} \stopalignment \myframe{\unhyphenated{\super\ + \super\ + \super\ + \super}} \stoptext

3 2

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

24 Jul '15

9 19

Accessibility and Tagged PDFs: Bugs and Feature Requests
by Dr. Dominik Klein 01 Jul '15

01 Jul '15

Context is the only Tex-based system that allows to properly tag a pdf. Tagged PDFs are one major requirement for accessibility. Indeed, in several large organizations/universities, accessibility is mandated by law, and this is a major obstacle for using Tex. In practice compliance is often assessed with Acrobat Pro's accessibility checker. Context produces a nice tag-structure, but there are some minor issues that prevent compliance to [1], and hence Acrobat Pro complains during the check. The main issues are: 1.) Elements that are not contained in the structure tree are not marked as an artifact. Consider this example: ------------------------------- \setuptagging[state=start] \setuppagenumbering [location=, alternative=doublesided] \setupheadertexts [{Chapter~\getmarking[chapternumber]\hskip1em\getmarking[chapter]}] [{Header Right}] [{Header Left}] [{Chapter~\getmarking[chapternumber]\hskip1em\getmarking[chapter]}] \setupfootertexts [Organization Name] [pagenumber] [pagenumber] [Organization Name] \starttext \startfrontmatter something \stopfrontmatter \startbodymatter some more text here \stopbodymatter \stoptext ------------------------------- Header, footer, pagenumber etc. will not be included in the tag structure. Of course this makes absolutely sense and is correct, however according to Section 14.8.2.2.2 of [1], then this content that is not in the structure tree should be marked as an artifact, i.e. /Artifact BMC .. EMC or in an advanced way with /Artifact PropertyList where the type of Artifact can be defined. It would be nice if those elements that are not included in the tag tree would be marked as artifacts by default. The same holds for \startelement[ignore] when one wants to explicitly remove something from the structure tree. 2.) Images without alternate text: According to Section 14.9.3 of [1], alternate descriptions in human readable text should be provided for images. It would be really helpful, if these could be defined in the source tex file, and then automatically added when creating the object in the structure tree. I.e. it would be nice to have something like: \placefigure[top][Image Reference]{Caption}{ \externalfigure[cow.pdf][width=10cm][alternate text = "This images shows a beautiful cow."] } The same holds for formulas: Whereas the mathml-like tagging of Context is very advanced, sometimes it might be still helpful to supply a textual description (alt-text ="The definition of the Pythagorean theorem: a^2 + b^2 = c^2") 3.) Tag names of the resulting tag structure: Section 14.8.4 of [1] defines standard structure types, such as <H>, <P>, <Sect> etc. Context creates a tag-tree that uses names directly representing the structure names of the context laguage, such as <sectiontitle>. This should however be mapped to something standard, such as <H>. Interestingly these mappings seem to have been considered in strc-tag.mkiv but I was unable to generate such a tagged pdf. Editing/Outcommenting things in strc-tag.mkiv didn't work for me. It would be nice if there was a switch somewhere, i.e. \setuptagging[state=start,tagnames=pdf17] - or maybe I overlooked something? 4.) Acrobat Pro always complains that the language for the whole document is not set. 5.) Tables The generated structure looks something like this: <table> <tablerow> <tablecell> ... <tablerow> <tablecell> ... Here, not only are the tag names non-compliant, also the tag structure should distinguish between the table header (THead), and table rows (TBody), c.f. Section 14.8.4.3.1 of [1]. A simple heuristic would be to always put the first line into THead tags, and the rest of the able into TBody. 6.) It would be nice if a flat tag structure could be created optionally. This is not a required feature according to [1], and in fact a properly nested structure is surely preferable for the final output; for debugging or checking during document creation however, a flat structure tree sometimes is easier to browse through. All in all, these seem to be the only issues that prevent accessible PDF documents with context. For those within an organization where accessibility is required legally for all publications, compliance to at least Acrobat Pro's checks is a huge issue. I do not know how difficult these things are to implement in Context (personally I am just lost in the code), but looking at e.g. tex.stackexchange for question related to accessibility, this is indeed a major obstacle for several people. cheers - Dominik [1] ISO 32000-1:2008, available at http://www.adobe.com/devnet/pdf/pdf_reference.html

5 7