Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Benjamin Buchmuller]

The problem seems to be resolved. Thanks to everyone, especially Hans, Taco and 
Wolfgang for the fast fix (offlist)!

After updating to

ConTeXt  ver: 2020.01.30 14:13 MKIV beta  fmt: 2020.4.26

Helvetica Neue works with:
==

\starttypescript [sans] [helvet]
   \setups[font:fallback:sans]
   \definefontsynonym [Sans]   [file:Helvetica Neue.ttc(Helvetica 
Neue)] [features=default]
   \definefontsynonym [SansBold]   [file:Helvetica Neue.ttc(Helvetica Neue 
Bold)]   [features=default]
   \definefontsynonym [SansItalic] [file:Helvetica Neue.ttc(Helvetica Neue 
Italic)]  [features=default]
   \definefontsynonym [SansBoldItalic] [file:Helvetica Neue.ttc(Helvetica Neue 
Bold Italic)] [features=default]
\stoptypescript

\definetypeface [helvet] [ss] [sans] [helvet] [default] 

\setupbodyfont [helvet, 12pt]

Optima works with:
==

\starttypescript [sans] [optima]
  \setups[font:fallback:sans]
  \definefontsynonym [Sans]   [file:Optima.ttc(Optima Regular)] 
[features=default]
  \definefontsynonym [SansBold]   [file:Optima.ttc(Optima Bold)]   
[features=default]
  \definefontsynonym [SansItalic] [file:Optima.ttc(Optima Italic)]  
[features=default]
  \definefontsynonym [SansBoldItalic] [file:Optima.ttc(Optima Bold Italic)] 
[features=default]
\stoptypescript

\definetypeface [optima] [ss] [sans] [optima] [default]

\setupbodyfont [optima]

\starttext
\tf Upright,
\bf Bold,
\it Italic,
\bi Bolditalic
\stoptext

Note 1: mtxrun --script fonts --list --all --pattern=helvetica etc. might still 
not display all variants correctly in the first place.

Note 2: There are predefined typescripts for Mac OS in ConTeXt 
(type-imp-osx.mkiv) but the file needs a update/cleanup.

> On 24 Apr 2020, at 12:14, Benjamin Buchmuller  
> wrote:
> 
> Hi Hraban,
> 
> Thanks for the hint (and the proper fontfamily setup), I have forced reload 
> ten times now from various accounts; the issue persists unfortunately. 
> 
> This might confirm Taco‘s notion that there is some bug lmtx. I’m running 
> macOS Catalina too, but as it worked with the standalone of Dec/Jan three 
> days ago, I suspect it is not because of a new feature in the OS, but rather 
> an old feature in mtxrun or elsewhere having disappeared. 
> 
>> On 24. Apr 2020, at 11:35, Henning Hraban Ramm  wrote:
>> 
>> 
>> 
>>> Am 24.04.2020 um 11:13 schrieb Benjamin Buchmuller 
>>> :
>>> 
>>> Although this specific issue might have been solved meanwhile by the 
>>> helpful suggestions of Wolfang, Thomas and others, I would like to point 
>>> out that I have recently also encountered an odd behaviour of the mtxrun 
>>> fontloader in the standalone, in which not all typefaces are 
>>> available/properly identified.
>>> 
>>> (I’m sorry to hijack this thread if this is unrelated.)
>>> 
>>> Basically, when I load “Helvetica Neue”, I get instead of “regular/normal” 
>>> always “light/italic”.
>>> 
>>> I have switched to heros for the meantime, but potentially there is some 
>>> bug behind this. (My documents with the version from Dec/Jan worked fine.)
>>> 
>>> I recite my example from Wed:
>>> 
>>> ConTeXt  ver: 2020.01.30 14:13 MKIV beta  fmt: 2020.4.22 (LuaTeX 1.11.1)
>>> 
>>> and I’m running now into troubles with system font indexing:
>>> 
>>> mtxrun --script fonts --reload
>>> 
>>> locates fonts in macOS directories appropriately (*.afm fonts placed in 
>>> .../tex/texmf-fonts are not found, but at the moment I don’t care too 
>>> much), however it resolves only to a single font variant for *.ttc instead 
>>> of all variants:
>>> 
>>> mtxrun --script fonts --list --all --pattern=helvetica
>>> 
>>> helvetica helvetica
>>> helveticalightoblique /System/Library/Fonts/Helvetica.ttc   
>>>  6
>>> helveticalightoblique helvetica
>>> helveticalightoblique /System/Library/Fonts/Helvetica.ttc   
>>>  6
>>> helveticaneuedeskinterfaceheavy   helveticaneuedeskinterface   
>>> helveticaneuedeskinterfaceheavy   
>>> /System/Library/Fonts/HelveticaNeueDeskInterface.ttc   10
>>> helveticaneuethinitalic   helveticaneue
>>> helveticaneuethinitalic   /System/Library/Fonts/HelveticaNeue.ttc   
>>>  14
>> 
>> If the subfont is not listed, ConTeXt/mtxrun couldn’t find it and won’t find 
>> it regardless of your setup.
>> 
>> Try
>> mtxrun --script fonts --reload --force
>> maybe even twice or thrice and check again.
>> (Unfortunately this is not reliable.)
>> 
>> I get the full list:
>> 
>> identifier   familyname   
>> fontname   filename  
>>  subfont   instances
>> 
>> helveticahelvetica
>> helvetica  
>> /System/Library/Fonts/Helvetica.ttc 

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Taco Hoekwater]

See this link:

https://wiki.contextgarden.net/Mac_Installation


In particular, you need this set of shell commands from that page:

mkdir $HOME/context
cd $HOME/context
rsync -av rsync://contextgarden.net/minimals/setup/first-setup.sh .
sh ./first-setup.sh --modules=all --engine=luatex

but we are currently investigating whether the problem may be binary-related,
because my mkiv started getting issues as well, so that may or may not work.

Also, it is possible that fonts work even though

  mtxrun --script fonts --list --all —pattern

does not list them.

And no, we are not sure why yet.

Taco

> On 24 Apr 2020, at 14:24, Gerben Wierda  wrote:
> 
> 
> 
>> On 24 Apr 2020, at 11:56, Taco Hoekwater  wrote:
>> 
>> Hi,
>> 
>> FYI, my "context mkiv” standalone seems to be fine (latest download). 
>> “lmtx” standalone (also latest download) not so much (same problems).
> 
> Thx. How do I get/install a ‘context mkiv’ standalone? The standalone on 
> http://www.pragma-ade.com/install.htm is only LMTX.
> 
> G
> 
>> 
>> Looks like something is broken in ltmx’ TTC parser.
>> 
>> OS X Catalina 10.15.4
>> 
>> Taco
>> ___
>> 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://context.aanhet.net
>> archive  : https://bitbucket.org/phg/context-mirror/commits/
>> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___

Taco Hoekwater
Elvenkind BV




___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Gerben Wierda]

> On 24 Apr 2020, at 11:56, Taco Hoekwater  wrote:
> 
> Hi,
> 
> FYI, my "context mkiv” standalone seems to be fine (latest download). 
> “lmtx” standalone (also latest download) not so much (same problems).

Thx. How do I get/install a ‘context mkiv’ standalone? The standalone on 
http://www.pragma-ade.com/install.htm  
is only LMTX.

G

> 
> Looks like something is broken in ltmx’ TTC parser.
> 
> OS X Catalina 10.15.4
> 
> Taco
> ___
> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Taco Hoekwater]

> On 24 Apr 2020, at 12:14, Benjamin Buchmuller  
> wrote:
> 
> Hi Hraban,
> 
> This might confirm Taco‘s notion that there is some bug lmtx. 

We have moved this off-list for a while. For now, if you have problems with 
lmtx, just
switch back to the regular mkiv standalone.

Best wishes,
Taco



___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Benjamin Buchmuller]

Hi Hraban,

Thanks for the hint (and the proper fontfamily setup), I have forced reload ten 
times now from various accounts; the issue persists unfortunately. 

