Coder Social home page Coder Social logo

sigchi / document-formats Goto Github PK

View Code? Open in Web Editor NEW
306.0 306.0 482.0 115.48 MB

Everything you need to know to publish using LaTeX or Word and then some.

Home Page: https://www.acm.org/publications/taps/word-template-workflow

License: GNU General Public License v2.0

document-formats's People

Contributors

ayman avatar floe avatar jofish avatar koppor avatar luileito avatar mporcheron avatar simonrob avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

document-formats's Issues

Latex - Proceedings and ExtAbs - Add Quotes section

Add section before Language, Style and Content called Quotes thus:

Quotes
Quotes should be italicized. Short quotes “may be placed inline” (Anab, 22F).
Longer quotes may be placed in their own paragraph and need not be in quotation marks. (Ramon, 39M).

Latex - Proceedings - Consolidate references advice

Move "References and Citations" section to end and combine with "References Format".

New wording should be this:

Your references should be published materials accessible to the public. Internal technical reports may be cited only if they are easily accessible and may be obtained by any reader for a nominal fee. Proprietary information may not be cited. Private communications should be acknowledged in the main text, not referenced (e.g., [Golovchinsky, personal communication]). References must be the same font size as other body text. References should be in alphabetical order by last name of first author. Use a numbered list of references at the end of the article, ordered alphabetically by last name of first author, and referenced by numbers in brackets. For papers from conference proceedings, include the title of the paper and the name of the conference. Do not include the location of the conference or the exact date; do include the page numbers if available. References should be in ACM citation format: http://acm.org/publications/submissions/latex_style. This includes citations to internet resources [1,4,8] according to ACM format, although it is often appropriate to include URLs directly in the text, as above. Example reference formatting for individual journal articles [3], articles in conference proceedings [7], books [9], theses [10], book chapters [11], an entire journal issue [6], websites [1,4], tweets [1], patents [5], and online videos [8] is given here. This formatting is a slightly edited version of the format automatically generated by the ACM Digital Library (http://dl.acm.org) as “ACM Ref”. DOI or URL links are optional but encouraged. Note that the Hyperlink style used throughout this document uses blue links; however, URLs in the references section may appear in black.

Orphan headings

There's a tendency for section headers to get typeset at the bottom of columns or pages in the proceedings format. In the sample, Figures/Captions and Conclusion are examples.

Referencing a section is impossible

I've tried to reference a section which was previously labeled, but no matter what I try (\ref, \autoref, \pageref, etc.) no reference is produced. I'm using ShareLaTeX, which is a web-based LaTeX editor. I've not tried to compile locally.

The entire LaTeX log is available here.

Here's a minimal example (which is based on the included proceedings.tex):

\documentclass{sigchi}

% Load basic packages
\usepackage{balance}  % to better equalize the last page
\usepackage{graphics} % for EPS, load graphicx instead 
\usepackage{txfonts}
\usepackage{times}    % comment if you want LaTeX's default font
\usepackage[pdftex]{hyperref}
\usepackage{color}
\usepackage{textcomp}
\usepackage{booktabs}
\usepackage{ccicons}
\usepackage{todonotes}

% llt: Define a global style for URLs, rather that the default one
\makeatletter
\def\url@leostyle{%
  \@ifundefined{selectfont}{\def\UrlFont{\sf}}{\def\UrlFont{\small\bf\ttfamily}}}
\makeatother
\urlstyle{leo}

% To make various LaTeX processors do the right thing with page size.
\def\pprw{8.5in}
\def\pprh{11in}
\special{papersize=\pprw,\pprh}
\setlength{\paperwidth}{\pprw}
\setlength{\paperheight}{\pprh}
\setlength{\pdfpagewidth}{\pprw}
\setlength{\pdfpageheight}{\pprh}

% Make sure hyperref comes last of your loaded packages, to give it a
% fighting chance of not being over-written, since its job is to
% redefine many LaTeX commands.
\definecolor{linkColor}{RGB}{6,125,233}
\hypersetup{%
  pdftitle={SIGCHI Conference Proceedings Format},
  pdfauthor={LaTeX},
  pdfkeywords={SIGCHI, proceedings, archival format},
  bookmarksnumbered,
  pdfstartview={FitH},
  colorlinks,
  citecolor=black,
  filecolor=black,
  linkcolor=black,
  urlcolor=linkColor,
  breaklinks=true,
}

\begin{document}
\section{Section}
\label{sec:section}
This is a section.
\section{Referencing}
Here's a reference to the previous section: \ref{sec:section}.
\end{document}

Latex - Proceedings, ExtAbs : Update table 1 to match Word

Update Table 1 to match word document as per image. I've seen reports that the current table can be confusing, because it looks like it conveys useful information when it's actually just sample text. This new table shows a variety of number formats, includes highlighting and less redundant lines. (And is a shout out to some of our colleagues who have left us.)
image

Clarify that author blocks and copyright area should be *empty* in anonymous review

