I have to make an .eps file from a large png for publication in PRL. When viewing the .eps in ghostscript/inkscape/illustrator/... it looks fine, but when I build it into a pdf using latex -> DVI -> PDF in TexnicCenter/TexMaker its got a big white block covering the right side.
I generated the latex using LyX export, and have been trying to get it to compile as well as it did in LyX. The figures look perfect when compiled with pdflatex in LyX, so there must be something different with my build profile that's obscuring my figures? Any tips?
EDIT: The minimal example below produces a 'file not found' for the graphic file using pdfLaTeX, and compiles with the figure cutoff on the right when compiled with latex -> DVI -> PDF. Some of my other .eps figures display perfectly when placed in that float, while others don't show at all. However, the .eps all look fine when viewed on their own, and appear to have good bounding boxes in ghostview.
\documentclass{paper}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{float}
\usepackage{amsmath}
\usepackage{graphicx}
\makeatletter
\makeatother
\usepackage{babel}
\begin{document}
\title{Blah}
\author{Bleh}
\begin{abstract}
Abstract goes here.
\end{abstract}
\maketitle
\begin{figure*}[t!]
\begin{centering}
\includegraphics[width=0.75\textwidth]{phasediagramstogether2}
\end{centering}
\caption{This figure is cutoff on the right, with a big white box}%
\label{RDFsandSamples}
\end{figure*}
\end{document}
The error log generated using pdfLaTeX: http://pastebin.com/MRGtUsQJ
The error log for latex -> DVI -> PDF: http://pastebin.com/QA4tVuzY
babel
error I think addingenglish
as a package option, i.e.\usepackage[english]{babel}
, would do the trick. Then try adding\usepackage{epstopdf}
.pdflatex
cannot use EPS files directly, so it has to be converted to PDF. In newer versions of TeX Live at least this happens automatically, but that is perhaps not the case for MikTeX 2.8.epstopdf
does the conversion, but you need to enableshell-escape
I think: tex.stackexchange.com/questions/82699/… (you may need--enable-write18
instead of--shell-escape
)