## USENIX Example Paper

*[Pekka Nikander](http://www.pnr.iki.fi/cv.html)**[Aalto University](http://www.pnr.iki.fi/cv.html)*

### Abstract

This is an example for aUSENIXpaper,in the formof an HTML/CSS template. Being heavily self-ref-erential, this template illustrates the features in-cluded in this template. It is expected that theprospective authors usingHTML/CSSwould createa new document based on this template, removethe 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 abstractin one paragraph, and remember that the optimallength for an abstract is 200-300 words.

**1 Introduction**For the purposes of USENIX conference publica-tions,the authors,not theUSENIXstaff,are solelyresponsible for the content and formatting of theirpaper. The purpose of this template is to helpthose authors that want to useHTML/CSSto writetheir papers. This template has been prepared byHåkon Wium Lie, and is based on a guide to usingFrameMaker for USENIX papers, written by PekkaNikander with the help of Jane-Ellen Long.               The rest of this paper is organized as follows.Section 2 gives a brief overview of related work,such as other templates and style manuals.Section3 discussesthedetailsofthistemplate, and Sec-tion 4 contains our conclusions.

**2 Related Work**Preparing good-looking publications is not easy.It requires understanding of style and typography.The purpose of the templates provided by theUSENIXorganization is to lift the burden of caringabout typography from the authors. However, theauthors still remain, and will always remain, re-sponsible for the style.

**2.1 Word and LaTeX templates**The USENIX website includes a template for Mi-crosoft Word, as well as LaTeX templates. Many ofthe settings in theCSSstyle sheet of this templatehave been copied from the LaTeX templates.

*[Jane-Ellen Long](http://www.pnr.iki.fi/cv.html)**[USENIX Association](http://www.pnr.iki.fi/cv.html)*

**Figure 1:** This figure is showed for illustrational purpos-es only; floppy disks are not required to use this tem-plate.

**2.2 Style manuals**Besides typography, style is the second elementof preparing easy-to-read publications. There aretens of good style manuals available. To mentionjust a couple, The Elements of Style by Strunk andWhite[1]isaclassic,andhasremainedabestsellersince its introduction in 1930’s. From the morecontemporary ones, Writing for Computer Scienceby Justin Zobel[2]seems appropriate.

**3 Implementation**In this section we cover the features included inthistemplate. Ourgoalhasbeenthattheauthorsdo not need to make modifications to the template;instead, they should be able to concentrate on thecontent and style.With this in mind,this templateincludes a number of features. On the other hand,we have also tried to keep this document simpleand easy to maintain.               This template is written in HTML, with CSS toprovide styling, and a small JavaScript to help for-mat references.

---

Esc

F1 F2 F3 2 @

½ 1 3 £ 4 $

Q W E

Web E-Mail Tuner Menu Previous

F4 F5 F6 F7 F8 5 6 7 8 9

|  | = |  | ? |  |
|---|---|---|---|---|
| ] | 0 | } | + |  |

R T Y U I O P

A S D F G H J K L ÆCaps Lock

Z X C V B N M< \

Ctrl

Alt

Alt Gr

**Figure 2:** This figure floats to the top of the page, spanning both columns.

**3.1 HTML5**Thistemplateuses HTML5 elementstoaidinrep-resenting the document structure. The sectionelement is used to split the text into sections, andthe header element holds the headlines. Thefigure element is used to include figures andtheir corrensponding captions live inside the fig-caption element.The cite elementholdsallref-erences.               A small microformat, based on a convention ofclass names,is used to encode the name and affili-ation of the authors.

**3.2 CSS**A CSS style sheet describes how to format the purposes.HTML document into a PDF file. CSS is a declar-

In order forPrince to process the script includ-ative language which attaches property values to ed in this template, a command line option mustHTML elements and documents. Many aspects of be specified:CSSis used to achieve the presentation ofUSENIXpapers, including:

- multi-column layout
- footnotes
- page and column floats
- multi-level counters

Some commonly used features are absent fromthe above list: page numbers and running headersshould not be specifed by USENIX authors, theseare added by those who compile the Proceedings.

**3.3 JavaScript**This template uses JavaScript to process refer-ences. References are added at the point wherethey appear, and a script is later used to move the

Next Mute -Volume +Volume

WakeF9 F10 F11 F12 Power Sleep Up                    Num Lock Caps Lock Scroll Lock

Print

Num

Scroll PauseScrn

Lock

Lock BreakSysRq 7 8 9

Å

PageInsert Home Up                    Home PgUp

" ~

4 5 6

Page

Ø

Delete End Down 1 2 3

End

PgDn

Enter 0Ctrl

Ins

Del

references to the end of the paper, leaving behinda numeric marker.

**3.4 PDF**(This section has been added by Håkon Wium Lie)               In order to convert the document toPDF,a for-matter is needed. Common browsers supportHTMLandCSS,but they do not support all theCSSfunctionality for page-based formatting. For ex-ample, browsers do not support footnotes or pagefloats. This paper has been formatted with[a]Prince, a purpose-built program for convertingHTML and XML documents into PDF by way ofCSS. Prince is a commercial product, but can bedownloaded and used for free for non-commercial

```
$ prince --javascript example.html
```

**4 Tables**The table below lists recipients of theUSENIXLife-timeAchievementAward in the1900s.Notice hownotes inside the table are moved to the end of thetable.

Year 1999

1998

1997

[a] www.princexml.com

Recipient

[X Window System*](http://en.wikipedia.org/wiki/X_Window_System)

[Tim Berners-Lee](http://en.wikipedia.org/wiki/Tim_Berners-Lee)

[Brian W](http://en.wikipedia.org/wiki/Brian_W._Kernighan)[. Kernighan](http://en.wikipedia.org/wiki/Brian_W._Kernighan)

---

1996 [The Software T](http://en.wikipedia.org/w/index.php?title=The_Software_Tools_Project&action=edit&redlink=1)[ools Project](http://en.wikipedia.org/w/index.php?title=The_Software_Tools_Project&action=edit&redlink=1)

1995 [The Creation ofUSENET**](http://en.wikipedia.org/wiki/USENET) 1994 Networking Technologies

1993 [Berkeley UNIX](http://en.wikipedia.org/wiki/Berkeley_UNIX)

* Given to the Community at Large[** Given toJim Ellis andT](http://en.wikipedia.org/wiki/Jim_Ellis_(computing%29)[om Truscott](http://en.wikipedia.org/wiki/Tom_Truscott)

**5 Conclusions**Each good paper concludes the most significantfindings in the end.

### Acknowledgments

Apolite author always includes acknowledgments.Thank everyone, especially those who funded the

work.

**Availability**Please include a section at the end of your paperproviding availability information. If the systemyou describe is available to others, and if more in-formation(reports,etc.)may be obtained,indicateterms and contact information.

### References

[1] STRUNK, W. JR., AND WHITE, E.B. The ElementsofStyle,4thEd,Allyn andBacon,August,1999,ISBN 020530902X[2] ZOBEL, J. Writing for Computer Science,Springer-Verlag, December 1997 ISBN9813083220