From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/6644
Path: main.gmane.org!not-for-mail
From: Jens-Uwe Morawski <morawski@gmx.net>
Newsgroups: gmane.comp.tex.context
Subject: Re: Setting up lbr fonts
Date: Thu, 24 Jan 2002 11:56:32 +0100
Sender: owner-ntg-context@let.uu.nl
Message-ID: <20020124115632.520f04b4.morawski@gmx.net>
References: <5.1.0.14.1.20020122132800.032ff078@server-1>
	<20020122114515.900@oxmail.ox.ac.uk>
	<5.1.0.14.1.20020122132800.032ff078@server-1>
	<5.1.0.14.1.20020123093117.033d0c00@server-1>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Trace: main.gmane.org 1035397160 12427 80.91.224.250 (23 Oct 2002 18:19:20 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 18:19:20 +0000 (UTC)
Original-To: ConTeXt <ntg-context@ntg.nl>
In-Reply-To: <5.1.0.14.1.20020123093117.033d0c00@server-1>
Xref: main.gmane.org gmane.comp.tex.context:6644
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:6644

On Wed, 23 Jan 2002 09:54:07 +0100
Hans Hagen <pragma@wxs.nl> wrote:

> Say that you have this palatino and that you used fontinst to generate ec 
> encoded fonts, then you have to make a script like:

First, thank you for your explanations.

> \starttypescript [serif] [adobepalatino] [ec]
> 
>    \definefontsynonym [Palatino]      [thefontinstgeneratedname]
>    \definefontsynonym [PalatinoBold]  [anotherfontinstgeneratedname]
> 
> \stoptypescript

Okay, that's the part i understand

But,

> It's a serif font, so now we define an accompanying serif script:
> 
> \starttypescript [serif] [adobepalatino] [name]
> 
>    \definefontsynonym [Serif]      [Palatino]
>    \definefontsynonym [SerifBold]  [PalatinoBold]
> 
> \stoptypescript
> 

What means/does [name] here?

When i declare a [serif] typescript, why i need:
\definefontsynonym [Serif]      [Palatino]

In my opinion this is redundant.
\definefontsynonym [Regular] [Palatino]
is what i would use. Of course i can map Serif-->Regular in an
other [serif] typescript, but i think that would break another
[sans] typescript with the same mapping.

Or the same question from another point of view: When the font-commands
use or look for Serif, SerifBold ... why the typescript must be declared as [serif]?

or what would mean a [sans] typescript with the same 
 \definefontsynonym [Serif...] [...] definitions?

> The next thing is using this font. Of course you can execute typescripts 
> yourself but best is to use the command
> 
> \definetypeface [myface] [rm] [serif] [adobepalatino] [default] [encoding=ec]

Here again. As far as i understand the font-switching-macros use the declarations
like Serif, or SerifBold. In this case: why i have to declared it as [rm] too?

Or, why i need 'rm' in the next declaration? 'myface' is already defined as 'rm'
> 
> \setupbodyfont[myface,10pt,rm]
> 

Hmm, many questions, which show that i understand nothing ;)

And another question: fontinst generates some fonts including
symbols like degree. upright-mu or the registered-symbol. These
are in (LaTeX) TS1 encoding. What declarations are needed to use them?

Thanks in advance. Regards,
  Jens