ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Visually replace one character by another one	automatically
Date: Tue, 27 Nov 2007 16:23:14 +0100	[thread overview]
Message-ID: <474C3662.6070100@wxs.nl> (raw)
In-Reply-To: <2e8813a0711270714r4516dd4an402a9f4f805cbb52@mail.gmail.com>

Jeff Smith wrote:
> On Nov 27, 2007 3:18 AM, Taco Hoekwater <taco@elvenkind.com> wrote:
>> This should happen automatically already. Context (well, TeX, really)
>> is even smarter than that: If you type 'hello', it will automatically
>> visualise that as 'hello'. If this does not happen, something is not
>> right with your input, and you'd better post a small example.
> 
> Indeed, your answer made me check back old documents I had printed.
> The comma apostrophe was there! When you don't think about those
> things, you never realize them...
> 
> So I checked back a bit, and what is wrong then is not my input per
> se, but my current document setup, which I don't know how to solve.
> 
> Two weeks ago, I asked about OpenType features. Mojca and Wolfgang
> thus gave examples of \definefontfeature. So, since I wanted to try
> out the historical ligatures in my font (dlig) alongside oldstyle
> nombers, I used the following, based on what I was told:
> 
> \definefontfeature
>  [myfeatures]
>  [method=node,script=latn,language=dflt,liga=yes,onum=yes,kern=yes,dlig=yes]
> 
> It turns out this is the culprit. When I comment that out, the comma
> apostrophes are back. :-)
> 
> This makes me very happy because after all I won't use the historical
> ligatures. Therefore, I can use the oldstyle feature set and
> everything works well.
> 
> That is not to say that wouldn't like to know how to solve what
> happened though. For the sake of it (and some eventual document's
> where this will be crucial), I would like to know what do I need to
> add to \definefontfeature for the apostrophe magic to work?

  tlig=yes trep=yes

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2007-11-27 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27  3:07 Jeff Smith
2007-11-27  8:18 ` Taco Hoekwater
2007-11-27  9:07   ` Taco Hoekwater
2007-11-27 15:14   ` Jeff Smith
2007-11-27 15:23     ` Hans Hagen [this message]
2007-11-27 16:15       ` Jeff Smith
2007-11-28 18:26         ` Henning Hraban Ramm
2007-11-28 19:07           ` Jeff Smith
2007-11-28 21:30             ` Henning Hraban Ramm

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=474C3662.6070100@wxs.nl \
    --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).