Simplefonts

Simplefonts

[Wolfgang Schuster]

Hi all,

I’m happy to announce a new version of the simplefonts code. Thew new version of the code
is a complete rewrite and brings many changes.

1. The module is now part of the core and no external module is needed anymore.

2. The commands to select a font have changed to commands which fit better to context normal syntax.

3. I removed the keys to enable font expansion and protrusion, when you need them use \definefontfeature.


To use a font with the simplefonts code two ways are available. The first method is to create
one or more typefaces and load it with \setupbodyfont. A complete example for this is:

\definefontfamily [mainface] [serif] [DejaVu Serif]
\definefontfamily [mainface] [sans]  [DejaVu Sans]
\definefontfamily [mainface] [mono]  [DejaVu Sans Mono] [feature=none]
\definefontfamily [mainface] [math]  [TeX Gyre Pagella Math]

\setupbodyfont[mainface]

\starttext
\startlines
\rm DejaVu Serif
\ss DejaVu Sans
\tt DejaVu Sans Mono
\m{c^2 = a^2 + b^2}
\stoplines
\stoptext


The second method is similar to the old commands of the simplefonts module (e.g. \setmainfont)
where the font is enabled after it was set and no \setupbodyfont is necessary. Below is a example
for this method but I recommend to avoid this method because it’s slow when you set font a font
for each style in your document.

\setupfontfamily [serif] [DejaVu Serif]
\setupfontfamily [sans]  [DejaVu Sans]
\setupfontfamily [mono]  [DejaVu Sans Mono] [feature=none]
\setupfontfamily [math]  [TeX Gyre Pagella Math]

\starttext
\startlines
\rm DejaVu Serif
\ss DejaVu Sans
\tt DejaVu Sans Mono
\m{c^2 = a^2 + b^2}
\stoplines
\stoptext


Another feature of simplefonts is the ability to set a fallback font when you need certain glyphs
from a different font (e.g. for cyrillic ) which aren’t available in the mainfont of the document.
To set such a fallback font the code provides the \definefallbackfamily command where you
can set in the fourth argument the range for the replacement characters.

\definefallbackfamily [mainface] [serif] [DejaVu Serif] [range=cyrillic,force=yes]
\definefontfamily     [mainface] [serif] [TeX Gyre Pagella]

\setupbodyfont[mainface]

\starttext

\input knuth

Традиционная систематика лишайников оказывается во многом условна и

\stoptext


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
___________________________________________________________________________________

Re: Simplefonts

[Zhichu Chen]

