COMPGROUPS.NET | Search | Post Question | Groups | Stream | About | Register

### Text line contains an invalid character

• Follow

I seem to be getting a repeating problem that is driving me nuts. I do
pdflatex of my document and sometimes it stops due to some error on my
part. So I kill the job. I correct the error and run the process
again. Now it just says:

Text line contains an invalid character l.1

I can't seem to get out of this loop. Sometimes it works when I simply

\begin{document}\end{document}

directly after the documentclass, (the behaviour happens both with
article and beamer) and then comment this out.

Any ideas?

Geoff

 0

Geoff <geoffostrin@yahoo.co.uk> wrote:

> I seem to be getting a repeating problem that is driving me nuts. I do
> pdflatex of my document and sometimes it stops due to some error on my
> part. So I kill the job. I correct the error and run the process
> again. Now it just says:
>
> Text line contains an invalid character l.1

Check your .log file in order to get the current filename.
Then open the file in a hex editor and inspect the first line
for unusual characters. In plain TeX and LaTeX usually
the character with code 0 has catcode 9 (invalid).

--
Heiko Oberdiek

 0

Geoff <geoffostrin@yahoo.co.uk> wrote:

> I seem to be getting a repeating problem that is driving me nuts. I do
> pdflatex of my document and sometimes it stops due to some error on my
> part. So I kill the job. I correct the error and run the process
> again. Now it just says:
>
> Text line contains an invalid character l.1

Check your .log file in order to get the current filename.
Then open the file in a hex editor and inspect the first line
for unusual characters. The catcode for invalid is 15.
LaTeX uses this catcode for most of the control
characters:
0x00 (0) -- 0x08 (8),
0x0B (11),
0x0E (14) -- 0x1F (31),
0x7F (127)

(PS: please ignore the previous cancelled posting)
--
Heiko Oberdiek

 0

On 01/09/10 20:52, Geoff wrote:
> I seem to be getting a repeating problem that is driving me nuts. I do
> pdflatex of my document and sometimes it stops due to some error on my
> part. So I kill the job. I correct the error and run the process
> again. Now it just says:
>
> Text line contains an invalid character l.1
>
> I can't seem to get out of this loop. Sometimes it works when I simply
>
> \begin{document}\end{document}
>
> directly after the documentclass, (the behaviour happens both with
> article and beamer) and then comment this out.
>
> Any ideas?

Open the file in an editor that shows you EVERY byte in the file, for
good or bad (eg Emacs). Some editors hide characters they consider you
ought not see, without realising that this prevents debugging.

///Peter

 0

At Wed, 1 Sep 2010 12:52:07 -0700 (PDT) Geoff <geoffostrin@yahoo.co.uk> wrote:

>
> I seem to be getting a repeating problem that is driving me nuts. I do
> pdflatex of my document and sometimes it stops due to some error on my
> part. So I kill the job. I correct the error and run the process
> again. Now it just says:
>
> Text line contains an invalid character l.1
>
> I can't seem to get out of this loop. Sometimes it works when I simply
>
> \begin{document}\end{document}
>
> directly after the documentclass, (the behaviour happens both with
> article and beamer) and then comment this out.
>
> Any ideas?

Are you using a UNICODE editor?  Or (shudder) MS-Word as a text editor?

TeX/LaTeX really only handle 7-bit ASCII characters.  Maybe newer
versions of TeX/LaTeX might handle selected UNICODE characters.

>
> Geoff
>

--
Robert Heller             -- 978-544-6933
http://www.deepsoft.com/  -- Binaries for Linux and MS-Windows


 0

Am Wed, 1 Sep 2010 12:52:07 -0700 (PDT) schrieb Geoff:

> I seem to be getting a repeating problem that is driving me nuts. I do
> pdflatex of my document and sometimes it stops due to some error on my
> part. So I kill the job. I correct the error and run the process
> again. Now it just says:
>
> Text line contains an invalid character l.1

How do you "kill the job"? Are you using the TeX input "x" or are
you closing some window or using ctrl+q or ctrl+z?

--
Ulrike Fischer

 0

5 Replies
2443 Views

Similiar Articles:

7/20/2012 2:43:58 PM