Re: [NTG-context] Problem with latest version ?
On 1/5/2023 2:40 AM, Gavin via ntg-context wrote: Hi List, I could not figure out the right spot for the files m-tikz-pgfplots.tex and m-tikz-pgfplotstable.tex. I don’t currently have files with those names anywhere, and files with similar names and contents appear in a couple different places. I had to put off sorting it out until I had some more time. I was able to find the right place for m-tikz.mkxl, and it prevented an error at \usemodule[pgfplots], but I’d still get an error if I tried to use any command from the pgfplots. indeed they go alongside the m-tikz file ... did you run mtxrun --generate? - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] \autoinsertedspace fails
On 1/5/2023 4:21 AM, Rik Kabel via ntg-context wrote:
On 2023-01-04 18:45, Hans Hagen wrote:
On 1/4/2023 11:10 PM, Rik Kabel via ntg-context wrote:
No change with the latest (2023.01.04).
Is this a problem with what I am doing, or a bug?
well, it's new and not thtat tested ... we need to specify it
This\optionalspace fails unexpectedly with autoinsertedspace.\par
This\optionalspace \emph{fails unexpectedly} with autoinsertedspace.\par
there can be more variants, like do we want to remove preceding spaces?
we already have:
This\optionalspace, fails unexpectedly with autoinsertedspace.\par
This\optionalspace, \emph{fails unexpectedly} with autoinsertedspace.\par
This\optionalspace fails unexpectedly with autoinsertedspace.\par
This\optionalspace \emph{fails unexpectedly} with autoinsertedspace.\par
\optionalspace works correctly (that is, as I want it to) for all of my
use cases under both MkIV and LMTX. Is there any reason that this should
not be used in user documents?
depends ... it checks punctuation
I do wonder what characters are considered "punctuation" for the purpose
of suppressing the next space. The standard six sentence termination
characters (?!.:;,) are honored, and so are many others (quotation
marks, including guillemot, square and curly braces, and parens). But
sentence opening characters (¿¡) are as well. Vertical bars (|¦) and
basic mathematical characters (+-=*) are not treated as punctuation.
Where (in the source or manuals) are these to be found?
we use unicode properties (collected in char-def.lua)
As far as removing leading spaces, I do not see that it is necessary,
but it may help create more readable sources.
Thank you for the fix.
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] \autoinsertedspace fails
On 2023-01-04 18:45, Hans Hagen wrote:
On 1/4/2023 11:10 PM, Rik Kabel via ntg-context wrote:
No change with the latest (2023.01.04).
Is this a problem with what I am doing, or a bug?
well, it's new and not thtat tested ... we need to specify it
This\optionalspace fails unexpectedly with autoinsertedspace.\par
This\optionalspace \emph{fails unexpectedly} with autoinsertedspace.\par
there can be more variants, like do we want to remove preceding spaces?
we already have:
This\optionalspace, fails unexpectedly with autoinsertedspace.\par
This\optionalspace, \emph{fails unexpectedly} with autoinsertedspace.\par
This\optionalspace fails unexpectedly with autoinsertedspace.\par
This\optionalspace \emph{fails unexpectedly} with autoinsertedspace.\par
\optionalspace works correctly (that is, as I want it to) for all of my
use cases under both MkIV and LMTX. Is there any reason that this should
not be used in user documents?
I do wonder what characters are considered "punctuation" for the purpose
of suppressing the next space. The standard six sentence termination
characters (?!.:;,) are honored, and so are many others (quotation
marks, including guillemot, square and curly braces, and parens). But
sentence opening characters (¿¡) are as well. Vertical bars (|¦) and
basic mathematical characters (+-=*) are not treated as punctuation.
Where (in the source or manuals) are these to be found?
As far as removing leading spaces, I do not see that it is necessary,
but it may help create more readable sources.
Thank you for the fix.
--
Rik
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Problem with latest version ?
Hi List, I could not figure out the right spot for the files m-tikz-pgfplots.tex and m-tikz-pgfplotstable.tex. I don’t currently have files with those names anywhere, and files with similar names and contents appear in a couple different places. I had to put off sorting it out until I had some more time. I was able to find the right place for m-tikz.mkxl, and it prevented an error at \usemodule[pgfplots], but I’d still get an error if I tried to use any command from the pgfplots. Gavin > On Jan 4, 2023, at 4:22 PM, Hans Hagen via ntg-context > wrote: > > On 1/4/2023 7:05 PM, Henning Hraban Ramm via ntg-context wrote: >> Am 04.01.23 um 19:00 schrieb Fabrice Couvreur via ntg-context: >>> The problem seems to come from pgfplots ... >> There was a message about the same by Gavin and an answer by Hans on >> 2022-12-30. Maybe the fix didn’t make it into the latest upload. > no news from gavin so ... not added yet > > > - > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > - > > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] \autoinsertedspace fails
On 1/4/2023 11:10 PM, Rik Kabel via ntg-context wrote:
No change with the latest (2023.01.04).
Is this a problem with what I am doing, or a bug?
well, it's new and not thtat tested ... we need to specify it
This\optionalspace fails unexpectedly with autoinsertedspace.\par
This\optionalspace \emph{fails unexpectedly} with autoinsertedspace.\par
there can be more variants, like do we want to remove preceding spaces?
we already have:
This\optionalspace, fails unexpectedly with autoinsertedspace.\par
This\optionalspace, \emph{fails unexpectedly} with autoinsertedspace.\par
This\optionalspace fails unexpectedly with autoinsertedspace.\par
This\optionalspace \emph{fails unexpectedly} with autoinsertedspace.\par
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
if not modules then modules = { } end modules ['spac-chr'] = {
version = 1.001,
optimize = true,
comment = "companion to spac-chr.mkiv",
author= "Hans Hagen, PRAGMA-ADE, Hasselt NL",
copyright = "PRAGMA ADE / ConTeXt Development Team",
license = "see context related readme files"
}
local byte, lower = string.byte, string.lower
-- beware: attribute copying is bugged ... there will be a proper luatex helper
-- for this
-- to be redone: characters will become tagged spaces instead as then we keep
track of
-- spaceskip etc
-- todo: only setattr when export / use properties
local next = next
local trace_characters = false trackers.register("typesetters.characters",
function(v) trace_characters = v end)
local trace_nbsp = false trackers.register("typesetters.nbsp",
function(v) trace_nbsp = v end)
local report_characters = logs.reporter("typesetting","characters")
local nodes, node = nodes, node
local nuts = nodes.nuts
local getid = nuts.getid
local getsubtype = nuts.getsubtype
local setsubtype = nuts.setsubtype
local getboth= nuts.getboth
local getnext= nuts.getnext
local getprev= nuts.getprev
local getattr= nuts.getattr
local setattr= nuts.setattr
local getlanguage= nuts.getlanguage
local setchar= nuts.setchar
local setattrlist= nuts.setattrlist
local getfont= nuts.getfont
local isglyph= nuts.isglyph
local setcolor = nodes.tracers.colors.set
local insertnodebefore = nuts.insertbefore
local insertnodeafter= nuts.insertafter
local remove_node= nuts.remove
local nextchar = nuts.traversers.char
local nextglyph = nuts.traversers.glyph
local copy_node = nuts.copy
local nodepool = nuts.pool
local new_penalty= nodepool.penalty
local new_glue = nodepool.glue
local new_kern = nodepool.kern
local new_rule = nodepool.rule
local nodecodes = nodes.nodecodes
local gluecodes = nodes.gluecodes
local glyph_code = nodecodes.glyph
local glue_code = nodecodes.glue
local spaceskip_code = gluecodes.spaceskip
local chardata = characters.data
local ispunctuation = characters.is_punctuation
local canhavespace = characters.can_have_space
local typesetters= typesetters
local unicodeblocks = characters.blocks
local characters = typesetters.characters or { } -- can be predefined
typesetters.characters = characters
local fonthashes = fonts.hashes
local fontparameters = fonthashes.parameters
local fontcharacters = fonthashes.characters
local fontquads = fonthashes.quads
local setmetatableindex = table.setmetatableindex
local a_character= attributes.private("characters")
local a_alignstate = attributes.private("alignstate")
local c_zero = byte('0')
local c_period = byte('.')
local function inject_quad_space(unicode,head,current,fraction)
if fraction ~= 0 then
fraction = fraction * fontquads[getfont(current)]
end
local glue = new_glue(fraction)
setattrlist(glue,current)
setattrlist(current) -- why reset all
setattr(glue,a_character,unicode)
return insertnodeafter(head,current,glue)
end
local function inject_char_space(unicode,head,current,parent)
local font = getfont(current)
local char = fontcharacters[font][parent]
local glue = new_glue(char and char.width or fontparameters[font].space)
setattrlist(glue,current)
setattrlist(current) -- why reset all
setattr(glue,a_character,unicode)
return insertnodeafter(head,current,glue)
end
local function
inject_nobreak_space(unicode,head,current,space,spacestretch,spaceshrink)
local glue= new_glue(space,spacestretch,spaceshrink)
local
Re: [NTG-context] Tabulate \TH command not working in latest release
On 1/5/2023 12:16 AM, Michael Guravage via ntg-context wrote: While typesetting a document containing a small tabulated table with the latest release I noticed that the tabulate \TH command hadn't added any vertical space between the rows. Here's a mwe. \starttext \starttabulate[|l|l|] \NC Γ \NC Gamma \NC\NR \NC Θ \NC Theta \NC\NR \TB[line] \NC Φ \NC Phi \NC\NR \stoptabulate \stoptext swap nop and yes in tabl-tbl.mkxl, like: \appendtoks \enforced\let\TB\tabl_tabulate_TB_nop \to \t_tabl_tabulate_initializers_first \appendtoks \enforced\let\TB\tabl_tabulate_TB_yes \to \t_tabl_tabulate_initializers_second 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Problem with latest version ?
On 1/4/2023 7:05 PM, Henning Hraban Ramm via ntg-context wrote: Am 04.01.23 um 19:00 schrieb Fabrice Couvreur via ntg-context: The problem seems to come from pgfplots ... There was a message about the same by Gavin and an answer by Hans on 2022-12-30. Maybe the fix didn’t make it into the latest upload. no news from gavin so ... not added yet - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Tabulate \TH command not working in latest release
While typesetting a document containing a small tabulated table with the latest release I noticed that the tabulate \TH command hadn't added any vertical space between the rows. Here's a mwe. \starttext \starttabulate[|l|l|] \NC Γ \NC Gamma \NC\NR \NC Θ \NC Theta \NC\NR \TB[line] \NC Φ \NC Phi \NC\NR \stoptabulate \stoptext --- Michael ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] \autoinsertedspace fails
No change with the latest (2023.01.04).
Is this a problem with what I am doing, or a bug?
--
Rik
On 2022-12-29 19:12, Rik Kabel via ntg-context wrote:
Happy New Year all!
Following up on the problem with \autoinsertnextspace
(https://mailman.ntg.nl/pipermail/ntg-context/2022/107111.html) and
the new \autoinsertedspace that came from that report, I see that
there is still a problem, or perhaps a problem again after it was
previously repaired.
The following code, run under the latest (and recent previous)
version, produces an incorrect result, with no space inserted where
expected in many cases. As the first examples after \starttext show,
the problem appears to be with \autoinsertedspace, but perhaps I am
using it incorrectly in the macro as well.
\starttexdefinition unexpanded BD
\dodoublegroupempty
\doBD
\stoptexdefinition
\starttexdefinition doBD #1#2
\removeunwantedspaces\ % insert a space
(
\ifsecondargument
#1|–|#2
\else\iffirstargument
#1–
\else
{\red I NEED A DATE OR DATES!}
\fi\fi
)
\autoinsertedspace
\stoptexdefinition
\tt
\starttext
This\autoinsertedspace fails unexpectedly with autoinsertedspace.\par
This\autoinsertedspace \emph{fails unexpectedly} with
autoinsertedspace.\par
This\autoinsertnextspace works with autoinsertnextspace.\par
This\autoinsertnextspace \emph{fails} as expected with
autoinsertnextspace.\par
Saussure\BD{1857}{1913} works.\par
Saussure \BD{1857}{1913} \emph{works}.\par
Saussure \BD{1857}{1913}. Works.\par
Chomsky\BD{1928} fails with LMTX, works with MkIV.\par
Chomsky \BD{1928} \emph{fails with LMTX, works with MkIV}.\par
Chomsky \BD{1928}. Works.\par
\BD blah\par
\contextversion\ \texenginename
\stoptext
--
Rik
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist :ntg-context@ntg.nl /https://www.ntg.nl/mailman/listinfo/ntg-context
webpage :https://www.pragma-ade.nl /http://context.aanhet.net
archive :https://bitbucket.org/phg/context-mirror/commits/
wiki :https://contextgarden.net
__
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] TUG 2023
On 04/01/2023 16:50, Thomas A. Schmitz via ntg-context wrote: Hi everybody, an excellent year 2023 to all of you - I hesitate to say "it can only get better from 2022." That's what we thought last year, and boy were we wrong and did it get worse... Let's hope that this year will be more peaceful and less pandemic... But to my topic: the official announcement for TUG 2023 is out. It will be in Bonn, Germany, in a building literally (literally!) just across the street from my university office. So I feel somewhat motivated to go and give a talk on ConTeXt and spread the word. Since I'm a simple user and no developer, I'm a bit hesitant though: is any of the developers going (Hans?)? Since the public will be 99 % LaTeX-centric I think you need not be afraid there: there will be a decent amount of generic stuff and a good number of plain TeX experts, I suspect. Yes, LaTeX tends to be the most popular TeX flavour in the talks, but I think overall it's much more varied than you are imagining! Joseph ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Problem with latest version ?
Am 04.01.23 um 19:00 schrieb Fabrice Couvreur via ntg-context: The problem seems to come from pgfplots ... There was a message about the same by Gavin and an answer by Hans on 2022-12-30. Maybe the fix didn’t make it into the latest upload. Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TUG 2023
Hi Thomas, Am 04.01.23 um 17:50 schrieb Thomas A. Schmitz via ntg-context: an excellent year 2023 to all of you... The same to you! is any of the developers going (Hans?)? I’m not a dev but I’ll be there. Since the public will be 99 % LaTeX-centric: I had the idea of showing (off) how ConTeXt can typeset xml and produce different outputs from the same source (similar to what I've done in Bassenge in 2019). Those of you who have been to TUG conferences before: would that be of interest even to people who know little to nothing about ConTeXt yet are familiar with other forms of TeX? I guess I just what to get a feeling what to expect at a TUG conference. I’ve never been to a TUG conference, but it’s also a DANTE conference, and I wouldn’t hesitate to talk about ConTeXt – your example is a good one to get people interested, I think. I’ll probably show how I make our architectural guides for Bonn – I suggested to have a guided tour to one of the HICOG settlements (that were built for the American forces and their German employees) with the group that’s behind the guides (Werkstatt Baukultur Bonn). Since I’ll be there on company time (I’m now working for my former main customer), I’ll probably also help presenting our LaTeX3-based documentation workflow. Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Problem with latest version ?
The problem seems to come from pgfplots ... Le mer. 4 janv. 2023 à 17:35, Fabrice Couvreur a écrit : > > Hi, > I just installed the latest version of LMTX and also updated to texlive > 2022 and I get this error message which was not the case before. > Thank you. > Fabrice > > > Running `lmtX' on `complexes_2' with > ``/home/fabrice/LMTX/tex/texmf-linux-64/bin/mtxrun --autogenerate --script > context --autopdf --purgeall complexes_2'' > > resolvers | formats | executing runner 'run luametatex format': > /home/fabrice/LMTX/tex/texmf-linux-64/bin/luametatex > --jobname="./complexes_2.tex" > --fmt=/home/fabrice/LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt > --lua=/home/fabrice/LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui > --c:autopdf --c:currentrun=1 --c:fulljobname="./complexes_2.tex" > --c:input="./complexes_2.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:purgeall > --c:texmfbinpath="/home/fabrice/LMTX/tex/texmf-linux-64/bin" > system > > system > ConTeXt ver: 2023.01.04 11:35 LMTX fmt: 2023.1.4 int: > english/english > system > > system > 'cont-new.mkxl' loaded > open source > level 1, order 1, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' > system > beware: some patches loaded from cont-new.mkiv > close source> level 1, order 1, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' > system > files > jobname './complexes_2', input > './complexes_2.tex', result './complexes_2' > fonts > latin modern fonts are not preloaded > languages > language 'en' is active > open source > level 1, order 2, name './complexes_2.tex' > open source > level 2, order 3, name 'exercises.mkiv' > open source > level 3, order 4, name 'terminale-modules.tex' > open source > level 4, order 5, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv' > close source> level 4, order 5, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv' > fonts > symbols > library 'mvs' loaded > open source > level 4, order 6, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/colo-imp-xwi.mkiv' > close source> level 4, order 6, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/colo-imp-xwi.mkiv' > colors > system 'xwi' is loaded > modules > 'tikz' is loaded > open source > level 4, order 7, name > '/home/fabrice/LMTX/tex/texmf-context/tex/context/modules/mkxl/m-tikz.mkxl' > open source > level 5, order 8, name 'pgfutil-common.tex' > open source > level 6, order 9, name 'pgfutil-common-lists.tex' > close source> level 6, order 9, name 'pgfutil-common-lists.tex' > close source> level 5, order 9, name 'pgfutil-common.tex' > open source > level 5, order 10, name 'pgfutil-context.def' > close source> level 5, order 10, name 'pgfutil-context.def' > open source > level 5, order 11, name 'pgfrcs.code.tex' > close source> level 5, order 11, name 'pgfrcs.code.tex' > open source > level 5, order 12, name 'pgfsys.code.tex' > open source > level 6, order 13, name 'pgfkeys.code.tex' > open source > level 7, order 14, name 'pgfkeysfiltered.code.tex' > close source> level 7, order 14, name 'pgfkeysfiltered.code.tex' > close source> level 6, order 14, name 'pgfkeys.code.tex' > open source > level 6, order 15, name 'pgf.cfg' > close source> level 6, order 15, name 'pgf.cfg' > Driver file for pgf: pgfsys-pdftex.def > > open source > level 6, order 16, name 'pgfsys-pdftex.def' > open source > level 7, order 17, name 'pgfsys-common-pdf.def' > close source> level 7, order 17, name 'pgfsys-common-pdf.def' > close source> level 6, order 17, name 'pgfsys-pdftex.def' > close source> level 5, order 17, name 'pgfsys.code.tex' > open source > level 5, order 18, name 'pgfkeys.code.tex' > close source> level 5, order 18, name 'pgfkeys.code.tex' > open source > level 5, order 19, name 'pgfsyssoftpath.code.tex' > close source> level 5, order 19, name 'pgfsyssoftpath.code.tex' > open source > level 5, order 20, name 'pgfsysprotocol.code.tex' > close source> level 5, order 20, name 'pgfsysprotocol.code.tex' > open source > level 5, order 21, name 'pgfcore.code.tex' > open source > level 6, order 22, name 'pgfmath.code.tex' > open source > level 7, order 23, name 'pgfmathcalc.code.tex' > open source > level 8, order 24, name 'pgfmathutil.code.tex' > fonts > beware: no fonts are loaded yet, using 'lm mono' in box > close source> level 8, order 24, name 'pgfmathutil.code.tex' > open source > level 8, order 25, name 'pgfmathparser.code.tex' > close source> level 8, order 25, name 'pgfmathparser.code.tex' > open source
[NTG-context] TUG 2023
Hi everybody, an excellent year 2023 to all of you - I hesitate to say "it can only get better from 2022." That's what we thought last year, and boy were we wrong and did it get worse... Let's hope that this year will be more peaceful and less pandemic... But to my topic: the official announcement for TUG 2023 is out. It will be in Bonn, Germany, in a building literally (literally!) just across the street from my university office. So I feel somewhat motivated to go and give a talk on ConTeXt and spread the word. Since I'm a simple user and no developer, I'm a bit hesitant though: is any of the developers going (Hans?)? Since the public will be 99 % LaTeX-centric: I had the idea of showing (off) how ConTeXt can typeset xml and produce different outputs from the same source (similar to what I've done in Bassenge in 2019). Those of you who have been to TUG conferences before: would that be of interest even to people who know little to nothing about ConTeXt yet are familiar with other forms of TeX? I guess I just what to get a feeling what to expect at a TUG conference. All best wishes Thomas ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Problem with latest version ?
Hi, I just installed the latest version of LMTX and also updated to texlive 2022 and I get this error message which was not the case before. Thank you. Fabrice Running `lmtX' on `complexes_2' with ``/home/fabrice/LMTX/tex/texmf-linux-64/bin/mtxrun --autogenerate --script context --autopdf --purgeall complexes_2'' resolvers | formats | executing runner 'run luametatex format': /home/fabrice/LMTX/tex/texmf-linux-64/bin/luametatex --jobname="./complexes_2.tex" --fmt=/home/fabrice/LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=/home/fabrice/LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui --c:autopdf --c:currentrun=1 --c:fulljobname="./complexes_2.tex" --c:input="./complexes_2.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:purgeall --c:texmfbinpath="/home/fabrice/LMTX/tex/texmf-linux-64/bin" system > system > ConTeXt ver: 2023.01.04 11:35 LMTX fmt: 2023.1.4 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source> level 1, order 1, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname './complexes_2', input './complexes_2.tex', result './complexes_2' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './complexes_2.tex' open source > level 2, order 3, name 'exercises.mkiv' open source > level 3, order 4, name 'terminale-modules.tex' open source > level 4, order 5, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv' close source> level 4, order 5, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/symb-imp-mvs.mkiv' fonts > symbols > library 'mvs' loaded open source > level 4, order 6, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/colo-imp-xwi.mkiv' close source> level 4, order 6, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/base/mkiv/colo-imp-xwi.mkiv' colors > system 'xwi' is loaded modules > 'tikz' is loaded open source > level 4, order 7, name '/home/fabrice/LMTX/tex/texmf-context/tex/context/modules/mkxl/m-tikz.mkxl' open source > level 5, order 8, name 'pgfutil-common.tex' open source > level 6, order 9, name 'pgfutil-common-lists.tex' close source> level 6, order 9, name 'pgfutil-common-lists.tex' close source> level 5, order 9, name 'pgfutil-common.tex' open source > level 5, order 10, name 'pgfutil-context.def' close source> level 5, order 10, name 'pgfutil-context.def' open source > level 5, order 11, name 'pgfrcs.code.tex' close source> level 5, order 11, name 'pgfrcs.code.tex' open source > level 5, order 12, name 'pgfsys.code.tex' open source > level 6, order 13, name 'pgfkeys.code.tex' open source > level 7, order 14, name 'pgfkeysfiltered.code.tex' close source> level 7, order 14, name 'pgfkeysfiltered.code.tex' close source> level 6, order 14, name 'pgfkeys.code.tex' open source > level 6, order 15, name 'pgf.cfg' close source> level 6, order 15, name 'pgf.cfg' Driver file for pgf: pgfsys-pdftex.def open source > level 6, order 16, name 'pgfsys-pdftex.def' open source > level 7, order 17, name 'pgfsys-common-pdf.def' close source> level 7, order 17, name 'pgfsys-common-pdf.def' close source> level 6, order 17, name 'pgfsys-pdftex.def' close source> level 5, order 17, name 'pgfsys.code.tex' open source > level 5, order 18, name 'pgfkeys.code.tex' close source> level 5, order 18, name 'pgfkeys.code.tex' open source > level 5, order 19, name 'pgfsyssoftpath.code.tex' close source> level 5, order 19, name 'pgfsyssoftpath.code.tex' open source > level 5, order 20, name 'pgfsysprotocol.code.tex' close source> level 5, order 20, name 'pgfsysprotocol.code.tex' open source > level 5, order 21, name 'pgfcore.code.tex' open source > level 6, order 22, name 'pgfmath.code.tex' open source > level 7, order 23, name 'pgfmathcalc.code.tex' open source > level 8, order 24, name 'pgfmathutil.code.tex' fonts > beware: no fonts are loaded yet, using 'lm mono' in box close source> level 8, order 24, name 'pgfmathutil.code.tex' open source > level 8, order 25, name 'pgfmathparser.code.tex' close source> level 8, order 25, name 'pgfmathparser.code.tex' open source > level 8, order 26, name 'pgfmathfunctions.code.tex' open source > level 9, order 27, name 'pgfmathfunctions.basic.code.tex' close source> level 9, order 27, name 'pgfmathfunctions.basic.code.tex' open source > level 9, order 28, name
Re: [NTG-context] problem with Segoe Ui Symbol as fallback font
On 1/4/2023 2:29 PM, Jacob Kauffmann via ntg-context wrote: The problem is that now that \bf, \it and so on stopped working outside math mode. A workaround is to add \rm after \starttext. Maybe the developers can shed some light :) \definefontfeature[mathextra][moderntocalligraphic=yes] you can peek inti pagella-math.lfg and common-math.lfg fallbacks in math are sort of gone in lmtx as it's only asking for troubles but we can overlay from other fonts in lfg files 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] problem with Segoe Ui Symbol as fallback font
Am 04.01.23 um 14:29 schrieb Jacob Kauffmann via ntg-context: The problem is that now that \bf, \it and so on stopped working outside math mode. A workaround is to add \rm after \starttext. \setupbodyfont[mainface] Did you try \setupbodyfont[mainface,rm] ? Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] problem with Segoe Ui Symbol as fallback font
The problem is that now that \bf, \it and so on stopped working outside math
mode.
A workaround is to add \rm after \starttext.
Maybe the developers can shed some light :)
Please find MWE below.
Cheers,
Jacob
\definefontfallback[cal-fallback][name:modern][uppercasescript,lowercasescript]
\starttypescript[mainface]
\definetypeface[mainface][rm][serif][pagella][default]
\definetypeface[mainface][ss][sans] [modern] [default][rscale=1.075]
\definetypeface[mainface][tt][mono] [modern] [default][rscale=1.075]
\definetypeface[mainface][mm][math] [pagella][default][fallbacks=cal-fallback]
\stoptypescript
\definefontfamily[mainface][mm][mainface]
\definefontfamily[mainface][rm][pagella][bf=style:bold]
\usetypescript[mainface]
\setupbodyfont[mainface]
\startbuffer
The quick brown fox jumps over the lazy dog
\stopbuffer
\starttext
% \rm % works
{\rm \getbuffer}\par
{\ss \getbuffer}\par
{\tt \getbuffer}\par
{\bf \getbuffer}\par
{\it \getbuffer}\par
{\sl \getbuffer}\par
{\bi \getbuffer}\par
{\bs \getbuffer}\par
{\sc \getbuffer}
Should be Palatino: $x + y$ $f({\bi x})$
Should be Latin Modern: ${\cal I}$ $\mathcal{I}$ $\mathscr{I}$
\stoptext
signature.asc
Description: Message signed with OpenPGP
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] problem with Segoe Ui Symbol as fallback font
Hi Hraban,
I had a similar problem with math fallbacks (no errors, fallbacks not used) and
just found a solution.
Please find a small example below.
I don't understand why we need the line \definefontfamily, but it's necessary
for the fallbacks to work.
Also, it stops working when I do \setupbodyfont[mainface,rm].
Cheers,
Jacob
\definefontfallback[cal-fallback][name:modern][uppercasescript,lowercasescript]
\starttypescript[mainface]
\definetypeface[mainface][rm][serif][palatino][default]
\definetypeface[mainface][ss][sans] [modern] [default][rscale=1.075]
\definetypeface[mainface][tt][mono] [modern] [default][rscale=1.075]
\definetypeface[mainface][mm][math]
[palatino][default][fallbacks=cal-fallback]
\stoptypescript
\definefontfamily[mainface][math][]
\usetypescript[mainface]
\setupbodyfont[mainface]
\starttext
{\rm \input ward }
{\ss \input ward }
{\tt \input ward }
Should be Palatino: $x + y$
Should be Latin Modern: ${\cal I}$ $\mathcal{I}$ $\mathscr{I}$
\stoptext
signature.asc
Description: Message signed with OpenPGP
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] lmtx upload
Hi, I uploaded the first 2023 lmtx. There are not that many changes, most relate to updating manuals. Currently we're looking at the metafun / luametafun and lowlevel manuals - adding some accumulated todo's. Keep in mind that when we update manuals that is is not automatically reflected in new pdf's (processing happens outside the tree on temporary paths) and only occasionally I push back a pdf (when it looks ok). So, manual sources can be more up to date than manual pdfs. If you feel something (fundamental and stable) is missing you can let us know here. We gained some performance over the last month, mostly due to using different low level mechanisms (there are some more not yet widely used ones). The gain depends on (extreme) usage so quite likely most goes unnoticed unless one has many runs. After all, there are no fundamental changes in context, which is already reasonable optimized for ages (it's kind of a game to make it faster without obscuring the code, which is a criterium for rejection). As usual, (new and old) bugs will be fixed, 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Cron /var/www/aanhet.net/context/bin/cron/context-mirror
receiving incremental file list ./ ctan.lsr document-2.htm download-1.htm download-2.htm logo-ade.png logo-cts.png logo-pod.png rss.xml show-fil.pdf context/latest/ context/latest/cont-mpd.zip context/latest/cont-ppc.zip context/latest/cont-sci.zip context/latest/cont-tmf.zip context/latest/cont-tst.7z context/latest/cont-tst.tar.xz context/latest/cont-tst.zip general/manuals/ general/manuals/lowlevel-loops.pdf general/manuals/luametatex.pdf sent 109,300 bytes received 24,121,459 bytes 2,307,691.33 bytes/sec total size is 449,288,830 speedup is 18.54 Running archiver: New dir: /var/www/aanhet.net/context//htdocs/archives/context-2023-01-04.12 172294866 /var/www/aanhet.net/context//htdocs/archives/context-2023-01-04.12/latest 126745317 /var/www/aanhet.net/context//htdocs/archives/context-2023-01-04.12/current 18956262 /var/www/aanhet.net/context//htdocs/archives/context-2023-01-04.12/alpha 126707516 /var/www/aanhet.net/context//htdocs/archives/context-2023-01-04.12/beta 444708057 /var/www/aanhet.net/context//htdocs/archives/context-2023-01-04.12 444708057 total ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