[-- Attachment #1.1: Type: text/plain, Size: 3789 bytes --]

Hi Wolfgang,

Good to know that, but I might have some questions.


On Fri, Oct 11, 2013 at 2:02 AM, Wolfgang Schuster <
wolfgang.schuster@gmail.com> wrote:

> Hi all,
>
> I’m happy to announce a new version of the simplefonts code. Thew new
> version of the code
> is a complete rewrite and brings many changes.
>
> 1. The module is now part of the core and no external module is needed
> anymore.
>
> 2. The commands to select a font have changed to commands which fit better
> to context normal syntax.
>
> 3. I removed the keys to enable font expansion and protrusion, when you
> need them use \definefontfeature.
>
>
> To use a font with the simplefonts code two ways are available. The first
> method is to create
> one or more typefaces and load it with \setupbodyfont. A complete example
> for this is:
>
> \definefontfamily [mainface] [serif] [DejaVu Serif]
> \definefontfamily [mainface] [sans]  [DejaVu Sans]
> \definefontfamily [mainface] [mono]  [DejaVu Sans Mono] [feature=none]
>
It seems the keyword here is "features"? Only the plural version works here
in my newest beta.

> \definefontfamily [mainface] [math]  [TeX Gyre Pagella Math]
>
> \setupbodyfont[mainface]
>
> \starttext
> \startlines
> \rm DejaVu Serif
> \ss DejaVu Sans
> \tt DejaVu Sans Mono
> \m{c^2 = a^2 + b^2}
> \stoplines
> \stoptext
>
>
> The second method is similar to the old commands of the simplefonts module
> (e.g. \setmainfont)
> where the font is enabled after it was set and no \setupbodyfont is
> necessary. Below is a example
> for this method but I recommend to avoid this method because it’s slow
> when you set font a font
> for each style in your document.
>
> \setupfontfamily [serif] [DejaVu Serif]
> \setupfontfamily [sans]  [DejaVu Sans]
> \setupfontfamily [mono]  [DejaVu Sans Mono] [feature=none]
> \setupfontfamily [math]  [TeX Gyre Pagella Math]
>
> \starttext
> \startlines
> \rm DejaVu Serif
> \ss DejaVu Sans
> \tt DejaVu Sans Mono
> \m{c^2 = a^2 + b^2}
> \stoplines
> \stoptext
>
>
> Another feature of simplefonts is the ability to set a fallback font when
> you need certain glyphs
> from a different font (e.g. for cyrillic ) which aren’t available in the
> mainfont of the document.
> To set such a fallback font the code provides the \definefallbackfamily
> command where you
> can set in the fourth argument the range for the replacement characters.
>
> \definefallbackfamily [mainface] [serif] [DejaVu Serif]
> [range=cyrillic,force=yes]
>
What if I want to use the CJK font? The code in  "font-sel.mkvi" hints I
could use range=chinese but it didn't work. I have to use interval
{0x00400-0x2FA1F} explicitly.

And how can I assign the boldfont, italicfont and bolditalicfont? I'm
currently using the Adobe Song Std as the regular font but it didn't come
with a bold version or else, hence I might need this feature.

> \definefontfamily     [mainface] [serif] [TeX Gyre Pagella]
>
> \setupbodyfont[mainface]
>
> \starttext
>
> \input knuth
>
> Традиционная систематика лишайников оказывается во многом условна и
>
> \stoptext
>
>
> 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
>
> ___________________________________________________________________________________




-- 
Best Regards
Chen

[-- Attachment #1.2: Type: text/html, Size: 4998 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 6439 bytes --]


Am 12.10.2013 um 15:04 schrieb Zhichu Chen <zhichu.chen@gmail.com>:

> Hi Wolfgang,
> 
> Good to know that, but I might have some questions.
> 
> 
> On Fri, Oct 11, 2013 at 2:02 AM, Wolfgang Schuster <wolfgang.schuster@gmail.com> wrote:
> Hi all,
> 
> I’m happy to announce a new version of the simplefonts code. Thew new version of the code
> is a complete rewrite and brings many changes.
> 
> 1. The module is now part of the core and no external module is needed anymore.
> 
> 2. The commands to select a font have changed to commands which fit better to context normal syntax.
> 
> 3. I removed the keys to enable font expansion and protrusion, when you need them use \definefontfeature.
> 
> 
> To use a font with the simplefonts code two ways are available. The first method is to create
> one or more typefaces and load it with \setupbodyfont. A complete example for this is:
> 
> \definefontfamily [mainface] [serif] [DejaVu Serif]
> \definefontfamily [mainface] [sans]  [DejaVu Sans]
> \definefontfamily [mainface] [mono]  [DejaVu Sans Mono] [feature=none]
> It seems the keyword here is "features"? Only the plural version works here in my newest beta. 

Yes, the name of the key is “features”, the missing “s” was a typo.

> \definefontfamily [mainface] [math]  [TeX Gyre Pagella Math]
> 
> \setupbodyfont[mainface]
> 
> \starttext
> \startlines
> \rm DejaVu Serif
> \ss DejaVu Sans
> \tt DejaVu Sans Mono
> \m{c^2 = a^2 + b^2}
> \stoplines
> \stoptext
> 
> 
> The second method is similar to the old commands of the simplefonts module (e.g. \setmainfont)
> where the font is enabled after it was set and no \setupbodyfont is necessary. Below is a example
> for this method but I recommend to avoid this method because it’s slow when you set font a font
> for each style in your document.
> 
> \setupfontfamily [serif] [DejaVu Serif]
> \setupfontfamily [sans]  [DejaVu Sans]
> \setupfontfamily [mono]  [DejaVu Sans Mono] [feature=none]
> \setupfontfamily [math]  [TeX Gyre Pagella Math]
> 
> \starttext
> \startlines
> \rm DejaVu Serif
> \ss DejaVu Sans
> \tt DejaVu Sans Mono
> \m{c^2 = a^2 + b^2}
> \stoplines
> \stoptext
> 
> 
> Another feature of simplefonts is the ability to set a fallback font when you need certain glyphs
> from a different font (e.g. for cyrillic ) which aren’t available in the mainfont of the document.
> To set such a fallback font the code provides the \definefallbackfamily command where you
> can set in the fourth argument the range for the replacement characters.
> 
> \definefallbackfamily [mainface] [serif] [DejaVu Serif] [range=cyrillic,force=yes]
> What if I want to use the CJK font? The code in  "font-sel.mkvi" hints I could use range=chinese but it didn't work. I have to use interval {0x00400-0x2FA1F} explicitly.

When you take a look into char-def.lua you can see names certain character ranges and “range=cyrillic”
used such a name.

For a chinese font you need “range={cjkunifiedideographs,cjkunifiedideographsextensiona,…}".
Because the list with names is very long you do this setup only once with the \definefontfamilypreset
command, e.g.

  \definefontfamilypreset[chinese][range={cjkunifiedideographs,cjkunifiedideographsextensiona,…}]

and load this setup when you set the font with \definefontfamilyfallback, e.g.

  \definefontfamilyfallback[<typeface>][<style>][<font>][preset=chinese]

For the moment I added three presets “chinese”, “japanese” and “korean” but they need better
names, e.g. “range:chinese” because there could be also “features:chinese” etc.

> And how can I assign the boldfont, italicfont and bolditalicfont? I'm currently using the Adobe Song Std as the regular font but it didn't come with a bold version or else, hence I might need this feature.

The module provides keys to apply a certain font and feature for each alternative (upright, italic etc.)
of a font, a complete list with all keys is shown in the table below.

-------------------------------------------------------
| Alternative | Font            | Feature             |
|-----------------------------------------------------|
| tf          | regularfont     | regularfeatures     |
| it          | italicfont      | italicfeatures      |
| sl          | slantedfont     | slantedfeatures     |
| bf          | boldfont        | boldfeatures        |
| bi          | bolditalicfont  | bolditalicfeatures  |
| bs          | boldslantedfont | boldslantedfeatures |
| sc          | smallcapsfont   | smallcapsfeatures   |
-------------------------------------------------------

The feature-keys expect the name from the \definefontfeature command, when you don’t
specify a feature to a certain alternative the value from the “features” key is used.

When you want to set a certain font for a alternative there are different ways, I’m going
to show the different ways with a few examples where I change the font for italic.

1. Use the filename of a font. With the “file:” prefix you can the tell the module
to look for a file with the given name, when the file isn’t found the font from
the tf-alternative is used. The file-method is also used when you omit the prefix.

\setupfontfamily [serif] [DejaVu Serif] [italicfont=file:dejavuserifbold]

\starttext
Regular and \it Italic
\stoptext

2. Use a certain style. When you use the “style: ”prefix the module looks for a certain
style of the requested font.

\setupfontfamily [serif] [DejaVu Serif] [italicfont=style:bolditalic]

\starttext
Regular and \it Italic
\stoptext

3. Search for a font with a certain name. When you use the “name:” prefix the module
looks for a font with the requested name. Names are internal values of a font which
is sometimes the same as the filename.

\setupfontfamily [serif] [DejaVu Serif] [italicfont=name:dejavuserifbold]

\starttext
Regular and \it Italic
\stoptext

4. Use the spec information. When you use the “spec:” prefix you can request a font
with a certain “weight” (bold or normal), “style” (italic or normal) and variant (smallcaps or normal).

\setupfontfamily [serif] [DejaVu Serif] [italicfont=spec:bold-italic]

\starttext
Regular and \it Italic
\stoptext


There is a possibility that I change the way to set font and features for alternatives
in the feature to a way which is more compact and easier to parse in Lua.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 9183 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Zhichu Chen]

[-- Attachment #1.1: Type: text/plain, Size: 6055 bytes --]

On 10/13/2013 01:39 AM, Wolfgang Schuster wrote:
>
> Am 12.10.2013 um 15:04 schrieb Zhichu Chen <zhichu.chen@gmail.com 
> <mailto:zhichu.chen@gmail.com>>:
>
>> Hi Wolfgang,
>>
>> Good to know that, but I might have some questions.
>>
>>
>> On Fri, Oct 11, 2013 at 2:02 AM, Wolfgang Schuster 
>> <wolfgang.schuster@gmail.com <mailto:wolfgang.schuster@gmail.com>> wrote:
>>
>>     Hi all,
>>
>>     \definefallbackfamily [mainface] [serif] [DejaVu Serif]
>>     [range=cyrillic,force=yes]
>>
>> What if I want to use the CJK font? The code in "font-sel.mkvi" hints 
>> I could use range=chinese but it didn't work. I have to use interval 
>> {0x00400-0x2FA1F} explicitly.
>
> When you take a look into char-def.lua you can see names certain 
> character ranges and “range=cyrillic”
> used such a name.
>
> For a chinese font you need 
> “range={cjkunifiedideographs,cjkunifiedideographsextensiona,…}".
> Because the list with names is very long you do this setup only once 
> with the \definefontfamilypreset
> command, e.g.
>
> \definefontfamilypreset[chinese][range={cjkunifiedideographs,cjkunifiedideographsextensiona,…}]
>
> and load this setup when you set the font with 
> \definefontfamilyfallback, e.g.
>
>   \definefontfamilyfallback[<typeface>][<style>][<font>][preset=chinese]
>
> For the moment I added three presets “chinese”, “japanese” and 
> “korean” but they need better
> names, e.g. “range:chinese” because there could be also 
> “features:chinese” etc.
I get it now. I can put range and features of the fallback fonts in the 
preset.
>
>> And how can I assign the boldfont, italicfont and bolditalicfont? I'm 
>> currently using the Adobe Song Std as the regular font but it didn't 
>> come with a bold version or else, hence I might need this feature.
>
> The module provides keys to apply a certain font and feature for each 
> alternative (upright, italic etc.)
> of a font, a complete list with all keys is shown in the table below.
>
> -------------------------------------------------------
> | Alternative | Font            | Feature             |
> |-----------------------------------------------------|
> | tf          | regularfont     | regularfeatures     |
> | it          | italicfont      | italicfeatures      |
> | sl          | slantedfont     | slantedfeatures     |
> | bf          | boldfont        | boldfeatures        |
> | bi          | bolditalicfont  | bolditalicfeatures  |
> | bs          | boldslantedfont | boldslantedfeatures |
> | sc          | smallcapsfont   | smallcapsfeatures   |
> -------------------------------------------------------
>
> The feature-keys expect the name from the \definefontfeature command, 
> when you don’t
> specify a feature to a certain alternative the value from the 
> “features” key is used.
>
> When you want to set a certain font for a alternative there are 
> different ways, I’m going
> to show the different ways with a few examples where I change the font 
> for italic.
Thanks for the descriptions. I have made a small test and turns out the 
"regularfont" has to be assigned to something or the other "xxxfont"s 
won't have any effects.

Here's my code:
=================================================
\definefallbackfamily [mainface] [serif] [adobesongstd]
   [range={0x00400-0x2FA1F}%
   ,regularfont=name:adobesongstdlight%
   ,italicfont=name:adobefangsongstdregular%
   ,boldfont=name:adobeheitistdregular%
   ,bolditalicfont=name:adobekaitistdregular%
   ,force=yes%
   ,features=song%
   ]
=================================================
and if I remove the "regularfont=..." line, the boldface Chinese 
characters will use the Adobe Song Std font as well. Same thing happened 
when I used the "preset=xxx" option which I don't know if it is intended 
to behave like that, by the way.

Oh, and off the topic, can I use "effect" to assign the fonts? Like if I 
have defined
=================================================
\defineeffect[mybold][alternative=both,rulethickness=\dimexpr\bodyfontsize/10\relax]
=================================================
I would like to use this effect to apply to my bold fonts, maybe:
=================================================
\setupfontfamily [serif] [DejaVu Serif] [boldfont=effect:mybold]
=================================================
I know this has nothing to do with this module. I just thought this 
might be interesting.
>
> 1. Use the filename of a font. With the “file:” prefix you can the 
> tell the module
> to look for a file with the given name, when the file isn’t found the 
> font from
> the tf-alternative is used. The file-method is also used when you omit 
> the prefix.
>
> \setupfontfamily [serif] [DejaVu Serif] [italicfont=file:dejavuserifbold]
>
> \starttext
> Regular and \it Italic
> \stoptext
>
> 2. Use a certain style. When you use the “style: ”prefix the module 
> looks for a certain
> style of the requested font.
>
> \setupfontfamily [serif] [DejaVu Serif] [italicfont=style:bolditalic]
>
> \starttext
> Regular and \it Italic
> \stoptext
>
> 3. Search for a font with a certain name. When you use the “name:” 
> prefix the module
> looks for a font with the requested name. Names are internal values of 
> a font which
> is sometimes the same as the filename.
>
> \setupfontfamily [serif] [DejaVu Serif] [italicfont=name:dejavuserifbold]
>
> \starttext
> Regular and \it Italic
> \stoptext
>
> 4. Use the spec information. When you use the “spec:” prefix you can 
> request a font
> with a certain “weight” (bold or normal), “style” (italic or normal) 
> and variant (smallcaps or normal).
>
> \setupfontfamily [serif] [DejaVu Serif] [italicfont=spec:bold-italic]
>
> \starttext
> Regular and \it Italic
> \stoptext
>
>
> There is a possibility that I change the way to set font and features 
> for alternatives
> in the feature to a way which is more compact and easier to parse in Lua.
>
> Wolfgang


[-- Attachment #1.2: Type: text/html, Size: 11205 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 1894 bytes --]


Am 13.10.2013 um 11:56 schrieb Zhichu Chen <zhichu.chen@gmail.com>:

> Thanks for the descriptions. I have made a small test and turns out the "regularfont" has to be assigned to something or the other "xxxfont"s won't have any effects.
> 
> Here's my code:
> =================================================
> \definefallbackfamily [mainface] [serif] [adobesongstd]
>   [range={0x00400-0x2FA1F}%
>   ,regularfont=name:adobesongstdlight%
>   ,italicfont=name:adobefangsongstdregular%
>   ,boldfont=name:adobeheitistdregular%
>   ,bolditalicfont=name:adobekaitistdregular%
>   ,force=yes%
>   ,features=song%
>   ]
> =================================================
> and if I remove the "regularfont=..." line, the boldface Chinese characters will use the Adobe Song Std font as well. Same thing happened when I used the "preset=xxx" option which I don't know if it is intended to behave like that, by the way.     

I can fit this, it’s a side effect for font families with a single font, e.g. Adobe Song Std which has only the Light font but no files for regular, bold etc.

> Oh, and off the topic, can I use "effect" to assign the fonts? Like if I have defined
> =================================================
> \defineeffect[mybold][alternative=both,rulethickness=\dimexpr\bodyfontsize/10\relax]
> =================================================
> I would like to use this effect to apply to my bold fonts, maybe:
> =================================================
> \setupfontfamily [serif] [DejaVu Serif] [boldfont=effect:mybold]
> =================================================
> I know this has nothing to do with this module. I just thought this might be interesting.

That’s not possible but you can the slant and extend options from \definefontfeature.

http://wiki.contextgarden.net/Simplefonts#Faking_italics_and_bold_fonts

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 2867 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Wolfgang Schuster]

Am 12.10.2013 um 19:39 schrieb Wolfgang Schuster <schuster.wolfgang@gmail.com>:

> The module provides keys to apply a certain font and feature for each alternative (upright, italic etc.)
> of a font, a complete list with all keys is shown in the table below.
> 
> -------------------------------------------------------
> | Alternative | Font            | Feature             |
> |-----------------------------------------------------|
> | tf          | regularfont     | regularfeatures     |
> | it          | italicfont      | italicfeatures      |
> | sl          | slantedfont     | slantedfeatures     |
> | bf          | boldfont        | boldfeatures        |
> | bi          | bolditalicfont  | bolditalicfeatures  |
> | bs          | boldslantedfont | boldslantedfeatures |
> | sc          | smallcapsfont   | smallcapsfeatures   |
> -------------------------------------------------------
> 
> The feature-keys expect the name from the \definefontfeature command, when you don’t
> specify a feature to a certain alternative the value from the “features” key is used.
> 
> When you want to set a certain font for a alternative there are different ways, I’m going
> to show the different ways with a few examples where I change the font for italic.
> 
> 1. Use the filename of a font. With the “file:” prefix you can the tell the module
> to look for a file with the given name, when the file isn’t found the font from
> the tf-alternative is used. The file-method is also used when you omit the prefix.
> 
> \setupfontfamily [serif] [DejaVu Serif] [italicfont=file:dejavuserifbold]
> 
> \starttext
> Regular and \it Italic
> \stoptext
> 
> 2. Use a certain style. When you use the “style: ”prefix the module looks for a certain
> style of the requested font.
> 
> \setupfontfamily [serif] [DejaVu Serif] [italicfont=style:bolditalic]
> 
> \starttext
> Regular and \it Italic
> \stoptext
> 
> 3. Search for a font with a certain name. When you use the “name:” prefix the module
> looks for a font with the requested name. Names are internal values of a font which
> is sometimes the same as the filename.
> 
> \setupfontfamily [serif] [DejaVu Serif] [italicfont=name:dejavuserifbold]
> 
> \starttext
> Regular and \it Italic
> \stoptext
> 
> 4. Use the spec information. When you use the “spec:” prefix you can request a font
> with a certain “weight” (bold or normal), “style” (italic or normal) and variant (smallcaps or normal).
> 
> \setupfontfamily [serif] [DejaVu Serif] [italicfont=spec:bold-italic]
> 
> \starttext
> Regular and \it Italic
> \stoptext
> 
> 
> There is a possibility that I change the way to set font and features for alternatives
> in the feature to a way which is more compact and easier to parse in Lua.

I changed the way to set fonts and features for certain alternatives (the existing keys
mentioned above will remain for a while) in the last beta and you can now set both
values in a single setup.

Below is a example where I changed the font and features for italic:

\definefontfamily [mainface] [serif] [TeX Gyre Pagella] [it={style:bolditalic,features:smallcaps}]

\setupbodyfont[mainface]

\starttext
Upright \it Italic \bf Bold \bi BoldItalic
\stoptext


The name for the keys are “tf”, “it”, “sl”, “bf”, “bi”, “bs” and “sc”. The values for the keys
can be a font change with the methods mentioned above where the method and argument
are separated by a colon. When you want to apply a feature use the “features” method.

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
___________________________________________________________________________________

Re: Simplefonts

[Lars Huttar]

Hi Wolfgang,

I'm doing an overhaul of font handling in our large project, and
wondering whether I should switch to simplefonts at this point.

Can you tell me, how mature is simplefonts? Is it ready for heavy-duty,
complex production use?

Also, is it superceding the standard ConTeXt font handling? That is,
should I expect to find better help available from this list for issues
with simplefonts? Will new development be focused more on simplefonts?

Thanks,
Lars


On 10/10/2013 2:02 PM, Wolfgang Schuster wrote:
> Hi all,
>
> I’m happy to announce a new version of the simplefonts code. Thew new version of the code
> is a complete rewrite and brings many changes.
>
___________________________________________________________________________________
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: Simplefonts

[Hans Hagen]

On 10/14/2013 5:17 PM, Lars Huttar wrote:
> Hi Wolfgang,

let me try to answer ...

> I'm doing an overhaul of font handling in our large project, and
> wondering whether I should switch to simplefonts at this point.

Tor a a real long term robust font usage it all depends on where you 
store your fonts: if you rely on the operating systems setup you could 
burn yourself in the long run with any setup, unless you use typescripts 
+ filenames but when you keep fonts in your project tree you can use 
selectfont (aka simplefonts) when it does the right job for you.

> Can you tell me, how mature is simplefonts? Is it ready for heavy-duty,
> complex production use?

The font system is sort of layered:

-- low level \font commands: most robust
-- \definefont: wrapper around this
-- typescripts: combines fonts in groups, create abstraction
-- fallbacks: combine fonts into one
-- typefaces: sets up a collection of fonts

In identifying fonts there are methods like file, name, spec and file is 
the most robust.

Selectfonts runs on top of all this, and given that its way of doing it 
has been around for a while (apart from the current implementation being 
done from scratch), it's pretty mature. If things change in the low 
level api (unlikely) I'm sure selectfont will adapt which is also easier 
now that it's in the core.

> Also, is it superceding the standard ConTeXt font handling? That is,
> should I expect to find better help available from this list for issues
> with simplefonts? Will new development be focused more on simplefonts?

It is not a font mechanism, but a wrapper that generates unseen the 
standard commands. So, it runs on top of the font mechanism and not 
alongside; it's not a matter of replacing but of convenience. If you 
have a crappy font setup or use fuzzy names of use fonts that have 
confusing properties, nothing will help and you can't blame selectfont, 
but it will do its best to help you as much as possible.

Improvements might be possible in the heuristics, but I'm pretty sure 
that Wolfgang already covered most of it. If there are issues, then the 
challenge is to see if they are general enough to become part of the 
heuristics. In that process improvements might migrate into other places.

As it's now in the core, you can probably expect more of the (mw) 
examples to use it which is educational too.

(Btw, this new modules is a nice examples of hybrid coding.)

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

[Prashanth]

[-- Attachment #1.1: Type: text/plain, Size: 3696 bytes --]

Hi Wolfgang,

Thanks for the update. I have a question, and I came across a bug.

Question: I need some keywords in a distinctively different font, which
I accomplished by defining \kword as "\definesimplefont[kword][DejaVu
Mono][size=13pt]". I looked through font-sel.mkvi, but I did not see any
way of implementing equivalents. (I still haven't learnt macros
properly, though.) Can you please give me a hint on how I can do this
with the latest fonts interface?

Bug: I prefer Euler font for math. This does not seem to work with the
latest fonts interface.

Best regards,
Prash


On 10/10/13 20:02, Wolfgang Schuster wrote:
> Hi all,
>
> I’m happy to announce a new version of the simplefonts code. Thew new version of the code
> is a complete rewrite and brings many changes.
>
> 1. The module is now part of the core and no external module is needed anymore.
>
> 2. The commands to select a font have changed to commands which fit better to context normal syntax.
>
> 3. I removed the keys to enable font expansion and protrusion, when you need them use \definefontfeature.
>
>
> To use a font with the simplefonts code two ways are available. The first method is to create
> one or more typefaces and load it with \setupbodyfont. A complete example for this is:
>
> \definefontfamily [mainface] [serif] [DejaVu Serif]
> \definefontfamily [mainface] [sans]  [DejaVu Sans]
> \definefontfamily [mainface] [mono]  [DejaVu Sans Mono] [feature=none]
> \definefontfamily [mainface] [math]  [TeX Gyre Pagella Math]
>
> \setupbodyfont[mainface]
>
> \starttext
> \startlines
> \rm DejaVu Serif
> \ss DejaVu Sans
> \tt DejaVu Sans Mono
> \m{c^2 = a^2 + b^2}
> \stoplines
> \stoptext
>
>
> The second method is similar to the old commands of the simplefonts module (e.g. \setmainfont)
> where the font is enabled after it was set and no \setupbodyfont is necessary. Below is a example
> for this method but I recommend to avoid this method because it’s slow when you set font a font
> for each style in your document.
>
> \setupfontfamily [serif] [DejaVu Serif]
> \setupfontfamily [sans]  [DejaVu Sans]
> \setupfontfamily [mono]  [DejaVu Sans Mono] [feature=none]
> \setupfontfamily [math]  [TeX Gyre Pagella Math]
>
> \starttext
> \startlines
> \rm DejaVu Serif
> \ss DejaVu Sans
> \tt DejaVu Sans Mono
> \m{c^2 = a^2 + b^2}
> \stoplines
> \stoptext
>
>
> Another feature of simplefonts is the ability to set a fallback font when you need certain glyphs
> from a different font (e.g. for cyrillic ) which aren’t available in the mainfont of the document.
> To set such a fallback font the code provides the \definefallbackfamily command where you
> can set in the fourth argument the range for the replacement characters.
>
> \definefallbackfamily [mainface] [serif] [DejaVu Serif] [range=cyrillic,force=yes]
> \definefontfamily     [mainface] [serif] [TeX Gyre Pagella]
>
> \setupbodyfont[mainface]
>
> \starttext
>
> \input knuth
>
> Традиционная систематика лишайников оказывается во многом условна и
>
> \stoptext
>
>
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 4519 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Wolfgang Schuster]

Am 14.10.2013 um 18:38 schrieb Prashanth <prash.n.rao@gmail.com>:

> Hi Wolfgang,
> 
> Thanks for the update. I have a question, and I came across a bug.
> 
> Question: I need some keywords in a distinctively different font, which I accomplished by defining \kword as "\definesimplefont[kword][DejaVu Mono][size=13pt]". I looked through font-sel.mkvi, but I did not see any way of implementing equivalents. (I still haven't learnt macros properly, though.) Can you please give me a hint on how I can do this with the latest fonts interface?

I’m not bringing it back but you can achieve the same by defining a new typeface/family and refer to a certain alternative of this typeface with the \classfont command.

\definefontfamily[keywords][ss][DejaVu Sans Mono]

\definefont[kword][\classfont{keywords}{Sans} at 13pt]

\definehighlight[keyword][style=kword]

\starttext
Text font \keyword{keyword font}
\stoptext

> Bug: I prefer Euler font for math. This does not seem to work with the latest fonts interface.


The name of the font is “Neo Euler”:

\definefontfamily[mainface][rm][TeX Gyre Pagella]
\definefontfamily[mainface][mm][Neo Euler]

\setupbodyfont[mainface]

\starttext
Text font $math font$
\stoptext

You can also use the predefined typescript which has the name “eulernova”:

\definefontfamily[mainface][rm][TeX Gyre Pagella]
\definefontfamily[mainface][mm][eulernova]

\setupbodyfont[mainface]

\starttext
Text font $math font$
\stoptext

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
___________________________________________________________________________________

Re: Simplefonts

[Otared Kavian]

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]


On 14 oct. 2013, at 19:38, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
> […]
> You can also use the predefined typescript which has the name “eulernova”:
> 
> \definefontfamily[mainface][rm][TeX Gyre Pagella]
> \definefontfamily[mainface][mm][eulernova]
> 
> \setupbodyfont[mainface]
> 
> \starttext
> Text font $math font$
> \stoptext
> 
> Wolfgang

Hi Wolfgang,

Thanks for this wonderful module and functionalities, and the very good tutorials you give us!
Out of curiosity I tested the examples you sent, which all work perfetcly, but the above code with eulernova typescript seems not to give the expected result (using ConTeXt  ver: 2013.10.13 23:58 MKIV) on my installation: please see the attached PDF result of the following example:

%%% begin Wolfgang's example
\definefontfamily[mainface][rm][TeX Gyre Pagella]
\definefontfamily[mainface][mm][eulernova]

\setupbodyfont[mainface]

\starttext
Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
\stoptext
%%% end Wolfgang's example

Best regards: OK

[-- Attachment #2: definefontfamily-math-eulernova.pdf --]
[-- Type: application/pdf, Size: 12726 bytes --]

[-- Attachment #3: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Hans Hagen]

On 10/15/2013 10:02 AM, Otared Kavian wrote:
>
> On 14 oct. 2013, at 19:38, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>> […]
>> You can also use the predefined typescript which has the name “eulernova”:
>>
>> \definefontfamily[mainface][rm][TeX Gyre Pagella]
>> \definefontfamily[mainface][mm][eulernova]
>>
>> \setupbodyfont[mainface]
>>
>> \starttext
>> Text font $math font$
>> \stoptext
>>
>> Wolfgang
>
> Hi Wolfgang,
>
> Thanks for this wonderful module and functionalities, and the very good tutorials you give us!
> Out of curiosity I tested the examples you sent, which all work perfetcly, but the above code with eulernova typescript seems not to give the expected result (using ConTeXt  ver: 2013.10.13 23:58 MKIV) on my installation: please see the attached PDF result of the following example:
>
> %%% begin Wolfgang's example
> \definefontfamily[mainface][rm][TeX Gyre Pagella]
> \definefontfamily[mainface][mm][eulernova]
>
> \setupbodyfont[mainface]
>
> \starttext
> Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
> \stoptext
> %%% end Wolfgang's example

The 'h' in mathfont is a probably a bug in the font (planck constant 
issue as unicode math has no italic h - sic) The large () puzzle me a 
bit as one would expect small ones to start with.

But ... keep in mind that eulernova is unfinished. Although it is an 
official (dante funded) project, we have to wait till Khaled has found 
time for it which is probably less an issue with a few smal patched to 
the font, but making it complete is large effort.

One complication is that euler is normally a mixed-in font, so there is 
an upright/italic cq. distinction issue there that will always make 
euler a font that should be used when the domain permits it.

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

[Mikael P. Sundqvist]

[-- Attachment #1.1: Type: text/plain, Size: 3427 bytes --]

On Tue, Oct 15, 2013 at 10:26 AM, Hans Hagen <pragma@wxs.nl> wrote:

> On 10/15/2013 10:02 AM, Otared Kavian wrote:
>
>>
>> On 14 oct. 2013, at 19:38, Wolfgang Schuster <schuster.wolfgang@gmail.com>
>> wrote:
>>
>>> […]
>>> You can also use the predefined typescript which has the name
>>> “eulernova”:
>>>
>>> \definefontfamily[mainface][**rm][TeX Gyre Pagella]
>>> \definefontfamily[mainface][**mm][eulernova]
>>>
>>> \setupbodyfont[mainface]
>>>
>>> \starttext
>>> Text font $math font$
>>> \stoptext
>>>
>>> Wolfgang
>>>
>>
>> Hi Wolfgang,
>>
>> Thanks for this wonderful module and functionalities, and the very good
>> tutorials you give us!
>> Out of curiosity I tested the examples you sent, which all work
>> perfetcly, but the above code with eulernova typescript seems not to give
>> the expected result (using ConTeXt  ver: 2013.10.13 23:58 MKIV) on my
>> installation: please see the attached PDF result of the following example:
>>
>> %%% begin Wolfgang's example
>> \definefontfamily[mainface][**rm][TeX Gyre Pagella]
>> \definefontfamily[mainface][**mm][eulernova]
>>
>> \setupbodyfont[mainface]
>>
>> \starttext
>> Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
>> \stoptext
>> %%% end Wolfgang's example
>>
>
> The 'h' in mathfont is a probably a bug in the font (planck constant issue
> as unicode math has no italic h - sic) The large () puzzle me a bit as one
> would expect small ones to start with.
>
> But ... keep in mind that eulernova is unfinished. Although it is an
> official (dante funded) project, we have to wait till Khaled has found time
> for it which is probably less an issue with a few smal patched to the font,
> but making it complete is large effort.
>
> One complication is that euler is normally a mixed-in font, so there is an
> upright/italic cq. distinction issue there that will always make euler a
> font that should be used when the domain permits it.
>
>
> 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 <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/<http://foundry.supelec.fr/projects/contextrev/>
> wiki     : http://contextgarden.net
> ______________________________**______________________________**
> _______________________
>

The first example by Wolfgang works as it should

\definefontfamily[mainface][rm][TeX Gyre Pagella]
\definefontfamily[mainface][mm][Neo Euler]

\setupbodyfont[mainface]

\starttext
Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
\stoptext

Maybe I misunderstood something (that Neo Euler and eulernova isn't the
same thing)?

/Mikael

[-- Attachment #1.2: Type: text/html, Size: 4865 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Hans Hagen]

On 10/15/2013 10:41 AM, Mikael P. Sundqvist wrote:

> The first example by Wolfgang works as it should
>
> \definefontfamily[mainface][rm][TeX Gyre Pagella]
> \definefontfamily[mainface][mm][Neo Euler]
>
> \setupbodyfont[mainface]
>
> \starttext
> Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
> \stoptext
>
> Maybe I misunderstood something (that Neo Euler and eulernova isn't the
> same thing)?

ok, so don't use eulernova then (i checked and it's the viortual one 
that picks from all places ...)

but anyway beware of the fatc that eulers are not complete (they were 
meant to be combined with concrete for instance)

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

[Marcin Borkowski]

Dnia 2013-10-15, o godz. 11:12:16
Hans Hagen <pragma@wxs.nl> napisał(a):

> but anyway beware of the fatc that eulers are not complete (they were 
> meant to be combined with concrete for instance)

BTW: what is the status of Concrete fonts?  I'd *love* to be able to
use them in ConTeXt (I can in LaTeX), what do I do to achieve this?

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
___________________________________________________________________________________
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: Simplefonts

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 655 bytes --]


Am 15.10.2013 um 21:12 schrieb Marcin Borkowski <mbork@wmi.amu.edu.pl>:

> Dnia 2013-10-15, o godz. 11:12:16
> Hans Hagen <pragma@wxs.nl> napisał(a):
> 
>> but anyway beware of the fatc that eulers are not complete (they were 
>> meant to be combined with concrete for instance)
> 
> BTW: what is the status of Concrete fonts?  I'd *love* to be able to
> use them in ConTeXt (I can in LaTeX), what do I do to achieve this?

Download the CMU fonts http://canopus.iacp.dvo.ru/~panov/cm-unicode/ and use them with

\definefontfamily [mainface] [rm] [CMU Concrete]

\setupbodyfont[mainface]

\starttext
\input knuth
\stoptext

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 1281 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Marcin Borkowski]

Dnia 2013-10-15, o godz. 21:17:03
Wolfgang Schuster <schuster.wolfgang@gmail.com> napisał(a):

> 
> Am 15.10.2013 um 21:12 schrieb Marcin Borkowski
> <mbork@wmi.amu.edu.pl>:
> 
> > Dnia 2013-10-15, o godz. 11:12:16
> > Hans Hagen <pragma@wxs.nl> napisał(a):
> > 
> >> but anyway beware of the fatc that eulers are not complete (they
> >> were meant to be combined with concrete for instance)
> > 
> > BTW: what is the status of Concrete fonts?  I'd *love* to be able to
> > use them in ConTeXt (I can in LaTeX), what do I do to achieve this?
> 
> Download the CMU fonts http://canopus.iacp.dvo.ru/~panov/cm-unicode/
> and use them with
> 
> \definefontfamily [mainface] [rm] [CMU Concrete]
> 
> \setupbodyfont[mainface]
> 
> \starttext
> \input knuth
> \stoptext
> 
> Wolfgang

Thanks, I'll try it as soon as I have some time.

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
___________________________________________________________________________________
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: Simplefonts

[Hans Hagen]

On 10/15/2013 9:12 PM, Marcin Borkowski wrote:
> Dnia 2013-10-15, o godz. 11:12:16
> Hans Hagen <pragma@wxs.nl> napisał(a):
>
>> but anyway beware of the fatc that eulers are not complete (they were
>> meant to be combined with concrete for instance)
>
> BTW: what is the status of Concrete fonts?  I'd *love* to be able to
> use them in ConTeXt (I can in LaTeX), what do I do to achieve this?

that's luigi's pet project .. making (pouring) perfect concrete fonts

(he showed some a few years ago at meetings)

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

[Hans Hagen]

On 10/15/2013 10:41 AM, Mikael P. Sundqvist wrote:

> The first example by Wolfgang works as it should
>
> \definefontfamily[mainface][rm][TeX Gyre Pagella]
> \definefontfamily[mainface][mm][Neo Euler]
>
> \setupbodyfont[mainface]
>
> \starttext
> Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
> \stoptext
>
> Maybe I misunderstood something (that Neo Euler and eulernova isn't the
> same thing)?

You need to change this in type-imp-euler.mkiv

     \starttypescript [\s!math] [eulernova] [\s!name]
         \loadfontgoodies[euler-math]
         \definefontsynonym [MathRoman] [\s!file:euler.otf] 
[\s!features=\s!math\mathsizesuffix]
     \stoptypescript

For Neo Euler a similar set up is generated at runtime by the selectfont 
mechanism and that code has some hard coded settings for fonts like 
these. Contrary to typescripts that can be changed and are loaded at 
runtime, the selectfont heuristics are more frozen into the core.

Anyhow, eulernova used to be a virtual variant using the Neo Euler (we 
used the name Nova before that but it's too close to other nova's so to 
confusing). However, we now overlay fonts at a different place too so 
that's where the weird () come from. The patch above is fixing this 
(okay, as nobody is going to complete the virtual vectors anyway).

so, to summarize:

   \definefontfamily[mainface][mm][Neo Euler]

uses the selectont heuristics

   \definefontfamily[mainface][mm][eulernova]

uses the predefined euler setup, buit both boil down to the same end 
result.

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

[Hans Hagen]

On 10/15/2013 11:26 AM, Hans Hagen wrote:
> On 10/15/2013 10:41 AM, Mikael P. Sundqvist wrote:
>
>> The first example by Wolfgang works as it should
>>
>> \definefontfamily[mainface][rm][TeX Gyre Pagella]
>> \definefontfamily[mainface][mm][Neo Euler]
>>
>> \setupbodyfont[mainface]
>>
>> \starttext
>> Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
>> \stoptext
>>
>> Maybe I misunderstood something (that Neo Euler and eulernova isn't the
>> same thing)?
>
> You need to change this in type-imp-euler.mkiv
>
>      \starttypescript [\s!math] [eulernova] [\s!name]
>          \loadfontgoodies[euler-math]
>          \definefontsynonym [MathRoman] [\s!file:euler.otf]
> [\s!features=\s!math\mathsizesuffix]
>      \stoptypescript
>
> For Neo Euler a similar set up is generated at runtime by the selectfont
> mechanism and that code has some hard coded settings for fonts like
> these. Contrary to typescripts that can be changed and are loaded at
> runtime, the selectfont heuristics are more frozen into the core.
>
> Anyhow, eulernova used to be a virtual variant using the Neo Euler (we
> used the name Nova before that but it's too close to other nova's so to
> confusing). However, we now overlay fonts at a different place too so
> that's where the weird () come from. The patch above is fixing this
> (okay, as nobody is going to complete the virtual vectors anyway).
>
> so, to summarize:
>
>    \definefontfamily[mainface][mm][Neo Euler]
>
> uses the selectont heuristics
>
>    \definefontfamily[mainface][mm][eulernova]
>
> uses the predefined euler setup, buit both boil down to the same end
> result.

I fixed the h for the combined variants, so we have:

% \definefontfamily[mainface][rm][pagella]
% \definefontfamily[mainface][mm][Neo Euler]
% \setupbodyfont[mainface]

% \definefontfamily[mainface][rm][pagella]
% \definefontfamily[mainface][mm][eulernova]
% \setupbodyfont[mainface]

% \usetypescriptfile[euler]
% \setupbodyfont [pagella-with-euler]

% \usetypescriptfile[euler]
% \setupbodyfont [euler-with-pagella]

% \setupbodyfont [eulernova]

\starttext
Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$ and 
[[$hij$]]
\stoptext


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

[Keith J. Schultz]

[-- Attachment #1.1: Type: text/plain, Size: 4164 bytes --]


Am 15.10.2013 um 10:26 schrieb Hans Hagen <pragma@wxs.nl>:

> On 10/15/2013 10:02 AM, Otared Kavian wrote:
>> 
>> On 14 oct. 2013, at 19:38, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>>> […]
>> 
>> Hi Wolfgang,
>> 
>> Thanks for this wonderful module and functionalities, and the very good tutorials you give us!
>> Out of curiosity I tested the examples you sent, which all work perfetcly, but the above code with eulernova typescript seems not to give the expected result (using ConTeXt  ver: 2013.10.13 23:58 MKIV) on my installation: please see the attached PDF result of the following example:
>> 
>> %%% begin Wolfgang's example
>> \definefontfamily[mainface][rm][TeX Gyre Pagella]
>> \definefontfamily[mainface][mm][eulernova]
>> 
>> \setupbodyfont[mainface]
>> 
>> \starttext
>> Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
>> \stoptext
>> %%% end Wolfgang's example
> 
> The 'h' in mathfont is a probably a bug in the font (planck constant issue as unicode math has no italic h - sic) The large () puzzle me a bit as one would expect small ones to start with.
For the fun of it I tried using MKII and with MKIV with:
\usetypescript[palatino]
\definetypeface [palatino] [mm] [math] [eulernova] [eulernova] [rscale=1.03] 

\starttext
Text font $math font( m^{(34+23)} )$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
\stoptext

and the result came out correct!

I would assume that simplefonts is not understanding the TYPESCRIPT eulernova correctly!

I just look at the log  and seems that MKIV load latin modern math as a fall back. From the log
</Users/quayjay/context/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf>

Using the above simplefonts method I see:
</Users/quayjay/context/tex/texmf/fonts/opentype/public/tex-gyre-math/texgyrepagella-math.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/euler/euler.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/tex-gyre-math/texgyrepagella-math.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/tex-gyre/texgyrepagella-regular.otf>

Using the above simplefonts method with \definefontfamily[mainface][mm][Neo Euler] I see:

</Users/quayjay/context/tex/texmf/fonts/opentype/public/euler/euler.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/euler/euler.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/tex-gyre/texgyrepagella-regular.otf>

This suggests to me that that simplefonts is some how trying to fall back and fails or allows a lower level method do the fall back!

> But ... keep in mind that eulernova is unfinished. Although it is an official (dante funded) project, we have to wait till Khaled has found time for it which is probably less an issue with a few smal patched to the font, but making it complete is large effort.
> 
> One complication is that euler is normally a mixed-in font, so there is an upright/italic cq. distinction issue there that will always make euler a font that should be used when the domain permits it.
> 
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 6758 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 2778 bytes --]


Am 15.10.2013 um 13:42 schrieb Keith J. Schultz <schultzk@uni-trier.de>:

> 
> Am 15.10.2013 um 10:26 schrieb Hans Hagen <pragma@wxs.nl>:
> 
>> On 10/15/2013 10:02 AM, Otared Kavian wrote:
>>> 
>>> On 14 oct. 2013, at 19:38, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>>>> […]
>>> 
>>> Hi Wolfgang,
>>> 
>>> Thanks for this wonderful module and functionalities, and the very good tutorials you give us!
>>> Out of curiosity I tested the examples you sent, which all work perfetcly, but the above code with eulernova typescript seems not to give the expected result (using ConTeXt  ver: 2013.10.13 23:58 MKIV) on my installation: please see the attached PDF result of the following example:
>>> 
>>> %%% begin Wolfgang's example
>>> \definefontfamily[mainface][rm][TeX Gyre Pagella]
>>> \definefontfamily[mainface][mm][eulernova]
>>> 
>>> \setupbodyfont[mainface]
>>> 
>>> \starttext
>>> Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
>>> \stoptext
>>> %%% end Wolfgang's example
>> 
>> The 'h' in mathfont is a probably a bug in the font (planck constant issue as unicode math has no italic h - sic) The large () puzzle me a bit as one would expect small ones to start with.
> For the fun of it I tried using MKII and with MKIV with:
> \usetypescript[palatino]
> \definetypeface [palatino] [mm] [math] [eulernova] [eulernova] [rscale=1.03] 
> 
> \starttext
> Text font $math font( m^{(34+23)} )$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
> \stoptext
> 
> and the result came out correct!
> 
> I would assume that simplefonts is not understanding the TYPESCRIPT eulernova correctly!
> 
> I just look at the log  and seems that MKIV load latin modern math as a fall back. From the log
> </Users/quayjay/context/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf>
> 
> Using the above simplefonts method I see:
> </Users/quayjay/context/tex/texmf/fonts/opentype/public/tex-gyre-math/texgyrepagella-math.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/euler/euler.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/tex-gyre-math/texgyrepagella-math.otf></Users/quayjay/context/tex/texmf/fonts/opentype/public/tex-gyre/texgyrepagella-regular.otf>

I can’t reproduce this, when I use “eulernova” for the math font these files are used:

</Users/wolf/context/beta/tex/texmf/fonts/opentype/public/euler/euler.otf>
</Users/wolf/context/beta/tex/texmf/fonts/opentype/public/euler/euler.otf>
</Users/wolf/context/beta/tex/texmf/fonts/opentype/public/tex-gyre/texgyrepagella-regular.otf>

Wolfgang


[-- Attachment #1.2: Type: text/html, Size: 4228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Keith J. Schultz]

Hi Wolfgang,

Just after I sent my post, Hans had already updated. so the problem has been solved.

regards
	Keith

Am 15.10.2013 um 19:08 schrieb Wolfgang Schuster <schuster.wolfgang@gmail.com>:

> 
> I can’t reproduce this, when I use “eulernova” for the math font these files are used:
> 
> </Users/wolf/context/beta/tex/texmf/fonts/opentype/public/euler/euler.otf>
> </Users/wolf/context/beta/tex/texmf/fonts/opentype/public/euler/euler.otf>
> </Users/wolf/context/beta/tex/texmf/fonts/opentype/public/tex-gyre/texgyrepagella-regular.otf>

___________________________________________________________________________________
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: Simplefonts

[Otared Kavian]

Hi Hans and Wolfgang,

The issue I reported this morning is indeed fixed with the new beta (ConTeXt  ver: 2013.10.15 13:52 MKIV).
Many thanks for the quick fix!

Best regards: OK

On 15 oct. 2013, at 10:26, Hans Hagen <pragma@wxs.nl> wrote:

> On 10/15/2013 10:02 AM, Otared Kavian wrote:
>> 
>> On 14 oct. 2013, at 19:38, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>>> […]
>>> You can also use the predefined typescript which has the name “eulernova”:
>>> 
>>> \definefontfamily[mainface][rm][TeX Gyre Pagella]
>>> \definefontfamily[mainface][mm][eulernova]
>>> 
>>> \setupbodyfont[mainface]
>>> 
>>> \starttext
>>> Text font $math font$
>>> \stoptext
>>> 
>>> Wolfgang
>> 
>> Hi Wolfgang,
>> 
>> Thanks for this wonderful module and functionalities, and the very good tutorials you give us!
>> Out of curiosity I tested the examples you sent, which all work perfetcly, but the above code with eulernova typescript seems not to give the expected result (using ConTeXt  ver: 2013.10.13 23:58 MKIV) on my installation: please see the attached PDF result of the following example:
>> 
>> %%% begin Wolfgang's example
>> \definefontfamily[mainface][rm][TeX Gyre Pagella]
>> \definefontfamily[mainface][mm][eulernova]
>> 
>> \setupbodyfont[mainface]
>> 
>> \starttext
>> Text font $math font$ and $\sin(t) = \int_{0}^t \cos(\theta)d\theta$
>> \stoptext
>> %%% end Wolfgang's example
> 
> The 'h' in mathfont is a probably a bug in the font (planck constant issue as unicode math has no italic h - sic) The large () puzzle me a bit as one would expect small ones to start with.
> 
> But ... keep in mind that eulernova is unfinished. Although it is an official (dante funded) project, we have to wait till Khaled has found time for it which is probably less an issue with a few smal patched to the font, but making it complete is large effort.
> 
> One complication is that euler is normally a mixed-in font, so there is an upright/italic cq. distinction issue there that will always make euler a font that should be used when the domain permits it.
> 
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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: Simplefonts

[Prashanth]

[-- Attachment #1.1: Type: text/plain, Size: 1113 bytes --]


On 14/10/13 19:38, Wolfgang Schuster wrote:
> I’m not bringing it back but you can achieve the same by defining a
> new typeface/family and refer to a certain alternative of this
> typeface with the \classfont command.
> \definefontfamily[keywords][ss][DejaVu Sans Mono]
> \definefont[kword][\classfont{keywords}{Sans} at 13pt]
> \definehighlight[keyword][style=kword] \starttext Text font
> \keyword{keyword font} \stoptext
>> Bug: I prefer Euler font for math. This does not seem to work with the latest fonts interface.
>
> The name of the font is “Neo Euler”:
>
> \definefontfamily[mainface][rm][TeX Gyre Pagella]
> \definefontfamily[mainface][mm][Neo Euler]
>
> \setupbodyfont[mainface]
>
> \starttext
> Text font $math font$
> \stoptext
>
> You can also use the predefined typescript which has the name “eulernova”:
>
> \definefontfamily[mainface][rm][TeX Gyre Pagella]
> \definefontfamily[mainface][mm][eulernova]
>
> \setupbodyfont[mainface]
>
> \starttext
> Text font $math font$
> \stoptext
>
> Wolfgang

Thanks, Wolfgang. Both solutions work well for me.

[-- Attachment #1.2: Type: text/html, Size: 1590 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

SimpleFonts

[hwitloc]

I just installed the "standalone" context and tried to typeset a document which uses "simplefonts" but the resolver indicates that simplefonts is not found.  This isn't surprising, but I need to learn how to install simplefonts to use with the standalone.

Use adding " --modules all"  as an option to  first-setup.sh do this?


Any advice is appreciated.
___________________________________________________________________________________
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: SimpleFonts

[Mikael P. Sundqvist]

On Wed, May 21, 2014 at 5:32 AM,  <hwitloc@gmail.com> wrote:
> I just installed the "standalone" context and tried to typeset a document which uses "simplefonts" but the resolver indicates that simplefonts is not found.  This isn't surprising, but I need to learn how to install simplefonts to use with the standalone.
>
> Use adding " --modules all"  as an option to  first-setup.sh do this?
>
>
> Any advice is appreciated.


I think that functionality is now included in the core, see the top of the page

http://wiki.contextgarden.net/simplefonts

to get a hint of the new syntax.

/Mikael
___________________________________________________________________________________
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: Simplefonts

[John Kitzmiller]

In August 2013 Aditya and Hans provided the following wizardry to include math symbols from pagella when using euler as math font.

http://www.mail-archive.com/ntg-context@ntg.nl/msg71000.html

(Thank you to all involved! It works fine.)

\usetypescriptfile[euler]
\starttypescript[mainface]
  \definetypeface[mainface][rm][serif][pagella]         [default]
  \definetypeface[mainface][mm][math] [pagellaovereuler][default]
\stoptypescript
\setupbodyfont[mainface]
  \appendtoks \rm \to \everymathematics
  \setupmathematics[lcgreek=normal, ucgreek=normal]

\starttext
The text font and $\angle ABD \cong \triangle XYZ$
\stoptext


Can this be achieved with the new simplefonts? I have tried the setups in this thread but the symbols do not show.

John

___________________________________________________________________________________
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: Simplefonts

[Wolfgang Schuster]

Am 19.10.2013 um 14:21 schrieb John Kitzmiller <kitz@inradius.net>:

> In August 2013 Aditya and Hans provided the following wizardry to include math symbols from pagella when using euler as math font.
> 
> http://www.mail-archive.com/ntg-context@ntg.nl/msg71000.html
> 
> (Thank you to all involved! It works fine.)
> 
> \usetypescriptfile[euler]
> \starttypescript[mainface]
>  \definetypeface[mainface][rm][serif][pagella]         [default]
>  \definetypeface[mainface][mm][math] [pagellaovereuler][default]
> \stoptypescript
> \setupbodyfont[mainface]
>  \appendtoks \rm \to \everymathematics
>  \setupmathematics[lcgreek=normal, ucgreek=normal]
> 
> \starttext
> The text font and $\angle ABD \cong \triangle XYZ$
> \stoptext
> 
> 
> Can this be achieved with the new simplefonts? I have tried the setups in this thread but the symbols do not show.


The example below works but you have to wait a few days because there was a bug in the code
when \definefallbackfamily was used with a math font.

\definefontfamily     [mainface] [serif] [DejaVu Serif]
\definefontfamily     [mainface] [sans]  [DejaVu Sans]
\definefontfamily     [mainface] [mono]  [DejaVu Sans Mono]

\definefallbackfamily [mainface] [math]  [TeX Gyre Pagella Math] [range=0x02100-0x02BFF,force=no]
\definefallbackfamily [mainface] [math]  [TeX Gyre Pagella Math] [range=0x1D400-0x1D7FF,force=no]
\definefallbackfamily [mainface] [math]  [TeX Gyre Pagella Math] [range=0x0210E]

\definefontfamily     [mainface] [math]  [Neo Euler]

\setupbodyfont[mainface]

\appendtoks \rm \to \everymathematics
\setupmathematics[lcgreek=normal, ucgreek=normal]

\starttext
The text font and $\angle ABD \cong \triangle XYZ$
\stoptext

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
___________________________________________________________________________________

Simplefonts

[Charles Doherty]

[-- Attachment #1.1: Type: text/plain, Size: 7272 bytes --]

Dear Wolfgang,

I sent an e-mail about problems with my simplefonts. I got no reply since my example had fonts that were probably not available to you. But the problem does not relate to the Gaelic fonts that I had been using. I am sending this file instead. The fonts below can be swapped about. The main font is always typeset as requested but the others are not. Am I doing something really silly? The readout from the console is below. I am using Context Minimals MarkIV on a Mac. Help would be appreciated.

Thanks,
Charlie 

  \usemodule[simplefonts] % load the module
  \setmainfont[TeX Gyre Adventor]


\starttext

Hello World

\blank[big]

\simplefont[TeX Gyre Heros]


\blank[big]

\simplefont[Zapfino]
Hello World


\stoptext

The argument "/Users/charlesdoherty/Documents/TestFolder/Untitled.tex" is not a valid TEXROOT path.
(There is no file "/Users/charlesdoherty/Documents/TestFolder/Untitled.tex/texmf/tex/plain/base/plain.tex")

mtx-context     | run 1: luatex --fmt="/Users/charlesdoherty/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/cont-en" --lua="/Users/charlesdoherty/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/cont-en.lui" --backend="pdf" "./Untitled.tex"
This is LuaTeX, Version beta-0.65.0-2010121316 
 \write18 enabled.
(Untitled.tex

ConTeXt  ver: 2011.02.25 22:03 MKIV  fmt: 2011.3.8  int: english/english

system          > cont-new.mkiv loaded
(/Users/charlesdoherty/context/tex/texmf-context/tex/context/base/cont-new.mkiv
system          > beware: some patches loaded from cont-new.mkiv
)
system          > Untitled.top loaded
(Untitled.top)
fonts           > latin modern fonts are not preloaded
languages       > language en is active
resolvers       > modules > loaded: 'simplefonts'
(/Users/charlesdoherty/context/tex/texmf-context/tex/context/third/simplefonts/t-simplefonts.tex
loading         > ConTeXt User Module / Simplefonts
<+ /Users/charlesdoherty/context/tex/texmf-context/tex/context/third/simplefonts/t-simplefonts.lua>)
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
fonts           > names > font database has matching configuration and file hashes
(/Users/charlesdoherty/context/tex/texmf-context/tex/context/base/type-siz.mkiv) (/Users/charlesdoherty/context/tex/texmf-context/tex/context/base/type-otf.mkiv){/Users/charlesdoherty/context/tex/texmf/fonts/map/dvips/lm/lm-math.map}{/Users/charlesdoherty/context/tex/texmf/fonts/map/dvips/lm/lm-rm.map}{/Users/charlesdoherty/context/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map}
system          > begin file Untitled.tex at line 5
backend         > xmp > using file '/Users/charlesdoherty/context/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pages           > flushing realpage 1, userpage 1, subpage 1
system          > end file Untitled.tex at line 20
 )</Users/charlesdoherty/context/tex/texmf/fonts/opentype/public/lm/lmromanunsl10-regular.otf></Users/charlesdoherty/context/tex/texmf/fonts/opentype/public/tex-gyre/texgyreadventor-regular.otf>
mkiv lua stats  > used config file          - selfautoparent:/texmf/web2c/texmfcnf.lua
mkiv lua stats  > used cache path           - /Users/charlesdoherty/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e
mkiv lua stats  > input load time           - 0.009 seconds
mkiv lua stats  > stored bytecode data      - 275 modules, 56 tables, 331 chunks
mkiv lua stats  > loaded tex modules        - 1 requested, 1 found (*-simplefonts), 0 missing
mkiv lua stats  > cleaned up reserved nodes - 33 nodes, 9 lists of 411
mkiv lua stats  > node memory usage         - 19 glue_spec
mkiv lua stats  > node list callback tasks  - 6 unique task lists, 5 instances (re)created, 4069 calls
mkiv lua stats  > used backend              - pdf (backend for directly generating pdf output)
mkiv lua stats  > loaded patterns           - en::2
mkiv lua stats  > callbacks                 - 4210 direct, 3743 indirect, 7953 total
mkiv lua stats  > randomizer                - resumed with value 0.83236534513178
mkiv lua stats  > lxml preparation time     - 0.000 seconds, 0 nodes, 15 lpath calls, 0 cached calls
mkiv lua stats  > result saved in file      - Untitled.pdf
mkiv lua stats  > loaded fonts              - 16 files: stmary10.afm lmmono10-regular.otf lmroman10-bold.otf lmroman10-regular.otf lmromanunsl10-regular.otf lmsans10-regular.otf texgyreadventor-regular.otf eufb10.tfm eufm10.tfm msam10.tfm msbm10.tfm lmex10.tfm lmmi10.tfm lmmib10.tfm lmsy10.tfm rm-lmr10.tfm
mkiv lua stats  > fonts load time           - 0.241 seconds 
mkiv lua stats  > luatex banner             - this is luatex, version beta-0.65.0-2010121316
mkiv lua stats  > control sequences         - 30184 of 165536
mkiv lua stats  > current memory usage      - 38 MB (ctx: 39 MB)
mkiv lua stats  > runtime                   - 0.886 seconds, 1 processed pages, 1 shipped pages, 1.129 pages/second

system          | total runtime: 1.175


[-- Attachment #1.2: Type: text/html, Size: 20565 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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: Simplefonts

[Wolfgang Schuster]

Am 11.03.2011 um 13:28 schrieb Charles Doherty:

> Dear Wolfgang,
> 
> I sent an e-mail about problems with my simplefonts. I got no reply since my example had fonts that were probably not available to you. But the problem does not relate to the Gaelic fonts that I had been using. I am sending this file instead. The fonts below can be swapped about. The main font is always typeset as requested but the others are not. Am I doing something really silly? The readout from the console is below. I am using Context Minimals MarkIV on a Mac. Help would be appreciated.

Fixed.

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
___________________________________________________________________________________

Re: Simplefonts

[Charles Doherty]

Dear Wolfgang,

Thank you very much. It works a treat!

Best wishes,
Charlie
On 11 Mar 2011, at 18:30, Wolfgang Schuster wrote:

> 
> Am 11.03.2011 um 13:28 schrieb Charles Doherty:
> 
>> Dear Wolfgang,
>> 
>> I sent an e-mail about problems with my simplefonts. I got no reply since my example had fonts that were probably not available to you. But the problem does not relate to the Gaelic fonts that I had been using. I am sending this file instead. The fonts below can be swapped about. The main font is always typeset as requested but the others are not. Am I doing something really silly? The readout from the console is below. I am using Context Minimals MarkIV on a Mac. Help would be appreciated.
> 
> Fixed.
> 
> 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
___________________________________________________________________________________

Simplefonts

[Charles Doherty]

Dear Wolfgang,

The file from which the extract is taken worked fine a few months ago. I have since updated minimals and also simplefonts but I now have a problem. This update was today. The main font is typeset as Gentium Basic as requested but the Gaelic font is set as a roman italic. The switch to Mionchló does not happen. If I reverse the two fonts and make the Mionchló the main font it typesets correctly as the Gaelic font but the switch in this case to Gentium Basic gives the same roman italic. I have not changed the file since it worked correctly.

Thanks,
Charlie

  

  \usemodule[simplefonts] % load the module
  \setmainfont[Gentium Basic]

 \starttext

Transcription of gloss on fol. 18 begins here:

\blank[2*big]

{\switchtobodyfont[14pt]{\simplefont[Mionchló]{Luan cengcegeise i(n)diu duī ingliid dalacha iſ tɼua ī ſcel tuathal do bith dithɼe {\high{\simplefont[Mionchló]{īdiu}}} ⁊ iſ tɼuagiu a hec 
a{\high{\simplefont[Mionchló]{ɼ}}}ɼaíɼ ⁊ a adnucul īnoſa}}}

\blank[big]

Luan cengcegeise i(n)diu dui(n) i ngliid dalacha is trua i(n) scel Tuathal do bith dithre \high{i(n)diu} \low{7}\  is truagiu a hec a\high{r}raír \low{7}\ a adnucul i(n)nosa

\blank[big]

It is Whit Monday here in Glendalough today. Sad is the news today that Tuathal is dying. It is even sadder that he died last night and just now is being buried.
\stoptext
___________________________________________________________________________________
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
___________________________________________________________________________________

simplefonts

[Herbert Voss]

I want to use \bf and \it with sinplefonts.
Is this the only way to get a bold style? Without it
I didn't get a bold style.

\usemodule[simplefonts]
\setmainfont[NexusSerif-Regular]
\definesimplefont[bf][NexusSerif-Bold][size=12pt]

\starttext
\bf \input knuth
\stoptext


the names are:
   rawname="NexusSerif-Bold",
   rawname="NexusSerif-Regular",
[ ... ]


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

[Aditya Mahajan]

On Sat, 13 Nov 2010, Herbert Voss wrote:

> I want to use \bf and \it with sinplefonts.
> Is this the only way to get a bold style? Without it
> I didn't get a bold style.

I don't know how to do this in simplefonts, but ...

> \usemodule[simplefonts]
> \setmainfont[NexusSerif-Regular]
> \definesimplefont[bf][NexusSerif-Bold][size=12pt]

... this certainly is not the right way. For example, with this \bf\it 
will not give you bold italic.

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

[Herbert Voss]

Am 13.11.2010 19:32, schrieb Aditya Mahajan:
> On Sat, 13 Nov 2010, Herbert Voss wrote:
> 
>> I want to use \bf and \it with sinplefonts.
>> Is this the only way to get a bold style? Without it
>> I didn't get a bold style.
> 
> I don't know how to do this in simplefonts, but ...
> 
>> \usemodule[simplefonts]
>> \setmainfont[NexusSerif-Regular]
>> \definesimplefont[bf][NexusSerif-Bold][size=12pt]
> 
> ... this certainly is not the right way. For example, with this \bf\it
> will not give you bold italic.

I know, but this is not my problem, I want to know, why I
do _not_ get a bold without such a definition. I thought
that simplefonts will do the job ...

\usemodule[simplefonts]
\setmainfont[NexusSerif-Regular]
\starttext

\rm\bf is not in bold! Why?

\stoptext

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

[Khaled Hosny]

On Sat, Nov 13, 2010 at 07:37:52PM +0100, Herbert Voss wrote:
> Am 13.11.2010 19:32, schrieb Aditya Mahajan:
> > On Sat, 13 Nov 2010, Herbert Voss wrote:
> > 
> >> I want to use \bf and \it with sinplefonts.
> >> Is this the only way to get a bold style? Without it
> >> I didn't get a bold style.
> > 
> > I don't know how to do this in simplefonts, but ...
> > 
> >> \usemodule[simplefonts]
> >> \setmainfont[NexusSerif-Regular]
> >> \definesimplefont[bf][NexusSerif-Bold][size=12pt]
> > 
> > ... this certainly is not the right way. For example, with this \bf\it
> > will not give you bold italic.
> 
> I know, but this is not my problem, I want to know, why I
> do _not_ get a bold without such a definition. I thought
> that simplefonts will do the job ...
> 
> \usemodule[simplefonts]
> \setmainfont[NexusSerif-Regular]

May be you should say \setmainfont[NexusSerif] without the Regular part
(which might be causing context to look for NexusSerif-Regular-Bold
which would not, normally, exist).

Regards,
 Khaled

-- 
 Khaled Hosny
 Arabic localiser and member of Arabeyes.org team
 Free font developer
___________________________________________________________________________________
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: simplefonts

[Wolfgang Schuster]

Am 13.11.2010 um 19:25 schrieb Herbert Voss:

> I want to use \bf and \it with sinplefonts.
> Is this the only way to get a bold style? Without it
> I didn't get a bold style.
> 
> \usemodule[simplefonts]
> \setmainfont[NexusSerif-Regular]

\setmainfont[Nexus Serif]

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
___________________________________________________________________________________

Re: simplefonts

[Herbert Voss]

Am 13.11.2010 19:44, schrieb Wolfgang Schuster:
> 
> Am 13.11.2010 um 19:25 schrieb Herbert Voss:
> 
>> I want to use \bf and \it with sinplefonts.
>> Is this the only way to get a bold style? Without it
>> I didn't get a bold style.
>>
>> \usemodule[simplefonts]
>> \setmainfont[NexusSerif-Regular]
> 
> \setmainfont[Nexus Serif]

thanks, also to Khaled, both worked
\setmainfont[Nexus Serif]  and
\setmainfont[NexusSerif]

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
___________________________________________________________________________________

simplefonts

[Michael Saunders]

Thomas A. Schmitz:


> That may be a lack of imagination on your part. If you want something that follows LaTeX rules, it might be a good idea to use LaTeX. It would have been a good idea to say so from the start instead of wasting my time.

I'm going to try to go on using Context without wasting any more of
your time.  First, I have to figure out why your typescript gives me
Latin Modern.

-- m
___________________________________________________________________________________
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
___________________________________________________________________________________

simplefonts

[Michael Saunders]

Thomas A. Schmitz:

Thank you, Thomas.  I've been studying this closely.

> A typescript file can contain a series of typeface definitions, e.g., one for serif, one for sans, one for mono, one for math, etc. hence the syntax \starttypescript

[<typeface>] [<identifier>]

I see!  So, I'm guessing that it is this <typeface> which connects the
typescripts to the font switching commands like \rm.  My guess is:
<typeface>     switch
serif              \rm
sans              \ss
mono            \tt
math             \mm
??                 \hw
??                 \cg
and that Context only permits these six families?


> > In the typography manual, Hans says,
> > "The third and fourth
> > arguments to \definetypeface are pointers to already declared font
> > sets; these are defined elsewhere."  I think by "font set" he must
> > mean a typescript like garamondprem, but I don't know where  the font
> > set (typescript?) "serif" is or why two font sets need to be pointed
> > to.

> ???

That's how I feel.  The command in question was:
\definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default]
The typography document says that the "[serif] [garamondprem]"
"are pointers to already declared font sets; these are defined elsewhere."
I know now that "[garamondprem]" is the "font set" in your typescript.
I don't know what font set "[serif]" points to or why.


> The same  typography document goes on to explain the fifth
> argument:
> "The fifth argument to \definetypeface specifies specific font size
> setups (if any), these will be covered in section ?? in the next
> chapter."
> This is getting scary, but I'm hoping putting "[optical]" there will
> solve everything.
>
I don't follow.

http://context.aanhet.net/svn/contextman/context-reference/en/co-typography.pdf
says:   "The fifth argument to \definetypeface specifies specific font
size setups (if any), these will be covered in section ?? in the next
chapter."
If this chapter were inserted into the manual, the next chapter would
be about color and backgrounds, so, no luck searching there.
But, I noticed that that fifth argument was filled by "[optical]" at
the bottom of this page:
http://wiki.contextgarden.net/Optical_Size
so:  "\definetypeface [minion-pro] [rm] [serif] [minion-pro] [optical]"



> > I'm confused about how [GaramondPremUpper] and [garamondpremupper]
> > seem to be getting associated with [rm] and [serif] after they were
> > already associated with
> > [GaramondPrem] and [garamondprem].  I don't see how, when I now use \rm, the
> > machine is going to know whether I mean garamondpremupper or garamondprem.
> > The rest of the file seems straightforward.

> In ConTeXt, you are always within a certain bodyfont (the one defined with the \definetypeface command). A switch like \it or \rm will thus take the italic/roman from this bodyfont. Meaning: when you say \setubodyfont[GaramondPrem], it will use "normal" Garamond Premier, if you use \switchtobodyfont[GaramondPremUpper], it will use the superior numbers variant.

Ahhh, okay.  It wasn't intuitive to me, as a user, that a relatively
small change (from, say, oldstyle to superiors) would take a much
bigger switch (of the whole bodyfont) than would a relatively big
change (from, say, roman to italic, which only needs a little \it).  I
wrote a set of font switches once (in LaTeX) that were all little
digraph codes

(major axis: rm, it, sl, ui; minor axis:  rg, ac, sc, sw, in, su, nu,
de, po, pl, to, tl  +  ornaments, which handles all of the variations
that Adobe makes, anyway).  Maybe I'll be able to reproduce it once I
get this working.

> > I get the error:
> > !undefined control sequence
> > <recently read>  \usetypescript
> > l.12 \usetypescript
> >                         [GaramondPrem]

> Then we will need your example - this is not normal behavior.

okay:

First, I put an almost exact copy of your file (with your comments
commented out) in type-garamondprem.tex in
C:\contextminimal\tex\texmf-local
and ran luatools --generate, which seems to see the directory alright.
Then I put the commands:
\usetypescriptfile [type-garamondprem]
\usetypescript [GaramondPremUpper]
\usetypsecript [GaramondPrem]
\setupbodyfont [GaramondPrem,12pt]
 in my preamble, with nothing else.

When I try to run Context, the above error was returned.  For the
record, here is the exact contents of type-garamondprem.tex:

%So we define a set of such features for the different font instances
we want to define.
%In my case, I want regular text with oldstyle figures, small caps
with lining figures, and superior numerals. This goes into your
typescript:

\definefontfeature
 [myroman]
 [protrusion=pure,expansion=quality,script=latn,liga=yes,onum=yes,pnum=yes,kern=yes,tlig=yes,trep=yes]

\definefontfeature
 [mysmcp]
 [mode=node,script=latn,language=dflt,liga=yes,onum=yes,pnum=yes,kern=yes,tlig=yes,trep=yes,smcp=yes]

\definefontfeature
 [mysup]
 [mode=node,script=latn,onum=no,pnum=yes,sups=yes]

%Next step: we set up the "normal" and smallcaps font:

\starttypescript [serif] [garamondprem]
 \definefontsynonym [Garamond-Roman]
[name:garamondpremierpro]  [features=myroman]
 \definefontsynonym [Garamond-Bold]
[name:garamondpremierprobold]  [features=myroman]
 \definefontsynonym [Garamond-Italic]
[name:garamondpremierproitalic]  [features=myroman]
 \definefontsynonym [Garamond-Bold-Italic]
[name:garamondpremierprobolditalicc] [features=myroman]
 \definefontsynonym [Garamond-SmallCaps]
[name:garamondpremierpro]  [features=mysmcp]
 \stoptypescript

\starttypescript [serif] [garamondprem]
 \definefontsynonym [Serif]           [Garamond-Roman] [features=myroman]
 \definefontsynonym [SerifItalic]     [Garamond-Italic] [features=myroman]
 \definefontsynonym [SerifBold]       [Garamond-Bold] [features=myroman]
 \definefontsynonym [SerifBoldItalic] [Garamond-Bold-Italic] [features=myroman]
 \definefontsynonym [SerifCaps]       [Garamond-SmallCaps] [features=mysmcp]
\stoptypescript

%Finally, define your first typeface:

\starttypescript [GaramondPrem]
 \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default]
\stoptypescript

%Next step: defining a typeface with superior numbers for footnote
references etc.:

\starttypescript [serif] [garamondpremupper]
 \definefontsynonym [GaramondPremUpper-Roman]
[name:agaramondproregular]  [features=mysup]
 \stoptypescript

\starttypescript [serif] [garamondpremupper]
 \definefontsynonym [Serif]           [GaramondPremUpper-Roman]
[features=mysup]
 \definefontsynonym [SerifItalic]     [Serif]
 \definefontsynonym [SerifBold]       [Serif]
 \definefontsynonym [SerifBoldItalic] [Serif]
 \definefontsynonym [SerifCaps]       [Serif]
 \stoptypescript

\starttypescript [GaramondPremUpper]
 \definetypeface [GaramondPremUpper] [rm] [serif] [garamondpremupper] [default]
\stoptypescript

%Save this typescript somewhere where ConTeXt can find it and run
luatools --generate. To use these in your documents, you need these
lines



Thank you again, this has been a huge help.
___________________________________________________________________________________
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: simplefonts

[Henning Hraban Ramm]

Am 2010-03-14 um 14:12 schrieb Michael Saunders:

>> A typescript file can contain a series of typeface definitions,  
>> e.g., one for serif, one for sans, one for mono, one for math, etc.  
>> hence the syntax \starttypescript
>
> [<typeface>] [<identifier>]
>
> I see!  So, I'm guessing that it is this <typeface> which connects the
> typescripts to the font switching commands like \rm.  My guess is:
> <typeface>     switch
> serif              \rm
> sans              \ss
> mono            \tt
> math             \mm
> ??                 \hw
> ??                 \cg
> and that Context only permits these six families?

see http://wiki.contextgarden.net/Basic_Text_Formatting


> That's how I feel.  The command in question was:
> \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default]
> The typography document says that the "[serif] [garamondprem]"
> "are pointers to already declared font sets; these are defined  
> elsewhere."
> I know now that "[garamondprem]" is the "font set" in your typescript.
> I don't know what font set "[serif]" points to or why.

"add a typeface to the GP family, that's a roman font, defined in the  
serif typescript garamondprem (i.e. [serif][garamondprem]) with  
features inherited from the default setting"

If you use "font clans" that have "families" for serif, sans-serif and  
perhaps other (like Latin Modern, Rotis, Stone, Lucida et al.) then  
you'll need typescripts for [serif][myclan] as well as [sans][myclan]  
etc.
When I define the font setup for a project, say a book, I define  
typescripts for [serif][mybook], [sans][mybook] etc, and just call the  
"mybook" font clan, even if it consists of completely different font  
families (say Palatino and Frutiger).

>> In ConTeXt, you are always within a certain bodyfont (the one  
>> defined with the \definetypeface command). A switch like \it or \rm  
>> will thus take the italic/roman from this bodyfont. Meaning: when  
>> you say \setubodyfont[GaramondPrem], it will use "normal" Garamond  
>> Premier, if you use \switchtobodyfont[GaramondPremUpper], it will  
>> use the superior numbers variant.
>
> Ahhh, okay.  It wasn't intuitive to me, as a user, that a relatively
> small change (from, say, oldstyle to superiors) would take a much
> bigger switch (of the whole bodyfont) than would a relatively big
> change (from, say, roman to italic, which only needs a little \it).  I
> wrote a set of font switches once (in LaTeX) that were all little
> digraph codes

You can also define your number style as a Variant, see http://wiki.contextgarden.net/Font_Variants

>> I get the error:
>> !undefined control sequence
>> <recently read>  \usetypescript
>> l.12 \usetypescript

Check if there are any invisible characters that aren't spaces, tabs  
or newlines in or behind \usetypescript

> \usetypsecript [GaramondPrem]

Here's a typo.


Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___________________________________________________________________________________
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: simplefonts

[Hans Hagen]

On 14-3-2010 14:12, Michael Saunders wrote:
> Thomas A. Schmitz:
>
> Thank you, Thomas.  I've been studying this closely.
>
>> A typescript file can contain a series of typeface definitions, e.g., one for serif, one for sans, one for mono, one for math, etc. hence the syntax \starttypescript
>
> [<typeface>] [<identifier>]
>
> I see!  So, I'm guessing that it is this<typeface>  which connects the
> typescripts to the font switching commands like \rm.  My guess is:
> <typeface>      switch
> serif              \rm
> sans              \ss
> mono            \tt
> math             \mm
> ??                 \hw
> ??                 \cg
> and that Context only permits these six families?

it can support as many as you want but only a few make sense

you can combine such combinations in typefaces and mix then any way and 
use multiple such mixtures in one document

> (major axis: rm, it, sl, ui; minor axis:  rg, ac, sc, sw, in, su, nu,
> de, po, pl, to, tl  +  ornaments, which handles all of the variations
> that Adobe makes, anyway).  Maybe I'll be able to reproduce it once I
> get this working.

sounds complex .. it's more like:

[typefaceone|typefacetwo|...| [rm|ss|tt|..] [tf|it|..]

so if you want a smallcaps set, you'd best do something

\definetypeface[Whatever]         [....]
\definetypeface[WhateverSmallcaps][....]

and then switch the lot to smallcaps using a typeface switch (which is 
quite fast) instead of defining all kind of extra smallcaps instances 
within the main typeface

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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
___________________________________________________________________________________

simplefonts

[Michael Saunders]

Aditya Mahajan:

> Have you read the chapter on typography in the new manual
> http://context.aanhet.net/svn/contextman/context-reference/en/co-typography.pdf

Yes.  Several times.  And I took notes.

------------------------------

Hans Hagen:



> > 1. What the first two arguments do.

> the mode=base|node determines if we use traditional tex mechanisms
> (base) or let mkiv do all work itself (node)

> 2. What keys and values are available for the third, and what they mean.

Thank you, but by "the first two arguments", I mean 1 and 2 of:
\definefontfeature [1][2][3].  For example, in
 \definefontfeature[smallcaps][smallcaps][script=latn]
I don't know what "[smallcaps][smallcaps]" is doing.

> > 3. Once I have composed a \definefontfeature command, how do I use it
> > in the text.

> not in the text, only when defining fonts; although you can enable and
> disable features in the running text (dynamicly) .. from the source:

> % \startbuffer
> % \definefontfeature[smallcaps][smallcaps][script=latn]
> % \definefontfeature[oldstyle] [oldstyle] [script=latn]
> %
> % \definedfont[name:cambria at 15pt]
> %
> % Hello there {\setff{smallcaps}capped 123 \setff{oldstyle}123!}    \blank
> % Hello there {\addff{smallcaps}capped 123 \addff{oldstyle}123!}    \blank
> % Hello there {\addff{smallcaps}capped     \subff{smallcaps}normal} \blank
> % \stopbuffer
> %
> % \typebuffer \getbuffer

Naturally, I don't know what any of this code means (which is why I seek
a human language explanation), but I'm guessing that in
\definefontfeature[oldstyle] [oldstyle] [script=latn]
the first "[oldstyle]" creates a command or variable called "oldstyle",
the second "[oldstyle]" relates this to something else (another command or
variable, maybe a font file) which is also called "oldstyle", and
the key-value pair "[script=latn]"qualifies this, selecting the only the Latin
part of the second "[oldstyle]".  (And, by the way, my font has Greek and
Cyrillic as well---why disable oldstyle in them?)  I think that leaves me with
a command or variable or something called "oldstyle", which I could include
in the text.  My first guess would have been that it's "\oldstyle", but, later
in your code snippet, I see "\setff{smallcaps}" and "\addff{smallcaps}".
There's no telling what the difference is.  So, I'm left guessing that
\definefontfeature[oldstyle] [oldstyle] [script=latn]
creates a possible argument for \setff{} and \addff{}, whatever they are.
They might be the commands for font switching in the text.
Since the code snippet isn't a human explanation, however, I can't tell---
I can only make wild guesses.


> > 4. For example, I gathered that I needed a [default]  [default]
> > [...onum=yes...] to get oldstyle numerals by default, but what if I
> > want to use some lining numerals here and there?
> > \definefontfeature [lining]  [lining]  [...onum=no...]
> > {\lining 123}
> > doesn't do it.

> lnum=yes

I tried this, and
\definefontfeature [lining]  [lining]  [lnum=yes]
{\lining 123}
still gives me "undefined control sequence" on \lining.
I also tried {\switchtobodyfont [lining] 123},
which had no effect.


> > 5. How I could use the superior and inferior shapes in my font---like
> > for the footnotemarks, for example?

> hm, with sups=yes,subs=yes i guess but better use \high{..} and \low{..}
> as often such font features are rather limited and depend on the font

I'll have to try that out (since I know which fonts have them), but:
\definefontfeature [?]  [?]  [sups=yes,subs=yes]      ?


------------------------------

Thomas A. Schmitz:

> This is not to disparage Wolfgang's great simplefonts module, but I learnt setting up fonts the old-fashioned way (with typescripts),
> so I will give a few explanations about this approach. Most of what you want can be achieved easily. I have Garamond Premier myself, and this is how I set it up:

Thank you, this is very encouraging.  I used to do this with otftotfm and .fd
files, so it's not totally alien to me.  I just need to grasp the syntax of the
Context commands.  I've been pouring over your example.  There are a
few points I still don't understand.

...
> Next step: we set up the "normal" and smallcaps font:

> \starttypescript [serif] [garamondprem]
>  \definefontsynonym [Garamond-Roman]          [name:garamondpremierpro]  [features=myroman]
>  \definefontsynonym [Garamond-Bold]           [name:garamondpremierprobold]  [features=myroman]
>  \definefontsynonym [Garamond-Italic]         [name:garamondpremierproitalic]  [features=myroman]
>  \definefontsynonym [Garamond-Bold-Italic]    [name:garamondpremierprobolditalicc] [features=myroman]
>  \definefontsynonym [Garamond-SmallCaps]      [name:garamondpremierpro]  [features=mysmcp]
>  \stoptypescript
>
> \starttypescript [serif] [garamondprem]
>  \definefontsynonym [Serif]           [Garamond-Roman] [features=myroman]
>  \definefontsynonym [SerifItalic]     [Garamond-Italic] [features=myroman]
>  \definefontsynonym [SerifBold]       [Garamond-Bold] [features=myroman]
>  \definefontsynonym [SerifBoldItalic] [Garamond-Bold-Italic] [features=myroman]
>  \definefontsynonym [SerifCaps]       [Garamond-SmallCaps] [features=mysmcp]
> \stoptypescript

I don't understand the syntax of \starttypescript.  It doesn't appear
in the manual.
It occurs twice in the "typography" document.  In both cases the first argument
appears to be the name of the typescript.  In one example, there is only one
argument, and in the other example, the second argument appears to be a list
of encodings.  Since everything is now utf-8, I guess that could be forgotten.
So, in your example here, I take "serif" to be the name of both typsecripts, but
I don't know what [garamondprem] is doing.

It's never spelled out, but from looking at examples of
\definefontsynonym [1][2] in the
docs, I think it means something like "what we used to call 2 we can
now call 1", i.e.,
telling the machine to replace instances of "1" with "2".  If this is
the case, your third
arguments above just seem to apply your features to the fonts referred
to, which makes sense.
I don't see, though, why this has to be done twice, and with an extra
layer of misdirection.
E.g., instead of:
\definefontsynonym [Garamond-Roman]          [name:garamondpremierpro]
 [features=myroman]
\definefontsynonym [Serif]           [Garamond-Roman] [features=myroman]
why not just:
\definefontsynonym [Serif]          [name:garamondpremierpro]
[features=myroman]?

I think the purpose of the above step is to connect identifiers like
"Serif" to a qualified font file.

> Finally, define your first typeface:
>
> \starttypescript [GaramondPrem]
>  \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default]
> \stoptypescript

I think this is a typescript called GaramondPrem that contains a
typeface called GaramondPrem.  It seems a little redundant that they
have the same name.  I know that the typescripts are  referred to by
\usetypescript, but I don't know where typefaces are referred to, so
maybe it's  just a dummy argument.  The "[rm]" seems to be what links
this to the font switching command, and the "[garamondprem]" obviously
refers to both the typescripts you defined above.  I don't  understand
what the "[serif]" is doing.  In the typography manual, Hans says,
"The third and fourth
arguments to \definetypeface are pointers to already declared font
sets; these are defined elsewhere."  I think by "font set" he must
mean a typescript like garamondprem, but I don't know where  the font
set (typescript?) "serif" is or why two font sets need to be pointed
to.  The same  typography document goes on to explain the fifth
argument:
"The fifth argument to \definetypeface specifies specific font size
setups (if any), these will be covered in section ?? in the next
chapter."
This is getting scary, but I'm hoping putting "[optical]" there will
solve everything.


> Next step: defining a typeface with superior numbers for footnote references etc.:

> \starttypescript [serif] [garamondpremupper]
>  \definefontsynonym [GaramondPremUpper-Roman]   [name:agaramondproregular]  [features=mysup]
>  \stoptypescript

> \starttypescript [serif] [garamondpremupper]
>  \definefontsynonym [Serif]           [GaramondPremUpper-Roman]      [features=mysup]
>  \definefontsynonym [SerifItalic]     [Serif]
>  \definefontsynonym [SerifBold]       [Serif]
>  \definefontsynonym [SerifBoldItalic] [Serif]
>  \definefontsynonym [SerifCaps]       [Serif]
>  \stoptypescript

I think I follow you, up to the line:
\definefontsynonym [SerifItalic]     [Serif].
These last lines seem to say that if you're in bold or italic, that
you should still use
regular superior figures, but the font has its own bold and italic
superiors.  I think
that's true of all the weight/shape/design size variations in the set.

>  \starttypescript [GaramondPremUpper]
>   \definetypeface [GaramondPremUpper] [rm] [serif] [garamondpremupper] [default]
>  \stoptypescript

I'm confused about how [GaramondPremUpper] and [garamondpremupper]
seem to be getting associated with [rm] and [serif] after they were
already associated with
[GaramondPrem] and [garamondprem].  I don't see how, when I now use \rm, the
machine is going to know whether I mean garamondpremupper or garamondprem.
The rest of the file seems straightforward.

>  OK so far?

Thank you---that brought me a lot closer to understanding!
after saving your example and running luatools --generate,
I put the last lines in my test document and tried running
Context on it in the usual way.  I get the error:
!undefined control sequence
<recently read>  \usetypescript
l.12 \usetypescript
                         [GaramondPrem]



> 5. How I could use the superior and inferior shapes in my font---like
> for the footnotemarks, for example?
>
> You have defined a font instance with superiors. To use it, set up your footnotes accordingly:
>
> \setupfootnotes[textstyle=normal,
>                textcommand={\switchtobodyfont[GaramondPremUpper]},
>                numbercommand={\switchtobodyfont[GaramondPremUpper]}]


> 7. Maybe \definefontfeature is how I should turn on hz?

> With the fontfeature, we have defined to use protrusion=pure,expansion=quality . To enable it, put this in the preamble of your document:

> \enableprotruding
> \enableadjusting



I'll try these when I get things working.  Thanks again.

------------------------------

Wolfgang Schuster:

> \setupalign[hanging,hz]

Or maybe I'll try that.

------------------------------

Andreas Harder:

>> 5. How I could use the superior and inferior shapes in my font---like
>> for the footnotemarks, for example?

> \definefontfeature [sups] [default] [sups=yes]
>
> \setupnote
>  [footnote]
>  [command=,   % -> numbercommand
>   textstyle=, % -> textcommand
>   numbercommand=\setff{sups}, % use superscript-figures
>   textcommand=\setff{sups}]
>
> So you don't have to define GaramondPremUpper.

Thank you.  With this, the marks in the text look good, the ones at the bottom
(with the footnotes) look absurdly small.  I suspect this might be because they
have been optically scaled down, not switched to the smaller design
size, so they
seem to evaporate.  They might look better if they remain the same
size as in the
text, I'm not sure.



------------------------------

Wolfgang Schuster:

http://wiki.contextgarden.net/Optical_Size

Ahhh, the rest of my weekend.  Thank you.

-- m
___________________________________________________________________________________
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: simplefonts

[Wolfgang Schuster]

Am 13.03.10 17:09, schrieb Michael Saunders:
>> 2. What keys and values are available for the third, and what they mean.
>>      
> Thank you, but by "the first two arguments", I mean 1 and 2 of:
> \definefontfeature [1][2][3].  For example, in
>   \definefontfeature[smallcaps][smallcaps][script=latn]
> I don't know what "[smallcaps][smallcaps]" is doing.
>    
Let's start with the normal version

\definefontfeature[default][liga=yes,kern=yes,tlig=yes,trep=yes]

creates a list with the name 'default' (predefined by context and used 
by default
for all fonts if not specified otherwise) with the opentype features 
liga (ligature),
kern (kerning) and the pseudo tex features tlig (-- -> –, --- -> —) and 
trep (' -> ’).

This feature is now applied to font in a typescript (ConTeXt system map 
font files
to commands, e.g. when you write \bf in your document your get Times New 
Roman Bold).


In the extended version with three arguments you copy the list from the 
second
argument to the new list which name is given in the first argument and 
you can
add new opentype features to the list, e.g.

\definefontfeature[mine][default][onum=yes]

creates the new list mine which inherits all features from default and 
adds onum
to the list, when the name in the first and second arguments are equal 
you extend
a already created list with additional features.

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
___________________________________________________________________________________

Re: simplefonts

[Thomas A. Schmitz]

On Mar 13, 2010, at 5:09 PM, Michael Saunders wrote:
> 
> I don't understand the syntax of \starttypescript.  It doesn't appear
> in the manual.
> It occurs twice in the "typography" document.  In both cases the first argument
> appears to be the name of the typescript.  In one example, there is only one
> argument, and in the other example, the second argument appears to be a list
> of encodings.  Since everything is now utf-8, I guess that could be forgotten.
> So, in your example here, I take "serif" to be the name of both typsecripts, but
> I don't know what [garamondprem] is doing.

We're talking about mkiv here, so we don't need to worry about encodings (which is a confusing topic - utf8 is not a font encoding, but an input encoding; these two are not identical). A typescript file can contain a series of typeface definitions, e.g., one for serif, one for sans, one for mono, one for math, etc. hence the syntax \starttypescript [<typeface>] [<identifier>]

> It's never spelled out, but from looking at examples of
> \definefontsynonym [1][2] in the
> docs, I think it means something like "what we used to call 2 we can
> now call 1", i.e.,
> telling the machine to replace instances of "1" with "2".  If this is
> the case, your third
> arguments above just seem to apply your features to the fonts referred
> to, which makes sense.
> I don't see, though, why this has to be done twice, and with an extra
> layer of misdirection.
> E.g., instead of:
> \definefontsynonym [Garamond-Roman]          [name:garamondpremierpro]
> [features=myroman]
> \definefontsynonym [Serif]           [Garamond-Roman] [features=myroman]
> why not just:
> \definefontsynonym [Serif]          [name:garamondpremierpro]
> [features=myroman]?
> 
> I think the purpose of the above step is to connect identifiers like
> "Serif" to a qualified font file.
> 
You could indeed write typescripts without the extra layer of abstraction. It just may make it easier if you want to mix different fonts etc.

>> Finally, define your first typeface:
>> 
>> \starttypescript [GaramondPrem]
>> \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default]
>> \stoptypescript
> 
> I think this is a typescript called GaramondPrem that contains a
> typeface called GaramondPrem.  It seems a little redundant that they
> have the same name.  

You can use two different names, if you prefer.

> I know that the typescripts are  referred to by
> \usetypescript, but I don't know where typefaces are referred to, so
> maybe it's  just a dummy argument.  

In the \usebodyfont or \switchtobodyfont commands.

> The "[rm]" seems to be what links
> this to the font switching command, and the "[garamondprem]" obviously
> refers to both the typescripts you defined above.  I don't  understand
> what the "[serif]" is doing.  In the typography manual, Hans says,
> "The third and fourth
> arguments to \definetypeface are pointers to already declared font
> sets; these are defined elsewhere."  I think by "font set" he must
> mean a typescript like garamondprem, but I don't know where  the font
> set (typescript?) "serif"

As I said: there's at least serif, sans, mono, math

> is or why two font sets need to be pointed
> to.  

???

> The same  typography document goes on to explain the fifth
> argument:
> "The fifth argument to \definetypeface specifies specific font size
> setups (if any), these will be covered in section ?? in the next
> chapter."
> This is getting scary, but I'm hoping putting "[optical]" there will
> solve everything.
> 
I don't follow.

> 
>> Next step: defining a typeface with superior numbers for footnote references etc.:
> 
>> \starttypescript [serif] [garamondpremupper]
>> \definefontsynonym [GaramondPremUpper-Roman]   [name:agaramondproregular]  [features=mysup]
>> \stoptypescript
> 
>> \starttypescript [serif] [garamondpremupper]
>> \definefontsynonym [Serif]           [GaramondPremUpper-Roman]      [features=mysup]
>> \definefontsynonym [SerifItalic]     [Serif]
>> \definefontsynonym [SerifBold]       [Serif]
>> \definefontsynonym [SerifBoldItalic] [Serif]
>> \definefontsynonym [SerifCaps]       [Serif]
>> \stoptypescript
> 
> I think I follow you, up to the line:
> \definefontsynonym [SerifItalic]     [Serif].
> These last lines seem to say that if you're in bold or italic, that
> you should still use
> regular superior figures, but the font has its own bold and italic
> superiors.  I think
> that's true of all the weight/shape/design size variations in the set.
> 

It depends what you want to achieve. I map everything onto Serif because I do not want the superior numbers to be bold or italic, even in an italic environment. Of course, you can define something for all these variants.

>> \starttypescript [GaramondPremUpper]
>>  \definetypeface [GaramondPremUpper] [rm] [serif] [garamondpremupper] [default]
>> \stoptypescript
> 
> I'm confused about how [GaramondPremUpper] and [garamondpremupper]
> seem to be getting associated with [rm] and [serif] after they were
> already associated with
> [GaramondPrem] and [garamondprem].  I don't see how, when I now use \rm, the
> machine is going to know whether I mean garamondpremupper or garamondprem.
> The rest of the file seems straightforward.
> 
In ConTeXt, you are always within a certain bodyfont (the one defined with the \definetypeface command). A switch like \it or \rm will thus take the italic/roman from this bodyfont. Meaning: when you say \setubodyfont[GaramondPrem], it will use "normal" Garamond Premier, if you use \switchtobodyfont[GaramondPremUpper], it will use the superior numbers variant.

>> OK so far?
> 
> Thank you---that brought me a lot closer to understanding!
> after saving your example and running luatools --generate,
> I put the last lines in my test document and tried running
> Context on it in the usual way.  I get the error:
> !undefined control sequence
> <recently read>  \usetypescript
> l.12 \usetypescript
>                         [GaramondPrem]
> 
> 
Then we will need your example - this is not normal behavior.

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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

simplefonts

[Michael Saunders]

> This works
>
> \definefontfeature[default]  [default]  [mode=node,script=latn]
> \definefontfeature[smallcaps][smallcaps][mode=node,script=latn]
>
> \usemodule[simplefonts]
>
> \setmainfont[garamondpremrpro]

Thank you once again.  That _did_ work, after I got rid of an \os (I
used it because I saw it in the manual).

The command \definefontfeature intrigues me greatly.  I wonder if it
could solve all my problems.  I'd love to understand it so that I
don't end up coming in here and asking you to write all my font setups
line by line.  I Googled it and found only a few scattered examples
here and there, mostly from this list.  I wish I could find an
explanation of it written down somewhere.  For example, I would very
much like to know:

1. What the first two arguments do.
2. What keys and values are available for the third, and what they mean.
3. Once I have composed a \definefontfeature command, how do I use it
in the text.
4. For example, I gathered that I needed a [default]  [default]
[...onum=yes...] to get oldstyle numerals by default, but what if I
want to use some lining numerals here and there?
\definefontfeature [lining]  [lining]  [...onum=no...]
{\lining 123}
doesn't do it.
5. How I could use the superior and inferior shapes in my font---like
for the footnotemarks, for example?
6. Could I use \definefontfeature to set up the different design sizes
of my font (I'm trying to use some standard Adobe fonts like Garamond
Premiere Pro, which have design sizes), as well as its other features?
7. Maybe \definefontfeature is how I should turn on hz?

I'm sure these things must be possible, but I'm stumped about how to
find them out.

-- m
___________________________________________________________________________________
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: simplefonts

[Aditya Mahajan]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 992 bytes --]

On Fri, 12 Mar 2010, Michael Saunders wrote:

>> This works
>>
>> \definefontfeature[default]  [default]  [mode=node,script=latn]
>> \definefontfeature[smallcaps][smallcaps][mode=node,script=latn]
>>
>> \usemodule[simplefonts]
>>
>> \setmainfont[garamondpremrpro]
>
> Thank you once again.  That _did_ work, after I got rid of an \os (I
> used it because I saw it in the manual).
>
> The command \definefontfeature intrigues me greatly.  I wonder if it
> could solve all my problems.  I'd love to understand it so that I
> don't end up coming in here and asking you to write all my font setups
> line by line.  I Googled it and found only a few scattered examples
> here and there, mostly from this list.  I wish I could find an
> explanation of it written down somewhere.  For example, I would very
> much like to know:

Have you read the chapter on typography in the new manual
http://context.aanhet.net/svn/contextman/context-reference/en/co-typography.pdf

Aditya

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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: simplefonts

[Hans Hagen]

On 12-3-2010 20:11, Michael Saunders wrote:

> The command \definefontfeature intrigues me greatly.  I wonder if it
> could solve all my problems.  I'd love to understand it so that I
> don't end up coming in here and asking you to write all my font setups
> line by line.  I Googled it and found only a few scattered examples
> here and there, mostly from this list.  I wish I could find an
> explanation of it written down somewhere.  For example, I would very
> much like to know:

> 1. What the first two arguments do.

the mode=base|node determines if we use traditional tex mechanisms 
(base) or let mkiv do all work itself (node)

> 2. What keys and values are available for the third, and what they mean.

the mode=base|node determines if we use traditional tex mechanisms 
(base) or let mkiv do all work itself (node)

there are also extra features and these are described on the wiki, in 
articles and mk.pdf and hybrid.pdf and once they are stable they will be 
properly documented

> 3. Once I have composed a \definefontfeature command, how do I use it
> in the text.

not in the text, only when defining fonts; although you can enable and 
disable features in the running text (dynamicly) .. from the source:

% \startbuffer
% \definefontfeature[smallcaps][smallcaps][script=latn]
% \definefontfeature[oldstyle] [oldstyle] [script=latn]
%
% \definedfont[name:cambria at 15pt]
%
% Hello there {\setff{smallcaps}capped 123 \setff{oldstyle}123!}    \blank
% Hello there {\addff{smallcaps}capped 123 \addff{oldstyle}123!}    \blank
% Hello there {\addff{smallcaps}capped     \subff{smallcaps}normal} \blank
% \stopbuffer
%
% \typebuffer \getbuffer

> 4. For example, I gathered that I needed a [default]  [default]
> [...onum=yes...] to get oldstyle numerals by default, but what if I
> want to use some lining numerals here and there?
> \definefontfeature [lining]  [lining]  [...onum=no...]
> {\lining 123}
> doesn't do it.

lnum=yes

> 5. How I could use the superior and inferior shapes in my font---like
> for the footnotemarks, for example?

hm, with sups=yes,subs=yes i guess but better use \high{..} and \low{..} 
as often such font features are rather limited and depend on the font

> 6. Could I use \definefontfeature to set up the different design sizes
> of my font (I'm trying to use some standard Adobe fonts like Garamond
> Premiere Pro, which have design sizes), as well as its other features?

i never looked into that as i don't have those fonts

> 7. Maybe \definefontfeature is how I should turn on hz?

sure, once it's implemented (probably no big deal but as said, i don't 
have those fonts)

> I'm sure these things must be possible, but I'm stumped about how to
> find them out.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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: simplefonts

[Thomas A. Schmitz]

Hi Michael,

This is not to disparage Wolfgang's great simplefonts module, but I learnt setting up fonts the old-fashioned way (with typescripts), so I will give a few explanations about this approach. Most of what you want can be achieved easily. I have Garamond Premier myself, and this is how I set it up:

It looks like you're only using mkiv. So: call a file type-garamondprem.tex. Here's what we will do:

first, we want to find out what features our font offers. On my system:

otfinfo -f ~/texmf/fonts/opentype/adobe/garmprem/GaramondPremrPro.otf 
aalt	Access All Alternates
c2sc	Small Capitals From Capitals
calt	Contextual Alternates
case	Case-Sensitive Forms
cpsp	Capital Spacing
dlig	Discretionary Ligatures
dnom	Denominators
fina	Terminal Forms
frac	Fractions
hist	Historical Forms
kern	Kerning
liga	Standard Ligatures
lnum	Lining Figures
numr	Numerators
onum	Oldstyle Figures
ordn	Ordinals
ornm	Ornaments
pnum	Proportional Figures
salt	Stylistic Alternates
sinf	Scientific Inferiors
size	Optical Size
smcp	Small Capitals
ss01	Stylistic Set 1
ss02	Stylistic Set 2
ss03	Stylistic Set 3
sups	Superscript
tnum	Tabular Figures
zero	Slashed Zero

You can enable these features with the four-letter-code and "yes." So we define a set of such features for the different font instances we want to define. In my case, I want regular text with oldstyle figures, small caps with lining figures, and superior numerals. This goes into your typescript:

\definefontfeature
  [myroman]
  [protrusion=pure,expansion=quality,script=latn,liga=yes,onum=yes,pnum=yes,kern=yes,tlig=yes,trep=yes]

\definefontfeature
  [mysmcp]
  [mode=node,script=latn,language=dflt,liga=yes,lnum=yes,tnum=yes,kern=yes,tlig=yes,trep=yes,smcp=yes]

\definefontfeature
  [mysup]
  [mode=node,script=latn,onum=no,pnum=yes,sups=yes]

Next step: we set up the "normal" and smallcaps font:

\starttypescript [serif] [garamondprem] 
  \definefontsynonym [Garamond-Roman]          [name:garamondpremierpro]  [features=myroman]
  \definefontsynonym [Garamond-Bold]           [name:garamondpremierprobold]  [features=myroman]
  \definefontsynonym [Garamond-Italic]         [name:garamondpremierproitalic]  [features=myroman]
  \definefontsynonym [Garamond-Bold-Italic]    [name:garamondpremierprobolditalicc] [features=myroman]
  \definefontsynonym [Garamond-SmallCaps]      [name:garamondpremierpro]  [features=mysmcp]
 \stoptypescript

\starttypescript [serif] [garamondprem]
  \definefontsynonym [Serif]           [Garamond-Roman] [features=myroman]
  \definefontsynonym [SerifItalic]     [Garamond-Italic] [features=myroman]
  \definefontsynonym [SerifBold]       [Garamond-Bold] [features=myroman]
  \definefontsynonym [SerifBoldItalic] [Garamond-Bold-Italic] [features=myroman]
  \definefontsynonym [SerifCaps]       [Garamond-SmallCaps] [features=mysmcp]
\stoptypescript

Finally, define your first typeface:

\starttypescript [GaramondPrem]
  \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default]
