From: Robert Blackstone <blackstone.robert@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Hyphenation errors (again or still) in recent mkiv
Date: Mon, 1 Aug 2016 11:02:09 +0200 [thread overview]
Message-ID: <891F46A1-FF9C-4238-95CE-FF842AF1AA34@gmail.com> (raw)
In-Reply-To: <mailman.839.1469991963.6154.ntg-context@ntg.nl>
On 31 Jul 2016, at 21:06 , Hans Hagen <pragma@wxs.nl>
>
> On 7/31/2016 12:57 PM, Robert Blackstone wrote:
>> Dear all,
>>
>> In the setupfile of my project I have \mainlanguage[en]. The font used is Verdana.
>> With mkiv versions till october 2015 the hyphenation of English words was always correct.
>>
>> The same files compiled with mkiv of july 2016 (version 2016.07.18 16;26) give hyphenations that are definitely wrong.
>> Some examples: begi-nning, pr-ocedure, adequ-ately, st-yle
>>
>> I made some tests with Linux Libertine sans and here also the earlier mkiv's gave correct hyphenations, the july version wrong ones.
>>
>> So it seems that ref. hyphenation something is wrong with this mkiv-version. Or do I now have to use something other than \mainlanguage[en] ?
>
> no example so no solution
>
> Hans
Hi Hans,
Here is an example:
%%%%%%%%%%%%%%%%%
\mainlanguage[en]
\usemodule[simplefonts]
\setmainfont[Verdana]
\setupbodyfont[10pt]
\contextversion
\showgrid
\starttext
\input knuth
\medskip
\input tufte
\stoptext
%%%%%%%%%%%%%%%%%
With mkiv version 2015.10.09 21:28 there are no hyphenation errors.
With mkiv version 2016.07.18 16:46 the following errors occur: wo-uld (line 6), synth-esize (line 13), enum-erate (line 18)
I mentioned some more errors in my original mail, see above.
Best regards,
Robert Blackstone
___________________________________________________________________________________
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
___________________________________________________________________________________
next parent reply other threads:[~2016-08-01 9:02 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 [this message]
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
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=891F46A1-FF9C-4238-95CE-FF842AF1AA34@gmail.com \
--to=blackstone.robert@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).