Re: paper accepted for publication, but need help!

2014-06-12 Thread 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!

2014-06-12 Thread 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!

2014-06-12 Thread 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


Trouble reading EMF and EPS graphic files

2014-06-12 Thread Samuel Gamtessa
Hello,
 
I have encountered a strange problem that I never did before.
 
The graphic files in .eps and .emf files are not properly read anymore, showing 
a message error connecting to a readable format 
 
I have never encountered this previously except that on a mac, I needed a 
separate software called eps to pdf. I am working on a pc currently and I did 
not face this trouble previously.
 
What might cause such a problem?
 
thanks!


Error SIGSEGV

2014-06-12 Thread Francesco Menoncin

Dear LyX users,

I am using LyX 2.1 on Xubuntu 13.04 and I have the following problem: 
when I have a file containing just one TeX inset (like in the attached 
file for the case of an R command with Knitr) and I try to close it with 
the mouse right botton, I receive a SIGSEGV error and I have to quit LyX.


This happens only when there is no text in the file. Instead, when there 
is some text, I am able to close the TeX inset as usual.


Francesco

--

Francesco Menoncin
Università degli Studi di Brescia
Dipartimento di Economia e Management
Via S. Faustino, 74/B
25122 Brescia (Italy)
Tel: 0039-030-2988806
Fax: 0039-030-2988837
E-mail: francesco.menon...@unibs.it
web: www.eco.unibs.it/~menoncin/
 sites.google.com/site/francescomenoncin/



--
Informativa sulla Privacy: http://www.unibs.it/node/8155


knitr.lyx
Description: application/lyx


Re: Error SIGSEGV

2014-06-12 Thread Richard Heck

On 06/12/2014 11:58 AM, Francesco Menoncin wrote:

Dear LyX users,

I am using LyX 2.1 on Xubuntu 13.04 and I have the following problem: 
when I have a file containing just one TeX inset (like in the attached 
file for the case of an R command with Knitr) and I try to close it 
with the mouse right botton, I receive a SIGSEGV error and I have to 
quit LyX.


This happens only when there is no text in the file. Instead, when 
there is some text, I am able to close the TeX inset as usual.


I believe this has been fixed for 2.1.1.

Richard



Re: Python Graphics in LyX [was: Python bindings]

2014-06-12 Thread Ross Reyes


On 6/11/2014 12:41 PM, Rainer M Krug wrote:


Envoyé de mon iPhone


Le 11 juin 2014 à 16:07, Ross Reyes philip_...@yahoo.com a écrit :


Hi Alex,

I still get the error converting to loadable format message.

I can run the python script from the command line and it does work.   I can
and have modified the .pygr script to produce other outputs in .png, .jpg, .ps, 
etc.
without problem.

But inside LyX, regardless of what I do to define the converter,  I can not get 
the image
to render nor can I produce a .pdf output from the LyX doc.

Something is not right.   I am using LyX 2.0.1

The converters are defined in the configuration file LyX. If you could take a 
loom at it and post the lines where you file formats and the converters are 
defined, one could see if there is something wrong. I don't have LyX at hand, 
so I can't give you the location of the config file.

Cheers,

Rainer

Hi Rainer,   I have this in my preferences file for pygr fomat and 
converter.


#
# FORMATS SECTION ##
#

\format pdf4 pdf PDF (xelatex)document,vector,menu=export
\format pygr pygr Python Graphics  auto auto vector
\default_view_format ps

#
# CONVERTERS SECTION ##
#

\converter pdflatex pdf4 xelatex $$i latex=pdflatex
\converter eps png epstopng.bat $$i 
\converter pygr png python $$i $$o 





Re: paper accepted for publication, but need help!

2014-06-12 Thread 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: Error SIGSEGV

2014-06-12 Thread Scott Kostyshak
Thanks for the report and nice *reproducible* example of the bug -- I
love bug reports from knitr users :)

On Thu, Jun 12, 2014 at 12:07 PM, Richard Heck rgh...@lyx.org wrote:

 I believe this has been fixed for 2.1.1.

I can confirm that on 2.2dev, this problem has been fixed. Francesco,
if you see the bug again in the next release of LyX, please let us
know. The correct mailing list is lyx-de...@lists.lyx.org or you can
post any bugs/feature requests on http://www.lyx.org/trac

Thanks,

Scott


Re: Python Graphics in LyX [was: Python bindings]

2014-06-12 Thread Alex Vergara Gil
- Original Message - From: Ross Reyes philip_...@yahoo.com Sent: 
Thursday, June 12, 2014 12:50 PM


On 6/11/2014 12:41 PM, Rainer M Krug wrote:


Envoyé de mon iPhone


Le 11 juin 2014 à 16:07, Ross Reyes philip_...@yahoo.com a écrit :


Hi Alex,

