February 2024 - ntg-context - NTG Mailing Lists

behaviour sy in externalfigure
by Hans van der Meer 16 Feb '24

16 Feb '24

The scaling in \externalfigure[][] with option sy=number seems to have a discrete change in behaviour between sy=1.0 and sy=(not 1.0). The MWE (see below, FIGURE REMOVED BECAUSE OTHERWISE MESSAGE TOO LARGE) shows that factor sy≠1.0 is applied to the original height of the figure, but for sy=1.0 the height is changed proportional to the reduction in width. Thus the series sy=0.999 sy=1.0 sy=1.001 has a discontinuity in the scaling of height. I would expect sy=1.0 to return the figure in the original height. Is this behaviour on purpose? With the current behaviour I must provide for sy=1.0 => sy=1.001 in order to get the original height. Although not to difficult with a jump to Lua code, I would prefer not. yours sincerely dr. Hans van der Meer \starttext \ConTeXt\space version \contextversion\blank \type{\externalfigure[testfile.jpg]} source figure\crlf \externalfigure[testfile.jpg]\crlf \type{\externalfigure[testfile.jpg][width=5cm]}\crlf \externalfigure[testfile.jpg][width=5cm]\crlf Explanation: height scaled proportional to the width reduction. \blank \type{\externalfigure[testfile.jpg][width=5cm,sy=0.999]}\crlf \externalfigure[testfile.jpg][width=5cm,sy=1.001]\crlf Explanation: sy different from 1.0 applies sy to original height. \blank \type{\externalfigure[testfile.jpg][width=5cm,sy=1.0]}\crlf \externalfigure[testfile.jpg][width=5cm,sy=1.0]\crlf Explanation: sy=1.0 exactly is ignored? \blank \type{\externalfigure[testfile.jpg][width=5cm,sy=1.001]}\crlf \externalfigure[testfile.jpg][width=5cm,sy=1.001]\crlf Explanation: sy different from 1.0 applies sy to original height. \blank \stoptext met vriendelijke groet, dr. Hans van der Meer Burgemeester Rijnderslaan 244 ingang D 1185 MC Amstelveen tel. 020 6452701 / 06 53743629

1 0

Fwd: Re: Context lmtx for 32bit under LUBUNTU 18.04
by Henning Hraban Ramm 16 Feb '24

16 Feb '24

