From: "Bart C. Wise" <bntgcontext@wiseguysweb.com>
To: ntg-context@ntg.nl
Subject: Re: XeTex & Mara Font
Date: Tue, 18 Nov 2008 13:26:02 -0700 [thread overview]
Message-ID: <200811181326.02873.bntgcontext@wiseguysweb.com> (raw)
In-Reply-To: <20081118201302.GK18156@phare.normalesup.org>
That seems to work. I just renamed the fontname and family (removing the
colon), generated a new ttf and loaded that into the system.
So this works:
\definetypeface[MaraFontNFPlain][rm][Xserif][MaraFontNFPlain]
\starttext
\startfont[MaraFontNFPlain]
This is a test.
\stoptext
And yes, the url is correct as far as where I got the font from. And yes,
there were other errors (or warnings) when I generated the font; however, it
does work.
One quick question (again expressing my ignorance). Why can't I take the code
above and change it to the following:
\definetypeface[Mara][rm][Xserif][MaraFontNFPlain]
\starttext
\startfont[Mara]
This is a test.
\stoptext
Thanks,
Bart
On Tuesday 18 November 2008 01:13:02 pm Arthur Reutenauer wrote:
> > Is the colon at the end of the name a problem?
>
> No, the message says the problem is with the space character, but it
> is of little concern here (XeTeX doesn't use PostScript font names at
> all).
>
> Is it the font from http://www.perry.com/disney/indy/marafont.html?
> It seems to have quite a number of other problems actually (xdvipdfmx
> protests heavily when I try loading it with plain XeTeX). You could try
> saving it again from FontForge, and installing that modified font (you
> of course need to uninstall the original one from your system, or more
> problems will likely happen). While doing so, you can of course modify
> whatever seems suspicious (like the trailing colon, etc.).
>
> Arthur
> ___________________________________________________________________________
>________ 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 : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________
>________
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-11-18 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 18:45 Bart C. Wise
2008-11-18 18:54 ` Arthur Reutenauer
2008-11-18 19:03 ` Bart C. Wise
2008-11-18 19:25 ` Bart C. Wise
2008-11-18 19:31 ` Bart C. Wise
2008-11-18 20:13 ` Arthur Reutenauer
2008-11-18 20:26 ` Bart C. Wise [this message]
2008-11-18 22:00 ` Arthur Reutenauer
2008-11-18 22:28 ` Wolfgang Schuster
2008-11-18 22:56 ` Bart C. Wise
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=200811181326.02873.bntgcontext@wiseguysweb.com \
--to=bntgcontext@wiseguysweb.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).