(Win XP Prof, Miketex 2.3, Lyx-Qt 1.3.2)

Hello,

I have problems inserting floating graphics into my *.lyx-File. I have one graphic, that works. So I tried to copy and paste it within Lyx, then changing the name of the file (to consort-checkliste.eps, 1,1 MB). But when trying to use pdflatex, I get:

pdfTeX warning (ext4): destination with the same identifier (name{figure.1})
 \caption{Consort-Checkliste}

When doing it like described in the Users guide (Insert float, then insert graphic there), I get 4 error messages (see below).

Any ideas?

Thanks

Michael

1.
pdfTeX warning (ext4): destination with the same identifier (name{figure.1})
 ...uf2/_praxis_Diss_lyx_consort-checkliste}}


File: c:/lyx/tmp/lyx_tmpdir1064a02580/lyx_tmpbuf2/_praxis_Diss_lyx_consort-chec


kliste.pdf Graphic file (type pdf)

2.
pdfTeX warning (ext4): destination with the same identifier (name{figure.1})
 ...uf2/_praxis_Diss_lyx_consort-checkliste}}


<c:/lyx/tmp/lyx_tmpdir1064a02580/lyx_tmpbuf2/_praxis_Diss_lyx_consort-checklist


e.pdf, id=111, 597.23125pt x 845.1575pt>

File: c:/lyx/tmp/lyx_tmpdir1064a02580/lyx_tmpbuf2/_praxis_Diss_lyx_consort-chec

kliste.pdf Graphic file (type pdf)

3.
Paragraph ended before [EMAIL PROTECTED] was complete.
 ...uf2/_praxis_Diss_lyx_consort-checkliste}}

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.


4. Argument of [EMAIL PROTECTED] has an extra }. ...uf2/_praxis_Diss_lyx_consort-checkliste}}

I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.

--
http://www.logies.de/ (u. a. _die_ Mailingliste f�r die Dentalbranche)
PGP-key (RSA/IDEA) kommt mit angeforderter Empfangsbest�tigung (return receipt)



Reply via email to