From: Willi Egger <context@boede.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Type 1 font loading with new beta
Date: Tue, 17 Jan 2012 13:45:13 +0100 [thread overview]
Message-ID: <D937D809-BF09-4358-B6E1-398B868DC6F0@boede.nl> (raw)
In-Reply-To: <9729B3EC-AE4E-433B-A1FA-9D754B743BA8@googlemail.com>
Hi Wolfgang,
thanks for this. Indeed it works ok! (Stupid me had edited the trypescriptfile of the wrong tree before writing yesterdays mail).
Willi
On 16 Jan 2012, at 23:11, Wolfgang Schuster wrote:
>
> Am 16.01.2012 um 23:00 schrieb Willi Egger:
>
>> Hi font gurus,
>>
>> With context from begin of the year it worked to load a type 1 font with a typescript based on the following syntax:
>>
>> \starttypescript [serif] [LTpalatino] [name]
>> \usetypescript[serif][fallback]
>> \definefontsynonym [Serif] [file:pr]
>> \definefontsynonym [SerifItalic][file:poios]
>> \definefontsynonym [SerifBold][file:pb]
>> \definefontsynonym [SerifCaps][file:posc]
>> \definefontsynonym [SerifBoldOsF][file:pobos]
>> \definefontvariant [Serif][osf][OsF]
>> \stoptypescript
>>
>> \starttypescript[LT-Palatino]
>> \definetypeface [LT-Palatino][rm][serif][LTpalatino][default][]
>> \stoptypescript
>>
>> Error:
>>
>> \232>28 ...oldOsF][file:pobos] \definefontvariant
>> [Serif][osf][OsF] \stoptyp...
>> <inserted text> \232>28
>> \232>29
>> \font_typescript_process_typescript_file_and_store ...
>>
>> \font_typescripts_load_file ...ipt_file_and_store
>> \else \font_typescript_pro...
>> \next2 #1,->\font_typescripts_load_file {#1}
>> \syst_helpers_do_process_comma_i...
>> ...
>> l.18 \setupbodyfont
>> [LT-Palatino,rm,10pt]
>>
>> Is due to the overhauling the approach now different?
>
> The \definefontvariant command is no longer available in MkIV because for truetype/opentype fonts it isn’t necessary.
>
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2012-01-17 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 22:00 Willi Egger
2012-01-16 22:11 ` Wolfgang Schuster
2012-01-17 12:45 ` Willi Egger [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=D937D809-BF09-4358-B6E1-398B868DC6F0@boede.nl \
--to=context@boede.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).