From: <josephcanedo@gmail.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: Obtaining features from EBGaramond font in ConTeXt
Date: Fri, 23 Oct 2015 19:19:00 +0000 [thread overview]
Message-ID: <e0807dbb9c524bb2aeb773e97ca09496@gmail.com> (raw)
In-Reply-To: <562A42F0.8060005@rik.users.panix.com>
[-- Attachment #1.1: Type: text/plain, Size: 2213 bytes --]
Thanks Rik,
I’ll install standalone ConTeXt along TexLive then.
Is there any place I could find docs on \definecharacterspacing command please ? Could not find any occurrence on the Wiki.
Many thanks
Best regards
Joseph
Sent from Windows Mail
From: Rik Kabel
Sent: Friday, October 23, 2015 4:23 PM
To: ntg-context@ntg.nl
On 2015-10-23 03:44, josephcanedo@gmail.com wrote:
Hello all,
Wondered if you could figure out what I did wrong with specifying the font.
Asked question on TexExchange.org already, with samples.
http://tex.stackexchange.com/questions/274471/obtaining-features-from-ebgaramond-font-in-context
I use texlive 2015 on Windows 8.1
Many thanks,
Best regards
Joseph Canedo
First, some small changes to your example. Remove the enableregime directive; ConTeXt MKIV, which you appear to be using, does not use this. It is from ConTeXt MKII. Next, modify the definefontfeature and definefontfamily commands as shown. (The default features for the font are in the file type-imp-ebgaramond.mkiv.) That should be it to get started.
\language[fr] % french hyphenation
\definefontfeature[myfeatures][ss02=yes,cv01=yes,cv03=yes,ss05=yes,cv91=yes]
\definefontfamily[mainfont][serif][EBGaramond][features={default,myfeatures}]
\setupbodyfont[mainfont, 8pt]
\starttext
session
univers
Que
Quelconque
Joseph
¶
\stoptext
TL15 has problems with EBGaramond. The best you will get is:
With a more recent standalone version, you will get:
If you are setting older texts, you may also want to take advantage of ConTeXt’s ability to automatically provide space before large punctuation characters using the definecharacterspacing command.
One other note. Character variant 01 (cv01) is a very dull sword. The rules for the use of long-ſ are much too complex for it to handle. For a good overview of the issues, see Andrew West’s article in the TUGboat at https://www.tug.org/TUGboat/tb32-1/tb100west.pdf. In my opinion you are better off learning to insert it as needed in the text.
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 6017 bytes --]
[-- Attachment #2: edjfaiia.png --]
[-- Type: image/png, Size: 5972 bytes --]
[-- Attachment #3: dajaigih.png --]
[-- Type: image/png, Size: 5802 bytes --]
[-- Attachment #4: 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:[~2015-10-23 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 7:44 josephcanedo
2015-10-23 14:23 ` Rik Kabel
2015-10-23 19:19 ` josephcanedo [this message]
2015-10-23 19:49 ` Rik Kabel
2015-10-23 20:47 ` josephcanedo
2015-10-23 21:33 ` Rik
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=e0807dbb9c524bb2aeb773e97ca09496@gmail.com \
--to=josephcanedo@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).