ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jeong Dalyoung <haksan@mac.com>
To: ntg-context@ntg.nl
Subject: 'TeX capacity exceeded' problem
Date: Fri, 12 Oct 2007 00:10:38 +0900	[thread overview]
Message-ID: <D21C6168-7820-4B4A-BEF1-529152E22E47@mac.com> (raw)

Dear all,

Finally, luatools is working(gwTeX, Mac OSX  10.4).

Following the instruction given by Thomas, I succeeded to run  
'luatools --generate'
but I got an error when I run 'luatools --ini --compile --verbose  
cont-en'.
There is a memory problem for the languages.
Following the suggestion, I add a line 'trie_size = 400000' at the  
end of texmf.cnf in the folder /usr/local/gwTeX/texmf.cnf.
After that  'luatools --ini --compile --verbose cont-en' is running  
without error and the format file is created in the folder /tmp/ 
luatex-cache/context/...

I test it using a simple file like
\starttext
some texts
\startlua
a = 1.5
b = 1.8
c = a*b
tex.print(c)
\stoplua
\stoptext

and it was working nicely.


But when I tested a sample file in the wiki,

\usetypescript[palatino]
\setupbodyfont[palatino,12pt]
\starttext
effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek
\sc effe fietsen 2: \input tufte $\sqrt{2}$ \eogonek
\stoptext

I got a fatal error. Here are some lines in log file.

.........
(/usr/local/gwTeX/texmf.pkgs/tex/context/base/type-siz.tex) (/usr/ 
local/gwTeX/texmf.pkgs/tex/context/base/type-otf.tex) (/usr/local/ 
gwTeX/texmf.pkgs/tex/context/base/type-tmf.tex) (/usr/local/gwTeX/ 
texmf.pkgs/tex/context/base/type-siz.tex
! TeX capacity exceeded, sorry [parameter stack size=60].
\donormalizedbodyfontsize #1.#2#3#4\to #5->
                                            \edef #5{#1\ifcase  
\fontdigits \o...
\docommand ...\scratchdimen \to \tempbodyfontsize
                                                   \setevalue {\??ft  
\fontcla...
\next7 #1,->\docommand {#1}
                            \doprocesscommaitem
<argument> \relax text,
                        script,scriptscript,x,xx,big,small
\doprocesscommalist ...aitem \gobbleoneargument #1
                                                   ,]\relax \global  
\advance ...
<argument> ...acommand [\fontsizelist ]\docommand
                                                   \copyparameters  
[\??ft \fo...
...
l.22 \stoptypescript


node memory in use: 1601 words out of 100604 (98904 untouched)
currently available: 1:3, 2:9, 3:3, 4:7, 6:4, 8:2 nodes
!  ==> Fatal error occurred, no output PDF file produced!


Would you please tell me what is wrong here?

Thank you.

Best regards,

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


             reply	other threads:[~2007-10-11 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 15:10 Jeong Dalyoung [this message]
2007-10-11 16:27 ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D21C6168-7820-4B4A-BEF1-529152E22E47@mac.com \
    --to=haksan@mac.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).