[export=yes,xhtml=yes]
\setupexport
[svgstyle=mathtest-style,
hyphen=yes,
width=60em]
the next upload will support the hyphen option (was disabled in lmtx
although we can actually do it there too)
\enabledirectives[export.css.hyphens=yes]
\enabledirectives[export.css.textwidth=100em
=mathtest-style,
hyphen=yes,
width=60em]
\enabledirectives[export.css.hyphens=yes]
\enabledirectives[export.css.textwidth=100em]
\starttext
\placefigure
[force]
[figure:crc2]
{Hacker}
{\externalfigure[hacker.jpg][width=.6\textwidth,
alternativetext={
A lot of math: $\int_0^\infty e^{-x^2
sys.mkxl one can chaneg this:
\enforced\let\newcontextversion\gobbleoneargument
fwiw, \enforced is like \aliased (inherits all properties) but only is
permissive when used in the format file
begin example
%\enabledirectives[overloadmode=error]
\definehighlight [Important] [styl
the line number of the warning in the log in one line off:
csname overload > warning, protection level 3, control sequence
'Important', properties 'frozen instance protected', file './context
128.tex', line 13
01 begin example
02 %\enabledir
gnore the mention of \newcontextversion (something Hans
should put in overloadmode) you should take a look at the \starttitle
warning.
begin example
%\enabledirectives[overloadmode=error]
\definehighlight [Important] [style=bold]
\definehighlight [Unimportant] [style=italic]
\starttex
Wed, 2 Jul 2025 at 01:38, Matthias Weber
wrote:
> You can try
>
>
> \enabledirectives [backend.usetags=testing]
> \setuptagging [state=start]
> \setupstructure [state=start]
> \setupbackend [format=PDF/A-3a]
> % \setupbackend [format=pdf/ua-1]
>
> \setupinteraction [page=y
You can try
\enabledirectives [backend.usetags=testing]
\setuptagging [state=start]
\setupstructure [state=start]
\setupbackend [format=PDF/A-3a]
% \setupbackend[format=pdf/ua-1]
\setupinteraction [page=yes,
menu=on
Thanks, Pablo (and everybody else reading this),
I should have put my question differently. When using the math.textblobs
tracker, this code:
\enabledirectives [backend.usetags=testing]
\setuptagging[state=start]
\setupstructure[state=start]
\setupbackend
[format=PDF/A-3a]
\setupbackend
below)?
I can do this manually, but my figures contain quite a bit of math, and it
would be nice if alternate text for math is provided consistently throughout
the document.
Thanks,
Matthias
\usemodule[mathml]
\enabledirectives [backend.usetags=testing]
\setuptagging[state=start
tives; fwiw: i've been running the highest level of protection
already for years now (error mode) .. you can try \enabledirectives
[overloadmode=error] at the top of your file to see how badly you behave
-- a few fixes here and there (related to mailing list questions and
reports
he highest level of protection already for years now
(error mode) .. you can try \enabledirectives [overloadmode=error] at
the top of your file to see how badly you behave
-- a few fixes here and there (related to mailing list questions and
reports); nothing spectacular
-- some preparations w
:
\setupbackend
[format={pdf/a-2a},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}]
\setuptagging
[state=start]
\enabledirectives
[backend.usetags=mkiv]
Specification: ISO 19005-2:2011, Clause: 6.2.4.3, Test number: 3
DeviceCMYK shall only be used if a device independent DefaultCMYK
]
\enabledirectives
[backend.usetags=mkiv]
Specification: ISO 19005-2:2011, Clause: 6.2.4.3, Test number: 3
DeviceCMYK shall only be used if a device independent DefaultCMYK colour
space has been set or if a DeviceN-based DefaultCMYK colour space has
been set when the DeviceCMYK colour
:
|\setupbackend[format={PDF/UA-1}] \setuptagging[state=start]
\enabledirectives[backend.usetags=crap] \startluacode
lpdf.injectxmpinfo("xml://rdf:RDF","1",false) \stopluacode |
Many thanks for the code, Rik.
Just in case anyone intends to use any form of TDM reservation, it
}] \setuptagging[state=start]
\enabledirectives[backend.usetags=crap] \startluacode
lpdf.injectxmpinfo("xml://rdf:RDF","1",false) \stopluacode |
Many thanks for the code, Rik.
Just in case anyone intends to use any form of TDM reservation, it seems
that it might break PDF/A validatio
-archive.com/ntg-context@ntg.nl/msg64956.html> and inserted
> it successfully as follows:
>
>
> \setupbackend[format={PDF/UA-1}]
> \setuptagging[state=start]
> \enabledirectives[backend.usetags=crap]
> \startluacode
> lpdf.injectxmpinfo("xml://rdf:RDF"
list at https://www.mail-
>> archive.com/ntg-context@ntg.nl/msg64956.html and inserted it
>> successfully as follows:
>>
>> |\setupbackend[format={PDF/UA-1}] \setuptagging[state=start]
>> \enabledirectives[backend.usetags=crap] \startluacode
>> lpdf.injectxmpinfo(&
On 5/1/25 00:02, Rik Kabel wrote:
> [...]
> I took the route described in the mailing list at https://www.mail-
> archive.com/ntg-context@ntg.nl/msg64956.html and inserted it
> successfully as follows:
>
> |\setupbackend[format={PDF/UA-1}] \setuptagging[state=start]
&
Many thanks for the reference.
> Perhaps ConTeXt could introduce something similar where invisible
> pages or invisible layers of nonsense are auto-generated but can't
> be seen on screen or when a document is printed?
There is something similar (Hans already mentioned it):
\enabledir
successfully as follows:
|\setupbackend[format={PDF/UA-1}] \setuptagging[state=start]
\enabledirectives[backend.usetags=crap] \startluacode
lpdf.injectxmpinfo("xml://rdf:RDF","xmlns:tdm='http://www.w3.org/ns/tdmrep/'>1"
2025.04.28 14:29):
\enabledirectives [backend.usetags=testing]
\setuptagging[state=start]
\setupstructure[state=start]
\setupbackend
[format=PDF/A-3a]
\setupbackend[format=pdf/ua-1]
\setupexternalfigures[location=default]
\starttext
\externalfigure[hacker][label={this is an image
0250427 + ConTeXt LMTX 2025.04.28 14:29):
>>
>> \enabledirectives [backend.usetags=testing]
>> \setuptagging[state=start]
>> \setupstructure[state=start]
>> \setupbackend
>>[format=PDF/A-3a]
>> \setupbackend[format=pdf/ua-1]
>> \setupexternalfigur
Dear All,
I am starting a new thread as requested.
I can confirm that
>
> the following should work with current latest (from yesterday,
> LuaMetaTeX 2.11.07 20250427 + ConTeXt LMTX 2025.04.28 14:29):
>
> \enabledirectives [backend.usetags=testing]
> \setupt
in german) that is the background for this
> announcement: https://bfsg-gesetz.de/ <https://bfsg-gesetz.de/>
Hi Steffen,
the following should work with current latest (from yesterday,
LuaMetaTeX 2.11.07 20250427 + ConTeXt LMTX 2025.04.28 14:29):
\enabledirectives [backend.usetags=tes
parent.dict.Alt = pdfunicode(label ~= "" and label or "image")
>
> And it should work for PDF/UA-1. Please, don’t forget that I don’t use
> math in ConTeXt at all (only for these testings).
>
> Source for the attached PDF document:
>
> \enabledi
= pdfunicode(label ~= "" and label or "image")
And it should work for PDF/UA-1. Please, don’t forget that I don’t use
math in ConTeXt at all (only for these testings).
Source for the attached PDF document:
\enabledirectives [backend.usetags=testing]
\setups
Thanks Pablo,
I don’t understand how to do this.
The following compiles, but I don’t think the label made it into the pdf.
\enabledirectives [backend.usetags=crap]
\setuptagging[state=start]
\setupstructure[state=start]
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966
gt;
>
>
> /Mikael
>
>
> On Thu, Apr 10, 2025 at 7:58 PM Matthias Weber
> wrote:
>>
>> Dear All,
>>
>>
>> Following the instructions in tagging.pdf,
>>
>> I tried
>>
>> \setupbackend[format=pdf/ua-2]
>> \setuptaggi
backend[format=pdf/ua-2]
> \setuptagging[state=start]
>
> \enabledirectives [backend.usetags=crap]
>
> \registermathsymbol[default][en][ z ][the variable]
> \registermathsymbol[default][en][ k ][the index]
>
>
> \starttext
> \startformula
> \startalign
> \NC \left|(z_0+h)^
Dear All,
Following the instructions in tagging.pdf,
I tried
\setupbackend[format=pdf/ua-2]
\setuptagging[state=start]
\enabledirectives [backend.usetags=crap]
\registermathsymbol[default][en][ z ][the variable]
\registermathsymbol[default][en][ k ][the index]
\starttext
\startformula
you can forget this thread in favour of “Alternate text for images?”.
I was ignorant when I started the thread that there was:
\enabledirectives [backend.usetags=crap]
This was the way to avoid the use of the right tagging for PDF/UA-1.
I hope it i
be PDF document
\enabledirectives [backend.usetags=testing]
\setuptagging[state=start]
\setupstructure[state=start]
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
level=0]
\setupbackend[format=pdf/ua-1]
\setupexternalfigures[location=default]
\starttext
\externalfigure[cow][label
AM, Matthias Weber wrote:
>>> [...]
>>> in order to provide screen readability (but the above doesn’t
>>> work, the PDF doesn’t have the alternate text).
>>
>> This one will add an Alt to the element
>>
>>\externalfigure[cow][label={this is a
lfigure[cow][label={this is a cow}]
Matthias,
this should work:
\enabledirectives [backend.usetags=crap]
\setuptagging[state=start]
\setupstructure[state=start]
\setupbackend
[format=PDF/A-3a,
intent=sRGB IEC61966-2.1,
level=0]
\setupbackend[format=pdf
On 4/7/25 22:23, Hans Hagen wrote:
> On 4/5/2025 9:05 AM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> At least, the validator only complains for the use of /DocumentFragment
>> (unknown to PDF-1.7).
>
> I think that (cf the tagging.pdf manual)
>
> \enabl
\externalfigure[cow][label={this is a cow}]
\stoptext
At least, the validator only complains for the use of /DocumentFragment
(unknown to PDF-1.7).
I think that (cf the tagging.pdf manual)
\enabledirectives [backend.usetags=crap]
should work and one can define ones own mappings
BTW
,prefix=no]
\startbuffer[text]
\quote{Welcome to my website} \cite[smith2025].
\stopbuffer
\savebuffer[list=text,file=text.tex,prefix=no]
\starttext
\setupinteraction[state=start,color=black]
\environment bib_env
\enabledirectives[hyphenators.urls.packslashes]
\sethyphenate
Dear list,
I’m struggling with an alternative list setup:
\showframe
\setupinteraction
[state=start,
style=,
focus=standard]
\enabledirectives[references.border=red]
\definelistalternative
[pmcols] [renderingsetup=pmcol]
\startsetups [pmcol]
\ifnum
Dear list,
I have the following sample:
\starttext
\showframe
%\setuppapersize[A5]
\setupinteraction
[state=start,
color=,]
\enabledirectives[references.border=darkgreen]
\definestructureconversionset[rom][n,R]
\protected\def\doPageNumber#1%
{#1\narrownobreakspace
},
]
\setuptagging
[state=start]
\enabledirectives
[backend.usetags=mkiv]
\starttext
a
\stoptext
is green with VeraPDF!
Many thanks for your testing, Thomas.
format={pdf/ua-2} is not defined I think, see: https://
source.contextgarden.net/tex/context/base/mkiv/lpdf-fmt.lua
It’s
On 2/16/25 11:09, Thomas Meyer wrote:
> \setupbackend[
> format={pdf/ua-1},
> profile={default_rgb.icc,default_gray.icc},
> ]
>
> \setuptagging
> [state=start]
>
> \enabledirectives
> [backend.usetags=mkiv]
>
> \starttext
> a
> \stoptext
>
&
\setupbackend[
format={pdf/ua-1},
profile={default_rgb.icc,default_gray.icc},
]
\setuptagging
[state=start]
\enabledirectives
[backend.usetags=mkiv]
\starttext
a
\stoptext
is green with VeraPDF!
format={pdf/ua-2} is not defined I think, see:
https://source.contextgarden.net/tex
; >>> even more crap .. let's wait till abbreviations are completely
>>> forbiddeb
>>> >>> (and also units and such )
>>> >> From what I see, /E may be helpful (similar to /ActualText).
>>> >
>>> > Imo it's useless:
>>
>> I think this may be a requirement for text-to-speech conversions.
>>> >>>
>>> >>> even more crap .. let's wait till abbreviations are completely forbiddeb
>>> >>> (and also units and such )
>>> >> From w
;> > (2) after that it is suposed to be known
>> > (3) if one jumps into a document in the middle one cannot expect it to be
>> > repeated every time
>> > (4) if that *is* expoected there is no need to use abbreviations at all
>> > (5) so, why should a '
nown
>> > (3) if one jumps into a document in the middle one cannot expect it to
>> be repeated every time
>> > (4) if that *is* expoected there is no need to use abbreviations at all
>> > (5) so, why should a 'read out' document have all abbreviations with an
&g
r me, the real problem with accessibility (and penalties for
> >> non-accessible documents) is that it will force all documents to be
> >> machine-readable (so we have to feed AI with all our public documents,
> >> whether we like it or not).
> >
> > i as
to use abbreviations at all
>> > (5) so, why should a 'read out' document have all abbreviations with an
>> expanded meaning and a typeset text not
>> >
>> >> For me, the real problem with accessibility (and penalties for
>> >> non-acc
nts) is that it will force all documents to be
> >> machine-readable (so we have to feed AI with all our public documents,
> >> whether we like it or not).
> >
> > i assume that such a machine learning or pattern recognotion app can
> quite well figure out t
and a typeset text not
>
>> For me, the real problem with accessibility (and penalties for
>> non-accessible documents) is that it will force all documents to be
>> machine-readable (so we have to feed AI with all our public documents,
>> whether we like it or n
gt; >> viewerprefix=\romanpage -,
> >> ]
> >>
> >> \dorecurse {6} \ipsum
> >>
> >> \stoptext
> >> ```
> >>
> >> In section 2, pages are shown with roman numerals in the document and
> as (roman numerals)-(arabic numer
> (roman numerals)-(arabic numerals) in the outline with Okular and Evince. I
>> don't know how to get only the first part, though.
>>
>> Best regards,
>> Florent
>>
>> Le mar. 24 sept. 2024 à 17:20, Shiv Shankar Dayal
>> a écrit :
>>>
gt; Florent
>
> Le mar. 24 sept. 2024 à 17:20, Shiv Shankar Dayal <
> shivshankar.da...@gmail.com> a écrit :
>
>> > Did you try a different PDF viewer? The display of the PDF outline
>> > probably depends on the viewer.
>>
>> I used Evince and Okular(I a
obably depends on the viewer.
>
> I used Evince and Okular(I am on Linux) and both work for LaTeX
> generated pdfs.
>
> > Maybe try
> > \enabledirectives[references.bookmarks.preroll]
> > or
> > \setupheads[expansion=yes]
>
> T
> Did you try a different PDF viewer? The display of the PDF outline
> probably depends on the viewer.
I used Evince and Okular(I am on Linux) and both work for LaTeX
generated pdfs.
> Maybe try
> \enabledirectives[references.bookmarks.preroll]
> or
> \setupheads[expansion=ye
outline
probably depends on the viewer.
Maybe try
\enabledirectives[references.bookmarks.preroll]
or
\setupheads[expansion=yes]
I’m not sure if the numbering of bookmarks is related to expansion of
their text.
Hraban
machine learning or pattern recognotion app can
quite well figure out that it's an abbreviation
I mean, no such as "\enabledirectives[backend.pdf.nounicode=❌]" allowed.
well, everything is allowed ... after all why do we typeset and
visualize otherwise ... it depends on the audience
ine-readable (so we have to feed AI with all our public documents,
whether we like it or not).
I mean, no such as "\enabledirectives[backend.pdf.nounicode=❌]" allowed.
Pablo
___
If your question is of interest
ou cna try this:
\setupinteraction
[title=TITLE,
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
\setupbackend
[format={pdf/a-2a},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}]
\setuptagging
[state=start]
\enabledirectives
[backe
ction
[title=TITLE,
subtitle=SUBTITLE,
author=AUTHOR,
keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}]
\setupbackend
[format={pdf/a-2a},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}]
\setuptagging
[state=start]
\enabledirectives
[backend.usetags=mkiv]
\starttext
\ch
Hans provided me with a patch that allows
\enabledirectives[system.dumpfiles=json]
It will be in the next update, I guess.
I’m using it with the new tool "addtogit.py"
in https://codeberg.org/fiee/context-tools
to add all files that are necessary for a
ConTeXt job to the current git
Am 20.07.24 um 10:04 schrieb Hans Hagen:
subconscious you know the answer:
look at the log file
Not only sub*; I forgot to mention I’d like to avoid parsing that.
of course you can also try
\enabledirectives[system.dumpfiles=lua]
and stare at the resulting job log file (jlg)
Thank
les"
of course you can also try
\enabledirectives[system.dumpfiles=lua]
and stare at the resulting job log file (jlg)
(the default is xml but i noticed some empty entries in there ... a very
old feature so i need to travel back in time now)
if files are missi
={two}] \getbuffer
\stopTEXpage
\startTEXpage[offset=1ts] \setupstacking[criterium={one,two}] \getbuffer
\stopTEXpage
\stoptext
-- support for more private pdf
\enabledirectives[backend.pdf.nounicode=noai]
\enabledirectives[backend.pdf.nounicode=nopilot]
\enabledirectives[backend.pdf.noun
erpret the page stream for
urls).
Anyway, a next upload will have this:
% \disabledirectives[backends.references.descriptions] % just link
% \enabledirectives [backends.references.descriptions] % some
detail (some todo) (default)
% \enabledirectives [backends.referenc
Dear list,
I have the following source:
\setupbodyfont[dejavu, sans, 24pt]
\setupinteraction[state=start, style=, color=,
contrastcolor=, display=new]
\enabledirectives[references.border=darkgreen]
\def\myurl#1%
{{\tt\goto{\hyphenatedurl{#1}}[url(#1)]}}
\protect
On 6/10/24 17:49, vm via ntg-context wrote:
> Is there a parameter for context lmtx to strip all metadata from the
> generated pdf?
> Or is that a better task for exiftool afterwards?
\enabledirectives[backend.date=none]
But this doesn’t remove all metadata.
Title, Producer and XMP d
t; to send the errors to
another file for careful study? (using Linux if that matters)
You can enable trackers like
\enabletrackers[figures.*]
But that just gives more log messages for debugging.
You get the list of all trackers with:
context --global m-trackers.mkiv
For your use case, direct
reful study? (using Linux if that matters)
You can enable trackers like
\enabletrackers[figures.*]
But that just gives more log messages for debugging.
You get the list of all trackers with:
context --global m-trackers.mkiv
For your use case, directives are more helpful, like
\enabledirectives[lo
On Mon, 19 Feb 2024 09:45:03 +0800
黄复雄 wrote:
> I recommend you to always show missing font markers in PDF documents
> with \replacemissingcharacters
Or let context throw an error in case a font/char is missing:
%% alternative:
%% context --errors='*'
\enabledirecti
mands,
\enabledirectives[overloadmode=error] % or warning
can give you some protection
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel
poor explanation of the issue.
Wanting to give a minimal sample, I didn’t add my full interaction setup:
\setupinteraction
[state=start,
style=,
color=,
contrastcolor=,
display=new,
focus=standard]
\enabledirectives
[references.border=darkgreen]
I
f the issue.
Wanting to give a minimal sample, I didn’t add my full interaction setup:
\setupinteraction
[state=start,
style=,
color=,
contrastcolor=,
display=new,
focus=standard]
\enabledirectives
[references.border=darkgreen]
I wanted to be able to setup the i
On 10/12/2023 3:14 PM, Pablo Rodriguez wrote:
Hi Hans,
I have the following source, which tries to resemble three kinds of links:
\setupinteraction[state=start, style=, focus=standard]
\def\inone#1{%
\start\setupinteraction[color=darkgreen]%
\enabledirectives
Hi Hans,
I have the following source, which tries to resemble three kinds of links:
\setupinteraction[state=start, style=, focus=standard]
\def\inone#1{%
\start\setupinteraction[color=darkgreen]%
\enabledirectives[references.border=darkgreen]%
\goto{#1}[url(#1)]\stop
]
\enabledirectives[references.border=darkgreen]
\starttext
\startTEXpage[offset=1dk]
\attachment[method=hidden, file=a(b).pdf]
\stopTEXpage
\stoptext
The name in EmbeddedFiles is "a\(b\).pdf".
Sorry for the obscure question, but how can I access this with
"\goto{link
Dear list,
I have the following source:
\setupinteraction[state=start, display=new]
\enabledirectives[references.border=darkgreen]
\starttext
\startTEXpage[offset=1dk]
\attachment[method=hidden, file=a(b).pdf]
\stopTEXpage
\stoptext
The name in EmbeddedFiles is "a\(b\
a bit more readable
If you load the module in lmtx you get an error on \checkparameters
which is not available in lmtx (here \ifparameters is a primitive)
because \doifelseassignment is the real tester (checkparameters is more
an mkii thing).
However, when you \enabledirectives[overloadmode=
aid that \in{attachment}[foobar] doesn‘t generate a link in your
sample.
Or do you get a link border from the following source?
\setupinteraction[state=start]
\enabledirectives[references.border=green]
\starttext
\startTEXpage[offset=1em]
\attachment[
file={hacker.jpg},
m
is:
>>>> \def\HOME{myhome}
>>>> \writestatus{1}{\meaning\HOME}
>>>> \letfrozen\HOME
>>>> \writestatus{2}{\meaning\HOME}
>>>> \def\HOME{other home}
>>>> \writestatus{3}{\meaning\HOME}
>>>> 
>>&

Is this mechanism broken? It looks so useful to prevent accidental redefinition!
here i run with
\enabledirectives[overloadmode=error]
(you can do that in cont-sys.mkxl)
\enabledirectives[overloadmode=warning]
Hans
Pity. Now I get on loading the tex file:
"csname overload >
home}
>> \writestatus{3}{\meaning\HOME}
>> 
>> Is this mechanism broken? It looks so useful to prevent accidental
>> redefinition!
>
> here i run with
>
> \enabledirectives[overloadmode=error]
>
> (you can do that in cont-sys.mkxl)
>
> \enabledi
ms to contradict this:
\def\HOME{myhome}
\writestatus{1}{\meaning\HOME}
\letfrozen\HOME
\writestatus{2}{\meaning\HOME}
\def\HOME{other home}
\writestatus{3}{\meaning\HOME}

Is this mechanism broken? It looks so useful to prevent accidental redefinition!
here i run with
\enabledirec
>> LuaTeX+MKIV, probably because there is code to fallback to other fonts?)
> and if you want to quit:
>
> \enabledirectives[logs.errors=missing characters]
Ok, this is useful.
I looked around, but I couldn't find a similar feature for w
d if you want to quit:
\enabledirectives[logs.errors=missing characters]
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 4
On 10/19/2022 3:01 AM, Max Chernoff via ntg-context wrote:
Hi Hans,
When running in \normalizelinemode=0, the \parinitleftskip and
\parinitrightskip nodes are either nonexistant or invisible from Lua,
causing tex.linebreak to not work correctly.
This sample file:
\enabledirectives
Hi Hans,
When running in \normalizelinemode=0, the \parinitleftskip and
\parinitrightskip nodes are either nonexistant or invisible from Lua,
causing tex.linebreak to not work correctly.
This sample file:
\enabledirectives[system.callbacks.permitoverloads]
\normalizelinemode=0
Hans Hagen via ntg-context writes:
> Hi,
>
> does (the obsolete)
>
> \enabledirectives[backend.pdf.forcecidset]
>
> help
No; same blank page. :(
(Also MKIV works without CIDSet...)
I looked into /StemV 0 (which was different in MKIV) but that works
with the TTF files,
Hi,
does (the obsolete)
\enabledirectives[backend.pdf.forcecidset]
help
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038
On 8/26/2022 3:00 AM, Max Chernoff wrote:
Hi Hans,
On Thu, 2022-08-25 at 08:57 +0200, Hans Hagen wrote:
On 8/25/2022 2:19 AM, Max Chernoff via ntg-context wrote:
But ... you can already do
\enabledirectives[logs.errors=*]
or
\enabledirectives[logs.errors=missing modules]
Didn't know
On 8/26/2022 3:00 AM, Max Chernoff wrote:
Hi Hans,
On Thu, 2022-08-25 at 08:57 +0200, Hans Hagen wrote:
On 8/25/2022 2:19 AM, Max Chernoff via ntg-context wrote:
But ... you can already do
\enabledirectives[logs.errors=*]
or
\enabledirectives[logs.errors=missing modules]
Didn't know
Hi Hans,
On Thu, 2022-08-25 at 08:57 +0200, Hans Hagen wrote:
> On 8/25/2022 2:19 AM, Max Chernoff via ntg-context wrote:
> But ... you can already do
>
> \enabledirectives[logs.errors=*]
>
> or
>
> \enabledirectives[logs.errors=missing modules]
Didn't know about
cuments that currently
work, but I think that this change is worth it, since I'd rather have
something break loudly (throwing an error) rather than silently (producing
a semi-corrupt document).
But ... you can already do
\enabledirectives[logs.errors=*]
or
\enabledirectives[logs.errors=miss
ry much. If there is not any other tool it seems that there
are no errors.
> The following will not report missing tags but will find other
> common issues and report them on the console:
>
> context --errors='*'
I guess this is equal to
\enabledirectives[logs.errors]
Wit
typescript
\starttypescript [jun-pr-lib]
\definetypeface [jun-pr-lib] [rm] [serif] [jun-pr-lib] [default]
\stoptypescript
% some tracking stuff
\enabletrackers[fonts.missing=replace]
\enabledirectives[logs.errors]
% text, we use lib-fb-jun first, then jun-pr-lib
\starttext
\setupbod
ipt
>
> \starttypescript[serif] [jun-pr-lib] [name]
> \definefontsynonym [Serif] [JunicodeRoman] [fallbacks=preferlibertine]
> \stoptypescript
>
> \starttypescript [jun-pr-lib]
>\definetypeface [jun-pr-lib] [rm] [serif] [jun-pr-lib] [default]
> \stoptypescript
>
> %
ib] [name]
>\definefontsynonym [Serif] [JunicodeRoman] [fallbacks=preferlibertine]
> \stoptypescript
>
> \starttypescript [jun-pr-lib]
> \definetypeface [jun-pr-lib] [rm] [serif] [jun-pr-lib] [default]
> \stoptypescript
>
>
> % some tracking stuff
>
> \enabletrac
-lib] [rm] [serif] [jun-pr-lib] [default]
\stoptypescript
% some tracking stuff
\enabletrackers[fonts.missing=replace]
\enabledirectives[logs.errors]
% text, we use lib-fb-jun first, then jun-pr-lib
\starttext
\setupbodyfont[lib-fb-jun]
{\em emph. lib-fb-jun: \Uchar61125 \char64259 \utfchar{"e
On Thu, 18 Nov 2021 19:27:25 +0100
Marco Patzer via ntg-context wrote:
> Is there a way to return failure if *any* error is encountered or
> do they need to be enabled each individually?
A solution is to use patterns (supported in the upcoming upload):
\enabledirectives
[logs.
tting the last run and if there are still
unresolved issues, it could then report the correct return value to
the environment. The runner is responsible for the final return
value, not the individual context run AFAIK.
> you need to be explicit:
>
> \enabledirectives [logs.errors={missi
1 - 100 of 347 matches
Mail list logo
