ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henri Menke <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Hyphenation errors (again or still) in recent mkiv
Date: Tue, 2 Aug 2016 13:58:13 +0200	[thread overview]
Message-ID: <56f9e16d-d963-8e20-200f-05743d1a98ef@gmail.com> (raw)
In-Reply-To: <4855198f-1113-a611-aef9-bb1a4642dda5@gmx.es>

On 08/01/2016 06:13 PM, Pablo Rodriguez wrote:
> On 08/01/2016 02:39 PM, Ulrike Fischer wrote:
>> Am Mon, 01 Aug 2016 11:52:11 +0200 schrieb Wolfgang Schuster:
>>
>>> The wrong hyphenation happens also with the default font.
>>>
>>> %\startexceptions[en]
>>> %    would syn-the-size enu-mer-ate
>>> %\stopexceptions
>>>
>>> \starttext \hsize=1mm
>>> would synthesize enumerate
>>> \stoptext
>>
>> On windows the hyphenation is correct, I just updated context and
>> tested. 
>>
>> (I get errors in the example with the simplefonts module, probably I
>> didn't update the module correctly).
> 
> Hans,
> 
> would it be possible that only Windows has the latest LuaTeX binary
> (0.98.0)?
> 
> Linux 32bit has luatex-0.95 and I get wrong hyphenations.

I have LuaTeX, Version 0.95.0 (TeX Live 2016) on openSUSE 13.2 (Harlequin) (x86_64) and correct hyphenations.  Wolfgangs minimal example

\starttext \hsize=1mm
would synthesize enumerate
\stoptext

produces

would
syn-
the-
size
enu-
mer-
ate

which is what pdfTeX produces as well for a similar example.

> 
> Just in case it helps,
> 
> 
> Pablo
> 

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

  reply	other threads:[~2016-08-02 11:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.839.1469991963.6154.ntg-context@ntg.nl>
2016-08-01  9:02 ` Robert Blackstone
2016-08-01  9:16   ` Hans Hagen
2016-08-01  9:52   ` Wolfgang Schuster
2016-08-01 10:29     ` Hans Hagen
2016-08-01 12:39     ` Ulrike Fischer
2016-08-01 16:13       ` Pablo Rodriguez
2016-08-02 11:58         ` Henri Menke [this message]
2016-08-02 13:15           ` Pablo Rodriguez
     [not found] <mailman.852.1470055202.6154.ntg-context@ntg.nl>
2016-08-02  7:16 ` Robert Blackstone
     [not found] <mailman.1.1470045601.2927.ntg-context@ntg.nl>
2016-08-01 10:57 ` Robert Blackstone
2016-07-31 10:57 Robert Blackstone
2016-07-31 14:51 ` Hans Hagen
2016-07-31 18:40   ` Jan Willem Flamma
2016-07-31 19:06     ` Pablo Rodriguez
2016-08-01  7:22       ` Jan Willem Flamma
2016-08-01  7:45         ` Hans Hagen
2016-08-01 13:32           ` Herbert Voss
2016-08-01 13:55             ` Hans Hagen
2016-08-01  8:28         ` 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=56f9e16d-d963-8e20-200f-05743d1a98ef@gmail.com \
    --to=henrimenke@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).