Re: Installing ConTeXt under Unix

Re: Installing ConTeXt under Unix

[Hans Hagen]

Tobias Burnus wrote:

> File font-def.txt ended with ^^Z (I removed it and teTeX (web2c) was
> happy again).

Then thats the one! Add \endinput as a last line!

> BTW: Which Linux Distribution are you going to use?
> RedHat 5.0, SuSE5.2, Candela OpenLinux or Debian or ...?

The german one, Suse. (Kees and) I tested RedHat, but the Suse install
is better. 

Hans

-----------------------------------------------------------------
                                              Hans Hagen | PRAGMA
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@pi.net
-----------------------------------------------------------------

Re: Installing ConTeXt under Unix

[Thomas Esser]

> Where does this page come from? All context source files should end with
> \endinput (to prevent problems with eof characters) and <ff> and
> <cr><lf> should also give no problems. This problem is unix oriented,
> and can be overcome by unzipping with a certain (i forgot one) switch
> concerning lineendings or so. 

I used UNIX unzip with options -L -a and the files looked ok. Some files
don't have \endinput:

base: context.tex font-kb.tex table.tex font-def.tex
modules: s-faq-00.tex s-faq-01.tex s-faq-02.tex s-faq-03.tex
ppchtex: m-ch-de.tex m-ch-en.tex m-ch-nl.tex m-chemic.sty m-chemie.sty ppchtex.noc

Thomas

Re: Installing ConTeXt under Unix

[Hans Hagen]

Tobias Burnus wrote:

> I personally recommend teTeX 0.9 (since one year a beta version,
> but quite stable); Available at:
> ftp://ftp.informatik.uni-hannover.de/home/te/private/.0.9/

teTeX uses web2c. 

> Since teTeX 0.9 also has a texmf.cnf file (in my case in /usr/lib/teTeX)

indeed. 

> PS: I hope that teTeX 1.0 will be released soon, since 0.9 is in no
> Unix/Linux/FreeBSD distribution included.
> Since it (0.9) is based on Web2c 7.2 and will include CONTeXT we
> (hopefully) won't need such an install guide anymore.
> (The TeX Live CD is based on teTeX 0.9)

For Unix users (soon I will be one too) a manual is needed anyway, if
only to understand localizing. For instance, users should be able to
update their context format file. 

Hans  

-----------------------------------------------------------------
                                              Hans Hagen | PRAGMA
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@pi.net
-----------------------------------------------------------------

Re: Installing ConTeXt under Unix

[Hans Hagen]

Hello Berend and others,

Here are some remarks on the draft installation manual. 

