Please, read the section Who can submit first.
Email new entries or updated versions of old entries to
They will be integrated into the next version. What forms are acceptable for entries is discussed below.
We will be updating this bibliography on a regular schedule. We will email a reminder to the COLT mailing list a short while before the deadline, though updates can be sent anytime.
``this supersedes ag-ersu-90''
better to have a comment like
``Earlier version appeared in 1st COLT, 1988'' The reason for this is that having `ag-ersu-90' appear in a journal in a bibliography is meaningless, while having `COLT 1988' is meaningful.
Because of the distributed nature of updates, it seems desirable to have some written guidelines for the format of entries, in order that the final product has a consistent style. The following suggestions are based on common practice where discernible, established authorities where possible, and personal opinion where unavoidable.
You will likely find existing entries in disagreement with these guidelines. Either the entry or the guidelines should be fixed. If some entry can't be decently handled by the current guidelines, or you think they're just plain wrong in any case, please let us know about it.
In the hope of keeping future input work reasonably simple and error-free, a few lexical conventions were set at the time of bibtex conversion, as follows. Where possible you should use lower case (for simplicity), a leading comma ``, volume = 12'' (to make missing commas obvious), and put all text for a field on a single line (to avoid spending time on prettyprinting). If you must break lines, such as in the abstract= or annote= or comments= or note= fields, start subsequent lines with a tab.
Special characters and diacriticals should be entered as specified on p.52 of the TeXbook. The common single-letter ones are described here.
Note that diacriticals precede the letter affected. A complication is that in TeX, control sequences specified using letters must somehow be separated from the ordinary letters that follow. A simple way is to use spaces as in "Erd\H os", but this will look like two separate words to bibtex. Another is to use braces as in "Erd\H{o}s", but this too is confounded by bibtex, which
Initially it might seem enough to put braces around the whole word when it contains either a fussy diacritical or (in a title field) a capital letter. However, it turns out that, because of how it handles the author field, bibtex dictates the convention to follow. Since adding a feature to recognize and handle accented characters in author fields (for benefit of the alpha bibliography styles), bibtex requires that we
``place the entire accented character in braces;
in this case either
{\"o} or {\"{o}}
will do .... furthermore these braces must not themselves be enclosed in
braces (other than the ones that might delimit the entire field or the
entire entry), and there must be a backslash as the very first character
inside the braces. ''
Thus you should use, for example,
Mathematical expressions, including numbers in titles, should always be entered in TeX notation.
Author, title, and page information from other than the title page of the paper itself is untrustworthy: you might want to do data entry from a proceedings table of contents for speed, but please take time to proofread against title pages for accuracy.
The next page contains a quick naming of parts for entries in the database, with discussions of the conventions that have evolved. More detailed information on entry formats can be found in the bibtex documentation.
back to the
COLTBIB
Thomas Zeugmann Division of Computer Science Hokkaido University N-14, W-9 Sapporo 060-0814, JAPAN < thomas @ ist . hokudai . ac .jp>
