- ntg-context - NTG Mailing Lists

registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
by Carlos 05 Apr '23

05 Apr '23

Hello list: This is under a fresh TeXLive installation. Sort as to put aside any texlive prepackaged issues. And the followign lines is the output of the error I've been having with the call of context on a recent texlive installation by both mtxrun --generate and luatools --generate right after. mtxrun --script cache --erase has also been called out to no avail registered function call [1160]: ...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied stack traceback: [C]: in upvalue 'func' ...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: in function 'lfs.dir' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:139: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:180: in function <.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:169> (...tail calls...) ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in upvalue 'walk_tree' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1190: in local 'method' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1152: in local 'traverse' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1200: in upvalue 'analyzefiles' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1286: in field 'identify' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1311: in field 'load' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1322: in field 'load' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1588: in field 'getfilename' ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:835: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:828> (...tail calls...) ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:378: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:366> (...tail calls...) ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:485: in field 'read' ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1377: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1234> (...tail calls...) 51 ;definetypeface[MyLucida][rm][serif][lucida][default][encoding=texnansi] 52 \definetypeface[MyLucida][ss][sans][lucida][default][encoding=texnansi] 53 \definetypeface[MyLucida][tt][mono][lucida][default][encoding=texnansi] 54 \stoptypescript 55 56 57 \starttext 58 59 \usetypescriptfile[type-lucida] 60 \usetypescript[Lucida][texnansi] 61 >> \setupbodyfont[MyLucida, 10pt] 62 63 \input zapf 64 65 \input tufte 66 67 68 \stoptext 69 mtx-context | fatal error: return code: 1 it doesn't matter either whatever the typescript name goes and whether is type-lucida from texnansi-lucida-map file as it has been previously advised to change the name from . makes no difference. Is LuaLaTeX behaving the same way? Answer: no. The permission denied message happened first with folders whose permeissions were not owned by the user, but the root, so I moved the files out of harm's way to another folder . Anothr folder, NOT a subfolder. Then the problem persisted to read folders and even subfolders (directories, subdirectories) with cache filenames and headers that follow So let's not get to apprehensive, It's understandable that say, not reasonable, but understandable maybe? that mtxrun or lua for that matter will stop right before. So the folders were moved right after. Gone out of the binaries. But what I can't understand is why would it try to access cache folders unrelated with anything TeX or header folders for that matter???? This is perhaps more serious than I thought at first. And Let's not blame the TeXLive pre-packaged running under Alpine Linux. To put it in laymans' terms and If anything is clear to me, is that Alpine ir not letting Lua running beserk on the system and its folders, owned by whatever/whoever else, and with pesmissions set elsewhere. It's out of the question. Or it rather be. This is all writh a fresh TeX Live Installation. I mentioned the problem that may arise by questioning the Alpine installation because there were some problems with some binaries from the prepackaged TeX Live put out by Alpine devs. But this is not prepackaged. Nope. -- "We are on the verge: Today our program proved Fermat's next-to-last theorem." -- Epigrams in Programming, ACM SIGPLAN Sept. 1982

4 23

English-Vietnamese facing pages
by jbf 03 Apr '23

03 Apr '23