> Type `context -ini context' to create the format file. Two questions
> are asked, press Enter twice to install the dutch interface to ConText
> or enter `english' twice to install the english language interface or
> `german' to install the german language interface.

Actually there are four files (1) context.tex, (2) cont-nl, (3) cont-de
and (4) cont-en. 

The fastest way to go is to use 2, 3 and 4. These run without asking
questions. The advantage is that one can say 

  %&cont-en 

on top of his document to load the relevant format automatically. 

> ----------output----------------
> 9042 words of font info for 28 preloaded fonts
> 15 hyphenation exceptions
> Hyphenation trie of length 20024 has 577 ops out of 1501
>   70 for language 9
>   139 for language 3
>   181 for language 2
>   187 for language 1
> Output written on context.dvi (1 page, 280 bytes).
> Transcript written on context.log.
> /usr/local/texmf/tex/context# ls context.fmt
> context.fmt
> -------end output---------------

Now, here went something wrong! There is one page produced. First, no
fonts should be preloaded at all, which makes context more tfm
independant.  

Where does this page come from? All context source files should end with
\endinput (to prevent problems with eof characters) and <ff> and
<cr><lf> should also give no problems. This problem is unix oriented,
and can be overcome by unzipping with a certain (i forgot one) switch
concerning lineendings or so. 

Tobias, can you try to trace the file that causes the troubless? Just
move up the \dump command in context.tex until the problem (page 1)
disappears. 

> Dit is CONTEXT versie <1998.5.21 > interface <dutch> meldingen <dutch>
> 
> ..
> 
> Copyright 1990-1998 / PRAGMA / J. Hagen - A.F. Otten
> 
> korps          : 12pt romaan wordt geladen
> specials       : postscript,yandy,dviwindo,pdf geladen

For unix users: say 

  \usespecials[reset,ps,tr,pdf] 

in the file 

  cont-sys.tex 

That way, the right special will be loaded at runtime.

Concerning the memory, here are the values I use:

pool_size        =  500000 
string_vacancies =   25000
max_strings      =   50000
pool_free        =  475000  % watch out Berend, you lost a 0  

trie_size        =   64000
hyph_size        =    1000
buf_size         =    5000
nest_size        =     750
max_in_open      =      15
param_size       =    1500
save_size        =    8000
stack_size       =    1500

Now concerning web2c, here I use the pdftex alternative. This one is
100% dvi compatible, but also offers pdf output. Just say 

  \usespecials[tpd] 

at the begin of the file, and get yourself pdf! One binary and one
format thereby serve both output formats!

Hans 

-----------------------------------------------------------------
                                              Hans Hagen | PRAGMA
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@pi.net
-----------------------------------------------------------------

Re: Installing ConTeXt under Unix

[Tobias Burnus]

> Hai All,
Haai everybody, hallo Berend,

> Here my first version of installing ConTeXt under Unix. Let me know what you thing of it.
Let's go on commenting: 

> *************************START*************************
> Step 1: do you have web2c?

You don't need a web2c based TeX distribution, but if you
don't want to re-compile the source you should have 
web2c 7.2 (7.1 should work as well).
Using teTeX 0.4 you are out of luck (teTeX 0.4 is based on
Web2c 7.0). (have a look at the PPCHTeX-FAQ for recompiling teTeX 0.4)

I personally recommend teTeX 0.9 (since one year a beta version,
but quite stable); Available at:
ftp://ftp.informatik.uni-hannover.de/home/te/private/.0.9/

Since teTeX 0.9 also has a texmf.cnf file (in my case in /usr/lib/teTeX)
is this not a reliable way to tell whether the next will work.
Try to run tex instead, it will show the version.

> Step 4: unpack your context distribution
> 
> But where? Assuming you have the TDS, my main TeX directory is in
> /usr/local/share/texmf. My local TeX directory is in
> /usr/local/texmf. I've installed context in my local
> directory. Example:
> 
> ----------output----------------
> /usr/local/texmf/tex$ mkdir context
> -------end output---------------

Using teTeX 0.9 there is already an emty context directory
(which will be filled sooner or later :-)

> Assuming you have the unzip command, you can simply unzip the context
> distribution by saying something like `unzip
> /home/berend/download/context.zip'. Replace the directory
> `/home/berend/download' by the directory where you have stored the
> context distribution.

Since the most files are upper case I would recommend to 
change them to lower case by running  unzip -L

> Step 6: Move the context format file to its correct destination
> 
> You need to move the `context.fmt' file to its proper location. On my
> system this is the main TeX directory tree in the web2c directory. So
> I need to type:
> 
> ----------output----------------
> /usr/local/texmf/tex/context$ mv context.fmt /usr/local/share/texmf/web2c/
> -------end output---------------

I prefer to create a symbolic link since ConTeXt is updated fequently...

> Step 7: adjust your kpathsea searching database
> 
> TeX does quite some directory searching. To speed them up a special
> database is used with all files TeX uses. So although context.fmt is
> in the correct location, it still might not be found. cd to your main
> TeX directory and use `mktexlsr' to update your database. mktexlsr may
> also be called differently like `MakeTeXlsR'.
> 
> ----------output----------------
> /usr/local/share/texmf$ mktexlsr
> mktexlsr: Updating /usr/local/texmf/ls-R...
> mktexlsr: Updating /usr/local/share/texmf/ls-R...
> mktexlsr: Updating /var/tmp/fonts/ls-R...
> mktexlsr: Done.
> -------end output---------------

Using teTeX you may run texhash for that purpose (which invokes the
right program)

> Step 8: test it
> 
> Now create a simple context file and try to compile it. A simple
> context file is:
> 
> ---------------------------
> \starttekst
> \stoptekst
> ---------------------------
or for English and German:
\starttext / \stoptext

In fact the shortest possible file would be:

Hello world
\bye

