ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: missing Dstroke & dstroke
Date: Fri, 24 Jan 2003 21:27:31 +0100	[thread overview]
Message-ID: <20030124202731.GB1093@scaprea> (raw)
In-Reply-To: <20030124135854.GA14636@mail.inet.hr>

On Fri, Jan 24, 2003 at 02:58:54PM +0100, Gour wrote:
> Simon Pepping (spepping@scaprea.hobby.nl) wrote:
> 
> > As was discussed some time ago the mapping of Unicode characters in
> > ConTeXt requires more work. The default encoding uses a simple
> > compatibility:
> > 
> > enco-def.tex:
> > \definecharacter Dstroke          {D}
> > \definecharacter dstroke          {d}
> > 
> 
> Thank you for your pointer for further "research". I've found that enco-mis.tex
> handles this D&dstroke mechanism since they are resolved as \DJ & \dj commands,
> but I don't have any idea whether it can be used somehow to solve my problem.
> 
It is dependent on the encoding of your output font. In enco-en.tex I
see this: 

\definecharacter dmacron         158
\definecharacter Eth             208

These seem to be other names for dstroke and Dstroke. If you use an
ec-encoded font and you say this:

\definecharacter dstroke         158
\definecharacter Dstroke         208

would that help?

Regards, Simon

-- 
Simon Pepping
email: spepping@scaprea.hobby.nl

  reply	other threads:[~2003-01-24 20:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 13:22 Gour
2003-01-23 21:12 ` Simon Pepping
2003-01-24 13:58   ` Gour
2003-01-24 20:27     ` Simon Pepping [this message]
2003-01-25  8:24       ` Gour
2003-01-28 16:54       ` missing Dstroke & dstroke - "solved" Gour
2003-01-31 22:28         ` Hans Hagen
2003-02-01 11:54           ` Zeljko Vrba
2003-02-01 13:36             ` Hans Hagen
2003-02-01 15:05               ` Zeljko Vrba
2003-02-01 13:59             ` Hans Hagen

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=20030124202731.GB1093@scaprea \
    --to=spepping@scaprea.hobby.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).