I still get the error converting to loadable format message.

I can run the python script from the command line and it does work.   I 
can
and have modified the .pygr script to produce other outputs in .png, 
.jpg, .ps, etc.

without problem.


If the scripts work fine outside LyX then your problem is with your LyX 
instalation. The only thing I can suggest is to update at least to version 
2.0.3 which is the one I have tested in my debian system.




But inside LyX, regardless of what I do to define the converter,  I can 
not get the image

to render nor can I produce a .pdf output from the LyX doc.

Something is not right.   I am using LyX 2.0.1
The converters are defined in the configuration file LyX. If you could 
take a loom at it and post the lines where you file formats and the 
converters are defined, one could see if there is something wrong. I 
don't have LyX at hand, so I can't give you the location of the config 
file.


Cheers,

Rainer

Hi Rainer,   I have this in my preferences file for pygr fomat and 
converter.


#
# FORMATS SECTION ##
#

\format pdf4 pdf PDF (xelatex)
document,vector,menu=export

\format pygr pygr Python Graphics  auto auto vector
\default_view_format ps

#
# CONVERTERS SECTION ##
#

\converter pdflatex pdf4 xelatex $$i latex=pdflatex
\converter eps png epstopng.bat $$i 
\converter pygr png python $$i $$o 



All of this seems ok, take into account that if you are on Windows the 
correct converter line should be

\converter pygr png python -tt $$i $$o 

but it would be better if you to have
\converter pygr eps python $$i $$o  on Linux
\converter pygr eps python -tt $$i $$o  on Windows 



Re: paper accepted for publication, but need help!

2014-06-12 Thread 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!

2014-06-12 Thread 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!

2014-06-12 Thread 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


Trouble reading EMF and EPS graphic files

2014-06-12 Thread Samuel Gamtessa
Hello,
 
I have encountered a strange problem that I never did before.
 
The graphic files in .eps and .emf files are not properly read anymore, showing 
a message error connecting to a readable format 
 
I have never encountered this previously except that on a mac, I needed a 
separate software called eps to pdf. I am working on a pc currently and I did 
not face this trouble previously.
 
What might cause such a problem?
 
thanks!


Error SIGSEGV

2014-06-12 Thread Francesco Menoncin

Dear LyX users,

I am using LyX 2.1 on Xubuntu 13.04 and I have the following problem: 
when I have a file containing just one TeX inset (like in the attached 
file for the case of an R command with Knitr) and I try to close it with 
the mouse right botton, I receive a SIGSEGV error and I have to quit LyX.


This happens only when there is no text in the file. Instead, when there 
is some text, I am able to close the TeX inset as usual.


Francesco

--

Francesco Menoncin
Università degli Studi di Brescia
Dipartimento di Economia e Management
Via S. Faustino, 74/B
25122 Brescia (Italy)
Tel: 0039-030-2988806
Fax: 0039-030-2988837
E-mail: francesco.menon...@unibs.it
web: www.eco.unibs.it/~menoncin/
 sites.google.com/site/francescomenoncin/



--
Informativa sulla Privacy: http://www.unibs.it/node/8155


knitr.lyx
Description: application/lyx


Re: Error SIGSEGV

2014-06-12 Thread Richard Heck

On 06/12/2014 11:58 AM, Francesco Menoncin wrote:

Dear LyX users,

I am using LyX 2.1 on Xubuntu 13.04 and I have the following problem: 
when I have a file containing just one TeX inset (like in the attached 
file for the case of an R command with Knitr) and I try to close it 
with the mouse right botton, I receive a SIGSEGV error and I have to 
quit LyX.


This happens only when there is no text in the file. Instead, when 
there is some text, I am able to close the TeX inset as usual.


I believe this has been fixed for 2.1.1.

Richard



Re: Python Graphics in LyX [was: Python bindings]

2014-06-12 Thread Ross Reyes


On 6/11/2014 12:41 PM, Rainer M Krug wrote:


Envoyé de mon iPhone


Le 11 juin 2014 à 16:07, Ross Reyes philip_...@yahoo.com a écrit :


Hi Alex,

I still get the error converting to loadable format message.

I can run the python script from the command line and it does work.   I can
and have modified the .pygr script to produce other outputs in .png, .jpg, .ps, 
etc.
without problem.

But inside LyX, regardless of what I do to define the converter,  I can not get 
the image
to render nor can I produce a .pdf output from the LyX doc.

Something is not right.   I am using LyX 2.0.1

The converters are defined in the configuration file LyX. If you could take a 
loom at it and post the lines where you file formats and the converters are 
defined, one could see if there is something wrong. I don't have LyX at hand, 
so I can't give you the location of the config file.

Cheers,

Rainer

Hi Rainer,   I have this in my preferences file for pygr fomat and 
converter.


#
# FORMATS SECTION ##
#