> Compile it with `context test.tex'. Your output should be like this:

Tobias

PS: I hope that teTeX 1.0 will be released soon, since 0.9 is in no
Unix/Linux/FreeBSD distribution included.
Since it (0.9) is based on Web2c 7.2 and will include CONTeXT we
(hopefully) won't need such an install guide anymore. 
(The TeX Live CD is based on teTeX 0.9)

Installing ConTeXt under Unix

[Berend de Boer]

Hai All,

Here my first version of installing ConTeXt under Unix. Let me know what you thing of it.

*************************START*************************

This guide `Installing ConTeXt under Unix for dummies' tries to give
you all the information you might need to successful install ConTeXt
on Unix based TeX implementations.

Note: if you get the TeX Live CD no 3 (not yet available), ConTeXt
will be preinstalled.

Assumptions:
1. You have a web2c based TeX implementation. If you don't know, we
try to find this out in the first step.
2. You use kpathsea file searching. If you have web2c you probably
have kpathsea file searching. 
3. Your system uses the TeX Directory Structure (TDS). This is not
necessary, but if you have it your directory structure will probably
be closer to mine, so some examples might be easier to follow.
4. Your system is close enough to BSD derived systems so my examples
work. I've tested this guide on FreeBSD, so if something doesn't work
on your Unix flavor, let me know.

Step 1: do you have web2c?

We try to find this out by locating texmf.cnf, the main TeX
configuration file. The fastest way to find this file is using the
`locate' command, but you need to have an up-to-date locate
database. If you don't have a locate database or have just installed
TeX this command won't help you, but see the next command `find'.

Using locate, you simply can type `locate texmf.cnf'. On my system
this gives quite some entries, I show you some of it's output:

----------output----------------
/home/berend# locate texmf.cnf
/usr/local/share/texmf/source/web2c-7.2/kpathsea/texmf.cnf
/usr/local/share/texmf/web2c/texmf.cnf
/usr/local/share/texmf/web2c/texmf.cnf.berend
-------end output---------------

If you don't have locate, you can find it by typing `find / -name
texmf.cnf'. On my system this gives:

----------output----------------
/home/berend# find / -name texmf.cnf
/usr/local/share/texmf/source/web2c-7.2/kpathsea/texmf.cnf
/usr/local/share/texmf/web2c/texmf.cnf
-------end output---------------

If you didn't find texmf.cnf, this guide probably isn't of no
help. You don't have a web2c based TeX implemtentation.

Step 2: modify texmf.cnf with special ConTeXt features

ConTeXt is quite a large system, so with the default settings you
can't use ConTeXt. You need to modify texmf.cnf and add the following
entries somewhere. You could add them to the end of this file:

---------------------------
buf_size.context = 50000
hash_extra.context = 15000
main_memory.context = 1100000
max_strings.context = 55000
nest_size.context = 500
param_size.context = 1500
pool_free.context = 47500
pool_size.context = 500000
save_size.context = 5000
stack_size.context = 1500
string_vacancies.context = 45000
---------------------------

You probably need superuser privileges to modify this file so either
use the `su' command to become superuser, or login under the `root'
account before modifying this file. You also need superuser priviliges
for the remaining steps.

Step 3: create the context command

Instead of calling TeX with the context format file everytime you want
to compile a ConTeXt file, it's much easier to create a special
command which autoloads the ConTeXT format file.

First, you need to know where your tex commands are installed. I.e. if
you type `latex' or `tex' or `initex', where are these commands
stored? You can use `locate latex' or `whereis latex' or 
`find / -name latex' to find the directory where these commands are
installed. For example, on my system they are in
/usr/local/bin/i586-freebsd2.2, but on your system they might be in
/usr/local/bin or in some other +directory.

If you have found the directory, cd to it and create a symbolic
link. Example is below:

----------output----------------
/home/berend$ cd /usr/local/bin/i586-freebsd2.2      
/usr/local/bin/i586-freebsd2.2$ ln -s tex context
-------end output---------------

Step 4: unpack your context distribution

But where? Assuming you have the TDS, my main TeX directory is in
/usr/local/share/texmf. My local TeX directory is in
/usr/local/texmf. I've installed context in my local
directory. Example:

----------output----------------
/usr/local/texmf/tex$ mkdir context
-------end output---------------

So go to your local TeX directory, `/usr/local/texmf' in my case. Make
sure you have a subdirectory called `tex' there, else create it. Next
go to the `tex' subdirectory and create the `context'
subdirectory. And go to the context subdirectory.

