Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference list generation fails for LaTeX if a space is in the path name (Origin: bugzilla #681209) #4839

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.1.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2012-08-04 19:54:38 +0000, Thomas Guymer wrote:

The reference list for LaTeX documentation fails to be generated if the path contains a space. The following output is given by doxygen:

Can't open perl script "/Users/guymer1/Work/Data/2011-06": No such file or directory
make -f documentation/latex/Makefile
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl refman.pdf
make[1]: *** No rule to make target refman.tex', needed by refman.pdf'. Stop.
make: *** [documentation] Error 2

The correct folder path is "/Users/guymer1/Work/Data/2011-06 TGS/make_streaked_fake_data/documentation" not "/Users/guymer1/Work/Data/2011-06". Note that it truncates the path at the exact place that a space exists.

On 2012-08-05 20:28:59 +0000, Dimitri van Heesch wrote:

Hi Thomas,

This error doesn't seem like something doxygen produces, but rather a script that (amongst others) runs doxygen. If you think it really is a doxygen issue, then please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem.

On 2012-08-07 16:52:03 +0000, Thomas Guymer wrote:

Created attachment 220585
Self contained example

Self contained example

On 2012-08-07 16:54:05 +0000, Thomas Guymer wrote:

So, if I run "doxygen" on the attached files in "/Users/guymer1/Documents/doxygen_test" I get the following output:

citelist:3: warning: expected

tag but found
instead!
citelist:4: warning: unexpected end of comment while looking for a html description title

If I rename the directory to "/Users/guymer1/Documents/doxygen test" and update the doxygen configuration file with the new paths then I get the following output instead:

Can't open perl script "/Users/guymer1/Documents/doxygen": No such file or directory

Thanks

On 2012-09-11 18:52:00 +0000, Thomas Guymer wrote:

(In reply to comment # 1)

Hi Thomas,

This error doesn't seem like something doxygen produces, but rather a script
that (amongst others) runs doxygen. If you think it really is a doxygen issue,
then please attach a self-contained example (source+config file in a tar or
zip) that allows me to reproduce the problem.

So, I have uploaded a self contained example for you, thanks.

On 2012-09-16 13:15:53 +0000, Dimitri van Heesch wrote:

Turns out that bibtex itself does not seem to be able to handle spaces.
The only solution I see is to (temporarily) copy the .bib files to the directory from which bibtex is run, so bibtex can find the files without path.

I'll include this approach in the next subversion update.

On 2012-09-21 08:40:58 +0000, Thomas Guymer wrote:

(In reply to comment # 5)

Turns out that bibtex itself does not seem to be able to handle spaces.
The only solution I see is to (temporarily) copy the .bib files to the
directory from which bibtex is run, so bibtex can find the files without path.

I'll include this approach in the next subversion update.

Thank you for looking into this for me!

I'll look forward to the next subversion update, :)

On 2012-12-26 16:09:23 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.3. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

On 2013-01-14 18:04:25 +0000, Thomas Guymer wrote:

I can confirm that this bug is resolved in version 1.8.3, thank you very much for the bug fix.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.