ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Problem with setuptagging and ebgaramond font
Date: Sat, 19 Nov 2016 20:58:49 -0500	[thread overview]
Message-ID: <7f0d4b9b-e4d5-dd26-d996-4db8c0f95e7f@rik.users.panix.com> (raw)
In-Reply-To: <901ab8e6-5606-96be-2c83-25beaaedbf45@rik.users.panix.com>

On 2016-11-19 20:48, Rik Kabel wrote:
> This was submitted over a year ago, but probably got lost in the 
> run-up to the 2015 annual meeting. It is still a problem with ConTeXt  
> ver: 2016.11.18 22:20 MKIV beta  fmt: 2016.11.19  int: english/english 
> luajittex, 1.0.1. I am happy to provide a pdf and log file, or other 
> traces, if that helps.
>
> %% When tagging state=start and the font is ebgaramond,
> %%  no hyphens are printed at word breaks.
> %%
> %% When tagging state=start and the font is libertine,
> %%  or any font other than ebgaramond that I have tried,
> %%  hyphens are printed at word breaks.
> %%
> %% When tagging is not started and the font is ebgaramond,
> %%  hyphens _are_ printed at word breaks.
> %%
>
>  \setuptagging[state=start]% remove this line for comparison
>  \setupbodyfont[ebgaramond]% \setupbodyfont[libertine]
>
>  \starttext
>
>    \hsize7cm
>
>    \input zapf \par
>    \input zapf \par
>    \input zapf \par
>    \input zapf \par
>    \input zapf \par
>    \input zapf \par
>  \stoptext
>
> Bug, or error on my part?

Hmmm, it does work (the hyphenation, at least) with TL2016. Both logs 
show the same font files and typescript files.

-- 
Rik

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-11-20  1:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-20  1:48 Rik Kabel
2016-11-20  1:58 ` Rik Kabel [this message]
2016-11-20  2:39   ` Rik
2016-11-20 10:52     ` Hans Hagen
2016-11-20 16:51       ` Rik
2016-11-20 17:17         ` Rik Kabel
2016-11-20 18:37           ` Hans Hagen
2016-11-21  1:54             ` Rik Kabel
2016-11-21 10:59               ` Hans Hagen
2016-11-21 15:38                 ` Rik Kabel

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=7f0d4b9b-e4d5-dd26-d996-4db8c0f95e7f@rik.users.panix.com \
    --to=context@rik.users.panix.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).