From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: error: unable to define unbatangRegular as \*Myface12ptrmtfa*
Date: Thu, 27 May 2010 09:57:44 +0200 [thread overview]
Message-ID: <4BFE25F8.8020804@elvenkind.com> (raw)
In-Reply-To: <B5107D47-AC18-4497-B5B2-BCAA8EB0375D@me.com>
Hi,
Jeong Dalyoung wrote:
>
> Both current version and "ConTeXt ver: 2010.05.24 13:05 MKIV fmt:
> 2010.5.27 int: english/english" version work same.
>
> Why isn't it able to define "unbatangRegular" while it can use the
> "unbatangBold"?
Drop the [uc] and '[encoding=uc]' from your typescript:
\starttypescript[serif][unbatang]
\definefontsynonym[unbatangRegular][file:UnBatang.ttf]
\definefontsynonym[unbatangBold][file:UnBatangBold.ttf]
\definefontsynonym[unbatangItalic][file:UnGraphic.ttf]
\definefontsynonym[unbatangBoldItalic][file:UnGraphicBold.ttf]
\stoptypescript
Explanation: The extra encoding arguments you had meant that mkiv
did not actually interpret that block of code. As a result, it
only saw
\definefontsynonym[Serif][unbatangRegular]
and that is interpreted as 'name:unbatangRegular', which is a
non-existing font name. unbatangBold worked ok because name:unbatangBold
actually *is* a valid font name.
Best wishes,
Taco
___________________________________________________________________________________
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:[~2010-05-27 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 7:28 Jeong Dalyoung
2010-05-27 7:57 ` Taco Hoekwater [this message]
2010-05-27 14:43 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=4BFE25F8.8020804@elvenkind.com \
--to=taco@elvenkind.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).