\format pdf4 pdf PDF (xelatex)document,vector,menu=export
\format pygr pygr Python Graphics  auto auto vector
\default_view_format ps

#
# CONVERTERS SECTION ##
#

\converter pdflatex pdf4 xelatex $$i latex=pdflatex
\converter eps png epstopng.bat $$i 
\converter pygr png python $$i $$o 





Re: paper accepted for publication, but need help!

2014-06-12 Thread 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: Error SIGSEGV

2014-06-12 Thread Scott Kostyshak
Thanks for the report and nice *reproducible* example of the bug -- I
love bug reports from knitr users :)

On Thu, Jun 12, 2014 at 12:07 PM, Richard Heck rgh...@lyx.org wrote:

 I believe this has been fixed for 2.1.1.

I can confirm that on 2.2dev, this problem has been fixed. Francesco,
if you see the bug again in the next release of LyX, please let us
know. The correct mailing list is lyx-de...@lists.lyx.org or you can
post any bugs/feature requests on http://www.lyx.org/trac

Thanks,

Scott


Re: Python Graphics in LyX [was: Python bindings]

2014-06-12 Thread Alex Vergara Gil
- Original Message - From: Ross Reyes philip_...@yahoo.com Sent: 
Thursday, June 12, 2014 12:50 PM


On 6/11/2014 12:41 PM, Rainer M Krug wrote:


Envoyé de mon iPhone


Le 11 juin 2014 à 16:07, Ross Reyes philip_...@yahoo.com a écrit :


Hi Alex,

I still get the error converting to loadable format message.

I can run the python script from the command line and it does work.   I 
can
and have modified the .pygr script to produce other outputs in .png, 
.jpg, .ps, etc.

without problem.


If the scripts work fine outside LyX then your problem is with your LyX 
instalation. The only thing I can suggest is to update at least to version 
2.0.3 which is the one I have tested in my debian system.




But inside LyX, regardless of what I do to define the converter,  I can 
not get the image

to render nor can I produce a .pdf output from the LyX doc.

Something is not right.   I am using LyX 2.0.1
The converters are defined in the configuration file LyX. If you could 
take a loom at it and post the lines where you file formats and the 
converters are defined, one could see if there is something wrong. I 
don't have LyX at hand, so I can't give you the location of the config 
file.


Cheers,

Rainer

Hi Rainer,   I have this in my preferences file for pygr fomat and 
converter.


#
# FORMATS SECTION ##
#

\format pdf4 pdf PDF (xelatex)
document,vector,menu=export

\format pygr pygr Python Graphics  auto auto vector
\default_view_format ps

#
# CONVERTERS SECTION ##
#

\converter pdflatex pdf4 xelatex $$i latex=pdflatex
\converter eps png epstopng.bat $$i 
\converter pygr png python $$i $$o 



All of this seems ok, take into account that if you are on Windows the 
correct converter line should be

\converter pygr png python -tt $$i $$o 

but it would be better if you to have
\converter pygr eps python $$i $$o  on Linux
\converter pygr eps python -tt $$i $$o  on Windows 



Re: paper accepted for publication, but need help!

2014-06-12 Thread 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!

2014-06-12 Thread 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!

2014-06-12 Thread 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


Trouble reading EMF and EPS graphic files

2014-06-12 Thread Samuel Gamtessa
Hello,
 
I have encountered a strange problem that I never did before.
 
The graphic files in .eps and .emf files are not properly read anymore, showing 
a message "error connecting to a readable format" 
 
I have never encountered this previously except that on a mac, I needed a 
separate software called "eps to pdf." I am working on a pc currently and I did 
not face this trouble previously.
 
What might cause such a problem?
 
thanks!


Error SIGSEGV

2014-06-12 Thread Francesco Menoncin

Dear LyX users,

I am using LyX 2.1 on Xubuntu 13.04 and I have the following problem: 
when I have a file containing just one TeX inset (like in the attached 
file for the case of an R command with Knitr) and I try to close it with 
the mouse right botton, I receive a SIGSEGV error and I have to quit LyX.


This happens only when there is no text in the file. Instead, when there 
is some text, I am able to close the TeX inset as usual.


Francesco

--

Francesco Menoncin
Università degli Studi di Brescia
Dipartimento di Economia e Management
Via S. Faustino, 74/B
25122 Brescia (Italy)
Tel: 0039-030-2988806
Fax: 0039-030-2988837
E-mail: francesco.menon...@unibs.it
web: www.eco.unibs.it/~menoncin/
 sites.google.com/site/francescomenoncin/



--
Informativa sulla Privacy: http://www.unibs.it/node/8155


knitr.lyx
Description: application/lyx


Re: Error SIGSEGV

2014-06-12 Thread Richard Heck

On 06/12/2014 11:58 AM, Francesco Menoncin wrote:

