e 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, directives are more helpful, like
\enabledire
s)
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[logs.errors=*] (i.e. break at every error)
ction[state=start]
> >
> > \startbuffer[testdata]
> > @Book{knuth1,
> > author = {Donald E. Knuth},
> > title = {TEX and METAFONT. New directions in typesetting},
> > year = {1979},
> > publisher = {Addison-Wesley},
> > }
> > @Art
ther,
> author = {Some Person and Some Otherperson},
> title = {Another title},
> year = {1900},
> }
> \stopbuffer
>
> % enable tracing
> \enabletrackers[publications, publications.crossref,
> publications.details, publications.cite, publications.str
900},
}
\stopbuffer
% enable tracing
\enabletrackers[publications, publications.crossref, publications.details,
publications.cite, publications.strings]
\usebtxdataset[main][testdata.buffer]
\usebtxdefinitions[aps]
\setupbtx[dataset=main]
\definebtxrendering[bibrendering][aps][dataset=main]
% this seems to h
doesn't
render correctly:
%% renders as mm·Hg, not as mmHg
\unit{millimetermercury}
How to get millimetermercury render as mmHg? And “inch mercury”
render as inHg? I can't find “inchmercury” in phys-dim.lua, only
“millimetermercury”, should it be added?
Example:
%% \enabletrackers
, not as mmHg
\unit{millimetermercury}
How to get millimetermercury render as mmHg? And “inch mercury”
render as inHg? I can't find “inchmercury” in phys-dim.lua, only
“millimetermercury”, should it be added?
Example:
%% \enabletrackers [physics.units]
%% inch should render as “in”
%% \setupunittext
, ok. Since almfixed is based on Knuth's mono, perhaps its visuals of the
control characters can be extracted and used as fallback symbols.
Yes: For typeset text/printing visualization is generally unnecessary (the
point of this thread).
2. \enabletrackers[typesetters.nbsp] gives a colored
visualization (consistent across fonts) and even then
it would add some mess because we're talking of a mix of characters that
can have gone (as part of rendering) or are not characters at all but
spacing
so, in that case only 'verbatim' is a candidate for visualization, not
so much typeset te
ack font one uses, as long as it has no
control-character symbols.
1. Can this approach be generalized to get what we want, viz., a way to toggle
the symbols?
2. \enabletrackers[typesetters.nbsp] gives a colored box, which is at least
something.. But how can we get the NBSP symbol that's alerady
Xt, ZWJ and ZWJ appear as symbols, but NBSP does not.
Thank you in advance for your guidance.
\enabletrackers[typesetters.nbsp]
Many thanks, Hans. The method appears to work only for nbsp, not zwj etc. Here
is the updated MWE:
===
\startTEXpage[offset=1em]
\disabletrackers[typesett
oes not.
Thank you in advance for your guidance.
\enabletrackers[typesetters.nbsp]
Many thanks, Hans. The method appears to work only for nbsp, not zwj etc. Here
is the updated MWE:
===
\startTEXpage[offset=1em]
\disabletrackers[typesetters.directions]
\disabletrackers[typesetters.zwj]
\di
J:
NBSP:
\stopTEXpage
==
In Notepad, all three control characters can be turned on or off at once.
In Scintilla, only the NBSP appears and there is no option to toggle.
In ConTeXt, ZWJ and ZWJ appear as symbols, but NBSP does not.
Thank you in advance for your guidance.
\enab
Ok, I've found a solution.
%
\enabletrackers[graphics.conversion]
\startluacode
local function convert(oldname, newname)
os.execute(string.format(
'gm convert "%s" "%s"', oldname, newname)
)
end
-- Set the PDF, JPEG and def
On 8/9/2023 12:10 PM, denis.ma...@unibe.ch wrote:
Keith, you can also check hyphenations using a script:
-- check-hyphens.lua
--[[
analyze hyphenations based on a ConTeXt log file
enable hyphenation tracking in the ConTeXt file with
\enabletrackers[hyphenation.applied
Keith, you can also check hyphenations using a script:
-- check-hyphens.lua
--[[
analyze hyphenations based on a ConTeXt log file
enable hyphenation tracking in the ConTeXt file with
\enabletrackers[hyphenation.applied]
then run this script with
lua check-hyphens.lua
ConTeXt. I have tried searching for hyphens using
Skim and Adobe Acrobate viewers but although they find hyphenation in
line they don't recognise hyphens at the edge of lines.
Any help would be appreciated.
I suppose you would be disappointed it there was no tracker ...
\enab
help would be appreciated.
I suppose you would be disappointed it there was no tracker ...
\enabletrackers[hyphenation.applied.console]
\enabletrackers[hyphenation.applied.visualize]
you even get a file with the hyphenated words
You can see all of them with
\disabledirectives[backend.clean
\setpenalties\widowpenalties{1}{150}
\setpenalties\clubpenalties {1}{150}
\stopsetups
\setuplayout[
width=10cm,
topspace=0.5in,
backspace=2.0cm,
header=7.5mm,
footer=0.25in,
location={middle,middle},
vs=2,
grid=yes,
setups=mypenalties
]
%\enabletrackers[makeup]
%\enabletrackers[builders.hpack.quality
}
\setpenalties\clubpenalties {1}{150}
\stopsetups
\setuplayout[
width=10cm,
topspace=0.5in,
backspace=2.0cm,
header=7.5mm,
footer=0.25in,
location={middle,middle},
vs=2,
grid=yes,
setups=mypenalties
]
%\enabletrackers[makeup]
%\enabletrackers[builders.hpack.quality]
\enabletrackers[builders.hpack.overflow
Thanks Hans, that works now.
Best Wishes
Keith
On 11/07/2023 10:37, Hans Hagen wrote:
On 7/11/2023 11:11 AM, Keith McKay wrote:
Hi All
Using\enabletrackers[paragraphs.passes=summary] whilst doing some
testing causes a fatal error after first run but pdf is produced.
Here is the error
On 7/11/2023 11:11 AM, Keith McKay wrote:
Hi All
Using\enabletrackers[paragraphs.passes=summary] whilst doing some
testing causes a fatal error after first run but pdf is produced. Here
is the error message from the MWE:
in spac-pas.lmt in lines 156 and 158 you can change
classes
Hi All
Using\enabletrackers[paragraphs.passes=summary] whilst doing some
testing causes a fatal error after first run but pdf is produced. Here
is the error message from the MWE:
lua error:
run callback [6]: bad argument #2 to 'format' (number expected,
got nil)
stack traceback
27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
vz.pdf
Description: Adobe PDF document
\starttext
\startbuffer[vz-1]
\starttext
\showframe[text]
\enabletrackers
.net
__
_
% master000.tex – ConTeXt MkIV Module
\startproduct master000
\project iebpmonographs
\environment ieb-c-layout-000
\environment monograph-local-layout
\usemodule[statistical-charts]
% \enabletrackers[typesetters.suspects]
% \showbody
document. See this thread
https://mailman.ntg.nl/pipermail/ntg-context/2021/104286.html
from last year.
2. ConTeXt ignores the redefinition of predefined entities.
If you run this code:
\enabletrackers[xml.entities]
\xmltexentity{apos}{XXX}
itbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
>
> ___
>
Not by the computer, so cannot test, but I found these in an old document
of mine:
\enabletrackers[nodes.destinations]
\enabl
be overwritten by updates.
no, these files are always read runtime (when present); personally i
only use cont-loc fdor things like this:
\enablemode[atpragma]
\enablemode[*allfonts]
\enabletrackers[pages.timing]
% \enabletrackers[system.usage=summary]
and there is very little in cont-new while in
lementary]
%definecolor[dictionary:unary functional]
%definecolor[dictionary:unary linear algebra]
%definecolor[dictionary:unary logical]
%definecolor[dictionary:unary set]
%definecolor[dictionary:unary vector]
%mathdictproperties \plusone
\mathdictgroup \mathdefaultdictionary
\enabletrack
t; The format string uses "@" rather then "%", as % is normally scanned as
> a comment.
>
Thank you again, but the "0.0" remains unchanged. The only way I've been
able to succeed is with a for loop to label explicitly. See mwe below for
things I've attempted. The
xt.externalfigure("{cow.pdf}",{width="0.5\\textwidth"})
It is subtle, but you need:
context.externalfigure({“cow.pdf"},{width="0.5\\textwidth"})
A “lua table” becomes [] stuff, a “lua string” becomes {} stuff. Your original
resulted in
\externalfigure{{cow.pdf}}[width={
0\points% < BLACK BOX?
>> \starttext
>> \startcolumns[n=3]
>> % Overfull lines will have slugs in colum margins.
>> \input linden
>> % Underfull hboxes get no warning
>> x
>> \stopcolumns
>> \stoptext
> i'll check it .. looks like som
mns
\stoptext
i'll check it .. looks like some interference with normalization ..
actually one can enable more advanced tracers:
% \enabletrackers[builders.hpack.quality]
% \enabletrackers[builders.hpack.overflow]
H
On 1/9/2022 11:23 AM, hanneder--- via ntg-context wrote:
Thank god, we have many TeX fonts derived from older ones that still
work, but many entries in
the TeX Font Catalogue do not!
It's often not that bad when you use context ...
% \enabletrackers[*comp*]
\definefontfeature
]
\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
\setupbodyfont[lib-fb-jun]
{\em emph. lib-fb-jun
] [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
>
> \enabletrackers[fo
erif] [JunicodeRoman] [fallbacks=preferlibertine]
> \stoptypescript
>
> \starttypescript [jun-pr-lib]
> \definetypeface [jun-pr-lib] [rm] [serif] [jun-pr-lib] [default]
> \stoptypescript
>
>
> % some tracking stuff
>
> \enabletrackers[fonts.missing=replace]
> \enable
]
\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{"eec5} (three glyphs)}
lib-fb-jun: \Uchar
is ook wat nederlands;},
{net als dit.},
{Niet dat het veel te betekenen heeft.}
}
}]
\enabletrackers[synchronize]
\setupsynchronizecontent
[nl]
[language=nl,
style=\tx,
left={[},
right={]},
color=darkblue]
\placesynchronize
[parallel-en-nl]
[distance=1pt
t;> {\starttikzpicture#1\stoptikzpicture}
>>
>> \stopmodule
>>
>> \endinput
>>
>> --
>>
>> Message: 3
>> Date: Mon, 13 Dec 2021 23:56:42 +
>> From: Bruce Horrocks
ich can be in the current file or in an
> environment file).
>
> 6) Most times you will need to quit and restart TeXShop when you change any
> of the above.
>
>
> You *do not* need:
>
> 1)
ening when I try to jump from PDF to
> editor or vice versa?
>
> Q2: Is this the same error as reported at the bottom of
> https://wiki.contextgarden.net/SyncTeX ? Or has that been fixed?
>
> PS: \enabletrackers[system.synctex.visualize] works as ex
: \enabletrackers[system.synctex.visualize] works as expected - i.e. the
.synctex file seems to be correct.
—
Bruce Horrocks
Hampshire, UK
___
If your question is of interest to others as well, please add an entry
23, 1998, at 7:52 PM, U.S. Pacific
Standard Time, is represented by the string D:199812231952-08'00
A test program:
\enabletrackers[backend.info]
\enabledirectives[backend.date=1234-12-30]% 1234-12-30T00:00:00+02:00
\enabledirectives[backend.date=1234-12-3
local time.
EXAMPLE: For example, December 23, 1998, at 7:52 PM, U.S. Pacific
Standard Time, is represented by the string D:199812231952-08'00
A test program:
\enabletrackers[backend.info]
\enabledirectives[backend.date=1234-12-30]%
1234-12-30T00:00:00+02:00
ut. (Being Dutch I actually never used \IJ
> or \ij).
>
> Now, we can assume that when your languages needs characters with
> accents that you use a font that has them. In MKIV and LMTX one can
> enable a checker
>
> \enabletrackers[fonts.missing]
> \enabletrackers[fonts.
d
> >
> > \stopluacode
> >
> > \starttext
> > \ctxlua{thirddata.explanation()}
> > \stoptext
> >
> > The actual use case is more complicated (where I use templates, so I don't
> > want to convert everything to context.startformula() etc.). The exa
ent)
end
\stopluacode
\starttext
\ctxlua{thirddata.explanation()}
\stoptext
The actual use case is more complicated (where I use templates, so I don't want
to convert everything to context.startformula() etc.). The example compiles
with MkIV but not LMTX.
Any idea what is going on?
\enabletrack
)
\starttext
% \enabletrackers[system.randomizer.details]
% empty == default
\newrepeatablerandom\MyRandom {Welcome 2 America}
\newrepeatablerandom\MyRandomN{\randomnumber{0}{1000}}
\newrepeatablerandom\MyRandomM{\randomnumber{0}{1000}}
\cldcontext
]
\enabletrackers [typesetters.directions]
%\showmakeup [glue,dir]
\definepapersize [Testing]
[width=6.69in]
\setuppapersize [Testing]
\setuplayout [width=fit,
backspace=1.4in,
cutspace=1in
\starttext
\enabletrackers[localanchor]
\startoverlayMPgraphic{mp:whatever-6}
draw anchorcell (1,1) withpen pencircle scaled 1pt withcolor
"blue" ;
fill anchorspan (2,2) (3,5) withpen pencircle scaled 1pt withcolor
"yellow" ;
draw anchorcell (2,2)
, 3) withcolor "yellow" ;
fill anchorspan (3, 1) (3, 3) withcolor "green" ;
path p ; p := anchorcell (2, 2) ;
fill p withcolor "red" ;
% now some weird stuff:
picture q ; q := externalfigure "t:/sources/cow.pdf" ;
q := q xysized (bbwid
zations). The format file is also
smaller (esp when you take into account that the mkiv one is zip
compressed and the lmtx one isn't).
But ... your problem was not related to the above.
The next upload will also mention detailed mem usage in the log file. If
you want to see how your docum
rry [reference count=32767]
This is not the normal memory consumption that bothers you
\enabletrackers[system.usage]
will show you more detail. Normally the default context configuration
will provide enough. In lmts memory is abit more dynamic so we start otu
smaller and then stepwise grow. And one
in the ConTeXt file with
\enabletrackers[hyphenation.applied]. Then, you can run the script with
lua check-hyphens.lua input_file whitelist.ending
As we assume .log for the input_file, the input file should be supplied without
file ending. For the (optional) whitelist a file ending has
ontext/base/mkiv/lpdf-pdx.xml'
only \enabletrackers[resolvers.details] adds the information "file not
readable", likely without any real effect.
I'm getting different results on windows and linux in more complex setup
and "file not readable" was the only difference in log files
On 4/10/2021 4:54 PM, Jano Kula wrote:
Hello Hans,
more specific resolver now:
\enabletrackers[resolvers.details]
\starttext
Readable?
\stoptext
On Sat, Apr 10, 2021 at 3:29 PM Hans Hagen <mailto:j.ha...@xs4all.nl>> wrote:
On 4/10/2021 3:10 PM, Jano Kula wrote:
&g
Hello Hans,
more specific resolver now:
\enabletrackers[resolvers.details]
\starttext
Readable?
\stoptext
On Sat, Apr 10, 2021 at 3:29 PM Hans Hagen wrote:
> On 4/10/2021 3:10 PM, Jano Kula wrote:
>
> > resolvers > resolving > file 'type-imp-loc.mkxl' is not read
On 4/10/2021 3:10 PM, Jano Kula wrote:
Hello,
updated lmtx (ver: 2021.04.09 19:59 LMTX), paths updated, etc.
\enabletrackers[resolvers.*]
\starttext
Readable?
\stoptext
shows in log some file are "not readable":
resolvers > resolving > file 'type-imp-loc.mkxl' is not re
Hello,
updated lmtx (ver: 2021.04.09 19:59 LMTX), paths updated, etc.
\enabletrackers[resolvers.*]
\starttext
Readable?
\stoptext
shows in log some file are "not readable":
resolvers > resolving > file 'type-imp-loc.mkxl' is not readable
resolvers > resolving
Well, see attached.
Interestingly, it does with \mainlanguage[de]. But, not for \language[de]
\enabletrackers[hyphenation.applied.visualize]
\startexceptions[de]
au{f-}{f}{ff}as-sen
\stopexceptions
\mainlanguage[de]
\starttext
auffassen
\language[en]
auffassen
\language[de]
auffassen
On 3/22/2021 12:11 PM, denis.ma...@ub.unibe.ch wrote:
Besides, is it intentional that this here will suppress the ff ligature?
---
\enabletrackers[hyphenation.applied.visualize]
\startexceptions[de]
au{f-}{f}{ff}as-sen
auf\zwnj fasste
>
> when not hyphenated (without the () the third one is the replacement)
So, what's the advantage of using
au{f-}{f}{ff}(f\zwnj f)as-ste
over
au{f-}{f}{ff}as-ste
if any?
Besides, is it intentional that this here will suppress the ff ligature?
?
the lookup is using the third argument, the replacement is the fourth
auffasste => auf\zwnj fasste
when not hyphenated (without the () the third one is the replacement)
\enabletrackers[hyphenation.applied.visualize]
\startexceptions[de]
au{f-}{f}{ff}as-ste
au{f-}{f}{ff}(f!f)ax-
On 3/19/2021 9:49 PM, denis.ma...@ub.unibe.ch wrote:
Wow, Hans, that looks awesome. Thanks a lot.
This is a nice example:
\setuplayout[tight]
\usebodyfont[modern]
\usebodyfont[pagella]
\usebodyfont[ebgaramond]
\usebodyfont[dejavu]
% \enabletrackers[hyphenation.applied]
\enabletrackers
o one can find where it's
documents because no one expects it).
Anyway, a pre-weekend distaction:
\starttext
\enabletrackers[hyphenation.applied]
\enabletrackers[hyphenation.applied.console]
\dontcomplain \dostepwiserecurse{0}{15}{1}{
{\advance\hsize -#1cm \input tufte \par} }
\stoptext
This
raph and it's not worth the trouble of keeping track of /
analyzing that detail (as usual all can be done but these are features that
hardly anyone uses, get forgotten and probably no one can find where it's
documents because no one expects it).
Anyway, a pre-weekend distaction:
\s
bably no one can find
where it's documents because no one expects it).
Anyway, a pre-weekend distaction:
\starttext
\enabletrackers[hyphenation.applied]
\enabletrackers[hyphenation.applied.console]
\dontcomplain \dostepwiserecurse{0}{15}{1}{
{\advance\hsize -#1cm \input tufte \par}
> pack quality> oeps.tex [ - 0011] : underfull hbox : m
> pack quality> oeps.tex [ - 0012] : underfull hbox : mm
> pack quality> oeps.tex [ - 0013] : underfull hbox : mmm
>
> pack quality> stop
>
> using the already available mechanism
> oeps.tex [ - 0010] : overfull hbox : m
pack quality> oeps.tex [ - 0011] : underfull hbox : m
pack quality> oeps.tex [ - 0012] : underfull hbox : mm
pack quality> oeps.tex [ - 0013] : underfull hbox : mmm
pack quality> stop
using the already avai
\luametatex\wincon\wincon.dll
(mtxrun --generate)
maybe
\enabletrackers[resolvers.libraries]
gives you a clue
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt
On Wed, 2021-02-24 at 15:49 +0100, Taco Hoekwater wrote:
> > On 24 Feb 2021, at 10:42, Christoph Hintermüller <
> > christ...@out-world.com> wrote:
> >
> > Hi
> > What command line parameters, trackers etc I should activate when i
>
> There is
&g
> On 24 Feb 2021, at 10:42, Christoph Hintermüller
> wrote:
>
> Hi
> What command line parameters, trackers etc I should activate when i
There is
\enabletrackers[export.*]
Best wishes,
Taco
—
Taco Hoekwater E: t...@bittext.nl
genderflui
O 12647-2:2004)},
intent={PSO Uncoated ISO12647 ECI},
]
\stopmode
\enabletrackers[backend.pdfx]
\stopenvironment
signature.asc
Description: PGP signature
___
If your question is of interest to others as well,
; them but nowadays that's the job of a font handler (script language control).
> We can keep them but assume them legacy. They normally don't belong in input.
> (Being Dutch I actually never used \IJ or \ij).
>
> Now, we can assume that when your languages needs characters with
ters with
accents that you use a font that has them. In MKIV and LMTX one
canenable a checker
\enabletrackers[fonts.missing]\enabletrackers[fonts.missing=replace]\e
nabletrackers[fonts.missing=remove]
but in LMTX it's upgraded with more clever replacements (Jano will
document that + more about ch
when your languages needs characters with
accents that you use a font that has them. In MKIV and LMTX one can
enable a checker
\enabletrackers[fonts.missing]
\enabletrackers[fonts.missing=replace]
\enabletrackers[fonts.missing=remove]
but in LMTX it's upgraded with more clever replacements (Jano will
e1.pgf
> t-filter> output file : tikztemp/example1.pgf.pdf
> ...
> system > 13: filename=img/example1.pgf foundname=img/example1.pgf
> fullname=.../img/example1.pgf usedmethod=direct
>
> Looks like ConTeXt can find the file, but the filter module
for ideas.
Already there for ages ... testsuite goodies-002.tex + demo.lfg shows
how to color your special characters ... one of the probably many
unknown features -)
There's also this:
\enabletrackers[fonts.missing=replace]
\startTEXpage
Jano uses \char 12345.
\stopTEXpage
and of course you
=.../img/example1.pgf usedmethod=direct
Looks like ConTeXt can find the file, but the filter module cannot.
--trackers=resolvers.schemes (or \enabletrackers) doesn’t change anything WRT
log/output.
Since this fails already, I don’t know if \processFILTERfile also uses
bufferbefore/-after (it s
in
.../lmtx/tex/texmf-local/metapost
This seems to work ok here, if not, can you see what the trackers report?
=== oeps.tex ===
\starttext
\usepath[mptest]
% \enabletrackers[resolvers*]
\startMPpage
% readfile(runscript("mp.string(resolvers.find_file('oeps.mp'))")) ;
% readfile
category {demo} unicode 105 \relax % rather low level
for now
\registerboxglyph category {demo} unicode 106 \relax % rather low level
for now
\definefontfeature[whatever][box=demo]
\definedfont[Serif*whatever]
% \enabletrackers[fonts.collecting]
\startTEXpage%[offset=0pt]
%\hbox{g
Thanks Hans!
I had forgotten about \enabletrackers[metapost.tracingall].
Best Wishes
Keith
On 07/01/2021 15:35, Hans Hagen wrote:
On 1/7/2021 4:11 PM, Keith McKay wrote:
In the MWE below I would expect the "show" command to print the value
of p in the console output (I us
p +2)*cm, (p + 2)*cm)
withcolor red ;
endfor;
StopPage;
\stopMPpage
\stoptext
\enabletrackers[metapost.tracingall]
but best use:
message(p);
-
Hans Hagen | PRAGMA ADE
Ri
d question: is it possible to get the MetaPost code that (I
think) the SVG gets translated to? I'm interested in how it looks
like.
\enabletrackers[metapost.svg.result]
but i have a fix that does clipping
in the test suite (sections/bookmarks-*.tex)
>
> You can specify bookmarks when you use \startsection etc an dalso add them
> any place to named lists.
Thanks Hans - I never thought to look in the test cases (d'oh!).
For the benefit of those searching the archives in the future, here is
n context is quite ok but for instance
> messing with node lists will always come at a cost (crossing the c
> boundary and such)
>
> - pdf: the backend code in luametatex is somewhat slower than in
> luatex but we're gaining there (because in related areas we can do
> thin
rall ConTeXt "computation"?
basic typesetting (hyphenation, font handling): takes a bit of time,
extra features that you use add some too: some timings are reported
after a run so you get an idea
par building: unles hz is used, quite fast
page building: fast but depending on what feature
.
It does here (not that i have a lib to test) so maybe check your path:
.../tex-context/tex/texmf-win64/bin/lib/luametatex/foo/libfoo.dll
(put the file there and run mtxrun --generate)
The lua versions should match and there shopuld be the initialer function.
\enabletrackers[*lib*]
gives some
the text, so the first thought is: is the italics
font setup correct? I would try italics in the main text or using
context default font. You can try \enabletrackers[publications.*] and
\enabletrackers[fonts.*] to see in log what's going on. If it doesn't
help a minimal working example
at the PDF (knowing nothing about bibliographies), I can't see
any italics in the text, so the first thought is: is the italics font setup
correct? I would try italics in the main text or using context default
font. You can try \enabletrackers[publications.*] and
\enabletrackers[fonts.*] to see in l
work:
\definefontfallback[mainface][rm][Symbola][preset=range:playingcards,force=yes]
\definefontfamily[mainface][rm][LibertinusSerif]
\enabletrackers[fonts.missing]
\setupbodyfont[mainface]
\starttext
Testing!
\stoptext
The PLAYING CARD ACE OF SPADES character does not show up in the output
PDF
():
>
> \starttext
>
> \showframe
>
> \enabletrackers[math.toysymbol]
>
> \definemathtoysymbol[Plus] [bin][+]
> \definemathtoysymbol[Minus][bin][-]
> \definemathtoysymbol[Equal][rel][=]
>
> $\dorecurse{199} {
> x_{#1} \ifodd#1\relax\Plus\else\Minus\fi
> }
\showframe
\enabletrackers[math.toysymbol]
\definemathtoysymbol[Plus] [bin][+]
\definemathtoysymbol[Minus][bin][-]
\definemathtoysymbol[Equal][rel][=]
$\dorecurse{199} {
x_{#1} \ifodd#1\relax\Plus\else\Minus\fi
} x_{200} \Equal n$
\blank
\dorecurse{10} {
test \discretionary
t can I do with \tracingall and
\enabletrackers[*].
Which is the meaning of error number 139? It might help me to know what
I should be looking at.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If y
seemed to
> happen randomly.
>
> you can try to run with
>
> \tracingall
>
> and/or
>
> \enabletrackers[*]
>
> and see where it crashes
>
> Hans
>
>
the future). And by doing so I recognized this error, which seemed
>to
>> happen randomly.
>you can try to run with
>
>\tracingall
>
>and/or
>
>\enabletrackers[*]
>
>and see where it crashes
>
>Hans
>
>
>
-version (to see if I need to change them
in the future). And by doing so I recognized this error, which seemed to
happen randomly.
you can try to run with
\tracingall
and/or
\enabletrackers[*]
and see where it crashes
Hans
For some strange reason, \comment isn’t added when there is no other
content in the paragraph.
I think it might be a bug. Could anyone confirm this?
Why is everything a bug?
Some elements like margin blocks or register entries need an anchor.
\enabletrackers[typesetters.margindata]
\starttext
ful that ConTeXt could translate XML
+ environments to ConTeXt sources.
\enabletrackers[context*]
in the xml setups that you use, something \xmlshow{#1} will give you a
clue of what you're dealing with
H
1 - 100 of 427 matches
Mail list logo
