From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/58639 Path: news.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: Hyphenation of composed words Date: Mon, 10 May 2010 10:12:24 +0200 Message-ID: <4BE7BFE8.7050706@wxs.nl> References: <20100416164615.7381cc63@vorbis> <4BC8D7B8.4090406@wxs.nl> <20100509213411.31b62ed9@vorbis> <4BE77CB8.7010800@googlemail.com> <20100510072707.19eb2897@vorbis> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1273479213 16167 80.91.229.12 (10 May 2010 08:13:33 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 10 May 2010 08:13:33 +0000 (UTC) Cc: Marco To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Mon May 10 10:13:30 2010 connect(): No such file or directory Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OBO7E-0004iQ-95 for gctc-ntg-context-518@m.gmane.org; Mon, 10 May 2010 10:13:28 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 981D6C9CB4; Mon, 10 May 2010 10:13:26 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id eKPp7AmKWFB2; Mon, 10 May 2010 10:13:21 +0200 (CEST) Original-Received: from balder.ntg.nl (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id E355DC9B80; Mon, 10 May 2010 10:13:20 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 69063C9B80 for ; Mon, 10 May 2010 10:13:19 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ovfaGShijpPZ for ; Mon, 10 May 2010 10:13:09 +0200 (CEST) Original-Received: from smtp.ziggozakelijk.nl (sc-162.r-213-125-29.schoolconnect.nu [213.125.29.162]) by balder.ntg.nl (Postfix) with ESMTP id A9004C9B49 for ; Mon, 10 May 2010 10:13:09 +0200 (CEST) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=10.100.1.100; Original-Received: from [10.100.1.100] (unverified [10.100.1.100]) by controller-9 (SurgeMail 4.3e) with ESMTP id 605-1713362 for multiple; Mon, 10 May 2010 10:12:19 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 In-Reply-To: <20100510072707.19eb2897@vorbis> X-Authenticated-User: hagen@controller-9 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:58639 Archived-At: On 10-5-2010 7:27, Marco wrote: >> 1. || does *not* produce a en-dash but to kerned hyphens > You're right, I looked it up in the sources. It just looked like an > en-dash for me. But this is wrong. For hyphenation a hyphen is used. The > font designer has created a dedicated glyph for this purpose. And two > hyphens (or an en-dash) is too large. I've never seen the advice in a > typography book to kern two hyphens. I don't know why this is > implemented like this. because we needed it to be this way: we use it for separating compound words and then we want to have the hyphen between the compounds to be different from the ones within ... dates back more than ten years (educational usage) .. also, the reason for kerned hyphens instead of an endash is simple: the endash is too thin (at least in lm) anyhow, when i want normal hyphens i just do |-| always >> 2. The correct method to get a *normal* hyphen is >> >> \setuphyphenmark[sign=normal] >> > Yes, this is the correct method. It should be enabled by default. If > somebody wants a larger hyphen (for some mysterious reasen), he/she can set it > up with > > \setuphyphenmark[sign=wide] > >> If the output is not correct it's a bug. > Yes, it is a bug. Hans already confirmed and said, he'll fix it, but it is not > yet done, that's why I wanted to remember him. You can try and run the example > from my first post. With Thomas' workaround the output is OK, but it is only a > workaround. I (and probably many other users) would like to have correct > behaviour by default. this works ok here (and i'm prety sure that it's also ok a few betas ago) \starttext test||test \setuphyphenmark[sign=normal] test||test test|-|test \stoptext and the defaults are unlikely to change, but you can set it in your local cont-sys.tex file Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | 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 ___________________________________________________________________________________