Grant Jacobs wrote:
I have a suspicion that the software I used to gather the references
doesn't know" the LaTeX encodings for the umlauts, etc. and just left
them in their original UniCode.
Ah ... I assumed your bibtex files initially came from BibDesk. Maybe
it's time to switch to a referen
Since writing below I have found a work-around, which I hope will
continue working on the biblio files:
In BibDesk, convert the bibtex database into bibtex. This seems a
little daft at first, but I picked this up on reading that on
importing and exporting BibDesk converts umlauts, etc. into
Make sure you have 'Unicode to TeX Conversion' enabled in BibDesk's
'Files' Preferences !!!
HTH,
Konrad
Grant Jacobs wrote:
One thing that bothers me about this being a BibTeX issue, is that
BibDesk writes these characters to RTF just fine. (It would tempt me to
think that there might a work-around that gets this directly from
BibDesk, avoiding BibTex.)
0) You have not understood the concept be
Thanks for explaining this. Its a damn nuisance I have admit, as I've
spend a long time trying to resolve this when I have little time to
spare really.
I thought I was starting a new thread: I set a new subject line. Is
there some other thing I am supposed to do to make that happen?? I'm
no
Jürgen Spitzmüller wrote:
> You need to use another encoding for the bib file, such as latin1, and
> insert the non-supported characters by means of the respective macros.
Also look here for some further information:
http://wiki.lyx.org/BibTeX/Tips#toc1
Jürgen
Grant Jacobs wrote:
> Having *finally* managed to persuade LyX to generate bibliographies
> at all, I now find that LyX seemingly cannot handle characters with
> diacritic marks (i.e. UniCode) in .bib files when exporting them to
> PDF, etc. Unfortunately this really has to work for me as it will b
Having *finally* managed to persuade LyX to generate bibliographies
at all, I now find that LyX seemingly cannot handle characters with
diacritic marks (i.e. UniCode) in .bib files when exporting them to
PDF, etc. Unfortunately this really has to work for me as it will be
the case with a very
