Re: paper accepted for publication, but need help!

[Guenter Milde]

On 2014-06-10, Jean-Marc Lasgouttes wrote:
 10/06/2014 13:49, Neal Becker:

 The problem is triggered by my .bib entry, which includes a non-ascii
 character:

author =   {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

 By playing with lyx Document/Settings/Encoding, selecting unicode
 XeTeX (utf-8), I seem to be able to export dvi and then convert dvipdf
 OK.

 So is this a good procedure, or is something else recommended here?

 You should use the same encoding for your document and the LyX output 
 encoding. A workaround is to use LaTeX markup in the .bib file so that 
 it is compatible with any encoding.

I would recommend LaTeX markup (the LICR encoding) as the most stable and
save way to represent non-ASCII characters in a *.bib file.

In the above case, it would be Karol .{Z}yczkowski. 

Some BibTeX-Managers allow to determine the encoding of the bib file and
will do the conversion for you.

Also LyX (usually)¹ does a good job in converting Unicode to the TeX LICR
encoding when you select DocumentSettingsLanguageEncoding: ASCII
Then you can paste/write offending entries into the main window and see
the translation in ViewSourceLaTeX.

Günter


¹ Don't use the LyX translation for Greek and Cyrillic script, as this does
  not use LICR but hard-coded slots in a TeX font encoding. (I am working on
  a patch.)

Re: paper accepted for publication, but need help!

[Guenter Milde]

On 2014-06-10, Jean-Marc Lasgouttes wrote:
 10/06/2014 13:49, Neal Becker:

 The problem is triggered by my .bib entry, which includes a non-ascii
 character:

author =   {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

 By playing with lyx Document/Settings/Encoding, selecting unicode
 XeTeX (utf-8), I seem to be able to export dvi and then convert dvipdf
 OK.

 So is this a good procedure, or is something else recommended here?

 You should use the same encoding for your document and the LyX output 
 encoding. A workaround is to use LaTeX markup in the .bib file so that 
 it is compatible with any encoding.

I would recommend LaTeX markup (the LICR encoding) as the most stable and
save way to represent non-ASCII characters in a *.bib file.

In the above case, it would be Karol .{Z}yczkowski. 

Some BibTeX-Managers allow to determine the encoding of the bib file and
will do the conversion for you.

Also LyX (usually)¹ does a good job in converting Unicode to the TeX LICR
encoding when you select DocumentSettingsLanguageEncoding: ASCII
Then you can paste/write offending entries into the main window and see
the translation in ViewSourceLaTeX.

Günter


¹ Don't use the LyX translation for Greek and Cyrillic script, as this does
  not use LICR but hard-coded slots in a TeX font encoding. (I am working on
  a patch.)

Re: paper accepted for publication, but need help!

[Guenter Milde]

On 2014-06-10, Jean-Marc Lasgouttes wrote:
> 10/06/2014 13:49, Neal Becker:

>> The problem is triggered by my .bib entry, which includes a non-ascii
>> character:

>>author =   {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

>> By playing with lyx Document/Settings/Encoding, selecting unicode
>> XeTeX (utf-8), I seem to be able to export dvi and then convert dvipdf
>> OK.

>> So is this a "good" procedure, or is something else recommended here?

> You should use the same encoding for your document and the LyX output 
> encoding. A workaround is to use LaTeX markup in the .bib file so that 
> it is compatible with any encoding.

I would recommend LaTeX markup (the "LICR encoding") as the most stable and
save way to represent non-ASCII characters in a *.bib file.

In the above case, it would be "Karol .{Z}yczkowski". 

Some BibTeX-Managers allow to determine the encoding of the bib file and
will do the conversion for you.

Also LyX (usually)¹ does a good job in converting Unicode to the TeX "LICR
encoding" when you select Document>Settings>Language>Encoding: ASCII
Then you can paste/write "offending" entries into the main window and see
the translation in View>Source>LaTeX.

Günter


¹ Don't use the LyX translation for Greek and Cyrillic script, as this does
  not use LICR but hard-coded slots in a TeX font encoding. (I am working on
  a patch.)

Re: paper accepted for publication, but need help!

[Neal Becker]

stefano franchi wrote:

 On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland 
 benedict.m.holl...@gmail.com wrote:
 
 That is a fantastic point. Also I just found this.

 http://wiki.lyx.org/BibTeX/Biblatex

 I don't know enough about Lyx to start programing stuff for it yet but it
 seems like pushing biber and biblatex as the default is about 15 years
 overdue. If someone who knows far more about the Lyx codebase can ping me
 or if this would be a great feature request, I would be willing to spend
 some time on this. I ran into very similar problem with a name much like
 Jürgen and I lost a few days trying to figure it out.


 Hi Benedict,
 
 I think most developers (of which I am not one) agree that full biblatex
 support would be desirable. However, from what I understand, adding such
 support is not an entirely trivial task, partly because biblatex/biber
 interact with latex in a very different way from bibtex. That does not mean
 you are not welcome to give it a try. In fact, you strongly encouraged to
 do so! There were some discussions of this topic on the lyx-devel list a
 few months ago. You may want to search for those threads to get started.
 
 I also tend to believe that one of the reasons why biblatex support does
 not have a very high priority on the developers' agenda is that the current
 workaround (described in the wiki page you referred to) is good enough for
 a lot of users. It has certainly been good enough for me for a number of
 years. I switched to biblatex/biber to get full unicode support and avoid
 the kind of time-consuming issues discussed in this thread. Once you get
 used to loading biblatex in the preamble (and adding a fake bibtex inset at
 the end) it is smooth sailing. If you tend to work with the same bib files
 all the time (as I do), you may even create a lyx template with the proper
 preamble and bibtex inset and you are done.
 
 Cheers,
 Stefano
 
 
 

Following the wiki instructions doesn't quite work for me.

1. It seems to fail to run biber.  All refs are undefined, and no bibliography 
is output.

If I export lyx-tex and run lualatex, it asks me to run biber.  After manually 
 
running biber, then the bibliography is output.

2. But, in IEEE style, with bibtex, the bib entries use a smaller font, But not 
with biblatex - they seem to use the standard font used in the main material.

Re: paper accepted for publication, but need help!

[stefano franchi]

On Fri, Jun 13, 2014 at 6:30 AM, Neal Becker ndbeck...@gmail.com wrote:

 stefano franchi wrote:

  On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland 
  benedict.m.holl...@gmail.com wrote:
 
  That is a fantastic point. Also I just found this.
 
  http://wiki.lyx.org/BibTeX/Biblatex
 
  I don't know enough about Lyx to start programing stuff for it yet but
 it
  seems like pushing biber and biblatex as the default is about 15 years
  overdue. If someone who knows far more about the Lyx codebase can ping
 me
  or if this would be a great feature request, I would be willing to spend
  some time on this. I ran into very similar problem with a name much like
  Jürgen and I lost a few days trying to figure it out.
 
 
  Hi Benedict,
 
  I think most developers (of which I am not one) agree that full biblatex
  support would be desirable. However, from what I understand, adding such
  support is not an entirely trivial task, partly because biblatex/biber
  interact with latex in a very different way from bibtex. That does not
 mean
  you are not welcome to give it a try. In fact, you strongly encouraged to
  do so! There were some discussions of this topic on the lyx-devel list a
  few months ago. You may want to search for those threads to get started.
 
  I also tend to believe that one of the reasons why biblatex support does
  not have a very high priority on the developers' agenda is that the
 current
  workaround (described in the wiki page you referred to) is good enough
 for
  a lot of users. It has certainly been good enough for me for a number of
  years. I switched to biblatex/biber to get full unicode support and avoid
  the kind of time-consuming issues discussed in this thread. Once you get
  used to loading biblatex in the preamble (and adding a fake bibtex inset
 at
  the end) it is smooth sailing. If you tend to work with the same bib
 files
  all the time (as I do), you may even create a lyx template with the
 proper
  preamble and bibtex inset and you are done.
 
  Cheers,
  Stefano
 
 
 

 Following the wiki instructions doesn't quite work for me.

 1. It seems to fail to run biber.  All refs are undefined, and no
 bibliography
 is output.

 If I export lyx-tex and run lualatex, it asks me to run biber.  After
 manually
 running biber, then the bibliography is output.


1. I would first make sure that you have selected biber as you
bibbliography processor in
DocumentSettingsBibliographyProcessor  (from the drop-down menu
choose biber)

2. Second, make sure that biber can actually find your bib files. Look in
the biber log for an appropriate message (DocumentLaTeX Log, then select
bibtex from the dropdown menu). do you see a message from biber to the
effect that one or more bib files could not be found?
Notice that biblatex requires you to specify the .bib extension in the
\addbibresource command in the preamble. ANd notice that you need to insert
the absolute path to the bib file (in the same command).

3. If biber is selected, and still it is not run by LyX during pdf
generation, I would check what LyX acutally does during such generation.
Choose ViewMessages Pane then click on the settings vertical tab in the
right, choose the selected radio button, and then in the rightmost pane
(Debug level) double click LaTeX generation/execution.
Then visualize the pdf file as usual and look at which kind of messages you
get.

Get back to us with the info you get and we'll take it further.



 2. But, in IEEE style, with bibtex, the bib entries use a smaller font,
 But not
 with biblatex - they seem to use the standard font used in the main
 material.


biblatex has a gazillion of options, I am sure there must be one somewhere
that does what you want. But as a quick hack, try the following in your
preamble:

\renewcommand{\bibfont}{\normalfont\small}



Cheers,

S.

-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies Ph:   +1 (979) 845-2125
Texas AM University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: paper accepted for publication, but need help!

[Neal Becker]

stefano franchi wrote:

 On Fri, Jun 13, 2014 at 6:30 AM, Neal Becker ndbeck...@gmail.com wrote:
 
 stefano franchi wrote:

  On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland 
  benedict.m.holl...@gmail.com wrote:
 
  That is a fantastic point. Also I just found this.
 
  http://wiki.lyx.org/BibTeX/Biblatex
 
  I don't know enough about Lyx to start programing stuff for it yet but
 it
  seems like pushing biber and biblatex as the default is about 15 years
  overdue. If someone who knows far more about the Lyx codebase can ping
 me
  or if this would be a great feature request, I would be willing to spend
  some time on this. I ran into very similar problem with a name much like
  Jürgen and I lost a few days trying to figure it out.
 
 
  Hi Benedict,
 
  I think most developers (of which I am not one) agree that full biblatex
  support would be desirable. However, from what I understand, adding such
  support is not an entirely trivial task, partly because biblatex/biber
  interact with latex in a very different way from bibtex. That does not
 mean
  you are not welcome to give it a try. In fact, you strongly encouraged to
  do so! There were some discussions of this topic on the lyx-devel list a
  few months ago. You may want to search for those threads to get started.
 
  I also tend to believe that one of the reasons why biblatex support does
  not have a very high priority on the developers' agenda is that the
 current
  workaround (described in the wiki page you referred to) is good enough
 for
  a lot of users. It has certainly been good enough for me for a number of
  years. I switched to biblatex/biber to get full unicode support and avoid
  the kind of time-consuming issues discussed in this thread. Once you get
  used to loading biblatex in the preamble (and adding a fake bibtex inset
 at
  the end) it is smooth sailing. If you tend to work with the same bib
 files
  all the time (as I do), you may even create a lyx template with the
 proper
  preamble and bibtex inset and you are done.
 
  Cheers,
  Stefano
 
 
 

 Following the wiki instructions doesn't quite work for me.

 1. It seems to fail to run biber.  All refs are undefined, and no
 bibliography
 is output.

 If I export lyx-tex and run lualatex, it asks me to run biber.  After
 manually
 running biber, then the bibliography is output.


 1. I would first make sure that you have selected biber as you
 bibbliography processor in
 DocumentSettingsBibliographyProcessor  (from the drop-down menu
 choose biber)
 
 2. Second, make sure that biber can actually find your bib files. Look in
 the biber log for an appropriate message (DocumentLaTeX Log, then select
 bibtex from the dropdown menu). do you see a message from biber to the
 effect that one or more bib files could not be found?
 Notice that biblatex requires you to specify the .bib extension in the
 \addbibresource command in the preamble. ANd notice that you need to insert
 the absolute path to the bib file (in the same command).
 
 3. If biber is selected, and still it is not run by LyX during pdf
 generation, I would check what LyX acutally does during such generation.
 Choose ViewMessages Pane then click on the settings vertical tab in the
 right, choose the selected radio button, and then in the rightmost pane
 (Debug level) double click LaTeX generation/execution.
 Then visualize the pdf file as usual and look at which kind of messages you
 get.
 
 Get back to us with the info you get and we'll take it further.
 
 
 
 2. But, in IEEE style, with bibtex, the bib entries use a smaller font,
 But not
 with biblatex - they seem to use the standard font used in the main
 material.


 biblatex has a gazillion of options, I am sure there must be one somewhere
 that does what you want. But as a quick hack, try the following in your
 preamble:
 
 \renewcommand{\bibfont}{\normalfont\small}
 
 
 
 Cheers,
 
 S.
 

1. Thanks!  I had forgotten to select biber as bib processor - now it's working

2. \renewcommand{\bibfont}{\normalfont\small} worked great!  Thanks again.  I 
looked for options, but nothing in 
http://mirror.utexas.edu/ctan/macros/latex/contrib/biblatex-contrib/biblatex-ieee/biblatex-ieee.pdf.
  I'll try contacting the author.

Re: paper accepted for publication, but need help!

[Neal Becker]

stefano franchi wrote:

 On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland 
 benedict.m.holl...@gmail.com wrote:
 
 That is a fantastic point. Also I just found this.

 http://wiki.lyx.org/BibTeX/Biblatex

 I don't know enough about Lyx to start programing stuff for it yet but it
 seems like pushing biber and biblatex as the default is about 15 years
 overdue. If someone who knows far more about the Lyx codebase can ping me
 or if this would be a great feature request, I would be willing to spend
 some time on this. I ran into very similar problem with a name much like
 Jürgen and I lost a few days trying to figure it out.


 Hi Benedict,
 
 I think most developers (of which I am not one) agree that full biblatex
 support would be desirable. However, from what I understand, adding such
 support is not an entirely trivial task, partly because biblatex/biber
 interact with latex in a very different way from bibtex. That does not mean
 you are not welcome to give it a try. In fact, you strongly encouraged to
 do so! There were some discussions of this topic on the lyx-devel list a
 few months ago. You may want to search for those threads to get started.
 
 I also tend to believe that one of the reasons why biblatex support does
 not have a very high priority on the developers' agenda is that the current
 workaround (described in the wiki page you referred to) is good enough for
 a lot of users. It has certainly been good enough for me for a number of
 years. I switched to biblatex/biber to get full unicode support and avoid
 the kind of time-consuming issues discussed in this thread. Once you get
 used to loading biblatex in the preamble (and adding a fake bibtex inset at
 the end) it is smooth sailing. If you tend to work with the same bib files
 all the time (as I do), you may even create a lyx template with the proper
 preamble and bibtex inset and you are done.
 
 Cheers,
 Stefano
 
 
 

Following the wiki instructions doesn't quite work for me.

1. It seems to fail to run biber.  All refs are undefined, and no bibliography 
is output.

If I export lyx-tex and run lualatex, it asks me to run biber.  After manually 
 
running biber, then the bibliography is output.

2. But, in IEEE style, with bibtex, the bib entries use a smaller font, But not 
with biblatex - they seem to use the standard font used in the main material.

Re: paper accepted for publication, but need help!

[stefano franchi]

On Fri, Jun 13, 2014 at 6:30 AM, Neal Becker ndbeck...@gmail.com wrote:

 stefano franchi wrote:

  On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland 
  benedict.m.holl...@gmail.com wrote:
 
  That is a fantastic point. Also I just found this.
 
  http://wiki.lyx.org/BibTeX/Biblatex
 
  I don't know enough about Lyx to start programing stuff for it yet but
 it
  seems like pushing biber and biblatex as the default is about 15 years
  overdue. If someone who knows far more about the Lyx codebase can ping
 me
  or if this would be a great feature request, I would be willing to spend
  some time on this. I ran into very similar problem with a name much like
  Jürgen and I lost a few days trying to figure it out.
 
 
  Hi Benedict,
 
  I think most developers (of which I am not one) agree that full biblatex
  support would be desirable. However, from what I understand, adding such
  support is not an entirely trivial task, partly because biblatex/biber
  interact with latex in a very different way from bibtex. That does not
 mean
  you are not welcome to give it a try. In fact, you strongly encouraged to
  do so! There were some discussions of this topic on the lyx-devel list a
  few months ago. You may want to search for those threads to get started.
 
  I also tend to believe that one of the reasons why biblatex support does
  not have a very high priority on the developers' agenda is that the
 current
  workaround (described in the wiki page you referred to) is good enough
 for
  a lot of users. It has certainly been good enough for me for a number of
  years. I switched to biblatex/biber to get full unicode support and avoid
  the kind of time-consuming issues discussed in this thread. Once you get
  used to loading biblatex in the preamble (and adding a fake bibtex inset
 at
  the end) it is smooth sailing. If you tend to work with the same bib
 files
  all the time (as I do), you may even create a lyx template with the
 proper
  preamble and bibtex inset and you are done.
 
  Cheers,
  Stefano
 
 
 

 Following the wiki instructions doesn't quite work for me.

 1. It seems to fail to run biber.  All refs are undefined, and no
 bibliography
 is output.

 If I export lyx-tex and run lualatex, it asks me to run biber.  After
 manually
 running biber, then the bibliography is output.


1. I would first make sure that you have selected biber as you
bibbliography processor in
DocumentSettingsBibliographyProcessor  (from the drop-down menu
choose biber)

2. Second, make sure that biber can actually find your bib files. Look in
the biber log for an appropriate message (DocumentLaTeX Log, then select
bibtex from the dropdown menu). do you see a message from biber to the
effect that one or more bib files could not be found?
Notice that biblatex requires you to specify the .bib extension in the
\addbibresource command in the preamble. ANd notice that you need to insert
the absolute path to the bib file (in the same command).

3. If biber is selected, and still it is not run by LyX during pdf
generation, I would check what LyX acutally does during such generation.
Choose ViewMessages Pane then click on the settings vertical tab in the
right, choose the selected radio button, and then in the rightmost pane
(Debug level) double click LaTeX generation/execution.
Then visualize the pdf file as usual and look at which kind of messages you
get.

Get back to us with the info you get and we'll take it further.



 2. But, in IEEE style, with bibtex, the bib entries use a smaller font,
 But not
 with biblatex - they seem to use the standard font used in the main
 material.


biblatex has a gazillion of options, I am sure there must be one somewhere
that does what you want. But as a quick hack, try the following in your
preamble:

\renewcommand{\bibfont}{\normalfont\small}



Cheers,

S.

-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies Ph:   +1 (979) 845-2125
Texas AM University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: paper accepted for publication, but need help!

[Neal Becker]

stefano franchi wrote:

 On Fri, Jun 13, 2014 at 6:30 AM, Neal Becker ndbeck...@gmail.com wrote:
 
 stefano franchi wrote:

  On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland 
  benedict.m.holl...@gmail.com wrote:
 
  That is a fantastic point. Also I just found this.
 
  http://wiki.lyx.org/BibTeX/Biblatex
 
  I don't know enough about Lyx to start programing stuff for it yet but
 it
  seems like pushing biber and biblatex as the default is about 15 years
  overdue. If someone who knows far more about the Lyx codebase can ping
 me
  or if this would be a great feature request, I would be willing to spend
  some time on this. I ran into very similar problem with a name much like
  Jürgen and I lost a few days trying to figure it out.
 
 
  Hi Benedict,
 
  I think most developers (of which I am not one) agree that full biblatex
  support would be desirable. However, from what I understand, adding such
  support is not an entirely trivial task, partly because biblatex/biber
  interact with latex in a very different way from bibtex. That does not
 mean
  you are not welcome to give it a try. In fact, you strongly encouraged to
  do so! There were some discussions of this topic on the lyx-devel list a
  few months ago. You may want to search for those threads to get started.
 
  I also tend to believe that one of the reasons why biblatex support does
  not have a very high priority on the developers' agenda is that the
 current
  workaround (described in the wiki page you referred to) is good enough
 for
  a lot of users. It has certainly been good enough for me for a number of
  years. I switched to biblatex/biber to get full unicode support and avoid
  the kind of time-consuming issues discussed in this thread. Once you get
  used to loading biblatex in the preamble (and adding a fake bibtex inset
 at
  the end) it is smooth sailing. If you tend to work with the same bib
 files
  all the time (as I do), you may even create a lyx template with the
 proper
  preamble and bibtex inset and you are done.
 
  Cheers,
  Stefano
 
 
 

 Following the wiki instructions doesn't quite work for me.

 1. It seems to fail to run biber.  All refs are undefined, and no
 bibliography
 is output.

 If I export lyx-tex and run lualatex, it asks me to run biber.  After
 manually
 running biber, then the bibliography is output.


 1. I would first make sure that you have selected biber as you
 bibbliography processor in
 DocumentSettingsBibliographyProcessor  (from the drop-down menu
 choose biber)
 
 2. Second, make sure that biber can actually find your bib files. Look in
 the biber log for an appropriate message (DocumentLaTeX Log, then select
 bibtex from the dropdown menu). do you see a message from biber to the
 effect that one or more bib files could not be found?
 Notice that biblatex requires you to specify the .bib extension in the
 \addbibresource command in the preamble. ANd notice that you need to insert
 the absolute path to the bib file (in the same command).
 
 3. If biber is selected, and still it is not run by LyX during pdf
 generation, I would check what LyX acutally does during such generation.
 Choose ViewMessages Pane then click on the settings vertical tab in the
 right, choose the selected radio button, and then in the rightmost pane
 (Debug level) double click LaTeX generation/execution.
 Then visualize the pdf file as usual and look at which kind of messages you
 get.
 
 Get back to us with the info you get and we'll take it further.
 
 
 
 2. But, in IEEE style, with bibtex, the bib entries use a smaller font,
 But not
 with biblatex - they seem to use the standard font used in the main
 material.


 biblatex has a gazillion of options, I am sure there must be one somewhere
 that does what you want. But as a quick hack, try the following in your
 preamble:
 
 \renewcommand{\bibfont}{\normalfont\small}
 
 
 
 Cheers,
 
 S.
 

1. Thanks!  I had forgotten to select biber as bib processor - now it's working

2. \renewcommand{\bibfont}{\normalfont\small} worked great!  Thanks again.  I 
looked for options, but nothing in 
http://mirror.utexas.edu/ctan/macros/latex/contrib/biblatex-contrib/biblatex-ieee/biblatex-ieee.pdf.
  I'll try contacting the author.

Re: paper accepted for publication, but need help!

[Neal Becker]

stefano franchi wrote:

> On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland <
> benedict.m.holl...@gmail.com> wrote:
> 
>> That is a fantastic point. Also I just found this.
>>
>> http://wiki.lyx.org/BibTeX/Biblatex
>>
>> I don't know enough about Lyx to start programing stuff for it yet but it
>> seems like pushing biber and biblatex as the default is about 15 years
>> overdue. If someone who knows far more about the Lyx codebase can ping me
>> or if this would be a great feature request, I would be willing to spend
>> some time on this. I ran into very similar problem with a name much like
>> Jürgen and I lost a few days trying to figure it out.
>>
>>
> Hi Benedict,
> 
> I think most developers (of which I am not one) agree that full biblatex
> support would be desirable. However, from what I understand, adding such
> support is not an entirely trivial task, partly because biblatex/biber
> interact with latex in a very different way from bibtex. That does not mean
> you are not welcome to give it a try. In fact, you strongly encouraged to
> do so! There were some discussions of this topic on the lyx-devel list a
> few months ago. You may want to search for those threads to get started.
> 
> I also tend to believe that one of the reasons why biblatex support does
> not have a very high priority on the developers' agenda is that the current
> workaround (described in the wiki page you referred to) is good enough for
> a lot of users. It has certainly been good enough for me for a number of
> years. I switched to biblatex/biber to get full unicode support and avoid
> the kind of time-consuming issues discussed in this thread. Once you get
> used to loading biblatex in the preamble (and adding a fake bibtex inset at
> the end) it is smooth sailing. If you tend to work with the same bib files
> all the time (as I do), you may even create a lyx template with the proper
> preamble and bibtex inset and you are done.
> 
> Cheers,
> Stefano
> 
> 
> 

Following the wiki instructions doesn't quite work for me.

1. It seems to fail to run biber.  All refs are undefined, and no bibliography 
is output.

If I export lyx->tex and run lualatex, it asks me to run biber.  After manually 
 
running biber, then the bibliography is output.

2. But, in IEEE style, with bibtex, the bib entries use a smaller font, But not 
with biblatex - they seem to use the standard font used in the main material.

Re: paper accepted for publication, but need help!

[stefano franchi]

On Fri, Jun 13, 2014 at 6:30 AM, Neal Becker  wrote:

> stefano franchi wrote:
>
> > On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland <
> > benedict.m.holl...@gmail.com> wrote:
> >
> >> That is a fantastic point. Also I just found this.
> >>
> >> http://wiki.lyx.org/BibTeX/Biblatex
> >>
> >> I don't know enough about Lyx to start programing stuff for it yet but
> it
> >> seems like pushing biber and biblatex as the default is about 15 years
> >> overdue. If someone who knows far more about the Lyx codebase can ping
> me
> >> or if this would be a great feature request, I would be willing to spend
> >> some time on this. I ran into very similar problem with a name much like
> >> Jürgen and I lost a few days trying to figure it out.
> >>
> >>
> > Hi Benedict,
> >
> > I think most developers (of which I am not one) agree that full biblatex
> > support would be desirable. However, from what I understand, adding such
> > support is not an entirely trivial task, partly because biblatex/biber
> > interact with latex in a very different way from bibtex. That does not
> mean
> > you are not welcome to give it a try. In fact, you strongly encouraged to
> > do so! There were some discussions of this topic on the lyx-devel list a
> > few months ago. You may want to search for those threads to get started.
> >
> > I also tend to believe that one of the reasons why biblatex support does
> > not have a very high priority on the developers' agenda is that the
> current
> > workaround (described in the wiki page you referred to) is good enough
> for
> > a lot of users. It has certainly been good enough for me for a number of
> > years. I switched to biblatex/biber to get full unicode support and avoid
> > the kind of time-consuming issues discussed in this thread. Once you get
> > used to loading biblatex in the preamble (and adding a fake bibtex inset
> at
> > the end) it is smooth sailing. If you tend to work with the same bib
> files
> > all the time (as I do), you may even create a lyx template with the
> proper
> > preamble and bibtex inset and you are done.
> >
> > Cheers,
> > Stefano
> >
> >
> >
>
> Following the wiki instructions doesn't quite work for me.
>
> 1. It seems to fail to run biber.  All refs are undefined, and no
> bibliography
> is output.
>
> If I export lyx->tex and run lualatex, it asks me to run biber.  After
> manually
> running biber, then the bibliography is output.
>
>
1. I would first make sure that you have selected biber as you
bibbliography processor in
Document>>Settings>>Bibliography>>Processor  (from the drop-down menu
choose "biber")

2. Second, make sure that biber can actually find your bib files. Look in
the biber log for an appropriate message (Document>>LaTeX Log, then select
bibtex from the dropdown menu). do you see a message from biber to the
effect that one or more bib files could not be found?
Notice that biblatex requires you to specify the .bib extension in the
\addbibresource command in the preamble. ANd notice that you need to insert
the absolute path to the bib file (in the same command).

3. If biber is selected, and still it is not run by LyX during pdf
generation, I would check what LyX acutally does during such generation.
Choose View>>Messages Pane then click on the "settings" vertical tab in the
right, choose the "selected" radio button, and then in the rightmost pane
("Debug level") double click "LaTeX generation/execution."
Then visualize the pdf file as usual and look at which kind of messages you
get.

Get back to us with the info you get and we'll take it further.



> 2. But, in IEEE style, with bibtex, the bib entries use a smaller font,
> But not
> with biblatex - they seem to use the standard font used in the main
> material.
>
>
biblatex has a gazillion of options, I am sure there must be one somewhere
that does what you want. But as a quick hack, try the following in your
preamble:

\renewcommand{\bibfont}{\normalfont\small}



Cheers,

S.

-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies Ph:   +1 (979) 845-2125
Texas A University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: paper accepted for publication, but need help!

[Neal Becker]

stefano franchi wrote:

> On Fri, Jun 13, 2014 at 6:30 AM, Neal Becker  wrote:
> 
>> stefano franchi wrote:
>>
>> > On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland <
>> > benedict.m.holl...@gmail.com> wrote:
>> >
>> >> That is a fantastic point. Also I just found this.
>> >>
>> >> http://wiki.lyx.org/BibTeX/Biblatex
>> >>
>> >> I don't know enough about Lyx to start programing stuff for it yet but
>> it
>> >> seems like pushing biber and biblatex as the default is about 15 years
>> >> overdue. If someone who knows far more about the Lyx codebase can ping
>> me
>> >> or if this would be a great feature request, I would be willing to spend
>> >> some time on this. I ran into very similar problem with a name much like
>> >> Jürgen and I lost a few days trying to figure it out.
>> >>
>> >>
>> > Hi Benedict,
>> >
>> > I think most developers (of which I am not one) agree that full biblatex
>> > support would be desirable. However, from what I understand, adding such
>> > support is not an entirely trivial task, partly because biblatex/biber
>> > interact with latex in a very different way from bibtex. That does not
>> mean
>> > you are not welcome to give it a try. In fact, you strongly encouraged to
>> > do so! There were some discussions of this topic on the lyx-devel list a
>> > few months ago. You may want to search for those threads to get started.
>> >
>> > I also tend to believe that one of the reasons why biblatex support does
>> > not have a very high priority on the developers' agenda is that the
>> current
>> > workaround (described in the wiki page you referred to) is good enough
>> for
>> > a lot of users. It has certainly been good enough for me for a number of
>> > years. I switched to biblatex/biber to get full unicode support and avoid
>> > the kind of time-consuming issues discussed in this thread. Once you get
>> > used to loading biblatex in the preamble (and adding a fake bibtex inset
>> at
>> > the end) it is smooth sailing. If you tend to work with the same bib
>> files
>> > all the time (as I do), you may even create a lyx template with the
>> proper
>> > preamble and bibtex inset and you are done.
>> >
>> > Cheers,
>> > Stefano
>> >
>> >
>> >
>>
>> Following the wiki instructions doesn't quite work for me.
>>
>> 1. It seems to fail to run biber.  All refs are undefined, and no
>> bibliography
>> is output.
>>
>> If I export lyx->tex and run lualatex, it asks me to run biber.  After
>> manually
>> running biber, then the bibliography is output.
>>
>>
> 1. I would first make sure that you have selected biber as you
> bibbliography processor in
> Document>>Settings>>Bibliography>>Processor  (from the drop-down menu
> choose "biber")
> 
> 2. Second, make sure that biber can actually find your bib files. Look in
> the biber log for an appropriate message (Document>>LaTeX Log, then select
> bibtex from the dropdown menu). do you see a message from biber to the
> effect that one or more bib files could not be found?
> Notice that biblatex requires you to specify the .bib extension in the
> \addbibresource command in the preamble. ANd notice that you need to insert
> the absolute path to the bib file (in the same command).
> 
> 3. If biber is selected, and still it is not run by LyX during pdf
> generation, I would check what LyX acutally does during such generation.
> Choose View>>Messages Pane then click on the "settings" vertical tab in the
> right, choose the "selected" radio button, and then in the rightmost pane
> ("Debug level") double click "LaTeX generation/execution."
> Then visualize the pdf file as usual and look at which kind of messages you
> get.
> 
> Get back to us with the info you get and we'll take it further.
> 
> 
> 
>> 2. But, in IEEE style, with bibtex, the bib entries use a smaller font,
>> But not
>> with biblatex - they seem to use the standard font used in the main
>> material.
>>
>>
> biblatex has a gazillion of options, I am sure there must be one somewhere
> that does what you want. But as a quick hack, try the following in your
> preamble:
> 
> \renewcommand{\bibfont}{\normalfont\small}
> 
> 
> 
> Cheers,
> 
> S.
> 

1. Thanks!  I had forgotten to select biber as bib processor - now it's working

2. \renewcommand{\bibfont}{\normalfont\small} worked great!  Thanks again.  I 
looked for options, but nothing in 
http://mirror.utexas.edu/ctan/macros/latex/contrib/biblatex-contrib/biblatex-ieee/biblatex-ieee.pdf.
  I'll try contacting the author.

Re: paper accepted for publication, but need help!

[Jürgen Spitzmüller]

2014-06-12 0:53 GMT+02:00 Benedict Holland:

 I think this is a problem with the default configuration, at least on
 linux. You really need to use Bibtex8 for the bibliogrophy generation. This
 is NOT the default. The default is bibtex which doesn't have any unicode
 support because it actually was written in the 1980's. bibtex8 should
 really be the default by now on any system. Also the language support in
 lyx should default to utf-8. It would make life much easier to not have to
 change these around so much and avoid these sorts of bugs. I also should
 point out that pdflatex does an excellent job at catching these problems.
 XeTex I think uses utf-8 by default which is why it worked when you
 switched from pdflatex to XeTex.


Note that bibtex8 does not support unicode either (but only 8-bit
encodings, as the name implies). There is one experimental unicode version
of bibtex, bibtexu, but I do not think it works reliable enough already.

For real unicode support, you must use biblatex with biber.

Jürgen

Re: paper accepted for publication, but need help!

[Benedict Holland]

That is a fantastic point. Also I just found this.

http://wiki.lyx.org/BibTeX/Biblatex

I don't know enough about Lyx to start programing stuff for it yet but it
seems like pushing biber and biblatex as the default is about 15 years
overdue. If someone who knows far more about the Lyx codebase can ping me
or if this would be a great feature request, I would be willing to spend
some time on this. I ran into very similar problem with a name much like Jürgen
and I lost a few days trying to figure it out.

~Ben


On Thu, Jun 12, 2014 at 2:17 AM, Jürgen Spitzmüller sp...@lyx.org wrote:

 2014-06-12 0:53 GMT+02:00 Benedict Holland:

 I think this is a problem with the default configuration, at least on
 linux. You really need to use Bibtex8 for the bibliogrophy generation. This
 is NOT the default. The default is bibtex which doesn't have any unicode
 support because it actually was written in the 1980's. bibtex8 should
 really be the default by now on any system. Also the language support in
 lyx should default to utf-8. It would make life much easier to not have to
 change these around so much and avoid these sorts of bugs. I also should
 point out that pdflatex does an excellent job at catching these problems.
 XeTex I think uses utf-8 by default which is why it worked when you
 switched from pdflatex to XeTex.


 Note that bibtex8 does not support unicode either (but only 8-bit
 encodings, as the name implies). There is one experimental unicode version
 of bibtex, bibtexu, but I do not think it works reliable enough already.

 For real unicode support, you must use biblatex with biber.

 Jürgen

Re: paper accepted for publication, but need help!

[stefano franchi]

On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland 
benedict.m.holl...@gmail.com wrote:

 That is a fantastic point. Also I just found this.

 http://wiki.lyx.org/BibTeX/Biblatex

 I don't know enough about Lyx to start programing stuff for it yet but it
 seems like pushing biber and biblatex as the default is about 15 years
 overdue. If someone who knows far more about the Lyx codebase can ping me
 or if this would be a great feature request, I would be willing to spend
 some time on this. I ran into very similar problem with a name much like 
 Jürgen
 and I lost a few days trying to figure it out.


Hi Benedict,

I think most developers (of which I am not one) agree that full biblatex
support would be desirable. However, from what I understand, adding such
support is not an entirely trivial task, partly because biblatex/biber
interact with latex in a very different way from bibtex. That does not mean
you are not welcome to give it a try. In fact, you strongly encouraged to
do so! There were some discussions of this topic on the lyx-devel list a
few months ago. You may want to search for those threads to get started.

I also tend to believe that one of the reasons why biblatex support does
not have a very high priority on the developers' agenda is that the current
workaround (described in the wiki page you referred to) is good enough for
a lot of users. It has certainly been good enough for me for a number of
years. I switched to biblatex/biber to get full unicode support and avoid
the kind of time-consuming issues discussed in this thread. Once you get
used to loading biblatex in the preamble (and adding a fake bibtex inset at
the end) it is smooth sailing. If you tend to work with the same bib files
all the time (as I do), you may even create a lyx template with the proper
preamble and bibtex inset and you are done.

Cheers,
Stefano



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies Ph:   +1 (979) 845-2125
Texas AM University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: paper accepted for publication, but need help!

[Scott Kostyshak]

On Thu, Jun 12, 2014 at 10:27 AM, Benedict Holland
benedict.m.holl...@gmail.com wrote:

 if this would be a great feature request

Expanding on what Stefano said, there is a 7-year-old feature request here:
http://www.lyx.org/trac/ticket/4065

Scott

Re: paper accepted for publication, but need help!

[Jürgen Spitzmüller]

2014-06-12 0:53 GMT+02:00 Benedict Holland:

 I think this is a problem with the default configuration, at least on
 linux. You really need to use Bibtex8 for the bibliogrophy generation. This
 is NOT the default. The default is bibtex which doesn't have any unicode
 support because it actually was written in the 1980's. bibtex8 should
 really be the default by now on any system. Also the language support in
 lyx should default to utf-8. It would make life much easier to not have to
 change these around so much and avoid these sorts of bugs. I also should
 point out that pdflatex does an excellent job at catching these problems.
 XeTex I think uses utf-8 by default which is why it worked when you
 switched from pdflatex to XeTex.


Note that bibtex8 does not support unicode either (but only 8-bit
encodings, as the name implies). There is one experimental unicode version
of bibtex, bibtexu, but I do not think it works reliable enough already.

For real unicode support, you must use biblatex with biber.

Jürgen

Re: paper accepted for publication, but need help!

[Benedict Holland]

That is a fantastic point. Also I just found this.

http://wiki.lyx.org/BibTeX/Biblatex

I don't know enough about Lyx to start programing stuff for it yet but it
seems like pushing biber and biblatex as the default is about 15 years
overdue. If someone who knows far more about the Lyx codebase can ping me
or if this would be a great feature request, I would be willing to spend
some time on this. I ran into very similar problem with a name much like Jürgen
and I lost a few days trying to figure it out.

~Ben


On Thu, Jun 12, 2014 at 2:17 AM, Jürgen Spitzmüller sp...@lyx.org wrote:

 2014-06-12 0:53 GMT+02:00 Benedict Holland:

 I think this is a problem with the default configuration, at least on
 linux. You really need to use Bibtex8 for the bibliogrophy generation. This
 is NOT the default. The default is bibtex which doesn't have any unicode
 support because it actually was written in the 1980's. bibtex8 should
 really be the default by now on any system. Also the language support in
 lyx should default to utf-8. It would make life much easier to not have to
 change these around so much and avoid these sorts of bugs. I also should
 point out that pdflatex does an excellent job at catching these problems.
 XeTex I think uses utf-8 by default which is why it worked when you
 switched from pdflatex to XeTex.


 Note that bibtex8 does not support unicode either (but only 8-bit
 encodings, as the name implies). There is one experimental unicode version
 of bibtex, bibtexu, but I do not think it works reliable enough already.

 For real unicode support, you must use biblatex with biber.

 Jürgen

Re: paper accepted for publication, but need help!

[stefano franchi]

On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland 
benedict.m.holl...@gmail.com wrote:

 That is a fantastic point. Also I just found this.

 http://wiki.lyx.org/BibTeX/Biblatex

 I don't know enough about Lyx to start programing stuff for it yet but it
 seems like pushing biber and biblatex as the default is about 15 years
 overdue. If someone who knows far more about the Lyx codebase can ping me
 or if this would be a great feature request, I would be willing to spend
 some time on this. I ran into very similar problem with a name much like 
 Jürgen
 and I lost a few days trying to figure it out.


Hi Benedict,

I think most developers (of which I am not one) agree that full biblatex
support would be desirable. However, from what I understand, adding such
support is not an entirely trivial task, partly because biblatex/biber
interact with latex in a very different way from bibtex. That does not mean
you are not welcome to give it a try. In fact, you strongly encouraged to
do so! There were some discussions of this topic on the lyx-devel list a
few months ago. You may want to search for those threads to get started.

I also tend to believe that one of the reasons why biblatex support does
not have a very high priority on the developers' agenda is that the current
workaround (described in the wiki page you referred to) is good enough for
a lot of users. It has certainly been good enough for me for a number of
years. I switched to biblatex/biber to get full unicode support and avoid
the kind of time-consuming issues discussed in this thread. Once you get
used to loading biblatex in the preamble (and adding a fake bibtex inset at
the end) it is smooth sailing. If you tend to work with the same bib files
all the time (as I do), you may even create a lyx template with the proper
preamble and bibtex inset and you are done.

Cheers,
Stefano



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies Ph:   +1 (979) 845-2125
Texas AM University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: paper accepted for publication, but need help!

[Scott Kostyshak]

On Thu, Jun 12, 2014 at 10:27 AM, Benedict Holland
benedict.m.holl...@gmail.com wrote:

 if this would be a great feature request

Expanding on what Stefano said, there is a 7-year-old feature request here:
http://www.lyx.org/trac/ticket/4065

Scott

Re: paper accepted for publication, but need help!

[Jürgen Spitzmüller]

2014-06-12 0:53 GMT+02:00 Benedict Holland:

> I think this is a problem with the default configuration, at least on
> linux. You really need to use Bibtex8 for the bibliogrophy generation. This
> is NOT the default. The default is bibtex which doesn't have any unicode
> support because it actually was written in the 1980's. bibtex8 should
> really be the default by now on any system. Also the language support in
> lyx should default to utf-8. It would make life much easier to not have to
> change these around so much and avoid these sorts of bugs. I also should
> point out that pdflatex does an excellent job at catching these problems.
> XeTex I think uses utf-8 by default which is why it worked when you
> switched from pdflatex to XeTex.
>

Note that bibtex8 does not support unicode either (but only 8-bit
encodings, as the name implies). There is one experimental unicode version
of bibtex, bibtexu, but I do not think it works reliable enough already.

For real unicode support, you must use biblatex with biber.

Jürgen

Re: paper accepted for publication, but need help!

[Benedict Holland]

That is a fantastic point. Also I just found this.

http://wiki.lyx.org/BibTeX/Biblatex

I don't know enough about Lyx to start programing stuff for it yet but it
seems like pushing biber and biblatex as the default is about 15 years
overdue. If someone who knows far more about the Lyx codebase can ping me
or if this would be a great feature request, I would be willing to spend
some time on this. I ran into very similar problem with a name much like Jürgen
and I lost a few days trying to figure it out.

~Ben


On Thu, Jun 12, 2014 at 2:17 AM, Jürgen Spitzmüller  wrote:

> 2014-06-12 0:53 GMT+02:00 Benedict Holland:
>
> I think this is a problem with the default configuration, at least on
>> linux. You really need to use Bibtex8 for the bibliogrophy generation. This
>> is NOT the default. The default is bibtex which doesn't have any unicode
>> support because it actually was written in the 1980's. bibtex8 should
>> really be the default by now on any system. Also the language support in
>> lyx should default to utf-8. It would make life much easier to not have to
>> change these around so much and avoid these sorts of bugs. I also should
>> point out that pdflatex does an excellent job at catching these problems.
>> XeTex I think uses utf-8 by default which is why it worked when you
>> switched from pdflatex to XeTex.
>>
>
> Note that bibtex8 does not support unicode either (but only 8-bit
> encodings, as the name implies). There is one experimental unicode version
> of bibtex, bibtexu, but I do not think it works reliable enough already.
>
> For real unicode support, you must use biblatex with biber.
>
> Jürgen
>
>

Re: paper accepted for publication, but need help!

[stefano franchi]

On Thu, Jun 12, 2014 at 9:27 AM, Benedict Holland <
benedict.m.holl...@gmail.com> wrote:

> That is a fantastic point. Also I just found this.
>
> http://wiki.lyx.org/BibTeX/Biblatex
>
> I don't know enough about Lyx to start programing stuff for it yet but it
> seems like pushing biber and biblatex as the default is about 15 years
> overdue. If someone who knows far more about the Lyx codebase can ping me
> or if this would be a great feature request, I would be willing to spend
> some time on this. I ran into very similar problem with a name much like 
> Jürgen
> and I lost a few days trying to figure it out.
>
>
Hi Benedict,

I think most developers (of which I am not one) agree that full biblatex
support would be desirable. However, from what I understand, adding such
support is not an entirely trivial task, partly because biblatex/biber
interact with latex in a very different way from bibtex. That does not mean
you are not welcome to give it a try. In fact, you strongly encouraged to
do so! There were some discussions of this topic on the lyx-devel list a
few months ago. You may want to search for those threads to get started.

I also tend to believe that one of the reasons why biblatex support does
not have a very high priority on the developers' agenda is that the current
workaround (described in the wiki page you referred to) is good enough for
a lot of users. It has certainly been good enough for me for a number of
years. I switched to biblatex/biber to get full unicode support and avoid
the kind of time-consuming issues discussed in this thread. Once you get
used to loading biblatex in the preamble (and adding a fake bibtex inset at
the end) it is smooth sailing. If you tend to work with the same bib files
all the time (as I do), you may even create a lyx template with the proper
preamble and bibtex inset and you are done.

Cheers,
Stefano



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies Ph:   +1 (979) 845-2125
Texas A University  Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: paper accepted for publication, but need help!

[Scott Kostyshak]

On Thu, Jun 12, 2014 at 10:27 AM, Benedict Holland
 wrote:

> if this would be a great feature request

Expanding on what Stefano said, there is a 7-year-old feature request here:
http://www.lyx.org/trac/ticket/4065

Scott

Re: paper accepted for publication, but need help!

[Benedict Holland]

I think this is a problem with the default configuration, at least on
linux. You really need to use Bibtex8 for the bibliogrophy generation. This
is NOT the default. The default is bibtex which doesn't have any unicode
support because it actually was written in the 1980's. bibtex8 should
really be the default by now on any system. Also the language support in
lyx should default to utf-8. It would make life much easier to not have to
change these around so much and avoid these sorts of bugs. I also should
point out that pdflatex does an excellent job at catching these problems.
XeTex I think uses utf-8 by default which is why it worked when you
switched from pdflatex to XeTex.

~Ben


On Tue, Jun 10, 2014 at 7:57 AM, Jean-Marc Lasgouttes lasgout...@lyx.org
wrote:

 10/06/2014 13:49, Neal Becker:

  The problem is triggered by my .bib entry, which includes a non-ascii
 character:

author =  {Wojciech Bruzda and Wojciech Tadej and Karol
 Życzkowski},

 By playing with lyx Document/Settings/Encoding, selecting unicode XeTeX
 (utf-8),
 I seem to be able to export dvi and then convert dvipdf OK.

 So is this a good procedure, or is something else recommended here?


 You should use the same encoding for your document and the LyX output
 encoding. A workaround is to use LaTeX markup in the .bib file so that it
 is compatible with any encoding.

 JMarc

Re: paper accepted for publication, but need help!

[Benedict Holland]

I think this is a problem with the default configuration, at least on
linux. You really need to use Bibtex8 for the bibliogrophy generation. This
is NOT the default. The default is bibtex which doesn't have any unicode
support because it actually was written in the 1980's. bibtex8 should
really be the default by now on any system. Also the language support in
lyx should default to utf-8. It would make life much easier to not have to
change these around so much and avoid these sorts of bugs. I also should
point out that pdflatex does an excellent job at catching these problems.
XeTex I think uses utf-8 by default which is why it worked when you
switched from pdflatex to XeTex.

~Ben


On Tue, Jun 10, 2014 at 7:57 AM, Jean-Marc Lasgouttes lasgout...@lyx.org
wrote:

 10/06/2014 13:49, Neal Becker:

  The problem is triggered by my .bib entry, which includes a non-ascii
 character:

author =  {Wojciech Bruzda and Wojciech Tadej and Karol
 Życzkowski},

 By playing with lyx Document/Settings/Encoding, selecting unicode XeTeX
 (utf-8),
 I seem to be able to export dvi and then convert dvipdf OK.

 So is this a good procedure, or is something else recommended here?


 You should use the same encoding for your document and the LyX output
 encoding. A workaround is to use LaTeX markup in the .bib file so that it
 is compatible with any encoding.

 JMarc

Re: paper accepted for publication, but need help!

[Benedict Holland]

I think this is a problem with the default configuration, at least on
linux. You really need to use Bibtex8 for the bibliogrophy generation. This
is NOT the default. The default is bibtex which doesn't have any unicode
support because it actually was written in the 1980's. bibtex8 should
really be the default by now on any system. Also the language support in
lyx should default to utf-8. It would make life much easier to not have to
change these around so much and avoid these sorts of bugs. I also should
point out that pdflatex does an excellent job at catching these problems.
XeTex I think uses utf-8 by default which is why it worked when you
switched from pdflatex to XeTex.

~Ben


On Tue, Jun 10, 2014 at 7:57 AM, Jean-Marc Lasgouttes 
wrote:

> 10/06/2014 13:49, Neal Becker:
>
>  The problem is triggered by my .bib entry, which includes a non-ascii
>> character:
>>
>>author =  {Wojciech Bruzda and Wojciech Tadej and Karol
>> Życzkowski},
>>
>> By playing with lyx Document/Settings/Encoding, selecting unicode XeTeX
>> (utf-8),
>> I seem to be able to export dvi and then convert dvipdf OK.
>>
>> So is this a "good" procedure, or is something else recommended here?
>>
>
> You should use the same encoding for your document and the LyX output
> encoding. A workaround is to use LaTeX markup in the .bib file so that it
> is compatible with any encoding.
>
> JMarc
>
>

paper accepted for publication, but need help!

[Neal Becker]

Submitting to IEEE conf.  They accept TeX.

If I try to give them the TeX output, they say they need dvi, and
all figures in eps (what is this, 1980??)

If I try to export to dvi from lyx, I get:

---
! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H return  for immediate help.
 ...  
  
l.13  Vazquez-Castro, and A.~Morello, ``{DVB��
  �S2 ACM} modes for
You need to provide a definition with \DeclareInputText 
or \DeclareInputMath before using this key.


! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H return  for immediate help.
 ...  
  
l.13 ... Vazquez-Castro, and A.~Morello, ``{DVB‐
  S2 ACM} modes for
You need to provide a definition with \DeclareInputText 
or \DeclareInputMath before using this key.
--

If I select dvi (LuaTeX) export, lyx does not complain.  But then if I test the 
dvi myself, I get:

dvipdf vhtpaper.dvi
dvips: ! invalid char 8208 from font ec-lmr8

Re: paper accepted for publication, but need help!

[Wolfgang Engelmann]

I guess, if you take out the ref: Vazquez-Castro, and A.~Morello the error is 
gone. Check carefully the reference, perhaps by adding parts only (eg only the 
first word of the title, journal etc)
Wolfgang

Am 10.06.2014 13:35, schrieb Neal Becker:

Submitting to IEEE conf.  They accept TeX.

If I try to give them the TeX output, they say they need dvi, and
all figures in eps (what is this, 1980??)

If I try to export to dvi from lyx, I get:

---
! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H return  for immediate help.
  ...
   
l.13  Vazquez-Castro, and A.~Morello, ``{DVB��

   �S2 ACM} modes for
You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.


! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H return  for immediate help.
  ...
   
l.13 ... Vazquez-Castro, and A.~Morello, ``{DVB‐

   S2 ACM} modes for
You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.
--

If I select dvi (LuaTeX) export, lyx does not complain.  But then if I test the
dvi myself, I get:

dvipdf vhtpaper.dvi
dvips: ! invalid char 8208 from font ec-lmr8

Re: paper accepted for publication, but need help!

[Neal Becker]

The problem is triggered by my .bib entry, which includes a non-ascii character:

  author =   {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

By playing with lyx Document/Settings/Encoding, selecting unicode XeTeX 
(utf-8), 
I seem to be able to export dvi and then convert dvipdf OK.

So is this a good procedure, or is something else recommended here?

Neal Becker wrote:

 Submitting to IEEE conf.  They accept TeX.
 
 If I try to give them the TeX output, they say they need dvi, and
 all figures in eps (what is this, 1980??)
 
 If I try to export to dvi from lyx, I get:
 
 ---
 ! Package inputenc Error: Keyboard character used is undefined
 (inputenc)in inputencoding `latin9'.
 
 See the inputenc package documentation for explanation.
 Type  H return  for immediate help.
  ...
   
 l.13  Vazquez-Castro, and A.~Morello, ``{DVB��
   �S2 ACM} modes for
 You need to provide a definition with \DeclareInputText
 or \DeclareInputMath before using this key.
 
 
 ! Package inputenc Error: Keyboard character used is undefined
 (inputenc)in inputencoding `latin9'.
 
 See the inputenc package documentation for explanation.
 Type  H return  for immediate help.
  ...
   
 l.13 ... Vazquez-Castro, and A.~Morello, ``{DVB‐
   S2 ACM} modes for
 You need to provide a definition with \DeclareInputText
 or \DeclareInputMath before using this key.
 --
 
 If I select dvi (LuaTeX) export, lyx does not complain.  But then if I test
 the dvi myself, I get:
 
 dvipdf vhtpaper.dvi
 dvips: ! invalid char 8208 from font ec-lmr8

Re: paper accepted for publication, but need help!

[Jean-Marc Lasgouttes]

10/06/2014 13:49, Neal Becker:

The problem is triggered by my .bib entry, which includes a non-ascii character:

   author =  {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

By playing with lyx Document/Settings/Encoding, selecting unicode XeTeX (utf-8),
I seem to be able to export dvi and then convert dvipdf OK.

So is this a good procedure, or is something else recommended here?


You should use the same encoding for your document and the LyX output 
encoding. A workaround is to use LaTeX markup in the .bib file so that 
it is compatible with any encoding.


JMarc

paper accepted for publication, but need help!

[Neal Becker]

Submitting to IEEE conf.  They accept TeX.

If I try to give them the TeX output, they say they need dvi, and
all figures in eps (what is this, 1980??)

If I try to export to dvi from lyx, I get:

---
! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H return  for immediate help.
 ...  
  
l.13  Vazquez-Castro, and A.~Morello, ``{DVB��
  �S2 ACM} modes for
You need to provide a definition with \DeclareInputText 
or \DeclareInputMath before using this key.


! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H return  for immediate help.
 ...  
  
l.13 ... Vazquez-Castro, and A.~Morello, ``{DVB‐
  S2 ACM} modes for
You need to provide a definition with \DeclareInputText 
or \DeclareInputMath before using this key.
--

If I select dvi (LuaTeX) export, lyx does not complain.  But then if I test the 
dvi myself, I get:

dvipdf vhtpaper.dvi
dvips: ! invalid char 8208 from font ec-lmr8

Re: paper accepted for publication, but need help!

[Wolfgang Engelmann]

I guess, if you take out the ref: Vazquez-Castro, and A.~Morello the error is 
gone. Check carefully the reference, perhaps by adding parts only (eg only the 
first word of the title, journal etc)
Wolfgang

Am 10.06.2014 13:35, schrieb Neal Becker:

Submitting to IEEE conf.  They accept TeX.

If I try to give them the TeX output, they say they need dvi, and
all figures in eps (what is this, 1980??)

If I try to export to dvi from lyx, I get:

---
! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H return  for immediate help.
  ...
   
l.13  Vazquez-Castro, and A.~Morello, ``{DVB��

   �S2 ACM} modes for
You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.


! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H return  for immediate help.
  ...
   
l.13 ... Vazquez-Castro, and A.~Morello, ``{DVB‐

   S2 ACM} modes for
You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.
--

If I select dvi (LuaTeX) export, lyx does not complain.  But then if I test the
dvi myself, I get:

dvipdf vhtpaper.dvi
dvips: ! invalid char 8208 from font ec-lmr8

Re: paper accepted for publication, but need help!

[Neal Becker]

The problem is triggered by my .bib entry, which includes a non-ascii character:

  author =   {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

By playing with lyx Document/Settings/Encoding, selecting unicode XeTeX 
(utf-8), 
I seem to be able to export dvi and then convert dvipdf OK.

So is this a good procedure, or is something else recommended here?

Neal Becker wrote:

 Submitting to IEEE conf.  They accept TeX.
 
 If I try to give them the TeX output, they say they need dvi, and
 all figures in eps (what is this, 1980??)
 
 If I try to export to dvi from lyx, I get:
 
 ---
 ! Package inputenc Error: Keyboard character used is undefined
 (inputenc)in inputencoding `latin9'.
 
 See the inputenc package documentation for explanation.
 Type  H return  for immediate help.
  ...
   
 l.13  Vazquez-Castro, and A.~Morello, ``{DVB��
   �S2 ACM} modes for
 You need to provide a definition with \DeclareInputText
 or \DeclareInputMath before using this key.
 
 
 ! Package inputenc Error: Keyboard character used is undefined
 (inputenc)in inputencoding `latin9'.
 
 See the inputenc package documentation for explanation.
 Type  H return  for immediate help.
  ...
   
 l.13 ... Vazquez-Castro, and A.~Morello, ``{DVB‐
   S2 ACM} modes for
 You need to provide a definition with \DeclareInputText
 or \DeclareInputMath before using this key.
 --
 
 If I select dvi (LuaTeX) export, lyx does not complain.  But then if I test
 the dvi myself, I get:
 
 dvipdf vhtpaper.dvi
 dvips: ! invalid char 8208 from font ec-lmr8

Re: paper accepted for publication, but need help!

[Jean-Marc Lasgouttes]

10/06/2014 13:49, Neal Becker:

The problem is triggered by my .bib entry, which includes a non-ascii character:

   author =  {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

By playing with lyx Document/Settings/Encoding, selecting unicode XeTeX (utf-8),
I seem to be able to export dvi and then convert dvipdf OK.

So is this a good procedure, or is something else recommended here?


You should use the same encoding for your document and the LyX output 
encoding. A workaround is to use LaTeX markup in the .bib file so that 
it is compatible with any encoding.


JMarc

paper accepted for publication, but need help!

[Neal Becker]

Submitting to IEEE conf.  They accept TeX.

If I try to give them the TeX output, they say they need dvi, and
all figures in eps (what is this, 1980??)

If I try to export to dvi from lyx, I get:

---
! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H   for immediate help.
 ...  
  
l.13  Vazquez-Castro, and A.~Morello, ``{DVB��
  �S2 ACM} modes for
You need to provide a definition with \DeclareInputText 
or \DeclareInputMath before using this key.


! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H   for immediate help.
 ...  
  
l.13 ... Vazquez-Castro, and A.~Morello, ``{DVB‐
  S2 ACM} modes for
You need to provide a definition with \DeclareInputText 
or \DeclareInputMath before using this key.
--

If I select dvi (LuaTeX) export, lyx does not complain.  But then if I test the 
dvi myself, I get:

dvipdf vhtpaper.dvi
dvips: ! invalid char 8208 from font ec-lmr8

Re: paper accepted for publication, but need help!

[Wolfgang Engelmann]

I guess, if you take out the ref: Vazquez-Castro, and A.~Morello the error is 
gone. Check carefully the reference, perhaps by adding parts only (eg only the 
first word of the title, journal etc)
Wolfgang

Am 10.06.2014 13:35, schrieb Neal Becker:

Submitting to IEEE conf.  They accept TeX.

If I try to give them the TeX output, they say they need dvi, and
all figures in eps (what is this, 1980??)

If I try to export to dvi from lyx, I get:

---
! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H   for immediate help.
  ...
   
l.13  Vazquez-Castro, and A.~Morello, ``{DVB��

   �S2 ACM} modes for
You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.


! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `latin9'.

See the inputenc package documentation for explanation.
Type  H   for immediate help.
  ...
   
l.13 ... Vazquez-Castro, and A.~Morello, ``{DVB‐

   S2 ACM} modes for
You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.
--

If I select dvi (LuaTeX) export, lyx does not complain.  But then if I test the
dvi myself, I get:

dvipdf vhtpaper.dvi
dvips: ! invalid char 8208 from font ec-lmr8

Re: paper accepted for publication, but need help!

[Neal Becker]

The problem is triggered by my .bib entry, which includes a non-ascii character:

  author =   {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

By playing with lyx Document/Settings/Encoding, selecting unicode XeTeX 
(utf-8), 
I seem to be able to export dvi and then convert dvipdf OK.

So is this a "good" procedure, or is something else recommended here?

Neal Becker wrote:

> Submitting to IEEE conf.  They accept TeX.
> 
> If I try to give them the TeX output, they say they need dvi, and
> all figures in eps (what is this, 1980??)
> 
> If I try to export to dvi from lyx, I get:
> 
> ---
> ! Package inputenc Error: Keyboard character used is undefined
> (inputenc)in inputencoding `latin9'.
> 
> See the inputenc package documentation for explanation.
> Type  H   for immediate help.
>  ...
>   
> l.13  Vazquez-Castro, and A.~Morello, ``{DVB��
>   �S2 ACM} modes for
> You need to provide a definition with \DeclareInputText
> or \DeclareInputMath before using this key.
> 
> 
> ! Package inputenc Error: Keyboard character used is undefined
> (inputenc)in inputencoding `latin9'.
> 
> See the inputenc package documentation for explanation.
> Type  H   for immediate help.
>  ...
>   
> l.13 ... Vazquez-Castro, and A.~Morello, ``{DVB‐
>   S2 ACM} modes for
> You need to provide a definition with \DeclareInputText
> or \DeclareInputMath before using this key.
> --
> 
> If I select dvi (LuaTeX) export, lyx does not complain.  But then if I test
> the dvi myself, I get:
> 
> dvipdf vhtpaper.dvi
> dvips: ! invalid char 8208 from font ec-lmr8

Re: paper accepted for publication, but need help!

[Jean-Marc Lasgouttes]

10/06/2014 13:49, Neal Becker:

The problem is triggered by my .bib entry, which includes a non-ascii character:

   author =  {Wojciech Bruzda and Wojciech Tadej and Karol Życzkowski},

By playing with lyx Document/Settings/Encoding, selecting unicode XeTeX (utf-8),
I seem to be able to export dvi and then convert dvipdf OK.

So is this a "good" procedure, or is something else recommended here?


You should use the same encoding for your document and the LyX output 
encoding. A workaround is to use LaTeX markup in the .bib file so that 
it is compatible with any encoding.


JMarc