May 2021 - ntg-context - NTG Mailing Lists

underscore hyphenation not working
by Pablo Rodriguez 10 May '21

10 May '21

Hans, some time ago, you provided me with the following code to hyphenate sha with underscore: \startluacode function document.addfunnyhyphen(tfmdata) local underscore = utf.byte("_") local char = tfmdata.characters[underscore] if not char then return end tfmdata.characters[0xFE000] = { width = 0, height = 0, depth = 0, commands = { { "right", -char.width }, { "down", char.depth }, { "slot", 1, underscore }, } } end utilities.sequencers.appendaction("aftercopyingcharacters", "after","document.addfunnyhyphen") local shared = { start = 1, length = 1, before = utf.char(0xFE000), after = nil, left = false, right = false, } local all = table.setmetatableindex({ }, function(t,k) return shared end) languages.hyphenators.traditional.installmethod("sha", function(dictionary,word,n) return all end) \stopluacode \definehyphenationfeatures [sha] [characters=all, alternative=sha, righthyphenchar="FE000] \sethyphenationfeatures[sha]% \setuphyphenation[method=traditional]% \starttext \hsize\zeropoint \tt abcde \stoptext I’m afraid that it isn’t working as expected with current latest from 2021.05.06 23:35. I wonder whether this might be caused by a bug or the code should be adapted to current latest. Many thanks for your help, Pablo -- http://www.ousia.tk

2 6

\prime is too high
by Jairo A. del Rio 10 May '21

10 May '21

The following: \starttext $s''$ %or $s^{\prime}$ \stoptext gives a too high symbol in ConTeXt LMTX 2021.05.06 23:35. ConTeXt MkIV isn't affected for such an issue. Jairo

3 2

Update setpath to set the path
by Thangalin 10 May '21

10 May '21

Thoughts on updating the setpath.bat file to persist setting the path? Here's an updated version that sets the system environment variable while preserving the existing unexpanded PATH value: rem SOF echo off set OWNPATH=%~dp0 set PLATFORM=mswin if defined ProgramFiles(x86) set PLATFORM=win64 if "%PROCESSOR_ARCHITECTURE%"=="AMD64" set PLATFORM=win64 if exist "%OWNPATH%tex\texmf-mswin\bin\context.exe" set PLATFORM=mswin if exist "%OWNPATH%tex\texmf-win64\bin\context.exe" set PLATFORM=win64 echo %PATH% | findstr "texmf-%PLATFORM%" > nul rem Only update the PATH if not previously updated if ERRORLEVEL 1 ( set Key="HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" set "CurrPath=" for /F "USEBACKQ tokens=2*" %%A in (`reg query %%Key%% /v PATH`) do ( if not "%%~B" == "" ( rem Preserve the existing PATH echo %%B > currpath.txt rem Update the current session set PATH=%PATH%;%OWNPATH%tex\texmf-%PLATFORM%\bin rem Change the PATH environment variable setx PATH "%%B;%OWNPATH%tex\texmf-%PLATFORM%\bin" /M ) ) ) rem EOF Another possibility would be to define CONTEXT_HOME as an unexpanded value added to both the system environment variables and the PATH variable. For example (haven't tried it): setx CONTEXT_HOME "%OWNPATH%tex\texmf-%PLATFORM%\bin" setx PATH "%%B;%%CONTEXT_HOME%%" The advantage with this pattern is that subsequent updates need only check for CONTEXT_HOME and change its value without having to worry about PATH parsing, which can be hairy. Yet another option to consider is changing the value for only the existing user, rather than system-wide. Perhaps two different batch files? The reason for this change is because the Windows installation instructions (on the wiki) are incomplete: technically, the user must run setpath.bat for each new session. This implies that any third-party program that wants to make use of ConTeXt on Windows would have to communicate said fact to the user, or let the user set the full path to ConTeXt within the third-party program. Both of these can be avoided by persisting the PATH setting across sessions. Thank you! P.S. Pasted: https://pastebin.com/qpsqXZNB

3 4

What is the ConTeXt way to handle this \vbox trick?
by Idris Samawi Hamid ادريس سماوي ح امد 09 May '21

09 May '21

Dear gang, Consider the following MWE (for a sequential multiple-choice exam), using some old and ugly TeX code: ======= \setupbodyfont[schola] \noheaderandfooterlines \setupwhitespace[big] \def\CHOICE#1#2{\leavevmode\vbox{\tabskip=0pt\everycr={} \halign{\strut\hfil##\hfil\cr#1\cr#2\cr}}} \starttext (Religion * Biology * Cosmology * Physics) is part of the subject matter of World Philosophies. (Religion * Biology * Cosmology * Physics) is part of the subject matter of World Philosophies. (\CHOICE{1}{Religion}\ * \CHOICE{X}{Biology} * \CHOICE{2}{Cosmology}\ * \CHOICE{X}{Physics}) is part of the subject matter of World Philosophies. \stoptext ======= Result is attached. Question: What is the most elegant ConTeXt way to get the same result as the above code, with equal or better control? Thank you in advance. Best wishes Idris -- Idris Samawi Hamid, Professor Department of Philosophy Colorado State University Fort Collins, CO 80512

2 1

weird word breaking in Win64
by Pablo Rodriguez 08 May '21

08 May '21

