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: [NTG Context] Storm (Lido) font support seems to be broken in newer versions of MKII
Date: Wed, 12 May 2010 10:48:08 +0200	[thread overview]
Message-ID: <4BEA6B48.60300@wxs.nl> (raw)
In-Reply-To: <op.vck3poxu1q7s5f@julesp>

On 12-5-2010 10:40, Honza Pohanka wrote:
> Dne Thu, 06 May 2010 22:13:57 +0200 Hans Hagen <pragma@wxs.nl> napsal(a):
>
>> On 3-5-2010 10:09, Honza Pohanka wrote:
>>> Hello,
>>> the Storm font support by Vit Zyka is broken in actual version of MKII.
>>> I spoke with him, but unfortunately he uses old version and does not
>>> have the time for updates. I discovered that renaming the enco-*.tex
>>> files to enco-*.mkii solves a part of the problem, but there still
>>> remains an issue with math typesetting. Context does not know many
>>> characters (\times, \neq, ...), boldmath etc. Typescripts looks OK and I
>>> don't know enough to look deeper. Could anyone help?
>>
>> aren't there open type storm fonts?
>
> Yes, there are. Could you please give me an example of installing OpenType
> font and creating corresponding typescript? I tried to do that but with no
> succes. (otfinst is not working in windows).

\starttypescriptcollection[myfonts]

     \starttypescript [serif] [myserif] [name]
         \setups[font:fallback:serif]
         \definefontsynonym [Serif]           [file:myserif.ttf] 
    [features=default]
         \definefontsynonym [SerifBold]       [file:myserifbold.ttf] 
    [features=default]
         \definefontsynonym [SerifItalic]     [file:myserifitalic.ttf] 
    [features=default]
         \definefontsynonym [SerifBoldItalic] 
[file:myserifbolditalic.ttf] [features=default]
     \stoptypescript

     \starttypescript[myfont]
         \definetypeface [myfont] [rm] [serif] [myserif]   [default]
     \stoptypescript

\stoptypescriptcollection

\setupbodyfont[myfont]

or use use the simplefonts module


> What was changed in MKII that makes Vit's type1 support unusable? He uses
> approximately two years old release?

nothing changed in mkii .. but as i have no storm fonts i cannot test 
anything .. anyway, if you can use mkiv, it's all easier as we no longer 
have encodings

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
___________________________________________________________________________________


      reply	other threads:[~2010-05-12  8:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 20:09 Honza Pohanka
2010-05-04  8:03 ` Jan Pohanka
2010-05-04 14:05   ` Jan Pohanka
2010-05-12 18:36   ` Mojca Miklavec
2010-05-13  7:40     ` Jan Pohanka
2010-05-13  8:59       ` Hans Hagen
2010-05-13  9:23         ` Jan Pohanka
2010-05-13  9:30         ` Jan Pohanka
2010-05-13 12:53       ` Mojca Miklavec
2010-05-13 13:09         ` Hans Hagen
2010-05-13 15:13           ` Honza Pohanka
2010-05-13 17:40             ` Aditya Mahajan
2010-05-14  8:32               ` Jan Pohanka
2010-05-13 20:19             ` Hans Hagen
2010-05-06 20:13 ` Hans Hagen
     [not found]   ` <op.vck3ngm61q7s5f@julesp>
2010-05-12  8:40     ` Honza Pohanka
2010-05-12  8:48       ` Hans Hagen [this message]

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=4BEA6B48.60300@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).