From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: opbd not behaving properly?
Date: Sat, 1 Sep 2018 19:18:22 +0200 [thread overview]
Message-ID: <49f99ad5-22c7-6216-4790-feb58a6ba591@gmx.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
Dear list,
I have the following sample:
\definefontfeature[default][default][protrusion=quality]
\definefontfeature[opbd][protrusion=yes,opbd=yes]
\setupalign[hanging]
\showframe
\starttext
\definedfont[LinLibertine_R.otf*default at 450pt]
%~ \definedfont[LinLibertine_R.otf*opbd at 450pt]
W
\stoptext
I cannot compile it with latest beta (from 2018.08.30 18:41). I get a
Lua error.
Using the same beta, opbd don’t seem to work anymore. I mean, opbd
worked with ConTeXt about a year:
\showframe
\definefontfeature[default][default][protrusion=quality, opbd=yes]
\definefontfamily[mainface][rm][TestOPBD]
\setupbodyfont[mainface, 60pt]
\setupalign[hanging]
\starttext
Ἠ\\Ἠ\\Ἦ\\ἯἯ
\stoptext
I mean, I compile it, but lfbd isn’t used at all (I attach the test font
I use).
Have I hit a bug or am I missing something?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
[-- Attachment #2: TestOPBD-Regular.otf --]
[-- Type: application/vnd.oasis.opendocument.formula-template, Size: 63840 bytes --]
[-- Attachment #3: 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 reply other threads:[~2018-09-01 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 17:18 Pablo Rodriguez [this message]
2018-09-01 18:24 ` Hans Hagen
2018-09-02 5:50 ` Pablo Rodriguez
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=49f99ad5-22c7-6216-4790-feb58a6ba591@gmx.es \
--to=oinos@gmx.es \
--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).