> 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 a
> #> 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-40
On Wed, Jul 28, 2010 at 12:41 PM, Hans Hagen 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 see from
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 of
> 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 : nt
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 t
> 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
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 using
> 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 fo
> 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
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
__
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 at typescr
As someone new to Context, I am trying to get to grips with font handling.
Reading through a fair amount of documentation it is not always to clear to me
what recommended practice in todays Luatex/MKIV enviroment is.
My setup is "Minimals" updated 26.7.2010 (luatex 0.60.2, MTXrun 2010.07.22)
se
13 matches
Mail list logo