There is a concern that authors occasionally (not maliciously) have specific, stylized ways of filling the author blocks and copyright areas during anonymous review that in practice reveal author identity. Copyright block and author area should gently indicate "leave blank, with no dummy content".

This brings up the larger question of whether the template is specifically meant to reflect a blind submission process. That's above my pay grade.

Enable use of CCS 2012 auto-generated latex

http://dl.acm.org/ccs_flat.cfm

http://dl.acm.org/ccs_flat.cfm#10003120

\begin{CCSXML}
<ccs2012>
<concept>
<concept_id>10003120.10003121.10003124.10010868</concept_id>
<concept_desc>Human-centered computing~Web-based interaction</concept_desc>
<concept_significance>500</concept_significance>
</concept>
<concept>
<concept_id>10003120.10003121.10003124.10010862</concept_id>
<concept_desc>Human-centered computing~Command line interfaces</concept_desc>
<concept_significance>100</concept_significance>
</concept>
<concept>
<concept_id>10010147.10010371.10010387.10010866</concept_id>
<concept_desc>Computing methodologies~Virtual reality</concept_desc>
<concept_significance>300</concept_significance>
</concept>
</ccs2012>
\end{CCSXML}

\ccsdesc[500]{Human-centered computing~Web-based interaction}
\ccsdesc[100]{Human-centered computing~Command line interfaces}
\ccsdesc[300]{Computing methodologies~Virtual reality}

EA template: Text is not justified

The template is using \RaggedRight{} together with hyphenation, which looks weird:
raggedright hyphen

On the other hand, the ragged2e package provides the \justify command, but it breaks the template.

Just to let you know.

Front page links to Proceedings and Ext Abs format are broked.

CHI uses two different formats for most submissions: CHI Proceedings Format and Extended Abstract Format. Please note that changing the leading, changing the tracking, adding small fonts for references, and other sizing tricks are strictly prohibited.

problem with crossref

Bibliography items that have a crossref to other references do not render correctly: the leading square bracket is missing from the typeset cross-reference (or a trailing close bracket is added). Unclear if this is a bug or just unsupported; it is easy to work around. A crossref'ed set of entries follows, as well as a screenshot of the output.

@incollection{Jorgensen:2013ab, Crossref = {Jorgensen:2013aa}, Pages = {54--104}, Title = {The Gameworld as Interface}}

@book{Jorgensen:2013aa, Address = {Cambridge, MA, USA}, Author = {Kristine J{\o}rgensen}, Booktitle = {Gameworld Interfaces}, Publisher = {MIT Press}, Title = {Gameworld Interfaces}, Year = {2013}}

screen shot 2015-09-16 at 12 17 45 pm 2

Incorrect page references in sections for LaTeX template

Just realized that in the auto-generated TOC, all top-level sections will link back to page 1, no matter where the section actually is in the document. [Sub]subsections work correctly, however - see below for a (slightly obfuscated) example. This is with most recent master branch.
screenshot from 2015-09-14 20 37 41

Default bibliography style is very verbose

The default .bst style is now extremely verbose IMHO. Also, it kind of contradicts the instructions, which specify that conference proceedings should be abbreviated as "Proc. XXX 2016", while the style currently always uses the full booktitle field. May I suggest to change the default to using "Proc." + series instead?

Builds are fragmented in folders

Right now builds are zipped in various directories. Instead, copy the needed files to a tmp location, compress it from there, move it to the builds dir then delete the intermediates.

Make URL colors black in refs.

Can redefine the URL style BEFORE refs like so:

\makeatletter
\def\url@leostyle{% 
\@ifundefined{selectfont}{\def\UrlFont{\sf}}{\def\UrlFont{\color{black}\small\bf\ttfamily}}}
\makeatother
\urlstyle{leo}
\balance{}

\bibliographystyle{SIGCHI-Reference-Format}
\bibliography{sample}

The class file should do this.

need for game citation format

Those working in the game space often need to cite games in our papers; authors have taken an ad hoc approach to this so far. I would like to move this forward into the official templates so that we have a clear format for games.

