Re: [NTG-context] module article-basic interferes with \definebodyfont?

] \stoptypescript \definetypeface [optima] [ss] [sans] [optima] [default] \definetypeface [optima] [rm] [sans] [optima] [default] \definetypeface [optima] [tt] [mono] [dejavu] \setupbodyfont [optima] \starttext \startMPpage[instance=doublefun]   picture pic; pic := textext("\definebodyfont[14.9p

Re: [NTG-context] module article-basic interferes with \definebodyfont?

> use pagella math with optima, not modern > Zo? \definetypeface [optima] [mm] [math] [pagella] [default] Ik gok, want documentatie die dat helder maakt heb ik niet. Er is geen uitleg in de manuals die bij de standalone context komen en op ContextGarden vond ik vooral mkii zaken die niet meer

Re: [NTG-context] module article-basic interferes with \definebodyfont?

On 5/1/2020 11:33 PM, Gerben Wierda wrote: use pagella math with optima, not modern Zo? \definetypeface [optima] [mm] [math] [pagella] [default] Ik gok, want documentatie die dat helder maakt heb ik niet. Er is geen uitleg in de manuals die bij de standalone context komen en op

Re: [NTG-context] module article-basic interferes with \definebodyfont?

On 1 May 2020, at 16:02, Wolfgang Schuster wrote: > > Gerben Wierda schrieb am 01.05.2020 um 13:58: >> \definetypeface [optima] [ss] [sans] [optima] [default] >> \definetypeface [optima] [rm] [serif] [optima] [default] >> \definetypeface [optima] [tt] [mono] [modern] [default] >>

Re: [NTG-context] module article-basic interferes with \definebodyfont?

Gerben Wierda schrieb am 01.05.2020 um 18:19: On 1 May 2020, at 16:02, Wolfgang Schuster > wrote: Gerben Wierda schrieb am 01.05.2020 um 13:58: \definetypeface [optima] [ss] [sans] [optima] [default] \definetypeface [optima] [rm] [serif] [optima]

Re: [NTG-context] module article-basic interferes with \definebodyfont?

On 5/1/2020 6:19 PM, Gerben Wierda wrote: mm should be modern anyway, I think (not that I need it, I only want the ss form anyway). use pagella math with optima, not modern - Hans Hagen |

Re: [NTG-context] module article-basic interferes with \definebodyfont?

d problems. > >> \setupbodyfont [optima] >> \starttext >> \startMPpage[instance=doublefun] >> picture pic; >> pic := textext("\definebodyfont[14.9pt][rm][default=Regular at >> 14.9pt]\switchtobodyfont[14.9pt]\setupinterlinespace[16.9pt]\framed[align=c

[NTG-context] module article-basic interferes with \definebodyfont?

] [default] \setupbodyfont [optima] \starttext \startMPpage[instance=doublefun] picture pic; pic := textext("\definebodyfont[14.9pt][rm][default=Regular at 14.9pt]\switchtobodyfont[14.9pt]\setupinterlinespace[16.9pt]\framed[align=center,frame=off,offset=none,width=335.350bp]{\colored[r=0.00

Re: [NTG-context] module article-basic interferes with \definebodyfont?

Gerben Wierda schrieb am 01.05.2020 um 13:58: \definetypeface [optima] [ss] [sans] [optima] [default] \definetypeface [optima] [rm] [serif] [optima] [default] \definetypeface [optima] [tt] [mono] [modern] [default] \definetypeface [optima] [mm] [math] [optima] [default] \setupbodyfont [optima]

Re: [NTG-context] module article-basic interferes with \definebodyfont?

On 5/1/2020 1:58 PM, Gerben Wierda wrote: But my guess is that if I had used ss instead of rm everywhere in my code it would have worked as well. or define the ss first and don't use \rm (first defined is default) -

Re: [NTG-context] module article-basic interferes with \definebodyfont?

] \stoptypescript \definetypeface [optima] [ss] [sans] [optima] [default] Set a math font to avoid problems. \setupbodyfont [optima] \starttext \startMPpage[instance=doublefun]   picture pic; pic := textext("\definebodyfont[14.9pt][rm][default=Regular at 14.9pt]\switchtobodyfont[1

Re: [NTG-context] Mkiv, fonts in text and math mode, with \definebodyfont

upbodyfont[12pt] \definebodyfont[12pt][rm][tf=rsfs10 sa *] \starttext \tf ABCD \tfa ABCD \stoptext The \tfa ABCD is displayed as rsfs as I wanted, but the \tf ABCD is displayed as default fonts. Why ? What could I change in order to have \tf ABCD in rsfs ? In math mode, I am not able to have

[NTG-context] Mkiv, fonts in text and math mode, with \definebodyfont

Hello, I am trying to understand something more about fonts in text and math mode, in Mkiv Context. I would like to be able to change things at the "define body fonts" level. I tried the following, in order to have rsfs fonts : \setupbodyfont[12pt] \definebodyfont[12pt][rm][tf

Re: [NTG-context] \definebodyfont not working for \typesetbuffer

On 10/16/2016 08:16 PM, Wolfgang Schuster wrote: >> Pablo Rodriguez 16. Oktober 2016 um 20:07 >> [...] >> Neither does it work now. > > Use \definebodyfontenvironment[17pt]. Many thanks for your fast reply, Wolfgang. It works as expected. Pablo -- http://www.ousia.tk

Re: [NTG-context] \definebodyfont not working for \typesetbuffer

Pablo Rodriguez <mailto:oi...@gmx.es> 16. Oktober 2016 um 20:07 Wolfgang, I did it before sending the message and it didn’t work. \startbuffer[buffer:inside] \definebodyfont[17pt] \definefontfamily[mainface][rm][TeX Gyre Pagella] \setupbodyfont[mainface, 17pt] \starttext \input zapf \st

Re: [NTG-context] \definebodyfont not working for \typesetbuffer

On 10/16/2016 07:59 PM, Wolfgang Schuster wrote: >> Pablo Rodriguez 16. Oktober 2016 um 19:56 >> [...] >> As suggested by Wolfgang, \definebodyfont should work. It worked then >> (https://mailman.ntg.nl/pipermail/ntg-context/2016/085260.html), but it >> does

Re: [NTG-context] \definebodyfont not working for \typesetbuffer

Pablo Rodriguez <mailto:oi...@gmx.es> 16. Oktober 2016 um 19:56 Dear list, I have the following sample: \definebodyfont[17pt] \startbuffer[buffer:inside] \definefontfamily[mainface][rm][TeX Gyre Pagella] \setupbodyfont[mainface, 17pt] \starttext \input zapf \stoptext \stopbuffer \sta

[NTG-context] \definebodyfont not working for \typesetbuffer

Dear list, I have the following sample: \definebodyfont[17pt] \startbuffer[buffer:inside] \definefontfamily[mainface][rm][TeX Gyre Pagella] \setupbodyfont[mainface, 17pt] \starttext \input zapf \stoptext \stopbuffer \starttext

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

Can you show me a example where simplefonts is so slow. Sure, here goes. I should say, most of my documents are 1-5 pages and build time is usually under 5 seconds (2nd and higher runs). One (relatively) slow use of simplefonts is the Chinese example (1) below. The way I pasted it, it runs

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

Standing corrected, the impact using eg. CharisSIL for phonetic/IPA symbols the impact is much less: eg. a jump from 2.8 to 4.8 seconds in Example (2) given below. The impact of 2 seconds is bearable! Then it must simply be the font. Whatever the amount of text you typeset using that

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

On 28-7-2010 11:08, Martin Althoff wrote: One (relatively) slow use of simplefonts is the Chinese example (1) below. The way I pasted it, it runs just under 13 seconds on 2nd and consecutive runs. Not using the adobe but eg the ht series is a whee faster. cjk fonts are huge ... are you

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

cjk fonts are huge ... are you using a slow machine with not that much memory? Hi Hans, well, slow is kind of right: MacBook 2GHz Core Duo (first series of MacBooks), but 2GB of RAM is something I would think to be ok. For the Chinese example I see: mkiv lua stats : current memory usage

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

Hans, thanks for the detailed answer! My understanding is slowly advancing :D in principle we could do without, but this helps predefining a couple of things that otherwise would slow down each font switch This confirms my (vague) assumption that deep in the internals it helps structure

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

indeed. in that case it's mostly the cpu caches that matter Ah... Time to save some money for new hardware ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist :

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

On 28-7-2010 11:47, Martin Althoff wrote: For this reason examples with wordy declarations are welcome... Working with hard-blocking Modula compilers was a good teacher, but that's long ago. Taco once told me that one could see from the context sources (old ones maybe) that I had my share

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

On Wed, Jul 28, 2010 at 12:41 PM, Hans Hagen pra...@wxs.nl wrote: On 28-7-2010 11:47, Martin Althoff wrote: For this reason examples with wordy declarations are welcome... Working with hard-blocking Modula compilers was a good teacher, but that's long ago. Taco once told me that one could

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

# grep -i MODULA tex/texmf-context/tex/context/base/* I especially like, from core-con.mkii: %D \macros %D {getdayoftheweek, dayoftheweek} %D %D The conversion algoritm is an old one and a translation from %D a procedure written in MODULA~2 back in the 80's. I finaly %D found the 4--100-400

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

While \MODULA\ taught me to structure, \TEX\ taught me to think recursive. I would certainly go along with the teaching structure part for Modula! ___ If your question is of interest to others as well, please add

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

On 26-7-2010 11:36, Martin Althoff wrote: \definebodyfont [10pt,11pt,12pt] [rm] [tfe=Serif at 48pt, ite=SerifItalic at 48pt] \tfe Big {\it Words}. What I simply don't understand is the need for multiple font size declarations. I can (kind of) see that it might be necessary (looking

Re: [NTG-context] using \definebodyfont with multiple size declarations -- Why?

Am 26.07.10 11:36, schrieb Martin Althoff: - when would I need to provide that information in typescript files I need to create? (simplefonts is very slow to load fonts with phonetic symbols) Can you show me a example where simplefonts is so slow. Wolfgang

[NTG-context] using \definebodyfont with multiple size declarations -- Why?

) setup on Mac OS X 10.6.4. I use it to produce documents I need in a language teaching environment. As I am starting of without legacy documents, there is no need for MKII or any other type of Tex. Confusing for me is the use of \definebodyfont in typescripts. I read in co-fonts.pdf (no release date

[NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

[Hei][AdobeHeitiStd-Regular] \definefontsynonym[FangSong][AdobeFangsongStd-Regular] \definefontsynonym[Kai][AdobeKaitiStd-Regular] \definebodyfont[12pt][rm] [tf=Song, bf=Hei sa 1, it=Kai sa 1, sl=FangSong sa 1] \setscript[hanzi

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

[FangSong] [file:AdobeFangsongStd-Regular] \definefontsynonym [Kai] [file:AdobeKaitiStd-Regular] \starttypescript [serif] [default] [size] \definebodyfont [12pt] [rm] [tf=Song sa 1, bf=Hei sa 1, it=Kai sa 1, sl=FangSong sa 1] \stoptypescript \starttypescript [serif] [chinese

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

2009/4/5 Wolfgang Schuster schuster.wolfg...@googlemail.com: Am 05.04.2009 um 15:07 schrieb Yanrui Li: I want to know why I can not override the preloading rm font. Dunno but it works for a complete definition. If I use other font size, it can work, such as: \definebodyfont[11pt][rm

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

Am 05.04.2009 um 17:16 schrieb Yanrui Li: I want to know why I can not override the preloading rm font. Dunno but it works for a complete definition. If I use other font size, it can work, such as: It has to do with the default setting which is 12pt roman.

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

Wolfgang Schuster wrote: Am 05.04.2009 um 17:16 schrieb Yanrui Li: I want to know why I can not override the preloading rm font. Dunno but it works for a complete definition. If I use other font size, it can work, such as: It has to do with the default setting which is 12pt roman.

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

Am 05.04.2009 um 22:04 schrieb Hans Hagen: Wolfgang Schuster wrote: Am 05.04.2009 um 17:16 schrieb Yanrui Li: I want to know why I can not override the preloading rm font. Dunno but it works for a complete definition. If I use other font size, it can work, such as: It has to do with the

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

Wolfgang Schuster wrote: Am 05.04.2009 um 22:04 schrieb Hans Hagen: Wolfgang Schuster wrote: Am 05.04.2009 um 17:16 schrieb Yanrui Li: I want to know why I can not override the preloading rm font. Dunno but it works for a complete definition. If I use other font size, it can work, such

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

Am 05.04.2009 um 23:14 schrieb Hans Hagen: \setupbodyfont[reset] \setupbodyfont[mymodern] Did not work because reset alone use the roman style also for italic and bold and he don't use his own typeface, your dummy mymodern lead us back to the start. tricky ... --mode=*nofonts Not

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

Wolfgang Schuster wrote: Am 05.04.2009 um 23:14 schrieb Hans Hagen: \setupbodyfont[reset] \setupbodyfont[mymodern] Did not work because reset alone use the roman style also for italic and bold and he don't use his own typeface, your dummy mymodern lead us back to the start. tricky ...

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

Am 05.04.2009 um 23:25 schrieb Hans Hagen: sure, but i'm not too eager to add that kind of hackery so loading a new typeface then makes more sense My hack can be done in a cleaner way with \appendtoks\letcsnamecs \csname\newfontidentifier\endcsname\undefined\to\everystarttext but a new

Re: [NTG-context] Why can not rm or rmtf fonts be set up by \definebodyfont macro?

2009/4/6 Wolfgang Schuster schuster.wolfg...@googlemail.com: Am 05.04.2009 um 23:25 schrieb Hans Hagen: sure, but i'm not too eager to add that kind of hackery so loading a new typeface then makes more sense My hack can be done in a cleaner way with

[NTG-context] definebodyfont vs. definebodyfontenvironment

(say 19.5pt), I have to put these lines in my preamble: \definebodyfontenvironment[19.5pt] \starttypescript [serif] [default] [size] \definebodyfont [19.5pt] [rm] [default] \stoptypescript and I get the output I want, but alas, not in the footnotes: there, font bar is not scaled. Would

Re: [NTG-context] definebodyfont vs. definebodyfontenvironment

an unusual size for the bodyfont (say 19.5pt), I have to put these lines in my preamble: \definebodyfontenvironment[19.5pt] \starttypescript [serif] [default] [size] \definebodyfont [19.5pt] [rm] [default] \stoptypescript and I get the output I want, but alas

Re: [NTG-context] definebodyfont vs. definebodyfontenvironment

On Feb 2, 2006, at 11:38 AM, Taco Hoekwater wrote: It is the token small, but it would be easier to set it to an explicit value. If you use \setupfootnotes[bodyfont=14.4pt] you don't even need a \definebodyfontenvironment, because it is predefined. (untested) Cheers, Taco Taco,