\stoptypescript 

Next step: defining a typeface with superior numbers for footnote references etc.:

\starttypescript [serif] [garamondpremupper]
  \definefontsynonym [GaramondPremUpper-Roman]   [name:agaramondproregular]  [features=mysup]
 \stoptypescript

\starttypescript [serif] [garamondpremupper]
  \definefontsynonym [Serif]           [GaramondPremUpper-Roman]      [features=mysup]
  \definefontsynonym [SerifItalic]     [Serif]
  \definefontsynonym [SerifBold]       [Serif]
  \definefontsynonym [SerifBoldItalic] [Serif]
  \definefontsynonym [SerifCaps]       [Serif]
  \stoptypescript

\starttypescript [GaramondPremUpper]
  \definetypeface [GaramondPremUpper] [rm] [serif] [garamondpremupper] [default]
\stoptypescript 

Save this typescript somewhere where ConTeXt can find it and run luatools --generate. To use these in your documents, you need these lines

\usetypescriptfile[type-garamondprem]
\usetypescript[GaramondPremUpper]
\usetypsecript[GaramondPrem]
\setupbodyfont[GaramondPrem,11pt]

OK so far?

On Mar 12, 2010, at 8:11 PM, Michael Saunders wrote:

> 
> Thank you once again.  That _did_ work, after I got rid of an \os (I
> used it because I saw it in the manual).
> 
> The command \definefontfeature intrigues me greatly.  I wonder if it
> could solve all my problems.  I'd love to understand it so that I
> don't end up coming in here and asking you to write all my font setups
> line by line.  I Googled it and found only a few scattered examples
> here and there, mostly from this list.  I wish I could find an
> explanation of it written down somewhere.  For example, I would very
> much like to know:
> 
> 1. What the first two arguments do.
> 2. What keys and values are available for the third, and what they mean.

