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
___________________________________________________________________________________