This might confirm Taco‘s notion that there is some bug lmtx. I’m running macOS 
Catalina too, but as it worked with the standalone of Dec/Jan three days ago, I 
suspect it is not because of a new feature in the OS, but rather an old feature 
in mtxrun or elsewhere having disappeared. 

> On 24. Apr 2020, at 11:35, Henning Hraban Ramm  wrote:
> 
> 
> 
>> Am 24.04.2020 um 11:13 schrieb Benjamin Buchmuller 
>> :
>> 
>> Although this specific issue might have been solved meanwhile by the helpful 
>> suggestions of Wolfang, Thomas and others, I would like to point out that I 
>> have recently also encountered an odd behaviour of the mtxrun fontloader in 
>> the standalone, in which not all typefaces are available/properly identified.
>> 
>> (I’m sorry to hijack this thread if this is unrelated.)
>> 
>> Basically, when I load “Helvetica Neue”, I get instead of “regular/normal” 
>> always “light/italic”.
>> 
>> I have switched to heros for the meantime, but potentially there is some bug 
>> behind this. (My documents with the version from Dec/Jan worked fine.)
>> 
>> I recite my example from Wed:
>> 
>> ConTeXt  ver: 2020.01.30 14:13 MKIV beta  fmt: 2020.4.22 (LuaTeX 1.11.1)
>> 
>> and I’m running now into troubles with system font indexing:
>> 
>> mtxrun --script fonts --reload
>> 
>> locates fonts in macOS directories appropriately (*.afm fonts placed in 
>> .../tex/texmf-fonts are not found, but at the moment I don’t care too much), 
>> however it resolves only to a single font variant for *.ttc instead of all 
>> variants:
>> 
>> mtxrun --script fonts --list --all --pattern=helvetica
>> 
>> helvetica helvetica
>> helveticalightoblique /System/Library/Fonts/Helvetica.ttc
>> 6
>> helveticalightoblique helvetica
>> helveticalightoblique /System/Library/Fonts/Helvetica.ttc
>> 6
>> helveticaneuedeskinterfaceheavy   helveticaneuedeskinterface   
>> helveticaneuedeskinterfaceheavy   
>> /System/Library/Fonts/HelveticaNeueDeskInterface.ttc   10
>> helveticaneuethinitalic   helveticaneue
>> helveticaneuethinitalic   /System/Library/Fonts/HelveticaNeue.ttc
>> 14
> 
> If the subfont is not listed, ConTeXt/mtxrun couldn’t find it and won’t find 
> it regardless of your setup.
> 
> Try
> mtxrun --script fonts --reload --force
> maybe even twice or thrice and check again.
> (Unfortunately this is not reliable.)
> 
> I get the full list:
> 
> identifier   familyname   
> fontname   filename   
> subfont   instances
> 
> helveticahelvetica
> helvetica  
> /System/Library/Fonts/Helvetica.ttc1
> helveticaneueblack   helveticaneue
> helveticaneuecondensedblack
> /System/Library/Fonts/HelveticaNeue.ttc10
> helveticaneuedeskinterfaceextrabold  helveticaneuedeskinterface   
> helveticaneuedeskinterfaceheavy
> /System/Library/Fonts/HelveticaNeueDeskInterface.ttc   10
> helveticaneuedeskinterfaceextralight helveticaneuedeskinterface   
> helveticaneuedeskinterfacethin 
> /System/Library/Fonts/HelveticaNeueDeskInterface.ttc   8
> helveticaneuedeskinterfacemedium helveticaneuedeskinterface   
> helveticaneuedeskinterfacemediump4 
> /System/Library/Fonts/HelveticaNeueDeskInterface.ttc   5
> helveticaneuedeskinterfacemediumitalic   helveticaneuedeskinterface   
> helveticaneuedeskinterfacemediumitalicp4   
> /System/Library/Fonts/HelveticaNeueDeskInterface.ttc   6
> helveticaneuedeskinterfacenormal helveticaneuedeskinterface   
> helveticaneuedeskinterfaceregular  
> /System/Library/Fonts/HelveticaNeueDeskInterface.ttc   1
> helveticaneueextralight  helveticaneue
> helveticaneuethin  
> /System/Library/Fonts/HelveticaNeue.ttc13
> helveticaneuenormal  helveticaneue
> helveticaneue  
> /System/Library/Fonts/HelveticaNeue.ttc1
> helveticaneueregular helveticaneue
> helveticaneue  
> /System/Library/Fonts/HelveticaNeue.ttc1
> helveticanormal  helvetica
> helvetica  
> /System/Library/Fonts/Helvetica.ttc1
> helveticaregular helvetica
> helvetica  
> 

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Taco Hoekwater]

Hi,

FYI, my "context mkiv” standalone seems to be fine (latest download). 
“lmtx” standalone (also latest download) not so much (same problems).

Looks like something is broken in ltmx’ TTC parser.

OS X Catalina 10.15.4

Taco
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Henning Hraban Ramm]

> Am 24.04.2020 um 11:13 schrieb Benjamin Buchmuller 
> :
> 
> Although this specific issue might have been solved meanwhile by the helpful 
> suggestions of Wolfang, Thomas and others, I would like to point out that I 
> have recently also encountered an odd behaviour of the mtxrun fontloader in 
> the standalone, in which not all typefaces are available/properly identified.
> 
> (I’m sorry to hijack this thread if this is unrelated.)
> 
> Basically, when I load “Helvetica Neue”, I get instead of “regular/normal” 
> always “light/italic”.
> 
> I have switched to heros for the meantime, but potentially there is some bug 
> behind this. (My documents with the version from Dec/Jan worked fine.)
> 
> I recite my example from Wed:
> 
> ConTeXt  ver: 2020.01.30 14:13 MKIV beta  fmt: 2020.4.22 (LuaTeX 1.11.1)
> 
> and I’m running now into troubles with system font indexing:
> 
> mtxrun --script fonts --reload
> 
> locates fonts in macOS directories appropriately (*.afm fonts placed in 
> .../tex/texmf-fonts are not found, but at the moment I don’t care too much), 
> however it resolves only to a single font variant for *.ttc instead of all 
> variants:
> 
> mtxrun --script fonts --list --all --pattern=helvetica
> 
> helvetica helvetica
> helveticalightoblique /System/Library/Fonts/Helvetica.ttc 
>6
> helveticalightoblique helvetica
> helveticalightoblique /System/Library/Fonts/Helvetica.ttc 
>6
> helveticaneuedeskinterfaceheavy   helveticaneuedeskinterface   
> helveticaneuedeskinterfaceheavy   
> /System/Library/Fonts/HelveticaNeueDeskInterface.ttc   10
> helveticaneuethinitalic   helveticaneue
> helveticaneuethinitalic   /System/Library/Fonts/HelveticaNeue.ttc 
>14

If the subfont is not listed, ConTeXt/mtxrun couldn’t find it and won’t find it 
regardless of your setup.

Try
mtxrun --script fonts --reload --force
maybe even twice or thrice and check again.
(Unfortunately this is not reliable.)

I get the full list:

identifier   familyname   fontname  
 filename   
subfont   instances

helveticahelveticahelvetica 
 /System/Library/Fonts/Helvetica.ttc
1
helveticaneueblack   helveticaneue
helveticaneuecondensedblack
/System/Library/Fonts/HelveticaNeue.ttc10
helveticaneuedeskinterfaceextrabold  helveticaneuedeskinterface   
helveticaneuedeskinterfaceheavy
/System/Library/Fonts/HelveticaNeueDeskInterface.ttc   10
helveticaneuedeskinterfaceextralight helveticaneuedeskinterface   
helveticaneuedeskinterfacethin 
/System/Library/Fonts/HelveticaNeueDeskInterface.ttc   8
helveticaneuedeskinterfacemedium helveticaneuedeskinterface   
helveticaneuedeskinterfacemediump4 
/System/Library/Fonts/HelveticaNeueDeskInterface.ttc   5
helveticaneuedeskinterfacemediumitalic   helveticaneuedeskinterface   
helveticaneuedeskinterfacemediumitalicp4   
/System/Library/Fonts/HelveticaNeueDeskInterface.ttc   6
helveticaneuedeskinterfacenormal helveticaneuedeskinterface   
helveticaneuedeskinterfaceregular  
/System/Library/Fonts/HelveticaNeueDeskInterface.ttc   1
helveticaneueextralight  helveticaneue
helveticaneuethin  
/System/Library/Fonts/HelveticaNeue.ttc13
helveticaneuenormal  helveticaneue
helveticaneue  
/System/Library/Fonts/HelveticaNeue.ttc1
helveticaneueregular helveticaneue
helveticaneue  
/System/Library/Fonts/HelveticaNeue.ttc1
helveticanormal  helveticahelvetica 
 /System/Library/Fonts/Helvetica.ttc
