From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: robust \dots command
Date: Mon, 12 Mar 2001 21:45:10 +0100 [thread overview]
Message-ID: <3.0.6.32.20010312214510.00b48df0@server-1> (raw)
In-Reply-To: <01030511522101.00898@bilbo>
At 11:52 AM 3/5/01 +0100, Uwe Koloska wrote:
>Hello,
>
>I suggest to change the definition of \dots to match the one from latex.
>With the current implementation \dots uses the math \ldots so it is not set
>in the current font.
>
>Latex makes a distinction between \textellipsis and \mathellipsis:
hm, they hardly look like ellipsis -)
>\DeclareRobustCommand{\dots}{%
> \ifmmode\mathellipsis\else\textellipsis\fi}
I'm more thinking of an extensions to the symbol mechanism that understanda
math, something:
\definesymbols[class][text][math] as companion to \definesymbol[class][text]
>\DeclareTextCommandDefault{\textellipsis}{%
> .\kern\fontdimen3\font
> .\kern\fontdimen3\font
> .\kern\fontdimen3\font}
\periods[124]
>\def\mathellipsis{\mathinner{\ldotp\ldotp\ldotp}}%
>
>
>The advantage of this definition is, that we can switch easyly to a real
>ellipsis if the current font has one.
This should be part of the encoding vector, so if someone collects those
... emdash endsh etc are also candidates, although i'm still not sure about
the distinction between what goes into a normal text font and what not, but
the default handler can catch it.
So, go ahead and collect symbols and they will be added,
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-03-12 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 10:52 Uwe Koloska
2001-03-12 20:45 ` Hans Hagen [this message]
2001-03-14 0:04 ` Uwe Koloska
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.20010312214510.00b48df0@server-1 \
--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).