Deadline: January 12, 1996. If we do not have an electronic version of your accepted submission(s) by this date, your work will not be included in the electronic publications.
These instructions describe how to prepare your accepted submission(s) for inclusion in the CHI 96 Electronic Proceedings and/or Conference Companion.
The following topics are covered:
http://www.acm.org/sigchi/chi95/Electronic/chi95cd.html
For CHI 96, electronic copies of these publications will once again be available through the WWW (no CD-ROM). This makes it much easier to distribute the information at a lower cost, and allows readers to quickly search for topics they are interested in. We need your help converting your accepted submission(s) into text and graphics files that can be easily incorporated into this electronic version. We use HTML (HyperText Markup Language) here to format the ASCII (simple plain character) text and included graphics of your accepted submission(s) so they can be displayed on the WWW.
Please use the following DOS file naming conventions: use the first two or three initials of the contact author's name, followed by an underscore, a 3-character label for the file, and a three letter file extension identifying the format. For a submission with Robert L. Mack as contact author, you might have the following files for the same contribution:
rlm_fg1.gif (Figure 1 in GIF form)
rlm_fg9.mov (Dynamic figure 9 in QuickTime MOV form)
rlm_tb2.jpg (Figure 2 in JPEG format)
If the contact author has more than one accepted submission, replace the
underscore with a number to keep the groups of files distinct from each
other.
rlm1fg1.gif (Figure 1 in 1st accepted submission)
rlm2fg1.gif (Figure 1 in 2nd accepted submission)
< > (less than/greater than brackets) are used to start and end formatting commands. & (ampersand) and " (quotes) are also perceived as codes in HTML. If you have any of these in your document text, they need to be changed as follows so they will be printed as text instead of interpreted as HTML codes:
Replace: With:Commands starting with < / (a bracketed slash) are for ending a formatting command.< &lt;
> &gt;
& &amp;
" &quot;
The following tags are the most commonly used. See Appendix A for an example of a document formatted in HTML, and how it looks when viewed through Netscape Navigator (a commonly used WWW browser).
<H1> Your Paper title </H1> <H2> Level 2 heading (topmost) </H2> <H3> Level 3 heading (next level) </H3> <H4> Level 4 heading (next level) </H4> <P> Paragraph break (end of paragraph -or- extra blank line) Includes a blank line following the paragraph <BR> Forces a line break with no extra space between lines <B> Begin Bold font </B> End Bold font <I> Begin Italic font </I> End Italic font <CENTER> Centers the following data </CENTER> Stops the Centering <PRE> Begins pre-formatted text </PRE> Ends pre-formatted text <HR> horizontal rule (a line that can be used to separate sections)
< img src="rlm_fg1.gif" alt="Figure 1">rlm_fg1.gif, for example) and also provide a
textual label for when a non-graphical browser is used. Use this where you
have replaced an image with a filename and label, inserting your filename
between the 1st set of quotes, and your label name between the 2nd set of
quotes. This command should appear on a line by itself.
By default the figures/images will be placed on the left hand margin.
If there is a positional tag in operation, CENTER for
example, then the image would be centered by the browser.
<OL> Numbered list <LI> List item 1 <LI> List item 2 </OL> End of list <UL> Bulleted list <LI> List item 1 <LI> List item 2 </UL> End of list <DL> Definition list <DT> Term 1 to be defined <DD> Term 1's definition <DT> Term 2 to be defined <DD> Term 2's definition </DL> End of listSome commands can be nested, and there are many other possibilities when using HTML. If you would like to learn more, we recommend looking up
http://kuhttp.cc.ukans.edu/lynx_help/HTML_quick.html
or
http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html
If you are already familiar with HTML, you may use additional formatting tags to achieve the look you might want. There are some formats (such as interactive or offsite links) that we cannot support; if you use a format we cannot support, we will work around it or simply remove it. If you want an example please look at the CHI '95 pages at the URL listed at the start of this document.
At the beginning of your document insert the following:
<HTML><HEAD> <TITLE>The title of your accepted submission</TITLE> </HEAD>The head will contain the title of the document, which most browsers prominently place so that it is displayed on all the screens your document is displayed on. The title should be the same as the title you use for the Heading one, e.g.<BODY>
<H1>.
After the document head, the document body starts. At the very end of the
document body, you should insert:
</BODY>
rlm_txt.html.
If you have more than one accepted submission with the same contact author,
again use a number instead of an underscore, such as
rlm1txt.html and rlm2txt.htmlto keep the groups of
files distinct and make sure they go with the matching image files.
README file and email message to go with your
collection of files.
Then choose one of the following for sending your files:
2. Using FTP to transfer files (preferred method)
3. Using email to send files
4. Using diskettes to send files
Once you have all your files ready to send in, you can use FTP to get them to the machine we're using for these publications. Alternatively, if FTP is not available to you, you can send them by email. As a last resort, you can send diskettes.
README
file to accompany them. In this file, please include the name,
email address, phone number(s) of a person we can contact if we have any
trouble setting up your files (yourself preferably) and how you are sending
your files. Please also include a complete list of the files being sent or
transferred, and any special instructions for working with them.
Remember - these files should be named using the DOS naming conventions
discussed above. In our example, Robert L. Mack's
README file would be named
rlm_rdme.txt
Besides including this README file with the files you transfer,
please also send a copy of the README file in an email message to
to notify us when your files have been transferred, or are on their way through email or on diskettes.
ftp.uni-paderborn.de login: chi-author password: XceptedThe directory structure is broken into the different submission categories (Papers, Panels, Videos, etc.). Change directory into the appropriate category and you will find a list of subdirectories for all contact authors with accepted submissions in a category. Change directory into the one appropriate for your files. Verify that there are no other files in the directory, and then transfer the files you prepared above from your machine to this directory. When you have finished, send email with a copy of your
README file to:
If the contact author is the same for more than one accepted submission in a
category, there will be a separate subdirectory for each accepted submission
(such as mack_robert1 and mack_robert2),
and you will get to choose which directory gets which set of files
(just make sure to keep them separate!).
We will send a reply as soon as we have verified receipt of all files, and will follow-up if we need further information. Once your files have been transferred and we have checked them in, the directory will be made read-only.
BINHEX encoders can be used on Macintosh, PC and UNIX machines,
and UUENCODE is available on PC and UNIX.
You may also want or need to compress files. For compression, use
StuffIt on Macs,
PKZip or gunzip on PC, and gzip
or compress on UNIX. Once your files are in a format that can
be sent by email, go back into the README file you have
created and make sure all the information about how files are compressed or
encoded is included. Then upload all your files to the machine you send
email from.
Send the README file by email to:
chi96-ep-deliver@acm.org
and cc: chi96-ep-submitted@acm.org.
Then send all of your other files to
chi96-ep-deliver@acm.org as attachments to individual email
messages.
We will check your files into the directory described in the FTP directions
above. This directory will then be protected from further access.
We will use the list in your README file to verify we have
received all files, and then notify you by email. We will follow-up if
there were any problems receiving or using your files, or if we need further
information.
README file.
If individual files do not fit on one diskette, use compression software to
compress files onto one or more diskettes. PKZip or
StuffIt will write the compressed files on multiple diskettes
if needed. Include a print out of the README file in your
package, describing the contents and formats of the files (PC, Macintosh,
compressed, etc.). Label the order in which diskettes are written onto if
there is more than one.
Also, please send a copy of the README file to
If you cannot use email, please fax it to the conference office or call them and leave a message to notify us that your files are coming on diskette and that they are on their way, so that we can watch for them and follow up if we do not receive them.
Thank you for making your submission available in an electronic format. We appreciate the extra work it takes.
The CHI 96 Electronic Publication Team:
Ralf Bilger, CHI 96 Electronic Publications Webmaster
Steve Guest, CHI 96 Technology Support Chair
Keith Instone, CHI 96 Hypermedia Support Chair
Robert Mack, CHI 96 Electronic Publications Chair
Michael J. Tauber, CHI 96 General Co-Chair
Images or bitmaps: GIF, JPEG, PICT, DIB, BMP, or TIFF
Tables or charts: Captured as an image (GIF ), RTF or MIF (same as the main document), or Encapsulated PostScript (EPS).
We prefer GIF or JPEG files if possible. If you use FrameMaker (MIF format), make sure graphic objects are in anchored frames.
If you do not have a WYSIWYG word processor (or computer) save the text object as an encapsulated PostScript file (EPS) and send this to us. Please do this only as a last resort.
Many computer stores, print shops or copying shops will scan graphic material for you (check the yellow pages).
If you have a problem getting material in appropriate electronic form, please contact the CHI 96 Electronic Publication Team via e-mail at chi96-ep-help@acm.org.
The CHI 96 Electronic Publication Team cannot help very much in this specialist area. Your first point of assistance should be your local support team. They will be much more familiar with your hardware and your needs. Again due to the diverse and very specialized equipment used, it is very unlikely that the CHI 96 Electronic Publication Team will have any knowledge or expertise in your particular setup.
It must be remembered that the idea of this presentation service is to reach out to many more CHI aware people. Yet we must remember that this service is based on the accepted submissions. Therefore if you do wish to have some material included please send your request to chi96-ep-help@acm.org. Someone will get back to you on the possibilities and arrange for a possible review of the materials.
File)
If you are not familiar with HTML save the source file and compare the source with the view of it.