ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Multiple Problems with font handling
Date: Sat, 02 Mar 2002 13:59:12 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20020302135603.02c96518@server-1> (raw)
In-Reply-To: <200203011554.g21FsxE01181@nathir.fiee.lan>

At 04:54 PM 3/1/2002 +0100, Henning Hraban Ramm wrote:
>Am Donnerstag, 28. Februar 2002 23:16 schrieb Hans Hagen:
> > >And did you fix the lower double quote problem?
> > eh, i remember the mail, was it an encoding issue (missing def in
> > encoding)?
>
>You do? I don't -- I told you in Erlangen, not by mail. ;-)

hm, anyhow, there has been some discussion on this issue ...

>I don't know what's the reason, but the lower left double quote ("99")
>is build from two commas (with *all* fonts), and these are too wide spread.
>First, ConTeXt should use an existent lldq from the font,
>second, if there's no lldq in the font, the two commas must be kerned
>together.

... which had to do with the fact that we need extend the current encoding 
vectors with symbolic names for this.

this is in enco-def:

\startencoding[default]

\definecharacter leftupperninequote   92
\definecharacter rightupperninequote  34
\definecharacter endash              123
\definecharacter emdash              124
\definecharacter hyphen               45

\stopencoding

also with the double ones, and enco-ec and alike should also define them. 
Can you give that a try?

[guillemots also fall in this category]

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
-------------------------------------------------------------------------
                                   fall-back web server: 
www.pragma-pod.nl
-------------------------------------------------------------------------


  reply	other threads:[~2002-03-02 12:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 11:06 Oliver Mihatsch
2002-02-27 19:51 ` Hans Hagen
2002-02-28 14:05   ` Oliver Mihatsch
2002-02-28 14:13     ` Frans Goddijn
2002-02-28 16:22       ` Oliver Mihatsch
2002-02-28 18:51         ` Henning Hraban Ramm
2002-02-28 16:38   ` Oliver Mihatsch
2002-02-28 18:54     ` Henning Hraban Ramm
2002-02-28 20:56       ` W. Egger
2002-02-28 21:54         ` Hans Hagen
2002-02-28 22:16       ` Hans Hagen
2002-03-01 15:54         ` Henning Hraban Ramm
2002-03-02 12:59           ` Hans Hagen [this message]
2002-03-01  0:19     ` Hans Hagen
2002-03-01  9:35       ` Oliver Mihatsch
2002-03-02 13:20         ` Hans Hagen
2002-03-04  9:32           ` Oliver Mihatsch
2002-03-04 10:06             ` Hans Hagen
2002-03-04 14:42               ` Oliver Mihatsch
2002-03-04 18:55                 ` Hans Hagen
2002-03-05  8:18                   ` Oliver Mihatsch

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=5.1.0.14.1.20020302135603.02c96518@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).