11

I have a problem with one of my bibtex items and I'm scratching my head to figure out what is wrong. I've narrowed it down to the specific reference, and in partiuclar the specific URL latex is having trouble compiling. It is the following:

    url = {http://www.opengroup.org/jericho/Jericho%20Forum%20Identity%20Commandments%20v1.0.pdf},

Usually this error occurs due to unbalanced paranthesis, but that is not the case here. What is problematic about this particular URL?

0

3 Answers 3

13

Load the url package in the preamble of your document:

\usepackage{url}
2
  • This works, but it changes the formatting of URLs in the bibliography, which isn't necessarily wanted.
    – naught101
    Sep 12, 2013 at 4:12
  • 2
    @naught101 usually URLs are typeset in monospaced font. To change the font with the package loaded, use \urlstyle{same} or some other of the available options. Sep 12, 2013 at 4:20
4

Is it that % is the Tex comment character? Try putting backslashes before each %

4

I know this is an old question, but I recently encountered a similar problem. After fixing errors in the .bib document (such as adding backslashes to the %) remember to delete the .bbl document first and recompile.

The way I add urls to bibtex is thus:

@misc{fenwayHouse,
  title={{Fenway House}},
  howpublished="\url{http://web.mit.edu/fenwayhouse}"
}

Made a stupid mistake by doing

howpublished="\url={http://web.mit.edu/fenwayhouse}"

instead (notice the extra misplaced =).

After finding that out and simply recompiling, I was scratching my head that the error still existed.

So this is an obvious fix that I neglected to notice, delete the .bbl file which is generated the first time you reference something in the .bib, this does not "update" fully when you change your an entry in .bib that has already been carried over to .bbl, so that extra = was still causing errors.

1
  • Well, this might be a solution. Could a please elaborate a little more on this, perhaps with some example?
    – user31729
    Jul 23, 2014 at 20:45

You must log in to answer this question.