Assuming you have the unzip command, you can simply unzip the context
distribution by saying something like `unzip
/home/berend/download/context.zip'. Replace the directory
`/home/berend/download' by the directory where you have stored the
context distribution.

Step 5: creating the context format file

If TeX would have to parse and compile the context.tex file everytime
you want to compile a context program, it would easily take minutes to
compile a program if you don't have a PIII at 1GHz. So TeX has the
ability to precompile the context main macro's and load them very fast
at startup. This process is called creating a format file.

If you encounter problems somewhere in this process, see below this
section to the paragraph starting with 'Problems:'.

Type `context -ini context' to create the format file. Two questions
are asked, press Enter twice to install the dutch interface to ConText
or enter `english' twice to install the english language interface or
`german' to install the german language interface.

If this command completes there exists a new file in your directory
called `context.fmt'. Check this by using `ls context.fmt'. You should
see output similar to mine:

----------output----------------
9042 words of font info for 28 preloaded fonts
15 hyphenation exceptions
Hyphenation trie of length 20024 has 577 ops out of 1501
  70 for language 9
  139 for language 3
  181 for language 2
  187 for language 1
Output written on context.dvi (1 page, 280 bytes).
Transcript written on context.log.
/usr/local/texmf/tex/context# ls context.fmt
context.fmt
-------end output---------------

In this example I also have shown the last lines of the context
compilation process, before typing 'ls context.fmt'.

Problems:

Problem 1: "If I type `context -ini context' I get a command not found
error"

You probably see something like
----------output----------------
/usr/local/texmf/tex/context# context -ini context
bash: context: command not found
-------end output---------------

Either you didn't create the `context' command (see step 3) or your
`context' command isn't in your path. You can check your path my
typing `echo $PATH'. The directory where your context command is
stored should be listed here.

Problem 2: "`context -ini context' did start, but it didn't finish
properly, but said something about pool sizes"

Your context command isn't started with enough memory. Make sure you
did modify texmf.cnf (see step 2) and that you did modify the correct
texmf.cnf.

Step 6: Move the context format file to its correct destination

You need to move the `context.fmt' file to its proper location. On my
system this is the main TeX directory tree in the web2c directory. So
I need to type:

----------output----------------
/usr/local/texmf/tex/context$ mv context.fmt /usr/local/share/texmf/web2c/
-------end output---------------

If you don't know the location of your format files (all format files
are in one directory) either use `locate latex.fmt' or `find / -name
latex.fmt' to find this location.

Step 7: adjust your kpathsea searching database

TeX does quite some directory searching. To speed them up a special
database is used with all files TeX uses. So although context.fmt is
in the correct location, it still might not be found. cd to your main
TeX directory and use `mktexlsr' to update your database. mktexlsr may
also be called differently like `MakeTeXlsR'.

----------output----------------
/usr/local/share/texmf$ mktexlsr
mktexlsr: Updating /usr/local/texmf/ls-R... 
mktexlsr: Updating /usr/local/share/texmf/ls-R... 
mktexlsr: Updating /var/tmp/fonts/ls-R... 
mktexlsr: Done.
-------end output---------------

Make sure both your main TeX tree (/usr/local/share/texmf in my case)
and your local TeX tree (/usr/local/texmf in my case) are updated.

Step 8: test it

Now create a simple context file and try to compile it. A simple
context file is:

---------------------------
\starttekst
\stoptekst
---------------------------

Compile it with `context test.tex'. Your output should be like this:

----------output----------------
home/berend/tmp$ context test
This is TeX, Version 3.14159 (Web2C 7.2)
(test.tex

Dit is CONTEXT versie <1998.5.21 > interface <dutch> meldingen <dutch>

..

Copyright 1990-1998 / PRAGMA / J. Hagen - A.F. Otten

korps          : 12pt romaan wordt geladen
specials       : postscript,yandy,dviwindo,pdf geladen
systeem        : aanmaken basale hulpfile
[1.2] )
Output written on test.dvi (1 page, 272 bytes).
Transcript written on test.log.
-------end output---------------

This is it. I would like to know about problems you encounter or
suggestions to clarify certain matter. Mail your comments to the
context mailing list (ntg-context@ntg.nl) or to Berend de Boer
(berend@pobox.com)

*************************END*************************

Groetjes,

Berend.