From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: Typefile with Chinese, Korean or Japanase text
Date: Mon, 19 Feb 2018 22:43:56 +0100 [thread overview]
Message-ID: <50adae87-402f-9957-f832-c5ee598066d8@gmx.es> (raw)
In-Reply-To: <ECB17F8B-2E7C-473B-9028-5FBB28010384@me.com>
On 02/19/2018 10:15 PM, Jeong Dal wrote:
> Dear Wolfgang,
>
> Two months ago, you suggested an example for typefile with korean. I
> just read it at that time and I try your sample today.
> Although there are Nanum Gothic and Nanum Gothic Coding in my system
> font, no output of korean for \ss and \tt.
> I run ‘mtxrun —script font —reload —force
> [...]
> Why ConTeXt couldn’t locate the font files?
>
> I am using Mac OSX 10.13 and latest beta.
Hi Jeong,
as far as I can remember, I experienced a similar problem with these
fonts. I needed the first option to get the fonts embedded in the PDF
document.
Go to tex/texmf-cache and remove the directory luatex-cache.
Run "mtxrun --generate" and compile the sample again.
If that doesn’t work, try to copy those fonts to tex/texmf-fonts (and
reload fonts with mxtrun)..
I hope it helps,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2018-02-19 21:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1637.1512580660.1988.ntg-context@ntg.nl>
2018-02-19 21:15 ` Jeong Dal
2018-02-19 21:43 ` Pablo Rodriguez [this message]
2018-02-20 0:12 ` Jeong Dal
[not found] <mailman.1646.1512595887.1988.ntg-context@ntg.nl>
2017-12-06 23:38 ` Jeong Dal
2017-12-05 20:32 Wim Neimeijer
2017-12-05 20:43 ` luigi scarso
2017-12-05 22:10 ` Wim Neimeijer
2017-12-05 22:53 ` Hans Hagen
2017-12-05 23:32 ` Wim Neimeijer
2017-12-06 8:53 ` Hans Hagen
2017-12-06 9:14 ` luigi scarso
2017-12-06 9:02 ` Henning Hraban Ramm
2017-12-06 11:00 ` Wolfgang Schuster
2017-12-06 17:16 ` Wim Neimeijer
2017-12-06 18:13 ` Aditya Mahajan
2017-12-06 18:24 ` Wim Neimeijer
2017-12-06 19:07 ` Pablo Rodriguez
2017-12-06 19:20 ` Rik Kabel
2017-12-06 20:25 ` Hans Hagen
2017-12-06 21:01 ` Wim Neimeijer
2017-12-06 21:30 ` Wim Neimeijer
2017-12-06 22:32 ` Wolfgang Schuster
2017-12-06 22:54 ` Alan Braslau
2017-12-06 18:17 ` 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=50adae87-402f-9957-f832-c5ee598066d8@gmx.es \
--to=oinos@gmx.es \
--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).