General ⇒ LaTeX => PS => PDF

[localghost]

I requested the log file, not the profile itself. So, please post that file in the attachment.

The epsfig package is obsolete hence you can omit it completely. Since you are using the graphicx package, modify your code as follows.

Code: Select all

\begin{figure}[!ht]
  \centering
  \caption{Example}\label{fig:example}
  \includegraphics[height=8cm,width=10cm]{filename}
\end{figure}

The suffix .eps can also be omitted. The graphicx package detects on its own which compiler (latex or pdflatex) is processing the source code.

[jesu]

Hello,
Indeed I used your tco file and looked into it physically but I could not see the paths. Now, when I compile a program using the Prosper package, I find that the output of my slides (presentation) is cropped half-way; in other words, half the image appears to the right hand side of the pdf viewer, and the left is a blank. Could you kindly amplify on this so that the output is normal. THe best alternative is to put a latex - ps-pdf as another default like the good old days or provide absolutely precise instructions for uninformed non-geeks like myself so that we can do this by ourselves.
Chris

[localghost]

[…] I would still like to know, just for the sake of the knowledge, how to create the LaTeX => PS => PDF profile for myself. It would also save me having to edit the .tco profile on new systems. […]

This profile is a relic from times where TeXnicCenter was able to detect the path to the required executables of MiKTeX on its own with having MiKTeX and Ghostscript installed before TeXnicCenter. Since MiKTeX 2.5, this is no more possible. I once exported this profile and so I'm able to reimport it every time I need it with adapting the paths. Perhaps you refer to the Ghostscript Documentation to get familiar with all its command line parameters.

Hello,
Indeed I used your tco file and looked into it physically but I could not see the paths. […]

Then you didn't look carefully enough. The paths should be displayed as seen in the attached screen shots. Maybe you can tell me how you looked at the profile. I hope not with a normal text editor. The formatting code of the profile is XML.

[…] Now, when I compile a program using the Prosper package, I find that the output of my slides (presentation) is cropped half-way; in other words, half the image appears to the right hand side of the pdf viewer, and the left is a blank. Could you kindly amplify on this so that the output is normal. […]

The prosper class (and the additional bug fixing package HA-prosper) is obsolete. You better use the powerdot class, which represents a merge and enhancement. If all that doesn't help, please provide a minimal working example (MWE) of your presentation which exactly shows the undesired behaviour. So we would be able to see what's going wrong and maybe can do some corrections.

[…] THe best alternative is to put a latex - ps-pdf as another default like the good old days or provide absolutely precise instructions for uninformed non-geeks like myself so that we can do this by ourselves. […]

I can't see how I could be more precisely than in another thread of this forum [1]. I introduced another (more complicated) build profile there and described in detail how to import it into TeXnicCenter and adapt the paths. Perhaps this will help. I can only emphasise to be very careful in adapting all the paths to the required executables. The profile works definitely correct, provided that all settings are made correctly. I should mention to omit -s personal.ist -g in the command line arguments of makeindex. The personal.ist is an index style file I build on my own and parameter -g is for German ordering. But this doesn't really affect a successful building process.

I do not consider myself a geek. Perhaps I only use my gray matter to get things work. In your case it seems to be some kind of PEBCAM (problem exists between chair and monitor). More than thousand other users seemed to be able to get things work (The profile was lost with the update of the forum software like all other attachments. Before that it was downloaded approximately 1500 times, which says nothing about how many were really able to use it.). So, follow the instructions in the above mentioned thread and try your best.


[1] Forum thread: Problems with pstricks :S

[tona]

I've tried this but wasnt work with me (I mean the graph)

Today I've found very simple good qulity way to have pdf file from ps file. I write this here so can every one benefit from it (esp beginner as me!)

The way as following:

first get ur file in ps file, then open it using GSview

From FILE menu in GSview choose "convert" and make sure that

Device >>> pdfwrite
Resoultion >> 600 or 720 as you want

and choose the pages you want to convert or all pages
and then click OK

then write the name of the output file you would like, for example
output.pdf

and save it

Best wishes

[localghost]

I've tried this but wasnt work with me (I mean the graph) [...]

I wonder what I shall think of that. What for heaven's sake is so difficult in adapting all the paths that you can't make that profile work? Many other users made it and so you can, too. In principal this is only an extension to the build profile "LaTeX => PS". The paths for the MiKTeX executables should be no big hurdle. So, find the path were Ghostscript (gswin32c.exe) is located (hopefully you remember were you installed it), insert it as shown in the pictures and everything will work fine. The command line parameters can be kept as they are (perhaps with exception of the paper size). The Ghostscript documentation could be very helpful. That's all I can offer for the moment.

Supplement:
OK then. One additional hint for all who have insurmountable difficulties with this profile. Our German TeX users group (DANTE) offers on its TeXnik website a profile that uses ps2pdf for this job [1]. You can find it at the very bottom of the page. But this profile doesn't release from path adaptation.

[1] /TeXnik/gui/TeXnikCenter


Best regards and good luck
Thorsten¹

[letianrong]

actually for me there was one small modification i had to make to the imported profile besides specifying directory paths to make it working. it is related to ghostscript configuration in the postprocessor tab, for the arguments i removed "%pm" in front of the "-sPAPERSIZE=a4 -dSAFER -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile="%bm.pdf" -c save pop -f "%bm.ps". that's all and now it works fine.

cheers,

lee

[localghost]

actually for me there was one small modification i had to make to the imported profile besides specifying directory paths to make it working. it is related to ghostscript configuration in the postprocessor tab, for the arguments i removed "%pm" in front of the "-sPAPERSIZE=a4 -dSAFER -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile="%bm.pdf" -c save pop -f "%bm.ps". that's all and now it works fine.

cheers,

lee

I don't know where this additional "%pm" comes from, but this is exactly the required sequence of command line parameters for Ghostscript.

Code: Select all

-sPAPERSIZE=a4 -dSAFER -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile="%bm.pdf" -c save pop -f "%bm.ps"

In my exported build profile I couldn't find that "%pm". And as I currently see, it comes from the profile that tona provided, who made a mess of my original profile. So this can't be usable and you have to take the version I provided in an earlier post of this thread. This makes me emphasise again that there is nothing to add in the profile I provided. It's just a matter of path adaptation for the executables. I thought that I already described that in detail earlier.

[Tig]

Thanks a lot, it worked perfectly for me (after changing the paths, obviously)

[Bozack]

Sorry to say it - but I'm having trouble with using this profile too.

I've changed the paths to the correct ones, and it compiles fine. But there is one problem (actually the reason I tried to use this profile from the start, instead of the "LaTeX => PDF"-one I normally use): When I try to make drawings with XY-pic, none of the lines shows up - only the letters and bullets. When I compile the following code I only get four dots:

Code: Select all

\documentclass[a4paper,dvips,10pt]{article}
\usepackage[latin1]{inputenc}
\usepackage[danish]{babel}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb}
\usepackage[pdftex]{color,graphicx}
\usepackage[all]{xy}
\begin{document}
\xymatrix{
	{\bullet} \ar@{--}[d]\ar@{=}[dr]\ar@{-}[r]
	& {\bullet} \ar@{.}[d] \\
	{\bullet} & {\bullet} \ar[l] }
\end{document}

There should be lots of lines between the dots!

Does anyone have any idea what's happening on my system?

[Stefan Kottwitz]

Hi Bozack,

if I compile your code with pdflatex I get just four dots too. But if I remove [pdftex] (option of color and graphicx), compile with latex to dvi and convert to ps by dvips I also get the lines.

Stefan