ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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 12:57:46 +0200	[thread overview]
Message-ID: <F31B5312-9219-402C-B9A9-0E4807E6881F@gmail.com> (raw)
In-Reply-To: <mailman.1.1470045601.2927.ntg-context@ntg.nl>


On 1 Aug 2016, at 12:00 , 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.
> 
> I get
> 
> Thus, I came to the conclusion that the designer of a new system must 
> not only be
> the implementer and first large--scale user; the designer should also 
> write the first
> user manual.
> The separation of any of these four components would have hurt T E X 
> significantly. If
> I had not participated fully in all these activities, literally hundreds 
> of improvements
> would never have been made, because I would never have thought of them 
> or per-
> ceived why they were important.
> But a system cannot be successful if it is too strongly influenced by a 
> single person.
> Once the initial design is complete and fairly robust, the real test 
> begins as people
> with many different viewpoints undertake their own experiments.
> We thrive in information--thick worlds because of our marvelous and 
> everyday ca-
> pacity to select, edit, single out, structure, highlight, group, pair, 
> merge, harmo-
> nize, synthesize, focus, organize, condense, reduce, boil down, choose, 
> categorize,
> catalog, classify, list, abstract, scan, look into, idealize, isolate, 
> discriminate, dis-
> tinguish, screen, pigeonhole, pick over, sort, integrate, blend, 
> inspect, filter, lump,
> skip, smooth, chunk, average, approximate, cluster, aggregate, outline, 
> summarize,
> itemize, review, dip into, flip through, browse, glance into, leaf 
> through, skim, re-
> fine, enumerate, glean, synopsize, winnow the wheat from the chaff and 
> separate the
> sheep from the goats.

Hi Hans,
I'm afraid I'm lost here.
When I copy what you write you get and paste it into my example I still get, with Verdana 10 pt, no hyphenation errors with mkiv version 2015.10.09 21:28 and some with mkiv version 2016.07.18 16:46: marv-elous and di-scriminate.

So doesn't it show that at least the two mkiv-versions differ in this respect and that when using the new version something extra or different has to be done in the setups to get the correct hyphenations?
Fortunately I still have kept some of the older ConTeXt-versions, so my project will not suffer from hyphenation error. But I suspect that reliance on older versions should not have to be necessary.

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
___________________________________________________________________________________

       reply	other threads:[~2016-08-01 10:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1470045601.2927.ntg-context@ntg.nl>
2016-08-01 10:57 ` Robert Blackstone [this message]
     [not found] <mailman.852.1470055202.6154.ntg-context@ntg.nl>
2016-08-02  7:16 ` Robert Blackstone
     [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
2016-08-02 13:15           ` Pablo Rodriguez
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=F31B5312-9219-402C-B9A9-0E4807E6881F@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).