PhilipPirrip <pip <at> net.hr> writes:
>
> On 06/15/2016 08:46 AM, Nikola Ivan Leder wrote:
> > Hi,
> > The subject pretty much sums it up. As
> > suggested in previous thread I've upgraded
> > to lyx 2.2.
> > The new version would not produce a result
> > when exporting to PDF because of unknown
> > characters. I've tracked this to Croatian
> > diacritics from the references bib file.
>
> Nikola,
> You shouldn't, in general,have any non-ASCII characters in your bib
> files,it's because of bibtex limitations. You could try with bibtex8
> (Document settings > Bibliography > Processor), or biblatex (with some
> additional work, http://wiki.lyx.org/BibTeX/Biblatex).
> It could be though that your bib file encoding and your lyx document
> encoding don't match: what's in your Document settings > Language >
> Encoding?
>
> To help you further, we'll need a minimal LyX file together with a bib
> database showing the error.
>
>
Okay, let me just say that I'm a doctor and not a programmer (just an IT
enthusiast) so I may be off on some of my answers here... what I
noticed that the čć and similar are converted to gibberish in bib file
key and lyx could not read it... it may indeed be problem due to bib
encoding or jabref new version... don't think that lyx is really the
problem here.
Now that I've manually removed the croatian diacritics from the
Bibtexkey I get a load of new errors complaining of undefined fields
like so:
\newblock Available from: \url
{http://stacks.iop.org/0031-
9155/48/i=16/a=...
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
This is due to DOI and URL fields in bib file, because if I erase them
no more errors. I can however ignore this error (warning?) and get a
perfect result.
So, apologies to LyX powers that be, I guess I was to blame here,
probably some encoding change in bib file after upgrading other software
that I didn't notice ... shouldn't use those characters in key fields
anyhow... :)