1
helveticaregular helveticahelvetica 
 /System/Library/Fonts/Helvetica.ttc
1



> As a consequence, when I run
> 
> \definefontfamily[mainface][ss][Helvetica Neue]
> \setupbodyfont[mainface, 12pt, sans]
> 
> I get the light oblique variant instead of the regular one. I have tried to 
> fix this via a 
> 
> \definefontfamily[mainface][ss][Helvetica Neue][tf=style:normal]

tf=helveticaregular
should work.


Best, Hraban

___
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  : 

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Benjamin Buchmuller]

Although this specific issue might have been solved meanwhile by the helpful 
suggestions of Wolfang, Thomas and others, I would like to point out that I 
have recently also encountered an odd behaviour of the mtxrun fontloader in the 
standalone, in which not all typefaces are available/properly identified.

(I’m sorry to hijack this thread if this is unrelated.)

Basically, when I load “Helvetica Neue”, I get instead of “regular/normal” 
always “light/italic”.

I have switched to heros for the meantime, but potentially there is some bug 
behind this. (My documents with the version from Dec/Jan worked fine.)

I recite my example from Wed:

ConTeXt  ver: 2020.01.30 14:13 MKIV beta  fmt: 2020.4.22 (LuaTeX 1.11.1)

and I’m running now into troubles with system font indexing:

mtxrun --script fonts --reload

locates fonts in macOS directories appropriately (*.afm fonts placed in 
.../tex/texmf-fonts are not found, but at the moment I don’t care too much), 
however it resolves only to a single font variant for *.ttc instead of all 
variants:

mtxrun --script fonts --list --all --pattern=helvetica

helvetica helvetica
helveticalightoblique /System/Library/Fonts/Helvetica.ttc   
 6
helveticalightoblique helvetica
helveticalightoblique /System/Library/Fonts/Helvetica.ttc   
 6
helveticaneuedeskinterfaceheavy   helveticaneuedeskinterface   
helveticaneuedeskinterfaceheavy   
/System/Library/Fonts/HelveticaNeueDeskInterface.ttc   10
helveticaneuethinitalic   helveticaneue
helveticaneuethinitalic   /System/Library/Fonts/HelveticaNeue.ttc   
 14

As a consequence, when I run

\definefontfamily[mainface][ss][Helvetica Neue]
\setupbodyfont[mainface, 12pt, sans]

I get the light oblique variant instead of the regular one. I have tried to fix 
this via a 

\definefontfamily[mainface][ss][Helvetica Neue][tf=style:normal]

but apparently I understand too little about this setup altogether …

Thanks already for any suggestions!



> On 24 Apr 2020, at 08:53, ntg-context-requ...@ntg.nl wrote:
> 
> Send ntg-context mailing list submissions to
>   ntg-context@ntg.nl
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://mailman.ntg.nl/mailman/listinfo/ntg-context
> or, via email, send a message with subject or body 'help' to
>   ntg-context-requ...@ntg.nl
> 
> You can reach the person managing the list at
>   ntg-context-ow...@ntg.nl
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ntg-context digest..."
> Today's Topics:
> 
>   1. Re: Basic font question (Optima, but no bold, no italics).
>  Standalone ConTeXt does not work. TeX Live 2019 works
>      (Wolfgang Schuster)
> 
> From: Wolfgang Schuster 
> Subject: Re: [NTG-context] Basic font question (Optima, but no bold, no 
> italics). Standalone ConTeXt does not work. TeX Live 2019 works
> Date: 24 April 2020 at 08:53:52 CEST
> To: mailing list for ConTeXt users , Gerben Wierda 
> 
> 
> 
> Gerben Wierda schrieb am 24.04.2020 um 08:48:
>> With Arial:
>> 
>> \definefontfamily[mainface][rm][Arial]
>> \setupbodyfont[mainface,10pt]
>> 
>> 
>> 
>> with Optima:
>> 
>> \definefontfamily[mainface][rm][Optima]
>> \setupbodyfont[mainface,10pt]
>> 
>> 
>> It doesn’t matter if the font statements are before or after \starttext
>> 
>> Then I thought, let’s test some other things. I logged in as another user, 
>> and used ConTeXt from TeX Live 2019:
>> 
>> 
>> It seems to be that on my system, the standalone installed ConTeXt does not 
>> work with Optima, but the TeX Live installed one does.
> 
> Can you try this:
> 
> \definefontfamily [mainface] [rm] [Optima]
>   [it=optimaitalic,
>bf=optimabold,
>bi=optimabolditalic]
> 
> 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  : https://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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Thomas A. Schmitz]

> On 24. Apr 2020, at 09:21, Gerben Wierda  wrote:
> 
> 
> I altready did that earlier as per the Wiki information (did not report it) 
> and just tried again. No difference.

Steps to happiness:

1. Extract the ttc font to ttf
2. Copy the ttf files to your local texmf directory
3. reload the font cache
4. enrich your vocabulary by learning the words “thank you”
5. never have to deal with stupid people who didn’t read all 10,000 lines of 
the log file you posted
6. profit!

Thomas
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Gerben Wierda]

> On 24 Apr 2020, at 08:53, Wolfgang Schuster 
>  wrote:
> 
> Can you try this:
> 
> \definefontfamily [mainface] [rm] [Optima]
>   [it=optimaitalic,
>bf=optimabold,
>bi=optimabolditalic]

I altready did that earlier as per the Wiki information (did not report it) and 
just tried again. No difference.

G

___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Gerben Wierda]

With Arial:

\definefontfamily[mainface][rm][Arial]
\setupbodyfont[mainface,10pt]



with Optima:

\definefontfamily[mainface][rm][Optima]
\setupbodyfont[mainface,10pt]


It doesn’t matter if the font statements are before or after \starttext

Then I thought, let’s test some other things. I logged in as another user, and 
used ConTeXt from TeX Live 2019:


It seems to be that on my system, the standalone installed ConTeXt does not 
work with Optima, but the TeX Live installed one does.

G



> On 24 Apr 2020, at 08:09, Henning Hraban Ramm  wrote:
> 
> 
> 
>> Am 24.04.2020 um 05:19 schrieb kaddour kardio :
>> 
>> It's noticed that Optima is a Sans Serif font.
>> Maybe it conflicts with MacOS way to handle fonts. 
> 
> No, ConTeXt doesn’t care what kind of font you define as rm/ss/tt, and the OS 
> has no say in that.
> 
> Best, Hraban
> 
> ___
> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Henning Hraban Ramm]

> Am 24.04.2020 um 08:48 schrieb Gerben Wierda :
> 
> Then I thought, let’s test some other things. I logged in as another user, 
> and used ConTeXt from TeX Live 2019:
> 
> 
> It seems to be that on my system, the standalone installed ConTeXt does not 
> work with Optima, but the TeX Live installed one does.

So what’s your ConTeXt version?

context --version
current version: 2020.01.30 14:13

luatex --version
This is LuaTeX, Version 1.11.1 (TeX Live 2020/dev)


Best, Hraban
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics). Standalone ConTeXt does not work. TeX Live 2019 works

[Wolfgang Schuster]

Gerben Wierda schrieb am 24.04.2020 um 08:48:

With Arial:

\definefontfamily[mainface][rm][Arial]
\setupbodyfont[mainface,10pt]


with Optima:

\definefontfamily[mainface][rm][Optima]
\setupbodyfont[mainface,10pt]

It doesn’t matter if the font statements are before or after \starttext

Then I thought, let’s test some other things. I logged in as another 
user, and used ConTeXt from TeX Live 2019:


