August 2016 - ntg-context - NTG Mailing Lists

Nicer than 'context("\\\\")'?
by Procházka Lukáš Ing. 08 Aug '16

08 Aug '16

Hello, is there an alternative code instead of 'context("\\\\")'? See the code: ---- \starttext %\startsetups[headertext] % \startframed[width=fit,align=flushleft] % Bla\\ % Uhh % \stopframed %\stopsetups \startluacode context.startsetups{"headertext"} context.startframed{frame = "off", align = "flushright", width = "fit", } context("AB") context("\\\\") -- Not very nice here context("CD") context(true) -- Trial 1 but doesn't give the same as "\\\\" context("EF") context.crlf() -- Trial 2 but doesn't give the same as "\\\\" context("GH") context.stopframed() context.stopsetups() \stopluacode \setupheadertexts[][\directsetup{headertext}] Foo \stoptext ---- Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS:nrpt3sn Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 (+420 720 951 172) Fax: +420 244 461 038

3 2

How to reset a new processor ?
by Fabrice Couvreur 08 Aug '16

08 Aug '16

Hi, I use a counter for each "Exercises" section of each chapter (Wolfgang thank you !). How to reset the counter to 1 for each section ? thank you, Fabrice \defineprocessor[ACPROCESSOR][command=\EXFRAME] \defineconversionset[ACCONVERSION][][ACPROCESSOR->n]

2 4

Header background off with \page?
by Procházka Lukáš Ing. 08 Aug '16

08 Aug '16

Hello, the following code: ---- \setupheadertexts[Le][Ri] \setupbackgrounds[header][text][bottomframe=on] \starttext \startTEXpage \externalfigure[dummy] \stopTEXpage \page[yes,header,footer,odd] % Empty page to come here Blabla \stoptext ---- should generate an empty page. The \page[yes,header,footer,odd] suppress header and footer, which is good, and inserts one page; the problem is that header and footer background is kept and still appears. Is it a "wanted" feature? My guess is that when one uses "\page[...,header,footer...]" than suppressing header/footer background is intended, too. If the background is not suppressed automatically with "header,footer", would it be possible to implement something like "\page[...,background,...] which would suppress header and footer background (or suppress their backgrounds automatically with \page[...header...footer...])? Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS:nrpt3sn Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 (+420 720 951 172) Fax: +420 244 461 038

1 0

Error in loading font Samim
by Mohammad Hossein Bateni 07 Aug '16

07 Aug '16

Hello, I believe this worked fine in June's beta but now gives an error. \starttext \definedfont[Samim] سلام \stoptext I got the font originally from here <https://github.com/rastikerdar/samim-font/releases/download/v0.11.0/samim-f…>, but then removed the MATH table because it was causing an error at the time to get the attached version. Now the above code gives the following error: ...ntext/tex/texmf-context/tex/context/base/mkiv/l-lpeg.lua:290: bad argument #2 to '__div' (invalid replacement value) stack traceback: [C]: in function '__div' ...ntext/tex/texmf-context/tex/context/base/mkiv/l-lpeg.lua:290: in function 'splitter' ...ext/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:159: in function 'addfeature' ...ext/tex/texmf-context/tex/context/base/mkiv/font-otc.lua:730: in function 'enhancer' ...ext/tex/texmf-context/tex/context/base/mkiv/font-con.lua:1269: in function 'enhance' ...ext/tex/texmf-context/tex/context/base/mkiv/font-con.lua:1291: in function 'apply' ...ext/tex/texmf-context/tex/context/base/mkiv/font-otl.lua:246: in function 'load' ...ext/tex/texmf-context/tex/context/base/mkiv/font-otl.lua:538: in function 'otftotfm' ...ext/tex/texmf-context/tex/context/base/mkiv/font-otl.lua:566: in function <...ext/tex/texmf-context/tex/context/base/mkiv/font-otl.lua:565> (...tail calls...) ...ext/tex/texmf-context/tex/context/base/mkiv/font-def.lua:304: in function 'loadfont' ...ext/tex/texmf-context/tex/context/base/mkiv/font-ctx.lua:492: in function 'loadfont' ...ext/tex/texmf-context/tex/context/base/mkiv/font-def.lua:418: in function 'read' ...ext/tex/texmf-context/tex/context/base/mkiv/font-ctx.lua:1172: in function <...ext/tex/texmf-context/tex/context/base/mkiv/font-ctx.lua:1059> Could you advise me on how to get over this issue? As far as I know, the font lacks Latin characters and is restricted to the Arabic/Farsi characters. In a more complicated example, I used dejavusans as fallback but the above MWE seemed fine, as far as I remember. Thanks, MHB

1 1

\pdfactualtext and \char
by Henri Menke 05 Aug '16

05 Aug '16

