From: Hans Hagen <pragma@wxs.nl>
Cc: <ntg-context@ntg.nl>
Subject: Re: emdash(?)
Date: Mon, 15 Nov 1999 09:42:15 +0100 [thread overview]
Message-ID: <3.0.6.32.19991115094215.00809d70@pop.wxs.nl> (raw)
In-Reply-To: <009d01bf2f39$f1b16780$0321a8c0@bmach.nederware.nl>
At 08:20 AM 11/15/99 +0100, Berend de Boer wrote:
>Is there a standard emdash in ConTeXt? I.e. not depending on certain font
>properties like:
>
> this is ---more often than not--- what I mean
>
>For certain fonts '-' cannot be put together because it looks very odd when
>the '-' is not exactly a line, but something more embellished.
>
>If ConTeXt doesn't have this, how long should such an emdash be? I call it
>an emdash but I think it probably is twice as large as that.
The instrument is:
this is |<|more often than not|>| what I mean
Using || takes care of hyphenation and spacing. In the language setup files, you will see the way the dash is hooked into the language. If you run into troubles with fonts, I think we should add something emdash (like guillemots, do a grep on them) so that a font encoding definition can adapt it to the font. Just collect me the right glyphs.
The compound word dash (||) is by default slightly longer than the single - and composed of two overlapping -'s. The reason for this is that I want to distinguish a hyphen from a compound hyphen but also wants them both to have equal height.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
prev parent reply other threads:[~1999-11-15 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 7:20 emdash(?) Berend de Boer
1999-11-15 8:42 ` Hans Hagen [this message]
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=3.0.6.32.19991115094215.00809d70@pop.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).