February 2019 - ntg-context - NTG Mailing Lists

Re: [NTG-context] \index[infinity]{$+\infty$} gives an error
by Wolfgang Schuster 05 Feb '19

05 Feb '19

Mikael P. Sundqvist schrieb am 05.02.19 um 20:17: > On Tue, Feb 5, 2019 at 5:11 PM Wolfgang Schuster > <wolfgang.schuster.lists(a)gmail.com> wrote: >> Mikael P. Sundqvist schrieb am 05.02.19 um 15:37: >>> Hi, >>> >>> With latest beta, the file below throws me the error given below the >>> example file. I thought this was possible (see >>> http://www.pragma-ade.com/general/manuals/cont-enp.pdf, (pdf)page >>> 202). The error is not present if I remove the third problematic index >>> entry. >>> >>> /Mikael >>> >>> % Example file >>> >>> \starttext >>> This does not look right: >>> \index{entry} >>> \index[key]{entry} >>> \index[infinifty]{$+\infty$} >> \index[infinifty]{$\mathplus\infty$} >> >> ConTeXt uses + as separator in index entries. >> >> In you example the argument is split into the two parts “$” and >> “\infty$” which creates two incomplete formulas. >> >> Wolfgang > Many thanks, works like charm for +\infty. For -\infty, it seems that > an endash(?) is picked up instead. I notice the following definitions > in math-ini.mkiv > > \unexpanded\def\mathplus {+} > \unexpanded\def\mathminus{\ifmmode –\else\iffontchar\font`−−\else –\fi\fi} Seems wrong to me because math mode should use the normal hyphen. > So, a follow-up question: Should I use something else than > \index[minusinfty]{$\mathminus\infty$} if I want -\infty in the index? Only + is a special character in the index entry but - can be used without problems and you don’t have to use \mathminus. Wolfgang

1 0

\index[infinity]{$+\infty$} gives an error
by Mikael P. Sundqvist 05 Feb '19

05 Feb '19

Hi, With latest beta, the file below throws me the error given below the example file. I thought this was possible (see http://www.pragma-ade.com/general/manuals/cont-enp.pdf, (pdf)page 202). The error is not present if I remove the third problematic index entry. /Mikael % Example file \starttext This does not look right: \index{entry} \index[key]{entry} \index[infinifty]{$+\infty$} \placeindex \stoptext % Error message tex error > tex error on line 68 in file /home/mps/tmp/indexproblem.tex: ! Extra }, or forgotten $ <recently read> } <argument> ...mand {[internal expandable lua function call]}} } \firstofoneargument #1->#1 \doapplyregisterentrycommand ...extcommand {#2}}}} \dostoptagged \registerentry ...plyregisterentrycommand {#2}{#5} \fi \popcurrentregister l.68 }

2 1

setupdirections RTL bug
by Mohammad Hossein Bateni 05 Feb '19

05 Feb '19

Hello, This is perhaps *related* to what Alan Bowen reported. Not the same, since I don't get compilation errors. Here's a MWE. See explanation of bad behavior below. \setupdirections[bidi=global,method=one] \definefont[Ar][dejavusans*arabic] \setupfootertexts[\setups{L}][\setups{R}] \startsetups L %\setupdirections[bidi=on,method=one] %\setupdirections[bidi=local,method=one] \Ar%left چپ \stopsetups \startsetups R %\setupdirections[bidi=on,method=one] \Ar%right راست \stopsetups \starttext Test \stoptext 1. The right footer is placed over the left footer. 2. There's no problem if I replace the RTL text of right footer with an LTR text. 3. Left footer's text does not get proper RTL treatment. Perhaps *this* is the change of behavior introduced in the past year. My guess is that RTLed footers are moved to the other side. 4. If I use bidi=local or bidi=on in the preamble, RTL treatment is applied to neither footer. I can't seem to turn on RTL via setupdirections inside the (left) footer. How does one do that? Thanks, MHB

2 2

inner option for \showgrid
by Marcus Vinicius Mesquita 05 Feb '19

05 Feb '19

Dear list, In the i-context.pdf file, among the \showgrid[…,…] options there are: right, left, and outer. Is it possible to add another option: inner? TIA Marcus Vinicius

2 2

Best strategy for ConTeXt to ePub update
by Martin Bruchanov 05 Feb '19

05 Feb '19

Hi all, While ago I wrote a book (http://sstv-handbook.com/) in ConTeXt and I have started to thinking about possibility to export also ePub and xHTML besides the PDF version. Few questions: 1. What is current support of ePub, will it export pictures automatically? 2. Do I need to rewrite source code to use those verbose \startsXXX of every element (paragraph, item,...) or is there any simplier way how to handle sources as they are now? Regards, BruXy

2 1

\setupdirections, methods one, two, and three
by Alan Bowen 04 Feb '19

04 Feb '19

The latest beta complains and stops when I try to process a book that has \setupdirections[bidi=global, method=one] for several, scattered phrases in Arabic and Hebrew (which I do not read). It works, however, when I set method=two or method=three. What is the difference between these methods and, am I right that the output will be the same if I switch to method two or three? Alan

1 0

Re: [NTG-context] problem with \sym?
by Wolfgang Schuster 04 Feb '19

04 Feb '19

Alan Bowen schrieb am 04.02.19 um 18:50: > Here is a mwe that gives the same error as the original: > > luatex warning > hpack filter: error: > ...eXt/tex/texmf-context/tex/context/base/mkiv/typo-dua.lua:422: attempt > to compare number with nil > > tex error > tex error on line 22 in file > /Users/bowen1/Desktop/TestTeX/test-02.tex: ? > > > \setupdirections[bidi=global, method=one]%<—— > > \defineitemgroup[CList][levels=2] > \setupCList[1][n, broad, packed, autointro, repeat, continue] > [itemalign=flushright, > left={},right={},stopper={.}, > margin=0pc, > before={\setupinterlinespace[off] > \setuplines[before={}, after={}] > \startlines}, > after={\stoplines}] > > \setupCList[2][n, broad, packed, joinedup, autointro] > [itemalign=flushright, > left={}, right={}, stopper={}, > margin=0pc, > ] > > \startcomponent[*] > \startCList > \sym{} Preface > \sym{0.} Prolegomena %<——line 22 > \stopCList > \stopcomponent > > The example processes as it should when the first line is commented out. It works with method two or three for \setupdirections. Below is a shorter minimal example. \setupdirections[bidi=global,method=one] \starttext \setbox\scratchbox\autodirhbox{xyz} \stoptext Wolfgang

1 0

Re: [NTG-context] problem with \sym?
by Wolfgang Schuster 04 Feb '19

04 Feb '19

Alan Bowen schrieb am 04.02.19 um 16:37: > I should have done this originally. Sorry for that. > > My table of contents is component of a book-project; it is essentially > a custom itemization. > > The following: > > \defineitemgroup[CList][levels=2] > \setupCList[1][n, broad, packed, autointro, repeat, continue] > [itemalign=flushright, > left={},right={},stopper={.}, > margin=0pc, > before={\setupinterlinespace[off] > \setuplines[before={}, after={}] > \startlines}, > after={\stoplines}] > > \setupCList[2][n, broad, packed, joinedup, autointro] > [itemalign=flushright, > left={}, right={}, stopper={}, > margin=0pc, > ] > > \def\leaderfill{\leaders\hbox to 1em{\hss. \hss}\hfill} > \define[1]\pg{{\switchtobodyfont[10pt]\hfill\at[#1]\crlf}} > > \startcomponent%\starttext > \startCList > \sym{} Illustrations and Tables\pg{Illustrations} > \sym{} Preface\pg{Preface} > \sym{} Acknowledgments\pg{Acknowledgments} > \blank[big, fixed] > \sym{0.} Prolegomena to the Study of Hellenistic Astronomy > \emph{Alan C.\ Bowen and Francesca Rochberg}\pg{ACB00} > \stopCList > \stopcomponent%\stoptext > > Oddly enough, there is no problem if the code is run between > \starttext and \stoptext. > > This used to work with the previous betas. \startcomponent expects the name of the current file as argument, e.g. \startcomponent [mycomponent] or \startcomponent mycomponent You can also replace the name of the current file with a asterisk, e.g. \startcomponent [*] In your document \startcomponent takes \startCList as argument which leads to the error message. Wolfgang

1 0

test-suite wiki page
by Sanjoy Mahajan 04 Feb '19

04 Feb '19

In another thread, Hans had pointed me to the examples of blocks in the test suite. That leads to my following two questions before I revise the associated wiki page: 1. The wiki page about the test suite <https://wiki.contextgarden.net/Test_suite> contains dead links to <https://foundry.supelec.fr/projects/contexttest> for the project homepage and to <https://foundry.supelec.fr/mail/?group_id=21> for the mailing list. Are those now officially dead; or, more directly stated, would there be any objections if I clean up that wiki page to remove those dead links? 2. I did find the (a?) test suite on the PRAGMA site at <http://www.pragma-ade.nl/download-1.htm> as a 7zip file. Is that the correct location to point people to (apologies for the awful construction of that sentence)? -Sanjoy

2 2

About the macro path intersectionpoint path with Metapost
by Fabrice Couvreur 04 Feb '19

04 Feb '19

Hi, I would like to reproduce the attached figure. My problem is to create the points of intersection between the circles. It seems that my approach is not the right one. Thank you. Fabrice \starttext \startMPcode path p, q, r, b ; p:= fullcircle scaled 6cm ; q:= fullcircle scaled 4cm shifted (2.5cm,2cm) ; r:= fullcircle scaled 4cm shifted (-2.5cm,2cm); b:= fullcircle scaled 2cm shifted (0,-3cm); pair A, B ; A:= p intersectionpoint r ; B:= p intersectionpoint r ; path u ; u:= A--B--cycle ; draw p ; draw q ; draw r ; draw b ; draw u numberstriped (.25,15,5) withcolor magenta ; \stopMPcode \stoptext

2 1