Wahrscheinlich kleiner Fehler!

[Father_smu]

Hallo liebe goLatex Community.

Mir ist nun schon zum wiederholten male passiert das Latex unverständliches Verhalten an den Tag legt.
Ich schreibe mit dem USBTech1.7 dem Texmaker. Seltsamer weise bekam ich nun zum zweiten mal eine unerklärliche Reihe von Fehlermeldungen obwohl die Syntax und alles andere stimmt. Denn wenn ich den Text den ich bis dahin wieder rausschneide und es versuch erneut zu kompilieren, gibt er die selben Fehler an. Das letzte mal als ich das Problem hatte habe ich die Textinhalte einfach per Copy Paste in ein anderes Dokument hinzugefügt und siehe da, es gab keine Fehler mehr. Sehr seltsam.
Hier die Masse an Fehlern die es ausspuckt.

! Paragraph ended before \contentsline was complete.
<to be read again>
\par
l.14 ... a bug in a package file you are using\par
} \par \def \GenericInfo ...
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
! Extra }, or forgotten \endgroup.
l.14 ... bug in a package file you are using\par }
\par \def \GenericInfo { ...
I've deleted a group-closing symbol because it seems to be
spurious, as in `$x}$'. But perhaps the } is legitimate and
you forgot something else, as in `\hbox{$x}'. In such cases
the way to recover is to insert both the forgotten and the
deleted material, e.g., by typing `I$}'.
! Use of doesn't match its definition.
l.14 ...g\par } \par \def \GenericInfo { }{LaTeX I
nfo: Active EOL character ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...} \par \def \GenericInfo { }{LaTeX Info: A
ctive EOL character found ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...\def \GenericInfo { }{LaTeX Info: Active E
OL character found while o...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ... \GenericInfo { }{LaTeX Info: Active EOL c
haracter found while outpu...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...nfo { }{LaTeX Info: Active EOL character f
ound while output routine ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...}{LaTeX Info: Active EOL character found w
hile output routine is act...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...X Info: Active EOL character found while o
utput routine is active \M...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ... Active EOL character found while output r
outine is active \MessageB...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...EOL character found while output routine i
s active \MessageBreak Thi...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ... character found while output routine is a
ctive \MessageBreak This m...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ile output routine is active \MessageBreak
This may be a bug in a pa...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...e output routine is active \MessageBreak T
his may be a bug in a pack...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...put routine is active \MessageBreak This m
ay be a bug in a package f...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...routine is active \MessageBreak This may b
e a bug in a package file ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...tine is active \MessageBreak This may be a
bug in a package file you...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ne is active \MessageBreak This may be a b
ug in a package file you a...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...s active \MessageBreak This may be a bug i
n a package file you are u...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ctive \MessageBreak This may be a bug in a
package file you are usin...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ive \MessageBreak This may be a bug in a p
ackage file you are using\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...sageBreak This may be a bug in a package f
ile you are using\par } {\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...reak This may be a bug in a package file y
ou are using\par } {\globa...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ... This may be a bug in a package file you a
re using\par } {\global \l...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...s may be a bug in a package file you are u
sing\par } {\global \let \...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
Overfull \hbox (9.40886pt too wide) in paragraph at lines 14--14
[]\T1/cmr/m/n/12 LaTeXnfo:ctiveOLharacteroundhileutputoutinesctivehisayeugnacka
geileouresing
[]
! Use of doesn't match its definition.
l.14 ... bug in a package file you are using\par }
{\global \let \egroup \Ge...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ug in a package file you are using\par } {
\global \let \egroup \Gene...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...age file you are using\par } {\global \let
\egroup \GenericError { }...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ... you are using\par } {\global \let \egroup
\GenericError { }{LaTeX E...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...\par } {\global \let \egroup \GenericError
{ }{LaTeX Error: \verb en...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ar } {\global \let \egroup \GenericError {
}{LaTeX Error: \verb ende...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ... } {\global \let \egroup \GenericError { }
{LaTeX Error: \verb ended ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! You can't use a prefix with `begin-group character {'.
<to be read again>
{
l.14 ...} {\global \let \egroup \GenericError { }{
LaTeX Error: \verb ended b...
I'll pretend you didn't say \long or \outer or \global or \protected.
! Use of doesn't match its definition.
l.14 ...bal \let \egroup \GenericError { }{LaTeX E
rror: \verb ended by end o...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...group \GenericError { }{LaTeX Error: \verb
ended by end of line}{See...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...oup \GenericError { }{LaTeX Error: \verb e
nded by end of line}{See t...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...enericError { }{LaTeX Error: \verb ended b
y end of line}{See the LaT...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ricError { }{LaTeX Error: \verb ended by e
nd of line}{See the LaTeX ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...rror { }{LaTeX Error: \verb ended by end o
f line}{See the LaTeX manu...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...r { }{LaTeX Error: \verb ended by end of l
ine}{See the LaTeX manual ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...X Error: \verb ended by end of line}{See t
he LaTeX manual or LaTeX C...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ror: \verb ended by end of line}{See the L
aTeX manual or LaTeX Compa...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...verb ended by end of line}{See the LaTeX m
anual or LaTeX Companion f...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ded by end of line}{See the LaTeX manual o
r LaTeX Companion for expl...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ... by end of line}{See the LaTeX manual or L
aTeX Companion for explana...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...d of line}{See the LaTeX manual or LaTeX C
ompanion for explanation.}...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...{See the LaTeX manual or LaTeX Companion f
or explanation.}{Try typin...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ... the LaTeX manual or LaTeX Companion for e
xplanation.}{Try typing <r...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...or LaTeX Companion for explanation.}{Try t
yping <return> to proceed....
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...X Companion for explanation.}{Try typing <
return> to proceed.\Messag...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...on for explanation.}{Try typing <return> t
o proceed.\MessageBreak If...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...for explanation.}{Try typing <return> to p
roceed.\MessageBreak If th...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...typing <return> to proceed.\MessageBreak I
f that doesn't work, type ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ing <return> to proceed.\MessageBreak If t
hat doesn't work, type X <...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...return> to proceed.\MessageBreak If that d
oesn't work, type X <retur...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...to proceed.\MessageBreak If that doesn't w
ork, type X <return> to qu...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ceed.\MessageBreak If that doesn't work, t
ype X <return> to quit.}}\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...\MessageBreak If that doesn't work, type X
<return> to quit.}}\let \...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...essageBreak If that doesn't work, type X <
return> to quit.}}\let \do...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...ak If that doesn't work, type X <return> t
o quit.}}\let \do \catcode...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...If that doesn't work, type X <return> to q
uit.}}\let \do \catcode `\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Missing number, treated as zero.
<to be read again>
l.14 ...pe X <return> to quit.}}\let \do \catcode
`\do \ \do \let \reserved@...
A number should have been here; I inserted `0'.
(If you can't figure out why I needed to see a number,
look up `weird error' in the index to The TeXbook.)
! Missing number, treated as zero.
<to be read again>
l.14 ...pe X <return> to quit.}}\let \do \catcode
`\do \ \do \let \reserved@...
A number should have been here; I inserted `0'.
(If you can't figure out why I needed to see a number,
look up `weird error' in the index to The TeXbook.)
! Use of doesn't match its definition.
l.14 ... \@M \let \reserved@d =[\def \def \let } }
} } }
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...@M \let \reserved@d =[\def \def \let } } }
} }
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ... \let \reserved@d =[\def \def \let } } } }
}
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.14 ...let \reserved@d =[\def \def \let } } } } }
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
Runaway argument?
{\numberline {4.3}{\ignorespaces Beispiel: Anfrage an imitierte Spe\ETC.
! Paragraph ended before \contentsline was complete.
<to be read again>
\par
l.15 ... a bug in a package file you are using\par
} \par \def \GenericInfo ...
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
Overfull \hbox (242.74634pt too wide) in paragraph at lines 14--15
[]\T1/cmr/m/n/12 LaTeXrror:ndedyndfineSeeheaTeXanualraTeXompanionorxplanation.T
ryypingreturn>oroceed.fhatoesn'tork,ypereturn>ouit.`
[]
! Use of doesn't match its definition.
l.15 ... bug in a package file you are using\par }
\par \def \GenericInfo { ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...in a package file you are using\par } \par
\def \GenericInfo { }{LaT...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! You can't use `\vadjust' in vertical mode.
\def ->\let \reserved@e \vadjust
\let \reserved@f \penalty \@M \let...
l.15 ...ackage file you are using\par } \par \def
\GenericInfo { }{LaTeX Inf...
Sorry, but I'm not programmed to handle this case;
I'll just pretend that you didn't ask for it.
If you're in the wrong mode, you might be able to
return to the right one by typing `I}' or `I$' or `I\par'.
! Missing number, treated as zero.
<to be read again>
l.15 ...ackage file you are using\par } \par \def
\GenericInfo { }{LaTeX Inf...
A number should have been here; I inserted `0'.
(If you can't figure out why I needed to see a number,
look up `weird error' in the index to The TeXbook.)
! Missing $ inserted.
<inserted text>
$
l.15 ...ackage file you are using\par } \par \def
\GenericInfo { }{LaTeX Inf...
I've inserted a begin-math/end-math symbol since I think
you left one out. Proceed, with fingers crossed.
! Use of doesn't match its definition.
l.15 ...g\par } \par \def \GenericInfo { }{LaTeX I
nfo: Active EOL character ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...} \par \def \GenericInfo { }{LaTeX Info: A
ctive EOL character found ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...\def \GenericInfo { }{LaTeX Info: Active E
OL character found while o...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... \GenericInfo { }{LaTeX Info: Active EOL c
haracter found while outpu...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...nfo { }{LaTeX Info: Active EOL character f
ound while output routine ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...}{LaTeX Info: Active EOL character found w
hile output routine is act...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...X Info: Active EOL character found while o
utput routine is active \M...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... Active EOL character found while output r
outine is active \MessageB...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...EOL character found while output routine i
s active \MessageBreak Thi...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... character found while output routine is a
ctive \MessageBreak This m...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ile output routine is active \MessageBreak
This may be a bug in a pa...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...e output routine is active \MessageBreak T
his may be a bug in a pack...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...put routine is active \MessageBreak This m
ay be a bug in a package f...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...routine is active \MessageBreak This may b
e a bug in a package file ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...tine is active \MessageBreak This may be a
bug in a package file you...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ne is active \MessageBreak This may be a b
ug in a package file you a...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...s active \MessageBreak This may be a bug i
n a package file you are u...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ctive \MessageBreak This may be a bug in a
package file you are usin...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ive \MessageBreak This may be a bug in a p
ackage file you are using\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...sageBreak This may be a bug in a package f
ile you are using\par } {\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...reak This may be a bug in a package file y
ou are using\par } {\globa...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... This may be a bug in a package file you a
re using\par } {\global \l...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...s may be a bug in a package file you are u
sing\par } {\global \let \...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Missing $ inserted.
<inserted text>
$
l.15 ... a bug in a package file you are using\par
} {\global \let \egroup \...
I've inserted a begin-math/end-math symbol since I think
you left one out. Proceed, with fingers crossed.
! Missing } inserted.
<inserted text>
}
l.15 ... a bug in a package file you are using\par
} {\global \let \egroup \...
I've inserted something that you may have forgotten.
(See the <inserted text> above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.
! \textfont 7 is undefined (character ).
<recently read> $
l.15 ... a bug in a package file you are using\par
} {\global \let \egroup \...
Somewhere in the math formula just ended, you used the
stated character from an undefined font family. For example,
plain TeX doesn't allow \it or \sl in subscripts. Proceed,
and I'll try to forget that I needed that character.
Overfull \hbox (67.59683pt too wide) in paragraph at lines 15--15
[]$\OMS/cmsy/m/n/12 \OT1/cmr/m/n/12 = [[]$
[]
! Use of doesn't match its definition.
l.15 ...g\par } \par \def \GenericInfo { }{LaTeX I
nfo: Active EOL character ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...} \par \def \GenericInfo { }{LaTeX Info: A
ctive EOL character found ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...\def \GenericInfo { }{LaTeX Info: Active E
OL character found while o...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... \GenericInfo { }{LaTeX Info: Active EOL c
haracter found while outpu...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...nfo { }{LaTeX Info: Active EOL character f
ound while output routine ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...}{LaTeX Info: Active EOL character found w
hile output routine is act...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...X Info: Active EOL character found while o
utput routine is active \M...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... Active EOL character found while output r
outine is active \MessageB...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...EOL character found while output routine i
s active \MessageBreak Thi...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... character found while output routine is a
ctive \MessageBreak This m...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ile output routine is active \MessageBreak
This may be a bug in a pa...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...e output routine is active \MessageBreak T
his may be a bug in a pack...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...put routine is active \MessageBreak This m
ay be a bug in a package f...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...routine is active \MessageBreak This may b
e a bug in a package file ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...tine is active \MessageBreak This may be a
bug in a package file you...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ne is active \MessageBreak This may be a b
ug in a package file you a...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...s active \MessageBreak This may be a bug i
n a package file you are u...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ctive \MessageBreak This may be a bug in a
package file you are usin...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ive \MessageBreak This may be a bug in a p
ackage file you are using\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...sageBreak This may be a bug in a package f
ile you are using\par } {\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...reak This may be a bug in a package file y
ou are using\par } {\globa...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... This may be a bug in a package file you a
re using\par } {\global \l...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...s may be a bug in a package file you are u
sing\par } {\global \let \...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
Overfull \hbox (9.40886pt too wide) in paragraph at lines 15--15
[]\T1/cmr/m/n/12 LaTeXnfo:ctiveOLharacteroundhileutputoutinesctivehisayeugnacka
geileouresing
[]
! Use of doesn't match its definition.
l.15 ... bug in a package file you are using\par }
{\global \let \egroup \Ge...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ug in a package file you are using\par } {
\global \let \egroup \Gene...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...age file you are using\par } {\global \let
\egroup \GenericError { }...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... you are using\par } {\global \let \egroup
\GenericError { }{LaTeX E...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...\par } {\global \let \egroup \GenericError
{ }{LaTeX Error: \verb en...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ar } {\global \let \egroup \GenericError {
}{LaTeX Error: \verb ende...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... } {\global \let \egroup \GenericError { }
{LaTeX Error: \verb ended ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! You can't use a prefix with `begin-group character {'.
<to be read again>
{
l.15 ...} {\global \let \egroup \GenericError { }{
LaTeX Error: \verb ended b...
I'll pretend you didn't say \long or \outer or \global or \protected.
! Use of doesn't match its definition.
l.15 ...bal \let \egroup \GenericError { }{LaTeX E
rror: \verb ended by end o...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...group \GenericError { }{LaTeX Error: \verb
ended by end of line}{See...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...oup \GenericError { }{LaTeX Error: \verb e
nded by end of line}{See t...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...enericError { }{LaTeX Error: \verb ended b
y end of line}{See the LaT...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ricError { }{LaTeX Error: \verb ended by e
nd of line}{See the LaTeX ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...rror { }{LaTeX Error: \verb ended by end o
f line}{See the LaTeX manu...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...r { }{LaTeX Error: \verb ended by end of l
ine}{See the LaTeX manual ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...X Error: \verb ended by end of line}{See t
he LaTeX manual or LaTeX C...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ror: \verb ended by end of line}{See the L
aTeX manual or LaTeX Compa...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...verb ended by end of line}{See the LaTeX m
anual or LaTeX Companion f...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ded by end of line}{See the LaTeX manual o
r LaTeX Companion for expl...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... by end of line}{See the LaTeX manual or L
aTeX Companion for explana...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...d of line}{See the LaTeX manual or LaTeX C
ompanion for explanation.}...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...{See the LaTeX manual or LaTeX Companion f
or explanation.}{Try typin...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... the LaTeX manual or LaTeX Companion for e
xplanation.}{Try typing <r...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...or LaTeX Companion for explanation.}{Try t
yping <return> to proceed....
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...X Companion for explanation.}{Try typing <
return> to proceed.\Messag...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...on for explanation.}{Try typing <return> t
o proceed.\MessageBreak If...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...for explanation.}{Try typing <return> to p
roceed.\MessageBreak If th...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...typing <return> to proceed.\MessageBreak I
f that doesn't work, type ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ing <return> to proceed.\MessageBreak If t
hat doesn't work, type X <...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...return> to proceed.\MessageBreak If that d
oesn't work, type X <retur...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...to proceed.\MessageBreak If that doesn't w
ork, type X <return> to qu...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ceed.\MessageBreak If that doesn't work, t
ype X <return> to quit.}}\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...\MessageBreak If that doesn't work, type X
<return> to quit.}}\let \...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...essageBreak If that doesn't work, type X <
return> to quit.}}\let \do...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ak If that doesn't work, type X <return> t
o quit.}}\let \do \catcode...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...If that doesn't work, type X <return> to q
uit.}}\let \do \catcode `\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Missing number, treated as zero.
<to be read again>
l.15 ...pe X <return> to quit.}}\let \do \catcode
`\do \ \do \let \reserved@...
A number should have been here; I inserted `0'.
(If you can't figure out why I needed to see a number,
look up `weird error' in the index to The TeXbook.)
! Missing number, treated as zero.
<to be read again>
l.15 ...pe X <return> to quit.}}\let \do \catcode
`\do \ \do \let \reserved@...
A number should have been here; I inserted `0'.
(If you can't figure out why I needed to see a number,
look up `weird error' in the index to The TeXbook.)
! Use of doesn't match its definition.
l.15 ...served@e {\reserved@f \relax }\penalty \@M
\hfil \penalty -\@M {\let...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...@e {\reserved@f \relax }\penalty \@M \hfil
\penalty -\@M {\let \rese...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...rved@f \relax }\penalty \@M \hfil \penalty
-\@M {\let \reserved@d =[...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ed@f \relax }\penalty \@M \hfil \penalty -
\@M {\let \reserved@d =[\d...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...\relax }\penalty \@M \hfil \penalty -\@M {
\let \reserved@d =[\def \d...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...served@e {\reserved@f \relax }\penalty \@M
\hfil \penalty -\@M {\uns...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...@e {\reserved@f \relax }\penalty \@M \hfil
\penalty -\@M {\unskip \r...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...rved@f \relax }\penalty \@M \hfil \penalty
-\@M {\unskip \reserved@e...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ed@f \relax }\penalty \@M \hfil \penalty -
\@M {\unskip \reserved@e {...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...\relax }\penalty \@M \hfil \penalty -\@M {
\unskip \reserved@e {\rese...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...M \hfil \penalty -\@M {\unskip \reserved@e
{\reserved@f \relax }\pen...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...\hfil \penalty -\@M {\unskip \reserved@e {
\reserved@f \relax }\penal...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...M {\unskip \reserved@e {\reserved@f \relax
}\penalty \@M \hfil \pena...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...{\unskip \reserved@e {\reserved@f \relax }
\penalty \@M \hfil \penalt...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...served@e {\reserved@f \relax }\penalty \@M
\hfil \penalty -\@M }\fut...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...@e {\reserved@f \relax }\penalty \@M \hfil
\penalty -\@M }\futurelet...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...rved@f \relax }\penalty \@M \hfil \penalty
-\@M }\futurelet \@let@to...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ed@f \relax }\penalty \@M \hfil \penalty -
\@M }\futurelet \@let@toke...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...\relax }\penalty \@M \hfil \penalty -\@M }
\futurelet \@let@token \le...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...\penalty -\@M }\futurelet \@let@token \let
\unskip \reserved@e {\res...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... -\@M }\futurelet \@let@token \let \unskip
\reserved@e {\reserved@f ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...relet \@let@token \let \unskip \reserved@e
{\reserved@f \relax }\pen...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...let \@let@token \let \unskip \reserved@e {
\reserved@f \relax }\penal...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...et \unskip \reserved@e {\reserved@f \relax
}\penalty \@M \hfil \pena...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... \unskip \reserved@e {\reserved@f \relax }
\penalty \@M \hfil \penalt...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...served@e {\reserved@f \relax }\penalty \@M
\hfil \penalty -\@M \unsk...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...@e {\reserved@f \relax }\penalty \@M \hfil
\penalty -\@M \unskip \re...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...rved@f \relax }\penalty \@M \hfil \penalty
-\@M \unskip \reserved@e ...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ...ed@f \relax }\penalty \@M \hfil \penalty -
\@M \unskip \reserved@e {\...
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Use of doesn't match its definition.
l.15 ... }\penalty \@M \hfil \penalty -\@M \unskip
\reserved@e {\reserved@f ...
If you say, e.g., `\def\a1{...}', th

[Genmutant]

Ah, wtf. Ich befürcht, nur mit der Fehlermeldung wird dir (wahrscheinlich) keiner helfen können. Was steht denn in der Zeile 14? Hast du probiert einfach mal alle Hilfsdateien zu löschen?
Ich vermute mal ein Minimalbeispiel wirst du nicht bauen können, das den Fehler reproduziert (hört sich zumindest so an)?
Hast du vielleicht vom kopieren irgendwelche komischen Sonderzeichen im Text? Das ist möglich wenn du z.b. Sachen aus Word o.ä. rauskopierst.

[Besserwisser]

\contentsline ist eine Anweisung, die üblicherweise in einem Verzeichnis verwendet wird. Demnach hast Du einen Fehler beispielsweise im Inhaltsverzeichnis, Tabellenverzeichnis oder Abbildungsverzeichnis. So ein Fehler übersteht üblicherweise auch min. einen LaTeX-Lauf. Deshalb ist Deine Analyse auch komplett falsch. Statt den problematischen Code wieder rauszuwerfen, solltest Du lieber ein echtes vollständiges Minimalbeispiel machen, Dein Dokument also zu einem Dokument reduzieren, das nur den problematischen Code enthält. Siehe dazu den Wiki-Eintrag zum Thema Minimalbeispiel.

PS: Morgen geht es endlich in Urlaub!!!

[Father_smu]

Ich habe gar nichts aus anderen quellen reinkopiert, diese line14 und line15 etc ist ja nicht nachzuvollziehen, den geschriebenen Text zeig ich euch mal. Mich wundert nur das es von jetzt auf nacher fast hundert errors gibt die ja nicht alle das selbe bedeuten.

das geschriebene:

\begin{figure}[!htb]
\centering
\includegraphics[width=1\textwidth]{Maccon_Order_Telegram.jpg}
\caption{Beispiel: Befehle an imitierten Maccon Controller des neutroSim}
\label{fig:Maccon_Order_Telegram}
\end{figure}

Anstatt den bis jetzt erörterten Anfragen, werden \verb|"neutroSim"| ebenso Befehle über den Com Port zugesendet. Diese Befehle werden in der Realität an den Controller gerichtet.\\
Demnach kann das hier entwickelte Programm durch eine Partnersoftware in gewisser Maße gesteuert oder manipuliert werden. Bei den Befehlen handelt es sich um reine Sicherheitsmechanismen von Seiten der Firmensoftware, um schwerwiegende Schäden einer realen Anlage möglichst zu vermeiden. Dieser Punkt ist einer der Hauptbestandteile, warum diese Software ins Leben gerufen wird. \verb|"neutroSim"| prüft, wie schon in Abschnitt \ref{sec:Motivation} erwähnt, die volle Funktionstüchtigkeit der verschiedensten Softwareversionen der Neutronenforschungsanlagen der Firma Astrium. Das erkennen der korrekten Ausführung bestimmter Sicherheitsmechanismen ist einer der wichtigsten Punkte. Denn Falls eine sicherheitsrelevante Funktion der Firmensoftware ausfallen sollte, wie zum Beispiel das abbremsen einer Scheibe oder der notwendigen Abkühlung des Systems, kann dies zu immensen wirtschaftlichen Schäden und zudem Lebensbedrohlichen Situationen führen.\\
Die Methode \verb|"setControllerValues()"| wertet zu erst, aus welchem \Go ComControl\Gu Objekt dieser Befehl entstammt. Danach unterscheiden sich die Befehle in simple Parameter Änderung und Parameter abhängigen Systemvorgängen. Ein Beispiel zu einem herkömmlichen Befehl zur Modifizierung der Parameter sehen sie in Abbildung \ref{fig:Maccon_Order_Telegram}. Es werden immer alle Parameterwerte gesamt mit dem Telegramm an \verb|"neutroSim"| gesendet. Dadurch ist die Größe des Paketes und dessen Inhalt vorauszusehen. Dies macht sich unsere Methode zu Nutzen und prüft die Rohdaten auf das spezielle \Go Accept-Endframe\Gu am Ende eines jeden Telegramms. Wurde dieses Zeichen erkannt, wird das Telegramm so gesplittet das die benötigten Informationen zu den jeweiligen Objekten übergeben werden können. Dem Absender wird noch ein spezielles Zeichen als Empfangsbestätigung gesendet.\\
Die übrigen Befehle dienen den zuvor erwähnten Systemvorgängen im Programm. 
Dies kommt einem Master-Slave Prinzip relativ nahe. Durch die Dokumentation \cite{Maccon_Controller} stehen dem Autor sämtliche mögliche Anfragen die an einen Maccon Controller gesendet werden können offen. Ebenso wurde die Dokumentation der Spectra Module zur Verfügung gestellt, womit dann auch die benötigten Protokolle zur Kommunikation studiert wurden.

%--------------------------------------------------------------
\newpage
Im Linken Feld des \Go Einrichten\Gu -Fensters dienen weitere Textboxen um einen TCP-Client zu erzeugen. Dazu benötigt es eine IP- Adresse und einen für das System bereits geöffneter Port. Ebenso kann dieser Verbindung ein ein Name zugeordnet werden. Als kleines Gimmick enthält dieser Teil der Datenübertragung eine Textbox mit welcher demonstriert werden kann das eine Verbindung zu einem Partnergerät hergestellt ist.\\ Da zum Zeitpunkt dieser Bachelor Thesis aber die Verwendung eines TCP-Clients nur niederer Wichtigkeit entstammte, wird diese Option nicht weiter mit dem Rest des Programms verknüpft.

[Genmutant]

Keine Ahnung woran das liegt, aber als zusätzlicher Tip: Benutz keine harten Umbrüche mit \\, sondern mach Absätze so wie es sich gehört: Mit einer Leerzeile.

[Sirius3]

Hallo,

wie Besserwisser bereits angedeutet hat, wird das Macro \contentline
beim Aufbau irgendwelcher Verzeichnisse benutzt. Dass der Fehler
weiterhin auftritt, obwohl Du die letzten Änderungen rückgängig gemacht hast,
liegt an der Art wie LaTeX solche Verzeichnisse erzeugt. Nehmen wir
zum Beispiel das Inhaltsverzeichnis. Es steht am Anfang des Dokuments.
Zu diesem Zeitpunkt kennt LaTeX ja eigentlich noch gar keine Kapitelüberschriften
und Seitenzahlen. Es bleibt also leer. Jedoch wird beim Erzeugen des restlichen
Textes für jedes Kapitel eine Zeile mit \contentline in eine Hilfsdatei (mit der Endung
.toc) geschrieben, in der Seitenzahl und Überschrift steht. Beim nächsten
Aufruf wird einfach diese .toc-Datei ins Dokument eingebunden und das
Inhaltsverzeichnis ist fertig. Für andere Verzeichnisse gibt es weitere Hilfsdateien.
Ist eine dieser Dateien fehlerhaft, so nützt es nichts, das Hauptdokument zu ändern.
Beheben läßt sich das, in dem man die Hilfsdateien löscht und den Befehl, der
den fehlerhaften Verzeichniseintrag produziert, korrigiert.

Was genau falsch lief, kann man ohne Beispiel nicht sagen.

Grüße
Sirius

[Gast]

diese line14 und line15 etc ist ja nicht nachzuvollziehen,

Schau in der log-Datei oberhalb des Fehlers nach, welche Datei latex gerade verarbeitet (wahrscheinlich die toc- oder lof-Datei). Du kannst erkennen, an der runden Klammer und dem Dateinamen erkennen, dass LaTeX eine Datei öffnet:

(I:\Z-Test\test-utf8.lof

Eine schließende Klammer zeigt an, dass LaTeX mit der Datei fertig ist.

Wenn du die Datei, die zum Fehler gehört, identifiert hast, öffne sie und überprüfe die Zeilen um Zeile 14 herum.

Ulrike Fischer
www.troubleshooting-tex.de

[Father_smu]

Ok vielen Dank,

ich habe nun diese LOF Datei aus dem Pfad in ein anderen Ordner verschoben, habe es geöffnet und line 14 und lin 15 deuteten auf die Einbindung der Bilder.
Nun habe ich das Dokument ohne diese LOF Datei compiliert und siehe da, er hat keinen Error mehr.
Ich dachte nun das LAtex einfach eine neue LOF Datei erzeugt, aber ich sehe keine neue LOF Datei im Pfad.
Seltsam, aber jetzt geht es wieder voran

[Gast]

Die lof-Datei wird erzeugt, wenn du ein \listoffigures + \caption in deinem Dokument hast.

Im Wesentlich gibt es drei Möglichkeiten, wie man an einen kaputte lof-Datei kommen kann:

1. Es ist ein Fehler in einer \caption. -> Muss man finden und korrigieren.

2. Es war mal ein Fehler in einer \caption und in der lof-Datei sind noch "Rückstände" -> es reicht die lof-Datei zu löschen.

3. LaTeX wurde während der Kompilation abgeschossen und die lof-Datei ist unvollständig -> es reicht die lof-Datei zu löschen.

Ulrike Fischer
www.troubleshooting-tex.de