- ntg-context - NTG Mailing Lists

Re: [NTG-context] Using lua to define a macro with one optional parameter in brackets
by Jaroslav Hajtmar 13 Jul '15

13 Jul '15

Thanks Hans. At this moment, it works fine. For me it is quite essential novelty and it is very much handy for me. It seems that works only in the standalone version because version in TeXlive 2014 version it tells an error message (but does not matter on it). I want to even ask how you can write a macro with one or more parameters? Now the parameter in square brackets displayed together with the contents of the macro. You can do this at all? It would get any minimal example? Thanks again for your support. Jaroslav Hajtmar Dne 9. 7. 2015 v 17:24 Hans Hagen napsal(a): > On 7/9/2015 5:05 PM, Jaroslav Hajtmar wrote: >> Thanx to Hans and Taco too, >> >> ad Taco) ala Perhaps interfaces.definecommand could be extended with a >> way to do global definitions? >> Indeed it seems to me. Changes in lua code does not affect the results >> in ConTeXt. >> >> ad Hans) interfaces.setmacro("name","value") >> >> Thanx, II tried to use it, but somehow I can not realize what I wanted. >> Not available somewhere a minimal example? I tried to scan codes in the >> folder with the installation of ConTeXt, but I never encountered a >> working example of where you could bounce. >> Thanks Jaroslav Hajtmar > > \starttext > > \startluacode > interfaces.setmacro("foo","bar") > \stopluacode > > \foo > > \start > \startluacode > interfaces.setmacro("foo","foo","global") > \stopluacode > \stop > > \foo > > \stoptext > > ----------------------------------------------------------------- > 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 > ----------------------------------------------------------------- > ___________________________________________________________________________________ > > If your question is of interest to others as well, please add an entry > to the Wiki! > > maillist : ntg-context(a)ntg.nl / > http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ___________________________________________________________________________________ > ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

2 1

Aligned equations break grid
by Sebastian Ørsted 13 Jul '15

13 Jul '15

Hi, I'm new on this mailing list. I subscribed in order to report the following, which I think is a bug in ConTeXt: An aligned set of equations does not respect the grid and puts the rest of the page out of alignment with the grid. It is most easily seen on this post on TeX.SE <http://tex.stackexchange.com/questions/254815/grid-on-aligned-equations-in-…> . Best regards, The TeX.SE user Gaussler

1 0

newotf definefontfeatures problem with script=hebr
by Rik Kabel 12 Jul '15

12 Jul '15

The following code fails; however, it succeeds without newotf, and it succeeds with newotf if the defined font feature (*hebrew) is removed from the \definefont command. The characters that demonstrate the problem are HEBREW LETTER LAMED combined with HEBREW POINT HOLAM, followed by HEBREW LETTER ALEF (U05DC with combining U05B9 followed by U05D0). I have not come across other combinations that cause the problem, but I have not done an exhaustive search. \usemodule [newotf] \setupdirections [bidi=global] \definefontfeature [hebrew] [default] [lang=heb,ccmp=yes,script=hebr] \definefont [Hebrew] [sileot*hebrew] \starttext \startTEXpage This is okay:{\hfill\Hebrew לא} This is okay:{\hfill{\Hebrew לֹ}} This fails:{\hfill{\Hebrew לֹא}} \stopTEXpage \stoptext It reports: error: C:/ConTeXt/tex/texmf-context/tex/context/base/font-ots.lua:1586: attempt to index a number value tex error > tex error on line 13 in file C://Users/rik/Desktop/newotf-features.tex: ? <inserted text> \par <to be read again> \vss \pack_framed_do_bottom ...amedparameter \c!bottom \raggedbottomcommand <to be read again> \localendstrut \pack_framed_do_bottom \egroup \stopfittingpage ->\removeunwantedspaces \egroup \egroup \doif {\fittingpage... l.13 \stopTEXpage The same problem occurs in the same way with the following fonts, most of which are shipped with Windows: Arial Regular Arial Bold Arial Narrow David Regular David Bold Ezra SIL Regular Ezra SIL SR Regular Keter YG Medium Levenim MT Regular Levenim MT Bold Taamey David CLM Tahoma Regular Tahoma Bold Times New Roman Regular Times New Roman Bold

2 1

Bibliography
by Procházka Lukáš Ing. - Pontex s. r. o. 12 Jul '15

12 Jul '15

