- ntg-context - Mailing Lists

Align TOC section numbers flushright
by Idris Samawi Hamid ادريس سماوي ح امد 26 Jun '18

26 Jun '18

Dear gang, Trying to get the sectioning numerals in the left margin of the TOC to be fushright; by default they are flushleft; see attached and below: ======= \setuphead[chapter] [conversion=R] \setuplist[chapter][width=2.8em] \definecombinedlist [content] [chapter] [level=chapter, alternative=c, numberalign=flushright] \starttext \placecontent[conversion=R] \startchapter[title={First},reference={}] \input ward \stopchapter \startchapter[title={Second},reference={}] \input ward \stopchapter \startchapter[title={Third},reference={}] \input ward \stopchapter \startchapter[title={Fourth},reference={}] \input ward \stopchapter \startchapter[title={Fifth},reference={}] \input ward \stopchapter \startchapter[title={Sixth},reference={}] \input ward \stopchapter \startchapter[title={Seventh},reference={}] \input ward \stopchapter \startchapter[title={Eighth},reference={}] \input ward \stopchapter \stoptext ======= numberalign=flushright would seem to be the governing keyword+value, but that has no effect here. For the form of the desired result, see toc-margin_numerals-MURE.pdf: https://www.dropbox.com/s/j0etnkt54zji6h5/toc-margin_numerals-MURE.pdf?dl=0 (note the stopper after each margin numeral!). Thank you in advance. Best wishes Idris -- Idris Samawi Hamid, Professor Department of Philosophy Colorado State University Fort Collins, CO 80512

2 4

latest beta and \seeindex
by Alan Bowen 25 Jun '18

25 Jun '18

The latest beta (ConTeXt ver: 2018.06.23 12:12 MKIV beta fmt: 2018.6.23) processes without a hitch but \seeindex is still not working as expected. In \starttext \index{sample} \index{fun+games}\index{fun+stuff} %\index{fun} \seeindex{fun}{sample} % now with heading (as it should be) \seeindex{fun}{blah} % not shown \seeindex{fun}{humbug} % not shown \seeindex{fun}{bug} % not shown \seeindex{fun+games}{entertainment} % not shown \placeindex[n=1] \stoptext When I generate the indices for my book, \seeindex{A}{B} works only if it is a unique x-ref and A is a heading. Multiple x-refs to the same heading fail as do x-refs to subheadings. Alan

4 9

letter: How to customize reference line?
by Paul Menzel 25 Jun '18

25 Jun '18

Dear ConTeXt folks, I am trying to customize the reference line in a letter. ``` $ context --version mtx-context | ConTeXt Process Management 1.01 mtx-context | mtx-context | main context file: /usr/share/texmf/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2017.05.15 21:48 ``` The example from Wolfgang’s `correspondence.pdf` [1] doesn’t work for me. ``` \setupletter [name={Joe User}, date=\currentdate] \setupletter [list={name,date}] ``` Only the date is shown in the reference line. The solution from chapter 9 also does not work. Still only the date is shown. ``` \setupletter [name={Joe User}, date=\currentdate] \setupletterstyle[reference][list={name,date}] ``` Do I need to create a new customized reference line to add other fields next to the date to the reference line? Kind regards, Paul [1]: https://bitbucket.org/wolfs/correspondence/downloads/

2 1

Table of Contents sectioning numbers in margin + oddity
by Idris Samawi Hamid ادريس سماوي ح امد 25 Jun '18

25 Jun '18

Dear gang, mtx-context | current version: 2018.06.24 18:28 In the attached and below, we want sectioning numbers placed and naturally aligned in the margin: ======= \definecombinedlist % \setuplist[] [content] [section] [level=section, alternative=c, criterium=local] \setuphead[section][alternative=inmargin] \setupitemize[1][inmargin][stopper=] \placecontent \starttext \startsection[title= First] \input ward \stopsection \startsection[title= Second] \startitemize[r] \startitem[] \input ward \stopitem \startitem[] \input ward \stopitem \stopitemize \stopsection \stoptext ======= 1. What is the most straightforward way to to the section numerals generated by \placecontent placed and aligned inmargin? 2. Oddity: Why does the TOC in the attached example default to a monospaced font? Thanks in advance. Best wishes Idris -- Idris Samawi Hamid, Professor Department of Philosophy Colorado State University Fort Collins, CO 80512

2 5

