Re: [NTG-context] setups within typescripts: can it be done?

13 Mar 2013

      On 3/11/2013 5:51 PM, Idris Samawi Hamid ادريس   سماوي حامد wrote:
...
Dear gang,
Here is the situation: For an upcoming book project I may use a set of
proprietary fonts whose license that does not allow modification even
for personal, private use. Some characters I need are absent, but the
I'd choose another font.
...
components I need are there (macrons, dots, etc). So I can conceivably
use \defineactivecharacter to map each needed unicode char to a \def
made of glyph components in the font.
there is a 'compose' feature that does some virtual magic ... it's also 
possible to specify things in a lfg file .. here is a copy from an 
upcoming manual:

Yet another demonstration of manipulation is the following. Not all 
fonts come
with all combined glyphs. Although we have an auto|-|compose feature in 
\CONTEXT\
it sometimes helps to be specific with respect to some combinations. This is
where the \type {compositions} goodie kicks in:

\starttyping
local compose = {
   [0x1E02] = {
     anchored = "top",
   },
   [0x1E04] = {
     anchored = "bottom",
   },
   [0x0042] = { -- B
     anchors = {
       top = {
         x = 300,
         y = 700,
       },
       bottom = {
         x = 300,
         y = -30,
       },
     },
   },
   [0x0307] = {
     anchors = {
       top = {
         x = -250,
         y = 550,
       },
     },
   },
   [0x0323] = {
     anchors = {
       bottom = {
         x = -250,
         y = -80,
       },
     },
   },
}

return {
   name = "lm-compose-test",
   version = "1.00",
   comment = "Goodies that demonstrate composition.",
   author = "Hans and Mojca",
   copyright = "ConTeXt development team",
   compositions = {
     ["lmroman12-regular"] = compose,
   }
}
\stoptyping

Of course this assumes some knowledge of the font metrics (in base 
points) and
\UNICODE\ slots, but it might be worth the trouble. After all, one only 
needs to
figure it out once. But keep in mind that it will always be a kludge.

A slightly different way to define such compositions is the following:

\starttyping
local defaultunits = 193 - 30

local compose = {
                  DY = defaultunits,
  -- [0x010C] = { DY = defaultunits }, -- Ccaron
  -- [0x02C7] = { DY = defaultunits }, -- textcaron
}

-- fractions relative to delta(X_height - x_height)

local defaultfraction = 0.85

local compose = {
   DY = defaultfraction, -- uppercase compensation
}

return {
   name = "lucida-one",
   version = "1.00",
   comment = "Goodies that complement lucida.",
   author = "Hans and Mojca",
   copyright = "ConTeXt development team",
   compositions = {
     ["lbr"]  = compose,
     ["lbi"]  = compose,
     ["lbd"]  = compose,
     ["lbdi"] = compose,
   }
}
\stoptyping

Of course no one really needs this because \OPENTYPE\ Lucida fonts
have replaced the \TYPEONE\ versions.

-----------------------------------------------------------------
                                           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
-----------------------------------------------------------------