From: Thangalin via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Thangalin <thangalin@gmail.com>
Subject: Re: Switching fonts changes framedtext justification
Date: Mon, 4 Apr 2022 18:16:41 -0700 [thread overview]
Message-ID: <CAANrE7qP==DX8p8Ux8SWu2D4dTBhtR8=tTpvh09=jFTnU2A85A@mail.gmail.com> (raw)
In-Reply-To: <3b61d75e-6bdd-a313-ed9f-cde34e26572f@gmx.es>
> The font is too old, but the TTF version works just fine on both Linux
> and Windows.
No dice with LMTX 2022.04.01 09:37 and the TTF file. Using the TTF,
the emojis don't appear, but the text is justified. Using the OTF, the
emojis appear, but the text is unjustified.
What version of ConTeXt are you using, Pablo?
___________________________________________________________________________________
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://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-04-05 1:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 0:36 Thangalin via ntg-context
2022-04-03 8:30 ` Marco Patzer via ntg-context
2022-04-03 9:09 ` Pablo Rodriguez via ntg-context
2022-04-03 23:21 ` Thangalin via ntg-context
2022-04-04 6:40 ` Henning Hraban Ramm via ntg-context
2022-04-04 15:49 ` Thangalin via ntg-context
2022-04-04 15:53 ` Pablo Rodriguez via ntg-context
2022-04-05 1:16 ` Thangalin via ntg-context [this message]
2022-04-05 14:17 ` Pablo Rodriguez via ntg-context
2022-04-07 17:50 ` Thangalin via ntg-context
2022-04-07 19:41 ` Pablo Rodriguez via ntg-context
2022-04-08 0:25 ` Thangalin via ntg-context
2022-04-08 7:26 ` Henning Hraban Ramm via ntg-context
2022-04-08 19:41 ` Thangalin via ntg-context
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='CAANrE7qP==DX8p8Ux8SWu2D4dTBhtR8=tTpvh09=jFTnU2A85A@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=thangalin@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).