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: Palatino patch for the current ConTeXt version
Date: Fri, 29 Nov 2013 20:44:38 +0100	[thread overview]
Message-ID: <15463.9968336143$1385754302@news.gmane.org> (raw)
In-Reply-To: <52965C4F.7020509@wxs.nl>

On 2013-11-27 Hans Hagen wrote:
> On 11/27/2013 9:16 PM, Jan Tosovsky wrote:
> > On 2013-11-27 Hans Hagen wrote:
> >> On 11/27/2013 12:40 AM, Jan Tosovsky wrote:
> >>> On 2013-11-17 Hans Hagen wrote:
> >>>> On 11/17/2013 12:23 PM, honyk wrote:
> >>>>> Hello Everyone,
> >>>>>
> >>>>> I am trying to fix a Palatino small caps issue using the
> >>>>> procedure explained here:
> >>>>> http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV
> >>>>>
> >>>>> That fix seems to be obsolete nowadays and returning errors.
> >
> > This LFG core settings:
> > unicodes = {
> >     ["a.sc"] = 97,     (1)
> >     ["b.sc"] = 983261, (2)
> > },
> >
> > (1) replaces all small 'a' into small caps variants - just for
> > testing purposes
> > (2) doesn't replace small caps 'i' to small caps 'b', but when small
> > caps text is selected, b is copied into the clipboard - so some
> > replacement is performed, but incomplete.
> >
> 
> this mechanism assumes that the shapes match the one that unicode
> expects so the (default) tounicode is used ... originally this features
> was meant for fonts with a faulty mapping (some dingbat fonts have
> that)
> 

So a different approach is needed. In another thread we've found out that
there are two glyphs of the same name:

glyph index | glyph name
1110        | i.sc        / small caps dotlessi
1170        | i.sc        / small caps i 

Currently when 'i' is to be rendered as small caps, 1170 is used, but I'd
like to use 1110 instead.

Can this be specified using a LFG file?

Thanks, 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:[~2013-11-29 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001a01cee387$691cd370$3b567a50$@tosovsky@email.cz>
2013-11-17 11:44 ` Hans Hagen
2013-11-26 23:40   ` Jan Tosovsky
     [not found]   ` <008801ceeb00$db41e820$91c5b860$@tosovsky@email.cz>
2013-11-27  8:37     ` Hans Hagen
2013-11-27 20:16       ` Jan Tosovsky
     [not found]       ` <00b901ceebad$900fb0a0$b02f11e0$@tosovsky@email.cz>
2013-11-27 20:55         ` Hans Hagen
2013-11-29 19:44           ` Jan Tosovsky [this message]
2013-12-01  8:40 ` Jan Tosovsky
2013-12-21 10:02 ` Jan Tosovsky
2013-11-17 11:23 honyk

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='15463.9968336143$1385754302@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).