TeX Failed on kompyuterra_kompyuterra_677_jurnal_kompyuterra_n_9_ot_06_marta_2007_goda

[GoogleCodeExporter]

2007-03-14 09:40:52,316 DEBUG    Downloading
'http://s3.amazonaws.com/fb2pdf/9123a1b04f955967436c2329fccef564.fb2' to file '
kompyuterra_kompyuterra_677_jurnal_kompyuterra_n_9_ot_06_marta_2007_goda.fb2'.

Original issue reported on code.google.com by kroko...@gmail.com on 14 Mar 2007 at 5:05

[GoogleCodeExporter]

<./encbvJ9Tk.jpg, id=1254, 130.60843pt x 129.73772pt> <use ./encbvJ9Tk.jpg>
Runaway argument?
{\normalfont \large \bfseries }{\write \@auxout {\string \@writefile \ETC.
! Paragraph ended before \@sect was complete.
<to be read again> 
                   \par 
l.1548 

All I see at this line is:

\vspace{12pt}

Hmm. Looks pretty normal to me. George, could you please take a look?

Original comment by kroko...@gmail.com on 15 Mar 2007 at 2:29

[GoogleCodeExporter]

This is awesome! Just look at this:

\subsection{\ \begin{center}
\includegraphics{./encsNP2og.jpg}
\end{center}
}

I don't think this is allowed. Researching.

Original comment by abc...@yopmail.com on 15 Mar 2007 at 5:11

[GoogleCodeExporter]

\includegraphics{} is definitely a problem.

Original comment by abc...@yopmail.com on 15 Mar 2007 at 5:52

[GoogleCodeExporter]

I guess we should ignore it in section title, like we do for hyperlinks.

Original comment by kroko...@gmail.com on 15 Mar 2007 at 6:04

[GoogleCodeExporter]

It is not a pretty solution. Hyperlink is one thing, but the image (in this 
case it is some diagram)—the content 
might not make any sense if we removed the image.

Original comment by abc...@yopmail.com on 15 Mar 2007 at 7:10

[GoogleCodeExporter]

Can we put it separately, and replace it with hyperlink?
Or perhaps put some placeholder [IMAGE] or somy unicode glyph....

Just throwing some ideas.

Original comment by kroko...@gmail.com on 15 Mar 2007 at 7:57

[GoogleCodeExporter]

Slightly on a tangent but we should probably come up with a generic way of 
warning the user that their content 
was crippled in a certain way in order to successfully finish the task. And if 
we could give them some specifics, 
they might even be able to edit away the problem and regenerate the book.

Original comment by abc...@yopmail.com on 15 Mar 2007 at 8:25

[GoogleCodeExporter]

We need workaround for this ASAP. I see in log users trying to convert this file
again and again. This is popular magazine.

Original comment by kroko...@gmail.com on 18 Mar 2007 at 12:16

[GoogleCodeExporter]

workaround commited.

Original comment by kroko...@gmail.com on 22 Mar 2007 at 3:46