Am always up for a challenge, but hope this one is not beyond my possibilities! Have a request to produce a book with English-Vietnamese facing pages. The text doesn't have to be strictly in sync, but generally so. The only ConTeXt guidelines I think I have at the moment are (1) an old module called m-streams (which I am assuming is now obsolete), and (2) an exchange of emails on this list over a decade about bilingual typesetting. It won't bother me too much if I have to tell the intending author and his editor that this might be beyond me, but before taking that stance, I have a couple of simple questions that someone might be able to respond to. And, BTW, the Vietnamese font is not the problem. Tex Gyre Pagella seems to be able to cope with that at least! Q 1: Has anybody reading this actually produced a bilingual book (it doesn't have to be en-vn) with ConTeXt? And if so would you be prepared to offer me some basic guidelines? Q 2: There is some guidance from Wolfgang on https://wiki.contextgarden.net/Columns towards the end of that page. I tried two or three pages of the first chapter of the book, placing English in outputstream[one] and the Vietnamese in outputstream[two] and kind of got a suitable result except that the last paragraph of both languages ended up BEFORE the chapter began. No idea why. The rest seemed okay. So my question is whether or not Wolfgang's sample (where he says 'a simple example but I had to write the splitter myself') would be sufficient for me to put the book together? Q 2: I suppose the third question is whether, since LMTX, there has been any further development in the 'streams' mechanism that might help me? Julian

4 6

separators between non-instantiantiated (foot)notes
by Rudd, Kevin 03 Apr '23

03 Apr '23

Is there a better (automatic, consistent) way to insert separators between non-instantiated (foot)notes (i.e., where there is at least one \note involved with an immediately preceeding/following \footnote or \note? looking at the source, the obvious hack was apparent but ... not ideal. Maybe I'm missing something obvious, but from what I see: \starttext something that works \footnote[a]{AAAA} \footnote[b]{BB} something that doesn't \footnote[c]{CCCCCC} \note[b] something else that doesn't \footnote[d]{DDDDDDDD} \unprotect\strc_notes_inject_separator\protect \note[b] but can be made to work, but does not adapt to \quotation{normal} \type{\footnote} style/format customizations \footnote[e]{E E E E}% \high{\tx{,}} \note[a] \stoptext It would be great if there were a command that treated a (some command like) \note as a \footnote-equivalent command for typesetting purposes but I'm not sure how/where the appropriate template that could produce this command might go. (And I don't know if there are? footnote-state subtleties that I'm missing that would make this kind of thing non-trivial to implement.)' Many thanks, -K Kevin W. Rudd, Ph.D. CAPT, USN (Ret) Computing Systems Researcher Computer Architecture & Computer Engineering (CACE) Advanced Computing Systems (ACS) Research Program Laboratory for Physical Sciences (LPS) kevin(a)lps.umd.edu Visiting Research Professor Electrical and Computer Engineering United States Naval Academy rudd(a)usna.edu Adjunct Faculty Secure, Trusted, and Assured Microelectronics (STAM) Center Arizona State University kevin.rudd(a)asu.edu

1 0

bold small caps
by Peter Münster 03 Apr '23

03 Apr '23

Hi, I'm quite sure, that this worked some time ago with the standard font (LM): \setff{smallcaps} Normal and \bf bold Small Caps. (See also https://wiki.contextgarden.net/Bold_small_caps) But it does not work with the latest ConTeXt version. How could I get bold small caps with the latest version please? TIA for any hints, -- Peter

3 2

Userdata environment
by Fabrice Couvreur 03 Apr '23

03 Apr '23

Hi, I have already created a thread on the subject and Wolgang, Marco and Taco have replied but the userdata environment is not yet clear to me. I would like, if possible, to write a definition, a property or a theorem on the left and illustrate it in the right margin with an example. In the code below, the second example is on the second page and not next to the second definition. Thanks. Fabrice ############################################################################ \ useMPlibrary[dum] \setuppapersize[A4] \mainlanguage [fr] \setuppagenumbering [alternative=doublesided] \setuplayout [width=12cm, rightmargin=60mm] \setupenumerations [before={\blank}, after={\blank}, alternative=serried, distance=0.5em, title=yes, titleleft=, titleright=, titlestyle=normal, headcommand=\groupedcommand{}{.}, numbercommand=\groupedcommand{}{}, titlecommand=\groupedcommand{(}{)}, width=fit] \defineenumeration [definition] [text=Définition, number=no, style=italic] \defineenumeration [exemple] [text=Exemple, number=no, style=normal] \definemargindata[marginfigure][inright] \setupmargindata [marginfigure][command=\vbox,align=middle,stack=yes] \defineuserdata [margintext] [alternative=margintext] \defineuserdataalternative [margintext] [renderingsetup=userdata:margintext] \startsetups [userdata:margintext] \margindata [inright] [ style={\switchtobodyfont[10pt]}, width=\rightmarginwidth, align={flushleft,broad} ] {\startexemple \getinlineuserdata \stopexemple} \stopsetups \showframe \starttext \startchapter[title={First Chapter},ownnumber=1] \startdefinition \input ward \stopdefinition \startuserdata [margintext] \input ward \stopuserdata \startdefinition \input ward \stopdefinition \startuserdata [margintext] \input knuth \stopuserdata \stopchapter \stoptext ############################################################################

2 1

attempt to index nil value with bidi math in hbox
by Max Chernoff 03 Apr '23

03 Apr '23

Hi Hans, This test file: \setupdirections[bidi=global,method=one] \starttext \hbox{$\varepsilon$-TeX} \stoptext gives the following error: callback error: ...ext/tex/texmf-context/tex/context/base/mkxl/typo-duc.lmt:618: attempt to index a nil value (local 'before') stack traceback: ...ext/tex/texmf-context/tex/context/base/mkxl/typo-duc.lmt:618: in upvalue 'resolve_weak' ...ext/tex/texmf-context/tex/context/base/mkxl/typo-duc.lmt:781: in upvalue 'resolve_levels' ...ext/tex/texmf-context/tex/context/base/mkxl/typo-duc.lmt:1053: in local 'handler' ...ext/tex/texmf-context/tex/context/base/mkxl/typo-dir.lmt:182: in upvalue 'typesetters_directions_handler' [string "local tonut = nodes.tonut..."]:20: in function <[string "local tonut = nodes.tonut..."]:13> (...tail calls...) Running either this: \starttext \hbox{$\varepsilon$-TeX} \stoptext or this: \setupdirections[bidi=global,method=one] \starttext \hbox{$\varepsilon$TeX} \stoptext works as expected, without any errors. Thanks, -- Max

2 1

Problems with building texlive/context from its sources
by Jakob Jakobson 03 Apr '23

03 Apr '23

Dear developers, I am/become one of the texlive mantainers on flathub a more or less recent and new approach for establishing a linux packaging format. The flatpak packages are usually build from source and so is the texlive package. You can find it under https://github.com/flathub/org.freedesktop.Sdk.Extension.texlive/tree/branc… . The file https://github.com/flathub/org.freedesktop.Sdk.Extension.texlive/blob/branc… is the build manifest which lists the files and commands/additional steps needed for the build process. The current build of texlive works well with pdflatex/lualatex/xelatex but with the context part I have some problems. Therefore, I would appreciate any help with the following questions: 1) Is context included in the texlive-20230313* tarballs or do I have to download it in an extra step? 2) If context is included in the texlive-20230313* tarballs, do I have to additionally download luametatex or is luametatex a part of context? 3) If luametatex is via context in the texlive-20230313* tarballs, how do I build it? Sorry for those (perhaps obvious) questions but I have to admit that I find the texlive building process quite confusing. Also, I could not find any installation guide that covers the scenario of building context within a texlive 2023 installation from its sources on linux. Thanks in advance and regards Jakob

1 0

Chinese labels in lang-txt.lua
by Li Yanrui (李延瑞) 02 Apr '23

02 Apr '23

Hi Hans, There are some inaccurate labels for Chinese in lang-txt.lua. Could you please apply the following patches to it? --------------------------------------------- --- lang-txt.lua 2023-04-03 11:10:00.267720005 +0800 +++ new-lang-txt.lua 2023-04-03 11:03:24.645426080 +0800 @@ -1192,7 +1192,7 @@ ["ar"]="ملحق ", ["be"]="Апендыцыт", ["ca"]="Apèndix ", - ["cn"]="附录", + ["cn"]="附录 ", ["cs"]="Příloha ", ["da"]="Bilag ", ["de"]="Anhang ", @@ -1473,7 +1473,7 @@ ["be"]="Глава ", ["bg"]="Eпизод ", ["ca"]="Capítol ", - ["cn"]={ "第", "章" }, + ["cn"]={ "第 ", " 章" }, ["cs"]="Kapitola ", ["da"]="", ["de"]="Kapitel ", @@ -1774,7 +1774,7 @@ ["be"]="Малюнак", ["bg"]="Фигура", ["ca"]="Figura ", - ["cn"]="图", + ["cn"]="图 ", ["cs"]="Obrázek ", ["da"]="Figur ", ["de"]="Abbildung ", @@ -1925,7 +1925,7 @@ ["be"]="Графіка ", ["bg"]="Графичен ", ["ca"]="Gràfica ", - ["cn"]="插图", + ["cn"]="插图 ", ["cs"]="Graf ", ["da"]="Grafik ", ["de"]="Grafik ", @@ -2058,7 +2058,7 @@ ["be"]="Інтэрмецца ", ["bg"]="Интермецо ", ["ca"]="Intermedi ", - ["cn"]="퉣", + ["cn"]="间奏 ", ["cs"]="Intermezzo ", ["da"]="Intermezzo ", ["de"]="Intermezzo ", @@ -2395,7 +2395,7 @@ ["be"]="радок ", ["bg"]="ред ", ["ca"]="línia ", - ["cn"]="行", + ["cn"]="行 ", ["cs"]="řádek ", ["da"]="linie ", ["de"]="Zeile ", @@ -2441,7 +2441,7 @@ ["be"]="радкi ", ["bg"]="редове ", ["ca"]="línies ", - ["cn"]="行", + ["cn"]="行 ", ["cs"]="řádky ", ["da"]="linier ", ["de"]="Zeilen ", @@ -3002,7 +3002,7 @@ ["be"]="Частка ", ["bg"]="Частка ", ["ca"]="Part ", - ["cn"]={ "第", "部分" }, + ["cn"]={ "第 ", " 部分" }, ["cs"]="Část ", ["da"]="Del ", ["de"]="Teil ", @@ -3130,7 +3130,7 @@ ["ar"]="فصل ", ["bg"]="Cекция ", ["ca"]="Secció ", - ["cn"]={ "第", "节" }, + ["cn"]={ "第 ", " 节" }, ["cs"]="Sekce ", ["da"]="", ["de"]="Abschnitt ", @@ -3513,7 +3513,7 @@ ["be"]="Табліца ", ["bg"]="Таблица ", ["ca"]="Taula ", - ["cn"]="表", + ["cn"]="表 ", ["cs"]="Tabulka ", ["da"]="Tabel ", ["de"]="Tabelle ", @@ -3863,7 +3863,7 @@ ["ar"]="الأشكال", ["be"]="Спіс ілюстрацый", ["ca"]="Figures", - ["cn"]="图形", + ["cn"]="图", ["cs"]="Seznam obrázků", ["da"]="Figurer", ["de"]="Abbildungen", @@ -4046,7 +4046,7 @@ ["be"]="Лагатыпы", ["bg"]="Логотипи", ["ca"]="Logotips", - ["cn"]="徽贬", + ["cn"]="徽标", ["cs"]="Loga", ["da"]="Logoer", ["de"]="Logos", --------------------------------------- -- Best regards, Li Yanrui

1 0

tikz error upgrading to texlive version (artix)
by Xavier B. 02 Apr '23

02 Apr '23

Hi, I use artix linux (a fork of arch with systemd alternative init systems). During the texlive package, I get this error: return { ["filename"]="/usr/share/texmf-dist/tex/generic/pgf/basiclayer/pgfcorepoints.code.tex", ["lastcontext"]="\n<inserted text> \n \\inaccessible \n<to be read again> \n \"\n\\pgfmath@catcodes ->\\catcode `\\==12 \\catcode `\\,=12 \\catcode `\\|=12 \\catcode `\\&=12 \\let \"\n \\pgfmath@char@quote \n\\pgfmathparse ->\\begingroup \\pgfmath@catcodes \n \\pgfmath@quickparsefalse \\ifpgfmathfloat \\let \\pgfmath@parse@next =\\pgfmathfloatparsenumber \\else \\let \\pgfmath@parse@next =\\pgfmathparse@ \\fi \\pgfmath@parse@next \n<argument> \\pgfmathparse \n {1cm}\\ifpgfmathmathunitsdeclared \\pgf@x \\pgfmathresult mu\\relax \\else \\pgf@x \\pgfmathresult pt\\relax \\fi \n\\pgfmath@next #1#2->#2\n \n...\nl.926 \\pgfsetxvec{\\pgfpoint{1cm}{0cm}}\n ", ["lastluaerror"]="?", ["lasttexerror"]="! Missing control sequence inserted", ["linenumber"]=926, ["offset"]=10, } I simply run context to this file: \usemodule[tikz] \starttext {\bf a} \tikz (0,0) -- (1,0); \stoptext My version of context is: [xan@coronari ~]$ context --version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /usr/share/texmf-dist/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2023.03.10 12:15 mtx-context | main context file: /usr/share/texmf-dist/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2023.03.10 12:15 My packages are: $ pacman -Qs texlive local/texlive-bibtexextra 2023.66579-1 (texlive-most) TeX Live - Additional BibTeX styles and bibliography databases local/texlive-bin 2023.66539-1 TeX Live binaries local/texlive-core 2023.66587-1 (texlive-most) TeX Live core distribution local/texlive-pictures 2023.66549-1 (texlive-most) TeX Live - Packages for drawings graphics local/texlive-publishers 2023.66550-1 (texlive-most) TeX Live - LaTeX classes and packages for specific publishers local/texlive-science 2023.66461-1 (texlive-most) TeX Live - Typesetting for mathematics, natural and computer sciences I also posted the message in Artix mailing list [https://lists.artixlinux.org/archives/artix-general/2023-March/000977.html] Thanks in advance, Xavier PS: In arch there are many AUR packages for installing minimal latest version: https://aur.archlinux.org/packages/context-minimals-git https://aur.archlinux.org/packages/context https://aur.archlinux.org/packages/context-modules Which one do you recomend to?

7 15

update / punctuation / math
by Hans Hagen 02 Apr '23

02 Apr '23

Hi, There have been some mails about punctuation spacing and a fix was added to the engine that related to that. As tests showed it to be okay so we made an update. It took a bit longer than normal because we were in the middle of some other math stuff: additional fonts and extensibles. Daniel Flipo maintains a few math fonts (like concrete, xcharter, erewhon, kp, euler) and the last few weeks more extensive support for extensibles was added and concrete became quite nice too, so these fonts make a nice benchmark. As they are part of the lmtx install and we made sure to support them. In the process we adapted our 2023 roadmap of which part is attached (we included an example end then decided to show of concrete). When we go through the process of 'upgrading' we noticed some interesting names for symbols and 'constructs'. Quite some come from plain and/or amsmath (in the past taco and aditya did some porting to context) and we're not always sure if something is really used (or even what it was intended for) so if you notice something weird or missing, let us know. Examples are welcome too. It might also be that something can go away because it's obsolete or never needed (so far we could resist te kick-out-symbole-name temptation when it comes to symbol names that we think no sane user can remember or imagine to be there). When often add extra tests to the test suite (math subsection). Hans & Mikael ps. Alan and I are still messing around with some cross referencing. That code is still experimental and can have issues that we're looking at but hard to nail down (huge complex cross-referencing documents). More about that later. ================================== We added the tex of the pdf below ====== extract from roadmap ====== \usemodule[article-basic,abbreviations-logos] \setupbodyfont[concrete] \starttext \startsubject[title=Math in \CONTEXT\ roadmap] \startitemize[n] \startitem After playing with math support for more than a year, we have come to the conclusion that it is time to move on. We have already discarded italic correction and now are replacing rules with extensibles. Much was already in place (and applied) but experiences with type one antykwas made us review some \OPENTYPE\ fonts. Not using rules makes some of them look better. The effect is subtle and probably not \AMS\ compliant, but we think that it will work out well for simple math like fractions of decimal numbers. Consequently, we have added to our shrinking to-do list the burden to investigate whether we can remove those obsolete code paths from the engine. After all, who needs italic correction, who prefers ugly rules to beautiful glyphs, and who understands all these font parameters? Furthermore, after all these years, we don't expect \OPENTYPE\ font and \UNICODE\ math technologies to improve much; we don't know if \MICROSOFT\ is developing their technology further at all. Therefore, we are confident that what we are doing is the way it should have been done when math was upgraded. Hopefully users will notice the improvements. \stopitem \startitem Math also means physics and units (that topic was brought up recently on the list by Gavin). Therefore, because we're in cleanup mode, we decided to eliminate some more. With \ISO\ now in place for a long time, we are going to ignore the existence of the inch as unit from now on. The unit will probably remain in the engine for nostalgic reasons, but it will no be accepted in MWE. Instead, we will provide some more modern, culturally correct, kid-friendly units that we will use in examples, manuals and such. Because the four-person strong team dealing with this wants to avoid making mistakes, we will go through a careful and scientifically sound process of calibration first, using a selected tex savvy audience. We expect these new units to be stable a month from now. Believe it or not, in the process of documenting all this, we found a buglet in the new math dimension spacing, so it has already paid off. Expect to hear more in a month or so, and enjoy your inches as long as you still can. In case you wonder how this relates to math other than mentioned: the math subsystem has 'mu' as adaptive unit, and that inspired is to come up with one for text (in addition to two new more or less fixed units). \stopitem \startitem The math family model is a fundamental concept in \TEX\ but we think we can do without. First of all, \OPENTYPE\ math fonts have (design) script and scriptscript sizes built in, so for that we have one family. Second, only full bold (heavy) makes sense as companion for regular math which is something that in practice we can support otherwise. So, this makes us consider dropping families altogether which then provides (mem) space for even more classes or dictionaries. If we nevertheless decide to keep families, we can certainly go with less than we have now, maybe two (or four if we want to be generous and also resemble original tex) of them is enough. We cannot imagine users wanting more. As a side note: completely divorcing families could make the math engine a bit leaner. It is hard to explain and users only care about the outcome. So more on this later. \stopitem \startitem Another path to explore is to identify the few building blocks that are needed for typesetting math, and then doing a bit more at the tex end. Of course that would nil quite some earlier effort, which is a bit frustrating, but still \unknown\ maybe the math engine can be reduced to a fraction of what is is now. \stopitem \startitem When we look at the math fonts and some characters in there, we sometimes wonder what makes sense. For some, searching in e.g. arXiv brings no hit. Basically we have obsolete math symbols and currently used one. That made us think about ancient math versus modern math, just like there is ancient greek and modern greek. Because math is a script one can wonder about obsolete math dialects with symbols just like there are plenty deal scripts in \UNICODE. We already are working on dictionaries but another axis is useability. \stopitem \startitem We no longer have the small / large extensible family model so we can simplify delimiters in the engine. Not something users should worry about. \stopitem \startitem We're not sure why math is considered stable because everything moved forward. Therefore we're preparing a bid for extra math symbols as needed in modern explorative and daring math thesis. When symbols are really used, and we have proof of that, it should be possible to get them un \UNICODE, just like all these emoji. We welcome input and as an example of currently faked symbols we added some to the distribution as easter eggs. One example: Mikael got contacted by a stressed student working on a thesis on probability. This student needed to typeset the characteristic function of a random variable \im {X} with density function \im {f_{X}}, and it was insisted to use another notation than the (wide) hat, that was already used for something else. For this reason the \tex {widerandomhat} was introduced, \useMPlibrary[newmath] \startformula E[\ee^{\ii tX}] = \widerandomhat{f_{X}}(t)\mtp{,} E[\ee^{\ii t(X_1+X_2)}] = \widerandomhat{f_{X_1} \ast f_{X_2}}(t)\mtp{.} \stopformula Naturally, it is automatically scaled, just like the ordinary wide hat \startformula \widehat{a+b+c+d+e+f} \neq \widerandomhat{a+b+c+d+e+f} \stopformula Once the thesis is printed, we will contact the \UNICODE\ Consortium to suggest that it gets a slot. \stopitem \startitem Our most ambitious project is a reverse engineering one, which is why it is conducted at the engineering faculty of the Dnul university (we cannot reveal the real name yet). In math articles one can find visualizing like $x\leftarrow x$ and there are plenty of \TEX\ commands that have arrow or hook in their names. If you look at the names of math symbols plenty are kind of weird. We think it is not natural and are considering a \quote {natural language math input} project, where you tell what it is and get the symbols you expect. For that we need to analyze typeset math and from the context as well as visualization derive a dataset that we can feed into a machine learning subsystem that then can be used to turn input into type. We have several stages in mind spanning years but it can be fun. Think of it like \quote {untagged math} which then of course results in \quote {untagged pdf}, but better! \stopitem \stopitemize Mikael & Hans \stopsubject \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 -----------------------------------------------------------------

6 10