It seems to be that on my system, the standalone installed ConTeXt 
does not work with Optima, but the TeX Live installed one does.


Can you try this:

\definefontfamily [mainface] [rm] [Optima]
  [it=optimaitalic,
   bf=optimabold,
   bi=optimabolditalic]

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics)

[Henning Hraban Ramm]

> Am 24.04.2020 um 05:19 schrieb kaddour kardio :
> 
> It's noticed that Optima is a Sans Serif font.
> Maybe it conflicts with MacOS way to handle fonts. 

No, ConTeXt doesn’t care what kind of font you define as rm/ss/tt, and the OS 
has no say in that.

Best, Hraban

___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics)

[Henning Hraban Ramm]

> Am 24.04.2020 um 02:10 schrieb Vladimir Lomov :
> 
> 
> I think Henning Hraban Ramm meant not OS font cache (but may be including it,
> I'm not a Mac OS user) but context font cache. Run
> 
> $ mtxrun --script fonts --reload --force
> 
> and try above '--list --all ...' command again

No, since all the subfonts were already found, that’s not the problem.


> and your example:
> 
>> \starttext
>> \definefontfamily[mainface][rm][Optima]
>> \setupbodyfont[mainface,10pt]
> 
>> {\bf Bold} and {\it Italic} and {\rm Regular} text.
>> \stoptext

The font definition belongs before \starttext. Good if it works...

But Gerben’s example was lacking \starttext .. \stoptext – didn’t try, but that 
might be the culprit.

Best, Hraban
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics)

[kaddour kardio]

It's noticed that Optima is a Sans Serif font.
Maybe it conflicts with MacOS way to handle fonts.


Le ven. 24 avr. 2020 à 01:10, Vladimir Lomov  a écrit :

> Hello,
> ** Gerben Wierda  [2020-04-23 23:57:26 +0200]:
>
> >> On 23 Apr 2020, at 19:18, Henning Hraban Ramm  wrote:
> >>
> >>>
> >>> Am 23.04.2020 um 16:42 schrieb Gerben Wierda :
> >>>
> 
>  On 23 Apr 2020, at 16:34, Henning Hraban Ramm  wrote:
> 
>
> [...]
>
>  What do you get from
>  mtxrun --script=fonts --list --all --pattern=Optima
> >>>
> >>> hermione:Export and Metapost gerben$ mtxrun --script fonts --list
> --all --pattern=optima
> >>> identifier familyname   fontname   filename
>subfont   instances
> >>>
> >>> optimablackoptima   optimaextrablack
>  /System/Library/Fonts/Optima.ttc   5
> >>> optimabold optima   optimabold
>  /System/Library/Fonts/Optima.ttc   2
> >>> optimabolditalic   optima   optimabolditalic
>  /System/Library/Fonts/Optima.ttc   4
> >>> optimaextrablack   optima   optimaextrablack
>  /System/Library/Fonts/Optima.ttc   5
> >>> optimaitalic   optima   optimaitalic
>  /System/Library/Fonts/Optima.ttc   3
> >>> optimanormal   optima   optimaregular
> /System/Library/Fonts/Optima.ttc   1
> >>> optimaregular  optima   optimaregular
> /System/Library/Fonts/Optima.ttc   1
> >>
> >> Hm. Here, ConTeXt only found subfont #5 until I rebuilt the font cache,
> then it looked like yours.
> >>
> >> And the minimal example (plus \starttext ... \stoptext) worked.
> >>
> >> (Latest ConTeXt on MacOS Mojave.)
>
> > No such luck for me. Any help welcome. I did remove the macOS font cache
> > with sudo atsutil databases -remove and I rebooted. I am running an up to
> > date macOS Mojave.
>
> I think Henning Hraban Ramm meant not OS font cache (but may be including
> it,
> I'm not a Mac OS user) but context font cache. Run
>
> $ mtxrun --script fonts --reload --force
>
> and try above '--list --all ...' command again and your example:
>
> > \starttext
> > \definefontfamily[mainface][rm][Optima]
> > \setupbodyfont[mainface,10pt]
>
> > {\bf Bold} and {\it Italic} and {\rm Regular} text.
> > \stoptext
>
> Hope this will resolve you issue.
>
> [...]
>
> ---
> WBR, Vladimir Lomov
>
> --
> Practically perfect people never permit sentiment to muddle their thinking.
> -- Mary Poppins
>
> ___
> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics)

[Vladimir Lomov]

Hello,
** Gerben Wierda  [2020-04-23 23:57:26 +0200]:

>> On 23 Apr 2020, at 19:18, Henning Hraban Ramm  wrote:
>> 
>>> 
>>> Am 23.04.2020 um 16:42 schrieb Gerben Wierda :
>>> 
 
 On 23 Apr 2020, at 16:34, Henning Hraban Ramm  wrote:
 

[...]

 What do you get from
 mtxrun --script=fonts --list --all --pattern=Optima
>>> 
>>> hermione:Export and Metapost gerben$ mtxrun --script fonts --list --all 
>>> --pattern=optima
>>> identifier familyname   fontname   filename 
>>>   subfont   instances
>>> 
>>> optimablackoptima   optimaextrablack   
>>> /System/Library/Fonts/Optima.ttc   5
>>> optimabold optima   optimabold 
>>> /System/Library/Fonts/Optima.ttc   2
>>> optimabolditalic   optima   optimabolditalic   
>>> /System/Library/Fonts/Optima.ttc   4
>>> optimaextrablack   optima   optimaextrablack   
>>> /System/Library/Fonts/Optima.ttc   5
>>> optimaitalic   optima   optimaitalic   
>>> /System/Library/Fonts/Optima.ttc   3
>>> optimanormal   optima   optimaregular  
>>> /System/Library/Fonts/Optima.ttc   1
>>> optimaregular  optima   optimaregular  
>>> /System/Library/Fonts/Optima.ttc   1
>> 
>> Hm. Here, ConTeXt only found subfont #5 until I rebuilt the font cache, then 
>> it looked like yours.
>> 
>> And the minimal example (plus \starttext ... \stoptext) worked.
>> 
>> (Latest ConTeXt on MacOS Mojave.)

> No such luck for me. Any help welcome. I did remove the macOS font cache
> with sudo atsutil databases -remove and I rebooted. I am running an up to
> date macOS Mojave.

