ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: iso latin 2 ; storm fonts
Date: Sun, 10 Apr 2005 22:31:50 +0200	[thread overview]
Message-ID: <42598D36.6040103@seznam.cz> (raw)
In-Reply-To: <20050315234505.5648@mail.comp.lancs.ac.uk>

Adam Lindsay wrote:
> Vit Zyka said this at Tue, 15 Mar 2005 19:23:05 +0100:
> 
>>  enco-st1.tex - ec encoding with storm glyph extension
>>  enco-st2.tex - xl2 encoding with storm glyph extension
>>  enco-st3.tex - variants (additional glyph) for enco-st1 and enco-st2
> 
> Vit,
> 
> I would refer you to this thread with Thomas Schmitz on "variant encodings":
> <http://www.ntg.nl/pipermail/ntg-context/2005/009057.html>
> 
> I'd call your st1 an EC variant, st2 an XL2 variant, and st3 some sort of
> custom expert encoding. Ultimately names aren't *that* important, but
> they can help a lot when others try to pick up and understand your work.

Thank you Adam for your suggestion. Your naming convention has a logic. 
The reason why I do not use it is that I utilized work of Petr Olsak. I 
am using all *.tfm, *.map and *.enc files. I believe it is not a 
drawback for ConTeXt but it is advantage for me: do not prepare hundreds 
of metric files.

>>? I have a problem to define mathematics chars. I did:
>>\starttypescript [math] [dynamoRE] [st1]
>>  \definefontsynonym [DynamoRE-Math-Letters]        [sdgr8te] 
>>[encoding=st1]
>>  \definefontsynonym [DynamoRE-Math-Letters-Italic] [sdgri8te] 
>>[encoding=st1]
>>  \definefontsynonym [DynamoRE-Math-Symbols]        [sdgr8te]
>>%  \definefontsynonym [DynamoRE-Math-Extension]        []
>>\stoptypescript
> 
>>But I get error: !Math formula deleted: Insufficient symbol fonts.
>>Where is the problem?

Answer: math family 2 (Math-Symbols) needs extended (math) metric. So I 
switched back to cmsy10. The same for family 3 (Math-Extension).

> I haven't had a chance to play with them yet, but the \setups[font:
> fallback:sans] look to be helpful.

Interesting, I used it.

>>? Storm fonts have different accent shapes for lover/upper case letters. 
>>Is there some mechanism to distinguish this making the composits?

It is incorporated like \UCtilde{I}. But hardly needed for Storm since 
nearly all imaginable accented letter are pressent as a single glyph.
I only defined this way: Ygrave, Ytilde, Ibreve, Ycaron, Etilde.
For details, see enco-st1.tex or enco-st2.tex

vit

  reply	other threads:[~2005-04-10 20:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 17:29 iso latin 2 Hans Hagen
2005-02-09 21:34 ` Vit Zyka
2005-02-09 22:18   ` Adam Lindsay
2005-02-09 23:33     ` Vit Zyka
2005-02-09 23:41       ` Adam Lindsay
2005-02-10  9:23         ` Hans Hagen
2005-02-11 10:56           ` Vit Zyka
2005-03-15 18:23       ` iso latin 2 ; storm fonts Vit Zyka
2005-03-15 18:29         ` Hans Hagen
2005-03-15 23:25         ` Hans Hagen
2005-03-16 23:52           ` Vit Zyka
2005-03-15 23:45         ` Adam Lindsay
2005-04-10 20:31           ` Vit Zyka [this message]
2005-04-11 11:16             ` Adam Lindsay
2005-02-09 22:21   ` iso latin 2 Hans Hagen
2005-02-09 23:52     ` Vit Zyka
2005-02-10  9:26       ` Hans Hagen
2005-02-11 10:17         ` Vit Zyka

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=42598D36.6040103@seznam.cz \
    --to=vit.zyka@seznam.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).