Oh! That is a good point. There is no pdf generated when I run that build. It works (with errors with the figures) when I run LaTeX => PDF and works fine when I run LaTeX => PS => PDF. Should it work okay if redo the changes I did to LaTeX=>PDF to LaTeX=>PS=>PDF?
Please note the extra " around the first path. I have information that these might be neccessary if you have spaces in the pathname. It may be the same thing for all others paths.
Regards,
Benjamin, thanks for writing the document. I just figured out what my problem is. It was not the quotation marks, but that suggestion did lead me to figure out what the problem was. It seems that some part of the synctex procedure does not like file names with spaces in them. I had been trying to test synctex with a tex file someone had given me that had a space in its name. I took out the space and suddenly synctex started working.
Sorry, to lead you guys astray with this -- the thing that confused me was that TeXnicCenter produced the pdf without any problem with the space in the name and the output window looked exactly the same with the synctex command line option -- just no pdf was produced. I didn't expect this kind of failure mode for the file name being the problem.
Sorry to interject on this thread, but just wanted to say thanks to the tutorial writer. The tutorial for me was correct, the issue i was having was not restarting TXC. Its great to be able to jump between TXC and Sumatra. Much appreciated folks
I advice you to use Texniccenter 2, cause it has full unicode support (this is also the default inputencoding). If you don't want to re-encode your files and stick with latin1, just change it in the preferences.
Best regards
Johannes
The smart way: Calm down and take a deep breath, read posts and provided links attentively, try to understand and ask if necessary.