See above: all the font features your font offers.

> 3. Once I have composed a \definefontfeature command, how do I use it
> in the text.
> 4. For example, I gathered that I needed a [default]  [default]
> [...onum=yes...] to get oldstyle numerals by default, but what if I
> want to use some lining numerals here and there?
> \definefontfeature [lining]  [lining]  [...onum=no...]
> {\lining 123}
> doesn't do it.

You can write {\sc 123} (because your smallcap font has lining figures). \os is tied to math and creates problems when used with professional fonts that don't have an accompanying math font.

> 5. How I could use the superior and inferior shapes in my font---like
> for the footnotemarks, for example?

You have defined a font instance with superiors. To use it, set up your footnotes accordingly:

\setupfootnotes[textstyle=normal,
		textcommand={\switchtobodyfont[GaramondPremUpper]},
		numbercommand={\switchtobodyfont[GaramondPremUpper]}]


> 6. Could I use \definefontfeature to set up the different design sizes
> of my font (I'm trying to use some standard Adobe fonts like Garamond
> Premiere Pro, which have design sizes), as well as its other features?

I haven't yet played with this, sorry.

> 7. Maybe \definefontfeature is how I should turn on hz?

With the fontfeature, we have defined to use protrusion=pure,expansion=quality . To enable it, put this in the preamble of your document:

