Hi, I have a strange behavior with the latest beta: - OpenType Font "Myriad" - Tagging enabled Result: Hyphenation is not working, i.e., the hyphens disappear. Example output correct (when disabling tagging): [...] If I had not partici- pated fully [...] Example output defect (when enabling tagging): [...] If I had not partici pated fully [...] MWE: \setuptagging[state=start] %<- correct when commenting this line \starttypescript[sans][myfont] \definefontsynonym[Sans][file:MyriadPro-Regular] \stoptypescript \definetypeface[Body][ss][sans][myfont] \setupbodyfont[Body,ss,10pt] \starttext \input knuth \input tufte \input reich \input linden \input darwin \stoptext Any feedback is welcome. @Hans: I can provide the Myriad font if this helps. Cheers, Christoph
On 11/09/2015 08:42 AM, Christoph Reller wrote:
MWE:
\setuptagging[state=start] %<- correct when commenting this line \starttypescript[sans][myfont] \definefontsynonym[Sans][file:MyriadPro-Regular] \stoptypescript \definetypeface[Body][ss][sans][myfont] \setupbodyfont[Body,ss,10pt] \starttext \input knuth \input tufte \input reich \input linden \input darwin \stoptext
Any feedback is welcome. @Hans: I can provide the Myriad font if this helps.
It's not specific to Myriad, I get the same problem with other fonts as well, such as Adobe Garamond or Optima (but not Minion Pro or Sabon). It's a bug with the new font loading mechanism; if you add \usemodule [oldotf] to your document, the problem goes away. Hans will probably write "fixed in next beta." Thomas
On 2015-11-09 07:34, Thomas A. Schmitz wrote:
On 11/09/2015 08:42 AM, Christoph Reller wrote:
MWE:
\setuptagging[state=start] %<- correct when commenting this line \starttypescript[sans][myfont] \definefontsynonym[Sans][file:MyriadPro-Regular] \stoptypescript \definetypeface[Body][ss][sans][myfont] \setupbodyfont[Body,ss,10pt] \starttext \input knuth \input tufte \input reich \input linden \input darwin \stoptext
Any feedback is welcome. @Hans: I can provide the Myriad font if this helps.
It's not specific to Myriad, I get the same problem with other fonts as well, such as Adobe Garamond or Optima (but not Minion Pro or Sabon). It's a bug with the new font loading mechanism; if you add
\usemodule [oldotf]
to your document, the problem goes away. Hans will probably write "fixed in next beta."
Thomas And this appears to be the same issue I reported (on 20151022) with tagging and ebgaramond, so no need for an Adobe-licensed font for testing.
-- Rik
participants (3)
-
Christoph Reller -
Rik Kabel -
Thomas A. Schmitz