new package sugconf for sas proceedings

git-svn-id: svn://tug.org/texlive/trunk@1934 c570f23f-e606-0410-a88d-b1316a301751

8 files changed, 494 insertions, 0 deletions

diff --git a/Master/texmf-dist/doc/latex/sugconf/README b/Master/texmf-dist/doc/latex/sugconf/README
new file mode 100644
index 00000000000..a2f68295708
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/sugconf/README
@@ -0,0 +1,95 @@
+       name: 00readme-sugconf.txt

+description: read me for sugconf.cls

+    purpose: introduction and explanation

+             of LaTeX document class sugconf

+             for SAS(R) User Group (SUG) conference authors

+       date: 8/10/2006 posted to CTAN

+     author: Ronald J. Fehd, SAS-L's macro maven

+                             TeX User Group (TUG) member

+             mailto:RJF2@cdc.gov

+       note: SAS-L is the name of listserv

+                   of the international online SAS user group community

+       note: CTAN: Comprehensive TeX Archive Network

+       note: License type:  Free, LaTeX project public license

+             http://www.latex-project.org/lppl/

+

+* SUG authors

+

+LaTeX is a set of macros for the TeX document processing application.

+

+Several years ago I began using LaTeX to write my SUG papers.

+In order to produce a paper which conforms

+to SAS User Group International conference paper guidelines

+it is necessary to modify the LaTeX document class article.

+

+After reviewing several other LaTeX class files: e.g.: acmconf.cls,

+I wrote my own SUGconf.cls and posted it to SAS-L.

+http://www.listserv.uga.edu/cgi-bin/wa?S1=sas-l

+

+The layout produced by the 'sugconf' class

+is based on the description contained in SUGI paper guidelines,

+published by SAS Institute: (2006)

+http://support.sas.com/usergroups/sugi/sugi31/package/WritersGuidelines.pdf

+

+At the 2006 PracTeX conference, a Little Birdie

+(SAS-L euphemism for a SAS Institute employee)

+suggested that it would be a Good Idea to post my class file

+and some examples to CTAN,

+by which act I would then accept responsibility for maintenance.

+

+

+* All SUG conferences now require submission of papers as a .pdf.

+TeX distributions provide pdfLaTeX.exe which produces a .pdf

+from the source text file. (.tex or .ltx or .txt).

+The .pdf can be read with Adobe Reader v5 or greater.

+Note: pdfLaTeX also produces a .dvi, which is easier to review

+while editing and polishing.

+See the command: \pdfoutput= in each .tex file.

+

+* filename extensions

+

+** .bat: windows batch file

+         executes pdfLaTeX, input      : <filename>.tex

+                      note: input may be <filename>.txt

+                            pdfoutput=0: <filename>.dvi

+                            pdfoutput=1: <filename>.pdf

+** .tex: input : text file containing LaTeX markup commands

+** .pdf: output: Adobe v5 or higher

+

+* Please review the following files

+in order to familiarize yourself with LaTeX markup commands.

+

+** article-example illustrates the LaTeX document class article

+article-example.bat

+article-example.tex

+article-example.pdf

+

+** this file provides the LaTeX document class sugconf based on article

+   you must download this file and place it in the same folder

+   with your SUG-conf-paper

+

+sugconf.cls

+

+** sugconf-example is a working example of the document class sugconf

+   download these files and rename them to <My-SUG-conf-paper>.*

+   note: remember to change the filename in the .bat file

+         from sugconf-example

+         to   <My-SUG-conf-paper>

+

+sugconf-example.bat

+sugconf-example.pdf

+sugconf-example.tex

+

+* processing your .tex file with a Windows .bat file

+- - - -  article-example.bat - - -

+pdfLaTeX article-example

+- - - -  article-example.bat end - - -

+

+note assumption: filename extension is .tex

+to process a text file other than .tex, specify the extension:

+pdfLaTeX article-example.txt

+

+* highly recommended

+I recommend a professional text editor.

+

+\end{document}%00readme-sugconf.txt}