\enableprotruding
\enableadjusting

HTH

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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: simplefonts

[Wolfgang Schuster]

Am 12.03.10 21:11, schrieb Thomas A. Schmitz:
>> 7. Maybe \definefontfeature is how I should turn on hz?
>>      
> With the fontfeature, we have defined to use protrusion=pure,expansion=quality . To enable it, put this in the preamble of your document:
>
> \enableprotruding
> \enableadjusting
>    
\setupalign[hanging,hz]

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
___________________________________________________________________________________

Re: simplefonts

[Andreas Harder]

Hi!

>> 
>> 5. How I could use the superior and inferior shapes in my font---like
>> for the footnotemarks, for example?
> 
> You have defined a font instance with superiors. To use it, set up your footnotes accordingly:
> 
> \setupfootnotes[textstyle=normal,
> 		textcommand={\switchtobodyfont[GaramondPremUpper]},
> 		numbercommand={\switchtobodyfont[GaramondPremUpper]}]

Or:

\definefontfeature [sups] [default] [sups=yes]

\setupnote
  [footnote]
  [command=,   % -> numbercommand
   textstyle=, % -> textcommand
   numbercommand=\setff{sups}, % use superscript-figures
   textcommand=\setff{sups}]

So you don't have to define GaramondPremUpper.

