From: Tobias Burnus <burnus@gmx.de>
Cc: NTG-ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: the dash from "||"
Date: Tue, 08 Feb 2000 22:13:27 +0100 [thread overview]
Message-ID: <38A086F7.8660F73F@gmx.de> (raw)
In-Reply-To: <m366vzsaam.fsf@coe.uga.edu>
Hi Ed,
> I sometimes wonder why the dash produced by "||" is so big:
> la-la la--la la$-$la la||la
>
> The last one is pretty dark and long. I like the ability to have
> optional breaks, but I'd expect the last one ("la||la") to look like
> the first ("la-la"). Sometimes the darker dash looks out of place in
> documents.
>
> Is there a grammatical reason for the darker dash, or some other
> reason perhaps?
It think Hans wanted to have a alternative to the hyphen which appears on the
end of the line.
(How to type ``Haber-Bosch process´´ here some prefer `--' because Fritz Haber
and Carl Bosch are two persons, a || might look nicer since a `-' is usually
bigger than a `--' and || is longer than `-'. In my opinion || is not the best
for words like `so-called' etc.)
It is defined in supp-lan.tex
%D The sequence \type{||} simply leads to two words connected by
%D a hyphen. Because we want to distinguish such a hyphen from
%D the one inserted when \TEX\ hyphenates a word, we use a bit
%D longer one.
\def\compoundhyphen {{-}\kern-.25ex{-}}
I'm sure you can setup the behaviour (maybe it is in the big manual), but I
cannot find it yet.
(It may work if you use \def\compoundhyphen{{-}}, but I'm to tied and have to
few time to think and test it.)
Tobias
next prev parent reply other threads:[~2000-02-08 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-08 20:34 Ed L. Cashin
2000-02-08 21:13 ` Tobias Burnus [this message]
2000-02-08 22:12 ` Barry Schwartz
2000-02-08 22:04 the dash from || pragma
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=38A086F7.8660F73F@gmx.de \
--to=burnus@gmx.de \
--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).