From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Calling fonts (was: Hebrew vowel placement in ConTeXt)
Date: Mon, 5 May 2014 17:54:38 +0200 [thread overview]
Message-ID: <8AFDBEA1-A1CD-4AD4-B795-5A736491AC55@gmail.com> (raw)
In-Reply-To: <CAKTWfUOR1o1xdWx-q+15P2S-apRasJWrnnkqKAYtudQ58Be74g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1874 bytes --]
Am 05.05.2014 um 17:29 schrieb Michael Ash <mash@econs.umass.edu>:
> ... see message 56606
> <http://www.mail-archive.com/ntg-context%40ntg.nl/msg56606.html> in the
> list archive. This is not the post-simplefonts solution, but the
> pre-simplefonts solution. It does allow much better control over all of
> the fonts that make up the typeface (using ConTeXt terminology).
>
> If you set only some Hebrew/Aramaic/Arabic, and especially if you do not
> need font variants (bold, italic, ...) you might prefer to define a
> single font.
>
> Thank you very much again. This was helpful, and here is my minimal working example:
>
>
> \definefontfeature[hebrew][default][script=hebr,ccmp=yes]
> \definefont [myhebrew] [SILEOTSR.ttf*hebrew]
> \setupdirections[bidi=on,method=two]
>
> \starttext
> Here is the first line of the Bible.
>
> {\myhebrew בְּרֵאשִׁ֖ית בָּרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָּׁמַ֖יִם וְאֵ֥ת הָאָֽרֶץ׃ }
> \stoptext
>
>
>
> I still have some questions. It took me a long time to understand that
>
> \definefont [myhebrew] [SILEOTSR.ttf*hebrew]
>
> would use the fontfeature "hebrew" that I had defined together with the font file SILEOTSR.ttf and assign this pairing to the nickname "myhebrew". Rik's example also has "sa 1" which I do not understand.
>
> \definefontfeature [aramaic] [default][ccmp=yes,script=hebr]
> \definefont [aramaic] [KeterYG-Medium.ttf*aramaic sa 1]
>
> Is the syntax for definefont using "*" documented somewhere? Is it similar to definefontsynonym at http://wiki.contextgarden.net/Fonts_in_LuaTeX (and below)?
You can find a description about the options in the old and new fonts manuals:
- http://pragma-ade.com/general/manuals/mfonts.pdf
- http://pragma-ade.com/general/manuals/fonts-mkiv.pdf
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 4230 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2014-05-05 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 15:29 Michael Ash
2014-05-05 15:54 ` Wolfgang Schuster [this message]
2014-05-05 18:37 ` Rik Kabel
2014-05-05 20:29 ` Calling fonts Hans Hagen
2014-05-05 18:59 Calling fonts (was: Hebrew vowel placement in ConTeXt) Michael Ash
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=8AFDBEA1-A1CD-4AD4-B795-5A736491AC55@gmail.com \
--to=schuster.wolfgang@gmail.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).