Dear list, \pdfactualtext behaves oddly when the argument is \char. \starttext \pdfactualtext{\char`A}{B} \stoptext In the example, the actual text in the PDF is »A« even though it should be »B«. If I just use \pdfactualtext{A}{B} it works fine. Cheers, Henri

2 1

How to switch single font?
by Henri Menke 05 Aug '16

05 Aug '16

Dear list, how can I switch to another typeface for the, say, roman font only? When I use \definefontfamily to do so it switches *all* the fonts, including math, to the one loaded (example below). This leads to very undesirable effects, such as math is no longer set in italics. Cheers, Henri --- \definefontfamily[main][rm][Linux Libertine O] \setupbodyfont[main] \starttext foo $bar$ \stoptext

2 1

Question about a link in a footnote to cite
by Ursula Hermann 05 Aug '16

05 Aug '16

Hello list! I would like to know: If I have this in a footnote \footnote\cite Truman, Harry: Inaugural Address. 1949. Letzter Zugriff: 10.07.2013, http:// <http://www.presidency.ucsb.edu/ws/?pid=13282> www.presidency.ucsb.edu/ws/?pid=13282. [Hervorhebung I.G.] whats the right way? \startbuffer[biblio] @url and I have an author and a year, do I have to write it here? } \stopbuffer \mainlanguage[en] \usebtxdataset[biblio.buffer] \starttext \startbodymatter \startchapter[title={Me}] That's me \footnote{\cite[url, author, year]? \stopchapter \stopbodymatter \startbackmatter \startchapter[title={Bibliography}] \placelistofpublications \stopchapter \stopbackmatter \stoptext

2 1

Question about links
by Ursula Hermann 05 Aug '16

05 Aug '16

Hello Henry and Alan and Wolfgang! If I have this example, wich works really fine , I would like to know , how the same sample works if i have a link in a footnote and want to write \cite ,with an autor and a year ? . \startbuffer[biblio] @url? , what is next to write, the autor, the year? Or only the link? } \stopbuffer \mainlanguage[en] \usebtxdataset[biblio.buffer] \starttext \startbodymatter \startchapter[title={Me}] Your attachment actively impedes the aim that brought you to it initially \footnote{\cite[url] [www.contextgarden.net]? \stopchapter \stopbodymatter \startbackmatter \startchapter[title={Bibliography}] \placelistofpublications \stopchapter \stopbackmatter \stoptext Thanks for your help. Uschi

1 0

OTF feature for a math font
by Mohammad Hossein Bateni 05 Aug '16

05 Aug '16

Dear Hans & Wolfgang, I resolved some of the minor issues. But the main question still stands. Is it possible to add an OTF feature to the math font? In the very simple case, I want to change any sequence like "1.2" to "1/2". My feature (see below) works for text fonts but not in math mode. Thanks, MHB On Tue, Aug 2, 2016 at 3:54 PM, Mohammad Hossein Bateni <bateni(a)gmail.com> wrote: > Could the problem be because math fonts use mode=base instead of > mode=node? Or is it because in math fonts, the digits and/or full-stop > have different codes? > —MHB > > On Mon, Aug 1, 2016 at 9:46 AM, Mohammad Hossein Bateni <bateni(a)gmail.com> > wrote: > >> Dear list, >> >> I want to add a customized font feature to the math font, to >> automatically change the decimal point (unicode 0x2E) to the Arabic/Farsi >> version (unicode 0x66B). This will go well with the mapping from Latin >> digits to Farsi digits (done in a sample with mathdigits fallback). >> >> For instance, I want to code in $123.45$ and get a result like ۱۲۳٫۴۵. >> However, I do not want to simply map 0x2E to 0x66B, because then "full >> stop" outside a number will also change. In particular, I'd like to have >> the mapping only when full-stop is preceded and succeeded by a digit. This >> will, among other things, leave the end-of-equation periods unchanged. >> >> Here is how I tried to achieve it. >> >> >> \startluacode >> digits = { 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39 } >> -- 0x66B instead of 0x2F gives an error! >> replacements = { [0x002E] = { 0x2F } } >> fonts.handlers.otf.addfeature { >> name = "mpf", >> type = "chainsubstitution", >> lookups = { { >> type = "multiple", >> data = replacements, >> } }, >> data = { >> rules = { >> { >> current = { { 0x002E } }, >> after = { digits }, >> before = { digits }, >> lookups = { 1 }, >> } >> } >> } >> } >> \stopluacode >> >> \definefontfeature[mathperiod][mpf=yes] >> >> \resetfontfallback [mathdigits] >> %\definefontfallback[mathdigits][dejavusansmono][ >> digitsextendedarabicindic][check=yes,force=yes,offset=digitsnormal] >> >> \definefontsynonym [MathRoman][name:modern][ >> features={math\mathsizesuffix,mathperiod},goodies=lm-math, >> fallbacks=mathdigits] >> >> \starttext >> $123.45.$ >> >> 123.45. >> >> \addff{mathperiod} >> 123.45. >> \stoptext >> >

1 0

\typescriptthree within the optional argument of \definefontsynonym
by Mohammad Hossein Bateni 04 Aug '16

04 Aug '16

Hello Hans, Suppose you have a typescript as follows. \starttypescript [first] [MyFont] [GoodieOne,GoodieTwo] \definefontsynonym [Serif] [\typescripttwo] [goodies=\typescriptthree] \stoptypescript Using macros \typescriptX (for X=one, two, and three) works in the first and second arguments in \definefontsynonym but not in the optional argument. This seems to be because the optional argument is not expanded. Is this a bug or a feature? What I want to do was have a set of "fixes" (correcting kern issues, etc.) for a collection of fonts. I can either put these in separate goodie files or feature sets (the latter being what I was trying but not in the sample above), and write generic typescripts that would load any of the fonts with its associated fixes. While I can use sans/serif/mono in the first argument, and name of the font in the second argument (to be mapped appropriately using \typescriptprefix to nmemonic name and real font name), the third (optional) argument of \definefontsynonym does not expand immediately, hence I'll end up with "undefined" \typescriptthree when it will be used. Best, Hossein

2 2