Dear LyX users,

I am using LyX 2.1 on Xubuntu 13.04 and I have the following problem: 
when I have a file containing just one TeX inset (like in the attached 
file for the case of an R command with Knitr) and I try to close it 
with the mouse right botton, I receive a SIGSEGV error and I have to 
quit LyX.


This happens only when there is no text in the file. Instead, when 
there is some text, I am able to close the TeX inset as usual.


I believe this has been fixed for 2.1.1.

Richard



Re: Python Graphics in LyX [was: Python bindings]

2014-06-12 Thread Ross Reyes


On 6/11/2014 12:41 PM, Rainer M Krug wrote:


Envoyé de mon iPhone


Le 11 juin 2014 à 16:07, Ross Reyes  a écrit :


Hi Alex,

I still get the "error converting to loadable format" message.

I can run the python script from the command line and it does work.   I can
and have modified the .pygr script to produce other outputs in .png, .jpg, .ps, 
etc.
without problem.

But inside LyX, regardless of what I do to define the converter,  I can not get 
the image
to render nor can I produce a .pdf output from the LyX doc.

Something is not right.   I am using LyX 2.0.1

The converters are defined in the configuration file LyX. If you could take a 
loom at it and post the lines where you file formats and the converters are 
defined, one could see if there is something wrong. I don't have LyX at hand, 
so I can't give you the location of the config file.

Cheers,

Rainer

Hi Rainer,   I have this in my preferences file for pygr fomat and 
converter.


#
# FORMATS SECTION ##
#

\format "pdf4" "pdf" "PDF (xelatex)" "" "" "" "document,vector,menu=export"
\format "pygr" "pygr" "Python Graphics" "" "auto" "auto" "vector"
\default_view_format ps

#
# CONVERTERS SECTION ##
#

\converter "pdflatex" "pdf4" "xelatex $$i" "latex=pdflatex"
\converter "eps" "png" "epstopng.bat $$i" ""
\converter "pygr" "png" "python $$i $$o" ""





Re: paper accepted for publication, but need help!

2014-06-12 Thread 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: Error SIGSEGV

2014-06-12 Thread Scott Kostyshak
Thanks for the report and nice *reproducible* example of the bug -- I
love bug reports from knitr users :)

On Thu, Jun 12, 2014 at 12:07 PM, Richard Heck  wrote:

> I believe this has been fixed for 2.1.1.

I can confirm that on 2.2dev, this problem has been fixed. Francesco,
if you see the bug again in the next release of LyX, please let us
know. The correct mailing list is lyx-de...@lists.lyx.org or you can
post any bugs/feature requests on http://www.lyx.org/trac

Thanks,

Scott


Re: Python Graphics in LyX [was: Python bindings]

2014-06-12 Thread Alex Vergara Gil
- Original Message - From: "Ross Reyes"  Sent: 
Thursday, June 12, 2014 12:50 PM


On 6/11/2014 12:41 PM, Rainer M Krug wrote:


Envoyé de mon iPhone


Le 11 juin 2014 à 16:07, Ross Reyes  a écrit :


Hi Alex,

I still get the "error converting to loadable format" message.

I can run the python script from the command line and it does work.   I 
can
and have modified the .pygr script to produce other outputs in .png, 
.jpg, .ps, etc.

without problem.


If the scripts work fine outside LyX then your problem is with your LyX 
instalation. The only thing I can suggest is to update at least to version 
2.0.3 which is the one I have tested in my debian system.




But inside LyX, regardless of what I do to define the converter,  I can 
not get the image

to render nor can I produce a .pdf output from the LyX doc.

Something is not right.   I am using LyX 2.0.1
The converters are defined in the configuration file LyX. If you could 
take a loom at it and post the lines where you file formats and the 
converters are defined, one could see if there is something wrong. I 
don't have LyX at hand, so I can't give you the location of the config 
file.


Cheers,

Rainer

Hi Rainer,   I have this in my preferences file for pygr fomat and 
converter.


#
# FORMATS SECTION ##
#

\format "pdf4" "pdf" "PDF (xelatex)" "" "" "" 
"document,vector,menu=export"

\format "pygr" "pygr" "Python Graphics" "" "auto" "auto" "vector"
\default_view_format ps

#
# CONVERTERS SECTION ##
#

\converter "pdflatex" "pdf4" "xelatex $$i" "latex=pdflatex"
\converter "eps" "png" "epstopng.bat $$i" ""
\converter "pygr" "png" "python $$i $$o" ""



All of this seems ok, take into account that if you are on Windows the 
correct converter line should be

\converter "pygr" "png" "python -tt $$i $$o" ""

but it would be better if you to have
\converter "pygr" "eps" "python $$i $$o" "" on Linux
\converter "pygr" "eps" "python -tt $$i $$o" "" on Windows