I've been trying to get dot2tex working on my MacBook Pro running Mac
OS X 10.5.5. I've installed the packages and dependencies but I've
been having trouble getting it to work properly using the \input{}
command. I ran the test_buildexamples.py in the test directory to
diagnose the problem and the test fails whilst trying to process the
balls.dot file. The problem appears to be during the ps2eps conversion
it can't find the balls.ps file. I think this stems from the fact that
the latex command in my TeX distribution is actually pdfeTeX and so
only a .pdf is generated rather than a .ps. Is there anything I can do
to get dot2tex to skip the ps conversion phase since pdfeTeX should
have already done that or does dot2tex only work with ps producing
versions of LaTeX?
Any suggestions or tips would be most welcome.
Thanks,
Alastair
On Wed, Oct 1, 2008 at 5:28 PM, Alastair <alastair.and...@gmail.com> wrote:
> Hi,
> I've been trying to get dot2tex working on my MacBook Pro running Mac > OS X 10.5.5. I've installed the packages and dependencies but I've > been having trouble getting it to work properly using the \input{} > command. I ran the test_buildexamples.py in the test directory to > diagnose the problem and the test fails whilst trying to process the > balls.dot file. The problem appears to be during the ps2eps conversion > it can't find the balls.ps file. I think this stems from the fact that > the latex command in my TeX distribution is actually pdfeTeX and so > only a .pdf is generated rather than a .ps. Is there anything I can do > to get dot2tex to skip the ps conversion phase since pdfeTeX should > have already done that or does dot2tex only work with ps producing > versions of LaTeX?
> Any suggestions or tips would be most welcome. > Thanks, > Alastair
Hi Alastair,
The LaTeX code generated by dot2tex should work fine with pdf(e)tex unless you use the pstricks output format. The pgf(default) and TikZ output format generate code that can be compiled directly with pdftex.
I don't remember why I have used ps2eps in the test_buildexamples.py file. Probably because I wanted to use the same code to build the pstricks examples.
If you run the following commands you should be able to get some hints in the generated log files:
where graph.dot is located in the same directory and just contains
digraph G{
Hello->World
}
I use a program called TeXShop to edit and compile my .tex files and
when I try to compile this file it returns the following errors:
Opening dot2tex stream dot-dot2tex-fig1.dotsh: dot2tex: command not
found
Package dot2texi Warning: Conversion of dot-dot2tex-fig1.dot failed..
Package dot2texi Warning: Please convert dot-dot2tex-fig1.dot
manually.
However if I open a terminal and type:
$ dot2tex
then it finds the command, the problem is as if the internal shell
process spawned to automatically run dot2tex is using a different path
from the normal user terminal.
In relation to your other advice about the running dot2tex then
pdflatex, it worked fine, there were no problems. I think it was just
as part of the test suite that problems were occurring.
I did notice in the log file there was a warning about using a
deprecated command.
Package tikz Warning: Snakes have been superseded by decorations.
Please use th
e decoration libraries instead of the snakes library on input line 14.
Thanks for all you help,
Alastair
On Oct 1, 6:51 pm, "Kjell Magne Fauske" <kjel...@gmail.com> wrote:
> On Wed, Oct 1, 2008 at 5:28 PM, Alastair <alastair.and...@gmail.com> wrote:
> > Hi,
> > I've been trying to get dot2tex working on my MacBook Pro running Mac
> > OS X 10.5.5. I've installed the packages and dependencies but I've
> > been having trouble getting it to work properly using the \input{}
> > command. I ran the test_buildexamples.py in the test directory to
> > diagnose the problem and the test fails whilst trying to process the
> > balls.dot file. The problem appears to be during the ps2eps conversion
> > it can't find the balls.ps file. I think this stems from the fact that
> > the latex command in my TeX distribution is actually pdfeTeX and so
> > only a .pdf is generated rather than a .ps. Is there anything I can do
> > to get dot2tex to skip the ps conversion phase since pdfeTeX should
> > have already done that or does dot2tex only work with ps producing
> > versions of LaTeX?
> > Any suggestions or tips would be most welcome.
> > Thanks,
> > Alastair
> Hi Alastair,
> The LaTeX code generated by dot2tex should work fine with pdf(e)tex
> unless you use the pstricks output format. The pgf(default) and TikZ
> output format generate code that can be compiled directly with pdftex.
> I don't remember why I have used ps2eps in the test_buildexamples.py
> file. Probably because I wanted to use the same code to build the
> pstricks examples.
> If you run the following commands you should be able to get some hints
> in the generated log files:
With only \begin{dot2tex} \input{graph.dot} \end{dot2tex} I get an error. It seems to be an issue with the TeX parser when a \ follows immediately after \begin{dot2tex}. I should add a note about this in the documentation...
If this does not help, you could try to add:
\usepackage[debug]{dot2texi}
That will generate at dot2tex.log file with more information.
> However if I open a terminal and type: > $ dot2tex
> then it finds the command, the problem is as if the internal shell > process spawned to automatically run dot2tex is using a different path > from the normal user terminal.
> In relation to your other advice about the running dot2tex then > pdflatex, it worked fine, there were no problems. I think it was just > as part of the test suite that problems were occurring.
> I did notice in the log file there was a warning about using a > deprecated command.
> Package tikz Warning: Snakes have been superseded by decorations. > Please use th > e decoration libraries instead of the snakes library on input line 14.
> Thanks for all you help, > Alastair
> On Oct 1, 6:51 pm, "Kjell Magne Fauske" <kjel...@gmail.com> wrote: >> On Wed, Oct 1, 2008 at 5:28 PM, Alastair <alastair.and...@gmail.com> wrote:
>> > Hi,
>> > I've been trying to get dot2tex working on my MacBook Pro running Mac >> > OS X 10.5.5. I've installed the packages and dependencies but I've >> > been having trouble getting it to work properly using the \input{} >> > command. I ran the test_buildexamples.py in the test directory to >> > diagnose the problem and the test fails whilst trying to process the >> > balls.dot file. The problem appears to be during the ps2eps conversion >> > it can't find the balls.ps file. I think this stems from the fact that >> > the latex command in my TeX distribution is actually pdfeTeX and so >> > only a .pdf is generated rather than a .ps. Is there anything I can do >> > to get dot2tex to skip the ps conversion phase since pdfeTeX should >> > have already done that or does dot2tex only work with ps producing >> > versions of LaTeX?
>> > Any suggestions or tips would be most welcome. >> > Thanks, >> > Alastair
>> Hi Alastair,
>> The LaTeX code generated by dot2tex should work fine with pdf(e)tex >> unless you use the pstricks output format. The pgf(default) and TikZ >> output format generate code that can be compiled directly with pdftex.
>> I don't remember why I have used ps2eps in the test_buildexamples.py >> file. Probably because I wanted to use the same code to build the >> pstricks examples.
>> If you run the following commands you should be able to get some hints >> in the generated log files:
On Thu, Oct 2, 2008 at 4:43 PM, Kjell Magne Fauske <kjel...@gmail.com> wrote:
> If this does not help, you could try to add:
> \usepackage[debug]{dot2texi}
> That will generate at dot2tex.log file with more information.
If pdftex can't find dot2tex this will of course not help. The log file generated by latex could give some hints. Under MikTeX the following command is used:
>> Package tikz Warning: Snakes have been superseded by decorations. >> Please use th >> e decoration libraries instead of the snakes library on input line 14.
Just ignore the warnings. The balls.dot example has not been updated to reflect the syntax changes introduced in PGF 2.0.
> On Thu, Oct 2, 2008 at 4:43 PM, Kjell Magne Fauske <kjel...@gmail.com> wrote:
> > If this does not help, you could try to add:
> > \usepackage[debug]{dot2texi}
> > That will generate at dot2tex.log file with more information.
> If pdftex can't find dot2tex this will of course not help. The log
> file generated by latex could give some hints. Under MikTeX the
> following command is used:
> >> Package tikz Warning: Snakes have been superseded by decorations.
> >> Please use th
> >> e decoration libraries instead of the snakes library on input line 14.
> Just ignore the warnings. The balls.dot example has not been updated
> to reflect the syntax changes introduced in PGF 2.0.
The example-dot2tex-fig1.dot just contains this: \input{graph.dot} As far as I can see there is no dot2tex.log generated only an example.log file which I sent you the excerpt from last time.
> On Thu, Oct 2, 2008 at 5:50 PM, Alastair <alastair.and...@gmail.com> > wrote:
> > After setting the debug argument and using \begin{dot2tex}[] the > > process still fails. > > Looking at the log file the command used shows up as:
On Thu, Oct 2, 2008 at 6:31 PM, Alastair Neil Andrew
<alastair.and...@gmail.com> wrote: > Hi, > The example-dot2tex-fig1.dot just contains this: > \input{graph.dot} > As far as I can see there is no dot2tex.log generated only an example.log > file which I sent you the excerpt from last time. > Thanks, > Alastair
I am sorry. It seems that you initial theory that the shell process spawned by latex is set up differently than your ordinary command line shell is correct. I have experienced similar issues on web servers. I am not familiar with OS-X so unfortunately I don't know how to solve it.
> On Thu, Oct 2, 2008 at 6:31 PM, Alastair Neil Andrew
> <alastair.and...@gmail.com> wrote:
> > Hi,
> > The example-dot2tex-fig1.dot just contains this:
> > \input{graph.dot}
> > As far as I can see there is no dot2tex.log generated only an example.log
> > file which I sent you the excerpt from last time.
> > Thanks,
> > Alastair
> I am sorry. It seems that you initial theory that the shell
> process spawned by latex is set up differently than your ordinary
> command line shell is correct. I have experienced similar issues on
> web servers. I am not familiar with OS-X so unfortunately I don't know
> how to solve it.
It was indeed a path issue. I solved it by including a link from my
dot2tex binary into the bin directory on the path of pdflatex. Perhaps
not the most elegant way but it works.
On Oct 3, 12:18 am, Alastair <alastair.and...@gmail.com> wrote:
> Not to worry, I'll consult the TeXShop forums and if I find a solution
> I'll post it up here.
> Thanks for all your help,
> Alastair
> On Oct 2, 5:49 pm, "Kjell Magne Fauske" <kjel...@gmail.com> wrote:
> > On Thu, Oct 2, 2008 at 6:31 PM, Alastair Neil Andrew
> > <alastair.and...@gmail.com> wrote:
> > > Hi,
> > > The example-dot2tex-fig1.dot just contains this:
> > > \input{graph.dot}
> > > As far as I can see there is no dot2tex.log generated only an example.log
> > > file which I sent you the excerpt from last time.
> > > Thanks,
> > > Alastair
> > I am sorry. It seems that you initial theory that the shell
> > process spawned by latex is set up differently than your ordinary
> > command line shell is correct. I have experienced similar issues on
> > web servers. I am not familiar with OS-X so unfortunately I don't know
> > how to solve it.
On Fri, Oct 3, 2008 at 4:08 PM, Alastair <alastair.and...@gmail.com> wrote:
> It was indeed a path issue. I solved it by including a link from my > dot2tex binary into the bin directory on the path of pdflatex. Perhaps > not the most elegant way but it works.
I am glad to hear that you found a solution, and thanks for posting it here!
