4:43 PM, Aditya Mahajan via ntg-context wrote:
>> On Mon, 2 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
>>> Hi,
>>>
>>> How can I check if a buffer or block has content (or is empty) before a
>>> \useblocks or \getbuffer statement?
>>>
&
On 8/2/2021 4:43 PM, Aditya Mahajan via ntg-context wrote:
On Mon, 2 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
Hi,
How can I check if a buffer or block has content (or is empty) before a
\useblocks or \getbuffer statement?
I would like to typeset a headline only if the buffer
On Mon, 2 Aug 2021, Benjamin Buchmuller via ntg-context wrote:
> Hi,
>
> How can I check if a buffer or block has content (or is empty) before a
> \useblocks or \getbuffer statement?
>
> I would like to typeset a headline only if the buffer/block has been used in
> a p
Hi,
How can I check if a buffer or block has content (or is empty) before a
\useblocks or \getbuffer statement?
I would like to typeset a headline only if the buffer/block has been used in a
particular section and want to avoid headlines with empty sections.
Thanks!
Benjamin
But currenntly the dimensions can't be zero.
Many thanks for your code update, Michal.
I’m extremely interested in investigating the possibilities this opens.
But I’m afraid that I will have other things to do first. It will take
me months to come back to this again.
> Hans, I would om
n take as
granted. But currenntly the dimensions can't be zero.
Hans, I would omit the check for 0 dimensions of rendering window (as
already noted in the source, it is useful for sound). See patch below.
Michal Vlasák
--- a/tex/context/base/mkxl/lpdf-wid.lmt
+++ b/tex/context/base/mkxl/
On 7/28/2021 10:12 PM, Wolfgang Schuster wrote:
2. Rather than adding a additional argument to \starttyping etc. provide
a \startnamedtyping with a mandatory argument with the name of the
instance.
ok, but i do need to check the before/after wrt setup
To save a few lines of code a flag (e.g
st }
lists[last] = data
lists[name] = data
trees[last] = list
return data
end)
lists[v_reset].attribute = unsetvalue -- so we discard 0
-- todo: glue kern attr
local function add(root,word,replacement)
local processor, replacement = splitprocessor(replacement,true) -- no check
replac
organizations, passing the
>
> Acrobat accessibility checker is a prerequisite, so it seems worthwhile
>
> to me to make ConTeXt capable of it.
>
> Most fo this is rather trivial but we need examples (mwe) and expected
> result (in only have an old acrobat x pro and the lat
On 7/27/2021 1:20 PM, Michal Vlasák wrote:
I thought that recent Edge versions used Chrome's PDFium, as you say
with some additions (like drawing). I would have to double check that.
yes but i think with their own additions (not sure about the pdf stuff)
i do notice differences in pri
ective can also
> confuse viewers
I thought that recent Edge versions used Chrome's PDFium, as you say
with some additions (like drawing). I would have to double check that.
From what I tried, from the tested viewers only Acrobat seemed to do
something with the double sided
orthwhile
to me to make ConTeXt capable of it.
Most fo this is rather trivial but we need examples (mwe) and expected
result (in only have an old acrobat x pro and the latest reader, so
maybe i can&
nnotations a problem
the command line program qpdf is one of the best programs to check (when
luigi sand i were checking luatex pdf issues we used qpdf and mupdf mostly)
Now to the different mechanisms:
1) Sound objects
- First appeared in PDF 1.2 (1996), but had since been deprecated (P
or JavaScript for
more control over the media playback.
Acrobat and Foxit both use Windows Media Player for playing the video.
Both support controls, but behave differently -- Acrobat displays the
controls outside of the multimedia annotation, Foxit within...
As if it wasn't enough there is
> Am 25.07.2021 um 12:17 schrieb Hans Hagen :
>
> On 7/25/2021 9:46 AM, Wolfgang Schuster wrote:
>
>> There is no mode value for LMTX, only MkIV is set. To check for LMTX
>> you have to use \ifcase\contextlmtxmode but an additional for lmtx
>> would be useful.
&
On 7/25/2021 9:46 AM, Wolfgang Schuster wrote:
There is no mode value for LMTX, only MkIV is set. To check for LMTX
you have to use \ifcase\contextlmtxmode but an additional for lmtx
would be useful.
i'll add an lmtx
{*lmtx}{lmtx}
I always get „mkiv“.
I’ve tried
- pre LMTX context
- LMTX --luatex
- LMTX (2021.07.23)
What is the recommended way to detect LMTX?
There is no mode value for LMTX, only MkIV is set. To check for LMTX
you have to use \ifcase\contextlmtxmode but an additional for lmtx
would be useful
data={\citizenshipdatatwo},
xlabels={\yearlabelsone}]
\stoptext
you need to put the modules under
tex/texmf-modules/tex/context/third/mkiv/statcharts
or so, and run 'mtxrun --generate' to updat ethe file database
(i didn't check of there was a module package
0, userpage 20, subpage 20
pages > flushing realpage 21, userpage 21, subpage 21
...
I stopped counting at 200,
Cheers,
Michael
On Thu, Jul 22, 2021 at 1:14 PM Henning Hraban Ramm wrote:
> columnsets need \setuplayout[grid=yes] – did you check that?
>
> HR
>
> > Am
columnsets need \setuplayout[grid=yes] – did you check that?
HR
> Am 22.07.2021 um 12:42 schrieb Michael Guravage :
>
> No, I'm afraid not. I have been combining the various table and column
> environments, all without success - yet.
>
> Michael
>
>
>
&g
tribute{#1}{ancestor::div[@class='section level1 hidden']}{id}}
{yes}{no}\blank
\stopxmlsetups
\starttext
\xmlprocessbuffer{main}{test}{}
\stoptext
I need to check whether the link is inside the same div or not.
I know how to obtain the destination identifier (\xmlref
many changes
>>> since MkII.
>>
>> So, just for confirmation that I understand this correctly, I need to simply
>> change the command from texexec to context --luatex and fix all settings in
>> my setup until I get it working again?
>
> I guess so. I don’t
>> You will probably need to update several setups, there were many changes
>> since MkII.
>
> So, just for confirmation that I understand this correctly, I need to simply
> change the command from texexec to context --luatex and fix all settings in
> my setup unti
e is some issue.
According to my tests LMTX doesn't work like you describe it should.
i'll check it
(in retrospect tex could better have enforced a suffix and not fallback
on .tex but i suppose the usage scenarios were hard to foresee let alone
the restart-the-program-time-penalty when you f
On 7/7/2021 10:13 PM, Marco Patzer wrote:
But maybe Hans can chime in and clarify.
I have to check it but syffixes and tex are kind of special. It has
nothing to do with operating systems (sorry for those who love to bash
windows for it). Personally I always use a suffix and don't look
bin ... will a 5 year old
installation update?); of course users can also decide to completely do
it themselves (check out etc) but for a local project-specific run one
doesn't want all those gigs
So, each approach has pros and cons, and we need to preven
ven
> though
> I define \startEndnote. This causes issues with the linter (mtxrun --script
> check
> ) but seems otherwise harmless.
>
> I am sure that others more versed in ConTeXt can find some ways to fix this
>
define \startEndnote. This causes issues with the linter
(mtxrun --script check ) but seems otherwise harmless.
I am sure that others more versed in ConTeXt can find some ways to fix
this and improve the overall approach. I welcome suggestions
news, there is now an abstracts page with lots of talk topics added
>> by Hans himself. Check that out as well!
>
> In other news the early bird deadline in the table header row on the linked
> page is 11th July.
You are not even the first person to p
form today or at the very
> last
> tomorrow, if you want to be eligible for the early bird discount.
>
> https://meeting.contextgarden.net/
>
> In other news, there is now an abstracts page with lots of talk topics added
> by Hans himself. Check that out as well!
In
ike a list entry, with page numbers
and so?
indeed
And, something seems to e wrong with the numbering of the notes:
The endnote marks in the text are correct.
i need to check that, we actually need a dedicated list handler
early bird discount.
https://meeting.contextgarden.net/
In other news, there is now an abstracts page with lots of talk topics added
by Hans himself. Check that out as well!
https://meeting.contextgarden.net/2021/abstracts.shtml
Finally: this year for the first time we do have a (small
ontext] new upload lmtx
>
> On 6/18/21 11:46 PM, Hans Hagen wrote:
> > Hi,
> >
> > End of the week so time to wrap up.
> > [...]
> > (2) (Pablo:) There is some progress with facing floats that Thomas
> > will check out for real usage. So, still experimenta
x if HOSTNAME is not known (did that change?)
> > > > -- on sunos always (does anyone know an env var?)
> > > > -- on freebsd always (does anyone know an env var?)
> > > >
> > > >
> > >
> -- on freebsd always (does anyone know an env var?)
> >
> >
> > Tbh I don't know. I'm on Ubuntu 20.04 and I haven't made any
> important
> > changes on the OS. In case it helps, only the latest LMT
gt; > -- on freebsd always (does anyone know an env var?)
> > >
> > >
> > > Tbh I don't know. I'm on Ubuntu 20.04 and I haven't made any
> > important
> > > changes on the OS. In case it helps, only the
e any important
> > changes on the OS. In case it helps, only the latest LMTX produces this
> > error.
> >
> > (the 'rb' looks suspicious ... i'll check that)
> what does
>
> echo $HOSTTYPE
>
>
The same as uname -m: x86_64
> repor
the OS. In case it helps, only the latest LMTX produces this
error.
> (the 'rb' looks suspicious ... i'll check that)
>
> Hans
>
> -
>Hans Hagen | PRAGMA ADE
&
freebsd always (does anyone know an env var?)
(the 'rb' looks suspicious ... i'll check that)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt |
f-context/scripts/context/lua/mtxrun.lua':
> > No existe el archivo o el directorio
> > cp: no se puede efectuar `stat' sobre
> >
> '/home/coragyps/lmtx/tex/texmf-context/scripts/context/lua/mtx-install.lua':
>
> > No existe el archivo o el directo
text/scripts/context/lua/mtx-install.lua':
>
> > No existe el archivo o el directorio
> >
> > Messages in Spanish say the directory or file doesn't exist. Am I
> > missing something? Thanks in advan
t' sobre
'/home/coragyps/lmtx/tex/texmf-context/scripts/context/lua/mtx-install.lua':
No existe el archivo o el directorio
Messages in Spanish say the directory or file doesn't exist. Am I
missing something? Thanks in advance
can you check what is missing by adding a pr
On 6/18/21 11:46 PM, Hans Hagen wrote:
> Hi,
>
> End of the week so time to wrap up.
> [...]
> (2) (Pablo:) There is some progress with facing floats that Thomas will
> check out for real usage. So, still experimental.
Excellent news, Hans.
Many thanks for your work, Hans
}\par}
{\addff{uppercasing} \samplefile{tufte}\par}
{\addff{lowercasing} \samplefile{tufte}\par}
{\addff{primes} 123'345''\par}
\stopTEXpage
\stoptext
(2) (Pablo:) There is some pogress with facing floats that Thomas will
check out for real usage. So, sti
; nothing
> > > to do with signatures.
>
> Here is a description:
> https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#search=4.35
> (link should work with Firefox).
Thanks a bunch! I wonder why PDF 2.0 still isn't uploaded there, but
probably it'
ry, objects is a very special term in PDF parlance. It has nothing
>> to do with signatures.
Here is a description:
https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#search=4.35
(link should work with Firefox).
But you might check yourself with the following sample:
\set
nput file 't-pgf.tex' is not found, quitting
mtx-context | fatal error: return code: 256
> The same error in LMTX. The error in Tex Live 2021 is:
>
> tex error > tex error on line 48 in file
> /usr/local/texlive/2021/texmf-
> di
I'll also be using
>> \definefontfamily [praise][serif][junicode]
>> but, the above min via behavior I couldn't get to work at live.contextgarden
>
> You need proper quotation mark (as shown in my example below) sand not
> ". Another option is to use the \quot
ve min via behavior I couldn't get to work at live.contextgarden
You need proper quotation mark (as shown in my example below) sand not
". Another option is to use the \quotation command and enable the
protrusion option for (see \setupquotation).
When you have a text with a lot of
ent's logging to trace a problem and
realize that \writeline is gone mute -
that is, the output of subsequent logging lines now gets joined up in
the same line, very hard to read...
i'll check it
___
If your
runtime, thereby providing an excellent
place for hacks,
%D patches, extensions and new features. There can be local
overloads in cont-loc
%D (which has always been the case) and experimental code in
cont-exp (which is also
%D so old that I need to remind myself to check it
hacks,
%D patches, extensions and new features. There can be local
overloads in cont-loc
%D (which has always been the case) and experimental code in
cont-exp (which is also
%D so old that I need to remind myself to check it occasionally, so
here is the
%D reminder).
I tried
.. we probably first have to
check if we need to add some to the xml definitions
(btw, the lmt metapost commands i.e. the key/value macros fit in well in
the optional argument appeoach, the more low level ones more resemble
the low level context commands for which we have specific definitions)
On 5/28/2021 6:05 PM, Werner Hennrich wrote:
Hello everyone,
I'm looking into my environment's logging to trace a problem and realize
that \writeline is gone mute -
that is, the output of subsequent logging lines now gets joined up in
the same line, very hard to read...
i&#
\usemodule[newmml]
> > \starttext
> > \xmlprocessdata{}{
> >
> >E
> >
> > π
> >
> >
> > }{}
> > \stoptext
> >
> > The π symbol does not show in red.
> Kind of trivial ... i'll send you a patched mo
On 5/27/2021 6:30 PM, Duncan Hothersall wrote:
Apologies Hans.
MWE:
\usemodule[newmml]
\starttext
\xmlprocessdata{}{
E
π
}{}
\stoptext
The π symbol does not show in red.
Kind of trivial ... i'll send you a patched module.
If you want you can check with the sta
that we can do better. This and the above are reasons to come
up with a variant memory model that permits playing with additional
features more easily. The existing storage model is stil there (after
all it's tex) but for those willing to check the alternative, in
page-ins.mkxl one can unco
the above are reasons to come up
with a variant memory model that permits playing with additional
features more easily. The existing storage model is stil there (after
all it's tex) but for those willing to check the alternative, in
page-ins.mkxl one can uncomment
% \insertmode\plustwo
On 5/26/2021 7:17 PM, Pablo Rodriguez wrote:
On 5/25/21 6:20 PM, Hans Hagen wrote:
[...] but for those willing to check the alternative, in
page-ins.mkxl one can uncomment
% \insertmode\plustwo
Many thanks for the new upload, Hans.
I’m extremely interested in testing this.
How can we
On 5/25/21 6:20 PM, Hans Hagen wrote:
> [...] but for those willing to check the alternative, in
> page-ins.mkxl one can uncomment
>
> % \insertmode\plustwo
Many thanks for the new upload, Hans.
I’m extremely interested in testing this.
How can we enable this feature in a perma
Hi,
I uploaded a new version of lmtx. Apart from some small fixes, the
configuration file is hopefully okay too. I'm sure MF will check it.
However, the biggest change is hidden. In traditional tex, inserts (used
for footnotes) are implemented using a quadruple of registers. In
co
the function
> definition follow a different route ... basically one that can follow
> \the; I suppose that I can also make 'property' a valid usage (alias)
>
> (btw often features like this are described in articles or wrapups inm
> documents in the distribution or even mentioned
es.implement
local context = context
local drawme_code = 6
local drawing = [==[
draw fullcircle scaled 10mm;
draw fullcircle shifted up scaled 5mm;
draw fulltriangle shifted (up+1/2right) scaled 5mm;
]==]
local function chicken(value)
if value == "value" or value == drawme_code then
no need
;mtx-context.lua' message. Does this mean my
'path' command didn't work (and why not? It should have) or do I still need to
run a setup before I try to compile?
You don't say which Linux you are using so I would first check to see that
/home/me/bin/context/tex/texmf-lin
Not pedantic, just correct. I should have said Linux Mint 21! I'll check
the status of mtxrun but I thought all that would be automatic
On Sun, 23 May 2021, 5:54 pm Bruce Horrocks, wrote:
> On 23 May 2021, at 07:52, jbf wrote:
> >
> > Someone will quickly clarify what I
un a setup before I try to compile?
You don't say which Linux you are using so I would first check to see that
/home/me/bin/context/tex/texmf-linux-64/bin/mtxrun
is executable.
I assume that you followed the instructions on the wiki page here?
<https://wiki.contextgarden.net/Instal
hs} is modeled after \type{visualizepaths} from
%D \filename{mp-tool}.
def sketchypaths =
let draw = sketchdraw ;
let fill = sketchfill ;
enddef ;
%D Check if \filename{mp-tool} is loaded
if not known context_tool :
let normaldraw = draw;
let normalfill = fill;
def naturalizepaths =
-context | main context file:
/usr/local/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2021.05.19 18:22
hm, maybe some missing file or so .. i'll check it
—generate
context —make
context —version still showed ver. 2021.04.29
when I ran
sh install.sh
again, the result was the same. The version installed was still 2021.04.29
Any suggestion to fix this?
maybe some hickup in th eupload ... will check tomorrow
On 5/19/2021 6:49 PM, Thomas A. Schmitz wrote:
On 19.05.21 18:34, Hans Hagen wrote:
Can you check the latest upload? You should be able to go way higher.
Yes, with 2021.05.19 18:22, the file compiles again in lmtx! I'm also
trying your suggestions for improving the Lua code and rethi
On 19.05.21 18:34, Hans Hagen wrote:
Can you check the latest upload? You should be able to go way higher.
Yes, with 2021.05.19 18:22, the file compiles again in lmtx! I'm also
trying your suggestions for improving the Lua code and rethinking my
tables for analyzing the vocabulary.
rry [reference count=32767]
Can you check the latest upload? You should be able to go way higher.
If you're worried about your lua macros performance you can always run
with:
--profile
and look at the luatex-profile.log file ... it gives a rough impression.
be prepared for a slow run (alth
Sorry for the disturbance…
> irr texshoip has soem setting for it (you need to check with Dick) which
> relates to a change in synctex
>
> anyway, this whole synctex thing is a mess ... it's rather bound to the way
> latex does things and way to complex due to these heuristi
ut not allowed in
> > Type2 where the limit is at 48.
>
> a rather low limit right from the start (we can assume only rrcurveto is
> affected)
>
> > It would be great if ConTeXt could check for this and insert additional
> > rrcuveto operators when necessary to avoid this
see for yourself. Sorry for the disturbance…
> irr texshoip has soem setting for it (you need to check with Dick)
> which relates to a change in synctex
It works just fine. Add this line at the top of your document:
% !TEX useOldSyncParser
I also have:
\setupsynctex[state=start,method=min
the right location
in the source file.
Has something changed in the way synctex used to work ?
Below I am sending you a test file with its PDF and .synctex files, for you to
see for yourself. Sorry for the disturbance…
btw, maybe you can check with texshop for the version ... there was at
some
the right location
in the source file.
Has something changed in the way synctex used to work ?
Below I am sending you a test file with its PDF and .synctex files, for you to
see for yourself. Sorry for the disturbance…
irr texshoip has soem setting for it (you need to check with Dick) which
ke draw and fill sketchy
%D ...
%D naturalizepaths; % Restore the value of draw and fill
%D ...
%Dendfig
%D \stoptyping
%D
%D The code is heavily inspired by Hans Hagen's Metafun macros.
%D
%D The macro \type{sketchypaths} is modeled after \type{visualizepaths} from
%D \filename{m
ketchy
%D ...
%D naturalizepaths; % Restore the value of draw and fill
%D ...
%Dendfig
%D \stoptyping
%D
%D The code is heavily inspired by Hans Hagen's Metafun macros.
%D
%D The macro \type{sketchypaths} is modeled after \type{visualizepaths} from
%D \filename{mp-too
at 48.
a rather low limit right from the start (we can assume only rrcurveto is
affected)
It would be great if ConTeXt could check for this and insert additional
rrcuveto operators when necessary to avoid this issue.
after some experiments ... attached
(no upload yet as i'm renaming some
nTeXt could check for this and insert additional
rrcuveto operators when necessary to avoid this issue.
hm, i can try but not today -)
Additionally we got a report that inkscape 1.0 seems to be incompatible
with the way commmands are passed to it for SVG files. Hendrik Seliger
suggested t
Type2 CharString is invalid. The CFF2 CharStrings of this
glyph invokes the rrcurveto operator with 63 arguments, which is
allowed in CFF2 where the argument limit is 513, but not allowed in
Type2 where the limit is at 48.
It would be great if ConTeXt could check for this and insert additional
rrcuveto oper
ss. :(
>> Also, it is a bit of a shame that the XXX-webfont.ttf has postscript glyph
>> names that map to the
>> online cheat sheet, but these names are not preserved in the tma file (at
>> least not in my lmtx
>> version). Keeping those would make the
ping those would make the whole typset-a-specific-glyph procedure
be a lot less
error-prone, at least.
i suppose you noted the message -)
can you confirm / check that we can safely assume zero length names to
be okay?
local length = readbyte(f)
%OWNPATH%tex\texmf-%PLATFORM%\bin" /M
)
)
)
rem EOF
Another possibility would be to define CONTEXT_HOME as an unexpanded value
added to both the system environment variables and the PATH variable. For
example (haven't tried it):
setx CONTEXT_HOME "%OWNPATH%tex\texmf-%PLATFORM%\bin
On 5/9/2021 6:09 PM, Pablo Rodriguez wrote:
On 5/9/21 4:40 PM, Hans Hagen wrote:
On 5/8/2021 7:55 PM, Pablo Rodriguez wrote:
I wonder whether this might be caused by a bug or the code should be
adapted to current latest.
hm, i'll check it ... looks like some lua closure side effect
On 5/9/21 4:40 PM, Hans Hagen wrote:
> On 5/8/2021 7:55 PM, Pablo Rodriguez wrote:
>
>> I wonder whether this might be caused by a bug or the code should be
>> adapted to current latest.
> hm, i'll check it ... looks like some lua closure side effect
Many thanks for
On 5/8/2021 7:55 PM, Pablo Rodriguez wrote:
I wonder whether this might be caused by a bug or the code should be
adapted to current latest.
hm, i'll check it ... looks like some lua closure side effect
from within the container as the /src directory.[2]
Once you are in the container run these commands to process the hello world
document:
# cd /src
# context hello_world.tex
There's no PDF viewer installed so you'll need to view it from the host in
"sources". On the Mac th
abledirectives[overloadmode=warning]
or even
\enabledirectives[overloadmode=error]
just in case you want to check if your own macros clash or harm the system.
Hans
-
Hans Hagen | PRAGMA ADE
..]
>
> Hi Adam,
>
> I’m on a Linux computer, so I’m not able to check this now.
>
> If the signature isn’t working, you mean that the output PDF document
> from fields-007.tex cannot be signed with Acrobat DC, don’t you?
>
> Sorry for asking the obvious question,
On 5/2/21 12:20 AM, Adam Reviczky wrote:
> Hi,
>
> I cannot get the signature working either, but almost certain it did
> work in February this year, as I have done some with MKIV.
> [...]
Hi Adam,
I’m on a Linux computer, so I’m not able to check this now.
If the signature isn
example
% TEXMFVAR = /var/lib/texmf
% is used in many distros. In this case, set VARTEXFONTS like this
%VARTEXFONTS = $TEXMFVAR/fonts
% and do not mention it in TEXMFDBS (but _do_ mention TEXMFVAR).
%
% Remove $VARTEXFONTS from TEXMFDBS if the VARTEXFONTS directory is below
% one of the TEXMF direct
On 4/30/2021 5:47 PM, Alan Bowen wrote:
I removed and then reinstalled luametex: the problem persists.
The stix fonts changed names (again) so the 2 in the names are gone and
text is in the filenames ...
Can you check if your names.tma has 2 in names?
Here it works ok with 'two
inimal example because I'm unable to reproduce it (copy all font settings
> to a new document and run ConTeXt).
>
> Can you also check if the font files are found by ConTeXt:
>
> mtxrun
have create a
minimal example because I'm unable to reproduce it (copy all font
settings to a new document and run ConTeXt).
Can you also check if the font files are found by ConTeXt:
mtxrun --script fonts --list --all stixtwotext*
Wol
share relevant files? AFAIK only cmarrows and .mf
files in
> the cm source folder are involved. I hope you can check it if a
solution
> is possible and not too demanding. Thanks beforehand.
you can make a minimal failure example but I gues sthat the solution
has
to
On 4/27/2021 9:23 AM, Jairo A. del Rio wrote:
So, should I share relevant files? AFAIK only cmarrows and .mf files in
the cm source folder are involved. I hope you can check it if a solution
is possible and not too demanding. Thanks beforehand.
you can make a minimal failure example but I gues
So, should I share relevant files? AFAIK only cmarrows and .mf files in the
cm source folder are involved. I hope you can check it if a solution is
possible and not too demanding. Thanks beforehand.
Regards,
Jairo
El lun, 26 de abr. de 2021 a la(s) 03:56, Hans Hagen (j.ha...@xs4all.nl)
escribió
On 4/26/2021 12:37 PM, Hans van der Meer wrote:
I get the following message in the log (latest beta):
fonts > !
fonts > ! check count_components with mkiv !
fonts > !
These are my font settings:
\definefontfeature [default] [default] [itlc=yes]
\setu
701 - 800 of 4742 matches
Mail list logo