diff --git a/Master/texmf-dist/doc/latex/sugconf/SUGI-paper-example.txt b/Master/texmf-dist/doc/latex/sugconf/SUGI-paper-example.txt
new file mode 100644
index 00000000000..53f13af6b59
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/sugconf/SUGI-paper-example.txt
@@ -0,0 +1,86 @@
+Paper 999-99
+
+Paper Written for the Annual SUGI Conference
+
+SUGI Author, ABC Corporation, City, State
+SUGI Co-Author, ABC Corporation, City, State
+
+ABSTRACT (HEADER 1)
+
+A brief summary at the beginning highlights the major points of your
+paper. Include the complete names of all SAS products that are
+discussed in the paper, names of operating environments (if
+applicable), and the skill level that the intended audience should
+have. (9-point Arial regular)
+
+INTRODUCTION (HEADER 1)
+
+The introduction explains the purpose and scope of your paper.
+
+MAIN IDEA (Body of Paper, HEADER 1)
+
+This is a main topic in the body of the paper. This is the body of
+the paper. This is the body of the paper. This is the body of the
+paper. This is the body of the paper. This is programming code in
+the body of the paper.
+
+data one;
+set two;
+if mix(var1, var2) > 0 then do;
+run;
+Continuation of body of the paper.
+
+SUB-TOPIC (HEADER 2)
+
+This is a sub-topic in the body of the paper. This is text in the
+sub-topic. This is text in the sub-topic. This is programming code
+in the sub-topic in the body of the paper.
+
+data one;
+set two;
+if mix(var1, var2) > 0 then do;
+run;
+Continuation of body – after source code.
+
+ANOTHER MAIN TOPIC (HEADER 1)
+
+This is the text of another main idea. This is the text of another
+main idea. This is the text of another main idea
+
+CONCLUSION (HEADER 1)
+
+The conclusion summarizes the main ideas in your paper. You can also
+use the conclusion to highlight final points and make
+recommendations or predictions.
+
+REFERENCES (HEADER 1)
+
+This section is required only when information that was written,
+tested, or researched by someone other than the author is included
+in the paper.
+
+ACKNOWLEDGMENTS (HEADER 1)
+
+This section is not required. Use this section to thank people who
+were especially helpful to you when you wrote your paper, for
+example, co-workers, reviewers, product developers.
+
+CONTACT INFORMATION (HEADER 1)
+
+Your comments and questions are valued and encouraged.
+Contact the author(s):
+Name
+Enterprise
+Address
+City, State, ZIP
+Work Phone:
+Fax:
+E-mail:
+Web:
+
+SAS and all other SAS Institute Inc. product or service names are
+registered trademarks or trademarks of SAS Institute Inc. in the USA
+and other countries. ® indicates USA registration.
+
+Other brand and product names are trademarks of their respective
+companies.
diff --git a/Master/texmf-dist/doc/latex/sugconf/article-example.bat b/Master/texmf-dist/doc/latex/sugconf/article-example.bat
new file mode 100644
index 00000000000..5f573f79b61
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/sugconf/article-example.bat
@@ -0,0 +1 @@
+pdfLaTeX article-example
\ No newline at end of file
diff --git a/Master/texmf-dist/doc/latex/sugconf/article-example.pdf b/Master/texmf-dist/doc/latex/sugconf/article-example.pdf
new file mode 100644
index 00000000000..c506abd94c9
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/sugconf/article-example.pdf
diff --git a/Master/texmf-dist/doc/latex/sugconf/article-example.tex b/Master/texmf-dist/doc/latex/sugconf/article-example.tex
new file mode 100644
index 00000000000..a41f804abb4
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/sugconf/article-example.tex
@@ -0,0 +1,118 @@
+%% name       : article-example.tex
+%% description: example of LaTeX document class article
+%% purpose    : illustrate use of LaTeX markup
+%%              for SAS User Group conference authors
+%% author     : Ronald J. Fehd for CTAN
+%% date       : 8/4/2006
+%% make       : pdflatex article-example
+
+\documentclass{article}%note: font size, default: 10 points
+%\documentclass[12pt]{article}%note: change font size to 12 points
+\pdfoutput=0%out=jobname.dvi
+\pdfoutput=1%out=jobname.pdf
+\renewcommand{\rmdefault}{phv}%Adobe Helvetica san-serif
+
+\title{{\small Paper 999-99}
+       \\% LaTeX note: double backslash: newline
+       Paper written for an annual SUG conference
+       }%end title
+\author{SUGI Author, ABC Corporation, City, State
+        \\% LaTeX note: double backslash: newline
+        SUGI Co-Author, ABC Corporation, City, State
+        }%end author
+\date{\relax}%TeX note: relax: null
+
+\begin{document}\maketitle%
+
+\begin{abstract} %(HEADER 1)? well, not exactly!
+
+A brief summary at the beginning highlights the major points of your
+paper. Include the complete names of all SAS products that are
+discussed in the paper, names of operating environments (if
+applicable), and the skill level that the intended audience should
+have. (9-point Arial regular)
+\end{abstract}
+
+\section{INTRODUCTION (HEADER 1)}
+
+The introduction explains the purpose and scope of your paper.
+
+\section{MAIN IDEA (Body of Paper, HEADER 1)}
+
+This is a main topic in the body of the paper. This is the body of
+the paper. This is the body of the paper. This is the body of the
+paper. %This is the body of the paper.
+
+This is programming code in the body of the paper.
+
+\begin{verbatim}
+data one;
+set two;
+if max(var1, var2) > 0 then do;
+run;
+\end{verbatim}
+
+Continuation of body of the paper.
+
+\subsection{SUB-TOPIC (HEADER 2)}
+
+This is a sub-topic in the body of the paper. This is text in the
+sub-topic. %This is text in the sub-topic.
+This is programming code
+in the sub-topic in the body of the paper.
+
+\begin{verbatim}
+data one;
+set two;
+if min(var1, var2) < 0 then do;
+run;
+\end{verbatim}
+
+Continuation of body – after source code.
+
+\section{ANOTHER MAIN TOPIC (HEADER 1)}
+
+This is the text of another main idea. This is the text of another
+main idea. This is the text of another main idea
+
+\section{CONCLUSION (HEADER 1)}
+
+The conclusion summarizes the main ideas in your paper. You can also
+use the conclusion to highlight final points and make
+recommendations or predictions.
+
+\section{REFERENCES (HEADER 1)}
+
+This section is required only when information that was written,
+tested, or researched by someone other than the author is included
+in the paper.
+
+\section{ACKNOWLEDGMENTS (HEADER 1)}
+
+This section is not required. Use this section to thank people who
+were especially helpful to you when you wrote your paper, for
+example, co-workers, reviewers, product developers.
+
+\section{CONTACT INFORMATION (HEADER 1)}
+Your comments and questions are valued and encouraged.
+
+Contact the author(s):
+\begin{tabular}[t]{rl}
+Name               & NameFirst NameLast               \\
+Enterprise         & My Employer                      \\
+Address            & 123 Main St                      \\
+City, State, ZIP   & Anytown, ZZ, 99999               \\
+Work Phone:        & 987-654-1234                     \\
+Fax:               & 987-654-3210                     \\
+E-mail:            & firstname.lastname@mycompany.com \\
+Web:               & mycompany.com                    \\
+\end{tabular}
+
+SAS and all other SAS Institute Inc. product or service names are
+registered trademarks or trademarks of SAS Institute Inc. in the USA
+and other countries. %®
+\textregistered\/ indicates USA registration.
+
+Other brand and product names are trademarks
+of their respective companies.
+\end{document}
diff --git a/Master/texmf-dist/doc/latex/sugconf/sugconf-example.bat b/Master/texmf-dist/doc/latex/sugconf/sugconf-example.bat
new file mode 100644
index 00000000000..5284804820a
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/sugconf/sugconf-example.bat
@@ -0,0 +1 @@
+pdfLaTeX sugconf-example
\ No newline at end of file
diff --git a/Master/texmf-dist/doc/latex/sugconf/sugconf-example.pdf b/Master/texmf-dist/doc/latex/sugconf/sugconf-example.pdf
new file mode 100644
index 00000000000..235899feb91
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/sugconf/sugconf-example.pdf
diff --git a/Master/texmf-dist/doc/latex/sugconf/sugconf-example.tex b/Master/texmf-dist/doc/latex/sugconf/sugconf-example.tex
new file mode 100644
index 00000000000..23cc5a0f9cd
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/sugconf/sugconf-example.tex
@@ -0,0 +1,193 @@
+%% name       : sugconf-example.tex
+%% description: example of LaTeX document class sugconf
+%% purpose    : illustrate use of LaTeX markup
+%%              for SAS User Group conference authors
+%% author     : Ronald J. Fehd for CTAN
+%% date       : 8/10/2006
+%% note       : all text after a percent sign (%) is a comment
+%% note       : open *.pdf, <Ctrl> D to view pdf description
+%% make       : pdflatex sugconf-example
+
+\documentclass{sugconf}%
+%\documentclass[nopagenumbers]{sugconf}%
+\pdfoutput=0%out=jobname.dvi
+\pdfoutput=1%out=jobname.pdf
+
+%macro variables used by sugconf
+\sugconfsubject{writing paper using sugconf class}%
+\sugconfpapernumber{Paper 999-99}%
+%\sugconfpapernumber{\relax}%note: no paper number: warning in log
+\sugconfkeywords{documentclass, LaTeX class, pdfLaTeX,
+                 sugconf class}%end keywords: see in pdf description
+
+%begin LaTeX document commands
+%% NOTE: do not put newline (\\) in title nor author
+         reason: newline cannot be writen into pdf description
+\title{sugconf class example: Paper written for an annual SUG conference
+       }%end title
+\author{Ronald J. Fehd, TeX User Group member, Atlanta, GA, USA
+        }%end author
+
+%%book: The LaTeX Web Companion, Goossens and Rahtz, pg 43, 64, 65
+\makeatletter%necessary to copy title and author into pdf description
+\usepackage[bookmarks   =false%SUGI style guide
+           ,pdfauthor   ={\@author}%
+%          ,pdfauthor   ={author and coauthor}%
+           ,pdfcreator  ={pdfLaTeX sugconf.cls}%
+           ,pdfkeywords ={\SUGconfKeywords}%
+           ,pdfstartview=FitBH%fit width of page to the window
+           ,pdfsubject  ={\SUGconfSubject}%
+           ,pdftitle    ={\@title}%
+]{hyperref}\makeatother\begin{document}%
+\pdfcompresslevel=9%best compression level for text and image
+%end LaTeX document commands
+
+\begin{abstract}%\section{Abstract}
+
+A brief summary at the beginning highlights the major points of your
+paper. Include the complete names of all
+\SASregistered
+\textit{(First use of company name SAS must have \textregistered.)}
+products that are
+discussed in the paper, names of operating environments (if
+applicable), and the skill level that the intended audience should
+have. (9-point Arial regular)
+\textit{Note: sugconf.cls uses Adobe Helvetica san-serif, 10 point.}
+
+\textit{You could use the \LaTeX\ abstract environment,
+illustrated in} \texttt{article-example.pdf} which centers the abstract.
+\begin{verbatim}
+\begin{abstract}
+A brief summary at the beginning
+highlights the major points of your paper.
+\end{abstract}
+\end{verbatim}
+
+Keywords: \SUGconfKeywords.%macro variable provided by sugconf.cls
+\end{abstract}
+
+\section{Introduction}
+
+The introduction explains the purpose and scope of this paper,
+which is to provide SAS user group conference authors
+with a text file, \texttt{sugconf-example.tex},
+for use as a template.
+
+\section{Main Idea}
+
+This is a main topic in the body of the paper.
+\LaTeX markup is simple.
+Instead of highlighting and bolding each topic explanation,
+use the markup keywords: \texttt{section} and \texttt{subsection}.
+%This is the body of the paper. These lines are commented out.
+%This is the body of the paper. This is the body of the paper.
+
+This illustrates markup in the body of the paper.
+
+\begin{verbatim}
+\section{Abstract}%note: is uppercase when printed
+A brief summary ...
+
+\section{Introduction}
+The introduction ...
+
+\subsection{Sub-Topic (Header 2)}
+This idea is ...
+\end{verbatim}
+
+%Continuation of body of the paper.
+This is programming code in the text of the paper.
+\texttt{proc freq data = sashelp.class;}
+That is programming code in the text of the paper.
+
+\subsection{Sub-Topic number 3)}
+
+Typesetting special characters (ampersand and percent sign)
+in your paper requires you to use
+the backslash before the character:
+\%Let mvar = value; \%put mvar \&mvar.;
+This is necessary when using \textit{texttt} as well:
+\texttt{\%Let mvar = value; \%put mvar \&mvar.;}
+
+This is programming code
+in the sub-topic in the body of the paper.
+
+\begin{verbatim}
+data one;
+set  two;
+if   max(var1, var2) > 0 then do;
+run;
+\end{verbatim}
+
+A single hyphen with spaces around it - is not a dash.
+Text continues --– after source code.
+The previous line contains an \textit{em} dash,
+which is typed as three hyphens;
+Use two hyphens (an \textit{en} dash) to indicate a range: pages 2--4.
+
+\section{Another Main Topic}
+
+This is the text of another main idea.
+When you use \LaTeX\ to write your SAS user group conference paper
+your output is an Adobe pdf (version 1.4, Acrobat 5.x).
+To view the pdf description: Ctrl D.
+%This is the text of another main idea.
+%This is the text of another main idea
+
+\section{Conclusion}
+
+The conclusion summarizes the main ideas in your paper.
+You can also use the conclusion to highlight final points
+and make recommendations or predictions.
+
+\section{References}
+
+This section is required only when information that was written,
+tested, or researched by someone other than the author is included
+in the paper.
+
+\begin{tabular}[t]{llll}
+\textbf{Required}
+&   A Guide to \LaTeX, 4e & Helmut Kopka and Patrick W. Daly \\
+& \multicolumn{2}{l}{\tiny\url{
+http://www.amazon.com/gp/product/0321173856/sr=1-1/qid=1154721435/ref=pd_bbs_1/103-4249973-4753405?ie=UTF8&s=books
+}}\\
+\textbf{Recommended}
+&   The \LaTeX\ Companion, 2e& Frank Mittelback and Michel Goossens,
+        et al. \\
+& \multicolumn{2}{l}{\tiny\url{
+http://www.amazon.com/gp/product/0201362996/ref=pd_sim_b_1/103-4249973-4753405?ie=UTF8
+}}\\
+&   The \LaTeX\ Web Companion & Michel Goossens and Sebastian Rahtz,
+        et al. \\
+& \multicolumn{2}{l}{\tiny\url{
+http://www.amazon.com/gp/product/0201433117/sr=1-1/qid=1154721919/ref=sr_1_1/103-4249973-4753405?ie=UTF8&s=books
+}}\\
+\end{tabular}
+
+\section{Acknowledgments}
+
+This section is not required. Use this section to thank people who
+were especially helpful to you when you wrote your paper, for
+example, co-workers, reviewers, product developers.
+
+\section{Contact Information}
+Your comments and questions are valued and encouraged.
+
+Contact the author(s):
+%\begin{tabular}[c]{ll}%both columns are left justtified
+\begin{tabular}[t]{rl}%note: double backslash(\\): newline
+Name               & Ronald J. Fehd                   \\
+Enterprise         & Centers for Disease Control      \\
+%Address            & 123 Main St                      \\
+City, State, ZIP   & Atlanta, GA, 30341               \\
+%Work Phone:        & 987-654-1234                     \\
+%Fax:               & 987-654-3210                     \\
+E-mail:            & \url{mailto:RJF2@cdc.gov}        \\
+%Web:               & mycompany.com                    \\
+\end{tabular}
+
+\SASisRegisteredTrademark%macro variable provided by sugconf.cls
+
+\OtherTrademarks%macro variable provided by sugconf.cls
+\end{document}