From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: Setting up lbr fonts
Date: Thu, 24 Jan 2002 11:56:32 +0100 [thread overview]
Message-ID: <20020124115632.520f04b4.morawski@gmx.net> (raw)
In-Reply-To: <5.1.0.14.1.20020123093117.033d0c00@server-1>
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
next prev parent reply other threads:[~2002-01-24 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 11:45 Randall Skelton
2002-01-22 12:28 ` Hans Hagen
2002-01-23 1:44 ` Jens-Uwe Morawski
2002-01-23 8:54 ` Hans Hagen
2002-01-24 10:56 ` Jens-Uwe Morawski [this message]
2002-01-24 13:23 ` Hans Hagen
2002-01-25 7:25 ` Jens-Uwe Morawski
2002-01-25 9:46 ` Hans Hagen
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=20020124115632.520f04b4.morawski@gmx.net \
--to=morawski@gmx.net \
/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).