ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>,
	Adam Reviczky <reviczky@gmail.com>
Subject: Re: Lato typescripts (MKIV/LMTX)
Date: Sat, 17 Sep 2022 20:40:27 +0200	[thread overview]
Message-ID: <0115217d-cc69-ebcf-77e0-ccb8121fc4f6@gmail.com> (raw)
In-Reply-To: <CABaoHuv5RHTPYYf6FY=QkcVNOZQTT71F+DxjrBwqNFshWLcnOA@mail.gmail.com>

Adam Reviczky via ntg-context schrieb am 17.09.2022 um 18:14:
> Hi,
>
> With the latest upload (2022-09-16 14:41) I wanted to compare some 
> older projects that I've used with MKIV to the LMTX 2.10.00.
>
> In one of which I am using the Lato 2.0 font 
> (https://packages.debian.org/sid/fonts-lato).
> With MKIV I get the correct output but LMTX complains about not being 
> able to find the font.

The problem lies in the debian package because the fonts I get from the 
website [1]
of the lato fonts have the same file names as the referenced one in the 
typescripts.

[1] https://www.latofonts.com/

Wolfgang

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2022-09-17 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 16:14 Adam Reviczky via ntg-context
2022-09-17 18:40 ` Wolfgang Schuster via ntg-context [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0115217d-cc69-ebcf-77e0-ccb8121fc4f6@gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=reviczky@gmail.com \
    --cc=wolfgang.schuster.lists@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).