The problem seems to be resolved. Thanks to everyone, especially Hans, Taco and
Wolfgang for the fast fix (offlist)!
After updating to
ConTeXt ver: 2020.01.30 14:13 MKIV beta fmt: 2020.4.26
Helvetica Neue works with:
==
\starttypescript [sans] [helvet]
See this link:
https://wiki.contextgarden.net/Mac_Installation
In particular, you need this set of shell commands from that page:
mkdir $HOME/context
cd $HOME/context
rsync -av rsync://contextgarden.net/minimals/setup/first-setup.sh .
sh ./first-setup.sh --modules=all --engine=luatex
but we
> On 24 Apr 2020, at 11:56, Taco Hoekwater wrote:
>
> Hi,
>
> FYI, my "context mkiv” standalone seems to be fine (latest download).
> “lmtx” standalone (also latest download) not so much (same problems).
Thx. How do I get/install a ‘context mkiv’ standalone? The standalone on
> On 24 Apr 2020, at 12:14, Benjamin Buchmuller
> wrote:
>
> Hi Hraban,
>
> This might confirm Taco‘s notion that there is some bug lmtx.
We have moved this off-list for a while. For now, if you have problems with
lmtx, just
switch back to the regular mkiv standalone.
Best wishes,
Taco
Hi Hraban,
Thanks for the hint (and the proper fontfamily setup), I have forced reload ten
times now from various accounts; the issue persists unfortunately.
This might confirm Taco‘s notion that there is some bug lmtx. I’m running macOS
Catalina too, but as it worked with the standalone of
Hi,
FYI, my "context mkiv” standalone seems to be fine (latest download).
“lmtx” standalone (also latest download) not so much (same problems).
Looks like something is broken in ltmx’ TTC parser.
OS X Catalina 10.15.4
Taco
> Am 24.04.2020 um 11:13 schrieb Benjamin Buchmuller
> :
>
> Although this specific issue might have been solved meanwhile by the helpful
> suggestions of Wolfang, Thomas and others, I would like to point out that I
> have recently also encountered an odd behaviour of the mtxrun fontloader
Although this specific issue might have been solved meanwhile by the helpful
suggestions of Wolfang, Thomas and others, I would like to point out that I
have recently also encountered an odd behaviour of the mtxrun fontloader in the
standalone, in which not all typefaces are available/properly
> On 24. Apr 2020, at 09:21, Gerben Wierda wrote:
>
>
> I altready did that earlier as per the Wiki information (did not report it)
> and just tried again. No difference.
Steps to happiness:
1. Extract the ttc font to ttf
2. Copy the ttf files to your local texmf directory
3. reload the
> On 24 Apr 2020, at 08:53, Wolfgang Schuster
> wrote:
>
> Can you try this:
>
> \definefontfamily [mainface] [rm] [Optima]
> [it=optimaitalic,
>bf=optimabold,
>bi=optimabolditalic]
I altready did that earlier as per the Wiki information (did not report it) and
just tried again.
With Arial:
\definefontfamily[mainface][rm][Arial]
\setupbodyfont[mainface,10pt]
with Optima:
\definefontfamily[mainface][rm][Optima]
\setupbodyfont[mainface,10pt]
It doesn’t matter if the font statements are before or after \starttext
Then I thought, let’s test some other things. I logged
> Am 24.04.2020 um 08:48 schrieb Gerben Wierda :
>
> Then I thought, let’s test some other things. I logged in as another user,
> and used ConTeXt from TeX Live 2019:
>
>
> It seems to be that on my system, the standalone installed ConTeXt does not
> work with Optima, but the TeX Live
Gerben Wierda schrieb am 24.04.2020 um 08:48:
With Arial:
\definefontfamily[mainface][rm][Arial]
\setupbodyfont[mainface,10pt]
with Optima:
\definefontfamily[mainface][rm][Optima]
\setupbodyfont[mainface,10pt]
It doesn’t matter if the font statements are before or after \starttext
Then I
13 matches
Mail list logo