Dear list, the following sample breaks some words not right in Win64 (I cannot reproduce it in Linux): \enabledirectives[fonts.injections.method=advance] \setuppapersize[A6] \definefontfamily[mainface][rm] [TeX Gyre Pagella] \setupbodyfont[mainface] \starttext \input zapf \stoptext Copying text from latest Acrobat Reader DC, I get: Coming back to the use of typefaces in electronic publishing: many of the new typog raphers receive their knowledge and infor mation about the rules of typog raphy from books, from com puter mag azines or the instruction manuals which they get with the purchase of a PC or software. There is not so much basic instruction, as of now, as there was in the old days, showing the differences between good and bad typographic design. Many people are just fascinated by their PC's tricks, and think that a widely--praised program, called up on the screen, will make everything automatic from now on. Lines 3-5 contain word breaks that make searching impossible. This seems to be added by fonts.injections.method=advance. Could anyone on Windows confirm this issue? Many thanks for your help, Pablo -- http://www.ousia.tk

3 3

upcoming versions of lmtx
by Hans Hagen 07 May '21

07 May '21

Hi, With luametatex becoming more mature, it's time to get rid of some old code. For instance, we have lmt files that assume 5.4, but regular lua files should work for luajittex (5.2) and luatex (5.3). Most noticable are the lack of bitwise operators and integer devision in luajittex, but there are more details. Till now, part of this problem is deals with by using functions that can actually be seen as macros that can are optimized when the format is made (kind of c-ish). It's not pretty, but works and probably no one ever noticed it. That mechanism will probably stay (for the fun of it) but the less it's used for creating the format the better. Another complication is that we use mtxrun for both running luatex and luametatex so there we need to be friendly to all three engines. But ... eventually luametatex will be the stub for also luatex and then mtxrun can become 5.4+ (the --luatex flag already works that way). An alternative is that we have mtxrun.lmt as well as mtxrun.lua but why bother. I also need to keep in mind that there are users of the font code that expect it to work with luajittex but that can be dealt with by splitting files. By splitting modules in lua and lmt variants we can tune for luametatex so that will happen anyway (less code, no engine specific sections, again a smaller format file, etc). All these adaptations have no functional consequences but of course there can be temporary hickups because of some oversight. At the engine level there is also some occasional cleanup, like replacing some left-over low level 5.2/5.3 lua api things by 5.4 but that's kind of ongoing (as lua progresses). In principle users should not notice such changes, just like probably no one noticed that we now use a different zip library (in the beginning some high speed variants were tested too but it's not that critical and I just don't want architecture dependencies that complicate a build and can influence stability). I still try to minimize the code base and dependencies, although I admit that sometimes stuff gets added (like the more efficient memory allocator). But my target max binary size of 3MB (less with link time optimization and related stripping) and fast compilation goals are still met. 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

Hyphen collapsing
by Thangalin 07 May '21

07 May '21

Not sure if this is a regression: % SOF \nohyphencollapsing \setuphead[chapter][align={nothyphenated}] \starttext \chapter{Such --- Emdashery} \stoptext % EOF Expected: No collapsed hyphens. Actual: Hyphens are collapsed. Workaround: Remove the nothyphenated option or insert \nohyphencollapsing into the \chapter command. Is there another way to prevent collapsing hyphens with a single setting that applies to the entire document? The hyphens did not collapse in the previous version. Current version: 2021.05.06

2 3

very long hanging caption
by Jano Kula 07 May '21

07 May '21

Dear list, having images with very long captions I'd like captions to be wrapped around the figures. I would guess hang=yes parameter could do so, but not in my case. ---------------- text of | | the caption | | which is ---------------- much longer than the height of the image and should be wrapped around the image The second question is how to change the distance between image and the caption, distance parameter has no effect. MkIV, because footnotes in columns are needed (not in lmtx, yet). % macros=mkiv \setupcaption[ number=no, hang=yes, align={nothyphenated,flushleft}, distance=4mm, location=righthanging] \startbuffer[caption] \dorecurse{60}{very long caption } \stopbuffer \starttext \startplacefigure[title={\getbuffer[caption]}] \externalfigure[cow][height=40mm,width=80mm] \stopplacefigure \stoptext Thank you, Jano

2 2

Bug with OpenBSD 6.9 amd64?
by Damien Thiriet 07 May '21

07 May '21

Hi, I have just upgraded my LMTX install to OpenBSD 6.9. Unfortunately, my first context run aborted with this error message /usr/local/context/tex/texmf-openbsd6.9-amd64/bin/mtxrun[1]: syntax error: `newline' unexpected I tried mtxrun --generate and ended with alomst the same error message, as I could have expected /usr/local/context/tex/texmf-openbsd6.9-amd64/bin/mtxrun[1]: syntax error: `newline' unexpected I wiped the cache, then suppressed it, didn't change anything. Which informations might be helpful to solve this problem? Best regards, Damien Thiriet

2 3

SVG transparent stroke shown
by Thangalin 06 May '21

06 May '21

Hi again! % SOF\startbuffer[svg] <svg width="247.038" height="208.251"><path fill="#fff" stroke="transparent" d="M10 146.188V10h165.278v136.188z"/><path fill="#eef4d7" stroke="#2e2e2e" d="M123.856 44.896h-77v62h77z"/></svg> \stopbuffer \starttext \placefigure{}{\includesvgbuffer[svg][conversion=mp]} \stoptext % EOF Expected: No border around the outer white box, border around the inner green box. Actual: Border around both boxes. Version: 2021.05.06 Additional details: The SVG is generated using GraphViz, which adds a white box as the background with a transparent border. The GraphViz is being invoked over a rest API. Even if the binary has a setting to change the border colour, that setting probably isn't accessible via HTTP POST.

1 0