From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problems with linespacing - typescript
Date: Sat, 5 Nov 2011 18:00:53 +0100 [thread overview]
Message-ID: <4E41594B-80BD-4B50-94BA-78D16166C3EB@googlemail.com> (raw)
In-Reply-To: <4EB565A4.5030701@gmx.de>
Am 05.11.2011 um 17:34 schrieb Jan Heinen:
>
> > Regenerate the font database with “mtxrun --script font --reload” and try it again.
>
> That was not successful.
>
> However, I changed your code a bit and now it seems ok:
>
> When I use:
> \definedfont[name:allerlight*default at 36pt]
>
> instead of:
> \definedfont[file:allerlt*default at 36pt]
>
> then it works.
> Changed:
> file: -> name:
> allerlt -> allerlight
When “file:allerlt” doesn’t work your fonts have a different filename than mine.
What output on the command line do you get?
keima:TeX wolf$ mtxrun --script font --list --all aller*
aller aller /Users/wolf/Library/Fonts/Aller_Rg.ttf
allerbold allerbold /Users/wolf/Library/Fonts/Aller_Bd.ttf
allerbolditalic allerbolditalic /Users/wolf/Library/Fonts/Aller_BdIt.ttf
allerdisplay allerdisplay /Users/wolf/Library/Fonts/AllerDisplay.ttf
allerdisplaynormal allerdisplay /Users/wolf/Library/Fonts/AllerDisplay.ttf
alleritalic alleritalic /Users/wolf/Library/Fonts/Aller_It.ttf
allerlight allerlight /Users/wolf/Library/Fonts/Aller_Lt.ttf
allerlightitalic allerlightitalic /Users/wolf/Library/Fonts/Aller_LtIt.ttf
allerlightlight allerlight /Users/wolf/Library/Fonts/Aller_Lt.ttf
allernormal alleritalic /Users/wolf/Library/Fonts/Aller_It.ttf
> Do I still use "type-aller"? Or did I destroy the connection to the typescript with my changes?
\definefont and \definedfont don’t use the typescript but context’s database where all recognized fonts are listed.
A typescript is simple spoken a list where you specify which file should be used for the regular, italic or bold alternative and with a typescript file these settings are available as module which can be reused for different document without putting the code in each document, all you need is a referenced to the file.
> Maybe important? The "aller"-files are ttf not otf.
Both versions I found are also in truetype format but it doesn’t matter which format the fonts have because context supports both and a truetype font can be also a opentype font.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-11-05 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 16:34 Jan Heinen
2011-11-05 17:00 ` Wolfgang Schuster [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-05 15:17 Jan Heinen
2011-11-05 15:56 ` Wolfgang Schuster
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=4E41594B-80BD-4B50-94BA-78D16166C3EB@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--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).