- ntg-context - NTG Mailing Lists

Missing kerns with latest 22.12.2020 LMTX
by Joseph 23 Dec '20

23 Dec '20

2 1

Re: [NTG-context] Hyphenation pattern for Esperanto
by Alain Delmotte 23 Dec '20

23 Dec '20

3 3

a new book has been published, made with the help of ConTeXt
by Robert Zydenbos 23 Dec '20

23 Dec '20

Dear readers, With great joy and a sense of relief I can now announce that my latest book, _A Manual of Modern Kannada_ by Robert Zydenbos (Heidelberg / Berlin: CrossAsia E-Publishing, 2020), a teaching manual of the Kannada language (Kannada belongs to the Dravidian family of languages, mainly spoken in southern India; also in the city of Bangalore, the 'Silicon Valley of India') has been published. It is an Open Access publication, which means it is available as a gratis download in PDF format from https://crossasia-books.ub.uni-heidelberg.de/xasia/catalog/book/736 (the clickable button “Buch herunterladen” means “Download book”; “Buch kaufen” means “Buy book”, for those who want a real book on paper). I was working on this book for the past few years and decided that the only affordably sensible way to achieve presentable results would be to use TeX, but plain TeX was too cumbersome, and in LaTeX the tables were difficult (and the book has many, many tables in various shapes and sizes). ConTeXt was The Solution (and has been duly mentioned in the technical note at the end of the book, with special thanks to Hans, Wolfgang and Pablo for valuable suggestions). For those who are curious how I used ConTeXt MkII with the XeTeX backend, a sample chapter is available at http://e.pc.cd/XlhotalK (and then click on "Direkt herunterladen"). Robert Zydenbos

2 2

new font trickery
by Hans Hagen 23 Dec '20

23 Dec '20

