ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Hyphenation errors (again or still) in recent mkiv
Date: Mon, 1 Aug 2016 09:45:50 +0200	[thread overview]
Message-ID: <103d2bed-6258-5758-bcea-d061c194d697@wxs.nl> (raw)
In-Reply-To: <F0DFBB6E-E166-48F9-A746-AEA06822BADF@icloud.com>

On 8/1/2016 9:22 AM, Jan Willem Flamma wrote:
> Hi Pablo,
>
> I wasn’t aware of the \hyphenatedword feature. Thanks for sharing.

 >mtxrun --script patterns --hyphenate schematic

hyphenator      |
hyphenator      | . s c h e m a t i c .   . s c h e m a t i c .
hyphenator      |  0s0c0h2                 0 0 0 2 0 0 0 0 0 0
hyphenator      |    2c0h0                 0 2 0 2 0 0 0 0 0 0
hyphenator      |    0c0h0e2               0 2 0 2 2 0 0 0 0 0
hyphenator      |          1m0a0           0 2 0 2 2 0 0 0 0 0
hyphenator      |            0a0t1i0c0     0 2 0 2 2 0 0 1 0 0
hyphenator      | .0s2c0h2e2m0a0t1i0c0.   . s c h e m a t-i c .
hyphenator      |
mtx-patterns    | us 3 3 : schematic : schematic


> I used an online hyphenation tool (English US) because it’s too tricky for me too!
> Using English UK the words maintenance and integrated are indeed correctly hyphenated. So I jumped to conclusions there.
>
> What remains is that ‘schematic' is incorrectly hyphenated as 'sc-hematic’.
> Another example is the word ‘cards’, which I see hyphenated as 'ca-rds’ but I’m unable to reproduce it in a MWE for now.
>
> Regards,
> Jan Willem
>
>
>
>> On 31 jul. 2016, at 21:06, Pablo Rodriguez <oinos@gmx.es> wrote:
>>
>> On 07/31/2016 08:40 PM, Jan Willem Flamma wrote:
>>> Dear all,
>>>
>>> I can confirm it behaves incorrectly on ConTeXt  ver: 2016.07.30 00:26 MKIV beta
>>
>> Hi Jan Willem,
>>
>> are patterns for Brittish English better?
>>
>>    \starttext
>>    \hyphenatedword{schematic, maintenance and integrated
>>                    beginning procedure adequately style}
>>
>>
>>    \uk\hyphenatedword{schematic, maintenance and integrated
>>                       beginning procedure adequately style}
>>    \stoptext
>>
>> Sorry, but English hyphenation is too tricky for me.
>>
>> Just in case it helps,
>>
>>
>> Pablo
>> --
>> http://www.ousia.tk
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  7:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2016-08-01 13:32           ` Herbert Voss
2016-08-01 13:55             ` Hans Hagen
2016-08-01  8:28         ` Hans Hagen
     [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
     [not found] <mailman.1.1470045601.2927.ntg-context@ntg.nl>
2016-08-01 10:57 ` Robert Blackstone
     [not found] <mailman.852.1470055202.6154.ntg-context@ntg.nl>
2016-08-02  7:16 ` Robert Blackstone

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=103d2bed-6258-5758-bcea-d061c194d697@wxs.nl \
    --to=pragma@wxs.nl \
    --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).