The link you provided is not the URL of a bibtex file. It's a regular html page that has a download link. But it's not the .bib itself. Here is what I see when I open the link.



You need to use the download link with BibBase, since that download link is the actual URL of your bibtex file. That's what I did in the following link and it seems to work just fine:

http://bibbase.org/show?bib=https://dl.dropboxuser...

Levente,

Thanks for the bug report. I found a different bug and fixed it. The link now seems to work.

Mendeley is not well supported at this point (as you can tell), but I'm working on a new implementation right now that should be more robust.

-- Christian

Walter: Thanks for reporting this and my apologies for this bug. Given your report I was now able to find the real problem (some permissions had to be changed on the server). Your page now seems to be working again.

BTW, when you are embedding this page into your homepage then this problem might go away all by itself, since you are probably specifying the character coding as utf-8 in your homepage already. This is set in the head of the html. BibBase pages don't have a head, so that they can be embedded easily. But this headlessness also means that I can't set the encoding in the bibbase page itself.

Eliseo: it looks fine to me (see screenshot below). What most probably is happening is that you are nor using unicode (utf-8) as your character encoding in your browser, or the font you are using as your default fault in your browser simply doesn't support utf-8.



In Chrome you can change the font and encoding in the advanced settings:

Stéphane, thanks for the pointer and the clarification. That is indeed too bad that Mendeley treats some pdfs as copyrighted when in fact they are not.

You are very welcome. Thanks for being an early adopter despite the hick-ups.

Hi Ricky,

I don't know what the problem was, but I cleared the cache and now it seems to be back to normal. Please verify that it looks OK.

One thing you can try if it happens again is to touch/edit your bib file in order to enforce a cache refresh. But if it happens, please still let me know. Maybe it's indicative of a different problem I'm not aware of. You are the first user to report this problem though.

-- Christian