> Am 08.10.2020 um 17:41 schrieb Denis Maier :
>
> where can I find the hyphenation patterns used by ConTeXt? I have two wrongly
> hyphenated words, and I want to check whether this is due to incorrect
> patterns. (I tried the source browser... not much luck so far.) The
want to check whether this is
# due to incorrect patterns. (I tried the source browser... not much
# luck so far.) The words are:
# 1. applicable => hyphenated as applic-able
# 2. obligated => hyphenated as oblig-ated
#
# I know I can use \hyphenation to correct that, but I wanted to
>
>>\definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
>>I don't know what the previous line does ... but it works ok here when
>>you remove it.
>> This line loads the font from a file ZapfDingbats.ttf. Without this line I
>> get no check marks
the previous line does ... but it works ok here when
you remove it.
This line loads the font from a file ZapfDingbats.ttf. Without this line
I get no check marks in the output and the following log messages:
i don't know that one
fonts > defining > font with asked name 'uzdr' i
s line loads the font from a file ZapfDingbats.ttf. Without this line I
get no check marks in the output and the following log messages:
fonts > defining > font with asked name 'uzdr' is not found using
lookup 'file'
fonts > defining > unknown font 'uzdr', loading
r
>>>
>>> Thank you Hans!
>>> Access by glyph index with \tochar{i:19} works well for both MKIV and
>>> LMTX. Access by name with \tochar{n:a39} does not work in LMTX with log
>>> message: char ✓ (U+02713) in font 'ZapfDingbats-4' with id 8: missing.
>>>
;
>>>>For nwo access by 'name' or 'index' (these are kind of stable for
>>> such
>>>>an old font):
>>>>
>>>> n:a34 : \getglyph{ZapfDingbats}{\tochar{n:a34}} \par
>>>> n:a35 : \getglyph{ZapfDingbats}{\to
{ZapfDingbats}{\tochar{i:49}} \par
> n:a104 : \getglyph{ZapfDingbats}{\tochar{n:a104}} \par
> n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
>
> Thank you Hans!
> Access by glyph index with \tochar{i:19} works well for both MKIV and
> LMTX. Access by
[name:ZapfDingbats]✓
\stoptext
I still get no check mark in the output PDF and a log message "char ✓
(U+02713) in font 'ZapfDingbats-4' with id 8: missing". Am I using the
font wrongly?
(This has not a high priority for me, because I have the unified access
by glyph index.)
yph names in LMTX.
> should be a bit better in yesterdays upload (i also changed the file
> name alias so that in pinciple unicode should work too)
Dear Hans,
Thank you for working on this. I have tried version 2020.09.20: Unicode
input works for the "Private Use Area" Unicodes reported i
Thanks. I'll need to check what happens here.
Am 19.09.2020 um 12:03 schrieb Hans Hagen:
On 9/18/2020 11:10 PM, denis.maier.li...@mailbox.org wrote:
Hi
Is there a setting that prevents footnotes from spreading over more than
one page? I have a document where this seems to be the case, but I
8: missing
(2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char
(U+F0013) in font 'ZapfDingbats-4' with id 8: missing
\ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
\stoptext
In MKIV, line (1) fails to output the requested glyph, while line (2)
produces a "check" (✓). In
}{983059} % LMTX log: char (U+F0013)
in font 'ZapfDingbats-4' with id 8: missing
\ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
\stoptext
In MKIV, line (1) fails to output the requested glyph, while line (2)
produces a "check" (✓). In LMTX, line (2) fails and line (1) produces
correctly. So, it appears to be an issue with font name to
filename mapping.
I'll try a clean install on a docker image and check it that works ... or just
wait for the newer version, which often fixes such things :-)
there have been no fundamental changes, but the names of these liber*
fonts change
pt
and it works correctly. So, it appears to be an issue with font name to
filename mapping.
I'll try a clean install on a docker image and check it that works ... or just
wait for the newer version, which often fixes such things :-)
Aditya
__
rtchapter [title={Chapter title}] [author={Author Name}]
I forgot to change the argument for the check off the author entry,
this should fix it.
\define[3]\ChapterListCommand
{\hbox\bgroup
\hbox to 3cm{\currentlistsymbol\hss}% number + labeltext
\vtop\bgroup
\hsize\dime
to the \ChapterListCommand do I need to make to accommodate
the following? Possibly an \else statement, but not sure how to include
that:
\startchapter [title={Chapter title}] [author={Author Name}]
I forgot to change the argument for the check off the author entry, this
should fix it.
\define[3
s what the wiki entry is about and what I can tell.
> Just know that when you say (in the new wiki addition) 'check on
> \rawstructurelistuservariable' that link simply tells me 'There is currently
> no text in this page'. That leaves someone like me without a lot of the
> long-g
Thanks, and I am sure that this entry into the wiki will be also helpful
for others. For me it will be step by step, and using your information I
can now at least get an author's name into the toc! But that's about
all. Just know that when you say (in the new wiki addition) 'check
Il 04/09/20 11:01, Henning Hraban Ramm ha scritto:
Am 03.09.2020 um 13:32 schrieb mf :
Use check=yes
But I need check=no, because my author has several entries like
Miller, Carolyne, born Princess of Sayn-Wittgenstein 123–125
Sayn-Wittgenstein, Carolyne of see Miller, Carolyne
i.e
> Am 03.09.2020 um 13:32 schrieb mf :
>
> Use check=yes
But I need check=no, because my author has several entries like
Miller, Carolyne, born Princess of Sayn-Wittgenstein 123–125
Sayn-Wittgenstein, Carolyne of see Miller, Carolyne
i.e. the reference target often has a
On 9/3/20 8:09 PM, Hans Hagen wrote:
> On 9/3/2020 4:52 PM, Pablo Rodriguez wrote:
>> [...]
>> I’m afraid that packed item lists are misbehaving.
>>
>> Could anyone confirm this?
> can you check again (new lmtx)
Many thanks for the new upload, Hans.
Now packed
]
\startitem Item\stopitem
\startitem Item\stopitem
\startitem Item\stopitem
\startitem Item\stopitem
\stopitemize
\stoptext
I’m afraid that packed item lists are misbehaving.
Could anyone confirm this?
can you check again (new lmtx)
Hans
;Ramm, Hraban}{}
No, this results in
"Ramm, Hraban passim see passim"
Only with check=yes, otherwise it works right.
And
\index{passim->Ramm, Hraban}
results in
"Ramm, Hraban passim 1"
No, see attachment page 2.
I.e. I’m still looking for an index entry without "
, Hraban passim see passim"
And
\index{passim->Ramm, Hraban}
results in
"Ramm, Hraban passim 1"
I.e. I’m still looking for an index entry without "see" or page number.
> \placeindex[check=no]
This is essential for references to not (exactly
This should be exactly what you asked for:
\defineprocessor[passim][right=\quad{\it passim}]
\starttext
\samplefile{ward}\index{Ward, Peter}
\samplefile{sapolsky}\index{Sapolsky, Robert}
\seeindex{passim->Ramm, Hraban}{}
\seeindex{Hraban}{Ramm, Hraban}
\page
\placeindex[check=yes]
\p
{Ward, Peter}
\samplefile{sapolsky}\index{Sapolsky, Robert}
\seeindex{Ramm, Hraban}{}
\seeindex{Hraban}{Ramm, Hraban}
\page
\placeindex[check=yes]
\page
\placeindex[check=no]
\stoptext
Massi
___
If your question
weight=200}]
\definefont
[sourcelight]
[file:SourceCodeVariable-Roman.otf*light]
\starttext
\sourcelight Hallo
\stoptext
Thanks. I'll check it. (Reminds me to check another issue in a variable
font that I observed recently, something with accuracy, but of could
also be a border case i
ulas in the math mode,
but I'll have to go back and check the implementation details.
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http:/
tween the lines" on
morning reports and therefore miss the point many times. \stopitem
\startitem Too few hours to do adequate offset well record check
\stopitem
\stopachoices
\stopquestion
\startquestion If the toolpusher noted the following trend while RIH with drill
ersion > 2020.08.14 18:27
yes, i noticed and will reupload (a rare case actually, two files
updated with overflowing the minutge but it might be why we sometimes
have issues so i now check it)
Hans
-
4:52 MESZ schrieb Hans Hagen :
>
> On 8/14/2020 11:41 AM, Jannik Voges wrote:
>
> Hello Pablo,
>
>
> thank you for your suggestions, but I don't use LMTX
> productively, so I
> have no problem with a broken LMTX-version. I only use i
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX-version (to see if I need to change them
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX-version (to see if I need to change them
our suggestions, but I don't use LMTX productively, so
>I
>> have no problem with a broken LMTX-version. I only use it to check
>> whether there are breaking changes in LMTX by typesetting all of my
>> documents with the newest LMTX-version (to see if I need to change
>them
>> in
On 8/14/2020 11:41 AM, Jannik Voges wrote:
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX
Pablo Rodriguez schrieb am 13.08.2020 um 16:18:
On 8/13/20 3:11 PM, Wolfgang Schuster wrote:
[...]
With the options "split=no" and "split=repeat" ConTeXt puts the table in
a \vbox but with "split=yes" this doesn't happen.
To check is this is the problem h
On 8/13/20 3:11 PM, Wolfgang Schuster wrote:
> [...]
> With the options "split=no" and "split=repeat" ConTeXt puts the table in
> a \vbox but with "split=yes" this doesn't happen.
>
> To check is this is the problem he can put the table in a float
>
in ConTeXt can trigger an implicit horizontal context.
With the options "split=no" and "split=repeat" ConTeXt puts the table in
a \vbox but with "split=yes" this doesn't happen.
To check is this is the problem he can put the table in a float
environment and d
and check again.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http
On 6 Aug 2020, at 21:30, Hans van der Meer wrote:
>>
>> This MWE is an example of strange font behaviour according to the log and I
>> do not understand what is causing it.
>> ConTeXt complains "check count_components with mkiv" when the word 'suffi'
>>
On 8/7/2020 9:29 AM, Taco Hoekwater wrote:
On 6 Aug 2020, at 21:30, Hans van der Meer wrote:
This MWE is an example of strange font behaviour according to the log and I do
not understand what is causing it.
ConTeXt complains "check count_components with mkiv" when the w
> On 6 Aug 2020, at 21:30, Hans van der Meer wrote:
>
> This MWE is an example of strange font behaviour according to the log and I
> do not understand what is causing it.
> ConTeXt complains "check count_components with mkiv" when the word 'suffi' is
> pr
This MWE is an example of strange font behaviour according to the log and I do not understand what is causing it.ConTeXt complains "check count_components with mkiv" when the word 'suffi' is present (see log message below).Now comes the most strange: remove 'suffi' or shorte
le below shows a
> better method.
>
> 2. What you do with \doifelse{...}{even} is to compare the numeric value of
> the section with the string "even" which is always false. To check whether
> the value is odd or even you have to use the \ifodd command.
>
>>
} is to compare the numeric value
of the section with the string "even" which is always false. To check
whether the value is odd or even you have to use the \ifodd command.
What to change in order to get the desired result?
begin example
\startsetups [section:odd]
\vfill
On 8/4/2020 1:47 PM, Henning Hraban Ramm wrote:
Am 04.08.2020 um 13:20 schrieb Hans Hagen :
On 8/4/2020 11:04 AM, Henning Hraban Ramm wrote:
Hi, me again...
Is there a check if a macro is called from inside of a footnote, like a system
mode *footnote?
(Same with captions?)
In my current
> Am 04.08.2020 um 13:20 schrieb Hans Hagen :
>
> On 8/4/2020 11:04 AM, Henning Hraban Ramm wrote:
>> Hi, me again...
>> Is there a check if a macro is called from inside of a footnote, like a
>> system mode *footnote?
>> (Same with captions?)
>> In my cu
On 8/4/2020 11:04 AM, Henning Hraban Ramm wrote:
Hi, me again...
Is there a check if a macro is called from inside of a footnote, like a system
mode *footnote?
(Same with captions?)
In my current project, index entries should get italic page numbers if they
occurr inside of a footnote
Hi, me again...
Is there a check if a macro is called from inside of a footnote, like a system
mode *footnote?
(Same with captions?)
In my current project, index entries should get italic page numbers if they
occurr inside of a footnote (or a caption, but that is rare).
I’m using different
On Fri, 31 Jul 2020, Hans Hagen wrote:
Thanks for the update.
Other work in progress is: better columns in itemize, esp proper
footnote support (not that I ever need that but I know users do so ...),
experiments work ok, but I need to check spacing. In general, footnotes
(will) behave a bit
>> support (not that I ever need that but I know users do so ...), experiments
>>> work ok, but I need to check spacing. In general, footnotes (will) behave a
>>> bit better, especially those used nested in other mechanisms. A side effect
>>> of more control i
On 8/1/2020 3:20 PM, Otared Kavian wrote:
On 31 Jul 2020, at 10:32, Hans Hagen wrote:
[…]
Other work in progress is: better columns in itemize, esp proper footnote
support (not that I ever need that but I know users do so ...), experiments
work ok, but I need to check spacing. In general
> On 31 Jul 2020, at 10:32, Hans Hagen wrote:
>
> […]
>
> Other work in progress is: better columns in itemize, esp proper footnote
> support (not that I ever need that but I know users do so ...), experiments
> work ok, but I need to check spacing. In general, fo
change it?
Is there a simple mwe to check this? It is no problem to bump the size
but maybe it's something else,
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt
t; shift without too much troubles. I'll wrap up more details in an article
> later.
>
> Other work in progress is: better columns in itemize, esp proper footnote
> support (not that I ever need that but I know users do so ...), experiments
> work ok, but I need to check spacing. In gen
that but I know users do so ...),
experiments work ok, but I need to check spacing. In general, footnotes
(will) behave a bit better, especially those used nested in other
mechanisms. A side effect of more control is that we can do other tricks
too and we're playing with it (kind of fun).
More work
r what it's worth, I'm running VSCode 1.46.0.
> >
> > How can I install the VSCode ConTeXt extension?
> Here i just run this (seems to work with latest update):
>
> data/context/vscode-context.cmd
&
/vscode-context.cmd
(I only occasionally check vscode and will look into it again when there
is easy suffix dependent runner support. Of course I do generate the
syntax files.)
Hans
-
Hans
Bump. I’m having the same issue with the following macro, which I’ve defined to work with a two-column layout and which I invoke within \setupheadertexts: \define\RefRange{% %Check if the first chapter matches the last chapter on the page: \doifelse{\getmarking[Chapter][1][top]}{\getmarking
to an environment file. As you write, "everything has to be in the same file".
The requirement was only necessary for the example to check if the metadata end
up in the PDF file. You could have a environment file for \setupdocument but
the goal here was to check the resulting metadata
gt;> Thank you, Wolfgang.
>>
>> The above example does work. It fails to set the metadata if one moves the
>> \setupdocument to an environment file. As you write, "everything has to be
>> in the same file".
> The requirement was only necessary for the example
.
The above example does work. It fails to set the metadata if one moves
the \setupdocument to an environment file. As you write, "everything
has to be in the same file".
The requirement was only necessary for the example to check if the
metadata end up in the PDF file. You
known file 'mult-fmt.lua'
>> error loading file: mult-fmt.lua (aborting)resolvers | formats |
> hm, typo in zip builder ... i'll fix it but first i need to do something
> else
Many thanks for the new version, Hans.
At least on Linux, it works perfectly fine. (Tomorrow I hav
obat Reader DC in Winows (no Professional version).
>> luametatex.pdf cannot be opened with Evince, Acrobat for Linux or xpdf
>> (e45c09ed2055fab7e8de40fa5f99da4ce46e6849f306a57ac34d99487e025049).
>> mupdf-gl has to repair the xref.
>
> can you check again ... i reverted something
ir broken xref
warning: repairing PDF document
I experience issues in Windows with current latest:
\starttext
\input zapf
\stoptext
The output PDF document opens in SumatraPDF fine. But in Acrobat DC, no
character is displayed.
can you check again
Many thanks for your fas
PDF document
I experience issues in Windows with current latest:
\starttext
\input zapf
\stoptext
The output PDF document opens in SumatraPDF fine. But in Acrobat DC, no
character is displayed.
can you check again
Many thanks for your fast reply, Hans.
Acrobat DC in Windows
warning: trying to repair broken xref
>>warning: repairing PDF document
>>
>> I experience issues in Windows with current latest:
>>
>> \starttext
>> \input zapf
>> \stoptext
>>
>> The output PDF document opens in SumatraPDF
\input zapf
\stoptext
The output PDF document opens in SumatraPDF fine. But in Acrobat DC, no
character is displayed.
can you check again
-
Hans Hagen | PRAGMA ADE
Hi Garulfo,
I uploaded a version that has some of the tranmslations merged in. I'll
now check some more, but I also saw some issues.
A criterium is that translations of variables and constants only are for
those that internally are used as v! and c! while for instance the s
On 12/07/20 03:48, Henning Hraban Ramm wrote:
Hi,
I just installed the latest ConTeXt MkIV (LuaTeX 2.06 20200706 + ConTeXt MkIV
2020.07.09 14:51) to check if the CG journal will look the same as with my
"old” installation (LuaTeX 1.11 7215 + ConTeXt MkIV 2020.01.30 14:13).
All looks
Hi,
I just installed the latest ConTeXt MkIV (LuaTeX 2.06 20200706 + ConTeXt MkIV
2020.07.09 14:51) to check if the CG journal will look the same as with my
"old” installation (LuaTeX 1.11 7215 + ConTeXt MkIV 2020.01.30 14:13).
All looks well in Preview.app and PDF Studio 2019, but
Hi,
It is possible that the Mint upgrade changed something in your environment that
affects ConTeXt.
Check for (new) env settings that start with TEXMF.
Best wishes,
Taco
> On 11 Jul 2020, at 03:07, jbf wrote:
>
> Hi,
>
> After upgrading from Linux Mint 19.3 to 20, when at
the
>>>
>>> I never noticed that ... what section/paragraph in the spec?
>> It’s in the implementation limits for Acrobat, not in the normative section.
>
> Great. That used to be 1 bp so now it's more. As it happens, we do have a
> check for this in context so w
in the spec?
It’s in the implementation limits for Acrobat, not in the normative section.
Great. That used to be 1 bp so now it's more. As it happens, we do have
a check for this in context so we can adapt it ... but, as this 3 bp is
kind of arbitrary and because 3 bp becomes a float and thereby
...
Apparently, Adobe InDesign demands that in a hard way.
Or maybe it just cannot handle zero's. The last time I ever ran into an
issue was that a scale should not be zero (so we always have 0.1 at
least). But I only have an old acrobat professional so I can't check the
latest demands.
Hans
rop:1]
> > \stoptext
> >
> > Your sample doesn’t work, because of the reference prefix. Right now,
> > the /Names reads in the PDF code:
> >
> > /Names [ (1) 5 0 R ]
> >
> > It seems that "referenceprefix" is forgotten there, which
On 7/6/20 8:48 PM, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 06.07.2020 um 20:04:
>> [...]
>> Hans, could you check this? (I’m afraid it doesn’t work with current
>> latest [2020.07.06 19:30])?
>
> I'm not Hans but this fixed the problem for m
rop:1) 5 0 R ]
Hans, could you check this? (I’m afraid it doesn’t work with current
latest [2020.07.06 19:30])?
I'm not Hans but this fixed the problem for me (strc-con.mkiv):
\def\strc_constructions_register_yes[#1][#2]% #1=optional user data
#2=interfaced-sett
esn’t work, because of the reference prefix. Right now,
the /Names reads in the PDF code:
/Names [ (1) 5 0 R ]
It seems that "referenceprefix" is forgotten there, which should read
with the sample code from above:
/Names [ (prop:1) 5 0 R ]
Hans, could you check this? (I’m af
e prefix. Right now,
the /Names reads in the PDF code:
/Names [ (1) 5 0 R ]
It seems that "referenceprefix" is forgotten there, which should read
with the sample code from above:
/Names [ (prop:1) 5 0 R ]
Hans, could you check this? (I’m afraid it doesn’t work with current
latest [202
ate some `data` tokens, but it doesn't apply
> > bound checking on it's arguments:
>
> there is no checking yet, there is an upper limit of 0x1F, so i'll add a
> check for that
OK, that explains it.
[...]
>
> eventually i want all to have reasonable ranges in the to
y consists of a single \fi)
i already fixed here (noticed it when documenting some conditionals)
- token.new can only create some `data` tokens, but it doesn't apply
bound checking on it's arguments:
there is no checking yet, there is an upper limit of 0x1F, so i'll
a
nderstands an arbitrary measure, e.g. \blank[3pt] or \blank[0.25em]
Probably also \blank[0.5*small] works (didn’t check, but \blank[3*big] works).
Otherwise see https://wiki.contextgarden.net/Command/blank
Hraban
Thanks Hraban,
These don't work though... It appears that a decimal will work with a
> degrees?
> >
> > I’ve tried \blank[1mm] and other dimensions but nothing will go smaller than
> small… :-(
>
> \blank understands an arbitrary measure, e.g. \blank[3pt] or \blank[0.25em]
>
> Probably also \blank[0.5*small] works (didn’t check, but \blank[3*big] works).
r dimensions but nothing will go smaller than
> small… :-(
\blank understands an arbitrary measure, e.g. \blank[3pt] or \blank[0.25em]
Probably also \blank[0.5*small] works (didn’t check, but \blank[3*big] works).
Otherwise see http
your help and for your time.
You can try to replace the line
replace('cd:instances/cd:constant', 'value', variables)
with
replace('cd:constant', 'value', variables)
in x-setups-basics.mkiv and check if this replaces the texts.
ative = figure buffer...
You have to provide your modified mult-def.lua file, otherwise there is
no way to check what's wrong.
Patch file : mult-def.lua.test1_figure.diff
context --make fr
context --interface=fr --global --result=setup-fr x-setups-overview.mkiv
Then the pdf file shows
- \demar
fect :
1- command "\startfigure \stopfigure"
2- "figure" in "\setuppageinjection" > alternative = figure buffer...
You have to provide your modified mult-def.lua file, otherwise there is
no way to check what's wrong.
I get another difficulty with \startitemize
in LMTX.
hm, it should work (alternative suffixes), but it i'll check it
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69
se, user can perform such evaluation, storage and conditional
extra-code-call individually, but maybe there is some support for similar
situations in Ctx.
there is a twopassdata mechanism for storing stuff but other than that
you can just write to a file and then check that (depending on what r
Hello,
I need to check within Lua.
My sample cases are very minimalistic - I'm working on more complicated task
actually, where check-for-control-sequence-existence need to be performed
run-time within Lua scope.
Best,
Lukas
-- Původní e-mail --
Od: Hans van der
will
> > > > normally assign new mathcodes anyway, but especially class 1 seems like
> > > > a *very* unnatural default for normal letters.
> > > i'll check it (digits get class 0) ... indeed these defaults nowadays
> > > never
> > > kick in this
em because the format will
normally assign new mathcodes anyway, but especially class 1 seems like
a *very* unnatural default for normal letters.
i'll check it (digits get class 0) ... indeed these defaults nowadays never
kick in this way
Thanks. Is there any way to convert either a token number (as
.
2. Before that, check last modified information (from "curl -I") and
avoid downloading if the already downloaded file is newer that the
remote version.
3. It would be better if downloaded files could have the remote time
("curl -R"), instead download time. CreationDate and ModDa
den.net
>
> _______
>
Oh, many thanks for the quick fix, Wolfgang! Now it looks as intended.
/Mikael
PS 1: No, the delab was there for me to check which one was the "wrong"
one. There are probably better
;> I got my system working by quick and dirty patching install.sh
>>
>> I have now
>>
>> PLATFORM="linux-aarch64"
>>
>> after the last esac and all works like expected.
>>
>> I would like to have a check fo
:mardi 26 mai 2020 18:33À : Joseph; mailing list for ConTeXt usersObjet :Re: RE : Re: RE : Re: [NTG-context] Issue with latest LMTX version 2020-05-25 On 5/26/2020 2:28 PM, Joseph wrote:> I want to check if current paragraph is being indented.I'll add \doifelseindented to lmtx ... which
I followed Lutz Haseloff's suggestion and inserted
PLATFORM="linux-aarch64"
after the last esac in install.sh and indeed it installed ConTeXt LMTX.
I assume the insertion of the next two lines in the install.sh file on
line 50 would solve the problem for future arm64 users (I di
:17 PM, Lutz Haseloff wrote:
>> Hi all,
>>
>> I got my system working by quick and dirty patching install.sh
>>
>> I have now
>>
>> PLATFORM="linux-aarch64"
>>
>> after the last esac and all works like expected.
>>
>> I w
901 - 1000 of 4487 matches
Mail list logo