The Game Studies journal has formal specifications for citing games (http://gamestudies.org/1501/submission_guidelines#GSCitation), which are based on APA format. I propose using the Game Studies journal format as a basis, but adapt it to match the format that we are using in SIGCHI. This puts it somewhere between book format and the various misc formats (online video, tweets, etc.). The style needs to have the game title be italicized, must include the publisher information, and should have the "Game [<platform>]" tag (similar to the Tweet and Online Video samples).

Here is a proposed format, which references a particular instance of a game (release date, platform):

<Developer>. <Year Released>. <Game Title (italicized, like a book)>. Game [<platform played / analyzed for manuscript>]. <Publisher>, <Release Location>. Played <most recent play date>.

Here are examples:

Atari, Inc. 1979. Adventure. Game [Atari 2600]. Atari, Inc., Sunnyvale, CA, USA. Played August 25, 2007.

343 Industries. 2012. Halo 4. Game [Xbox 360]. Microsoft Studios, Redmond, WA, USA. Played December 31, 2012.

Namco. 2004. Katamari Damacy. Game [PS2]. Namco, Tokyo, Japan. Played January 20, 2005.

Lucas Pope. 2013. Papers, Please. Game [OS X]. Self-published.

I surfaced this on the CHI Games Facebook group, to little interest. Unclear if there is another body that might have a helpful opinion.

year appears in the reference twice

The CHI LaTeX reference format seems to put the year in the reference twice. In the example LaTeX pdf, we see:

Anna Cavender, Shari Trewin, and Vicki Hanson. 2014. Accessible Writing Guide. (2014). http://www.sigaccess.org/welcome- to- sigaccess/ resources/accessible- writing- guide/.

Jofish Kaye and Paul Dourish. 2014. Special issue on science fiction and ubiquitous computing. Personal and Ubiquitous Computing 18, 4 (2014), 765–766. DOI: http://dx.doi.org/10.1007/s00779- 014- 0773- 4

Seems a bit redundant. Is this intentional, or something that should be fixed?

"Add Tags to Document" in Acrobat (v10.1.15) makes document unreadable on iOS 9

"Add Tags to Document" in Acrobat (v10.1.15) makes the resulting PDF document unreadable on iOS 9 (see screenshot of output at bottom)

Steps to reproduce the error:

  1. Compile a clean PDF from the proceedings.tex example.
  2. "Add Tags to Document" in Acrobat.
  3. View on iOS 9 device.
  4. Profit!

I don't have an iOS device myself to debug this. The accessible PDF looks fine in iSimulator with iOS 8.2 on my Mac. I know Add Tags introduces an unembedded Times-Roman font. I was able to re-embed the font with Acrobat. Now shows as "TimesNewRoman (Embedded Subset), Type: TrueType (CID)". However, the problem on iOS 9 unfortunately persists.

I don't know if the problems also exists with a .doc file as the source. No iOS device to really debug, as I said.

sigchi-ios9-

Template LaTex and Word are not the same

I noticed that the LaTex template for extended abstracts are not the same as the word template. Please find attached the first pages of both pdf outputs, (created on a mac). Notice the difference in font type and the line above the copyright block. When making proceedings for a conference I am confronted with this, because I do not want to ask people to redo their LaTex paper in a Word template, but now I am not able to make consistent proceedings.
ae 2016 left_latex right_word

What do the file versions mean in the LaTeX class?

Investigate if these need revision and why/when they do.

\def\fileversion{V0.19}                  % [sm] for ACM's tracking purposes 
\def\filedate{July, 30, 2014}            % [sm] tracking data
\def\docdate {Wednesday, July 30th 2014} % [sm] 

UPDATED date in Word needs to be a static string not a dynamic date

Right now both Word docs start the abstract with

UPDATED - 24 August 2015

That needs to be a static string, not an auto-updating date. It's very easy to accidentally put in an automatically updating date field -- if you hit return when the yellow window saying 24 August 2015, then it'll be replaced with an automatically updating field. It looks like this got changed (by accident) in the last Word doc update. It needs to get changed back.

todonotes throws error

Using \todo (from the todonotes package) in the latex template does produce the following error in the line where the command is used:
TeX capacity exceeded, sorry [input stack size=5000].
I tested this on both Windows and OS X, using MikTex, Tex Live, and MacTex.

Figure placement in Example Word Document

The example Word document states that figures and table should be placed at the top or bottom of columns, however, on the very same page both a figure and a table are placed in the middle of a column.

screen shot 2015-10-11 at 17 25 51

(I'd make a pull request with a corrected Word document, but I'm not sure how Git manages the merging of docx files).

Latex: hyperref does not produce working bookmarks for sections (first level elements)

Building the sample file proceedings.tex (or any derivative thereof) does not produce working PDF bookmarks for sections (first level elements). Looking closer into the issue in Acrobat reveals that the used destination name has different casing than the actual destination name. For example, the bookmark for the Introduction section points to the destination "section*.4", whereas the actual destination for the Introduction section is "SECTION*.4". Manually changing the destination for each section in Acrobat solves the issue. However, this should obviously be automatic.

I looked into the sigchi.cls, but this is about where my Latex foo ends. Didn't find a fix other than manually fixing bookmarks in Acrobat.

Initial Ref # Is Bold

In the SIGCHI Extended Abstracts Sample File, the first reference number is bolded but the rest aren't -- I assume they don't want to be bold, I think it picked it up from the header.

Caption style different between Latex and Word

In the word template, captions (also multiline) are centered, in the Latex template only single line captions are centered.
According to CHI specs, captions should be centered. Also, I think it looks way nicer.

Word Proceedings out of sync.

The word doc has several edits but was not committed (the PDF was). LaTeX bugs have been mostly cleared but now the Word version needs to be brought to sync - which may be a bit difficult but should be made easy by looking at the closed latex issues.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.