bob@mmsac.UUCP (Bob Brown) (07/02/89)
Hi, I hope someone can help me figure out what's wrong with the
following LaTeX file.
When I print, there is no pagebreak at the end of the first page
unless I force it. The words simply print off the end of the page.
After a paragraph or two, the document picks up on the next page. The
subsequent pages cause no problem whatsoever. While I can put in the
pagebreak at the appropriate place to make it do what I want, I would
think that LaTeX could figure out the pagebreak by itself.
I suspect the problem is tied up with either the "\LARGE" at the top
of the file or the multiply nested items. Any help would be appreciated.
bob
####### Start Here for the actual document #######
\documentstyle{article} % Specifies the document style.
\begin{tabbing}
------------------------------------------------------------\= --------------------- \= \kill
Contract Number GS-09F-50007 \>Task Order PFC579009
\end{tabbing}
\begin{center}
\LARGE
28 May 1989
\vspace{1ex}
Martin Marietta Data Systems\\
\vspace{2ex}
ADP Support Services for Highly\\
Technical Software Development\\
for Scientific Applications\\
\vspace{1ex}
Completion Task Progress Report\\
\end{center}
\begin{document}
\large
\newcounter{lev1}
\begin{list}{\Alph{lev1}}{\usecounter{lev1}}
\item {\bf Heading}
\newcounter{lev2}
\begin{list}%
{\arabic{lev2}}
{\usecounter{lev2}}
\item GSA Contract Number: GS-09F-5007
\item Using Agency: Air Logistics Center (ALC), McClellan AFB,
CA
\item Task Order Number: PFC579009
\item Subtask Number: E01
\end{list}
\item {\bf Body of the Report}
\newcounter{lev3}
\begin{list}%
{\arabic{lev3}}
{\usecounter{lev3}}
\item Purpose/Scope of Subtask: The purpose of this task, in
support of the Air Force Logistics Command (AFLC), Air
Logistics Center (ALC) at McClellan AFB, CA, is the
accomplishment of the detailed design, development, testing,
and implementation of thne Computer Console and Network
Monitoring System ({\sc Ccanms}). The purpose of this subtask
is to accomplish the detailed design.
\item Deliverable Products:
\newcounter{lev4}
\begin{list}%
{\alph{lev4}}
{\usecounter{lev4}}
% Put first deliverable product here
\item The Draft Detailed Design
\begin{description}
\newpage
\item [Brief description] A draft description
of what the product will consist of, including
appearance of screens, format of data bases,
forms of input and output, and required
hardware configuration.
\item [Scheduled start date] 03 Jan 89
\item [Scheduled completion date] 30 April 89
\item [Status] this product was delivered on
schedule and is currently under customer review
\item [Work Scheduled for Next Reporting
Period] \sloppy{We are awaiting the government's
review and inputs on the Draft Design.}
\end{description}
\item Final Detailed Design
\begin{description}
\item [Brief description] A more complete
description of what the product will consist
of, including appearance of screens, format of
data bases, forms of input and output, and
required hardware configuration. This
description is to be based on user feedback
combined with actual product development,
testing against Air Force computers, and
validation of the draft design.
\item [Scheduled start date] 01 July 1989
\item [Scheduled completion date] 31 July 1989
\item [Status] We are working toward
completing code and toward gaining access so
that we can validate the design and test the
code generated to date. Once government
review is completed on the draft, we will
incorporate that into the final.
\item [Work scheduled for next reporting
period] \sloppy{Plan to continue getting access. This
deliverable may be impacted by our inability
to gain access and validate the design, as
outlined in our letter to GSA, of 14 April 89.}
\end{description}
\item {\sc Ccanms}
\begin{description}
\item [Description] A working hardware and
software application which reflects the final
detailed design document.
\item [Scheduled start date] 03 January 1989
\item [Scheduled completion date] 31 December 1989
\item [Status]
\begin{itemize}
\item Hardware and software
support were obtained for the
computer system
\item The color editor was
finished and functional.
\item the vt100 emulator was
made fully functional, and
tested against various
alternative emulators
\item ``patch'', a key
software tool, was made
functional in our environment
\item SunOS patches were
applied which made our Sun
workstations considerably more
stable
\item Code to generate an
online version of our manuals
was obtained. It generates
online-readable versions of
documentation written--as ours
is--in the language, TeX.
\end{itemize}
\item [Work scheduled for next reporting
period] \sloppy{Plan to continue getting access. This
deliverable may be impacted by our inability
to gain access and validate the design, as
outlined in our letter to GSA, of 14 April 89.}
\end{description}
\end{list}
\item Highlights of the month
% 29 May 89 through 25 June 89
\begin{itemize}
\item A meeting was held with key department
leaders from McClellan AFB, the GSA representative,
and MMDS personnel, in which the Air Force
agreed to give a sufficient level of real-time
access to MMDS at their site in Sacramento
\item \sloppy{Eben Visher took over on-site task
leadership from Hal Trainer.}
\end{itemize}
\item The following items are noted for the record:
\begin{itemize}
\item We are concerned about the tremendous
loss of time and manpower resulting from
efforts to obtain required access to computers
at McClellan AFB.
\item We are still awaiting promised access to
all important machines.
\item The building managers continue inaction
on getting the working environment to a
reasonable temperature range.
\end{itemize}
\end{list}
\end{list}
\end{document}
########## end here ##########
Thanks for your help
bob brown
uunet!mmsac!bobken@cs.rochester.edu (Ken Yap) (07/03/89)
|When I print, there is no pagebreak at the end of the first page |unless I force it. The words simply print off the end of the page. |After a paragraph or two, the document picks up on the next page. The |subsequent pages cause no problem whatsoever. While I can put in the |pagebreak at the appropriate place to make it do what I want, I would |think that LaTeX could figure out the pagebreak by itself. Move the \begin{document} to just after \documentstyle. You should not have any matter to be typeset before the \begin{document} line.
leichter@CS.YALE.EDU (Jerry Leichter (LEICHTER-JERRY@CS.YALE.EDU)) (07/06/89)
In article <767@luna.mmsac.UUCP>, bob@mmsac.UUCP (Bob Brown) writes... > >Hi, I hope someone can help me figure out what's wrong with the >following LaTeX file. > >When I print, there is no pagebreak at the end of the first page >unless I force it.... > >\documentstyle{article} % Specifies the document style. > >\begin{tabbing} >... >\end{tabbing} > >\begin{center} >... >\end{center} > >\begin{document} >\large >... >\end{document} You cannot have ANY text-generating stuff before the \begin{document}, or random things will go wrong. In most cases, LaTeX will diagnose this problem. For complex reasons that aren't work going into, this particular example manages to evade LaTeX's tests; so it SEEMS to work - at least for a while. The solution to your problem is simple: Move the \begin{document} to just after the \documentstyle, and it will work normally. (The EXPLANATION of why LaTeX fails to diagnose the problem in this case is not simple, and in fact would require some staring at the LaTeX sources to understand in detail.) BTW, you might want to look at the actual text being used in this memo and compare it what the LaTeX book says about various typographical conventions. For example, read the LaTeX book's discussion of where to use n-dashes (--) and where to use m-dashes (---). You might also consider defining your own list environment for your inner lettered lists, rather than writing them out in terms of \begin{list} each time. Even better, since you seem to want ALL your lists to follow this format, you should think of your definitions as creating a new style - a style very similar to "article", but distinct none- theless. Hence, you might want to create a private variation of "article" with \enumerate modified to follow your conventions. The kind of change you would need to make is quite simple, and some time spent looking at the defi- -- Jerry