From: "Jairo A. del Rio" <jairoadelrio6@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Emoji color fonts not working on LMTX/Context MKIV
Date: Wed, 20 May 2020 05:26:08 -0500 [thread overview]
Message-ID: <CAKyqqabaudRKCTZBmz1C6mnX_2aX1DFAHy40ujORz3StLm5NfQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1740 bytes --]
I've tried the following from the manuals and adapted some code to see if
it works:
1.
\definefontfeature[svg][svg=yes]
\definefontsynonym[Emoji][file:emojionecolor-svginot.ttf*default,svg]
\definesymbol[bug][\getglyphdirect{Emoji}{\char"1F41B}]
\starttext
\symbol[bug]
\stoptext
The emoji has no color when compiled with LuaTeX. Furthermore, the log
includes a lot of lines like the ones below:
fonts > svg conversion > executing runner 'otfsvg': inkscape
--export-area-drawing --shell > temp-otf-svg-shape.log
fonts > svg conversion > processing 1829 svg containers
xml > core > load error: invalid xml file - parsed text
With LMTX it gives an error about mlib-svg.
2.
\definefontfeature[overlay][default][ccmp=yes,colr=yes,dist=yes]
\definefontfeature[svg]
[default][svg=yes]
\definefontfeature[bitmap] [default][sbix=yes]
\definefontfeature [colored] [default]
[ccmp=yes,dist=yes,
colr=yes,svg=yes,sbix=yes]
\definefontsynonym[Emoji][file:notocoloremoji*default,colored]
\definesymbol[bug][\getglyphdirect{Emoji}{\char"1F41B}]
\starttext
\symbol[bug]
\stoptext
What I get is:
fonts > png conversion > processing 3374 png containers
sh: 1: gm: not found
sh: 1: gm: not found
sh: 1: gm: not found sh: 1: gm: not found
...
and the same line repeating itself
...
close source > level 1, order 3, name
'/home/lol/lmtx/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv'
! error: (file /usr/share/fonts/truetype/noto/NotoColorEmoji.ttf) (ttf):
loca table not found
LMTX prints a file without any emoji.
Only Twemoji Mozilla and Segoe UI Emoji worked for me, so, what am I doing
wrong?
I'm working with Ubuntu 20.04 LTS x86_64 and Inkscape 0.92.5 (2060ec1f9f,
2020-04-08) in case it helps. Thank you in advance.
[-- Attachment #1.2: Type: text/html, Size: 3576 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2020-05-20 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 10:26 Jairo A. del Rio [this message]
2020-05-20 19:31 ` Pablo Rodriguez
2020-05-20 19:39 ` Hans Hagen
2020-05-20 20:18 ` Pablo Rodriguez
2020-05-20 21:30 ` Hans Hagen
[not found] <mailman.228.1590003553.9468.ntg-context@ntg.nl>
2020-05-20 20:26 ` Jairo A. del Rio
2020-05-20 21:25 ` Hans Hagen
2020-05-20 21:32 ` Jairo A. del Rio
2020-05-20 21:42 ` Jairo A. del Rio
2020-05-21 15:22 ` Pablo Rodriguez
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=CAKyqqabaudRKCTZBmz1C6mnX_2aX1DFAHy40ujORz3StLm5NfQ@mail.gmail.com \
--to=jairoadelrio6@gmail.com \
--cc=ntg-context@ntg.nl \
/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).