- ntg-context - Mailing Lists

A Metafun-Problem
by Willi Egger 13 Apr '21

13 Apr '21

Hi can somebody tell me why I do not get a trapezoid with bottom angles of 120 degrees? Please try the attached minimal example. Thank you! Willi

3 4

Sudoku module
by Jairo A. del Rio 12 Apr '21

12 Apr '21

Hi, list! I've just finished a minimal module for sudoku puzzles based on Peter Norvig's algorithm. The module and examples are in the link below: https://github.com/JairoAdelRio/context-sudoku My port is a sorta literal translation of Python's version, so improvements are to be done. As always, I'm having trouble passing color data from TeX to Lua so that sudokus have more customizable aesthetics. I'll gladly accept any feedback and recommendations before I submit the module to the Garden. Thank you very much. Stay safe. Jairo

1 0

Alignment with an enumeration
by Fabrice Couvreur 12 Apr '21

12 Apr '21

Hi, Is it possible that the first item is on the baseline of the definition environment title ? Thank you. Fabrice \define\ItemCommand {\hskip\zeropoint\relax\autoinsertnextspace} \setupitemgroup [itemize] [color=darkred, style=bold, distance=\spaceamount] \setupitemgroup [itemize:1] [option={n,packed,fit,intext}, command=\ItemCommand] \setupitemgroup [itemize:2] [lefttext=, righttext=, option={a,text}] \setupenumerations [before={}, after={\blank}, alternative=serried, number=no, title=yes, titleleft={(}, titleright={)}, prefix=yes, prefixsegments=chapter, way=bychapter, titlestyle=bold, width=broad] \defineenumeration [definition] [text=Définition, number=no, headcommand=\groupedcommand{}{}, style=normal] \starttext \startdefinition \input knuth \stopdefinition \startdefinition \startitemize[n] \startitem First item \stopitem \startitem Second item \stopitem \stopitemize \stopdefinition \stoptext

1 0

Re: [NTG-context] Ligature suppression word list
by rha17＠t-online.de 12 Apr '21

12 Apr '21

