|
Home
News
Citegeist
|
Browse Groups
Search Groups
Journals
|
FAQs
Howto
Discussion
|
![]() |
![]() |
![]() |
![]() |
Hello This article: "doi:10.1016/j.solmat.2006.09.003" (on sciencedirect) has a title including"efficiency—An overview", this however turns into "efficiency—An overview" in biblography.bib (and mainfile.bbl) after exporting from CiteULike.
After compiling tex file the error message states: "! LaTeX Error: Command `\texteuro unavailable in encoding T1"
My uneducated guess is this hyphen needs utf-8, but there are, as far as I know many bibstyle's that dont support utf-8. So i seems to me that it is unfortunate that the plugin(s) creates a utf-8 format for the bibtex file exported from CiteULike.
Is there a solution to this or should this be regarded as a bug?
btw:I'm using TeXnicCenter (wich not support unicode to my knowledge) on XP if that matters, but the problem seems to be that many(?) bibstyles (or bibtex?) cannot handle utf-8.
Regards Lars
Posted by LarsOlav on 2009-01-07 13:57:47.
3 replies. Login or join this group to post to this thread.
BibTeX only theoretically supports (7-bit) ASCII though it sometimes seems to work "a bit" in a semi-unpredictable way. For example, bibtex/pdflatex (which we use to generate our PDF export) seems to work fine in this case.
Converting all chars (e.g., that em-dash) to LaTeX/ASCII is a Sisyphean task :-( If only I could find a generic utf2latex program somewhere on the interweb.
I'm afraid I don't have any quick fix for this.
Posted by thegoose on 2009-01-07 18:02:40.
Thank you for your clearing comment, thegoose. I redraw my suggestion that the plugin(s) creating a utf-8 format is unfortunate. I realize the wise thing is (for me at least, since this is rare problem) just to edit the Bibtex entry via citeulike, it took me be about 2.15 sec.
Posted by LarsOlav on 2009-01-08 11:20:23.