From: Nicolas Girard <nicolas.girard@nerim.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: No em/en dashes (was: define font | font with name Delicious-Roman is not found)
Date: Thu, 28 May 2009 18:47:20 +0200 [thread overview]
Message-ID: <51b0095d0905280947s76aba9e9w5196baada24fd87f@mail.gmail.com> (raw)
2009/5/28 Wolfgang Schuster <schuster.wolfgang@googlemail.com>:
>
Hi Wolfgang,
thanks for such a fast answer !
> Am 28.05.2009 um 17:59 schrieb Nicolas Girard:
>
>>
>> \starttext
>> \font\Myfont=Delicious-Roman at 24pt
>> \Myfont Hello, world
>> \stoptext
>
>
> Please don't use \font, use ConTeXt's \definefont instead:
>
OK, but why ? Reading the list, I see that you were still using it six
months ago ; is is deprecated now ?
> \definefont[Myfont][name:Delicious-Roman][features=default]
This indeed let me get the font. But then, I can't get any en/em
dashes when typing -- / ---.
I have:
$ mtxrun --script fonts --list --info --pattern="delicious*roman"
MTXrun | fontname: deliciousroman
MTXrun | fullname: Delicious-Roman
MTXrun | filename: /usr/local/share/fonts/d/delicious_roman.otf
MTXrun |
MTXrun | gpos features:
MTXrun |
MTXrun | feature script languages
MTXrun |
MTXrun | kern latn dflt
MTXrun |
MTXrun | gsub features:
MTXrun |
MTXrun | feature script languages
MTXrun |
MTXrun | tlig all all
MTXrun | trep all all
but none of the following tests did succeed:
%=====
\starttext
\definefont[Myfont][name:Delicious-Roman][features=default]
\Myfont Goodbye --- cruel -- world
\stoptext
%=====
\starttext
\definefontfeature[default][mapping=tex-text]
\definefont[Myfont][name:Delicious-Roman][features=default]
\Myfont Goodbye --- cruel -- world
\stoptext
%=====
\starttext
\definefontfeature[default][tlig=yes,mapping=tex-text]
\definefont[Myfont][name:Delicious-Roman][features=default]
\Myfont Goodbye --- cruel -- world
\stoptext
%=====
\starttext
\definefontfeature[default][tlig=yes,script=latn,mapping=tex-text]
\definefont[Myfont][name:Delicious-Roman][features=default]
\Myfont Goodbye --- cruel -- world
\stoptext
Any thoughts ?
--
Nicolas
___________________________________________________________________________________
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 reply other threads:[~2009-05-28 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 16:47 Nicolas Girard [this message]
2009-05-28 17:01 ` Wolfgang Schuster
2009-05-28 17:27 ` Nicolas Girard
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=51b0095d0905280947s76aba9e9w5196baada24fd87f@mail.gmail.com \
--to=nicolas.girard@nerim.net \
--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).