ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context <ntg-context@ntg.nl>
Subject: Re: take \dots from the actual font
Date: Fri, 23 Feb 2001 11:00:00 +0100	[thread overview]
Message-ID: <3.0.6.32.20010223110000.019397c0@server-1> (raw)
In-Reply-To: <01022300421007.00637@bilbo>

At 12:42 AM 2/23/01 +0100, Uwe Koloska wrote:
>Hello,
>
>since texnansi encoding has ellipsis included, I want to redefine the 
>meaning of the plainTeX macro \dots to give this real glyph from the actual 
>font.  Because if the font is different from cmr it looks very funny to see 
>these ellipsis from cmr next to this totally different characters ...
>
>It's at position 133 in texnansi encoding.  So I tried
>  \startencoding[texnansi]
>    \definecharacter dots 133
>  \stopencoding
>both in the working file and in enco-ans (with rebuilding the format).  
>There is the normal dots from cmr.
>
>Now -- as a quick hack -- I use
>  \def\dots{\char133}
>but since this assumes that all text is output in texnansi it is a bad 
>solution.
>
>How can we integrate this glyph (and some others -- the actual texnansi has 
>the euro currency sign at position 1) into texnansi encoding?
> 

If you can wait a cople of weeks, it can be added to the named glyph
collection. 

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
-------------------------------------------------------------------------


      reply	other threads:[~2001-02-23 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 23:42 Uwe Koloska
2001-02-23 10:00 ` 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.20010223110000.019397c0@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).