From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: how to handle the fonts whose name contains a blank space?
Date: Fri, 30 Dec 2011 12:29:17 +0100 [thread overview]
Message-ID: <BCB3CA98-1092-4B97-995A-E417959E6C85@googlemail.com> (raw)
In-Reply-To: <639701AD-69B3-4831-956E-F4E20A007055@me.com>
Am 30.12.2011 um 02:52 schrieb dalyoung:
> Dear all,
>
> Sometime ago, I asked the same question and got replies.
> However, I couldn't make it work and I didn't try since then.
>
> Now, I am asking the same question again with a hope.
>
> I have several Korean fonts whose name contains a blank space.
>
> For example, in KoPubBatang_Pro family, there are 3 fonts:
> KoPubBatang_Pro Light (font file name is "KoPubBatang_Pro Light.otf")
> KoPubBatang_Pro Medium (font file name is "KoPubBatang_Pro Medium.otf")
> KoPubBatang_Pro Bold (font file name is "KoPubBatang_Pro Bold.otf")
>
> You can download the fonts from here:
> http://www.mcst.go.kr/web/notifyCourt/notice/mctNoticeView.jsp?pSeq=6870
>
>
> Here is a sample code:
>
> \definefont[test][KoPubBatang_Pro Light.otf]
Remove the space:
\definefont[test][file:kopubbatangprolight*default]
Wolfgang
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-12-30 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 1:52 dalyoung
2011-12-30 11:29 ` Wolfgang Schuster [this message]
[not found] <mailman.1511.1325275694.4232.ntg-context@ntg.nl>
2011-12-30 23:23 ` dalyoung
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=BCB3CA98-1092-4B97-995A-E417959E6C85@googlemail.com \
--to=schuster.wolfgang@googlemail.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).