I think Henning Hraban Ramm meant not OS font cache (but may be including it,
I'm not a Mac OS user) but context font cache. Run

$ mtxrun --script fonts --reload --force

and try above '--list --all ...' command again and your example:

> \starttext
> \definefontfamily[mainface][rm][Optima]
> \setupbodyfont[mainface,10pt]

> {\bf Bold} and {\it Italic} and {\rm Regular} text.
> \stoptext

Hope this will resolve you issue.

[...]

---
WBR, Vladimir Lomov

-- 
Practically perfect people never permit sentiment to muddle their thinking.
-- Mary Poppins


signature.asc
Description: PGP signature
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question (Optima, but no bold, no italics)

[Gerben Wierda]

> On 23 Apr 2020, at 19:18, Henning Hraban Ramm  wrote:
> 
>> 
>> Am 23.04.2020 um 16:42 schrieb Gerben Wierda :
>> 
>>> 
>>> On 23 Apr 2020, at 16:34, Henning Hraban Ramm  wrote:
>>> 
 
 Am 23.04.2020 um 16:22 schrieb Gerben Wierda :
 
 
 
> On 23 Apr 2020, at 16:16, Vladimir Lomov  wrote:
> 
> Hello,
> ** Gerben Wierda  [2020-04-23 16:00:34 +0200]:
> 
>> On my Mac, I am trying:
> 
>> \definefontfamily[mainface][rm][Optima]
>> \setupbodyfont[mainface,10pt]
> 
>> {\bf Bold} and {\it Italic} and {\rm Regular} text.
> 
> https://wiki.contextgarden.net/Font_Switching
> 
>> What do I need to do to get actual bold and italics in my output?
> 
> \bi == \bf\it
> 
> Or by "actual bold" you mean something different?
 
 Yes, in my output everything is regular, there is no bold or italics text, 
 even when I use \bf or \it
>>> 
>>> What do you get from
>>> mtxrun --script=fonts --list --all --pattern=Optima
>> 
>> hermione:Export and Metapost gerben$ mtxrun --script fonts --list --all 
>> --pattern=optima
>> identifier familyname   fontname   filename  
>>  subfont   instances
>> 
>> optimablackoptima   optimaextrablack   
>> /System/Library/Fonts/Optima.ttc   5
>> optimabold optima   optimabold 
>> /System/Library/Fonts/Optima.ttc   2
>> optimabolditalic   optima   optimabolditalic   
>> /System/Library/Fonts/Optima.ttc   4
>> optimaextrablack   optima   optimaextrablack   
>> /System/Library/Fonts/Optima.ttc   5
>> optimaitalic   optima   optimaitalic   
>> /System/Library/Fonts/Optima.ttc   3
>> optimanormal   optima   optimaregular  
>> /System/Library/Fonts/Optima.ttc   1
>> optimaregular  optima   optimaregular  
>> /System/Library/Fonts/Optima.ttc   1
> 
> Hm. Here, ConTeXt only found subfont #5 until I rebuilt the font cache, then 
> it looked like yours.
> 
> And the minimal example (plus \starttext ... \stoptext) worked.
> 
> (Latest ConTeXt on MacOS Mojave.)


No such luck for me. Any help welcome. I did remove the macOS font cache with 
sudo atsutil databases -remove and I rebooted. I am running an up to date macOS 
Mojave.

\starttext
\definefontfamily[mainface][rm][Optima]
\setupbodyfont[mainface,10pt]

{\bf Bold} and {\it Italic} and {\rm Regular} text.
\stoptext

results in



Gerben Wierda
Chess and the Art of Enterprise Architecture 
Mastering ArchiMate 
Architecture for Real Enterprises 
 at InfoWorld
On Slippery Ice  at EAPJ

Console:

$ context test.tex

resolvers   | formats | executing runner 'run luametatex format': 
/usr/local/context-osx-64/tex/texmf-osx-64/bin/luametatex --jobname="test" 
--fmt=/usr/local/context-osx-64/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
 
--lua=/usr/local/context-osx-64/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui
 cont-yes.mkiv --c:currentrun=1 --c:fulljobname="./test.tex" 
--c:input="./test.tex" --c:kindofrun=1 --c:maxnofruns=9 
--c:texmfbinpath="/usr/local/context-osx-64/tex/texmf-osx-64/bin"
This is LuaMetaTeX, Version 2.05.01 
open source > level 1, order 1, name 'cont-yes.mkiv'
system  > 
system  > ConTeXt  ver: 2020.04.03 10:31 MKIV beta  fmt: 2020.4.7  int: 
english/english
system  > 
system  > 'cont-new.mkiv' loaded
open source > level 2, order 2, name 
'/usr/local/context-osx-64/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
system  > beware: some patches loaded from cont-new.mkiv
close source> level 2, order 2, name 
'/usr/local/context-osx-64/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
system  > files > jobname 'test', input './test', result 'test'
fonts   > latin modern fonts are not preloaded
languages   > language 'en' is active
open source > level 2, order 3, name './test.tex'
fonts   > preloading latin modern fonts (second stage)
fonts   > 'fallback modern-designsize rm 12pt' is loaded
backend > xmp > using file 
'/usr/local/context-osx-64/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml'
pages   > flushing realpage 1, userpage 1, subpage 1
close source> level 2, order 3, name './test.tex'
close source> level 1, order 3, name 'cont-yes.mkiv'

mkiv lua stats  > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua
mkiv lua stats  > used cache path: 
/usr/local/context-osx-64/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e
mkiv lua stats  > resource resolver: loadtime 0.006 seconds, 0 scans with 
scantime 0.000 seconds, 0 shared scans, 12 found files, scanned paths: 
mkiv lua stats 

Re: [NTG-context] Basic font question

[Henning Hraban Ramm]

> Am 23.04.2020 um 16:42 schrieb Gerben Wierda :
> 
>> 
>> On 23 Apr 2020, at 16:34, Henning Hraban Ramm  wrote:
>> 
>>> 
>>> Am 23.04.2020 um 16:22 schrieb Gerben Wierda :
>>> 
>>> 
>>> 
 On 23 Apr 2020, at 16:16, Vladimir Lomov  wrote:
 
 Hello,
 ** Gerben Wierda  [2020-04-23 16:00:34 +0200]:
 
> On my Mac, I am trying:
 
> \definefontfamily[mainface][rm][Optima]
> \setupbodyfont[mainface,10pt]
 
> {\bf Bold} and {\it Italic} and {\rm Regular} text.
 
 https://wiki.contextgarden.net/Font_Switching
 
> What do I need to do to get actual bold and italics in my output?
 
 \bi == \bf\it
 
 Or by "actual bold" you mean something different?
>>> 
>>> Yes, in my output everything is regular, there is no bold or italics text, 
>>> even when I use \bf or \it
>> 
>> What do you get from
>> mtxrun --script=fonts --list --all --pattern=Optima
> 
> hermione:Export and Metapost gerben$ mtxrun --script fonts --list --all 
> --pattern=optima
> identifier familyname   fontname   filename   
> subfont   instances
> 
> optimablackoptima   optimaextrablack   
> /System/Library/Fonts/Optima.ttc   5
> optimabold optima   optimabold 
> /System/Library/Fonts/Optima.ttc   2
> optimabolditalic   optima   optimabolditalic   
> /System/Library/Fonts/Optima.ttc   4
> optimaextrablack   optima   optimaextrablack   
> /System/Library/Fonts/Optima.ttc   5
> optimaitalic   optima   optimaitalic   
> /System/Library/Fonts/Optima.ttc   3
> optimanormal   optima   optimaregular  
> /System/Library/Fonts/Optima.ttc   1
> optimaregular  optima   optimaregular  
> /System/Library/Fonts/Optima.ttc   1

Hm. Here, ConTeXt only found subfont #5 until I rebuilt the font cache, then it 
looked like yours.

And the minimal example (plus \starttext ... \stoptext) worked.

(Latest ConTeXt on MacOS Mojave.)

Best, Hraban
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question

[Gerben Wierda]

> On 23 Apr 2020, at 16:34, Henning Hraban Ramm  wrote:
> 
>> 
>> Am 23.04.2020 um 16:22 schrieb Gerben Wierda :
>> 
>> 
>> 
>>> On 23 Apr 2020, at 16:16, Vladimir Lomov  wrote:
>>> 
>>> Hello,
>>> ** Gerben Wierda  [2020-04-23 16:00:34 +0200]:
>>> 
 On my Mac, I am trying:
>>> 
 \definefontfamily[mainface][rm][Optima]
 \setupbodyfont[mainface,10pt]
>>> 
 {\bf Bold} and {\it Italic} and {\rm Regular} text.
>>> 
>>> https://wiki.contextgarden.net/Font_Switching
>>> 
 What do I need to do to get actual bold and italics in my output?
>>> 
>>> \bi == \bf\it
>>> 
>>> Or by "actual bold" you mean something different?
>> 
>> Yes, in my output everything is regular, there is no bold or italics text, 
>> even when I use \bf or \it
> 
> What do you get from
> mtxrun --script=fonts --list --all --pattern=Optima

hermione:Export and Metapost gerben$ mtxrun --script fonts --list --all 
--pattern=optima
identifier familyname   fontname   filename 
  subfont   instances

optimablackoptima   optimaextrablack   
/System/Library/Fonts/Optima.ttc   5
optimabold optima   optimabold 
/System/Library/Fonts/Optima.ttc   2
optimabolditalic   optima   optimabolditalic   
/System/Library/Fonts/Optima.ttc   4
optimaextrablack   optima   optimaextrablack   
/System/Library/Fonts/Optima.ttc   5
optimaitalic   optima   optimaitalic   
/System/Library/Fonts/Optima.ttc   3
optimanormal   optima   optimaregular  
/System/Library/Fonts/Optima.ttc   1
optimaregular  optima   optimaregular  
/System/Library/Fonts/Optima.ttc   1

> ?
> 
> Best, Hraban
> ___
> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question

[Gerben Wierda]

> On 23 Apr 2020, at 16:16, Vladimir Lomov  wrote:
> 
> Hello,
> ** Gerben Wierda  [2020-04-23 16:00:34 +0200]:
> 
>> On my Mac, I am trying:
> 
>> \definefontfamily[mainface][rm][Optima]
>> \setupbodyfont[mainface,10pt]
> 
>> {\bf Bold} and {\it Italic} and {\rm Regular} text.
> 
> https://wiki.contextgarden.net/Font_Switching
> 
>> What do I need to do to get actual bold and italics in my output?
> 
> \bi == \bf\it
> 
> Or by "actual bold" you mean something different?

Yes, in my output everything is regular, there is no bold or italics text, even 
when I use \bf or \it

G

> 
>> Thx,
> 
>> G
> 
> ---
> WBR, Vladimir Lomov
> 
> -- 
> There has been an alarming increase in the number of things you know
> nothing about.
> ___
> 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://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question

[Henning Hraban Ramm]

> Am 23.04.2020 um 16:22 schrieb Gerben Wierda :
> 
> 
> 
>> On 23 Apr 2020, at 16:16, Vladimir Lomov  wrote:
>> 
>> Hello,
>> ** Gerben Wierda  [2020-04-23 16:00:34 +0200]:
>> 
>>> On my Mac, I am trying:
>> 
>>> \definefontfamily[mainface][rm][Optima]
>>> \setupbodyfont[mainface,10pt]
>> 
>>> {\bf Bold} and {\it Italic} and {\rm Regular} text.
>> 
>> https://wiki.contextgarden.net/Font_Switching
>> 
>>> What do I need to do to get actual bold and italics in my output?
>> 
>> \bi == \bf\it
>> 
>> Or by "actual bold" you mean something different?
> 
> Yes, in my output everything is regular, there is no bold or italics text, 
> even when I use \bf or \it

What do you get from
mtxrun --script=fonts --list --all --pattern=Optima
?

Best, Hraban
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Basic font question

[Vladimir Lomov]

Hello,
** Gerben Wierda  [2020-04-23 16:00:34 +0200]:

> On my Mac, I am trying:

> \definefontfamily[mainface][rm][Optima]
> \setupbodyfont[mainface,10pt]

> {\bf Bold} and {\it Italic} and {\rm Regular} text.

https://wiki.contextgarden.net/Font_Switching

> What do I need to do to get actual bold and italics in my output?

\bi == \bf\it

Or by "actual bold" you mean something different?

> Thx,

> G

---
WBR, Vladimir Lomov

-- 
There has been an alarming increase in the number of things you know
nothing about.


signature.asc
Description: PGP signature
___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

[NTG-context] Basic font question

[Gerben Wierda]

On my Mac, I am trying:

\definefontfamily[mainface][rm][Optima]
\setupbodyfont[mainface,10pt]

{\bf Bold} and {\it Italic} and {\rm Regular} text.

What do I need to do to get actual bold and italics in my output?

Thx,

G___
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] Virtual font question