Hello, I have a bibliography database in Lua. I suppose to use this DB to create a list of publications with Lua and \startpublication ... \stoppublication. So I will get something like: ---- % Will be generated by Lua, but for now >> \startpublication [k=me, t=article, a=LPr, y=2000, s=Shr, n=1, ] \city{Prg} \stoppublication % Will be generated by Lua, but for now << \setuppublications[alternative=apa] \starttext Hello \cite[me] -- \cite[Shr] -- \cite[1]. \placepublications[criterium=all] \stoptext ---- The problem is that \cite produces "(Xxxxxxxxxx, 0000)" and no list of publications is generated. What am I doing wrong? NB: I learned from http://wiki.contextgarden.net/Bibliography_mkiv and http://www.let.rug.nl/alfa/texmf/tetex30/context/bib/bibmod-doc.pdf My one-off is that I have not a .bib file and I would like to avoid .bib generation and use of BibTeX if possible. I guess that having a biblio DB in Lua is handy enough as Lua can convert the DB in whatever format - eg. via context.startpublication(...) ... context.stoppublication() So, how to "handle" the bibliography in a best manner? Than you in advance, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038

4 10

[Tools] ConTeXt Language Module for BBEdit, v1.0
by Paul Mazaitis 12 Jul '15

12 Jul '15

Hello list! I am pleased to announce v1.0 of ConTeXtBBLM, a BBEdit Language Module to support ConTeXt. This language module is built for BBEdit v11, and supports MkIV-style sectioning for navigation. A brief list of features: * Navigation by heading titles (including titles from user-defined heads). * Navigation by callouts (TODO:, FIXME:, etc.) in comments. * Navigation to files referenced by the \environment command. * Folding text within balanced \start and \stop commands. * Syntax coloring of text, comments, commands, command parameters, and command options. * Keyword support. * Command completion. More information and sources can be found at: https://github.com/pmazaitis/ConTeXtBBLM. ...and the release is available here: https://github.com/pmazaitis/ConTeXtBBLM/releases/tag/v1.0 ...or here: http://paul.mazaitis.org/assets/ConTeXt-bblm-v1.0.zip Some notes: This language module could (always!) use more testing. Bug reports cheerfully welcome! The language module tries to be clever about recovering from mis-matched /startcommand and /stopcommand pairs when generating folds. This will likely cause surprising behavior if the offending mis-match involves a user-defined head command. For keyword support, the module loads the keyword set from the file "context-keywords.txt" in the Resources directory of the language module plugin. At the moment, this file is empty, and can be customized as needed (plain text, one keyword per line). For command completion, the language module loads a command set from the text file "context-commands-en.txt" in the Resources directory of the language module plugin. I'd like to use the output of: mtxrun -script interface --text ...as a drop-in for this text file, but it appears the command list this script generates is incomplete. Hans or Taco (or anyone?): are there plans to update mtxrun to generate the current complete interface when using this script? Thanks! -Paul

2 1

beta/7.7.2015: error with \in
by Procházka Lukáš Ing. - Pontex s. r. o. 12 Jul '15

12 Jul '15

Hello, I'm getting the following error: " mtx-context | run 1: luatex --fmt="c:/Ctx-Beta/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde... iv" --c:kindofrun=1 --c:maxnofruns=9 --c:nonstopmode --c:path="C:\\Lukas\\ConTeXt\\Styles" "cont-yes.mkiv" This is LuaTeX, Version beta-0.80.1 (TeX Live 2015/W32TeX) (rev 5274) \write18 enabled. system > callbacks > not registering frozen 'find_format_file' open source > 1 > 1 > c:/Ctx-Beta/tex/texmf-context/tex/context/base/cont-yes.mkiv ConTeXt ver: 2015.07.07 21:43 MKIV beta fmt: 2015.7.9 int: english/english ... c:/Ctx-Beta/tex/texmf-context/tex/context/base/strc-ref.lua:1610: attempt to index field 'structure' (a nil value) stack traceback: c:/Ctx-Beta/tex/texmf-context/tex/context/base/strc-ref.lua:1610: in function 'identify_inner_or_outer' c:/Ctx-Beta/tex/texmf-context/tex/context/base/strc-ref.lua:1785: in function 'identify' c:/Ctx-Beta/tex/texmf-context/tex/context/base/strc-ref.lua:1806: in function 'action1' [string "..."]:21: in function <[string "..."]:20> (...tail calls...) ... 45 >> Hello \in{kap.}[NonExisting] ... " Any quick fix? ( I'm not attaching a MNWE as the error appears in a large project so extracting a MNWE is not so easy... but is possible... not at the moment... But error message would help. ) Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038

