We don't know what you expect, but it is really -*- text -*-
Copyright (C) 2005, 2007 DMTCS, Nancy, France
Author: Jens Gustedt <Jens Gustedt [AT] dmtcs org>

This directory contains a proceedings kit for DMTCS. 

* What you need:

A system that is equipped with a modern version of LaTeX, GNU make,
and perl. Most mondern *NIX-like systems should have these.

Please also read the instructions that come with the dmtcs style file
yourself. Try to convice the authors that this is important and that
they should stick to the rules that are expressed there. This will
save you a lot of work.

* What you have to provide:

In this directory (named MAIN, say) create subdirectories, one for
each paper. The names of these directories should only consist of
alphanumeric characters, mixed case if you like.

Put *all* files that correspond to a paper in its directory. If a
directory is named DIR the main LaTeX file in it should have the name
DIR.tex. 

Each paper *must* compile flawlessly with the dmtcs.cls and the option
`proceedings' like in the examples. This should be true for both,
latex to produce (dvi,ps,ps.gz) and pdflatex (pdf). But see also below
under ``Graphics''.

Please take special care to the `author', `title', `keywords' commands
and the `abstract' environment. *None* of them should include
unbreakable spaces (`\ ' or '~'), non-ascii characters, `\cite' or
`\ref' commands, or any other home-brew commands provided by the
authors. Simply spell everything out in LaTeX, please! 

The only file that should *not* be in DIR is dmtcs.cls. We prefer to
use the same file for all submissions, just to be sure that this is
the most recent one. 

Create (or modify) a file paperlist.txt here in MAIN. Put one line
with the corresponding directory name in that file. Order is
important, this is the order in which the papers will appear in the
volume. This file `paperlist.txt' should not contain empty lines and
properly terminate with a end-of-line character.

Create (or modify) a file volume-info.tex here in MAIN. It should
contain four different data, see the example file that came with this
kit. You should have received publicationid from us, this is a two
letter code.

* What you should do:

Backup your data. Don't forget this.

make Makefile-inc
make prevs
make ps

verify that all individual papers compiled flawlessly, then

make pdf

* What this will do for you:

A whole chain of events should happen. Several files and links are
produced and latex and pdflatex are called on each paper twice. This
will probably take some time, lean back and relax.

If everything worked smoothly the page numbers of the papers should
now be consecutive according to the order in which they are listed in
paperlist.txt. 

If you now latex the file frontpage-sample.tex you should see a cover
page and an index generated. Best is probably to copy this
frontpage-sample.tex to frontpage.tex. Edit this file to yours needs
but please leave the legal stuff in. 

This should be all you have to do to generate a printable version of
your proceedings volume. 

* If something goes wrong:

You may do things step by step.

make Makefile-inc
make prevs
make ps
make pdf

Then you might sucsessively look into your source directories and try
to compile there. Good luck.

* What this doesn't do:

This will not yet produce the web pages for the journal. This is
somewhat tricky since this has to convert the abstracts from latex to
html. The code to do this can not be released, since it is a bit too
complex to use.

But what you could do to help us is to run

./buildPlain.pl

This should produce subdirectory `plain' with one file for each paper
containing the metadata of each. If then you do 

grep TITLE plain/*abs

you should see a list of all the paper titles in the right
order. There should be no TeXnicalities that remained in there, only
html. The same goes with AUTHOR in the place of TITLE. Please check if
all accented characters etc were successfully transcribed into
entities, e.g {\'e} should have been translated into &eacute;


* What you have to provide to us:

If the `make pdf' worked well for you and this is now definitively the
final version that went to print... do `make tgz' and provide us with
the resulting file that is named dm??.tgz. It contains all the files
that where produced plus the sources.

Please do *not* send it per email. Put it on a web page or something
like that and tell us about it.

Also don't forget that *you* had to collect the signed copyright
forms. Please send them via snail mail.

Then last but not least, we archieve any correspondance concerning
DMTCS of scientific value. It would be a good idea to bundle the
reports that you sent out to the authors and make them available to
us.

* At the end:

Enjoy your conference.

**********************************************

* Graphics

Usually the most complex task for such a volume is to get all the
nice graphics right. You *must* use the graphicx package for this,
epsfile is not allowed. The reason for that is simple, graphicx allows
to automatically chose files according to the output format that is
produced. This is done automatically **if and only if** you don't put
a file extension into the \usegraphics command. E.g

\usegraphics[width=5cm]{toto.eps}           % BAD!
\usegraphics[width=0.8\textwidth]{hui}      % GOOD

Most people will only give you graphics in one format .eps (or .ps) of
.pdf. Since we want to produce final versions in PostScript and PDF,
we have to generate the missing ones. In one direction this seems to
be easy, namely epstopdf produces nice .pdf from .eps. In the other
direction I didn't find anything as comfortable and reliable. If this
is just one such .pdf graphic to convert you might use gimp or
something alike.

If for one particular paper you are not able to produce pdf, place an
empty file named nopdf in the corresponding subdirectory. The same for
ps, place a file nops there, instead. You probably guessed that you
never should place both in the same subdirectory, since this wouldn't
produce anything.
