[NTG-context] presentation in ConTeXt and XeTeX
Dear all,
I tested presentation mode with "pre-green" module and it worked fine.
I also tested the same file with the addition of few lines which set
my personal font script for XeTeX-ConTeXt.
\usetypescriptfile[type-xkor]
\usetypescript[myface]
\switchtobodyfont[Myface, 12pt, rm]
Save the file(utf-8) and compiled it and I got errors:
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-akb.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-xtx.tex)
(/Users/dalyoung/Library/texmf/tex/xetex/type-xkor.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-enc.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-dis.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-siz.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-map.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-spe.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-akb.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-xtx.tex)
(/Users/dalyoung/Library/texmf/tex/xetex/type-xkor.tex)) (./context-
pre.tuo)
Runaway argument?
{^^G^^[⻊\usedmapfile {=}{original-base}\usedmapfile {=}{ec-public-l
\ETC.
! File ended while scanning use of \thisisbytesequence.
\par
\relax
\dodoreadfile ...normalinput \readfilename \relax
\the
\everyafterreadfile
\doutilities ...textension }\donothing \donothing
\the
\everyafterutilityrea...
...pass }\jobname \empty \relax \relax
\ifx \twopassdata
\empty \...
\firstofoneargument #1->#1
...
l.20 \starttext
? x
No pages of output.
Is there a way to use presentation module in ConTeXt-XeTeX
environment using my fonts?
Thank you.
Dalyoung___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] bug in \seeindex
The code in \seeindex has a bug. There was something in the mailing
list about a year ago (2004-06-21), but as far as I can see, the
patch Hans proposed then has been integrated into core-reg.tex.
Here's a minimal test file:
\starttext
This \index{this} and \index{and} that \seeindex{this}.
\placeindex
\stoptext
And the error log:
! Argument of \@@filterlevelpart has an extra }.
\par
}
\doifprevlevelelse ...tor \@@filterlevelpart [#1]}
\edef
\@@tocsectiontype {\...
\dosetpageregisterpage ...->\doifreglevelelse [#5]
{\dodosetpageregisterpage ...
l.46 ...isterpage{index}{,}{3}{2::0:0:0:0:0:0:0}{}
Unfortunately, the bug messes up the .tui file, so even if you delete
the \seeindex command, the file will not compile unless you delete
the .tui manually. Ideas, anybody?
Best
Thomas
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Q: http://wiki.contextgarden.net/Thumb_index
Quoting "Alexander Lazic" : > -- was [EMAIL PROTECTED] on Sep 27, 2005 at 08:10:43AM -- > On Die 27.09.2005 07:03, VnPenguin wrote: > >On 9/27/05, Alexander Lazic <[EMAIL PROTECTED]> wrote: > >> > >>I have used the code fro: http://wiki.contextgarden.net/Thumb_index > >> > >>TeXExec 3.1 - ConTeXt / PRAGMA ADE 1997-2002 > > > >Your ConTeXt and pdfetex are TOO old. Maybe you need update them. > > I use debian unstable/testing an have assume that this 'version' of > debian use the current stable version of the programs. So you may be interested in a packaging of the TeXlive for Debian GNU/Linux: http://www.tug.org/texlive/debian.html Greetings, Olivier ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] DOC/RTF to ConTeXt via XML
Idris Samawi Hamid said this at Tue, 27 Sep 2005 09:10:27 -0600: >Adam (privately) suggested hiring someone to write a structured format for >authors. Is that where docbook comes in? Ah, sorry about that. I meant you *could* hire someone to design a format, but the bigger point was that it would be rather futile without a user-level authoring tool backing it up! -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED] Lancaster University, InfoLab21+44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
RE: [NTG-context] DOC/RTF to ConTeXt via XML
Hi Duncan, I know little about xml and virtually nothing about Word (except that it's crap) so please forgive me if this is a stupid or clueless question-) >But you should also explore DocBook-in-ConTeXt, which >uses ConTeXt's native XML processing capabilities. Is it possible to create a Word template that is isomorphic with a DocBook format? Adam (privately) suggested hiring someone to write a structured format for authors. Is that where docbook comes in? Basically, authors in the humanities use Word and it's virtually a lost cause getting them to switch to anything else, even free tools like OO.o (let alone ConTeXt). It would have to be someting where I could do word=>docbook=>ConTeXt. Best Idris Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
RE: [NTG-context] DOC/RTF to ConTeXt via XML
Hi Christopher, Duncan, Hans, and Adam, Thank you so much for your detailed comments and suggestions. Again, I'm completely new to xml and feel like a fish out of water. OTOH I use sooo much time just manually extracting text (with innumerable transliteration diacritics) and then copying-pasting to WinEDT that I am willing to explore the xml approach if it can be made sane enough... >= Original Message From Christopher Creutzig <[EMAIL PROTECTED]> = >Duncan Hothersall wrote: >> Well, XSLT seems to have been designed, and certainly tends to be >> implemented, as a tool for simple transformations of small XML chunks. > > No, xslt is a tool for arbitrary xml -> xml conversions (and a little >more than that). Ok, you guys have lost me now-) Maybe the best thing to do is try something practical: take an average word article and see what's involved in converting it to ConTeXt. From what I gather so far the process goes something like doc => rtf rtf => OO.o OO.o => xml But here things get dicey because \startHans converting open office xml is not always easy; stay away from tab's and use high level constructs as much as possible \stopHans Question: Will a proper doc (or OO.o) template solve this problem or is this a post-OO.o-processing problem no matter what I do beforehand? >From this discussion it seems that I (as an xml ignoramous) would be better off converting to ConTeXt code rather than processing pure xml blocks (but maybe I'm wrong). Once I get a sane xml file (this seems to be the biggest problem) what is the best tool to convert this to ConTeXt? We are all extremely busy, of course, but if anyone finds this interesting I can send a sample doc article from my journal. Maybe we can do a MyWay or something to document this process for ourselves and others, as well as find the most practical approach to creating a sane workflow. Besides, this kind of project seems to be exactly the kind of thing to illustrate the full power of ConTeXt. This is a mid-term project so no urgency (I'll keep copying and pasting for now->) Thanks again you all for your advice. Best Idris Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] DOC/RTF to ConTeXt via XML
Duncan Hothersall wrote: > Well, XSLT seems to have been designed, and certainly tends to be > implemented, as a tool for simple transformations of small XML chunks. No, xslt is a tool for arbitrary xml -> xml conversions (and a little more than that). With a good implementation (say, saxon), working with moderately large trees is pretty fast. The stylesheet is actually compiled before running. > Obviously complex transformations can be constructed from a bunch of > simple transformations, but there comes a point when you should really Just about any programming language gives you simple operations to build whatever you want from. > just use a better tool - though these tend to cost serious money (e.g. „Better“ depends on your task at hand. > OmniMark). Also, most XSLT implementations use the DOM model, which is XSLT uses a DOM model, which is different from the W3C DOM model. > fine for a 50Kb file but will be incredibly resource-hungry if you're > processing files of 5Mb. At that point you want a streaming model, and That depends on what you want to do with your data. For many of my needs, a streaming model simply wouldn't work without keeping lots of information (to be processed later) in memory, defeating the model. I have found splitting my data into files that form conceptional units to be a good way, both for editing the files and for turnaround times. (I am using Makefiles, so the granularity of finding unchanged items for me is the file.) We are talking about almost 15MB here, which I regard as pretty much, considering it is almost pure text. Again, I don't mind using something else on XML data. I'm doing it myself. It all depends on what you want to do. In the case of transforming xml to ConTeXt, I would go for an xslt implementation, but ymmv. After all, the choice of tools always depends on many factors, including familiarity. (I've continued using perl instead of ruby for ages, until recently, for that reason.) > for a streaming model you want a better suited language than XSLT. As I > say, horses for courses. For article-length pieces and simple > transforms, XSLT might suffice. For number crunching, xslt is certainly inadequate. Transforming books of average length (say, 300-500 pages) is certainly doable, although I would go for a transformation chapter-by-chapter,especially considering that we are talking about a process where crossreferences etc. are going to be handled later in the chain. But I thought we were talking about article-length pieces anyway? Christopher ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] interaction in \cite
Hello Adam, The module was written at a time when I was not too well versed in ConTeXt yes, and because I only produced paper documents, I had no need for interaction anyway. I'll see what I can do. Actually, \in[bibref] should jump you to the right place in the publication list, but it produces a numbered link that (the page number, I guess). Cheers, Taco Adam Duck wrote: Hello ConTeXters, I do not want to ask too much, especially as Taco already mentioned he'll be doing a patch for the BibTeX-module... But how do I setup interaction in \cite? \setupinteraction[state=true] works for \at, \in and in the contents but not for \cite. As I weren't able to find it in the documentation nor in the archives, I'll try here. Thx in advance, Adam. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Beta bib module release
Hi,
I have prepared a beta release of the bibliography module,
and uploaded it as
http://tex.aanhet.net/bib/m-bib-beta-20050927.zip
Because it is only a beta, I have not fixed the documentation yet.
The differences between this version and the one in the ConTeXt
distribution are outlined below.
I know that the wishlist is quite long, and there are even still
bugs I have not looked into, but I have to release *something*
otherwise nothing will ever happen. Somehow I never seem to get
around to working on the module. :-(
Comments (and testfiles) are welcome, and feel free to update
the wishlist on the wiki :
http://wiki.contextgarden.net/User:Taco/Bib
Happy TeXing, Taco
==
Bugfixes:
* The extra spaces in the output of authors and editors
inside the publication list should be gone.
* \newbibfield now works as advertised
* It is possible to use context commands with the same
name as a bib fieldname inside the arguments of the
fields. This now compiles correctly:
\startpublication[k=garden,t=misc,a={Wiki people}]
\thekey{Wiki people}
\title{The \type{\ConTeXt} garden}
\note{See also \useurl[pedia]{http://wikipedia.com}\url[pedia]}
\url{http://wiki.contextgarden.net}
\stoppublication
New features:
* Two new styles are now part of the distribution:
bibl-apa-de.tex and bibl-ssa.tex
* \cite now accepts \setupcite arguments in the
optional argument, so you can do stuff like
\cite[right={, chapter 5)}][key]
The commands
\cite[alternative=author][key]
and
\cite[author][key]
are equivalent
* The bibtex fields URL and LASTCHECKED have been added
to the bst files.
* Two new \setupcite arguments 'andtext' and 'otherstext'
have been added, and the language-dependancy of the bst
files has been removed.
* There is a new type of \citation:
\cite[url][key]
It does not do any kind of interaction, if you want that
you have to wrap the \cite in another command. Internally,
this uses the new 'u=' argument to \startpublication.
* Also, \cite[doi][key] now actually does generate the doi in
the text (this uses the 'o=' argument to \startpublication)
* Finally, you can get selected data bits from a publication
by using
\getcitedata [url] [garden] to \gardenlink
(in this case, \gardenlink will be \def-ed to the value
of the \url{..} field in the bib item with label 'garden').
Discontinued:
* I have removed t-bibltx.tex. All it did was define the
\newcommand command, and you are better off using the
new latex emulation module for that.
* I dropped support for the INSTITUTE field in bibtex
(it was never actually used anyway)
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] DOC/RTF to ConTeXt via XML
Slightly OT, sorry: >>OpenOffice.org does allow you to attach an XSLT stylesheet to an export >>process which therefore allows you to do a (limited) transformation from >>the visual markup which is its native format to a more structured one > > Why „limited“? Well, XSLT seems to have been designed, and certainly tends to be implemented, as a tool for simple transformations of small XML chunks. Obviously complex transformations can be constructed from a bunch of simple transformations, but there comes a point when you should really just use a better tool - though these tend to cost serious money (e.g. OmniMark). Also, most XSLT implementations use the DOM model, which is fine for a 50Kb file but will be incredibly resource-hungry if you're processing files of 5Mb. At that point you want a streaming model, and for a streaming model you want a better suited language than XSLT. As I say, horses for courses. For article-length pieces and simple transforms, XSLT might suffice. > Also, don't limit your authors to Word. Offering Word is obviously a > requirement, but if you go the way through OOo, there would be no point > in not offering an OOo template file. If you are using a standard xml > format, such as (a subset of) DocBook or TEI, you probably should accept > articles in that format, too. And, of course, ConTeXt. Absolutely; particularly if you can offer authors an incentive or direct benefit from adopting OO.o, such as speed of turnaround of proofs, etc. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] How up-to-date is cont-enp.pdf
On Die 27.09.2005 10:22, Adam Lindsay wrote: No. :) Okay, okay i understand ;-) It's in the early stages yet. Well i can wait, and work with the onlineresources. greetings al ;-) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] How up-to-date is cont-enp.pdf
Alexander Lazic said this at Tue, 27 Sep 2005 10:17:18 +0200: >>- a general overview of context will be provided by a book written by >>steve peter and adam lindsay > >Do you know when the book will arrive? No. :) It's in the early stages yet. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED] Lancaster University, InfoLab21+44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] DOC/RTF to ConTeXt via XML
Duncan Hothersall wrote: >>Question: Is it possible to design a doc or rtf template that Open Office can >>convert to a sane, consistent xml format? > > > OpenOffice.org does allow you to attach an XSLT stylesheet to an export > process which therefore allows you to do a (limited) transformation from > the visual markup which is its native format to a more structured one Why „limited“? Complicated things are just, well, a bit complicated to achieve. It is certainly possible to get a structured document from, say, an average xhtml file. I would prefer not to write that code, though. It would be rather boring and full of hard-to-read special cases. > which you would need. But the biggest challenge is that all > wordprocessors are designed for visual editing, meaning that there are, > for example, 15 or so different ways to get a bulleted list in Word, > creating 15 or so different RTF constructs, and coping with this can be > a nightmare. Yes, it can. (Although RTF is completely unrelated to this problem, since OOo would read the Word file. And the OOo step greatly simplifies the problem, since iirc the OOo format has just one or maybe two ways of saving bulleted lists. Or were you refering to different bullets?) The stricter your rules for the authors are, the easier it is to write the required xslt program. If your authors expect to be able to write chapter headers by manually switching to a font in the range of 20 to 24 pt and adding a number in front, you've got a hell of a coding session in front of you. If, otoh, you take the dictatorical approach of telling them in advance that manual font changes (maybe apart from pseudo-italics and pseudo-bold which will be mapped to \em in the end) will simply be ignored, your code will be much easier but you may have a problem with the authors. > The FO approach (Paul Tremblay's focus) is one way to process XML to > paginated output, but there are many others. Personally I don't like the > FO approach, for a variety of reasons, but I'm sure others have had > success with it. But you should also explore DocBook-in-ConTeXt, which > uses ConTeXt's native XML processing capabilities. And don't rule out The advantage of using DocBook is that you get a very rich set of capabilities. The disadvantage can be described in almost the same words, plus, as I said before, DocBook is one of the most verbose formats in common use. If you only use the format as an intermediate step, that is irrelevant, but if your authors willsend in files that way, it is not. > using a separate scripting language to convert XML into ConTeXt as a > batch process, since that will give you the ultimate flexibility in > accessing all of ConTeXt's abilities. Personally, I'd use xslt for that. Navigating the xml tree is extremely easy and writing out text instead of xml is not really a problem. >>Question: Does the entire journal have to be in programmed in xml or can >>ConTeXt process xml locally? For example, I may have my own article done in >>COnTeXt mixed with other articles done in rtf=>xml. > > > You can just put XML into \startXMLdata ... \stopXMLdata blocks. I do > this for MathML processing within a larger ConTeXt document. I'd approach Idris' problem the other way round: Transform the xml files to ConTeXt and leave the ConTeXt files as is. Then, texexec the whole thing. >>Any other advice (and/or pitfalls to watch for) would be appreciated. This >>sounds very promising! > > > Horses for courses. It's possible to get sucked into things like an FO > implementation or an XML conversion and find that you have spent months > perfecting it and it only shaves half an hour off your production time! Amen. Also, don't limit your authors to Word. Offering Word is obviously a requirement, but if you go the way through OOo, there would be no point in not offering an OOo template file. If you are using a standard xml format, such as (a subset of) DocBook or TEI, you probably should accept articles in that format, too. And, of course, ConTeXt. Christopher ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Q: http://wiki.contextgarden.net/Thumb_index
On Die 27.09.2005 09:42, Hans Hagen wrote: an option is to download the linux minimal distribution from out site and use that for testing, install it in (e.g.) Yes, i must go this way. Greetings al ;-) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] How up-to-date is cont-enp.pdf
Hi, On Die 27.09.2005 09:39, Hans Hagen wrote: - actually it's a partial manual, some chapters are still 'unedited' - because i don't want too much detail in it, some topics got their own manual (column sets, details, color, metafun, tables, etc) - i'll redo the manual (maybe start this winter) and may split off more parts and/or add other (easier to maintain) Thanx for explain ;-) - a general overview of context will be provided by a book written by steve peter and adam lindsay Do you know when the book will arrive? greetings al ;-) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] DOC/RTF to ConTeXt via XML
> Question: Is it possible to design a doc or rtf template that Open Office can > convert to a sane, consistent xml format? OpenOffice.org does allow you to attach an XSLT stylesheet to an export process which therefore allows you to do a (limited) transformation from the visual markup which is its native format to a more structured one which you would need. But the biggest challenge is that all wordprocessors are designed for visual editing, meaning that there are, for example, 15 or so different ways to get a bulleted list in Word, creating 15 or so different RTF constructs, and coping with this can be a nightmare. > If the Tremblay approach is rich > enough, that would solve a lot of problems! Here is my idea: > > 1. Give each author a doc/rtf template for formatting their article; > 2. Use OpenOffice to convert to xml; > 3. Use the Tremblay method (have not tried it yet) to process this in Context. The FO approach (Paul Tremblay's focus) is one way to process XML to paginated output, but there are many others. Personally I don't like the FO approach, for a variety of reasons, but I'm sure others have had success with it. But you should also explore DocBook-in-ConTeXt, which uses ConTeXt's native XML processing capabilities. And don't rule out using a separate scripting language to convert XML into ConTeXt as a batch process, since that will give you the ultimate flexibility in accessing all of ConTeXt's abilities. > Question: Does the entire journal have to be in programmed in xml or can > ConTeXt process xml locally? For example, I may have my own article done in > COnTeXt mixed with other articles done in rtf=>xml. You can just put XML into \startXMLdata ... \stopXMLdata blocks. I do this for MathML processing within a larger ConTeXt document. > Any other advice (and/or pitfalls to watch for) would be appreciated. This > sounds very promising! Horses for courses. It's possible to get sucked into things like an FO implementation or an XML conversion and find that you have spent months perfecting it and it only shaves half an hour off your production time! Also, you do tend to have to make compromises in design if you want to be able to process directly from XML. But if you have sufficient throughput and an appropriate design, it can be a real boon. Hope that helps. Duncan ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] footnote bug
Hi, Just collect the 'real bugs' and i'll look into it asap; i'm away for a few days (dante meeting and such) and will pick up that thread afterwards. 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [dev-context] RE: [NTG-context] footnote numbering
Idris Samawi Hamid wrote:
{Title\footnote{test}} % 1
{Title\footnote{test}} % 2
\incrementnumber[footnote]
%\setupnumber[footnote][start=3] % or
%\setnumber[footnote]{3} % or
Test\footnote{test} % 4?
\stoptext
keep in mind that start is only used when a number is reset (per page, chapter, etc) and that when you set a number, it will be incremented at the next usage (so indeed 3 is needed to get 4 next)
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
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Q: http://wiki.contextgarden.net/Thumb_index
Alexander Lazic wrote:
Hi,
please can anybody help me about the following error, sorry i don't know
what the error can be :-(
I have used the code fro: http://wiki.contextgarden.net/Thumb_index
---
TeXExec 3.1 - ConTeXt / PRAGMA ADE 1997-2002
executable : pdfetex
format : cont-en
inputfile : thumb_index
output : pdftex
interface : en
options : color
current mode : none
TeX run : 1
This is pdfeTeX, Version 3.14159-1.10b-2.1 (Web2C 7.4.5)
entering extended mode
(./thumb_index.tex{/usr/share/texmf/pdftex/config/pdftex.cfg}
ConTeXt ver: 2003.1.31 fmt: 2005.8.2 int: english mes: english
language : language en is active
.
.
layout : calculating backgrounds
! Undefined control sequence.
\@@suthumbs ->\definemeasure
[thumbheight][\dimexpr \paperheight /\NOfChapte...
\executedefinedoverlay ...x {\the \everyoverlay #2
}}\dimen 0\wd
\scratchbox ...
\dodobackgroundbox ...4}{\dimen 6}{#3}{#4}{#5}{#6}
}}}\wd \extraframebox
\zer...
\rawprocesscommaitem ...commalevel \endcsname {#1}
\expandafter
\rawprocessco...
\rawprocesscommalist ... \rawprocesscommaitem #1,]
,\global \advance
\commale...
\dobackgroundbox ...st [#2]\noexpand \docommando }
\box #1\hss }}
...
l.45 \chapter{second}
\dorecurse{10}{\input davis }
? No pages of output.
---
Greetings
al ;-)
old + new context mixed up
an option is to download the linux minimal distribution from out site and use that for testing, install it in (e.g.)
/usr/local/mytex
go there, and run
. setuptex (shell script)
and then
mktexlsr
plus
texexec --make --all
and you should have a working context (when you open a new console setuptex is to be run once before you start working)
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
-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] How up-to-date is cont-enp.pdf
Alexander Lazic wrote: Hi, i hope it's not a to bad question but how up-to-date is: cont-enp.pdf => November 12, 2001 and are the .tex-Files available for look and learn ;-) Just to satisfy my curiosity ;-) - actually it's a partial manual, some chapters are still 'unedited' - because i don't want too much detail in it, some topics got their own manual (column sets, details, color, metafun, tables, etc) - i'll redo the manual (maybe start this winter) and may split off more parts and/or add other (easier to maintain) - a general overview of context will be provided by a book written by steve peter and adam lindsay 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
