ICS'96 Final Paper Information
The final paper is due March 10, 1996.
The page limit (eight pages) is strict!
You should send high quality camera-ready print (two copies)
directly to the Program Chair, to arrive by March 10.
The paper should arrive together with a signed ACM copyright release form.
- Prof. Pen-Chung Yew
4-192 EE/CS Building
Dept. of Computer Science
University of Minnesota
200 Union Street
Minneapolis, MN 55455-0159 USA
When sending the final copy, please:
- Do not use staples, paper clips, or anything that will bend, fold,
punch holes through or leave marks on the paper; remember that your copy will
be reproduced directly, and a dirty original makes a dirty copy.
(I am aghast at how often we get bent, stapled or folded "camera-ready" papers.)
- Do not include page numbers on the paper; page numbers will be added
by the printer.
- Do not write anything on the front that you do not want reproduced.
- DO write lightly on the back of each sheet, in blue pencil
(NOT INK), the first author's last name and the page number.
If you do not have a blue pencil, use a black pencil, but write in a corner
on the back.
- Send two copies of the paper; we'll choose the best looking one.
- Remember to leave space on the first page for the
ACM Copyright notice.
- To help with preparation for LaTeX users, there are an old
acmproc.sty and a newer
style files available.
- ACM Copyright Procedures.
- Author's Guide to the ACM Interim Copyright Policies.
- Postscript copy of the ACM Copyright Form,
a signed copy of which MUST be returned with the final paper.
This Postscript file may be edited so that the author's names and paper title
come out printed by the Postscript printer.
An example is available.
- Suggestions for slide preparation.
- Postscript file showing the
- See the short note "How to give a good research talk" by
Simon L. Peyton Jones, John Hughes, and John Launchbury,
in the November 1993 ACM SIGPLAN Notices (Volume 28, Number 11, pages 9-12),
for some suggestions about giving a good talk;
you may not agree with all their points (few readers do), but they have
many good ideas for making your presentation more interesting and successful.
Michael Wolfe / firstname.lastname@example.org