From: Jeong Dalyoung <haksan@me.com>
To: ntg-context@ntg.nl
Subject: Re: font name has a space.
Date: Mon, 07 Mar 2011 21:03:06 +0900 [thread overview]
Message-ID: <8133C56B-0324-459C-BFA2-637CCCC397E3@me.com> (raw)
Dear Taco,
Thank you for your comment.
I renamed the font to ~.ttf, luatools --generate first.
And try the same file.
At this time, there is no "Fatal error messages", but still it doesn't locate the font file.
So, I tested a few more things.
Test 1:
luatools locates all the fonts which has no space from the same font maker. And, LuaTeX runs well to yield fine output.
Math-iMac:~ graph$ luatools 산돌돌CB.otf
/Users/graph/Library/Fonts/산돌돌CB.otf
Math-iMac:~ graph$ luatools 산돌명조B.otf
/Users/graph/Library/Fonts/산돌명조B.otf
#######
Test 2:
luatools cannot locate the fonts which has space from the same font maker.
Math-iMac:~ graph$ luatools 산돌명조M.otf
Math-iMac:~ graph$ luatools 산돌명조 M.otf
Math-iMac:~ graph$ luatools 산돌명조\space M.otf
But it locates the same file if I enclose "font name".
Math-iMac:~ graph$ luatools "산돌명조 M.otf"
/Users/graph/Library/Fonts/산돌명조 M.otf
So I tired \definefont[testfont][file:"산돌명조 M.otf"], but LuaTeX issue an error
system > begin file testmp.tex at line 29
! LuaTeX error <main ctx instance>:1: ')' expected near '?'.
system > tex > error on line 30 in file testmp.tex: LuaTeX error ...
25
26 \definefont[testfont][file:"산돌명조 M.otf"]
27
28
29 \starttext
30 >> \testfont
31 \chapter{X}
32 \section{One}
33 \dorecurse{10}{test fone file. }
34 \dorecurse{10}{산 돌 명조 폰트 file입니다. }
35
36 \stoptext
\lowleveldefinefont ...ies ", "\@@fontgoodies " )}
\edef \somefontspec {at \n...
\dododefinefont ...inefont {#2}\rawfontidentifier
\csname \rawfontidentifier...
l.30 \testfont
?
I tested english font which has a space in its name and got the same results. For example, "Geogia Bold.ttf" font.
luatools cannot locate it and LuaTeX said "unknown font." and used default font.
I renamed it GeogiaBold.ttf in /Library/fonts and tried again, but not succeed.
Hence, I think that the font whose name contains no space has no problem.
The fonts whose name contains a space make a trouble eventhough I removed the space from it.
Am I doing right?
I am using Mac OSX. And,
This is LuaTeX, Version beta-0.65.0-2010121316
\write18 enabled.
(testmp.tex
ConTeXt ver: 2011.02.25 22:03 MKIV fmt: 2011.3.1 int: english/english
Thank you again.
Best regards,
Dalyoung
___________________________________________________________________________________
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 reply other threads:[~2011-03-07 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 12:03 Jeong Dalyoung [this message]
2011-03-07 17:10 ` Wolfgang Schuster
-- strict thread matches above, loose matches on Subject: below --
2011-03-07 23:42 Jeong Dalyoung
2011-03-06 23:58 Jeong Dalyoung
2011-03-07 7:21 ` Taco Hoekwater
2011-03-06 12:52 Jeong Dalyoung
2011-03-06 15:45 ` Hans Hagen
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=8133C56B-0324-459C-BFA2-637CCCC397E3@me.com \
--to=haksan@me.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).