From: Nikolai Weibull <mailing-lists.context-users@rawuncut.elitemail.org>
Subject: [BUG] unic-032.tex 0x2026 HORIZONTAL ELLIPSIS definition wrong
Date: Wed, 20 Jul 2005 01:16:06 +0200 [thread overview]
Message-ID: <20050719231606.GA5232@puritan.pnetwork> (raw)
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
\textellipsis usually expands to \cdots and that's fine, but
\textellipsis shouldn't be used in unic-032.tex for 0x2026 HORIZONTAL
ELLIPSIS, as this codepoint is for a symbol of dots on the base-line,
not in the center. I've posted about this previously, but got no
response. Anyway, I've attached a patch that fixes the problem. I
don't know if using \dots instead is the best solution, though, so
further discussion may be necessary?,
nikolai
--
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
[-- Attachment #2: unic-032.patch --]
[-- Type: text/plain, Size: 663 bytes --]
--- old-unic-032.tex 2005-07-20 01:13:44.414092288 +0200
+++ unic-032.tex 2005-07-20 01:13:54.869502824 +0200
@@ -113,7 +113,7 @@
\strippedcsname \unknownchar \or % U+2023 TRIANGULAR BULLET
\strippedcsname \unknownchar \or % U+2024 ONE DOT LEADER
\strippedcsname \unknownchar \or % U+2025 TWO DOT LEADER
- \strippedcsname \textellipsis \else % U+2026 HORIZONTAL ELLIPSIS
+ \strippedcsname \dots \else % U+2026 HORIZONTAL ELLIPSIS
\ifcase\numexpr#1-48\relax
\strippedcsname \perthousand \or % U+2030 PER MILLE SIGN
\strippedcsname \unknownchar \or % U+2031 PER TEN THOUSAND SIGN
[-- Attachment #3: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2005-07-19 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 23:16 Nikolai Weibull [this message]
2005-07-20 19:47 ` Hans Hagen
2005-07-20 21:02 ` Nikolai Weibull
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=20050719231606.GA5232@puritan.pnetwork \
--to=mailing-lists.context-users@rawuncut.elitemail.org \
--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).