https://bugs.kde.org/show_bug.cgi?id=305713
--- Comment #17 from German <germanzo...@gmail.com> --- Now I understand it's not a bug, and can also guess why dvips solves the problem. Including or not ps parsing in dvi frontend is a developers decision. And I'm not a developer. So I'll argue from user point of view. Philosophically, a dvi parser should not parse ps. In the other side, there is an integration issue with kile. tikz is becoming an usual package in latex. Not so long ago, tikz came with a warning telling it should be compiled with pdflatex (I read that in todonotes documentation), and that was a pain in systems which didn't support backward search of pdf. I guess that is why someone implemented that mixture of ps and dvi. One can blame tikz developers, one can go with mixing dvi and ps, or, as kile + okular does manage backward search of pdf, one can try to find a compromise solution. Actually I'm doing that by hand: depending on which machine I'm using, I use kile|pdflatex|okular, or texnikcenter|latex|yap. I wander if it is a good idea or not making kile to detect that tikz issue and warn the user or even change it automatically. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
