ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: wrong \sc i with Palatino Linotype
Date: Mon, 17 Feb 2014 20:46:40 +0100	[thread overview]
Message-ID: <9824.12060625411$1392666427@news.gmane.org> (raw)
In-Reply-To: <53025E32.9020106@gmx.es>

On 2014-02-17 Pablo Rodriguez wrote:
> 
> I have noticed that ConTeXt (beta from 2014.02.14 17:07) has a problem
> with Palatino Linotype.
> 
> Here the sample:
> 
> \definefontfeature[capstosc][c2sc=yes]
> \definefontfamily[mainface][serif][Palatino Linotype]
> \setupbodyfont[mainface]
> \starttext
> {\addfeature[capstosc] AEIOU}
> 
> \sc aeiou
> \stoptext
> 
> All vowels are fine, but the i is a dotted small cap i. The regular
> small cap i is defined as i.sc (and the dotted small cap i is defined
> as i.sc too). But FontForge applies both c2sc and smcp substitutions
> fine.
> 

It seems to be a regression as this example now produces a dot as well:
http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV

(in ConTeXt 2013.12.20 it was Ok)

Jan

___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2014-02-17 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 19:08 Pablo Rodriguez
2014-02-17 19:46 ` Jan Tosovsky [this message]
     [not found] ` <00ac01cf2c18$fa9eebb0$efdcc310$@tosovsky@email.cz>
2014-02-17 19:59   ` Pablo Rodriguez

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='9824.12060625411$1392666427@news.gmane.org' \
    --to=j.tosovsky@email.cz \
    --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).