Re: [NTG-context] Type 1 font loading with new beta
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...
>> \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
___
Re: [NTG-context] Type 1 font loading with new beta
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...
> \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
___
[NTG-context] Type 1 font loading with new beta
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...
\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?
Kind regards
Willi
___
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
___
Re: [NTG-context] TYPE 1 font
On 11-11-2010 12:59, Herbert Voss wrote: Am 11.11.2010 12:10, schrieb Mojca Miklavec: 2010/11/11 Herbert Voss wrote: Does ConTeXt always needs an afm-file for the metrics of an type 1 font? And, of course, a map file? Shouldn't DANTE launch a pet project and convert the font to OpenType? (That should be 10-60 minutes of work for somebody familiar with fonts.) But yes, as Hans replied, you need afm file. pdfTeX gets all the font metric data from tfm files, while ConTeXt MKIV prefers to be able to use more than 256 characters when they are available in Type1 font (it doesn't need or read enc, map, vf and tfm files). thanks, I converted it with fontforge to otf. Now I get v...@shania:/opt/context> mtxrun --script fonts --list --all --pattern=*dante* dante dante DANTE.otf dantenormal dante DANTE.otf Is this the intended behaviour, that the afm files are now no more listed? without the otf version the output is: v...@shania:/opt/context> mtxrun --script fonts --list --all --pattern=*dante* dante dante dante.afm dantenormal dante dante.afm indeed, as the names are the same, otf takes precedence over type one Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
Re: [NTG-context] TYPE 1 font
Am 11.11.2010 12:10, schrieb Mojca Miklavec: > 2010/11/11 Herbert Voss wrote: >> Does ConTeXt always needs an afm-file for the metrics of an >> type 1 font? And, of course, a map file? > > Shouldn't DANTE launch a pet project and convert the font to OpenType? > (That should be 10-60 minutes of work for somebody familiar with > fonts.) > > But yes, as Hans replied, you need afm file. pdfTeX gets all the font > metric data from tfm files, while ConTeXt MKIV prefers to be able to > use more than 256 characters when they are available in Type1 font (it > doesn't need or read enc, map, vf and tfm files). thanks, I converted it with fontforge to otf. Now I get v...@shania:/opt/context> mtxrun --script fonts --list --all --pattern=*dante* dante dante DANTE.otf dantenormal dante DANTE.otf Is this the intended behaviour, that the afm files are now no more listed? without the otf version the output is: v...@shania:/opt/context> mtxrun --script fonts --list --all --pattern=*dante* dante dante dante.afm dantenormal dante dante.afm Herbert ___ 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 ___
Re: [NTG-context] TYPE 1 font
2010/11/11 Herbert Voss wrote: > I have a pfb and tfm file of the DANTE font, > which has only the five characters D,A,N,T,E > However, this did not work > > \definefont[dante][dante at 16pt] > \starttext > \dante DANTE > \stoptext > > When I create a afm file from the dante.pfb then > everything is fine. > > Does ConTeXt always needs an afm-file for the metrics of an > type 1 font? And, of course, a map file? Shouldn't DANTE launch a pet project and convert the font to OpenType? (That should be 10-60 minutes of work for somebody familiar with fonts.) But yes, as Hans replied, you need afm file. pdfTeX gets all the font metric data from tfm files, while ConTeXt MKIV prefers to be able to use more than 256 characters when they are available in Type1 font (it doesn't need or read enc, map, vf and tfm files). Mojca ___ 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 ___
Re: [NTG-context] TYPE 1 font
On 11-11-2010 9:16, Herbert Voss wrote: I have a pfb and tfm file of the DANTE font, which has only the five characters D,A,N,T,E However, this did not work \definefont[dante][dante at 16pt] \starttext \dante DANTE \stoptext When I create a afm file from the dante.pfb then everything is fine. Does ConTeXt always needs an afm-file for the metrics of an type 1 font? And, of course, a map file? yes, because in context it gets a unicode encoding (which also means that you can access more than 256 characters if the font has them no more encodings Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ 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 ___
[NTG-context] TYPE 1 font
I have a pfb and tfm file of the DANTE font, which has only the five characters D,A,N,T,E However, this did not work \definefont[dante][dante at 16pt] \starttext \dante DANTE \stoptext When I create a afm file from the dante.pfb then everything is fine. Does ConTeXt always needs an afm-file for the metrics of an type 1 font? And, of course, a map file? Herbert ___ 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 ___
