After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 670487 - It is not mandatory to use EPS images for LaTeX output
It is not mandatory to use EPS images for LaTeX output
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: documentation
1.7.6.1
Other Windows
: Normal enhancement
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks:
 
 
Reported: 2012-02-20 22:21 UTC by Stefan
Modified: 2018-07-30 10:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stefan 2012-02-20 22:21:58 UTC 
The documentation tells us, that one needs to use EPS files as images for LaTeX output.
Using EPS files results in a much longer time to be used to generate the PDF file from LaTeX compared to using PNG files for instance.

I am using the latest MiKTeX release and PNG images without problems.

As an example see the UltraDefrag project at SourceForge ( http://ultradefrag.svn.sourceforge.net/viewvc/ultradefrag/release/doc/html/handbook/ )

Would it be possible to mention this in the documentation?

--
Stefan
Comment 1 milasudril 2014-10-08 10:02:37 UTC 
It depends. The general rule is

  * pdflatex does not accept eps (it needs pdf or png)
  * latex require eps

This sounds more like a bug in docs rather than an enhancement.
Comment 2 André Klapper 2018-07-30 10:11:32 UTC 
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to 

   https://github.com/doxygen/doxygen/issues

All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github.

Hence I am closing this GNOME Bugzilla ticket.
Please use the corresponding ticket in Github instead. Thanks a lot!