ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: inactive -- and ---
Date: Sun, 20 Nov 2005 14:55:26 +0100	[thread overview]
Message-ID: <19FA03A3-869A-4CD7-88A9-708239177AC2@uni-bonn.de> (raw)
In-Reply-To: <438076A7.8030805@elvenkind.com>

I just looked into font conversion for another project. In EC.enc,  
you have this line:

% LIGKERN hyphen hyphen =: endash ; endash hyphen =: emdash ;

so fonts converted by texfont and using --enc=ec should have the  
dashes enabled automagically. The problem I had was with the f- 
ligatures, I had to manually add these lines:

% LIGKERN f f =: ff ; f i =: fi ; f l =: fl ;
% LIGKERN ff f =: fff ; ff i =: ffi ; ff l =: ffl ;

In general, texnansi still seems to be doing a better job with this  
sort of thing. The ligkern instructions are not mentioned explicitly  
in texnansi.enc, but they are still used, so I assume texfont has  
them hardwired into its own code somewhere. May be Adam knows more  
about it?

Best

Thomas

On Nov 20, 2005, at 2:14 PM, Taco Hoekwater wrote:

> Thomas A. Schmitz wrote:
>> Hraban,
>> AFAIK, -- and --- aren't active, but they (should) produce  
>> ligatures,  so the problem is most probably at the level of the  
>> tfms you  produced. How did you obtain them? By running texfont?  
>> Which encoding  are you using?
>
> \defaultencoding expands to 'ec' these days (used to be 'texnansi').
> Perhaps that is the problem?
>
> Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2005-11-20 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20 12:12 Henning Hraban Ramm
2005-11-20 12:29 ` Thomas A. Schmitz
2005-11-20 13:14   ` Taco Hoekwater
2005-11-20 13:55     ` Thomas A. Schmitz [this message]
2005-11-20 22:43       ` Henning Hraban Ramm
2005-11-23 11:20         ` Thomas A. Schmitz

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=19FA03A3-869A-4CD7-88A9-708239177AC2@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).