- ntg-context - NTG Mailing Lists

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

Suppressing headers and footers on blank pages before pagebreak at the end of a chapter.
by rha17＠t-online.de 07 Apr '21

07 Apr '21

Hi list, I typeset my first project with ConTeXt, a small booklet with some chapters, frontmatter, no headers, but pagenumbers in the middle of the footers. I use two environment files. The text is split into component TeX-files. All is structured by a project and a product file. Now I have run in some problems, I couldn’t solve with the garden and the archives of this and stackexchange’s list. But I’m sure that it is almost too simple for you experts. Let’s start with one. As intended, a new chapter starts on a right/odd page. If the chapter before ends on a right page, too, there should be a blank left/even page. But in my case there is the pagenumber in the footer – which looks more horrible than an orphan line. A. Which setting in which setup or definition gives a command like: suppress/skip/hide the header, footer and margin of last page of a chapter, if the text area is empty. B. More elaborate, a set of commands could – distinguish between headers, footers, an margins and – extend the commands on those pages at the end of the chapters – that do not show any text within the last line of the text area, i. e. the very last page of a chapter (even, but whith some text) – or the second last page (odd, with some text, before a complete blank even page). A book design according to (A) is standard. I’m sure there is a solution in ConTeXt. (B) can be found often, at least in books from pre-computer times. Ralf

2 1

Parenthesis error in metapost
by Mikael Sundqvist 07 Apr '21

07 Apr '21

Hi, the following code has been working before: \starttext \startMPpage[instance=decimalfun] draw function(1,"x","x*sin(x)",0.5,1,1/100) scaled 1in; \stopMPpage \stoptext Now (with an updated ConTeXt) I get an error: metapost > loading 'metafun' as 'metafun.mpxl' using method 'decimal' metapost > initializing number mode 'decimal' metafun > log > metafun > log > error: Missing ')' has been inserted metafun > log > metapost > log > <to be read again> metapost > log > ( metapost > log > <scantokens> x*sin( metapost > log > x) metapost > log > <to be read again> metapost > log > ) Maybe I have done something wrong earlier, but I cannot see any unmatched parenthesis now. /Mikael

2 1

"Scheduled" downtime of the contextgarden server
by Mojca Miklavec 05 Apr '21

05 Apr '21

Dear ConTeXters, There will be a "scheduled" downtime of the contextgarden.net server for maintenance reasons (the part that's hosted in Slovenia; that excludes wiki & modules, but includes the old distribution, buildbot CI, CTAN, TL pretest & w32tex mirror, ...) in one of the following days. It's not yet clear when exactly the downtime will happen (and all the lockdowns etc. make that even harder to predict) and I'm also not entirely sure how long it will take, this is just to give you a notice upfront. Mojca (PS: I hope that TL 21 won't need any further builds, else we can postpone this.)

1 1

SVG comments, transparency, and extended font styles
by Thangalin 03 Apr '21

03 Apr '21

Issues encountered with version 2021.03.31 18:04. 1. Comments in SVG % SOF \startbuffer[svg] <svg viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg"> <g><circle cx="50" cy="50" r="20"/></g></svg> \stopbuffer \starttext \placefigure{}{\includesvgbuffer[svg][conversion=mp]} \stoptext % EOF Expected: Black circle, no border, comment lines ignored. Actual: Empty square. 2. Transparent stroke % SOF \startbuffer[svg] <svg xmlns="http://www.w3.org/2000/svg" version="1.1"> <polygon fill="#eeffff" stroke="transparent" points="500,10 500,0 0,0 0,10" /> </svg> \stopbuffer \starttext \placefigure{}{\includesvgbuffer[svg][conversion=mp]} \stoptext % EOF Expected: Light cyan rectangle, no border (it's transparent). Actual: Light cyan rectangle with visible border. 3. Inkscape font specification We discussed this previously: Inkscape extends the SVG specification with a custom style class ("-inkscape-font-specification") that allows its users to refine font styles. % SOF \startbuffer[svg] <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 154.6 19.3" width="155" height="19"><text x="-6.7" y="-2.3"><tspan x="-1.9" y="15" style="-inkscape-font-specification:'Roboto, Ultra-Light';font-family:Roboto;font-size:20px;font-weight:200">Roboto Ultra-Light</tspan></text></svg> \stopbuffer \starttext \placefigure{}{\includesvgbuffer[svg][conversion=mp]} \stoptext % EOF Expected: "Roboto Ultra-Light" appears in Roboto Ultra-Light font. Actual: Empty square. Supporting this via MetaPost would help maintain backwards compatibility (with ConTeXt invoking Inkscape). Thank you!

2 3

Floating objects next to text mess up paragraph spacing
by Daniel Barker 01 Apr '21

01 Apr '21

Hi all, I have noticed that placing a floating object next to text with location "left", "right", etc. seems to move the current paragraph slightly up, resulting in too little space between the current and previous paragraph. This can be seen quite clearly in the output of the following example: \setupbodyfont[dejavu, serif, 12pt] \starttext \samplefile{lorem} \startplacefigure[location={right, none}] \framed[width=3cm, height=2cm]{graphic} \stopplacefigure \samplefile{lorem} \samplefile{lorem} \stoptext I am using the current (2021.03.31 18:04) version of ConTeXt LMTX. On ConTeXt live, which seems to be running an older version, this does not occur, i.e. the spacing is even, as I would expect it to be. I assume this is a bug, or am I doing something wrong? Thank you, Daniel

2 1

Running a couple of context statements in a linux bash shell heredocument?
by Alexander Rosenstock 01 Apr '21

01 Apr '21

4 3