Introduction

This page contains some hopefully useful information for creating your write up for the lattice 2005 conference. The definitive information on the look and feel of the paper is controlled by the POS style file that you will be sent by email.

Revising submitted papers

If for some unavoidable reason a manuscript submitted to the PoS site needs revising, please ask the editors at lat05@liverpool.ac.uk. Please do not contact PoS, because this is the job of the editors. Also please don't attach anything to the email, we prefer that the authors upload their own contributions.

Combining contributions

PoS specify that each contribution must have one (and only one) "speaker". They are allocating numbers to each speaker. So it will be necessary to have at least the designated number of contributions. In the latex file the command \speaker cannot be repeated, and also it wouldn't look good to have the same paper title in two sessions of the conference in the PoS pages.

The editors, however, are happy for groups working together to trade pages: so that 6+6 might become 11+1 with the 1 being mainly a reference to the 11. Alternatively something like 8+4 is allowed.

Collaboration name(s)

One way to add a collaboration name is to use a second \author line: 
\author{HPQCD collaboration}
without address Another is just to add the collaboration in the author list.

Problems with pdflatex

The people at PoS have fixed the reported problems with the PoS.cls file. Information on how to get the updated class file is here.

This is information about the older class file, it is better to update. We have seen some problems with the PoS.cls class file with pdflatex and some recent versions of latex. Following Dirk Brömmel suggestion, you can get the file to latex if you add 

\newcommand{\pdfannotlink}{\pdfstartlink}
to the preamble. This worked with pdflatex at Liverpool but a lot of the hyperlinks were broken. PoS are working on this. Note that pdflatex requires that the figures are in PDF or JPEG format. This is inconvenient (and is the reason that the PoS LOGO causes problems)! We recommend that contributors don't use pdflatex (unless they really know what they are doing).

What is more inconvenient is that some linux distribution actually hardwire a link in of the form: 

/usr/bin/latex -> pdfetex

One way to force pdfetex to behave like latex is to add the command
\let\pdfoutput\defined before the preamble. 

\let\pdfoutput\defined
\documentclass{PoS}
(We thank Carsten Urbach for this tip.) This will produce a standard dvi file that you can convert into PDF using: 
dvips -Ppdf -z -G0  LAT2005_skeleton.dvi -o
ps2pdf -sPAPERSIZE=a4 LAT2005_skeleton.ps

Problems with older version PoS.cls

There is an updated version of the PoS.cls file. Information on how to get the new class file is here. The update occurred on 6th September.

Problems ps2pdf

Problem: The fi ligature is improperly rendered by ps2pdf with certain fonts such as helvetica and times bold. The spacing of the characters is incorrect in the pdf file only.

There are different variants of the ps2pdf command that produce different version of PDF. The above problems are removed if the command ps2pdf14 is used instead.

Multiple authors at different institutions.

QUESTION
We often have papers with many authors from several institutions - and wish to have the authors in a particular order. Is there a preferred way to set up markers (superscript numbers or letters) on the author's names to flag these addresses?

ANSWER
we suggest this way (here is the LaTeX code) 

\author{First Author$^a$, Second Scientist$^{ab}$ and Third
Writer$^{b}$\\
        \llap{$^a$}Department, University\\
        Place, Country\\
        \llap{$^b$}Departamento, Universidad\\
        Ciudad, Pais\\
        E-mail: \email{first@where.is}, \email{second@place.edu},
        \email{third@place.edu}}

Note the editor will only require that the email of the speaker is included. More than one email addresses is allowed.

Posters

A person who presented a poster is regarded by the POS style file as a speaker.

Adding colour text

Now that the proceedings are online it is possible to make more use of colour in the text. 
\usepackage{color}
\let\normalcolor\relax

%%
%%
We present \textcolor{red}{important} results
Please note that the editors will reject any paper that uses coloured text in a over-enthusiastic or inappropriate way.

Other routes

Don Sinclair reported that the recommended 
dvips -Ppdf -z -G0 lattice2005.dvi -o
ps2pdf -sPAPERSIZE=a4 lattice2005.ps
produced corrupted output on his machine, even with the updated class file. However the commands below worked. 
dvipdfm -p a4 lattice2005.dvi
There is information on dvipdfm . Both the above commands worked at Liverpool.

The references

There is a specific style of references that POS recommend (see our example). Please note that this is a recommendation. The editors will accept any paper with the references in a normal and reasonable scientific format. The editors do actually prefer the PoS style references. We particularly like the links in the document to the papers on the archive. Also, we like seeing the titles of the papers in the references, but we know that other people don't share our enthusiasm for helping the reader in this way, so we don't enforce this style.

The recommended style is the same as for the JHEP journal. Using the bibtex style file from JHEP makes the creation of the reference list easy. We recommend the use of bibtex, but you can of course do the references by hand (as long as they look like the standard format requested by POS). The output from bibtex needs some slight tweaking, particularly for capital letters. The output from SPIRES is not smart enough to deal with multiple collaboration names.

There is information from SPIRES on using bibtex.

We have created a simple example for new bibtex users.

Jonivar Skullerud has produced a modified version of the JHEP.bst file, which includes a couple of improvements on the original JHEP file.

The file is available from SPIRES.

Referencing other talks at the conference

QUESTION
Will there be an easy way for contributors to refer to other contributions (ie will the allocated number of contributions be available to use as a reference)?

ANSWER
Yes, you can refer to other contributions using the identification number assigned to each of them. That is, PoS(LAT2005)nnn, where "nnn" stands for the progressive number assigned to each contribution. Every author has its own number, that can be seen from their personal page. You can find this by clicking on LAT2005 (under the word "code") on your personal page for the conference.

If you want to also hyper-link into the presentation you can try 

@Article{MichaelCOLOR,
  author ="C. Michael ",
  journal="\href{http://pos.sissa.it/archive/conferences/020/008/LAT2005_008.pdf}{PoS(LAT2005)008}",
  title = "Hadronic decays",
  year="2005",
     eprint    = "hep-lat/0509023",
  howpublished="Talk presented at International Symposium on Lattice Field Theory (Lattice 2005)",
}
The above is clearly a bit of a hack. In principle the .bst file should be able to generate the href link from the PoS number. No one at Liverpool had the enthusiasm to implement this. In the above example the talk number at the conference is 008. The best easist thing to do is take the bibtex reference from SLAC and add the journal entry in the above format. The above example worked without the eprint field as well.

Or you can add the references by hand. 

\bibitem{farchioni}
 F.~Farchioni~et al.,
 \href{http://pos.sissa.it/archive/conferences/020/072/LAT2005_072.pdf}{{
 {\em PoS(LAT2005)072}}}.
The number of the conference is 20.

Physics comments

If you want to review or comment on papers submitted to the lattice 2005 conference, you are better using physics comments with the paper submitted to hep-lat. There is also an experimental linkage feature between the archives and BLOG enteries about a paper.
Lattice05 editors <lat05@liverpool.ac.uk>
Last modified: Tue Sep 27 16:00:30 2005