Manoj Rajagopalan wrote:
I've discovered problems with bibtex parsing at LyX startup if the
abstract field contains unicode characters: the failure is soft (I see a
message on stderr) and the document is loaded but most of the entries in
the bibtex database associated with the document are
Manoj Rajagopalan wrote:
> I've discovered problems with bibtex parsing at LyX startup if the
> abstract field contains unicode characters: the failure is soft (I see a
> message on stderr) and the document is loaded but most of the entries in
> the bibtex database associated with the document
I've discovered problems with bibtex parsing at LyX startup if the abstract
field contains unicode characters: the failure is soft (I see a message on
stderr) and the document is loaded but most of the entries in the bibtex
database associated with the document are not available during
I've discovered problems with bibtex parsing at LyX startup if the abstract
field contains unicode characters: the failure is soft (I see a message on
stderr) and the document is loaded but most of the entries in the bibtex
database associated with the document are not available during
Guenter Milde wrote:
should be adressed in a generic way as well (not only iconv but any helper
application) (as this can happen also with unknown glyphs).
You get a warning now with unknown glyphs in bibitems (as you get in most
other contexts)
Jürgen
Guenter Milde wrote:
> should be adressed in a generic way as well (not only iconv but any helper
> application) (as this can happen also with unknown glyphs).
You get a warning now with unknown glyphs in bibitems (as you get in most
other contexts)
Jürgen
http://www.lyx.org/trac/ticket/6534
This post on lyx-docs
http://marc.info/?l=lyx-docsm=126595372224033w=2
pointed me towards various unicode problems in the bibitem inset. Two issues:
1. if the label of a bibitem has a unicode glyph that is unknown to the output
encoding, this has to be
On 2010-02-12, Jürgen Spitzmüller wrote:
Currently, a unicode glyph (outside the output file's encoding) either
in the label or in the key yields a silent iconv error
...
The attached patch against branch solves both issues.
Objections, comments?
Thanks.
However, the silence of the iconv
http://www.lyx.org/trac/ticket/6534
This post on lyx-docs
http://marc.info/?l=lyx-docs=126595372224033=2
pointed me towards various unicode problems in the bibitem inset. Two issues:
1. if the label of a bibitem has a unicode glyph that is unknown to the output
encoding, this has to be
On 2010-02-12, Jürgen Spitzmüller wrote:
> Currently, a unicode glyph (outside the output file's encoding) either
> in the label or in the key yields a silent iconv error
...
> The attached patch against branch solves both issues.
> Objections, comments?
Thanks.
However, the "silence" of the
10 matches
Mail list logo
