USENIX Example Paper Pekka Nikander Jane-Ellen Long Aalto University USENIX Association Abstract This is an example for a USENIX paper, in the form of an HTML/CSS template. Being heavily self-ref- erential, this template illustrates the features in- cluded in this template. It is expected that the prospective authors using HTML/CSS would create a new document based on this template, remove the content, and start writing their paper. Note that in this template, you may have a mul- ti-paragraph abstract. However, that it is not nec- essarily a good practice. Try to keep your abstract in one paragraph, and remember that the optimal length for an abstract is 200-300 words. 1 Introduction For the purposes of USENIX conference publica- tions, the authors, not the USENIX staff, are solely responsible for the content and formatting of their paper. The purpose of this template is to help those authors that want to use HTML/CSS to write Figure 1: This figure is showed for illustrational purpos- their papers. This template has been prepared by es only; floppy disks are not required to use this tem- Håkon Wium Lie, and is based on a guide to using plate. FrameMaker for USENIX papers, written by Pekka Nikander with the help of Jane-Ellen Long. 2.2 Style manuals The rest of this paper is organized as follows. Besides typography, style is the second element Section 2 gives a brief overview of related work, such as other templates and style manuals. Section of preparing easy-to-read publications. There are 3 discusses the details of this template, and Sec- tens of good style manuals available. To mention tion 4 contains our conclusions. just a couple, The Elements of Style by Strunk and White [1] is a classic, and has remained a bestseller since its introduction in 1930’s. From the more 2 Related Work contemporary ones, Writing for Computer Science Preparing good-looking publications is not easy. It requires understanding of style and typography. by Justin Zobel [2] seems appropriate. The purpose of the templates provided by the 3 Implementation USENIX organization is to lift the burden of caring about typography from the authors. However, the In this section we cover the features included in authors still remain, and will always remain, re- this template. Our goal has been that the authors sponsible for the style. do not need to make modifications to the template; instead, they should be able to concentrate on the content and style. With this in mind, this template 2.1 Word and LaTeX templates The USENIX website includes a template for Mi- includes a number of features. On the other hand, we have also tried to keep this document simple crosoft Word, as well as LaTeX templates. Many of and easy to maintain. the settings in the CSS style sheet of this template This template is written in HTML, with CSS to have been copied from the LaTeX templates. provide styling, and a small JavaScript to help for- mat references. Web E-MailTuner Menu PreviouNext Mute -Volum+Volume Esc F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 Power Sleep Upke Num Lock Caps LockScroll Lock § ! " # ¤ % & / ( ) = ? ` Print Scroll Pause Num / _ | SysRq Lock Break Lock * ½ 1 2 @ 3 £ 4 $ 5 6 7 { 8 [ 9 ] 0 } + ' 7 8 9 Q W E R T Y U I O P Å ^ Insert Home Upge € " ~ Home PgUp + Caps Lock A S D F G H J K L Æ Ø * Delete End Down 4 5 6 ' _ > Z X C V B N M ; : 1 2 3 < \ , . - End PgDn Enter 0 , Ctrl Alt Alt Gr Ctrl Ins Del Figure 2: This figure floats to the top of the page, spanning both columns. references to the end of the paper, leaving behind 3.1 HTML5 a numeric marker. This template uses HTML5 elements to aid in rep- resenting the document structure. The section 3.4 PDF element is used to split the text into sections, and (This section has been added by Håkon Wium Lie) the header element holds the headlines. The In order to convert the document to PDF, a for- figure element is used to include figures and matter is needed. Common browsers support their corrensponding captions live inside the fig- HTML and CSS, but they do not support all the CSS caption element. The cite element holds all ref- functionality for page-based formatting. For ex- erences. ample, browsers do not support footnotes or page A small microformat, based on a convention of floats. This paper has been formatted with class names, is used to encode the name and affili- [a] Prince, a purpose-built program for converting ation of the authors. HTML and XML documents into PDF by way of CSS. Prince is a commercial product, but can be 3.2 CSS downloaded and used for free for non-commercial A CSS style sheet describes how to format the purposes. HTML document into a PDF file. CSS is a declar- In order for Prince to process the script includ- ative language which attaches property values to ed in this template, a command line option must HTML elements and documents. Many aspects of be specified: CSS is used to achieve the presentation of USENIX $ prince --javascript example.html papers, including: • multi-column layout 4 Tables • footnotes The table below lists recipients of the USENIX Life- • page and column floats time Achievement Award in the 1900s. Notice how • multi-level counters notes inside the table are moved to the end of the Some commonly used features are absent from table. the above list: page numbers and running headers should not be specifed by USENIX authors, these Year Recipient are added by those who compile the Proceedings. 1999 X Window System* 3.3 JavaScript 1998 Tim Berners-Lee This template uses JavaScript to process refer- 1997 Brian W. Kernighan ences. References are added at the point where they appear, and a script is later used to move the [a] www.princexml.com 1996 The Software Tools Project work. 1995 The Creation of USENET ** Availability 1994 Networking Technologies Please include a section at the end of your paper 1993 Berkeley UNIX providing availability information. If the system * Given to the Community at Large you describe is available to others, and if more in- ** Given to Jim Ellis and Tom Truscott formation (reports, etc.) may be obtained, indicate terms and contact information. 5 Conclusions References Each good paper concludes the most significant [1] STRUNK, W. JR.,AND WHITE, E.B. The Elements findings in the end. of Style, 4th Ed, Allyn and Bacon, August, 1999, ISBN 020530902X Acknowledgments [2] Z OBEL, J. Writing for Computer Science, A polite author always includes acknowledgments. Springer-Verlag, December 1997, ISBN Thank everyone, especially those who funded the 9813083220