Sorry, I can’t help ATM. But Hans’ latest upload includes 32bt Linux binaries again. Hraban -------- Weitergeleitete Nachricht -------- Betreff: Re: [NTG-context] Re: Context lmtx for 32bit under LUBUNTU 18.04 Datum: Wed, 14 Feb 2024 17:28:38 +0100 Von: Alain Delmotte <alain.delmotte(a)leliseron.org> An: Henning Hraban Ramm <texml(a)fiee.net> Dear Henning, ------------------- Your instructions: PWD=`pwd` cd tex/texmf-context/source/luametatex sh build.sh cp build/native/luametatex "$PWD/tex/texmf-linux/bin/" cd "$PWD" ------------------- My actions: I created a 'context' folder in my home/alain directory in which I extracted the contlm.zip file. In context I did in a console PWD='pwd' then in context/source/luametatex sh build.sh alain@alain:pwd$ sh build.sh build.sh: 28: [: unexpected operator build.sh: 37: [: unexpected operator build.sh: 117: build.sh: cmake: not found build.sh: 122: build.sh: cmake: not found tex trees so I commented lines:28-111 and 119 this seems instruction to take into account the different plateforms, I did leave the last instruction: lines 112-118 and installed cmake, which I didn't have. then alain@alain:~/context/source/luametatex$ sh build.sh -- The C compiler identification is GNU 7.5.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Performing Test limited_support -- Performing Test limited_support - Success -- Configuring done -- Generating done -- Build files have been written to: /home/alain/context/source/luametatex/build/native Unknown argument --parallel Unknown argument 8 Usage: cmake --build <dir> [options] [-- [native-options]] Options: <dir> = Project binary directory to be built. --target <tgt> = Build <tgt> instead of default targets. May only be specified once. --config <cfg> = For multi-configuration tools, choose <cfg>. --clean-first = Build target 'clean' first, then build. (To clean only, use --target 'clean'.) --use-stderr = Ignored. Behavior is default in CMake >= 3.0. -- = Pass remaining options to the native tool. tex trees resources like public fonts : tex/texmf/.... the context macro package : tex/texmf-context/.... the luametatex binary : tex/texmf-native/bin/... optional third party modules : tex/texmf-context/.... fonts installed by the user : tex/texmf-fonts/fonts/data/.... styles made by the user : tex/texmf-projects/tex/context/user/.... binaries: tex/texmf-<your platform>/bin/luametatex : the compiled binary (some 2-3MB) tex/texmf-<your platform>/bin/mtxrun : copy of or link to luametatex tex/texmf-<your platform>/bin/context : copy of or link to luametatex tex/texmf-<your platform>/bin/mtxrun.lua : copy of tex/texmf-context/scripts/context/lua/mtxrun.lua tex/texmf-<your platform>/bin/context.lua : copy of tex/texmf-context/scripts/context/lua/context.lua commands: mtxrun --generate : create file database mtxrun --script fonts --reload : create font database mtxrun --autogenerate context ... : run tex file (e.g. from editor) The binaries have not been created! My cmake doesn't support --parallel (what is the use of parallèle?) I erased everything and started again with canges made to build.sh >>> this is the instructions at lines 121-122 >>> I commented the end of linee 122 alain@alain:~/context$ PWD='pwd' alain@alain:pwd$ cd source/luametatex alain@alain:~/context/source/luametatex$ sh build.sh -- The C compiler identification is GNU 7.5.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Performing Test limited_support -- Performing Test limited_support - Success -- Configuring done -- Generating done -- Build files have been written to: /home/alain/context/source/luametatex/build/native Usage: cmake --build <dir> [options] [-- [native-options]] Options: <dir> = Project binary directory to be built. --target <tgt> = Build <tgt> instead of default targets. May only be specified once. --config <cfg> = For multi-configuration tools, choose <cfg>. --clean-first = Build target 'clean' first, then build. (To clean only, use --target 'clean'.) --use-stderr = Ignored. Behavior is default in CMake >= 3.0. -- = Pass remaining options to the native tool. tex trees resources like public fonts : tex/texmf/.... the context macro package : tex/texmf-context/.... the luametatex binary : tex/texmf-native/bin/... optional third party modules : tex/texmf-context/.... fonts installed by the user : tex/texmf-fonts/fonts/data/.... styles made by the user : tex/texmf-projects/tex/context/user/.... binaries: tex/texmf-<your platform>/bin/luametatex : the compiled binary (some 2-3MB) tex/texmf-<your platform>/bin/mtxrun : copy of or link to luametatex tex/texmf-<your platform>/bin/context : copy of or link to luametatex tex/texmf-<your platform>/bin/mtxrun.lua : copy of tex/texmf-context/scripts/context/lua/mtxrun.lua tex/texmf-<your platform>/bin/context.lua : copy of tex/texmf-context/scripts/context/lua/context.lua commands: mtxrun --generate : create file database mtxrun --script fonts --reload : create font database mtxrun --autogenerate context ... : run tex file (e.g. from editor) ------------------------------------------------ there is no binaries and the tex tree doesn't exist. It seems that make require a folder <dir> in which to create the compiled files. Any help? Alain Le 13-02-24 à 18:21, Henning Hraban Ramm a écrit : > Am 13.02.24 um 17:29 schrieb Alain Delmotte: >> Hi, >> >> A month or so ago Hans provided a new upload (thanks I managed to get >> and install it on my Windows 10 64b). At that time I was struggling >> for having my computers back in order (that appends sometimes). >> >> Now I'd like to have LMTX on an old but still used (when travelling) >> portable under lubuntu 18.04 32Bits. >> >> There is no more executable available on pragma and I am using >> Context from TeX Live, but it is the 2017 version. >> >> I can do with it, but it would be better to have Context lmtx latest. >> >> Is it possible to have it? But if this a too complicate problem, I'll >> stand with the TeX Live Context. > > Just compile it yourself. > > > In your installation root (where install.sh is): > > PWD=`pwd` > cd tex/texmf-context/source/luametatex > sh build.sh > cp build/native/luametatex "$PWD/tex/texmf-linux/bin/" > cd "$PWD" > > > Hraban > ___________________________________________________________________________________ > > If your question is of interest to others as well, please add an entry > to the Wiki! > > maillist : ntg-context(a)ntg.nl / > https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl > webpage : https://www.pragma-ade.nl / https://context.aanhet.net > (mirror) > archive : https://github.com/contextgarden/context > wiki : https://wiki.contextgarden.net > ___________________________________________________________________________________ >

4 5

XML processing, unwanted indentation/alignment
by Michael Guravage 16 Feb '24

16 Feb '24

Greetings, I'm typesetting an address book whose addresses are in XML. A typical entry has this structure: <family surname=""> <address street="" housenumber="" postcode="1" city="" telephone="" /> <members> <member first_name="" initials="" maiden_name="" birthday="" email="" mobile="" /> <member first_name="" initials="" birthday="" email="" mobile="" /> <member first_name="" initials="" birthday="" /> </members> </family> initials and birthday are required, first_name can be left blank and email, mobile and maiden_name are optional. I've written a macro (name) to compose the name, i.e. initials, first_name (maiden_name), and another macro (nameemaillink) to make the name a link associated with an email address. % Derive an individual's name \def\name#1% {\ifxmlattempty{#1}{first_name} {\xmlatt{#1}{initials}} \else {\xmlatt{#1}{initials}, \xmlatt{#1}{first_name}} \fi \ifxmlattempty{#1}{maiden_name} {} \else { \tfxx(\xmlatt{#1}{maiden_name})} \fi} % Create a mailto:link that associates a individual's name with their email address. \def\nameemaillink#1% {\ifxmlattempty{#1}{email} {\name{#1}} \else {\goto{\name{#1}} [url(mailto:\xmlatt{#1}{email})]} \fi} I thought I was done when I noticed that a composed name with an empty first name, with or without an email address, is slightly indented. In the mwe Moe and Curly, without first names, are indented; while Shemp and Michael aren't. That the undesired indentation/alignment is dependent on the presence of a first name is baffling. After this long description, if someone would look at the code and tell me where I've gone wrong I would be very grateful. The interesting bits begin on lines 8 and 12 in xml.tex. -- With kind regards, Michael

4 3

Re: An announcement of my new book.
by SirColeman 15 Feb '24

15 Feb '24

>> This is wrong, the counter commands are official and the number variants are kept for backwards compatibility with old styles. I do recall reading on the ConTeXt wiki that \definenumber is maintained for backwards compatibility reasons. However, why then does ConTeXt fail to compile with \getcounter, if that's how it's supposed to work? I was confused, don't get me wrong, but what I wrote was my own conclusion on the matter. Clearly, we have a bug that needs to be reported. I wish my email hadn't included such misinformation. But now, this is a bug that needs to be resolved. I'm running ConTeXt version 2024.01.24, and the given attachment fails to compile, even with MkIV. I don't want to pester those subscribed to this mailing list with bug reports, so I thought it would be more sensible to post such reports on the context developers mailing list. I ask for confirmation that I can post there instead of here. Thanks.

12 14

/AFRelationship for attachments
by Pablo Rodriguez 15 Feb '24

15 Feb '24

Dear list, the new lpdf-wid.lmt contains in lines 302 and 377: local relation = specification.relation or "Unspecified" AFRelationship = pdfconstant(relation), The following sample compiled with current latest: \setupinteraction[state=start] \starttext attachment\attachment[method=hidden, relation=Data, file=xml-mkiv.pdf] \stoptext Gives the following object: 2 0 obj << /AFRelationship /Unspecified /EF << /F 1 0 R >> /F (xml-mkiv.pdf) /Type /Filespec /UF <FEFF0078006D006C002D006D006B00690076002E007000640066> >> endobj Sorry, but which is the right way to specify the /AFRelationship for embedded documents? Many thanks for your help, Pablo

1 0

Installation of linux-32bits
by Alain Delmotte 15 Feb '24

15 Feb '24

Hi! I tried to install the linux 32 bits kindly provided by Hans. It went all right up to: mtxrun -generate First I had to change my PATH putting the path to lmtx before TeXlive, because it was always the files from TeXlive which were used. Then I got: ---------------------------- alain@alain:~/context/tex/texmf-linux/bin$ mtxrun --generate resolvers | resolving | variable 'SELFAUTOLOC' set to '/home/alain/context/bin' resolvers | resolving | variable 'SELFAUTODIR' set to '/home/alain/context' resolvers | resolving | variable 'SELFAUTOPARENT' set to '/home/alain' resolvers | resolving | variable 'TEXMFCNF' set to '' resolvers | resolving | variable 'TEXMF' set to '' resolvers | resolving | variable 'TEXOS' set to 'context' [...] resolvers | resolving | resolvers | resolving | warning: no lua configuration files found resolvers | resolving | no texmf paths are defined (using TEXMF) resolvers | resolving | mtxrun | mtxrun | elapsed lua time: 0.113 seconds ----------------------------- so the binaries were not created. What did I wrong? How to solve the problem? Thanks, Alain

1 0

Seeindex with zie instead of see?
by G.C.H.M. Verhaag 15 Feb '24

15 Feb '24

Hi ConTeXt users, Wondering whether there is a possibility to modify the word *see* into the Dutch word *zie* in the use of the \seeindex command? Regards, Gerard

3 2

upload
by Hans Hagen 15 Feb '24

15 Feb '24

Hi, as we're around texlive code freeze time we're also in upload mode - i uploaded a new lmtx - i also added linux and windows 32 bin (as it seems to have users) - we're now using lua 5.5 which has one restriction (was already announced a while ago): for i=1,10 in t do .... i = 2 * i .... end should now be: for i=1,10 in t do .... local i = 2 * i .... end as one cannot change the (local constant) i which actually is not that different from what metapost does. The good news is that voilating this is reported when a lua file is loaded so one can't get it unexspectedly. 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 -----------------------------------------------------------------

3 3

mtxrun.lua:10080: bad argument #9 to 'format'
by Garulfo 15 Feb '24

15 Feb '24

Hi, return is OK with: mtxrun --script font --list --spec --filter="fontname=ibm*" but removing the m from the pattern mtxrun --script font --list --spec --filter="fontname=ib*" I get : lua error : function call: ...0-app_context-linux-64/tex/texmf-linux-64/bin/mtxrun.lua:10080: bad argument #9 to 'format' (number expected, got string) mtxrun --version mtxrun | ConTeXt TDS Runner Tool 1.32 mtxrun | source path

5 8

An announcement of my new book.
by SirColeman 14 Feb '24

14 Feb '24

Greetings all. I have a passion for typesetting. I found that currently the best typesetting systems are those that are based on TeX. Of them, there are LaTeX, and ConTeXt. LaTeX is very well documented and popular; ConTeXt, on the other hand, is apparently very powerful and capable, but is not as well documented. There are things that are spectacularly well documented, others that only show hints, and leave it up to the user to figure things out on their own, and others still that won't even compile on a more recent version of ConTeXt (apparently the proper way to access a counter's value in ConTeXt is to use \getnumber or \convertednumber, and not \getcounter. That's just an example). I thus thought, as an exercise in typesetting, in writing, and also to help the ConTeXt documentation, to write a new book, a large book, that teaches the details of how ConTeXt on a lower level works, allowing one to understand how to utilize low level typesetting features for anything more sophisticated than a simple book or article. By lower level, I mean how things like heads, items, references, alignment, tables, etc., work. Also, I would like a book that teaches things like how to program it using lua, how to understand and utilize the underlying engine itself (the low level LuaMetaTeX), how to even use DocBook with ConTeXt, etc. (I do realize that there already are manuals for lua in ConTeXt and on LuaMetaTeX, etc., and manuals on various different parts of ConTeXt, and I'll certainly be learning from them whenever their particular topic comes, but I reserve the opportunity to rewrite parts of these manuals for this book, as is necessary for the book's purpose, perhaps referencing these manuals for further details.) In particular, I want to go a step beyond the book "A not so short introduction to ConTeXt Mark IV", and teach the particularly advanced features, where there is sparse information. Particularly, it's meant to serve as one complete reference, instead of having to hunt for different manuals, which explain things differently, and with the consequence that it's hard to find a particular piece of information because its scattered around so many different places. This book should serve as the one and only final documentation that you would need. It would contain everything in a highly cohesive format, in one place, and make particular pieces of information particularly easy to find. I realize that this is a very ambitious undertaking, but I find that a unified source of information is better than information with varying levels of quality scattered across more places than one can hold in his head. I just have one question: What is all the necessary material to understand and utilize the low level TeX programming language itself? That is, what do I need to read to learn to be able to read the ConTeXt source code itself (which is written in TeX---and lua, but I can help myself in that regard)? Is the "Low Level TeX" set of manuals all that I'll need, or will I need other sources of information too? And also, is it worth learning Plain TeX, and reading The TeXbook, or is not necessary? And, I'm grateful to have an alternative to LaTeX. It's certainly promising, but I would like to help make it appealing, by making it easy to learn and master it, and provide a single source of information. I'm grateful for having ConTeXt. P.S. If I have bugs to file, should I file them on this mailing list, or on the dev-context(a)ntg.nl mailing list? And, to all beginner ConTeXt users: What would you like to see covered in this book? Thanks. -- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com

4 3