Greetings
	Andreas
___________________________________________________________________________________
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: simplefonts

[Wolfgang Schuster]

Am 12.03.10 21:11, schrieb Thomas A. Schmitz:
>> 6. Could I use \definefontfeature to set up the different design sizes
>> of my font (I'm trying to use some standard Adobe fonts like Garamond
>> Premiere Pro, which have design sizes), as well as its other features?
>>      
> I haven't yet played with this, sorry.
>    
http://wiki.contextgarden.net/Optical_Size

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
___________________________________________________________________________________

Re: simplefonts

[Hans Hagen]

On 12-3-2010 21:38, Wolfgang Schuster wrote:
> Am 12.03.10 21:11, schrieb Thomas A. Schmitz:
>>> 6. Could I use \definefontfeature to set up the different design sizes
>>> of my font (I'm trying to use some standard Adobe fonts like Garamond
>>> Premiere Pro, which have design sizes), as well as its other features?
>> I haven't yet played with this, sorry.
> http://wiki.contextgarden.net/Optical_Size

ok, i was thinking of embedded optical sized (i.e. one font file that 
has several sizes)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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: simplefonts

[Wolfgang Schuster]

Am 12.03.10 23:29, schrieb Hans Hagen:
> ok, i was thinking of embedded optical sized (i.e. one font file that 
> has several sizes)
Is there anything besides different sizes in opentype math fonts and the 
ruby feature in cjk fonts?

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
___________________________________________________________________________________