\reference not working with reference prefix and focus=standard
by Christoph Reller 25 Jun '18

25 Jun '18

Hi, Thank you, Hans, for supporting the focus=standard option in interactive PDFs. I stumbled over the following problem: \setupinteraction[state=start, focus=standard] \starttext \pushreferenceprefix{parent} \reference[label]{Text}Bla \page \about[label] \popreferenceprefix \stoptext The link's visual appearance is generated correctly and the PDF link annotation correctly references a named destination "parent:label". In the PDF's catalog, however, the only named destination has a name "label", lacking the prefix. Could you please consider fixing this issue? Kind regards, Christoph

1 0

\nopdfcompression and no date information
by Pablo Rodriguez 24 Jun '18

24 Jun '18

Dear list, I would like to avoid adding date info in certain PDF documents to be able to regenerate them having the same SHA512s. Is there a command (similar to \nopdfcompression) that has the same effect than compiling the document with "context --nodates"? Many thanks for your help, Pablo -- http://www.ousia.tk

2 2

MetaPost shading broken with latest beta
by Adam Reviczky 24 Jun '18

24 Jun '18

Hi, Using the shading function in a metapost image the whole page is filled in instead of the figure that defines it. Minimal example as from the metafun manual 8.3.3 (http://www.pragma-ade.nl/general/manuals/metafun-p.pdf) \starttext \startMPcode fill fullsquare xyscaled (1cm,1cm) withshademethod "linear" withshadevector (1,0) withshadecolors (darkred,darkgreen) ; \stopMPcode \stoptext ConTeXt ver: 2018.06.23 12:12 MKIV beta fmt: 2018.6.23 int: english/english luatex version 1.09 with functionality level 6823, MetaPost 2.00 With this, I get a full A4 page with the shading colors. This worked until the beta 2018-06-22 16:02 and the desired output is shown when using live.contextgarden.net. Thanks, Adam

2 1

setmemstream to use pdfe.new instead of epdf.openMemStream
by Adam Reviczky 24 Jun '18

24 Jun '18

Hi, I am using the "figures.setmemstream" for inline images and it is broken now with the latest luatex on the changes from epdf.openMemStream to pdfe.new. Although it does say "very experimental and likely to change", but can we update the call from epdf.openMemStream? Minimal example: \starttext \startluacode figures.setmemstream("inline",mime.unb64("iVBORw0KGgoAAAANSUhEUgAAAAEAAAABAQMAAAAl21bKAAAAA1BMVEUAAACnej3aAAAAAXRSTlMAQObYZgAAAApJREFUCNdjYAAAAAIAAeIhvDMAAAAASUVORK5CYII=")) context.externalfigure({"memstream:///inline"}) \stopluacode \stoptext or as in grph-mem.lua: -- \startluacode -- figures.setmemstream("whatever",io.loaddata("t:/sources/cow.pdf")) -- \stopluacode -- -- \externalfigure[memstream:///t:/sources/cow.pdf] -- \externalfigure[memstream:///whatever] The error message is: /usr/share/texmf/tex/context/base/mkiv/grph-mem.lua:32: attempt to index global 'epdf' (a nil value) stack traceback: /usr/share/texmf/tex/context/base/mkiv/grph-mem.lua:32: in function 'setmemstream' [ctxlua]:2: in main chunk Which points to the line of "local memstream, identifier = epdf.openMemStream(stream,#stream,name)" LuaTeX commit 6822 change was "epdf.new (aka memstreams) (HH)" ConTeXt ver: 2018.06.23 12:12 MKIV beta fmt: 2018.6.23 int: english/english luatex version 1.09 with functionality level 6823, Thanks, Adam

2 1

MetaPost shading broken with latest beta
by Akira Kakuto 24 Jun '18

24 Jun '18

> With this, I get a full A4 page with the shading colors. > This worked until the beta 2018-06-22 16:02 and the desired output is > shown when using live.contextgarden.net. Even in the previous mtx-context | current version: 2018.06.22 15:55 I get a full A4 page with the shading colors if I use Luatex 1.09.0 Development id: 6823 The desired output is obtained if I use Luatex 1.08.0 Development id: 6731 So I think the latest experimental binary is problematic in this example. Best, Akira

1 0

beta
by Akira Kakuto 23 Jun '18

23 Jun '18

> On Linux armhf i get with the same context and luatex: > ... 1.09.0 is varying. Please see Development id by luatex --credits Best, Akira

2 1