[Zhichu Chen]

Hi everybody,

I finally got my typescript work. It was the serif typeface that 
failed me. When I defined the fixed size type:

===
\definetypeface [mathtimespro] [rm] [serif] [times] [default]
\definetypeface [mathtimespro] [ss] [sans] [helvetica] 
[default] [rscale=0.9]
\definetypeface [mathtimespro] [tt] [mono] [courier]   
[default] [rscale=1.1]
\definetypeface [mathtimespro] [mm] [math] [mathtimespro]
[default]

===
where mathtimespro in the last line was defined as:
===
\definefontsynonym [MathTimeProA-Regular] 
[MTP06A-Regular@mtpro06a-regular]

===
Everything was fine. But the designsize version needs to be:
===
\definetypeface [mathtimespro] [rm] [serif] [times] 
[default][designsize=auto]
\definetypeface [mathtimespro] [ss] [sans]  [helvetica] 
[default] [rscale=0.9]
\definetypeface [mathtimespro] [tt] [mono]  [courier] [default] 
[rscale=1.1]
\definetypeface [mathtimespro] [mm] [math] [mathtimespro]
[default][designsize=auto]

===
Without the last parameter in the serif definition, the math font could 
not be remapped (WHY???).


Fix me if I'm wrong about this conclusion.


Best regards,
Zhichu

On 06/23/2015 01:20 PM, Zhichu Chen wrote:

Hi Aditya,


On 06/23/2015 11:57 AM, Aditya Mahajan wrote:
I don't have the fonts, so I cannot describe the exact method. But 
see below and also have a look at Section 5 of
https://www.tug.org/TUGboat/tb30-2/tb95mahajan-cmath.pdf The 
description is old, and some of the file locations have changes, but 
the basic infrastructure is still the same.