Re: simplefonts

[Khaled Hosny]

On Sat, Mar 13, 2010 at 06:35:30AM +0100, Wolfgang Schuster wrote:
> Am 12.03.10 23:29, schrieb Hans Hagen:
> >ok, i was thinking of embedded optical sized (i.e. one font file
> >that has several sizes)
> Is there anything besides different sizes in opentype math fonts and
> the ruby feature in cjk fonts?

OpenType fonts can set a size feature, setting the optical size of the
font and the size range in which it is used, so different font files in
the same family with different optical sizes can be set (like LM).
http://www.microsoft.com/typography/otspec/features_pt.htm#size
But I don't think there is support for a single font file with different
optical sizes.

Fontloader already expose the size info if present, we wrote some code
for LaTeX that loads the best optical size automatically based on the
requested font size, it isn't that hard.

Regards,
 Khaled

-- 
 Khaled Hosny
 Arabic localiser and member of Arabeyes.org team
 Free font developer
___________________________________________________________________________________
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: simplefonts

[Hans Hagen]

On 13-3-2010 7:19, Khaled Hosny wrote:
> On Sat, Mar 13, 2010 at 06:35:30AM +0100, Wolfgang Schuster wrote:
>> Am 12.03.10 23:29, schrieb Hans Hagen:
>>> ok, i was thinking of embedded optical sized (i.e. one font file
>>> that has several sizes)
>> Is there anything besides different sizes in opentype math fonts and
>> the ruby feature in cjk fonts?
>
> OpenType fonts can set a size feature, setting the optical size of the
> font and the size range in which it is used, so different font files in
> the same family with different optical sizes can be set (like LM).
> http://www.microsoft.com/typography/otspec/features_pt.htm#size
> But I don't think there is support for a single font file with different
> optical sizes.

