Andreas Kathol (kathol@socrates.berkeley.edu)
Mon, 16 Jun 1997 11:29:04 -0700 (PDT)
Dear colleagues, (This message is sent to both the HPSG list and the list of speakers at the Ithaca HPSG conference. Our apologies if you receive this twice. The original announcement is appended below for those that did not receive the previous message.) Here is an update on the HPSG97-related publication effort: 1. A number of speakers at the Ithaca HPSG conference have let us know that the 8 August deadline would be difficult for them to meet. We therefore decided to move the deadline back by one month to: September 12 Please note that this is still a firm deadline (i.e., submissions that reach us after that date will not be considered for the 97 volume). The categories of solicited contributions and the associated page limits are still the same, in particular: 1. regular presentations at the Ithaca conference: 15 pages, 2. invited presentations at the Ithaca conference: 20 pages, 3. presentations in the Special Symposium on Constructions: 15 pages, 4. papers from the three previous HPSG conferences: 15 pages. 2. CSLI provided us with erroneous information regarding the site of the relevant LaTeX stylefiles. Please note the following correction: From: Tony Gee <gee@Csli.Stanford.EDU> To: Andreas Kathol <kathol@socrates.berkeley.edu> Subject: Re: CSLI Publication update (fwd) Andreas, I made a mistake. The directory that I pointed you to is incorrect. The "article" directory is for our technical reports series. Please redirect people to the report directory, i.e., ftp://ftp-csli.stanford.edu/pub/publications/latex-package/report/ Sorry about this confusion. Also, please inform all latex users that these are not compatible with latex2e. Thanks, Tony Hopefully these files will not have the problems that some of you reported to us earlier. Let us know if there are still problems. 3. Also, note that it is not necessary to exclusively use the macros defined in the CSLI stylefiles. For instance, if you are accustomed to using your own macros for typesetting AVMs, trees, etc., you're welcome to continue to do so (as long as you provide all required stylefiles). However, the CSLI specifications should be respected re. format issues such as margins. 4. We still strongly encourage the use of LaTeX, based on CSLI's recommendation. However, CSLI has since expressed an increased willingness to deal with other formats such as MS Word. As said earlier, please let us know as soon as possible if you plan to use a non-LaTeX format so any necessary arrangements can be made soon. Thanks very much for your cooperation, The editors (Gert Webelhuth, Andreas Kathol, Jean-Pierre Koenig) ================================================================== Subject: CSLI Publication update To: hpsg@ling.ohio-state.edu (hpsg) Date: Thu, 5 Jun 1997 10:11:05 -0700 (PDT) Dear colleagues, A while ago, the new CSLI series "Studies in Constraint-Based Lexicalism" was announced on the HPSG list. One of the purposes of that series is to provide a forum for the publication of high-quality work in HPSG in general, and work based on presentations at the yearly HPSG conference in particular. The first volume will be edited by Gert Webelhuth, Andreas Kathol, and Jean-Pierre Koenig. This message is to inform eligible submittors about some more details of this year's volume. The deadline for submitting papers is: August 8, 1997 (one week after the end of the Ithaca LSA Institute) There are 4 categories of papers that are solicited, together with the page limit: 1. regular presentations at the Ithaca conference: 15 pages, 2. invited presentations at the Ithaca conference: 20 pages, 3. presentations in the Special Symposium on Constructions: 15 pages, 4. papers from the three previous HPSG conferences: 15 pages. The August 8 deadline applies to all categories and is ABSOLUTELY FIRM (we mean it!). Each submitted paper will undergo a review process. Revised versions of accepted articles should be submitted in late October (details to follow in due course). Because the end result is NOT an ordinary conference proceedings volume, but a book representing some of the best in HPSG-related work of the current year, it is imperative that all authors cooperate as much as possible in achieving a homogeneous format for the entire book. Based on CSLI's preference, we therefore STRONGLY suggest that papers be submitted in LaTeX format. Authors for whom this is problematic are encouraged to contact the editors early. Below are the general guidelines for LaTeX submissions. The stylefiles pubsart10.sty, pubsarticle.sty, pubsbib.sty, pubsmacs.sty, and pubsbib.bst can be found at the following site: ftp://ftp-csli.stanford.edu/pub/publications/latex-package/article/ Please let us know if you have any questions. Best regards, The editors (Gert Webelhuth, Andreas Kathol, Jean-Pierre Koenig) =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= GUIDELINES FOR PREPARING LATEX MANUSCRIPTS FOR CSLI PUBLICATIONS This information is for authors preparing documents for submission to CSLI Publications. It accompanies a package of latex .sty files and a sample document. These guidelines are addressed to a wide range of authors, including those who know very little about LaTeX. The following remarks address some finer aspects of typographical style. Please refer to _The Chicago Manual of Style_ if you have further questions. * Whatever you do, be consistent. * Paragraphs should be separated by a blank line (NOT just by indenting the first line a few spaces). * If your document is partitioned into sections (rather than being a single unbroken block of prose paragraphs), then indicate partition headings by placing them inside curly braces, preceded by a description of the partitioning level, as follows (including the backslash): \subsection{<heading>} Each of these partition headings should be on a line by itself, preceded and followed by exactly one blank line. Capitalize all words in chapter and section headings (except unstressed articles), not just the first word. If your document is a technical report or a paper to be included in a collection, the top-level partition will be a "section", divided into "subsections" and then perhaps "subsubsections". If your document is a book, the top-level partition will typically be a "chapter", divided into "sections", "subsections", etc., though chapters may also be collected into "parts". In either case, we recommend partitioning no deeper than the level of subsections. * Avoid using abbreviations like `e.g.' or `i.e.'. But if you do, then please punctuate them properly. `E.g.', `i.e.', and `viz.' have periods as indicated and are always followed by a comma. `Etc.' is too, unless it is at the end of a sentence. * Use quote marks properly: double quote marks indicate that you are either (a) emphasizing but USING the marked passage, (b) QUOTING someone else's use, (c) listing the title of an article, etc. Single quote marks indicate that you are MENTIONING a passage. For example, the phrase `the cat on the mat' has five words in it, whereas ``the cat on the mat'' may in fact be a male beatnik reclining on a small rug near the door. Use two single quotes for double quotes, as illustrated (left and right) in the previous paragraph. Never use the single `"' symbol as a quote marker in a LaTeX or TeX document. Punctuation marks always go outside of quote marks, except in two cases: namely, when double quote marks are accompanied by a comma or period. For example, there are many three letter words, such as `cat', `dog', or `pot'. And you may or may not think the following period looks ``clumsy.'' * Passages to be {\it italicized\/} or {\bf boldfaced} should be put inside curly braces, where the opening brace is followed by `\it' or `\bf', as just illustrated. * There are four kinds of "dashes": hyphens (-), en-dashes (--), em-dashes (---), and minus-signs (- in math text). Hyphens are used to make compound words; en-dashes are used in number ranges, e.g., for page ranges or date intervals; and em-dashes are used as sentence breaks---like this, with no spaces between the dash and the adjoining words. * Anything to be formatted as a math symbol or math equation should be placed inside dollar signs, e.g., $1-1=0$ or, If $P$ implies $Q$, and $P$, then $Q$. * Footnotes should be put inside curly braces and preceded by the command `\footnote', as illustrated here.\footnote{This will generate an automatically numbered footnote at the bottom of the page on which it occurs.} The "\footnote" string should not be preceded by a space nor by a carriage-return. There should be no space between the opening "{" and the begiining of the footnote. * If there is to be an index, you will need to indicate index entries in the files you send us. There are sometimes two indexes---a subject index, and an author or name index---in which case we need two ways to flag things. We often use a system illustrated in the following sample paragraph: "In 1990 Barwise\INA{Barwise, J.} and Etchemendy\INA{Etchemendy, J.} published a book on first-order logic\INS{logic!first-order}, which was packaged with a program called Tarski's World\INS{Tarski's World}. It allowed student's to create worlds\INS{world} and sentence files\INS{sentence file}\INS{file!sentence}. One of these files was later declared obscene and the book was confiscated by Jesse Helms's\INA{Helms, J.} Committee on Inappropriate Activities." Notice that each index command (either "\INS{...}" or "\INA{...}") goes right up against the word or phrase to be indexed. Don't leave an intervening space, though leave a space or carriage-return afterwards. Don't start a new line with an index command. The preceding carriage- return is in effect an intervening space between the index command and the preceding text. It is crucial that you specify the arguments of these index commands exasctly as they are to appear (alphabetically) in the index, e.g., specify an author's last name first. An "!" inside the argument of an index command is used to specify subitems of index items. "\INS{foo!bar}" will put an item "foo" in the index, alphabetized under the "f"s, and it will have a subitem "bar" followed by a page-number. You can have at most two such "!"s per index command (to get items, subitems, and subsubitems, but no subsubsubitems). For further information about indexing, take a look at Leslie Lamport's "MakeIndex: An Index Processor for LaTeX". (To get this document at CSLI and elsewhere, simply "latex makeindex" (twice) from wherever you are on your computer system, and chances are that a makeindex.dvi file will miraculously appear which you can then send to the printer. Remove the resulting .dvi, .aux, and .log files when you are done.) * If possible, use LaTeX's BibTeX program for your bibliography. Be sure to send us the .bib data file for your job. (See Leslie Lamport's LaTeX manual (pages 72--75, 140--147, 187--188) for an explanation of how this program works.) See also the sample .bib file in this directory. We normally use the Chicago-Manual-of-Style format: AUTHOR. DATE. TITLE. PUBLICATION INFORMATION. Book titles are italicized. Article titles are in roman, with no quote marks but with all main words capitalized. Our "pubsbib" bibliography style (included as pubsbib.bst and pubsbib.sty in this directory) takes care of this automatically, as long as all bibliography information in the .bib file is correct and complete. We use a corresponding author/date format for citing bibliographical references in the text. So _Situations and Attitudes_ would be cited as Barwise and Perry 1983. Our "pubsbib" bib style also takes care of this nicely: "\cite{<cite-key>}" yields a full author/date citation, while "\shcite{<cite-key>}" yields only the date. Notice: there are no parentheses nor square brackets. You may insert parentheses in the text when they are appropriate. Parentheses are used only if part or all of the citation is in fact parenthetical---they are not used as citation markers. E.g., Barwise and Perry (\shcite{bp:sanda}) claim that situations are parts of the world. It has also been claimed (\cite{bp:sanda}) that semantics is a slippery business. will yield Barwise and Perry (1983) claim that situations are parts of the world. It has also been claimed (Barwise and Perry 1983) that semantics is a slippery business. You can choose cite-keys however you like. Generally they will be strings you can easily recall. On the other hand, we have developed a system for cite-keys which is important when it comes to consolidating .bib data files from multiple authors---we all have to use the same system if duplicate references are to be discovered and handled uniformly. The key has the form "auth:titl00" where "auth" is the string of first four letters of the (first) author's last name; "titl" is the string of first four letters of the first significant word of the title; and "00" is the pair of last two digits of the year of publication. E.g., the cite-key for _Situations and Attitudes_ is "barw:situ83". The key for _The Situation in Logic_ is "barw:situ89". (If this scheme is not able to distinguish two references published with similar authors and titles in the same year, add a string of four more letters after the date, from the next differing significant word in the title: "barw:situ89prop". But this is actually rare. The main thing is that we all do it the same way. Please let us know if you come up with a better system.) * If there are abbreviations in your text consisting entirely of capital letters, such as `CSLI' or `NP', we often reduce these in size by one point. You might want to define and use some simple macros, such as: \def\NP{\hbox{\small\rm NP}} \def\CSLI{\hbox{\small\rm CSLI}} Or define a multi-purpose macro like \def\smallcap#1{\hbox{\small\rm #1}} You are then able to talk about {\NP}'s in a paper to be published by {\CSLI} Publications. When you finally e-mail your document files to CSLI, don't forget to include any such macros you have developed to handle things peculiar to your work. Please try to keep such things as simple as possible. You might put these personal macros in a separate .sty file (e.g., the file mymacs.sty in this directory), to be included as one of the options in the documentstyle command. * Run your document through an automatic spell-checker if one is available on your system. * Make sure there are no LaTeX bugs. Run your job on your system and take care of any error messages before sending the files to us. Make sure BibTeX works with the data file you plan to send us. Run makeindex on your job to see if it gives you what you want in the index. Modify any index commands in the text files that don't alphabetize properly. Fine-tune the text so that it looks exactly like it ought to look.
This archive was generated by hypermail 2.0b3 on Fri Dec 18 1998 - 20:36:07 PST