Thank you for sharing this article. It seems that the
===
return {
mathematics = {
mapfiles = {
mtpro2.map,
},
virtuals = {
[mtpro06a-regular] = {
...
===
codes may have done the job in the mathematics.make_font function.

In this snippet:
===
\definefontsynonym
  [LMMathRoman10-Regular]
  [LMMath10-Regular@lmroman10-math]
===
I know that LMMathRoman10-Regular will be used as the font synonym, 
@lmroman10-math is the
virtual font, but what does LMMath10-Regular stand for? I chose some 
random names in my typescript

but maybe there's some magic there?
The vectors mptpro2-mi etc are not defined. Look at math-ttv.lua for 
a list of predefined vectors (mapping type1 fonts to unicode symbols. 
It is quite likely that the mtpro fonts would follow the standard 
mappings; if not, you will need to create an approrpriate mapping for 
each font. This is not difficult (just monotonous).
I've already defined these vectors in the same .lfg file. What a 
tedious work it was, by the way. I thought
that would be irrelevant, so I skipped those codes. I'm sorry I didn't 
make that clear.


I almost forgot to mention. The font has its own \Relbar and \relbar 
characters rather than the equality
and the dash marks. What is the best way to use them? I currently put 
them in a private-use-area slot

in the vectors' definitions, but I'm not sure that's a good solution.



===
I guess the suffixes f s and t may correspond to five 
seven and ten, but that's
not important. I could use one of them as the virtual font in the 
typescript:


Once this is done, rest of the typescript should work. It may be a 
good idea to try to see if you can get roman letters from mtpro.

If I claimed the font synonym with the virtual font directly:
===
# typescripts
\definefontsynonym [\s!MathRoman] [MTPro10a-Regular@mtpro10a-regular]
===
the 10-size-version fonts were loaded without any problem. But if I 
want to use the designsize feature:

===
-- lfg
designsizes = {
[MathTimeProA-Regular] = {
[4pt]  = MTPro06a-Regular@mtpro06a-regular,
[5pt]  = MTPro06a-Regular@mtpro06a-regular,
[6pt]  = MTPro06a-Regular@mtpro06a-regular,
...
# typescripts
\definefontsynonym [\s!MathRoman] [\v!file:mathtimeproa-regular]
===
the mathtimeproa-regular font could not be remapped to the correct 
virtual font with the appropriate size.
I 

[NTG-context] Virtual font question

[Zhichu Chen]

Hello list,

I was trying to use the Math Times Pro 2 fonts in ConTeXt MKIV. This 
Type1 font
contains a map file, a set of pfb files and the corresponding tfm files. 
I was managed

to write a .lfg file and a type-imp-xxx file, but here's my problem.

The font comes with three different sizes, the virtual fonts in my .lfg 
file look like:

===
virtuals = {
[mtpro06a-regular] = {
{ name = file:texgyretermes-regular.otf, features = 
virtualmath, main = true },
{ name = mt2mif.tfm, vector = mtpro2-mi, 
skewchar=0x7F },
{ name = mt2syf.tfm, vector = mtpro2-sy, 
skewchar=0x30, parameters = true },
{ name = mt2mbf.tfm, vector = mtpro2-mb, 
skewchar=0x7F },
{ name = mt2syaf.tfm, vector = mtpro2-sya, 
skewchar=0x7F },
{ name = mt2bbf.tfm, vector = mtpro2-bb, 
skewchar=0x7F },
{ name = mt2msf.tfm, vector = mtpro2-mca, 
skewchar=0x7F },
{ name = mt2bmsf.tfm, vector = mtpro2-bmca, 
skewchar=0x7F },
{ name = mt2mff.tfm, vector = mtpro2-mfa, 
skewchar=0x7F },
{ name = mt2bmff.tfm, vector = mtpro2-bmfa, 
skewchar=0x7F },
{ name = mt2bbif.tfm, vector = mtpro2-bbi, 
skewchar=0x7F },

},
[mtpro08a-regular] = {
{ name = file:texgyretermes-regular.otf, features = 
virtualmath, main = true },
{ name = mt2mis.tfm, vector = mtpro2-mi, 
skewchar=0x7F },
{ name = mt2sys.tfm, vector = mtpro2-sy, 
skewchar=0x30, parameters = true },
{ name = mt2mbs.tfm, vector = mtpro2-mb, 
skewchar=0x7F },
{ name = mt2syas.tfm, vector = mtpro2-sya, 
skewchar=0x7F },
{ name = mt2bbs.tfm, vector = mtpro2-bb, 
skewchar=0x7F },
{ name = mt2mss.tfm, vector = mtpro2-mca, 
skewchar=0x7F },
{ name = mt2bmss.tfm, vector = mtpro2-bmca, 
skewchar=0x7F },
{ name = mt2mfs.tfm, vector = mtpro2-mfa, 
skewchar=0x7F },
{ name = mt2bmfs.tfm, vector = mtpro2-bmfa, 
skewchar=0x7F },
{ name = mt2bbis.tfm, vector = mtpro2-bbi, 
skewchar=0x7F },

},
[mtpro10a-regular] = {
{ name = file:texgyretermes-regular.otf, features = 
virtualmath, main = true },
{ name = mt2mit.tfm, vector = mtpro2-mi, 
skewchar=0x7F },
{ name = mt2syt.tfm, vector = mtpro2-sy, 
skewchar=0x30, parameters = true },
{ name = mt2mbt.tfm, vector = mtpro2-mb, 
skewchar=0x7F },
{ name = mt2syat.tfm, vector = mtpro2-sya, 
skewchar=0x7F },
{ name = mt2bbt.tfm, vector = mtpro2-bb, 
skewchar=0x7F },
{ name = mt2mst.tfm, vector = mtpro2-mca, 
skewchar=0x7F },
{ name = mt2bmst.tfm, vector = mtpro2-bmca, 
skewchar=0x7F },
{ name = mt2mft.tfm, vector = mtpro2-mfa, 
skewchar=0x7F },
{ name = mt2bmft.tfm, vector = mtpro2-bmfa, 
skewchar=0x7F },
{ name = mt2bbit.tfm, vector = mtpro2-bbi, 
skewchar=0x7F },

},
===
I guess the suffixes f s and t may correspond to five seven 
and ten, but that's
not important. I could use one of them as the virtual font in the 
typescript:

===
\definefontsynonym [\s!MathRoman] [MTPro10a-Regular@mtpro10a-regular]
===
The output pdf used the 10-size font as expected.

I stole some codes from lm.lfg and added the following code:
===
designsizes = {
[MathTimeProA-Regular] = {
[4pt]  = MTPro06a-Regular@mtpro06a-regular,
[5pt]  = MTPro06a-Regular@mtpro06a-regular,
[6pt]  = MTPro06a-Regular@mtpro06a-regular,
[7pt]  = MTPro08a-Regular@mtpro08a-regular,
[8pt]  = MTPro08a-Regular@mtpro08a-regular,
[9pt]  = MTPro08a-Regular@mtpro08a-regular,
[10pt] = MTPro10a-Regular@mtpro10a-regular,
[11pt] = MTPro10a-Regular@mtpro10a-regular,
[12pt] = MTPro10a-Regular@mtpro10a-regular,
default  = MTPro10a-Regular@mtpro10a-regular
},
===
and modified the typescript:
===
\definefontsynonym [\s!MathRoman] [\v!name:MathTimeProA-Regular] 
[\s!goodies=math-times-pro-math]

===
It failed as expected:
===
fontsdefining  start stage one: MathRoman mo 1
fontsdefining  specification 'MathRoman 

Re: [NTG-context] Virtual font question

[Aditya Mahajan]

On Tue, 23 Jun 2015, Zhichu Chen wrote:

I was trying to use the Math Times Pro 2 fonts in ConTeXt MKIV. This 
Type1 font contains a map file, a set of pfb files and the corresponding 
tfm files. I was managed to write a .lfg file and a type-imp-xxx file, 
but here's my problem.


I don't have the fonts, so I cannot describe the exact method. But see 
below and also have a look at Section 5 of
https://www.tug.org/TUGboat/tb30-2/tb95mahajan-cmath.pdf The description 
is old, and some of the file locations have changes, but the basic 
infrastructure is still the same.


The font comes with three different sizes, the virtual fonts in my .lfg 
file look like:

===
virtuals = {
[mtpro06a-regular] = {
{ name = file:texgyretermes-regular.otf, features = 
virtualmath, main = true },
{ name = mt2mif.tfm, vector = mtpro2-mi, 
skewchar=0x7F },

[...]

},


The vectors mptpro2-mi etc are not defined. Look at math-ttv.lua for a 
list of predefined vectors (mapping type1 fonts to unicode symbols. It is 
quite likely that the mtpro fonts would follow the standard mappings; if 
not, you will need to create an approrpriate mapping for each font. This 
is not difficult (just monotonous).



===
I guess the suffixes f s and t may correspond to five seven 
and ten, but that's
not important. I could use one of them as the virtual font in the 
typescript:


Once this is done, rest of the typescript should work. It may be a good 
idea to try to see if you can get roman letters from mtpro.


Aditya
___
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] Virtual font question

[Zhichu Chen]

Hi Aditya,


On 06/23/2015 11:57 AM, Aditya Mahajan wrote:
I don't have the fonts, so I cannot describe the exact method. But see 
below and also have a look at Section 5 of
https://www.tug.org/TUGboat/tb30-2/tb95mahajan-cmath.pdf The 
description is old, and some of the file locations have changes, but 
the basic infrastructure is still the same.

Thank you for sharing this article. It seems that the
===
return {
mathematics = {
mapfiles = {
mtpro2.map,
},
virtuals = {
[mtpro06a-regular] = {
...
===
codes may have done the job in the mathematics.make_font function.

In this snippet:
===
\definefontsynonym
  [LMMathRoman10-Regular]
  [LMMath10-Regular@lmroman10-math]
===
I know that LMMathRoman10-Regular will be used as the font synonym, 
@lmroman10-math is the
virtual font, but what does LMMath10-Regular stand for? I chose some 
random names in my typescript

but maybe there's some magic there?
The vectors mptpro2-mi etc are not defined. Look at math-ttv.lua for a 
list of predefined vectors (mapping type1 fonts to unicode symbols. It 
is quite likely that the mtpro fonts would follow the standard 
mappings; if not, you will need to create an approrpriate mapping for 
each font. This is not difficult (just monotonous).
I've already defined these vectors in the same .lfg file. What a tedious 
work it was, by the way. I thought
that would be irrelevant, so I skipped those codes. I'm sorry I didn't 
make that clear.


I almost forgot to mention. The font has its own \Relbar and \relbar 
characters rather than the equality
and the dash marks. What is the best way to use them? I currently put 
them in a private-use-area slot

in the vectors' definitions, but I'm not sure that's a good solution.



===
I guess the suffixes f s and t may correspond to five seven 
and ten, but that's
not important. I could use one of them as the virtual font in the 
typescript:


Once this is done, rest of the typescript should work. It may be a 
good idea to try to see if you can get roman letters from mtpro.

If I claimed the font synonym with the virtual font directly:
===
# typescripts
\definefontsynonym [\s!MathRoman] [MTPro10a-Regular@mtpro10a-regular]
===
the 10-size-version fonts were loaded without any problem. But if I want 
to use the designsize feature:

===
-- lfg
designsizes = {
[MathTimeProA-Regular] = {
[4pt]  = MTPro06a-Regular@mtpro06a-regular,
[5pt]  = MTPro06a-Regular@mtpro06a-regular,
[6pt]  = MTPro06a-Regular@mtpro06a-regular,
...
# typescripts
\definefontsynonym [\s!MathRoman] [\v!file:mathtimeproa-regular]
===
the mathtimeproa-regular font could not be remapped to the correct 
virtual font with the appropriate size.
I just want to know how type-imp-ebgaramond.mkiv managed to remap the 
designsize filename

file:ebgaramond-regular to file:EBGaramond12-Regular.


Aditya
___ 

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] Metapost Font Question

[Taco Hoekwater]

David Arnold wrote:

All,

The attached Metapost file uses the statsmac package by Anthony Phan. 


http://www-math.univ-poitiers.fr/~phan/statsmac.html

And the package:

mps.tar.gz 
http://www-math.univ-poitiers.fr/~phan/downloads/metapost/mps.tar.gz

To compile the attached file I use:

mpost Untitled.mp
mptopdf Untitled.1

I've attached the resulting file. I am wondering why the cm label is set in a 
larger font than the ticklabels. Can anyone help?


The tick labels are typeset by metapost itself, but the cm is
typeset externally (by ConTeXt, if you run the garden distribution).
Metapost is probably using 10pt while ConTeXt uses its default 12pt.

  verbatimtex
  \setupbodyfont[10pt]
  etex

or something similar is needed at the top of the file.

Best wishes,
Taco


___
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] Metapost Font Question

[David Arnold]

Taco,

Thanks.

D.

On Jan 1, 2010, at 12:26 AM, Taco Hoekwater wrote:

 David Arnold wrote:
 All,
 The attached Metapost file uses the statsmac package by Anthony Phan. 
 http://www-math.univ-poitiers.fr/~phan/statsmac.html
 And the package:
 mps.tar.gz 
 http://www-math.univ-poitiers.fr/~phan/downloads/metapost/mps.tar.gz
 To compile the attached file I use:
 mpost Untitled.mp
 mptopdf Untitled.1
 I've attached the resulting file. I am wondering why the cm label is set 
 in a larger font than the ticklabels. Can anyone help?
 
 The tick labels are typeset by metapost itself, but the cm is
 typeset externally (by ConTeXt, if you run the garden distribution).
 Metapost is probably using 10pt while ConTeXt uses its default 12pt.
 
  verbatimtex
  \setupbodyfont[10pt]
  etex
 
 or something similar is needed at the top of the file.
 
 Best wishes,
 Taco
 
 
 ___
 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
___

[NTG-context] Metapost Font Question

[David Arnold]

All,The attached Metapost file uses the statsmac package by Anthony Phan.http://www-math.univ-poitiers.fr/~phan/statsmac.htmlAnd the package:mps.tar.gzTo compile the attached file I use:mpost Untitled.mpmptopdf Untitled.1I've attached the resulting file. I am wondering why the "cm" label is set in a larger font than the ticklabels. Can anyone help?David.

Untitled.mp
Description: Binary data


Untitled-1.pdf
Description: Adobe PDF document
___
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] A font question.

[Hans Hagen]

Taco Hoekwater wrote:


Hi John,

John R. Culleton wrote:


I use Context for highly formatted non-fiction, but I am a bit
reluctant to use it for much of my work because of the strange
(to me) font handling arrangements. I see no purpose for the
multiple synonyms of the same font. That just adds layers of
extra work.



It also adds layers of configurability. Clearly you do not
need that (your font setups is extremely simple and low-level),
but lots of other people do. For example, I have documents that
use 6 totally different font sets, because all 'examples' and
'definitions' are typeset in font families that differ from
the normal text font family. It would be a nightmare if I had to
define and remember the 200+ font definitions by hand.



Also, when you want some special size, by using the synonyms you can say 
\definedfont[Serif at 123pt] without worrying about what the current 
serif is.


Many years ago, Taco wrote a style for the dutch math journal which had 
several font sets, complex columns, mixed encodings per document, etc  
(i still do not understand how he managed to do it in those-days context 
-). A few years later when some specs changed I was asked to rewrite 
those styles and in the process typescripts (font classes), column sets 
(complex figure placement) and some more things evolved.  Since then 
Taco and I have less nighmares -)



So here is my question. If I set up my own font definition
system and as part of it I have statements like:
\font\tfa bchr8r at 10.45pt
\font\tfb bchr8r at 11.37pt
...
... will the rest of Context accept the above tfb font and size in 
places

where a heading macro automatically defaults to tfb?



Only if you never make any \{setup,switchto}bodyfont switches after
your new font definitions.



if you want that, you'd say:

\definefont[MyNiceBigFont][bchr8r at 10.45pt]

or better:

\usetypescript [serif] [charter] [ec]

\definefont[MyNiceBigFont][Charter-Roman at 10.45pt]

in which case you at least see what font is used, and more important, 
you get the encoding for free


\setuphead[chapter][style=\MyNiceBigFont]

btw, if there is a system behind those sizes, you can say:

\definebodyfontenvironment
 [default]
 [a=1.045,
  b=1.137]

and such which lets the a-d sizes scale that way


Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] A font question.

[John R. Culleton]

I use Context for highly formatted non-fiction, but I am a bit
reluctant to use it for much of my work because of the strange
(to me) font handling arrangements. I see no purpose for the
multiple synonyms of the same font. That just adds layers of
extra work.  And I am used to tweaking both the font size and the
baselineskip by fractional amounts to help in getting the
pagination just right and the spacing on the individual page
correct. For example I have the main body font on a current
project defined thus:

\font\rm=8r-AGaramond-Regular at 10.5pt
and this:
\baselineskip 12.0pt plus .25pt

If the page comes up a line short because of strict widow
prevention then the extra space is distributed imperceptibly
among the lines. \parskip is 0 pt for this novel. With a fixed
baselineskip the extra space is distributed only at paragraph breaks,
which gives an ugly result. 

This kind of fine tuning by users is perhaps foreign to Context as it now
exists. Font sizes are in fixed steps for one thing. 

However abandoning the typescript etc. process deprives one of
the useful feature of using tfa, tfb, tfx etc. to adjust font
sizes semi-automatically.

So here is my question. If I set up my own font definition
system and as part of it I have statements like:
\font\tfa bchr8r at 10.45pt
\font\tfb bchr8r at 11.37pt
...
... will the rest of Context accept the above tfb font and size in places
where a heading macro automatically defaults to tfb?


John Culleton

 







___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] A font question.

[Taco Hoekwater]

Hi John,

John R. Culleton wrote:

I use Context for highly formatted non-fiction, but I am a bit
reluctant to use it for much of my work because of the strange
(to me) font handling arrangements. I see no purpose for the
multiple synonyms of the same font. That just adds layers of
extra work.


It also adds layers of configurability. Clearly you do not
need that (your font setups is extremely simple and low-level),
but lots of other people do. For example, I have documents that
use 6 totally different font sets, because all 'examples' and
'definitions' are typeset in font families that differ from
the normal text font family. It would be a nightmare if I had to
define and remember the 200+ font definitions by hand.


If the page comes up a line short because of strict widow
prevention then the extra space is distributed imperceptibly
among the lines. 


It is only imperceptible if the paper you print on does not
shine through at all, and if you use a noteblock (head) binding
instead of book (back) binding, so it is not something I would
recommend for general use.


This kind of fine tuning by users is perhaps foreign to Context as it now
exists. Font sizes are in fixed steps for one thing. 


The fixed steps (of .1pt) are actually an optimization, and it
is possible to circumvent that, using either

  \chardef\fontdigits=2

or

  \def\normalizebodyfontsize#1\to#2{\setvalue{#2}{#1}}


So here is my question. If I set up my own font definition
system and as part of it I have statements like:
\font\tfa bchr8r at 10.45pt
\font\tfb bchr8r at 11.37pt
...
... will the rest of Context accept the above tfb font and size in places
where a heading macro automatically defaults to tfb?


Only if you never make any \{setup,switchto}bodyfont switches after
your new font definitions.

Cheers,

Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context