Hi, I finally decided to start an experiment that I had on my todo list for a while: dynamically scaling fonts. Below is an example of usage (plus some comment). In that example some 2*200 different font sizes are used which in mkiv demands 400 font definitions. This costs time and memory. The example below runs (on my old laptop) in less than 2 seconds and only uses two instances. I bet that our CJK users will love it. I post it because: (1) I need to discuss the impact with Wolfgang ... how do we integrate this. We can for instance define some sizes (\tfa \tfb ...) differently. (2) I want to see if average performance improves on huge documents with many fonts / sizes (that is for Massimiliano to test). (3) Are there side effects? It does work for math (rather neat trickery) but maybe we need an additional configration for that. (4) I considered several variants but for now use a low level \glyphscale command that takes a number (in goodl old tex tradition a scale of 1.0 is entered as 1000). (5) The implementation can be improved a bit (performance wise). There is a bit more overhead involved but usually I can compensate that. (6) It will not be backported to MKIV so one can only test in LMTX. it's a bit of a mix between engine and context features. (7) There can be bugs (unforseen side effects, or typos in the somewhat quick patches in the source). Consider it an experiment, but so far I'm rather satisfied, Hans %%%% EXAMPLE %%%% \setuplayout[middle] \setupbodyfont[pagella,10pt] \setupalign[verytolerant,stretch] \setupwhitespace[big] \starttext \startbuffer \definescaledfont[bfe][scale=2000,style=bf] \setuphead[chapter][style=\bfe] \dostepwiserecurse {10} {2020} {10} { \title{Here we go #1!} \start \glyphscale#1\relax \setupinterlinespace \samplefile{ward}% \bf \samplefile{ward} \par \stop \page } \stopbuffer \getbuffer \title{Scaled fonts} Although \CONTEXT\ is quite efficient with fonts there is always room for improvement. However, after years of finetuning the font mechanisms there was not that much room left. This made me think of a different approach to scaling. Nowadays fonts seldom come in design sizes. Also, in \CONTEXT\ \MKIV\ and therefore \LMTX\ we always had so called dynamic features: apply additional features locally, although that comes with a small penalty in performance, it saves additional font instances. It is a good approach for the occasional small stretch of glyphs, like small capped logos and such. We now can also do dynamic font scaling, which means that we don't need to define a new font instance when the same feature set is used. Or course in addition to this features one can still use the dynamic features. This means that for instance chapter titling can use the bodyfont instance and just apply additional scaling. Although for a normal run the number of loaded fonts is normally small, and the number of instances also isn't that impressive it can happen in a large document that you end up with a few dozen. That number can now be reduced to half a dozen. Of course there can be side effects, whcich is why it's currently tagged as experimental. There is also a small performance hit because we now need to track it but that is gained back because we load less fonts and have less glyph runs. It even works in math, although there some different trickery is needed. \typebuffer \stoptext ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

2 2

cow-font
by Peter Münster 23 Dec '20

23 Dec '20

Hi, How could I make use of the cow-font please? I've tried this test-file: --8<---------------cut here---------------start------------->8--- \setupbodyfont[cow] \starttext test \stoptext --8<---------------cut here---------------end--------------->8--- But the page is empty. With version 2017.08.29 it worked well... TIA for any help, -- Peter

3 3

issue with \cite in ConTeXt ver: 2020.12.22 22:14 LMTX fmt: 2020.12.22
by Alan Bowen 22 Dec '20

22 Dec '20

\cite no longer works as expected MWE: \startsetups[tightspace] \spaceskip 0.5\interwordspace plus.5\interwordstretch minus \interwordshrink \stopsetups \def\dostartbibitem[#1][#2]% {\doifsomethingelse{#2}% {\startBibItem[reference={#1},title={#2}]}% {\startBibItem[reference={#1},title={#1}]}% } \def\startbibitem{\dodoubleempty\dostartbibitem} \def\stopbibitem{\stopBibItem} \definedescription[BibItem][ width=broad, margin=1.5pc, indenting={no}, indentnext=no, alternative=hanging, hang=1, headcommand=\gobbleoneargument, align=right, before={\directsetup{tightspace}\bgroup\language[packed]}, after={\egroup}, ] \definereferenceformat [cite] [type=title,left={},right={}] \definereferenceformat [bibpage] [type=page] starttext Now \cite[test 2020] on page \page \startbibitem[test 2020] \input ward \stopbibitem \stoptext Instead of “Now test 2020 on page”, I get “Now 248>BibItem:referencetext on page” and no sign of an internal link. Alan

1 0

Snooping around in LMTX: Questions about Lua global variables
by Neven Sajko 22 Dec '20

22 Dec '20

Hello again, While learning about how to drive TeX through Lua, I decided to recursively list all Lua global variables (actually this is traversing the _G table) in the LMTX environment, half to learn more Lua, half for getting to know ConTeXt better. I was quite surprised by the huge size of the environment, a file that contains the listing of all the globals is 42 MB long! I wonder if it would be possible to reduce the exposed globals by replacing some of them by getter and setter-like functions? That seems like it would be much nicer and less error prone - because Lua is so dynamic, polluting the global namespace seems even more dangerous than in C-like languages. I guess it could also be more performant, because Lua would conceivably spend less time managing huge tables. There were also some global variables with suspicious random variation in values between runs of ConTeXt: I ran my Lua script like so multiple times (attached, in case someone is interested in it): context s.lua rm s.tuc s.pdf s.log And I found that the values of some variables unpredictably and randomly vary: The variable resolvers.suffixmap.lua sometimes has the value "scripts", and sometimes "lua". I think this means that files with the file name suffix ".lua" are sometimes classified as general scripts and sometimes as Lua scripts. This seems like it could even be a bug? The variables storage.tofmodules and storage.toftables are also interesting: they vary from run to run like this: tofmodules: 0.175483 0.149536 0.150493 0.150005 toftables: 0.008407 0.008118 0.008395 0.008116 I'd like to know what is their purpose, if it's not to involved to explain? Thanks, Neven

2 7

LMTX, PGF/TikZ absolute positioning
by Jean-Philippe Rey 22 Dec '20

22 Dec '20

Dear list, I have a problem with LMTX when I try to place a tikz drawing at an absolute location on the page. Here is a minimal failing example. ======================= \usemodule[tikz] \starttext \starttikzpicture[remember picture, overlay] \draw (current page.center) circle [radius=20mm]; \stoptikzpicture \stoptext ======================= The error is about \hoffset being undefined (see attached log file). Everything works fine with MkIV. Thank you for any help. -- Jean-Philippe Rey jean-philippe.rey(a)centralesupelec.fr 91192 Gif-sur-Yvette Cedex - France Empreinte PGP : 807A 5B2C 69E4 D4B5 783A 428A 1B5E E83E 261B BF51

1 0

Regarding XML export and EPUB
by Andres Conrado Montoya 22 Dec '20

22 Dec '20

Hello, list. I've been experimenting with the export scripts and the instructions and manuals you can find in: https://wiki.contextgarden.net/XML https://wiki.contextgarden.net/Export https://wiki.contextgarden.net/Epub https://wiki.contextgarden.net/ePub This with the expectation of being able to make an epub file form a context document that epubcheck can accept. I see there is an experimental support for epub, and I have played around with the export options a bit. However, what I would really want to know is. It's possible and if so, how can you map context's elements so they can get translated to specific html tags? I mean, the current export output uses divs with custom attributes and classes, or custom tags; but I would like to map lists to ul, list-items to li, headings to h1, h2, h3, paragraphs to <p> etc. In the manuals I see that you can do the opposite: map xml/html tags to context's elements; I wonder if you can go the other way around, and a good place to start reading about it. Apologies if I missed something obvious. Thank you. -- Andrés Conrado Montoya Andi Kú andresconrado(a)gmail.com http://sesentaycuatro.com http://messier87.com http://chiquitico.org ---------------------------------------- Los fines no justifican los medios, porque la medida verdadera de nuestro carácter está dada por los medios que estamos dispuestos a utilizar, no por los fines que proclamamos. ---------------------------------------- “You develop an instant global consciousness, a people orientation, an intense dissatisfaction with the state of the world, and a compulsion to do something about it. From out there on the moon, international politics look so petty. You want to grab a politician by the scruff of the neck and drag him a quarter of a million miles out and say, ‘Look at that, you son of a bitch.’” — Apollo 14 astronaut Edgar Mitchell

2 1

Re: [NTG-context] Polar pgfplots seems to be broken (Aditya Mahajan)
by Gavin 21 Dec '20

21 Dec '20

> Date: Mon, 21 Dec 2020 00:51:06 -0500 (EST) > From: Aditya Mahajan <adityam(a)umich.edu> > > On Sun, 20 Dec 2020, Gavin wrote: > >> Hello, >> >> I’m drawing solar system diagrams using the pgfplots module, but the polar library seem to be broken. It looks like it is calling something with a \begin{axis}... command. Here is the error message for a short document, included below. >> >>> tex error > tex error on line 18 in file /Users/Gavin/Documents/Computer/ConTeXt/Polar Plot Experiments/Untitled.tex: ! Undefined control sequence >>> >>> \pgfplots@environment@polaraxis@ [#1]->\begin >>> {axis}[#1,data cs=polar,axis type=polar] >>> l.18 \startpolaraxis[] >>> >>> 16 \startsection[title={Polar Plot}] >>> 17 \starttikzpicture % tikz code >>> 18 >> \startpolaraxis[] >>> 19 \addplot+[mark=none,domain=0:720,samples=600]{sin(4*x)}; >>> 20 \stoppolaraxis >>> 21 \stoptikzpicture >>> 22 \stopsection >>> >>> mtx-context | fatal error: return code: 256 >> >> I’d love a fix or an idea for a work around. > > This is a bug in pgfplots macro pgfplotsdefineaxistype, which uses an explicit \begin{axis} ... \end{axis} instead of the more portable \axis ... \endaxis. Attached is a quick fix, but it has been quite a while since I looked at pgfplots code, so it may be better to post a bug-report on pgfplots mailing list for a proper fix. > > Aditya > > URL: <http://mailman.ntg.nl/pipermail/ntg-context/attachments/20201221/d7278aca/a…> Aditya, Thanks for the quick fix! I will post a bug report on the pgfplots mailing list, including your helpful diagnosis of the problem. Gavin

1 0