3 2

new beta
by Hans Hagen 12 Jul '15

12 Jul '15

Hi, I uploaded a new beta. As a prelude to some updates / improvements in the font handling an experimental new otf fontloader/handler is present. This one is not used by default but will likely replace the current one (only when it has been tested enough). At that time also some other pending changes will happen (no functional differences, only improvements). There are a few advantages to the new approach: - Indentifying fonts goes a bit faster (some 20 times) but that is already in the core. - The mem footprint of initial loading a font is smaller. - Initial loading can a bit slower depending on the kind of font (no big deal as we cache files) and if really needed can be sped up a bit. - The cached instance is smaller. - Loading the cached font is faster (not that it was slow but still). - Some bits and pieces have been optimized (there is room for more but I might decide not to do that). - Extra substitution features like tlig and trep are now runtime and not cached. - Processing in node mode can be somewhat faster for complex fonts. - The generic font code will stay as it is for at least a while after the new code has become stable and the current method will stay around too. Of course there will be bugs although the test suite runs without crashing. I will use the new code on my machine but you can test it with: \usemodule[newotf] before \starttext (or in cont-loc.mkiv). 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 -----------------------------------------------------------------

6 21

newotf, problem with .ttc fonts
by Rik Kabel 11 Jul '15

11 Jul '15

It appears that the newotf mechanism does not handle .ttc fonts. The following MWE uses fonts found on Windows 8.1: \usemodule [newotf] %% the following fonts, all .ttc, fail in the same way: % C:/ConTeXt/tex/texmf-context/tex/context/base/font-oup.lua:651: bad argument #1 to '(for generator)' (table expected, got nil) %\definefont [testfont] [MSMincho sa 1] %\definefont [testfont] [MingLiU sa 1] %\definefont [testfont] [Gulim sa 1] %\definefont [testfont] [Batang sa 1] %\definefont [testfont] [msyh sa 1] % Microsoft YaHei %\definefont [testfont] [msjh sa 1] % Microsoft JhengHei %\definefont [testfont] [SimSun sa 1] %% the following, none .ttc, work: %\definefont [testfont] [arialuni sa 1] % Arial Unicode MS %\definefont [testfont] [yugothic sa 1] % Yu Gothic %\definefont [testfont] [yumin sa 1] % Yu Mincho %\definefont [testfont] [kaiu sa 1] % DFKai-SB Regular %\definefont [testfont] [simfang sa 1] % FangSong Regular %\definefont [testfont] [simhei sa 1] % SimHei Regular \definefont [testfont] [simkai sa 1] % KaTi Regular \starttext Confucius’ {\em Analects} ({\testfont 論語} {\em LunYu}). \stoptext Without the new module, this works with all of the test fonts. -- Rik

2 1

OT features and newotf
by Pablo Rodriguez 11 Jul '15

11 Jul '15

Dear list, I’m afraid that features don’t work with newotf: \usemodule[newotf] \definefontfeature[noliga][liga=no] \starttext \startTEXpage[offset=1em] fiflff \addfeature[noliga]fiflff \stopTEXpage \stoptext Is this a bug or am I missing something? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

Tabulate: lines bellow header
by Procházka Lukáš Ing. - Pontex s. r. o. 11 Jul '15

11 Jul '15

Hello, Let's have the following code: ---- \starttext \setuptabulate[header=repeat,split=yes] \starttabulatehead \HL \NC H \NC H \NC\NR \LL % \LL[8] causes error \stoptabulatehead \starttabulate[|l|l|] \dorecurse{50}{ \NC A \NC A \NC\NR \HL[8] } \stoptabulate \stoptext ---- It produces: 1) horizontal line bellow header, which is somewhat shifted down, closer to the first body row, but only on the 1st page; 2) horizontal line bellow header on page look differently from that on page 1 - its thickness if about a half of that between body rows, - and also its position is different from that on page 1. 3) Is there a way to affect thickness of the rule bellow header? \LL[8] causes error. I guess this is quite normal - to have a table header separated by a thicker rule, to have: ------------ table header ============ body row 1 ------------ body row 2 ------------ So: Ad 1: Is it possible to place the rule bellow the header to a "better" position? E.g. using a "more proper" command than \LL? Ad 2: Is it a Ctx feature or -- ? Ad 3: Any idea how to achieve this? Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038

1 0