ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Palatino patch for the current ConTeXt version
Date: Wed, 27 Nov 2013 21:55:43 +0100	[thread overview]
Message-ID: <52965C4F.7020509@wxs.nl> (raw)
In-Reply-To: <00b901ceebad$900fb0a0$b02f11e0$@tosovsky@email.cz>

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.
>>>>>
>>>>
>>>> there are several ways to apply patches runtime, see *.lfg files
>>>> (and also fonts-mkiv.pdf)
>>>
>>> 1) I've created a sample LFG file
>>> 2) placed it into the folder where other LFG files are stored
>>> 3) removed pala.tma and pala.tmc files from the cache
>>> 4) triggered the generating
>>>
>>> My pala.lfg file seems to be ignored:
>>>
>>> return {
>>>       name = "pala",
>>>       comment = "Switching the small capped 'i' to a dotless variant
>>>                  in Palatino Linotype.",
>>>           remapping = {
>>>           tounicode = true,
>>>           unicodes = {
>>>               ["i.sc"] = 983201,
>>>           },
>>>       },
>>> }
>>
>> you have to load them ... see fonts-mkiv.pdf
>
> Thanks, I got it. Two next steps are required and one turned out as
> redundant.
>
> 1) Create a sample LFG file
> 2) Place it into the folder where other LFG files are stored
> 3) NEW! Execute 'mtxrun --generate' command to include newly added LFG file
> into a file database
> 4) NEW! Specify a new font feature referencing to this goodie:
> \definefontfeature[dotlessi][mode=base,goodies=pala,unicoding=yes]
> \definefontfamily[mainface][rm][Palatino
> Linotype][features={default,quality,dotlessi}]
> 5) Trigger the generating
>
> It does something, but not what I need :-)
>
> My MWE:
> \definefontfeature[dotlessi][mode=base,goodies=pala,unicoding=yes]
> \definefontfamily[palatino][rm][Palatino
> Linotype][features={default,quality,dotlessi}]
> \setupbodyfont[palatino]
> \starttext
> Athenians \sc{Athenians}
> \stoptext
>
> 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.
>
> Maybe other tables need to be tweaked as well...
> Has anybody any experience with this?

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)

Hans




-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2013-11-27 20:55 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 [this message]
2013-11-29 19:44           ` Jan Tosovsky
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=52965C4F.7020509@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).