From: Allin Cottrell <cottrell@wfu.edu>
Subject: newbie problem with modules
Date: Thu, 9 Aug 2001 15:47:19 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0108091531560.11944-100000@ricardo.ecn.wfu.edu> (raw)
I've used LaTeX for a long time, and recently decided to try context.
I can get a trivial document to compile OK (to pdf) but when I tried
using a presentation module (pre-original) I got an error with
use of \dodefinedfont "not matching its definition". Any guidance
would be appreciated. Partial output from th texexec run follows.
This is pdfTeX, Version 3.14159-14h-released-20010417 (Web2C 7.3.3.1)
(./try.tex{/usr/share/texmf/tex/pdftex/base/pdftex.cfg}
ConTeXt ver: 2001.7.11 fmt: 2001.8.9 int: english mes: english
[ info on loading of files ]
then:
systems : begin file try at line 3
! Use of \dodefinedfont doesn't match its definition.
<argument> ... \dosingleempty \dodefinedfont \@EA
\setvalue #1->\expandafter \def \csname #1
\endcsname
\dosetunexpanded #1#2->\@EA #1\@EA {\@EA #2\@EA }
\@EA {\@EA \donottest
\csna...
<argument> ...ed \setvalue {\string \definedfont }
{\dododefinefont
{\string ...
\doifinstringelse ...se \@EA {\@@@instring }{#2}#3
\else #4\fi
\dodefinedfont ...font [\string \definedfont ][#1]
\fi \getvalue
{\string \de...
...
l.4 \TitlePage {My first context example}
The source file is just a trivial test:
\usemodule[pre-original]
\starttext
\TitlePage {My first context example}
\Topics {Today's talk}
\Topic {First item}
This is the first item in my talk.
\Topic {Second item}
This is the second item in my talk.
\Subject {A subitem}
Here is stuff under a ``Subject'' heading.
\Subject {Another subitem}
Here is stuff under a new ``Subject'' heading.
\stoptext
--
Allin Cottrell
Department of Economics
Wake Forest University, NC
next reply other threads:[~2001-08-09 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 19:47 Allin Cottrell [this message]
[not found] <Pine.LNX.4.33.0108091531560.11944-100000@ricardo.ecn.wfu.e du>
2001-08-20 9:13 ` 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=Pine.LNX.4.33.0108091531560.11944-100000@ricardo.ecn.wfu.edu \
--to=cottrell@wfu.edu \
/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).