ah

> Fontloader already expose the size info if present, we wrote some code
> for LaTeX that loads the best optical size automatically based on the
> requested font size, it isn't that hard.

sure, it's no big deal to support it, but as said .. i don't have such 
fonts (and i don't want illegal copies on my machine) so i haven't 
looked into it; also, for the few cases that are there, typescripts can 
cover it (if it concerns different font files) .. if it crosses out 
paths wolfgang and i can add it to the mkiv heuristics handler

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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: simplefonts

[Wolfgang Schuster]

Am 13.03.10 13:16, schrieb Hans Hagen:
>> Fontloader already expose the size info if present, we wrote some code
>> for LaTeX that loads the best optical size automatically based on the
>> requested font size, it isn't that hard.
> sure, it's no big deal to support it, but as said .. i don't have such 
> fonts (and i don't want illegal copies on my machine) so i haven't 
> looked into it; also, for the few cases that are there, typescripts 
> can cover it (if it concerns different font files) .. if it crosses 
> out paths wolfgang and i can add it to the mkiv heuristics handler
ConTeXt already has the relevant information (designsize, minsize and 
maxsize in the font database) and i have a few test files which use them.

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
___________________________________________________________________________________

Re: simplefonts

[Hans Hagen]

On 13-3-2010 13:26, Wolfgang Schuster wrote:
> Am 13.03.10 13:16, schrieb Hans Hagen:
>>> Fontloader already expose the size info if present, we wrote some code
>>> for LaTeX that loads the best optical size automatically based on the
>>> requested font size, it isn't that hard.
>> sure, it's no big deal to support it, but as said .. i don't have such
>> fonts (and i don't want illegal copies on my machine) so i haven't
>> looked into it; also, for the few cases that are there, typescripts
>> can cover it (if it concerns different font files) .. if it crosses
>> out paths wolfgang and i can add it to the mkiv heuristics handler
> ConTeXt already has the relevant information (designsize, minsize and
> maxsize in the font database) and i have a few test files which use them.

ok, so we take care of it already (sort of)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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: simplefonts

[Andreas Harder]

Am 13.03.2010 um 13:26 schrieb Wolfgang Schuster:

> Am 13.03.10 13:16, schrieb Hans Hagen:
>>> Fontloader already expose the size info if present, we wrote some code
>>> for LaTeX that loads the best optical size automatically based on the
>>> requested font size, it isn't that hard.
>> sure, it's no big deal to support it, but as said .. i don't have such fonts (and i don't want illegal copies on my machine) so i haven't looked into it; also, for the few cases that are there, typescripts can cover it (if it concerns different font files) .. if it crosses out paths wolfgang and i can add it to the mkiv heuristics handler
> ConTeXt already has the relevant information (designsize, minsize and maxsize in the font database) and i have a few test files which use them.

Hello Wolfgang,

would you provide an example of how to use this information?

Thank you in advance
	
	Andreas
___________________________________________________________________________________
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: simplefonts

[Wolfgang Schuster]

Am 13.03.10 14:27, schrieb Andreas Harder:
> would you provide an example of how to use this information?
>    
font-ini.mkiv

%D some low level helpers
%D
%D \starttyping
%D \def\TestLookup#1%
%D   {\dolookupfontbyspec{#1}
%D     pattern: #1, found: \dolookupnoffound
%D    \blank
%D    \dorecurse {\dolookupnoffound} {%
%D      \recurselevel:~\dolookupgetkeyofindex{fontname}{\recurselevel}\quad
%D    }%
%D    \blank}
%D
%D \TestLookup{familyname=helveticaneue}
%D \TestLookup{familyname=helveticaneue,weight=bold}
%D \TestLookup{familyname=helveticaneue,weight=bold,style=italic}
%D \stoptyping

You can ask ConTeXt to look for a font in it's database with the keys

- familyname (e.g. TeX Gyre Pagella or Latin Modern Roman)
- weight (normal, bold, light, medium etc.)
- style (normal, italic)
- variant (normal, smallcaps)
- fontname (e.g. texgyrepagellaregular)
- ...

The information in the database are not always perfect (because fonts 
are a mess) but I'll try to improve this in the next time.

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
___________________________________________________________________________________

Re: simplefonts

[Andreas Harder]

Am 13.03.2010 um 17:17 schrieb Wolfgang Schuster:

> Am 13.03.10 14:27, schrieb Andreas Harder:
>> would you provide an example of how to use this information?
>>   
> font-ini.mkiv
> 
> %D some low level helpers
> %D
> %D \starttyping
> %D \def\TestLookup#1%
> %D   {\dolookupfontbyspec{#1}
> %D     pattern: #1, found: \dolookupnoffound
> %D    \blank
> %D    \dorecurse {\dolookupnoffound} {%
> %D      \recurselevel:~\dolookupgetkeyofindex{fontname}{\recurselevel}\quad
> %D    }%
> %D    \blank}
> %D
> %D \TestLookup{familyname=helveticaneue}
> %D \TestLookup{familyname=helveticaneue,weight=bold}
> %D \TestLookup{familyname=helveticaneue,weight=bold,style=italic}
> %D \stoptyping
> 
> You can ask ConTeXt to look for a font in it's database with the keys
> 
> - familyname (e.g. TeX Gyre Pagella or Latin Modern Roman)
> - weight (normal, bold, light, medium etc.)
> - style (normal, italic)
> - variant (normal, smallcaps)
> - fontname (e.g. texgyrepagellaregular)
> - …

Thank you Wolfgang!

I've played with it, but with \TestLookup{familyname=minionpro,designsize=11pt} no fonts are found. 

By the way, is luaTeX able to use ttc-fonts? 

Andreas
___________________________________________________________________________________
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: simplefonts

[Wolfgang Schuster]

Am 13.03.10 17:59, schrieb Andreas Harder:
> I've played with it, but with \TestLookup{familyname=minionpro,designsize=11pt} no fonts are found.
>    
Values are passed from to to Lua as string and the size is a number, 
what i do is to ask for the font only and loop where i check the size of 
the font.

\dorecurse
   {\dolookupnoffound}
   {\dolookupgetkeyofindex{designsize}{\recurselevel}} % minsize, maxsize

Fonts use a different system for the size a value of 100 stands for 
10pt, 120 for 12pt etc.

You should be also know that fonts are not perfect and in *many* cases 
fonts without optical size use '0' as value for the size.
> By the way, is luaTeX able to use ttc-fonts?
>    
Yes but a few fonts in snow leopard have problems.

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
___________________________________________________________________________________

simplefonts

[Michael Saunders]

> Add
>
> \definefontfeature[default]  [default]  [mode=node,script=latn]
> \definefontfeature[smallcaps][smallcaps][mode=node,script=latn]
>
> before \setmainfont.

Thank you, Wolfgang, but this has no effect.

-- m
___________________________________________________________________________________
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: simplefonts

[Wolfgang Schuster]

Am 12.03.10 11:05, schrieb Michael Saunders:
>> Add
>>
>> \definefontfeature[default]  [default]  [mode=node,script=latn]
>> \definefontfeature[smallcaps][smallcaps][mode=node,script=latn]
>>
>> before \setmainfont.
>>      
> Thank you, Wolfgang, but this has no effect.
>    
This works

\definefontfeature[default]  [default]  [mode=node,script=latn]
\definefontfeature[smallcaps][smallcaps][mode=node,script=latn]

\usemodule[simplefonts]

\setmainfont[garamondpremrpro]

\starttext

text ffi ffl To Ta -- ---

\stoptext

and this also

\usemodule[simplefonts]

\setmainfont[garamondpremrpro][mode=node,script=latin]

\starttext

text ffi ffl To Ta -- ---

\stoptext

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
___________________________________________________________________________________

simplefonts

[Michael Saunders]

I couldn't get Context running from within TexnicCenter again, so I'm
running it from a batch file.  After pouring over all the mentions of
typescripts here and there, I can't make sense of them.  For example,
I used to be able to write font definition files that would
automatically shift between different design sizes depending on what
font size was called for.  How to do that here?  Not a clue.

Finally I settled on trying simplefonts.  The two lines of
documentation in Context Garden are:

\usemodule[simplefonts] % load the module
\setmainfont[Delicious] % set Delicious as main (serif) font

I tried this at home:

\usemodule[simplefonts]
\setmainfont[garamondpremrpro]

and, indeed, it loads Garamond, but normal ligatures (e.g. ffi) are
broken, TeX ligatures (e.g. ---) are broken, small caps are broken,
etc.  It doesn't even take advantage of the superior figures for the
footnote marks, which are now tiny, spindly things.  The documentation
that comes with the module is one line long:

\simplefont[<font>][..,..=..,..]

followed by a list of OpenType features.  So, I tried it:

\simplefont[garamondpremrpro] [features=liga]

It doesn't seem to do anything.  Even standard ligatures don't work.

-- m
___________________________________________________________________________________
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: simplefonts

[Wolfgang Schuster]

Am 12.03.10 05:50, schrieb Michael Saunders:
> I couldn't get Context running from within TexnicCenter again, so I'm
> running it from a batch file.  After pouring over all the mentions of
> typescripts here and there, I can't make sense of them.  For example,
> I used to be able to write font definition files that would
> automatically shift between different design sizes depending on what
> font size was called for.  How to do that here?  Not a clue.
>
> Finally I settled on trying simplefonts.  The two lines of
> documentation in Context Garden are:
>
> \usemodule[simplefonts] % load the module
> \setmainfont[Delicious] % set Delicious as main (serif) font
>
> I tried this at home:
>
> \usemodule[simplefonts]
> \setmainfont[garamondpremrpro]
>
> and, indeed, it loads Garamond, but normal ligatures (e.g. ffi) are
> broken, TeX ligatures (e.g. ---) are broken, small caps are broken,
> etc.  It doesn't even take advantage of the superior figures for the
> footnote marks, which are now tiny, spindly things.
Add

\definefontfeature[default]  [default]  [mode=node,script=latn]
\definefontfeature[smallcaps][smallcaps][mode=node,script=latn]

before \setmainfont.

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
___________________________________________________________________________________

Re: simplefonts

[Vyatcheslav Yatskovsky]

Hi Wolfgang,

I just saw interesting commands:
> \usemodule[simplefonts]
>
> \setmainfont[TeX Gyre Heros][weight=condensed]
>    
Searching for wiki, I found the line "For instance, assuming the 
Delicious fonts <http://www.josbuivenga.demon.nl/delicious.html> are 
properly installed and recognized by ConTeXt, you can simply write....". 
What do you mean by "properly installed and recognized"? Can I just say

\setmainfont[Times New Roman]

and get Window's standard Times New Roman working?

Regards,
Vyatcheslav

___________________________________________________________________________________
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: simplefonts

[Wolfgang Schuster]

Am 21.11.2009 um 22:33 schrieb Vyatcheslav Yatskovsky:

> Searching for wiki, I found the line "For instance, assuming the Delicious fonts <http://www.josbuivenga.demon.nl/delicious.html> are properly installed and recognized by ConTeXt, you can simply write....". What do you mean by "properly installed and recognized"? Can I just say
> 
> \setmainfont[Times New Roman]
> 
> and get Window's standard Times New Roman working?

Why don't you just try it.

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
___________________________________________________________________________________

Re: simplefonts

[Alan BRASLAU]

On Sunday 22 November 2009 13:24:19 Wolfgang Schuster wrote:
> Am 21.11.2009 um 22:33 schrieb Vyatcheslav Yatskovsky:
> > Searching for wiki, I found the line "For instance, assuming the
> > Delicious fonts <http://www.josbuivenga.demon.nl/delicious.html> are
> > properly installed and recognized by ConTeXt, you can simply write....".
> > What do you mean by "properly installed and recognized"? Can I just say
> >
> > \setmainfont[Times New Roman]
> >
> > and get Window's standard Times New Roman working?
> 
> Why don't you just try it.


\setmainfont[Times New Roman]
\starttext
Hello, {\CONTEXT} community!
\stoptext

! Undefined control sequence.
l.1 \setmainfont
                [Times New Roman]
? X
___________________________________________________________________________________
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: simplefonts

[Wolfgang Schuster]

Am 22.11.2009 um 14:10 schrieb Alan BRASLAU:

\usemodule[simplefonts]

> \setmainfont[Times New Roman]
> \starttext
> Hello, {\CONTEXT} community!
> \stoptext

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
___________________________________________________________________________________

Re: simplefonts

[Alan BRASLAU]

Of course, I need
\usemodule[simplefonts]

Now I *am* impressed!
(and I'm not running Windows)
</usr/share/fonts/truetype/msttcorefonts/Times_New_Roman.ttf>

Alan

On Sunday 22 November 2009 14:10:28 Alan BRASLAU wrote:
> On Sunday 22 November 2009 13:24:19 Wolfgang Schuster wrote:
> > Am 21.11.2009 um 22:33 schrieb Vyatcheslav Yatskovsky:
> > > Searching for wiki, I found the line "For instance, assuming the
> > > Delicious fonts <http://www.josbuivenga.demon.nl/delicious.html> are
> > > properly installed and recognized by ConTeXt, you can simply
> > > write....". What do you mean by "properly installed and recognized"?
> > > Can I just say
> > >
> > > \setmainfont[Times New Roman]
> > >
> > > and get Window's standard Times New Roman working?
> >
> > Why don't you just try it.
> 
> \setmainfont[Times New Roman]
> \starttext
> Hello, {\CONTEXT} community!
> \stoptext
> 
> ! Undefined control sequence.
> l.1 \setmainfont
>                 [Times New Roman]
> ? X
> 
___________________________________________________________________________________
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
___________________________________________________________________________________

simplefonts

[Wolfgang Schuster]

Hi all,

I uploaded a new (29th August :) release of the simplefonts module,
the biggest changes are:

- different names for the keys to select fonts in the case bold,
   italic etc. alternatives are not found, each of the key ends now
   with ..font, e.g. italicfont, boldfont, bolditalicfont ...

- the command name to define a typeface (\definetypeface) is now
   \definesimplefonttypeface but this will eventually change again

- I added keys to enable font expansion and protrusion, you can use
   them with \setupsimplefonts what will affect all fonts or with
   \set..font which will affect only the current style

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
___________________________________________________________________________________