Author's guide - Instructions for Final preparation
Constraint Programming Letters
[Based heavily on the JAIR/JMLR Author's Guide, gratefully reproduced by permission of JMLR]
Checklist (see detailed instructions below)
1. [ ] Format article using CPL style.
2. [ ] Have your article proofread.
3. [ ] Contact editor (firstname.lastname@example.org), obtain final approval and formatting check.
4. [ ] Fill out permission to publish form, and send it.
5. [ ] Fill out source code release, and send it (only necessary if you are releasing source code in an online appendix).
6. [ ] Fill in page numbers and publication date, make final changes.
7. [ ] Create HTML version (strongly recommended, but not required).
8. [ ] Send all the required files.
9. [ ] Inform the editor of any special mailing lists or newsgroups you'd like an announcement sent to.
10. [ ] After your article is published, create forward pointers (optional).
Once a paper has been accepted for publication in CPL, you should follow the procedure outlined below. The final version of your manuscript is due to us within three months of the acceptance date. If you require more than three months, please request an extension from the editor.
1. Format your article according the CPL style, which is described in Instructions for Formatting CPL Articles. The instructions also describe the use of the CPL LaTeX style file, which should simplify adhering to the requirements. There is also an annotated CPL sample paper available as LaTeX source, PostScript and PDF, which we strongly recommend using as a template for your submission.
Authors are responsible for correctly formatting their article.
Here are things to check, before you send us your article:
- Capitalize section and subsection titles.
- Make sure your abstract reads well. It will be used to advertise your paper.
- We recommend you use small caps for system names. (In LaTex that's \sc)
- Capitalize references to figures and tables, e.g. "In Figure 7..."
- Ensure that your paper has both sets of running heads: authors and
- It is preferable to cite published papers, rather than tech reports.
- Carefully read the section on citations in Instructions for Formatting CPL Articles. Here are examples of BAD citations:
- "See (Ginsberg, 1994) for an analysis..." [Uses citation as a noun]
- "Drummond (Drummond, 1994) showed that..." [Should be "Drummond (1994)"]
- "...the best method (see the ERT test (Davis, 1995))..." [double parens, should be "...best method (see the ERT test, Davis, 1995)..."]
- In the authors' addresses, don't use commas at the end of the lines.
- Do not start a section with a subsection. (E.g., Each section should start with some text, rather than immediately starting with a subsection) Similarly, don't start a subsection with a subsubsection.
- Your paper should be formatted for 8.5 x 11 letter size paper, not A4 (common in Europe). If you are in Europe and use Latex, use "dvips -t" when you create your PostScript file to get the right size.
2. Make any final changes and have your article proofread. For better or worse, we do not have a copyediting staff. (Note: Authors are notoriously bad proofreaders. Have the paper proofread by a skilled proofreader - NOT one of the authors.)
3. Send the paper to the editor in charge of your article. Also send a copy email@example.com. You should leave the publication date and page numbers blank for the moment, pending final approval from the editor (step 7, below).
4. Please print out, fill in, and sign the Permission to Publish form form . Send the form:
Constraint Programming Letters
Jean-Charles Régin, Editor
I3S, 2000, route des Lucioles
Les Algorithmes - bât. Euclide B
06903 Sophia Antipolis Cedex
The form agreement provides non-exclusive rights for electronic publication to CPL; the copyright remains with the authors.
5. We encourage you to make use of "online appendices" where appropriate. Online appendices can contain source code, data, even quicktime demonstrations -- anything that that will make life easier (or more interesting) for your readers and researchers who follow in your footsteps.If there are online appendices containing source code, please sign the software release form (available in PostScript and PDF formats) and send it along with the Copyright form. The release form is intended to reduce the liability of CPL.
6. Once you have the final approval on the paper and the formatting, you should add in the page numbers and publication date sent to you by the editor. Put the final touches on any additional versions of the paper that you want us to publish alongside the PostScript or PDF version. As noted above, we encourage authors to produce an HTML version of their paper.
7. Send the editor all the files. (A single tar file is convenient.) We would appreciate it if you use the following naming scheme for your files. Assuming the first author's last name is "Jones" and the current year is 2000, you should send us:
- jones00a.ps, the final PostScript file
- jones00a.tex (or jones00a.txt), a single LaTex source file (or, if you didn't use LaTex, some sort of ascii version of the paper if possible) which we can use for our search engine
- jones00a.tar, a tar file containing all the source files (latex files, figures, word file, whatever) which we will archive.
- abstract.txt, an ascii version of the abstract. Please also include the title at the top.
- jones00a.bw.ps, a version of your paper with grayscale (not color) figures. If your paper contains color figures, we need a black-and-white version for the hardcopy edition to be printed by MIT Press.
- jones00a.pdf, a pdf version of your paper. We will create one ourselves if you don't send it to us.
- jones00a-appendix1.txt (or .ps, .lisp, or .whatever), an online appendix. If there are two or more, name them jones00a-appendix2.txt and so on.
As an alternative to emailing the files, you can send FTP instructions to the editor.
9. After we receive the final version and release the article, we will post an announcement on the CPL mailing list. The paper will also be stored at the CPL distribution site and forwarded to ACM's computing repository (CORR) and the CiteSeer Index.
If you know of any other mailing lists where it would be appropriate to post an announcement for your paper, please feel free to forward our announcement. If you would prefer that we do, please let the managing editor know the addresses where he should forward the announcement.