From: Joseph Canedo <josephcanedo@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Missing font features in page header if \feature[-]is used in header text
Date: Wed, 30 May 2018 16:26:18 +0200 [thread overview]
Message-ID: <5b0eb486.1c69fb81.1ba47.f7ee@mx.google.com> (raw)
In-Reply-To: <6112dfc4-26f2-1f44-4b51-629028937695@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1884 bytes --]
Thanks a lot Hans for your prompt response.
De : Hans Hagen
Envoyé le :mercredi 30 mai 2018 16:17
À : mailing list for ConTeXt users; Joseph Canedo
Objet :Re: [NTG-context] Missing font features in page header if \feature[-]is used in header text
On 5/30/2018 2:31 PM, Joseph Canedo wrote:
> Dear list,
>
> Provided MWE below I notice that font features seem ignored in page
> header rendering. Anything I am doing wrong ?
>
> Rendering is fine if \headerok is used.
>
> Any help would be appreciated.
>
> Thanks
>
> Best regards
>
> Joseph
>
> \definefontfeature[base][mode=node, liga=yes, dlig=yes, hlig=yes, kern=yes]
>
> \definefontfeature[xvicentury][]
>
> \definefontfamily[mainfont][serif][EBGaramond][features=base]
>
> \setupbodyfont[mainfont, 9pt]
>
> \showfontkerns
>
> \def\wrongheader{First book {\feature[-][xvicentury]v} Psalme De David.}
> %% \feature[-] seems to cause problems in header
>
> \def\headerok{First book v Psalme De David.}
>
> \setupheadertexts[\wrongheader] %% kern/ligatures missing <---
>
> % \setupheadertexts[\headerok] %% kern/ligatures ok <---
>
> \starttext
>
> \wrongheader %% all ok in main text
>
> \headerok
>
> \stoptext
you can put this in cont-new.mkiv after \unprotect
\unexpanded\def\resetglobalattributes{\the\t_attr_list_global\attribute\zerocount\zerocount}
\unexpanded\def\resetlocalattributes {\the\t_attr_list_local
\attribute\zerocount\zerocount}
\let\resetallattributes\resetlocalattributes
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 5052 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-05-30 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 12:31 Missing font features in page header if \feature[-] is " Joseph Canedo
2018-05-30 14:17 ` Hans Hagen
2018-05-30 14:26 ` Joseph Canedo [this message]
2019-04-14 16:20 Joseph Canedo
2019-04-15 9:03 ` 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=5b0eb486.1c69fb81.1ba47.f7ee@mx.google.com \
--to=josephcanedo@gmail.com \
--cc=j.hagen@xs4all.nl \
--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).