> Message: 2 > Date: Tue, 6 Apr 2021 15:03:54 +0000 > From: <denis.maier(a)ub.unibe.ch <mailto:denis.maier@ub.unibe.ch>> > To: <j.hagen(a)xs4all.nl <mailto:j.hagen@xs4all.nl>>, <ntg-context(a)ntg.nl <mailto:ntg-context@ntg.nl>> > Subject: Re: [NTG-context] Ligature suppression word list > Message-ID: <41e6530172b54bffb7a82febff0a6be5(a)ub.unibe.ch <mailto:41e6530172b54bffb7a82febff0a6be5@ub.unibe.ch>> > Content-Type: text/plain; charset="iso-8859-1" > >> -----Ursprüngliche Nachricht----- >> Von: Hans Hagen <j.hagen(a)xs4all.nl <mailto:j.hagen@xs4all.nl>> >> Gesendet: Samstag, 3. April 2021 17:58 >> An: mailing list for ConTeXt users <ntg-context(a)ntg.nl <mailto:ntg-context@ntg.nl>>; Maier, Denis >> Christian (UB) <denis.maier(a)ub.unibe.ch <mailto:denis.maier@ub.unibe.ch>> >> Betreff: Re: [NTG-context] Ligature suppression word list […] >> >>> 2. A bigger solution might be to use selnoligs patterns in a script >>> that can be run over a large corpus, such as the DWDS (Digitales >>> Wörterbuch der deutschen Sprache). That should produce us a more >>> complete list of words where ligatures must be suppressed. >> >> where is that DWDS ... i can write some code to deal with it (i'd rather start >> from the source than from some interpretation; who know what more there >> is to uncover) > > As it turn out, the linguists that helped with the selnolig package did use another corpus: Stuttgart "Deutsch" Web as Corpus > They describe their approach in that paper: https://raw.githubusercontent.com/SHildebrandt/selnolig-check/master/selnol… <https://raw.githubusercontent.com/SHildebrandt/selnolig-check/master/selnol…> A lot of corpora can be found here: https://wortschatz.uni-leipzig.de/de <https://wortschatz.uni-leipzig.de/de> especially here: https://wortschatz.uni-leipzig.de/de/download/German <https://wortschatz.uni-leipzig.de/de/download/German> There are corpora of many other languages, too, such as English, French, Dutch, Spanish, Russian, Japanese, Latin, … HTH Ralf

2 2

Set luatex cache directory path
by Thangalin 11 Apr '21

11 Apr '21

Peter Münster once asked: > What should I do please, to prevent ConTeXt from creating $HOME/luatex-cache? I'd like to do the same: $ cd $HOME $ ls luatex-cache ls: cannot access 'luatex-cache': No such file or directory $ context test.tex $ ls luatex-cache/ context $ rm -rf luatex-cache $ export TEXMFCACHE=/tmp $ context test.tex mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' $ export TEXMFCACHE= $ context --version ... mtx-context | current version: 2021.03.31 18:04 What environment variable must change to set the luatex-cache directory? Thank you!

3 8

Arabic place names
by jbf 11 Apr '21

11 Apr '21

I have a lengthy text in English which occasionally uses Arabic place names in brackets, e.g. Khàbab ( خبب )is a Syrian town 50 km south of Damascus The text is copy-pasted from a Word file, so I do not have to type the Arabic as such, and would not know how to do that anyway. Since I never usually have to work with Arabic script (though I do have a font installed and recognised by ConTeXt (with the usual mtxrun commands) I am not sure how to achieve this. There might be just half a dozen of these place names involved in a text of some 300 pages worth. The font, BTW is Arslan Wessam A.ttf My humble attempt: I did the following in my preamble: \definefallbackfamily [mainface] [sans] [aarslanwessama] [range=arabic] The rest of the [mainface] setups are obviously western fonts. But the fallbackfamily approach did nothing to help. I also tried: Khàbab {\switchtobodyfont[aarslanwessama](خبب)} is a Syrian town 50 km south of Damascus... but that did nothing either. Am quite out of my depth with this one so any help would be appreciated. Julian

2 3

files not readable
by Jano Kula 10 Apr '21

10 Apr '21

Hello, updated lmtx (ver: 2021.04.09 19:59 LMTX), paths updated, etc. \enabletrackers[resolvers.*] \starttext Readable? \stoptext shows in log some file are "not readable": resolvers > resolving > file 'type-imp-loc.mkxl' is not readable resolvers > resolving > file './type-imp-loc.mkxl' is not readable resolvers > resolving > file 'type-imp-loc.mkxl' is not readable resolvers > resolving > file 'type-imp-loc.mkiv' is not readable resolvers > resolving > file './type-imp-loc.mkiv' is not readable [...] resolvers > resolving > file 'lpdf-pdx.xml' is not readable resolvers > resolving > file './lpdf-pdx.xml' is not readable I have the same problem with some of my own files (some only), but have noticed even files in the distro are "not readable". Same on windows and linux. Deleting cache didn't help either. What could be the reason? Regards, Jano

2 4

Hyphenation patterns
by Denis Maier 09 Apr '21

09 Apr '21

Hi, where can I find the hyphenation patterns used by ConTeXt? I have two wrongly hyphenated words, and I want to check whether this is due to incorrect patterns. (I tried the source browser... not much luck so far.) The words are: 1. applicable => hyphenated as applic-able 2. obligated => hyphenated as oblig-ated I know I can use \hyphenation to correct that, but I wanted to check the patterns nevertheless. Best, Denis

6 11

new upload
by Hans Hagen 09 Apr '21

09 Apr '21

Hi, I uploaded a new version of lmtx. (1) The only additions are in the language arena (discussed here before). For those working on that, the trackers hyphenation.applied hyphenation.applied.console hyphenation.applied.visualize[=ligatures] languages.patterns languages.goodies languages.applied have been updated. Also, exceptions can be stored in the goodies files (and then follow a slightly different route). There's also (at the engine level): \tracinghyphenation which is 1 by default (report bad patterns, as before); a value of 2 reports hyphenation and exceptions states, while 3 also adds detail if it has been applied. (2) A second aspect of the upload concerns windows. Till now we use binaries that are crosscompiled on linux. These perform somewhat better than native msvc compiled binaries ... until last week. The native windows binaries now are some 5+ % faster than the cross compiled ones. However, because it is still somewhat experimental, the installation uses the ming ones. (Running the test suite went down from 1350 sec cross compiled to 1200 seconds native.) If you want to check this out, fetch the binaries from the build server: https://dl.contextgarden.net/build/luametatex/win64/ make sure you replace/link luametatex.exe, mtxrun.exe and context.exe so that all then use the replacement. Mojca also configured the setup for native 32 bit binaries in case you need those. (The clang variants are compiled because want to keep an eye on that but they are definitely slower.) If this experiment works out ok I might also investigate it for other platforms. The gain is mostly in the lua department, less in metapost and tex but still a valid reason to use my laptop for another few years. (It is anyway cheaper and more environment friendly to make luametatex faster than to buy a new machine.) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Ligature suppression word list
by denis.maier＠ub.unibe.ch 08 Apr '21

08 Apr '21

Hi everyone Now that Hans has implemented the new ligature suppression mechanism via language goodies - thanks again Hans! - we now need to come up with wordlists. I've started working on a list of German words with ligatures that should be suppressed. The list is derived from the word list that comes with the lualatex selnolig package: https://github.com/micoloretan/selnolig/blob/master/selnolig-german-wordlis… You can find the current list here : https://github.com/denismaier/context-nolig-wordlist The list is currently organized as follows : 1. L.25-l.35: This specifies words where automatic pattern matching is more difficult than usually because the words contain multiple ligatures, some of which must be suppressed while others must be preserved. In the case of « Auflagefläche » it's even the same combination of letters. So here, we use the bar | to manually indicate points where no ligature must occur. 2. L. 36ff.: The vast amount of words is currently in that list that specifies words where a ff, fl, fi, ffi, or ffl ligature has to be broken up after the first f. 3. L.1804ff contain words where ffi, ffl, or fff ligatures have to be prevented after the second f, so the first two fs form a ligature. 4. The remaining blocks starting at L.1900, l. 2073, l. 2157, l. 2225, and l. 2277 suppress ligatures for « ft » and « fft », « fb » and « ffb », « fh » and « ffh», «fj» and «ffj», and «fk» and «ffk» Obviously, that list is far from being complete, and the question is if it ever can be. Please have a look and feel free to propose more words to be included - either via mail or directly on github. More generally, there's the question how such a list should be enhanced? I was thinking about two options: 1. The new language options features include a tracker that allows for tracking for which words in a given document ligature prevention happened, and which words haven't been touched by the mechanism. It should be possible to analyze the log file and to create lists of words with ligatures. Should be a rather simple step to derive new words for the ligature-suppression wordlist. 2. A bigger solution might be to use selnoligs patterns in a script that can be run over a large corpus, such as the DWDS (Digitales Wörterbuch der deutschen Sprache). That should produce us a more complete list of words where ligatures must be suppressed. What do you think? Best, Denis

4 12