Re: Missing bracket errors

[Maria Gouskova]

Yep, doing this right now--I think I only really need the bibtex/bst
directory, anyway.

On Wed, Sep 25, 2024 at 6:49 AM Jürgen Spitzmüller 
wrote:

> Am Mittwoch, dem 25.09.2024 um 06:47 -0400 schrieb Maria Gouskova:
> > A happy ending to this story: I moved my home/me/texmf directory
> > somewhere else temporarily, and both files are compiling fine now. I
> > have no idea which package was causing the error, but that was indeed
> > the source of these bugs.
>
> Good to know. Maybe re-enter the files one by one to find the bad guy.
>
> --
> Jürgen
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Missing bracket errors

[Jürgen Spitzmüller]

Am Mittwoch, dem 25.09.2024 um 06:47 -0400 schrieb Maria Gouskova:
> A happy ending to this story: I moved my home/me/texmf directory
> somewhere else temporarily, and both files are compiling fine now. I
> have no idea which package was causing the error, but that was indeed
> the source of these bugs.

Good to know. Maybe re-enter the files one by one to find the bad guy.

-- 
Jürgen
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Missing bracket errors

[Maria Gouskova]

A happy ending to this story: I moved my home/me/texmf directory somewhere
else temporarily, and both files are compiling fine now. I have no idea
which package was causing the error, but that was indeed the source of
these bugs. Thanks, Jürgen!

On Tue, Sep 24, 2024 at 12:14 PM Jürgen Spitzmüller 
wrote:

> Am Montag, dem 23.09.2024 um 12:47 -0400 schrieb Maria Gouskova:
> > Follow-up: I was able to compile as PDF every other manual in LyX,
> > except for two: Embedded Objects (as described earlier), and,
> > ironically, Linguistics (for an unrelated, much simpler reason--see
> > error screenshot below).
> >
> > A closer look at the Embedded Objects file tells me it's full of
> > tables with multiple columns and all sorts of complicated stuff
> > inside the tables, so it's like the files that are giving me this
> > problem.
>
> It really looks like a problem with your installation. Can you check
> whether you have up-to-date packages and maybe older packages
> interfering from your personal tex path?
>
> --
> Jürgen
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
>
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Missing bracket errors

[Jürgen Spitzmüller]

Am Montag, dem 23.09.2024 um 12:47 -0400 schrieb Maria Gouskova:
> Follow-up: I was able to compile as PDF every other manual in LyX,
> except for two: Embedded Objects (as described earlier), and,
> ironically, Linguistics (for an unrelated, much simpler reason--see
> error screenshot below). 
> 
> A closer look at the Embedded Objects file tells me it's full of
> tables with multiple columns and all sorts of complicated stuff
> inside the tables, so it's like the files that are giving me this
> problem.

It really looks like a problem with your installation. Can you check
whether you have up-to-date packages and maybe older packages
interfering from your personal tex path?

-- 
Jürgen
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Missing bracket errors

[Jürgen Spitzmüller]

Am Montag, dem 23.09.2024 um 10:35 -0400 schrieb Maria Gouskova:
> I can't provide a MWE because it happens unpredictably, but I did
> encounter a version of my problem in a setting that others might
> reproduce: about a million missing bracket errors while trying to
> make a PDF of the Embedded Objects lyx file.

Just a shot in the dark: does it help if you select "Put
fragile content out of moving arguments" in Document >
Settings > Output?

The only error in your log is due to a missing graphic.

-- 
Jürgen
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Missing bracket errors

[Jürgen Spitzmüller]

Am Dienstag, dem 27.08.2024 um 18:20 -0400 schrieb Maria Gouskova:
> This is a general question. For the past few years--can't be sure how
> long it's been--I've been seeing an increasing number of "Missing }
> inserted" errors crop up. Usually it will happen in a table of some
> complexity (bibliography references inside a table, IPA fonts, merged
> rows/columns, etc.), but not necessarily a table containing LaTeX
> code. It's frustrating to encounter these, because I haven't inserted
> any { brackets, so there shouldn't be any } ones, missing or
> otherwise.
> 
> I'm currently on Lyx 2.4.1, but it's been an issue for quite a few
> versions running now. 
> 
> My usual approach toward debugging these errors is to comment out the
> offending portion of the text, usually a table, and to copy text into
> a new table bit by bit. It's slow and annoying. I'd like to know
> where these errors are coming from so I can hopefully avoid
> introducing them in the first place.

If you are able to provide us with minimal example files exposing these
errors, fixing them will be much easier.

-- 
Jürgen
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Missing bracket errors

[Maria Gouskova]

Hi LyX users,

This is a general question. For the past few years--can't be sure how long
it's been--I've been seeing an increasing number of "Missing } inserted"
errors crop up. Usually it will happen in a table of some complexity
(bibliography references inside a table, IPA fonts, merged rows/columns,
etc.), but not necessarily a table containing LaTeX code. It's frustrating
to encounter these, because I haven't inserted any { brackets, so there
shouldn't be any } ones, missing or otherwise.

I'm currently on Lyx 2.4.1, but it's been an issue for quite a few versions
running now.

My usual approach toward debugging these errors is to comment out the
offending portion of the text, usually a table, and to copy text into a new
table bit by bit. It's slow and annoying. I'd like to know where these
errors are coming from so I can hopefully avoid introducing them in the
first place.

Maria
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: How locate LyX errors

[Daniel]

On 2023-08-14 18:35, Herbert Voss wrote:



Am 14.08.23 um 16:07 schrieb Edwin Burmeister:


I am using LyX 2.3.7 on a Mac (silicon chip) running OS Ventura 13.5.


From LaTeX Errors window:


“Selecting an error ... the cursor will jump to the location in the 
document where the error occurred.”



This does not happen for me. How can I get it to work?


I then tried to locate my errors via line number. But putting


\usepackage[left,modulo]{lineno}

\linenumbers


in the LaTeX Preamble did not work.



No problem on my macOS. Export the document to LaTeX and run it.
Then you should see an error message.


Just to be sure: This answer sounds as if the normal way to hunt down 
LaTeX errors in LyX is to export to LaTeX. That is not so (and probably 
not what is meant). It should work directly from the LaTeX Errors window.


However, there are some exceptions. Most notably errors in the preamble. 
I don't think those can be found the way LyX suggests. And since, 
unfortunately, the code preview pane does not have proper line numbers, 
it is hard to track those errors down. In that case exporting to another 
editor might be a better way indeed.


Daniel

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: How locate LyX errors

[Herbert Voss]

Am 14.08.23 um 16:07 schrieb Edwin Burmeister:


I am using LyX 2.3.7 on a Mac (silicon chip) running OS Ventura 13.5.


From LaTeX Errors window:


“Selecting an error ... the cursor will jump to the location in the 
document where the error occurred.”



This does not happen for me. How can I get it to work?


I then tried to locate my errors via line number. But putting


\usepackage[left,modulo]{lineno}

\linenumbers


in the LaTeX Preamble did not work.



No problem on my macOS. Export the document to LaTeX and run it.
Then you should see an error message.

Herbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Need help locating LyX errors

[Richard Kimberly Heck]

On 8/13/23 15:12, Edwin Burmeister wrote:


Hi--


Need some LyX help.


I am using LyX 2.3.7 on a Mac (silicon chip) running OS Ventura 13.5.


From LaTeX Errors window:


“Selecting an error ... the cursor will jump to the location in the 
document where the error occurred.”



This does not happen for me. How can I get it to work?

Generally, this should work, but it may not in some cases. The code that 
tracks line locations is pretty complicated.


Note that you do have access to the full LaTeX log, which can help 
finding errors.


Riki


-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

How locate LyX errors

[Edwin Burmeister]

I am using LyX 2.3.7 on a Mac (silicon chip) running OS Ventura 13.5.


From LaTeX Errors window:


“Selecting an error ... the cursor will jump to the location in the document 
where the error occurred.”


This does not happen for me. How can I get it to work?


I then tried to locate my errors via line number. But putting


\usepackage[left,modulo]{lineno}

\linenumbers


in the LaTeX Preamble did not work.


How can I obtain line numbers as an aid for locating errors?


***
Edwin Burmeister
Research Professor of Economics Emeritus
Duke University
Commonwealth Professor of Economics Emeritus
University of Virginia
e...@econ.duke.edu<mailto:e...@econ.duke.edu>



-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Need help locating LyX errors

[Edwin Burmeister]

Hi--


Need some LyX help.


I am using LyX 2.3.7 on a Mac (silicon chip) running OS Ventura 13.5.


From LaTeX Errors window:


“Selecting an error ... the cursor will jump to the location in the document 
where the error occurred.”


This does not happen for me. How can I get it to work?


I then tried to locate my errors via line number. But putting


\usepackage[left,modulo]{lineno}

\linenumbers


in the LaTeX Preamble did not work.


How can I obtain line numbers as an aid for locating errors?


Thanks in advance for your help.


Ed


***
Edwin Burmeister
Research Professor of Economics Emeritus
Duke University
Commonwealth Professor of Economics Emeritus
University of Virginia
e...@econ.duke.edu<mailto:e...@econ.duke.edu>



-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

finding errors in lyx

[Wolfgang Engelmann via lyx-users]

In converting a bibtex document to a biblatex/luatex I have quite a lot 
of errors. I got an important tip by Frank Mittelbach (Dante e.V.):


put in the preamble

\tracinglostchars=3

The warning is converted to an error message and stops there, so that 
one can correct it (in my case often math stuff which is apparently not 
represented by the luatex)


It might be of help for others searching for warnings.

Wolfgasng

Here the German message:
Am 09.12.21 um 10:13 schrieb Frank Mittelbach:
> Am 09.12.21 um 09:22 schrieb Wolfgang Engelmann:
>>
>>  > Die einfachste Methode ist vermutlich zu schauen, an welcher Stelle
>>  > im Dokument sich LaTeX beschwert, und dann den Text an der Stelle zu
>>  > loeschen, und dann wieder manuell zu schreiben.
>
> und das geht am einfachsten, in dem man
>
> \tracinglostchars=3
>
> in der Präambel setzt, dann wird die Warnung eine Fehlermeldung und TeX
> hält a der Stelle an
>
> Frank
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: tkzpeople is throwing errors

[Joel Kulesza]

On Sat, Sep 1, 2018 at 7:56 PM, Anthony  wrote:

> I am trying to use tkzpeople package to place an object at a node.
>
>
>
> The MWE is attached, along with the error log.
>
> I am running MiKTeX 2.9 on windows 10 using LyX2.3.0
>
>
>
> Kind Regards,
>
> Anthony
>
>
>
> Sent from Mail  for
> Windows 10
>

If I comment out the last line in your preamble (the line below my
signature), then I don't get an error.  Do you need this line as part of
the MWE / eventual use case?

- Joel

%\pgfplotsset{width=10cm,compat=1.15}

>

Re: Lyx 2.2 errors w/ miktex 2.9.6 (on win10)

[Cris Fuhrman]

I can share a bit as a win10 user of 2.2.2.

One annoying quirk of LyX and MikTeX is the fact that MikTeX on-the-fly
installs can sometimes fail for weird but not rare reasons. For example,
you configured MikTeX to use server ABC but for some strange reason that
server's archive is broken and the package LyX needs fails a sanity check.
When these failures occur, LyX gives a vague answer, probably due to the
level of nesting. It wasn't until I ran MikTeX update as administrator that
I got the helpful message that let me know to switch servers. The average
user might not be so tolerant or persistent.  It's too bad the MikTeX
redundant system is not more robust.

Another problem I encounter is with long file paths, but only when using,
say, PNG images in my LyX files. LyX again fails with an obscure error.
Debugging the image conversion in the cache showed that my the filename was
really long and at some point the converted image was "not found". I moved
my LyX file directory to a path closer to the root, thus making the cache
file names shorter, and the errors stop. I can probably reproduce this
easily, if more info is needed.

On Apr 13, 2017 09:53, "Stephan Witt"  wrote:

> Am 13.04.2017 um 15:44 schrieb Mitch Gusat :
> >
> > Seen the same issues on Mac and Linux, but it's particularly vexing on
> Windows since the recent (April'17) Miktex 2.9 release: Lyx 2.0/1/2 used to
> work flawlessly for years before the new miktex release.
>
> Hi Mitch,
>
> I’d like to get more detailed infos regarding the problems you’ve
> mentioned for LyX on Mac.
>
> Thank you
> Stephan
>
>

Re: Lyx 2.2 errors w/ miktex 2.9.6 (on win10)

[Stephan Witt]

Am 13.04.2017 um 15:44 schrieb Mitch Gusat :
> 
> Seen the same issues on Mac and Linux, but it's particularly vexing on 
> Windows since the recent (April'17) Miktex 2.9 release: Lyx 2.0/1/2 used to 
> work flawlessly for years before the new miktex release.

Hi Mitch,

I’d like to get more detailed infos regarding the problems you’ve mentioned for 
LyX on Mac.

Thank you
Stephan

Lyx 2.2 errors w/ miktex 2.9.6 (on win10)

[Mitch Gusat]

Seen the same issues on Mac and Linux, but it's particularly vexing on
Windows since the recent (April'17) Miktex 2.9 release: Lyx 2.0/1/2 used to
work flawlessly for years before the new miktex release.

Now it needs multiple re-installs, remove miktex, re-install miktex,
reconfig Lyx, check Tex (still fails), check/edit Paths, reconfig again...
even the Lyx install bundle fails to do any better... :-(

Lyx was a great tool, yet the current issues w/ paths, Tex compilers,
missing styles etc. started long ago (similar reports from a decade ago).
Now they're aggravated by whatever Miktex has changed in miktex-2.9.6236

Can we help somehow to fix this hurdle?

I can't tell my colleagues and students to keep trying to fix a broken
Lyx/Miktex install ... until they get it right :-)

cheers and thanks for Lyx!

Cheers,
Mitch
-- 
Mitchell Gusat  -   IBM  Zurich  Research Laboratory
Saumerstrasse 4, CH-8803 Rueschlikon/Switzerland
Phone1: +41-44-724-8568 Fax: +41-44-724-8578
Master Inventor,Internet: gusat@{acm,ieee}.org

makefile errors 'recipe for target 'lyx' failed / ..for target 'all' failed

[Michael Berger]

Dear lyX friends,
I started to install Lyx 2.2.0

./configure
 went through and I was encouraged:
Type make to compile the program.
But that stopped and presented me the errors as per subject.
See also the log attached.

Could somebody please help?

Thanks and cheers,
Michael
[mb39@localhost ~]$ cd /home/mb39/Downloads/lyx-2.2.0
[mb39@localhost lyx-2.2.0]$ ./configure
configuring LyX version 2.2.0
checking for build type... release
checking for version suffix... 
checking whether Qt5 is requested... no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking what packaging should be used... posix
checking whether to enable maintainer-specific portions of Makefiles... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking for a Python interpreter with version >= 2.7.0 or 3.3.0... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... 
${exec_prefix}/lib64/python2.7/site-packages
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar   
  
checking the archiver (ar) interface... ar  
  
checking for ranlib... ranlib   
  
checking for g++... g++ 
  
checking whether we are using the GNU C++ compiler... yes   
  
checking whether g++ accepts -g... yes  
  
checking dependency style of g++... gcc3
  
checking how to run the C++ preprocessor... g++ -E  
  
checking for grep that handles long lines and -e... /usr/bin/grep   
  
checking for egrep... /usr/bin/grep -E  
  
checking for ANSI C header files... no  
  
checking for sys/types.h... yes 
  
checking for sys/stat.h... yes  
  
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether the compiler is clang... no
checking whether STL is libstdc++... yes
checking whether STL is libstdc++ using the C++11 ABI... no
checking whether the compiler implements C++11... yes
checking regex usability... yes
checking regex presence... yes
checking for regex... yes
checking for correct regex implementation... yes
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking dependency style of gcc... (cached) gcc3
checking for extra library directory... NONE
checking for extra include directory... NONE
checking for extra lib+include directory... NONE
checking for main in -lshlwapi... no
checking for main in -lpsapi... no
checking for main in -lgdi32... no
checking whether to use included boost library... yes
checking whether to use included MyThes library... yes
checking whether byte ordering is bigendian... no
checking whether printing callstack is possible... yes
checking size of wchar_t... 4
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for iconv... yes
checking for working iconv... yes
checking for iconv declaration... 
 extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, 

Re: typos in koma-letter2.lyx template preamble can cause errors

[Richard Talley]

​Richard Heck informs me this has been corrected. Way cool.
​

On Sun, Jun 5, 2016 at 11:12 PM, Richard Talley 
wrote:

> I've been working on learning more about KOMAScript classes and found a
> problem with the preamble that comes with the LyX koma-letter2 template
> (and has for some time).
>
> The preamble has a number of options in the \KOMAoptions section,
> including these lines:
>
> %pagenumber=botcenter%   position of the page number (see docu)
> %,parskip=false%  Use indent instead of skip (more options cf.
> docu)
> fromalign=center%alignment of the address
>
>
> The problem is that the first and third lines of this excerpt from the
> preamble lack leading commas (the KOMAoptions are comma delimited).
>
> If you uncomment the parskip option by removing the leading % then it gets
> parsed together with the fromalign option (because fromalign lacks a
> leading comma) and generates an 'undefined control sequence' error.
>
> Another confusion is that 'parskip=false' is the default for this document
> class. If you want a block style letter with no indents and a space between
> paragraphs you need to change this option to 'parskip=true'.
>
> -- Rich
>
>

typos in koma-letter2.lyx template preamble can cause errors

[Richard Talley]

I've been working on learning more about KOMAScript classes and found a
problem with the preamble that comes with the LyX koma-letter2 template
(and has for some time).

The preamble has a number of options in the \KOMAoptions section, including
these lines:

%pagenumber=botcenter%   position of the page number (see docu)
%,parskip=false%  Use indent instead of skip (more options cf. docu)
fromalign=center%alignment of the address


The problem is that the first and third lines of this excerpt from the
preamble lack leading commas (the KOMAoptions are comma delimited).

If you uncomment the parskip option by removing the leading % then it gets
parsed together with the fromalign option (because fromalign lacks a
leading comma) and generates an 'undefined control sequence' error.

Another confusion is that 'parskip=false' is the default for this document
class. If you want a block style letter with no indents and a space between
paragraphs you need to change this option to 'parskip=true'.

-- Rich

Re: in biblatex changing style=alphabetic to style=apa produces errors

[Michael Berger]

On 09/10/2015 09:03 AM, Jürgen Spitzmüller wrote:

2015-09-09 21:10 GMT+02:00 Michael Berger:

Dear Friends of LyX,
I have a well compiling LyX document using biblatex.
In the preamble I have the following entry:
*\usepackage**[**st**y**le**=**alphabetic,natbib
=true,backref=true,backend**=**biber,babel=hyphen]**{**biblatex}*
and in the LyX document see screen shot.
Because I want to switch to the apa style I studied the biblatex
reference manual, the wikilyx and other references I got hold of
and then changed style=alphabetic to style=apawhile everything
else seemingly was correct.
Errors:
Undefined control sequence (5 times)
Description:
\printbibliography[heading=bibintoc]
After removing the option[bibintoc] I got again 'Undefined control
sequence' 5 times, but without above description.

What could be wrong here?


Insert

\DeclareLanguageMapping{english}{english-apa}
\DeclareLanguageMapping{german}{german-apa}

etc. for any involved language after loading biblatex.

See the biblatex-apa manual for an exlantion why language mapping is 
needed here.


HTH
Jürgen

Hallo Jürgen,
it did not work with \DeclareLanguageMapping{english}{english-apa} (same 
error as before!)

Would be nice to know why!?
However, it did eventually work with 
\DeclareLanguageMapping{american}{american-apa} and after I changed 
'English' to 'English (USA)' in Documents > Settings > Language.


Jürgen,
once more I have to thank you very much for your precise and prompt help!
Cheers!
Michael

Re: in biblatex changing style=alphabetic to style=apa produces errors

[Jürgen Spitzmüller]

2015-09-09 21:10 GMT+02:00 Michael Berger:

> Dear Friends of LyX,
> I have a well compiling LyX document using biblatex.
> In the preamble I have the following entry:
> *\usepackage**[**st**y**le**=**alphabetic,natbib
> =true,backref=true,backend**=**biber,babel=hyphen]**{**biblatex}*
> and in the LyX document see screen shot.
> Because I want to switch to the apa style I studied the biblatex
> reference manual, the wikilyx and other references I got hold of and then
> changed style=alphabetic to style=apa while everything else seemingly was
> correct.
> Errors:
> Undefined control sequence (5 times)
> Description:
> \printbibliography[heading=bibintoc]
> After removing the option[bibintoc] I got again 'Undefined control
> sequence' 5 times, but without above description.
>
> What could be wrong here?
>

Insert

\DeclareLanguageMapping{english}{english-apa}
\DeclareLanguageMapping{german}{german-apa}

etc. for any involved language after loading biblatex.

See the biblatex-apa manual for an exlantion why language mapping is needed
here.

HTH
Jürgen


> Thanks and cheers,
>
>

in biblatex changing style=alphabetic to style=apa produces errors

[Michael Berger]

Dear Friends of LyX,
I have a well compiling LyX document using biblatex.
In the preamble I have the following entry:
*\usepackage**[**st**y**le**=**alphabetic,natbib 
=true,backref=true,backend**=**biber,babel=hyphen]**{**biblatex}*

and in the LyX document see screen shot.
Because I want to switch to the apa style I studied the biblatex 
reference manual, the wikilyx and other references I got hold of and 
then changed style=alphabetic to style=apawhile everything else 
seemingly was correct.

Errors:
Undefined control sequence (5 times)
Description:
\printbibliography[heading=bibintoc]
After removing the option[bibintoc] I got again 'Undefined control 
sequence' 5 times, but without above description.


What could be wrong here?
Thanks and cheers,

Michael Berger, Dipl. Ing.
Im Borngrund 7a
D-35606 Solms
id...@online.de
Fon: +49 6442 706509
Fax: 032121247536
Linux member

Re: Errors when using apacite for bibliography

[Simon Maina]

Florian  phpws.org> writes:

> 
> On Fri, 23 Nov 2012 18:09:30 +0800
>   Ray Rashif  gmail.com> wrote:
> > Try enabling Default citation style in preferences and then in
> > preamble save the following:
> > 
> > % Workaround for APA style (must turn off natbib first)
> > \usepackage{apacite}
> > \usepackage[authoryear]{natbib}
> 
> Thanks, this seems to resolve the problem.
> 
> Best, Florian
> 
> 


Hi Florian,
What other options did you set? Mine does not work still with the default
(natbib>numerical) and the packages loaded in that order.
My LyX file has the report class. Below is the LyX file exported to LaTeX:
%% LyX 2.0.1 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[english]{report}
\usepackage{lmodern}
\renewcommand{\ttdefault}{lmodern}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\setcounter{secnumdepth}{3}
\setcounter{tocdepth}{3}

\makeatletter

%% LyX specific LaTeX commands.
\providecommand{\LyX}{L\kern-.1667em\lower.25em\hbox{Y}\kern-.125emX\@}

%% User specified LaTeX commands.
%
\usepackage[american]{babel}
\usepackage{csquotes}

\usepackage{lmodern}

\usepackage{apacite}
\usepackage[authoryear]{natbib}


\usepackage{babel}
\begin{document}
\cite{Gilbert2004} said that APA6 is hard to implement in \LyX{}.
\cite{Herbst-Damm2005}

 \bibliographystyle{apacite}
\bibliography{apa6}
 
\end{document}

Re: Strategies for locating errors

[Will Furnass]

> Will Furnass wrote:
>>
>> If would be great if LyX would switch to/open the child document
>> containing the likely location of the error and move the cursor to that
>> location.

Ticket filed: http://www.lyx.org/trac/ticket/9539

Re: Strategies for locating errors

[Georg Baum]

Will Furnass wrote:

> On 5 May 2015 at 21:38, Georg Baum  wrote:
> 
>>
>> If you select the error item in the error dialog then the corresponding
>> LyX contents should should be selected in the main area as well. This is
>> not always 100% correct, but usually the error cause is nearby. Does this
>> not work in your case?
>>
> 
> Ah, I hadn't noticed that before!  That works perfectly if the error is in
> the master document but not if the error is in a child document (of which
> I have quite a few).
> 
> If would be great if LyX would switch to/open the child document
> containing the likely location of the error and move the cursor to that
> location.

I agree. Please file an enhancement request at 
http://www.lyx.org/trac/wiki/BugTrackerHome. It should not be too difficult 
to implement, since LyX has all information which is needed (which file and 
which line number). I guess it was simply forgotten.


Georg

Re: Strategies for locating errors

[Gordon Cooper]

On 06/05/15 09:57, Will Furnass wrote:

That works perfectly if the error is in the master document but not if
the error is in a child document (of which I have quite a few).


I have been having similar problems with errors, mainly relating to 
producing printable pdf versions
of a Software User Manual that has fairly frequent updates and changes. 
This manual is a team effort
written with Lyx with an on-line HTML version being the primary release 
format. The HTML does not
show some Latex errors but they do appear when a pdf conversion is 
attempted, and my team task

is to deal with the pdfs.

Error reports give a line number, which has been difficult to translate 
into a location in the Lyx file.
However, I'm now experimenting with the Latex Editor, Texmaker.  It 
appears to happily present the
Lyx files, all with line numbers. Perhaps this will help my error 
finding, we can but see.


Gordon
Tauranga
New Zealand.

Re: Strategies for locating errors

[Will Furnass]

On 5 May 2015 at 21:38, Georg Baum  wrote:

>
> If you select the error item in the error dialog then the corresponding LyX
> contents should should be selected in the main area as well. This is not
> always 100% correct, but usually the error cause is nearby. Does this not
> work in your case?
>

Ah, I hadn't noticed that before!  That works perfectly if the error is in
the master document but not if the error is in a child document (of which I
have quite a few).

If would be great if LyX would switch to/open the child document containing
the likely location of the error and move the cursor to that location.

Will

Re: Strategies for locating errors

[Georg Baum]

Will Furnass wrote:

> How do others locate compilation errors in large multi-file documents?
> 
> I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
> relate that line number to the LyX source.  I then try exporting to tex
> using pdflatex into a temporary directory and search through all 16 tex
> files looking for errors on or near line 1052.

If you select the error item in the error dialog then the corresponding LyX 
contents should should be selected in the main area as well. This is not 
always 100% correct, but usually the error cause is nearby. Does this not 
work in your case?


Georg

Re: Strategies for locating errors

[Georg Baum]

Wolfgang Engelmann wrote:

> That was the reason I was asking a while ago, whether the latex source
> panel (under >view) could show the tex line number. But I was told it is
> not possible under lyx.

Why that? Of course it would only be possible if the panel is set to show 
the full source (otherwise the line number would be wrong), but in that case 
it should not be a problem.



Georg

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 15:06, Wolfgang Engelmann wrote:
> That was the reason I was asking a while ago, whether the latex
> source panel (under >view) could show the tex line number. But I was
> told it is not possible under lyx.

That would certainly be a step in the right direction.  Given that we
already have forward and backward search between LyX and a PDF viewer
using SyncTeX then something similar for LyX to/from TeX should be feasible.

Will

Re: Strategies for locating errors

[Wolfgang Engelmann]

Am 05.05.2015 um 15:18 schrieb Will Furnass:

On 05/05/15 13:27, Rainer M Krug wrote:

Will Furnass  writes:

could LyX be improved to make locating errors less manual
though? For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced
in error messages.

I am by no means a LaTeX expert -0 so I might be wrong, but - the
LaTeX error messages are already quite cryptic, and the error you
quote (Missing } inserted' error for 'l.1052') means that the
missing "}" is inserted in this line - where it is actually
missing and what is causing this does not even LaTeX know - so
there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

That was the reason I was asking a while ago, whether the latex source 
panel (under >view) could show the tex line number. But I was told it is 
not possible under lyx.

Wolfgang

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 13:27, Rainer M Krug wrote:
> Will Furnass  writes:
>> 
>> could LyX be improved to make locating errors less manual
>> though? For example, if a mapping was generated at compile time
>> from LyX lines to TeX lines then buttons could be added to the
>> compilation pane to move the cursor between the lines referenced
>> in error messages.
> 
> I am by no means a LaTeX expert -0 so I might be wrong, but - the 
> LaTeX error messages are already quite cryptic, and the error you 
> quote (Missing } inserted' error for 'l.1052') means that the 
> missing "}" is inserted in this line - where it is actually
> missing and what is causing this does not even LaTeX know - so
> there is no chance that LyX will be able to tell you.

True, but the line number associated with a LaTeX error is a useful
clue when fault-finding and being able to quickly move the cursor to
the corresponding line in LyX could make fixing broken documents much
quicker in many situations.  The compilation pane could display a
caveat next to buttons for moving the cursor between error line
numbers saying something like 'the root cause of this error may not
lie at this location'.

Will

Re: Strategies for locating errors

[Rainer M Krug]

Will Furnass  writes:

> On 05/05/15 12:47, Nikos Alexandris wrote:
>> * Will Furnass  [2015-05-05 11:51:56 +0100]:
>> 
>>> How do others locate compilation errors in large multi-file documents?
>>>
> 
>> 
>> Something like "binary search": split in two halfs, try to find out
>> which half does not compile. Then, again, repeat the same: split in
>> half, identify the erroneous part. Sooner or later you'll nail the
>> source of the error.
>
> A good idea, but could LyX be improved to make locating errors less
> manual though?  For example, if a mapping was generated at compile time
> from LyX lines to TeX lines then buttons could be added to the
> compilation pane to move the cursor between the lines referenced in
> error messages.

I am by no means a LaTeX expert -0 so I might be wrong, but - the LaTeX
error messages are already quite cryptic, and the error you quote
(Missing } inserted' error for 'l.1052') means that the missing "}" is
inserted in this line - where it is actually missing and what is causing
this does not even LaTeX know - so there is no chance that LyX will be
able to tell you.

Rainer

>
> Will
>
>
>
>
>
>

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: Strategies for locating errors

[Will Furnass]

On 05/05/15 12:47, Nikos Alexandris wrote:
> * Will Furnass  [2015-05-05 11:51:56 +0100]:
> 
>> How do others locate compilation errors in large multi-file documents?
>>

> 
> Something like "binary search": split in two halfs, try to find out
> which half does not compile. Then, again, repeat the same: split in
> half, identify the erroneous part. Sooner or later you'll nail the
> source of the error.

A good idea, but could LyX be improved to make locating errors less
manual though?  For example, if a mapping was generated at compile time
from LyX lines to TeX lines then buttons could be added to the
compilation pane to move the cursor between the lines referenced in
error messages.

Will

Re: Strategies for locating errors

[Nikos Alexandris]

* Will Furnass  [2015-05-05 11:51:56 +0100]:

> How do others locate compilation errors in large multi-file documents?
> 
> I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
> relate that line number to the LyX source.  I then try exporting to tex
> using pdflatex into a temporary directory and search through all 16 tex
> files looking for errors on or near line 1052.
> 
> An alternative approach would have been to comment the
> 'includes'/'inputs' for various chapters of my thesis then try to
> recompile but this partitioning approach would be slow given that it
> currently takes ~5mins to compile my thesis.
> 
> I'm sure I can find the cause of the error eventually; I was just
> wondering if there were a neat way of identifying the location of
> errors.  At present pretty much everything in LyX is a joy and very
> slick apart from locating the source of errors.
> 
> FYI, yes I am using a little Evil Red Text (to use \resizebox within
> table floats).

Something like "binary search": split in two halfs, try to find out
which half does not compile. Then, again, repeat the same: split in
half, identify the erroneous part. Sooner or later you'll nail the
source of the error.

Cheers, Nikos

Strategies for locating errors

[Will Furnass]

How do others locate compilation errors in large multi-file documents?

I get a 'Missing } inserted' error for 'l.1052' when compiling but can't
relate that line number to the LyX source.  I then try exporting to tex
using pdflatex into a temporary directory and search through all 16 tex
files looking for errors on or near line 1052.

An alternative approach would have been to comment the
'includes'/'inputs' for various chapters of my thesis then try to
recompile but this partitioning approach would be slow given that it
currently takes ~5mins to compile my thesis.

I'm sure I can find the cause of the error eventually; I was just
wondering if there were a neat way of identifying the location of
errors.  At present pretty much everything in LyX is a joy and very
slick apart from locating the source of errors.

FYI, yes I am using a little Evil Red Text (to use \resizebox within
table floats).

Cheers,

Will

Re: Latex Errors

[Gordon Cooper]

On 18/01/15 18:31, Scott Kostyshak wrote:
>
> Hi Gordon,
>
> Are you able to give a reproducible example? For example, if you can
> give a small .lyx file and give exactly the behavior (you mention
> "previously"), and the behavior you see now, perhaps with screen
> shots, that would give us a better idea of what's going on.
>
> Best,
>
> Scott
>
  Hi Scott,
   I hope to supply this very soon. Problem I have is
that I corrected all the mistakes in the project - mainly by glaring
at the Source Pane looking for irregularities. 
Will try to write something with similar errors.

Regards,

Gordon

Re: Latex Errors

[Scott Kostyshak]

On Sat, Jan 10, 2015 at 7:23 PM, Gordon Cooper
 wrote:
>  While using Lyx to edit a moderately long technical manual (being
> written by others) and exporting it as pdf and html,  Latex errors
> have become difficult to find. Previously I could select an error and
> it would be highlighted in the Lyx script.   That highlighting has
> disappeared.   Is this function in  the texlive package?
>
> Using Lyx  2.1.2 in MX Linux.
>
> Gordon
> Tauranga N.Z.
>

Hi Gordon,

Are you able to give a reproducible example? For example, if you can
give a small .lyx file and give exactly the behavior (you mention
"previously"), and the behavior you see now, perhaps with screen
shots, that would give us a better idea of what's going on.

Best,

Scott

Latex Errors

[Gordon Cooper]

 While using Lyx to edit a moderately long technical manual (being
written by others) and exporting it as pdf and html,  Latex errors
have become difficult to find. Previously I could select an error and
it would be highlighted in the Lyx script.   That highlighting has
disappeared.   Is this function in  the texlive package?

Using Lyx  2.1.2 in MX Linux.

Gordon
Tauranga N.Z.

Re: Biber produces errors where bibtex8 does not

[Jürgen Spitzmüller]

2014-06-21 16:29 GMT+02:00 Benedict Holland:

> Which begs the question why are they not automatically escaped? I have a
> bibliography of over 70 references. Getting an item error because there is
> a problem in my references which has an easy workaround but hours of work
> tracing it to the source is bad.
>
Well, this is a task of the bibliography manager, not LyX.


> Can lyx or biber do preprocessing to fix these bugs?
>

biber probably can.

Jürgen


> Thanks,
> ~Ben
>

Re: Biber produces errors where bibtex8 does not

[Benedict Holland]

Which begs the question why are they not automatically escaped? I have a
bibliography of over 70 references. Getting an item error because there is
a problem in my references which has an easy workaround but hours of work
tracing it to the source is bad. Can lyx or biber do preprocessing to fix
these bugs?

Thanks,
~Ben
On Jun 21, 2014 3:53 AM, "Jürgen Spitzmüller"  wrote:

> 2014-06-20 23:47 GMT+02:00 Benedict Holland:
>
>> So it appears that the reason is that biber does not escape the abstract
>> of a reference, even if it doesn't at all display that abstract.
>> Specifically this is occurring if a percentage sign is within the abstract.
>> Apparently all percentage signs must be escaped? Is this a bug with lyx or
>> with biber?
>>
>
>
> Actually, I wonder why bibtex8 does not choke on this. These kind of
> characters need to be escaped in general.
>
> Jürgen
>
>

Re: Biber produces errors where bibtex8 does not

[Jürgen Spitzmüller]

2014-06-20 23:47 GMT+02:00 Benedict Holland:

> So it appears that the reason is that biber does not escape the abstract
> of a reference, even if it doesn't at all display that abstract.
> Specifically this is occurring if a percentage sign is within the abstract.
> Apparently all percentage signs must be escaped? Is this a bug with lyx or
> with biber?
>


Actually, I wonder why bibtex8 does not choke on this. These kind of
characters need to be escaped in general.

Jürgen

Re: Biber produces errors where bibtex8 does not

[Benedict Holland]

So it appears that the reason is that biber does not escape the abstract of
a reference, even if it doesn't at all display that abstract. Specifically
this is occurring if a percentage sign is within the abstract. Apparently
all percentage signs must be escaped? Is this a bug with lyx or with biber?

~Ben


On Fri, Jun 20, 2014 at 5:21 PM, Benedict Holland <
benedict.m.holl...@gmail.com> wrote:

> Hello,
>
> I tried using biber and biblatex following the instructions here:
>
> http://wiki.lyx.org/BibTeX/Biblatex
>
> I received some very strange errors like "Lonely \item - perhaps a missing
> list environment" when some of my references were included. It was actually
> 2/35 which were throwing the error except the error wasn't anywhere near
> those references. Even so, there was nothing wrong with the references and
> they worked perfectly well when generated using bibtex8. I examined the two
> references which caused problems and they were exactly the same as any
> other reference. Again, they work in bibtex8 but not biber.
>
> Does anyone know what could cause this error? When these two references
> are removed the document compiles but I need these references.
>
> ~Ben
>

Biber produces errors where bibtex8 does not

[Benedict Holland]

Hello,

I tried using biber and biblatex following the instructions here:

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

I received some very strange errors like "Lonely \item - perhaps a missing
list environment" when some of my references were included. It was actually
2/35 which were throwing the error except the error wasn't anywhere near
those references. Even so, there was nothing wrong with the references and
they worked perfectly well when generated using bibtex8. I examined the two
references which caused problems and they were exactly the same as any
other reference. Again, they work in bibtex8 but not biber.

Does anyone know what could cause this error? When these two references are
removed the document compiles but I need these references.

~Ben

Re: Tracking changes output errors

[Jürgen Spitzmüller]

2014-03-26 16:23 GMT+01:00 Andy :

> Hi people.
>
> I have a Ph.d thesis as a master document with various branches. I've been
> using track changes to edit individual chapters. My problem arise when I
> try to produce the Master document without showing changes. I keep getting
> ! Undefined control sequence.\lyxadded or \lyxdeleted. The document can be
> produced if I show changes in the output file. It is only one include file
> which causes these errors.
>

This is a known bug that will be fixed in forthcoming LyX 2.1.0 (but not
2.0.8). See
http://www.lyx.org/trac/ticket/8893

A workaround is to put this code to the preamble of the master:

 \DeclareRobustCommand{\lyxadded}[3]{#3}

\DeclareRobustCommand{\lyxdeleted}[3]{}

Jürgen


>
>
>

> Thanks for any help
>
> Andy
>

Tracking changes output errors

[Andy]

Hi people.

I have a Ph.d thesis as a master document with various branches. I've been
using track changes to edit individual chapters. My problem arise when I
try to produce the Master document without showing changes. I keep getting
! Undefined control sequence.\lyxadded or \lyxdeleted. The document can be
produced if I show changes in the output file. It is only one include file
which causes these errors.

I'm using ubuntu 12.10.4 (LTS) and have Lyx 2.0.6

Thanks for any help

Andy

Re: LyX generates errors on eps and pdf files produced by Stata

[Paul A . Rubin]

Are you sure the graphics files have not been changed in any way? If so, can
you post one here?

Paul

LyX generates errors on eps and pdf files produced by Stata

[Ly Tran]

Hello,

I recently decided to use LyX to write my thesis, and everything was going
just fine until yesterday. I woke up, turned on my computer, and LyX no
longer recognizes the graphic files (eps) that were produced by Stata. I
tried to change it to pdf and other types, but nothing worked. LyX still
reads other graphic files (jpg, bmp) just fine. As I said, these files
showed up nicely the day before yesterday, so I am very puzzled as for what
happened to my computer overnight.

On LyX GUI, it says "Error converting to loadable format." When I click
"view", an error message shows up "An error occured while running: epstopdf
-- outfile = "[some path, I assume to my eps file]""

If it was a pdf file, the error message is pdfTeX Error.

I looked for solutions online, but haven't found anything that works. I
also uninstalled everything (MikTeX, GhostScript, LyX), and then
reinstalled them, but still, the same error occurs. I am running LyX 2.0.6
on Windows 7.

I would really appreciate it if anybody could help me with this issue.
Thank you very much.


-- 
Ly Tran

Re: Lyx 2.0.6 Mac OS X Spell checker not underlying errors

[Miguel Ángel Artaso Landa]

Hi Scott,

The "Spellcheck continuously"was enabled but it was, as you pointed
out, a magnifying
problem. I use a 13.3" screen, 1280*800 resolution and I had set up
the magnifying at 140%. It needed to be, in my case, at least at 150%. I
didn't think of this possibility...

Thanks a lot,

Re: Lyx 2.0.6 Mac OS X Spell checker not underlying errors

[Scott Kostyshak]

On Sat, Jun 1, 2013 at 4:15 PM, Miguel Ángel Artaso Landa
 wrote:

> I've just installed Lyx 2.0.6 on Mac OS X 10.8.3. Since I upgraded the
> version of Lyx, the spell checker is not underlying in red the words that
> are not correctly spelled although when invoking the spell checker it is
> stopping in the words that need to be corrected. Is someone else suffering
> of this?

Hi Miguel,

What do you have in Tools > Preferences > Language Settings >
Spellchecker? Specifically, is "Spellcheck continuously" checked? If
not, check it. If it was already checked, then I'm guessing it's a
zooming issue. Try changing the zoom value. Does that help?

Scott

Lyx 2.0.6 Mac OS X Spell checker not underlying errors

[Miguel Ángel Artaso Landa]

Hi,

I've just installed Lyx 2.0.6 on Mac OS X 10.8.3. Since I upgraded the
version of Lyx, the spell checker is not underlying in red the words that
are not correctly spelled although when invoking the spell checker it is
stopping in the words that need to be corrected. Is someone else suffering
of this?

Regards,
Miguel A.

Errors with moderncv imported from latex

[nluetic]

Hello,

recently I decided to use moderncv to create a nice looking CV as PDF, which
works ok.

Now I wanted to export this to HTML and use lyx (2.0.3. coming with Ubuntu
12.10) for editing, which doesn't work as expected.

The imported latex file seemingly can be exported to HTML, as it says
"export successful", but the output is not ok:
it prints literal \items after the first itemize command inside a cventry.

Trying an export to pdf gives errors on every cventry, cvitem or
cvlistdoubleitem,.i.e.:
Paragraph ended before \\cvitem was complete.

I tried this with the example file template.tex coming with moderncv.

I tried with the current version 1.2.1 of moderncv after encountering the
problems described with the one preinstalled on Ubuntu 12.10. 

As the last posts hinting to similar difficulties date from years ago, I
suppose I must be missing something obvious. On the other hand some
workarounds and hints given then, could meanwhile be outdated:
http://www.mail-archive.com/lyx-users@lists.lyx.org/msg61970.html
The tip given here to treat the optional {} in the cventry, etc. definitions
as obligatory didn't help me.

Can anybody give me a hint, how I can use moderncv with lyx?





--
View this message in context: 
http://lyx.475766.n2.nabble.com/Errors-with-moderncv-imported-from-latex-tp7580202.html
Sent from the LyX - Users mailing list archive at Nabble.com.

Re: Insert->Float->Algorithm results in Latex errors

[José Matos]

On 12/27/2012 05:23 PM, Regina Anger wrote:
> Hi,
>
> Updating memoir helped, it works now like a charme. Thanks a lot!
> I wonder however, how can Fedora distribute packages *that* old.
>
> Thx, Regi

There are two reasons:
* due to the license of texlive packages (the license was incorrect
or non-free for some)
This process was finished around January of this year, when upstream
texlive finished the auditing of all packages

* time to integrate the changes necessary to Fedora packages, since
Fedora 17 was coming soon it was impossible to integrate those changes
on time, that is why the changes slipped to Fedora 18.

-- 
José Matos

RE: Insert->Float->Algorithm results in Latex errors

[Regina Anger]

Hi again,

> http://fedoraproject.org/wiki/Features/TeXLive (search for the
> instructions regarding Fedora 17)
> If you follow the instructions there you can update the packages to
> newer versions.
> 
> For Fedora 18 (to be released in January) and newer the packages there
> are the default.

Glad to know there are updated packages for F17 available, too.
Thanks for letting me know and for helping me with the memoir issue.

- Reggi
  

RE: Insert->Float->Algorithm results in Latex errors

[Regina Anger]

Hi,

Updating memoir helped, it works now like a charme. Thanks a lot!
I wonder however, how can Fedora distribute packages *that* old.

Thx, Regi
  

Re: Insert->Float->Algorithm results in Latex errors

[José Matos]

On 12/27/2012 04:07 PM, Regina Anger wrote:
> Does this mean I manually have to update my latex installation? Is
> there any way you can recommend, without re-compiling my whole
> software-stack?
> The whole situation is a bit sad, as I am sitting behind a ~100kBit/s
> GPRS line :/
>
> Thx, Reggi

For Fedora 17, there is the texlive-2012 repository that has all the
available packages:

http://fedoraproject.org/wiki/Features/TeXLive (search for the
instructions regarding Fedora 17)

If you follow the instructions there you can update the packages to
newer versions.

This repository was put in place by Fedora texlive maintainer and the
repository is a backport.

For Fedora 18 (to be released in January) and newer the packages there
are the default.

-- 
José Matos

Re: Insert->Float->Algorithm results in Latex errors

[Richard Heck]

On 12/27/2012 11:07 AM, Regina Anger wrote:

Hello Jürgen,


> Your file compiles fine here. This is with most recent TL 2012 and LyX
> 2.0.6dev. Maybe some of your packages are outdated. The versions are 
printed

> to the log file if you enter \listfiles into the preamble. Here's mine:

I am using the most recent packages (lyx, latex, ...) distributed with 
Fedora-17-updates:


*File List*

memoir.cls 2005/09/25 v1.618 configurable document class

mem10.clo 2002/07/27 v0.2 memoir class 10pt size option

mempatch.sty 2007/01/22 v4.8 Patches for memoir class v1.618

fontenc.sty

t1enc.def 2005/09/27 v1.99g Standard LaTeX file

inputenc.sty 2006/05/05 v1.1b Input encoding file

latin9.def 2006/05/05 v1.1b Input encoding file

float.sty 2001/11/08 v1.3d Float enhancements (AL)

amsthm.sty 2004/08/06 v2.20

amsmath.sty 2000/07/18 v2.13 AMS math features

amstext.sty 2000/06/29 v2.01

amsgen.sty 1999/11/30 v2.0

amsbsy.sty 1999/11/29 v1.2d

amsopn.sty 1999/12/14 v2.01 operator names


which seem to be *really* outdated, compared to the package-versions 
you list.


Does this mean I manually have to update my latex installation? Is 
there any way you can recommend, without re-compiling my whole 
software-stack?
The whole situation is a bit sad, as I am sitting behind a ~100kBit/s 
GPRS line :/


Ugh. Well, if you have a laptop and can take it somewhere with better 
speed, you might want to try using the updated TeXLive repository, as 
described here:

http://fedoraproject.org/wiki/Features/TeXLive
It takes a while to download it the first time, but then you should be OK.

Richard

Re: Insert->Float->Algorithm results in Latex errors

[Jürgen Spitzmüller]

Regina Anger wrote:
> Does this mean I manually have to update my latex installation? Is there any
> way you can recommend, without re-compiling my whole software-stack? The
> whole situation is a bit sad, as I am sitting behind a ~100kBit/s GPRS line
> :/

Probably updating memoir will suffice. You can grab the most recent version 
from CTAN [1], unpack the files by running "latex memoir.ins" and "latex 
mempatch.ins" and then put them in you TEXMF home directory (usually 
~/texmf/tex/latex/memoir). Run "texhash" afterwards to update the filename 
database.

HTH
Jürgen

[1] http://mirrors.ctan.org/macros/latex/contrib/memoir.zip

RE: Insert->Float->Algorithm results in Latex errors

[Regina Anger]

Hello Jürgen,


> Your file compiles fine here. This is with most recent TL 2012 and LyX 
> 2.0.6dev. Maybe some of your packages are outdated. The versions are printed 
> to the log file if you enter \listfiles into the preamble. Here's mine:

I am using the most recent packages (lyx, latex, ...) distributed with 
Fedora-17-updates:


 *File List*
  memoir.cls2005/09/25 v1.618 configurable document class
   mem10.clo2002/07/27 v0.2 memoir class 10pt size option
mempatch.sty2007/01/22 v4.8 Patches for memoir class v1.618
 fontenc.sty
   t1enc.def2005/09/27 v1.99g Standard LaTeX file
inputenc.sty2006/05/05 v1.1b Input encoding file
  latin9.def2006/05/05 v1.1b Input encoding file
   float.sty2001/11/08 v1.3d Float enhancements (AL)
  amsthm.sty2004/08/06 v2.20
 amsmath.sty2000/07/18 v2.13 AMS math features
 amstext.sty2000/06/29 v2.01
  amsgen.sty1999/11/30 v2.0
  amsbsy.sty1999/11/29 v1.2d
  amsopn.sty1999/12/14 v2.01 operator names
which seem to be *really* outdated, compared to the package-versions you list.

Does this mean I manually have to update my latex installation? Is there any 
way you can recommend, without re-compiling my whole software-stack?
The whole situation is a bit sad, as I am sitting behind a ~100kBit/s GPRS line 
:/

Thx, Reggi
  

Re: Insert->Float->Algorithm results in Latex errors

[Jürgen Spitzmüller]

Regina Anger wrote:
> Hi folks,
> 
> I would like to insert an algorithm float in my document.
> However, even for empty documents, doing so results in:
> 
> LaTeX Error: Command \newfloat already defined.
> LaTeX Error: Missing \begin{document}.
> 
> 
> Any idea what could be wrong here?

Your file compiles fine here. This is with most recent TL 2012 and LyX 
2.0.6dev. Maybe some of your packages are outdated. The versions are printed 
to the log file if you enter \listfiles into the preamble. Here's mine:

 *File List*
  memoir.cls2011/03/06 v3.6j configurable book, report, article document 
class
   ifpdf.sty2011/01/30 v2.3 Provides the ifpdf switch (HO)
  ifetex.sty2011/12/15 v1.2 ifetex
 ifxetex.sty2010/09/12 v0.6 Provides ifxetex conditional
ifluatex.sty2010/03/01 v1.3 Provides the ifluatex switch (HO)
etex.sty1998/03/26 v2.0 eTeX basic definition package (PEB)
   mem10.clo2008/01/30 v0.3 memoir class 10pt size option
mempatch.sty2009/07/24 v6.0f Patches for memoir class v1.6180339
 fontenc.sty
   t1enc.def2005/09/27 v1.99g Standard LaTeX file
inputenc.sty2008/03/30 v1.1d Input encoding file
  latin9.def2008/03/30 v1.1d Input encoding file
   float.sty2001/11/08 v1.3d Float enhancements (AL)
  amsthm.sty2009/07/02 v2.20.1
 amsmath.sty2000/07/18 v2.13 AMS math features
 amstext.sty2000/06/29 v2.01
  amsgen.sty1999/11/30 v2.0
  amsbsy.sty1999/11/29 v1.2d
  amsopn.sty1999/12/14 v2.01 operator names
   babel.sty2008/07/08 v3.8m The Babel package
 english.ldf2005/03/30 v3.3o English support from the babel system
 ***

HTH
Jürgen

Re: koma-letter2.lyx gives errors when compiling

[Jürgen Spitzmüller]

Roey Angel wrote:
> I figured that was the problem but even setting 'always babel' under
> 'Language package' didn't seem to work.

No, "always babel" currently means "babel, even if polyglossia would be more 
apt".

Jürgen

Re: koma-letter2.lyx gives errors when compiling

[Roey Angel]

Thanks!
I figured that was the problem but even setting 'always babel' under 'Language
package' didn't seem to work.

Roey

Re: koma-letter2.lyx gives errors when compiling

[Jürgen Spitzmüller]

Roey Angel wrote:
> Using Lyx 2.05 and KOMA-script 3.11 I'm getting errors when trying to
> compile koma-letter2.lyx or the example file koma-letter2-example.lyx from
> http://wiki.lyx.org/Examples/KomaLetter2.
> 
> This is what they look like in the log:
> 
> ! Undefined control sequence.
> \select@language ... \@empty }\languageshorthands 
>   {none}\babel@beginsave
> \cs... l.66 \begin{document}

Interesting. The class seems to rely on (but not load) the babel package, 
although the documentation states otherwise.

LyX 2.0.5 does not automatically load babel if English is the only language 
(this is how LyX always was supposed to behave, but due to a bug fixed in LyX 
2.0.5, babel was loaded nevertheless).

For the time being, a manual

\usepackage[english]{babel}

in the preamble will help you.

Jürgen

koma-letter2.lyx gives errors when compiling

[Roey Angel]

Hi,
Using Lyx 2.05 and KOMA-script 3.11 I'm getting errors when trying to compile
koma-letter2.lyx or the example file koma-letter2-example.lyx from
http://wiki.lyx.org/Examples/KomaLetter2.

This is what they look like in the log:

! Undefined control sequence.
\select@language ... \@empty }\languageshorthands 
  {none}\babel@beginsave \cs...
l.66 \begin{document}
 
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

Anyone encountered this in the past?

Thanks,
Roey

Re: Errors when using apacite for bibliography

[Florian]

On Fri, 23 Nov 2012 18:09:30 +0800
 Ray Rashif  wrote:

Try enabling Default citation style in preferences and then in
preamble save the following:

% Workaround for APA style (must turn off natbib first)
\usepackage{apacite}
\usepackage[authoryear]{natbib}


Thanks, this seems to resolve the problem.

Best, Florian

Re: Errors when using apacite for bibliography

[Ray Rashif]

On 23 November 2012 02:58, Florian  wrote:
> Hi there,
>
> I would need some help with apacite, as I do not seem to get it working. I
> use LyX 2.0.5 on Windows 7.

Try enabling Default citation style in preferences and then in
preamble save the following:

% Workaround for APA style (must turn off natbib first)
\usepackage{apacite}
\usepackage[authoryear]{natbib}


--
GPG/PGP ID: C0711BF1

Errors when using apacite for bibliography

[Florian]

Hi there,

I would need some help with apacite, as I do not seem to get it 
working. I use LyX 2.0.5 on Windows 7.
If I try to use the apacite style, I get the following list of errors 
when compiling to PDF:



snip >>>>>>>


! Undefined control sequence.
l.11 \APACinsertmetastar
 {%
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.


! LaTeX Error: Environment APACrefauthors undefined.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...

l.13 \begin{APACrefauthors}
   %
Your command was ignored.
Type  Ito replace it with another command,
orto continue without it.


! LaTeX Error: \begin{thebibliography} on input line 1 ended by 
\end{APACrefaut

hors}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...

l.15 \end{APACrefauthors}
 %
Your command was ignored.
Type  Ito replace it with another command,
orto continue without it.

! Undefined control sequence.
l.18 \APACrefYear
 {2012}.
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

! Undefined control sequence.
l.20 \APACrefbtitle
{Test Book} {Test book}.
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

! Undefined control sequence.
l.22 \APACaddressPublisher
  {}{Test Publishing}.
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

! Undefined control sequence.
l.23 \PrintBackRefs
   {\CurrentBib}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

! Undefined control sequence.
l.23 \PrintBackRefs{\CurrentBib
   }
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

)

<<<<<< snap <<<<<<


This is a fresh install and I used the 1.x versions of Lyx before, 
where I cannot remember having this happen. And I have no idea why 
this should happen, I've even tried just starting a new document and 
doing nothing but inserting two words and a reference and then 
apacite. The errors above are from the LyX and Bib files below.


There are no errors unless I actually cite something, if that helps.

I'd be really grateful if someone had an idea.

Best,

Florian

--- test.lyx ---
#LyX 2.0 created this file. For more info see http://www.lyx.org/
\lyxformat 413
\begin_document
\begin_header
\textclass article
\use_default_options true
\begin_modules
linguistics
\end_modules
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding auto
\fontencoding global
\font_roman lmodern
\font_sans lmss
\font_typewriter lmtt
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100

\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_amsmath 1
\use_esint 1
\use_mhchem 1
\use_mathdots 1
\cite_engine natbib_authoryear
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\use_refstyle 1
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header

\begin_body

\begin_layout Standard
Test test.
 
\begin_inset Command

Converting module from version 11 to 35 -- WAS: Errors when opening LyX files? - caused by module?

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

OK - that inotify was solved with a reboot - no idea what happened there.

I looked at the manual, and modified the offending module to the version 
attached, but I still get
errors:

LLyX: Unknown InsetLayout tag [around line 20 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'LabelType' context: '']
LyX: Unknown InsetLayout tag [around line 21 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'Static' context: '']
LyX: Unknown InsetLayout tag [around line 33 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'Align' context: '']
LyX: Unknown InsetLayout tag [around line 34 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'Center' context: '']
LyX: Unknown InsetLayout tag [around line 37 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 38 of file 
~/.lyx/layouts/todonotesalternate.module
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 126 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 127 of file 
~/.lyx/layouts/todonotesalternate.module
current token: '1' context: '']
yX: Unknown InsetLayout tag [around line 20 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'LabelType' context: '']
LyX: Unknown InsetLayout tag [around line 21 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'Static' context: '']
LyX: Unknown InsetLayout tag [around line 33 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'Align' context: '']
LyX: Unknown InsetLayout tag [around line 34 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'Center' context: '']
LyX: Unknown InsetLayout tag [around line 37 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 38 of file 
~/.lyx/layouts/todonotesalternate.module
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 126 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 127 of file 
~/.lyx/layouts/todonotesalternate.module
current token: '1' context: '']

when adding this module to the document. I must say, I don't have any ideas 
left what is causing
this, as the LabelType tag should be valid, ant the value "custom" as well? 
=What is there still
wrong?

As soon as this is solved, I will try to upload it to the LyX wiki.

Thanks,

Rainer




On 20/09/12 18:27, Rainer M Krug wrote:
> On 20/09/12 18:06, Liviu Andronic wrote:
>> On Thu, Sep 20, 2012 at 5:41 PM, Rainer M Krug  wrote:
>>> QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No 
>>> space left on
>>> device
>>> 
>> Are you sure all your partitions have adequate free space? Maybe that's 
>> tripping something
>> up.
> 
> I guess this should be enough - but I was wondering as well:
> 
> Filesystem  Size  Used Avail Use% Mounted on /dev/sda2
> 21G   11G  8.5G  56% / udev1.7G  4.0K  1.7G   
> 1% /dev tmpfs
> 681M  936K  681M   1% /run none5.0M 0  
> 5.0M   0% /run/lock 
> none1.7G  968K  1.7G   1% /run/shm /dev/sda1
> 958M  105M  805M  12% /boot /dev/sda3   186G  159G   
> 24G  88% /home
> 
> 
> Rainer
> 
> 
>> Liviu
> 
> 
> 
> 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys.
(Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBcLT4ACgkQoYgNqgF2egrgtQCfeqSvwns4b1od934vXLU0RURM
Ny8AmwdJeYvaM/aBSO9bDp26SFFLYJYR
=vLrc
-END PGP SIGNATURE-
#\DeclareLyXModule{ToDo Notes Environments}
#DescriptionBegin
#Defines some custom insets to implement the todonotes package.
#DescriptionEnd
#Requires   
#Excludes

#Author: Stephen 

Format 35


AddToPreamble
\usepackage[color=green!40]{todonotes}
EndPreamble



InsetLayout "Flex:MakeTabl

Re: Errors when opening LyX files? - caused by module?

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 20/09/12 18:06, Liviu Andronic wrote:
> On Thu, Sep 20, 2012 at 5:41 PM, Rainer M Krug  wrote:
>> QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No 
>> space left on device
>> 
> Are you sure all your partitions have adequate free space? Maybe that's 
> tripping something up.

I guess this should be enough - but I was wondering as well:

Filesystem  Size  Used Avail Use% Mounted on
/dev/sda221G   11G  8.5G  56% /
udev1.7G  4.0K  1.7G   1% /dev
tmpfs   681M  936K  681M   1% /run
none5.0M 0  5.0M   0% /run/lock
none1.7G  968K  1.7G   1% /run/shm
/dev/sda1   958M  105M  805M  12% /boot
/dev/sda3   186G  159G   24G  88% /home


Rainer

> 
> Liviu
> 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys.
(Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBbQ9YACgkQoYgNqgF2egrfEgCgiegjqin+XZ2mHig/H6UtQKT0
uU0An3TBqWtLNOC0syvtd/JNSL1sdIaD
=dTaR
-END PGP SIGNATURE-

Re: Errors when opening LyX files? - caused by module?

[Liviu Andronic]

On Thu, Sep 20, 2012 at 5:41 PM, Rainer M Krug  wrote:
> QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No space 
> left on device
>
Are you sure all your partitions have adequate free space? Maybe
that's tripping something up.

Liviu

Re: Errors when opening LyX files? - caused by module?

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 20/09/12 16:09, Richard Heck wrote:
> On 09/20/2012 07:32 AM, Rainer M Krug wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>> 
>> On 20/09/12 13:23, Rainer M Krug wrote:
>>> Hi
>>> 
>>> when I start LyX it restres the last session and everything looks fine, but 
>>> in the
>>> terminal from which I start LyX, I get abunch of errors:
>>> 
>>> 
>>> LyX: Unknown InsetLayout tag [around line 21 of file

<>>

>>> 
>>>   [1] GPL 
>>> Ghostscript 9.05: Unrecoverable error, exit code 1
>>> 
>>> 
>>> Any ideas what is causing this?
>> I could reproduce it as follow:
>> 
>> I have the attached module installed, and if I add it to an empty file, save 
>> the file and
>> open LyX, the error occurs - but there seems nothing wrong with the module?
>> 
> There is something wrong with the format number, I think. Certainly HTML 
> stuff cannot go into a
> file with Format 11, since that was 1.6.x and XHTML output wasn't introduced 
> until 2.0.x. So
> LyX is getting confused during the conversion to the current format. Not sure 
> why you are
> seeing the error at "OptionalArgs", but that's the kind of thing that is 
> happening.

OK - I changed it to 35 (I saw that one in my LyX installation, but now I am 
getting:

QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No space 
left on device
QFileSystemWatcher: failed to add paths: /home/rkrug/.config/ibus/bus
../../src/insets/InsetLayout.cpp(191): Flex insets must have names of the form 
`Flex:'.
This one has the name `MakeTableOfToDos'
Ignoring LyXType declaration.
LyX: Unknown InsetLayout tag [around line 20 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'custom' context: '']
LyX: Unknown InsetLayout tag [around line 20 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'LabelType' context: '']
LyX: Unknown InsetLayout tag [around line 21 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'Static' context: '']
LyX: Unknown InsetLayout tag [around line 33 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'Align' context: '']
LyX: Unknown InsetLayout tag [around line 34 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'Center' context: '']
LyX: Unknown InsetLayout tag [around line 37 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 38 of file 
~/.lyx/layouts/todonotesalternate.module
current token: '0' context: '']
../../src/insets/InsetLayout.cpp(191): Flex insets must have names of the form 
`Flex:'.
This one has the name `Todo[Inline]'
Ignoring LyXType declaration.
LyX: Unknown InsetLayout tag [around line 46 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'custom' context: '']
../../src/insets/InsetLayout.cpp(191): Flex insets must have names of the form 
`Flex:'.
This one has the name `Todo[margin]'
Ignoring LyXType declaration.
LyX: Unknown InsetLayout tag [around line 80 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'custom' context: '']
../../src/insets/InsetLayout.cpp(191): Flex insets must have names of the form 
`Flex:'.
This one has the name `MissingFigure'
Ignoring LyXType declaration.
LyX: Unknown InsetLayout tag [around line 111 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'custom' context: '']
LyX: Unknown InsetLayout tag [around line 126 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 127 of file 
~/.lyx/layouts/todonotesalternate.module
current token: '1' context: '']
../../src/insets/InsetLayout.cpp(191): Flex insets must have names of the form 
`Flex:'.
This one has the name `Warning'
Ignoring LyXType declaration.
LyX: Unknown InsetLayout tag [around line 145 of file 
~/.lyx/layouts/todonotesalternate.module
current token: 'custom' context: '']

Any suggestions to what I should change the format number?

Rainer


> 
> Richard
> 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys.
(Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBbOQwACgkQoYgNqgF2egpYRACdFRI9xByC5Ldrh08GenLulWNr
rFwAmwZ2x+N9KBBSqaH+a1XwMR/WviSo
=uY9M
-END PGP SIGNATURE-

Re: Errors when opening LyX files? - caused by module?

[Richard Heck]

On 09/20/2012 07:32 AM, Rainer M Krug wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 20/09/12 13:23, Rainer M Krug wrote:

Hi

when I start LyX it restres the last session and everything looks fine, but in 
the terminal
from which I start LyX, I get abunch of errors:


LyX: Unknown InsetLayout tag [around line 21 of file
/tmp/lyx_tmpdir.T17549/convert_layout.h17549 current token: 'LabelType' 
context: ''] LyX:
Unknown InsetLayout tag [around line 22 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: 'Static' context: ''] LyX: Unknown InsetLayout tag [around line 
34 of file
/tmp/lyx_tmpdir.T17549/convert_layout.h17549 current token: 'Align' context: 
''] LyX: Unknown
InsetLayout tag [around line 35 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549 current
token: 'Center' context: ''] LyX: Unknown InsetLayout tag [around line 38 of 
file
/tmp/lyx_tmpdir.T17549/convert_layout.h17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 39 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 127 
of file
/tmp/lyx_tmpdir.T17549/convert_layout.h17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 128 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: '1' context: ''] LyX: Unknown InsetLayout tag [around line 31 of 
file
/tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 32 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 44 of 
file
/tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 45 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 57 of 
file
/tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 58 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 70 of 
file
/tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 71 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 83 of 
file
/tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 84 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 96 of 
file
/tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 97 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 109 
of file
/tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 110 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 122 
of file
/tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
context: ''] LyX:
Unknown InsetLayout tag [around line 123 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: '']

Running: svn proplist "AS_BC_manuscrip.lyx">  
"/tmp/lyx_tmpdir.T17549/lyxvcout.S17549" LyX:
Unknown InsetLayout tag [around line 21 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.n17549
current token: 'LabelType' context: ''] LyX: Unknown InsetLayout tag [around 
line 22 of file
/tmp/lyx_tmpdir.T17549/convert_layout.n17549 current token: 'Static' context: 
''] LyX: Unknown
InsetLayout tag [around line 34 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.n17549 current
token: 'Align' context: ''] LyX: Unknown InsetLayout tag [around line 35 of file
/tmp/lyx_tmpdir.T17549/convert_layout.n17549 current token: 'Center' context: 
''] LyX: Unknown
InsetLayout tag [around line 38 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.n17549 current
token: 'OptionalArgs' context: ''] LyX: Unknown InsetLayout tag [around line

Re: Errors when opening LyX files? - caused by module?

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 20/09/12 13:23, Rainer M Krug wrote:
> Hi
> 
> when I start LyX it restres the last session and everything looks fine, but 
> in the terminal
> from which I start LyX, I get abunch of errors:
> 
> 
> LyX: Unknown InsetLayout tag [around line 21 of file
> /tmp/lyx_tmpdir.T17549/convert_layout.h17549 current token: 'LabelType' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 22 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.h17549 
> current token: 'Static' context: ''] LyX: Unknown InsetLayout tag [around 
> line 34 of file
> /tmp/lyx_tmpdir.T17549/convert_layout.h17549 current token: 'Align' context: 
> ''] LyX: Unknown
> InsetLayout tag [around line 35 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.h17549 current
> token: 'Center' context: ''] LyX: Unknown InsetLayout tag [around line 38 of 
> file
> /tmp/lyx_tmpdir.T17549/convert_layout.h17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 39 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.h17549 
> current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 127 
> of file
> /tmp/lyx_tmpdir.T17549/convert_layout.h17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 128 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.h17549 
> current token: '1' context: ''] LyX: Unknown InsetLayout tag [around line 31 
> of file
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 32 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 
> current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 44 
> of file
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 45 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 
> current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 57 
> of file
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 58 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 
> current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 70 
> of file
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 71 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 
> current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 83 
> of file
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 84 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 
> current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 96 
> of file
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 97 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 
> current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 109 
> of file
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 110 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 
> current token: '0' context: ''] LyX: Unknown InsetLayout tag [around line 122 
> of file
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 current token: 'OptionalArgs' 
> context: ''] LyX:
> Unknown InsetLayout tag [around line 123 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.L17549 
> current token: '0' context: '']
> 
> Running: svn proplist "AS_BC_manuscrip.lyx" > 
> "/tmp/lyx_tmpdir.T17549/lyxvcout.S17549" LyX:
> Unknown InsetLayout tag [around line 21 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.n17549 
> current token: 'LabelType' context: ''] LyX: Unknown InsetLayout tag [around 
> line 22 of file
> /tmp/lyx_tmpdir.T17549/convert_layout.n17549 current token: 'Static' context: 
> ''] LyX: Unknown
> InsetLayout tag [around line 34 of file 
> /tmp/lyx_tmpdir.T17549/convert_layout.n17549 cu

Errors when opening LyX files?

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

when I start LyX it restres the last session and everything looks fine, but in 
the terminal from
which I start LyX, I get abunch of errors:


LyX: Unknown InsetLayout tag [around line 21 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: 'LabelType' context: '']
LyX: Unknown InsetLayout tag [around line 22 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: 'Static' context: '']
LyX: Unknown InsetLayout tag [around line 34 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: 'Align' context: '']
LyX: Unknown InsetLayout tag [around line 35 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: 'Center' context: '']
LyX: Unknown InsetLayout tag [around line 38 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 39 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 127 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 128 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.h17549
current token: '1' context: '']
LyX: Unknown InsetLayout tag [around line 31 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 32 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 44 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 45 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 57 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 58 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 70 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 71 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 83 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 84 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 96 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 97 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 109 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 110 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: '']
LyX: Unknown InsetLayout tag [around line 122 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 123 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.L17549
current token: '0' context: '']

Running: svn proplist "AS_BC_manuscrip.lyx" > 
"/tmp/lyx_tmpdir.T17549/lyxvcout.S17549"
LyX: Unknown InsetLayout tag [around line 21 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.n17549
current token: 'LabelType' context: '']
LyX: Unknown InsetLayout tag [around line 22 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.n17549
current token: 'Static' context: '']
LyX: Unknown InsetLayout tag [around line 34 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.n17549
current token: 'Align' context: '']
LyX: Unknown InsetLayout tag [around line 35 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.n17549
current token: 'Center' context: '']
LyX: Unknown InsetLayout tag [around line 38 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.n17549
current token: 'OptionalArgs' context: '']
LyX: Unknown InsetLayout tag [around line 39 of file 
/tmp/lyx_tmpdir.T17549/convert_layout.n17549
current token: '0' context: &#x

Re: errors typesetting UserGuide.lyx

[Richard Talley]

Rather than further troubleshoot my issues with LyX on Snow Leopard, I
decided to wait until I could start fresh with Lion.

After some hardware repairs, I wiped the hard drive on my MacBook Pro and
installed Lion 10.7.4, MaxTeX-2012 (which I immediately updated with the
TeX Live Utility), LyX2.0.4+qt4, and Skim 1.3.21.

I ran LyX -> Reconfigure, and then set LyX and Skim to sync with each other.

Now I can successfully typeset LyX documentation without error.

I want to thank everybody on this mailing list who tried to help me
troubleshoot; sometimes an OS simply has too much cruft from being ridden
and put up wet too many times, and it's simpler just to start over.

-- Rich

On Tue, Feb 7, 2012 at 9:58 AM, Richard Heck  wrote:

>  On 02/07/2012 11:35 AM, Rich Talley wrote:
>
> Yes, I did reconfigure LyX.
>
>  I am going to create a small test document that only has a title and a
> couple of the problematic graphics files from the User's Manual, one eps
> and one pdf. Then I'll see what's in the LaTeX log when I try to typeset it
> & get back to the list.
>
>  You should also try typesetting it manually from the command line, in so
> far as that is possible.
>
> Richard
>
>
>  -- Rich
>
> On Tue, Feb 7, 2012 at 9:29 AM, Jens Nöckel  wrote:
>
>>
>> On Feb 7, 2012, at 6:12 AM, Richard Heck wrote:
>>
>> > On 02/07/2012 12:50 AM, Jens Nöckel wrote:
>> >>
>> >> I think this can only be solved if you save the user's guide to an
>> external file, bisect that new file until you localize the error to a
>> reasonably small portion of the file, and then inspect the LaTeX log.
>> >>
>> > Did the OP reconfigure LyX after getting convert working?
>> >
>>
>>  Good question. Rich -- that should definitely be the first thing to do!
>>
>> Jens
>>
>
>
>
>

Re: Fwd: Re: Dimensions too large + minibox problems (LaTeX errors)

[Merhebi, Bob]

On Mon 09 Jul 2012 09:31:56 AM EEST, Ignacio García wrote:
>
>
> 2012/7/8 Merhebi, Bob mailto:bobmerh...@gmail.com>>
>
>
> To get the zip: https://dl.dropbox.com/u/60916509/lyx.zip
>
>
> "Dimensions too large" error is back when i inserted the image)
>
> Note: all errors appear in DVI view
>
>
>
> I can get a right PDF output fixing the following :
>
> 1. The last box:  I think "Box(Makebox)" is not accurate here. Change
> it to Minipage or Parbox
> 2. Delete the ragged line break just before this box
>

Great;
I used the line break since without it the box appears shifted to the 
right (i.e; not aligned with the other boxes)

> The PDF output is possible, but the math out of margins, because the
> Width of the box
> is set to 100 Page height. Chnage it to 100 Text Width
>
> Now it looks OK in the PDF output
>

Indeed. Thank you

> The DVI output errors, I don't know fix it.

Maybe someone else can help with this?

On 07/09/2012 02:17 AM, Marcelo Acuña wrote:> Dimensions too large is a 
nightmare for me.
> This error appears when I change font size and I can't resolve it.
>
> Marcelo

I change the default size to 12. No problems with that! How did you 
change it?

--
Sincerely Yours,
-Merhebi, Bob

Thunderbird Signature

Re: Dimensions too large + minibox problems (LaTeX errors)

[Marcelo Acuña]

Dimensions too large is a nightmare for me.
This error appears when I change font size and I can't resolve it.

Marcelo

Fwd: Fwd: Re: Dimensions too large + minibox problems (LaTeX errors)

[Merhebi, Bob]

I am not sure if my mail has been reaching out; I checked the online
archive of the mailing list & couldn't find my last 2 forwards. So I
removed the attached zip in case this is the cause of the problem.

To get the zip: https://dl.dropbox.com/u/60916509/lyx.zip


Sorry for the inconvenience, if any!

 Original Message 
Subject: Fwd: Re: Dimensions too large + minibox problems (LaTeX errors)
Date: Sun, 08 Jul 2012 20:31:58 +0300
From: Merhebi, Bob 
Reply-To: bobmerh...@gmail.com
To: Ignacio García 
CC: LyX Users 




 Original Message 
Subject: Re: Dimensions too large + minibox problems (LaTeX errors)
Date: Tue, 26 Jun 2012 03:55:17 +0300
From: Merhebi, Bob 
Reply-To: bobmerh...@gmail.com
To: Ignacio García 
CC: lyx-users 



On Mon 25 Jun 2012 09:47:45 AM EEST, Ignacio García wrote:
>   Merhebi, Bob wrote
>
> > When I want to view the DVI I get several LaTeX errors; mainly the
> > "Dimension too Large"
>
> I can't reproduce it
>

neither can I! (oh see below!)

> > & the other errors related to the last minibox.
>
> The last minibox is in 'Description' environment: change it to Normal layout
>
that solved it :D thanks



>  > Moreover, one "graphical" problem is the long minibox. In the original
> > document it's too long to appear on the page (part of it is hid under
> > the bottom margin). In the attached document you can see that it reaches
> > the page number!
>
> You can try to adjust the Page Margins in Document Settings

I do not wish to adjust the margins as I already set them to the
desired values. Isn't there an option such that the box splits into two
(i.e; on separate pages) to remain within the margins?

Ah I was just checking the box settings & found "Allow Page Breaks"
which I cannot use except when "Inner Box" is "None"; then I get Latex
errors again! (attached as zip with image included; the previous
"Dimensions too large" error is back when i inserted the image)

Note: all errors appear in DVI view

> Regards
> Ignacio García


--
Sincerely Yours,
-Merhebi, Bob

Thunderbird Signature



-- 
Sincerely Yours,
-Merhebi, Bob

Thunderbird Signature





-- 
Sincerely Yours,
-Merhebi, Bob

Thunderbird Signature





0x66D60862.asc
Description: application/pgp-keys


0x66D60862.asc
Description: application/pgp-keys

Re: Dimensions too large + minibox problems (LaTeX errors)

[Ignacio García]

  Merhebi, Bob wrote

> When I want to view the DVI I get several LaTeX errors; mainly the
> "Dimension too Large"

I can't reproduce it

> & the other errors related to the last minibox.

The last minibox is in 'Description' environment: change it to Normal layout

 > Moreover, one "graphical" problem is the long minibox. In the original
> document it's too long to appear on the page (part of it is hid under
> the bottom margin). In the attached document you can see that it reaches
> the page number!

You can try to adjust the Page Margins in Document Settings

Regards
Ignacio García

Dimensions too large + minibox problems (LaTeX errors)

[Merhebi, Bob]

Dear LyXers,

I am writing a technical document & need some help from you. Attached is
the related file.

When I want to view the DVI I get several LaTeX errors; mainly the
"Dimension too Large" & the other errors related to the last minibox.

Moreover, one "graphical" problem is the long minibox. In the original
document it's too long to appear on the page (part of it is hid under
the bottom margin). In the attached document you can see that it reaches
the page number!

You help is greatly appreciated!

Thanks in advance

-- 
Sincerely Yours,
-Merhebi, Bob

Thunderbird Signature



0x66D60862.asc
Description: application/pgp-keys


newfile1.lyx
Description: application/lyx

Re: Errors on publishing [to pdf]

[Eric Weir]

On Feb 13, 2012, at 9:16 AM, stefano franchi wrote:

> you may have to check the encoding of your lyx file. If you use XeTeX
> compilation (or LuaTeX, for that mater) the file should be in Unicode.
> It looks like it isn't. Be sure:
> 
> 1. that Scrivener-generated LateX code is in Unicode encoding (it may
> be an option---LaTex was unable to read unicode until recently.

Thanks, Stefano. I'm still waiting on a response from the Scrivener listserv.

> 2. That Lyx properly treats the file as Unicode-encoded. IT should do
> so automatically, but just to be on the safe side,go to
> Document>>Settings>>Language  under "Encoding" select the radio button
> "Other" and from the drop-down list next to it choose *Unicode (XeTeX)
> (UTF8)"

I made this change and tried compiling with XeTeX and LuaTeX. Still getting the 
weird substitutions. Tried quitting LyX and compiling again with the same 
result.

Is it possible that I will need to reimport the tex output from Scrivener?

Sincerely,
--
Eric Weir
Decatur, GA  USA
eew...@bellsouth.net

"Imagining the other is a powerful antidote to fanaticism and hatred." 

- Amos Oz

Re: Errors on publishing [to pdf]

[stefano franchi]

On Mon, Feb 13, 2012 at 6:14 AM, Eric Weir  wrote:
>
> On Feb 12, 2012, at 1:18 PM, Richard Heck wrote:
>
> Once you have the file in LyX, just try: View>PDF(XeTeX), e.g. That said,
> I'm definitely not an expert on this encoding stuff. If you could produce a
> really simple example file---create it in Scrivener and export it as
> usual---that exhibits the problem, that will definitely help.
>
>
> Thanks again, Richard. I thought the XeTeX/LuaTeX suggestion would involve
> an additional compiling step. I see that it does not. Both compile, but
> instead of giving error messages they substitute weird characters for the
> problemmatic characters, e.g., an em-dash becomes âĂT. Sometimes it does
> the same for en-dashes, sometimes not. Sometimes with the apostrophe,
> sometimes not. Also with accented characters.
>

Eric,

you may have to check the encoding of your lyx file. If you use XeTeX
compilation (or LuaTeX, for that mater) the file should be in Unicode.
It looks like it isn't. Be sure:

1. that Scrivener-generated LateX code is in Unicode encoding (it may
be an option---LaTex was unable to read unicode until recently.
2. That Lyx properly treats the file as Unicode-encoded. IT should do
so automatically, but just to be on the safe side,go to
Document>>Settings>>Language  under "Encoding" select the radio button
"Other" and from the drop-down list next to it choose *Unicode (XeTeX)
(UTF8)"

Hope it helps,

Stefano

> The file I'm working on is not that complicated: 12 pages with bibliography
> and footnotes; title, author, and section headings formatted KOMA-Script
> default.
>
> Assuming that the problem is Unicode characters, I'm also gonna check with
> the Scrivener forum to see if there's a way to stop that.
>
> Sincerely,
> --
> Eric Weir
> Decatur, GA  USA
> eew...@bellsouth.net
>
>
>
>



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

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

Re: Errors on publishing [to pdf]

[Eric Weir]

On Feb 12, 2012, at 1:18 PM, Richard Heck wrote:

> Once you have the file in LyX, just try: View>PDF(XeTeX), e.g. That said, I'm 
> definitely not an expert on this encoding stuff. If you could produce a 
> really simple example file---create it in Scrivener and export it as 
> usual---that exhibits the problem, that will definitely help.


Thanks again, Richard. I thought the XeTeX/LuaTeX suggestion would involve an 
additional compiling step. I see that it does not. Both compile, but instead of 
giving error messages they substitute weird characters for the problemmatic 
characters, e.g., an em-dash becomes âĂT. Sometimes it does the same for 
en-dashes, sometimes not. Sometimes with the apostrophe, sometimes not. Also 
with accented characters.

The file I'm working on is not that complicated: 12 pages with bibliography and 
footnotes; title, author, and section headings formatted KOMA-Script default. 

Assuming that the problem is Unicode characters, I'm also gonna check with the 
Scrivener forum to see if there's a way to stop that.  

Sincerely,
--
Eric Weir
Decatur, GA  USA
eew...@bellsouth.net

Re: Errors on publishing [to pdf]

[Richard Heck]

On 02/12/2012 12:04 PM, Eric Weir wrote:


On Feb 12, 2012, at 10:41 AM, Richard Heck wrote:

The problem may be that these are Unicode characters (so is the quote 
you mentioned). You might try compiling with XeTeX or LuaTeX, which 
use Unicode.


Thanks, Richard. My only way to get from Scrivener to LaTeX/LyX is to 
compile in Scrivener. The out from Scrivener is a tex file. Would I 
then compile that with XeTeX or LuaTex? If so, could you give me quick 
pointers how to get started with that? Or a reference to instructions?


Once you have the file in LyX, just try: View>PDF(XeTeX), e.g. That 
said, I'm definitely not an expert on this encoding stuff. If you could 
produce a really simple example file---create it in Scrivener and export 
it as usual---that exhibits the problem, that will definitely help.


I don't know if its possible, would another option be to get Scrivener 
to stop outputing Unicode characters?



It might, but I don't know Scrivener.

Richard

Re: Errors on publishing [to pdf]

[Eric Weir]

On Feb 12, 2012, at 10:41 AM, Richard Heck wrote:

> The problem may be that these are Unicode characters (so is the quote you 
> mentioned). You might try compiling with XeTeX or LuaTeX, which use Unicode.

Thanks, Richard. My only way to get from Scrivener to LaTeX/LyX is to compile 
in Scrivener. The out from Scrivener is a tex file. Would I then compile that 
with XeTeX or LuaTex? If so, could you give me quick pointers how to get 
started with that? Or a reference to instructions? 

I don't know if its possible, would another option be to get Scrivener to stop 
outputing Unicode characters?  

--
Eric Weir
Decatur, GA 
eew...@bellsouth.net

"We do not inherit the earth from our ancestors, 
we borrow it from our children." 

- Chief Seattle.

Re: Errors on publishing [to pdf]

[Paul A . Rubin]

In addition to Richard's suggestion, another option would be to open your LyX
document in a text editor and globally replace the Unicode character for the
long dash with two ordinary dashes.

Paul

Re: Errors on publishing [to pdf]

[Richard Heck]

On 02/12/2012 07:15 AM, Eric Weir wrote:


When I attempt to publish [format and print to pdf] a document 
compiled from Scrivener and imported into LyX I get a long list of 
errors, all of which have to do with Lyx--or the document class I'm 
using, KOMA-Script article--not liking some of the punctuation carried 
over from Scrivener.


The major offender is--I'm going to describe, because I don't know the 
name--a long dash which Scrivener converts to when I enter two regular 
dashes in succession. Single dashes and some single and double 
quotation marks also give errors. [The error with the long 
dash--again, forgive my not knowing the name of the thing--may be due 
to the fact that I believe it is normally preceded and followed by a 
space; I recently switched to use of long dashes that without the 
preceding and following spaces.]


The long dash is called an "em-dash". There's also a slightly shorter 
one called an "en-dash". In LyX, these would be entered as "---" and 
"--", respectively. The spaces won't matter, and (at least in US 
typesetting) one doesn't normally use them.



This is the message I get regarding the long dash:

We believe this impasse—
between a rigorous method that is difficult

You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.


The problem may be that these are Unicode characters (so is the quote 
you mentioned). You might try compiling with XeTeX or LuaTeX, which use 
Unicode.


Richard

Errors on publishing [to pdf]

[Eric Weir]

When I attempt to publish [format and print to pdf] a document compiled from 
Scrivener and imported into LyX I get a long list of errors, all of which have 
to do with Lyx--or the document class I'm using, KOMA-Script article--not 
liking some of the punctuation carried over from Scrivener. 

The major offender is--I'm going to describe, because I don't know the name--a 
long dash which Scrivener converts to when I enter two regular dashes in 
succession. Single dashes and some single and double quotation marks also give 
errors. [The error with the long dash--again, forgive my not knowing the name 
of the thing--may be due to the fact that I believe it is normally preceded and 
followed by a space; I recently switched to use of long dashes that without the 
preceding and following spaces.]

This is the message I get regarding the long dash:

We believe this impasse—
between a rigorous method that is difficult

You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.

My first thought was to go back to Scrivener and change the offending 
characters--adding spaces before and after double dashes--but that might be 
unnecessarily laborious, and will not work for the offending single dashes and 
single and double quotes. Here is an error message related to single quotes:

Cartwright, N. (1989a). Nature’
s Capacities and Their Measurement.

You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.

And double quotes:

relatively specific practices
``instituting universal preschool''

You need to provide a definition with \DeclareInputText
or \DeclareInputMath before using this key.


Suggestions for resolving the problem would be appreciated.

Sincerely,
--
Eric Weir
Decatur, GA  USA
eew...@bellsouth.net

"Hatred destroys. Love heals."

- Eknath Easwaran

Re: errors typesetting UserGuide.lyx

[Richard Heck]

On 02/07/2012 11:35 AM, Rich Talley wrote:

Yes, I did reconfigure LyX.

I am going to create a small test document that only has a title and a 
couple of the problematic graphics files from the User's Manual, one 
eps and one pdf. Then I'll see what's in the LaTeX log when I try to 
typeset it & get back to the list.


You should also try typesetting it manually from the command line, in so 
far as that is possible.


Richard


-- Rich

On Tue, Feb 7, 2012 at 9:29 AM, Jens Nöckel > wrote:



On Feb 7, 2012, at 6:12 AM, Richard Heck wrote:

> On 02/07/2012 12:50 AM, Jens Nöckel wrote:
>>
>> I think this can only be solved if you save the user's guide to
an external file, bisect that new file until you localize the
error to a reasonably small portion of the file, and then inspect
the LaTeX log.
>>
> Did the OP reconfigure LyX after getting convert working?
>

Good question. Rich -- that should definitely be the first thing
to do!

Jens

Re: errors typesetting UserGuide.lyx

[Rich Talley]

Yes, I did reconfigure LyX.

I am going to create a small test document that only has a title and a
couple of the problematic graphics files from the User's Manual, one eps
and one pdf. Then I'll see what's in the LaTeX log when I try to typeset it
& get back to the list.

-- Rich

On Tue, Feb 7, 2012 at 9:29 AM, Jens Nöckel  wrote:

>
> On Feb 7, 2012, at 6:12 AM, Richard Heck wrote:
>
> > On 02/07/2012 12:50 AM, Jens Nöckel wrote:
> >>
> >> I think this can only be solved if you save the user's guide to an
> external file, bisect that new file until you localize the error to a
> reasonably small portion of the file, and then inspect the LaTeX log.
> >>
> > Did the OP reconfigure LyX after getting convert working?
> >
>
> Good question. Rich -- that should definitely be the first thing to do!
>
> Jens
>

Re: errors typesetting UserGuide.lyx

[Jens Nöckel]

On Feb 7, 2012, at 6:12 AM, Richard Heck wrote:

> On 02/07/2012 12:50 AM, Jens Nöckel wrote:
>> 
>> I think this can only be solved if you save the user's guide to an external 
>> file, bisect that new file until you localize the error to a reasonably 
>> small portion of the file, and then inspect the LaTeX log.
>> 
> Did the OP reconfigure LyX after getting convert working?
> 

Good question. Rich -- that should definitely be the first thing to do!

Jens
 

Re: errors typesetting UserGuide.lyx

[Richard Heck]

On 02/07/2012 12:50 AM, Jens Nöckel wrote:
I think this can only be solved if you save the user's guide to an 
external file, bisect that new file until you localize the error to a 
reasonably small portion of the file, and then inspect the LaTeX log.



Did the OP reconfigure LyX after getting convert working?

Richard


Jens

On Feb 6, 2012, at 1:09 PM, Rich Talley wrote:

Thanks. As convert is now working, I'll put off installing software I 
probably don't actually need. I am able to convert the problematic 
files (such as mobius.eps) to pngs at the command line using convert 
manually. The problem appears to be that my installation of LyX is 
not using convert.


As one of the wiki pages recommend, I ran this command:

lyx -dbg graphics

A bunch of graphic formats are listed as loadable. Pdf files are not; 
is this correct?


I confirmed that I only have one copy of convert and that it's in my 
path.


I looked at LyX -> Preferences -> File Handling -> Converters -> EPS 
-> PNG


This shows 'convert $$i $$o', which I believe is correct.

I show only two PDF converters, PDF(ps2pdf) to EPS and to Postscript. 
Should there be more?



-- Rich



On Sun, Feb 5, 2012 at 7:40 PM, Jens Nöckel > wrote:


Assuming convert is really the problem, perhaps you can try a
different imagemagick installation.

Two options would be Macports,
http://www.macports.org/install.php
or Fink,
http://www.finkproject.org/download/index.php?phpLang=en

You only need one of these. Most people seem to choose Macports
nowadays, but it really doesn't matter for your purposes.
After following the installation instructions for one of these
package managers, you can then install imagemagick by typing either
sudo port install imagemagick
(for Macports)
or
fink install imagemagick
(for Fink).

This won't interfere with the MacTeX installation, so it can't
hurt to try. I have used both methods and found convert to work fine.

Jens

On Feb 5, 2012, at 5:41 PM, Richard Talley wrote:


So I found a problem with the 'convert' utility (part of
ImageMagick 6.6.9) that MacTex 2011 installs. The installation
fails to install the necessary xml files that 'convert' needs to
function correctly at the command line.

Over at the macosx-tex mailing list, Dick Koch provided a link
to the necessary xml files with this comment:

"We supply convert mainly for tex4html, thinking that users
familiar with the Unix version
will want to install the full ImageMagick. So the conversion you
are using was never tested."

So I got 'convert' working at the command line. Unfortunately,
this turned out to be a red herring. I still can't typeset LyX's
user manual
from within LyX. Pdf and eps files (such as mobius.eps) still
don't display within LyX ('Error converting to loadable format')
and
typesetting still fails.

I tried exporting the LyX user manual to LaTeX(plain) and
typesetting the resulting TeX file in TeXShop. That actually works,
except cross references break ('see section ??' in the resulting
pdf). But the pdf and eps files that are problematic in LyX typeset
in TeXShop.

What am I missing?

-- Rich


On Sat, Feb 4, 2012 at 2:47 PM, Richard Talley
mailto:rich.tal...@gmail.com>> wrote:

I had been running MacTex 2009 and Lyx 1.6.8. and using them
extensively for technical documentation and homework
assignments.

I upgraded this morning to MacTex 2011 (using the Tex Live
Utility to bring all the packages up to date) and Lyx 2.0.2.

I tried to create a pdf of the UserGuide (located in
/Applications/LyX.app/Contents/Resources/doc/ - opens as
read only)

Four eps files are generating 'Error converting to loadable
format' in the LyX document. The LaTeX error dialog shows:

Package pdftex.def Error: File
`34_Applications_LyX_app_Contents_Resources_doc_clipart_mobius.pdf}

Using draft setting for this image.
Try typing  to proceed.
If that doesn't work, type X  to quit.


- OR -

Package pdftex.def Error: File
`42_Applications_LyX_app_Contents_Resources_doc_clipart_escher-lsd.pdf}}
\hfill{}\subfloat[\label{f...


So my system doesn't seem to be converting eps files
correctly into pdfs for LyX to use. Any suggestions for
troubleshooting? I've saved the complete LaTeX log, but it's
huge and I'm not sure what's relevant.

-- Rich
MacBook Pro/OS X 10.6.8

Re: errors typesetting UserGuide.lyx

[Jens Nöckel]

I think this can only be solved if you save the user's guide to an external 
file, bisect that new file until you localize the error to a reasonably small 
portion of the file, and then inspect the LaTeX log.

Jens

On Feb 6, 2012, at 1:09 PM, Rich Talley wrote:

> Thanks. As convert is now working, I'll put off installing software I 
> probably don't actually need. I am able to convert the problematic files 
> (such as mobius.eps) to pngs at the command line using convert manually. The 
> problem appears to be that my installation of LyX is not using convert.
> 
> As one of the wiki pages recommend, I ran this command:
> 
> lyx -dbg graphics
> 
> A bunch of graphic formats are listed as loadable. Pdf files are not; is this 
> correct?
> 
> I confirmed that I only have one copy of convert and that it's in my path.
> 
> I looked at LyX -> Preferences -> File Handling -> Converters -> EPS -> PNG
> 
> This shows 'convert $$i $$o', which I believe is correct.
> 
> I show only two PDF converters, PDF(ps2pdf) to EPS and to Postscript. Should 
> there be more?
> 
> 
> -- Rich
> 
> 
> 
> On Sun, Feb 5, 2012 at 7:40 PM, Jens Nöckel  wrote:
> Assuming convert is really the problem, perhaps you can try a different 
> imagemagick installation. 
> 
> Two options would be Macports,
> http://www.macports.org/install.php
> or Fink, 
> http://www.finkproject.org/download/index.php?phpLang=en
> 
> You only need one of these. Most people seem to choose Macports nowadays, but 
> it really doesn't matter for your purposes. 
> After following the installation instructions for one of these package 
> managers, you can then install imagemagick by typing either 
> sudo port install imagemagick
> (for Macports)
> or
> fink install imagemagick
> (for Fink).
> 
> This won't interfere with the MacTeX installation, so it can't hurt to try. I 
> have used both methods and found convert to work fine.
> 
> Jens
> 
> On Feb 5, 2012, at 5:41 PM, Richard Talley wrote:
> 
>> So I found a problem with the 'convert' utility (part of ImageMagick 6.6.9) 
>> that MacTex 2011 installs. The installation fails to install the necessary 
>> xml files that 'convert' needs to function correctly at the command line.
>> 
>> Over at the macosx-tex mailing list, Dick Koch provided a link to the 
>> necessary xml files with this comment:
>> 
>> "We supply convert mainly for tex4html, thinking that users familiar with 
>> the Unix version 
>> will want to install the full ImageMagick. So the conversion you are using 
>> was never tested."
>> 
>> So I got 'convert' working at the command line. Unfortunately, this turned 
>> out to be a red herring. I still can't typeset LyX's user manual 
>> from within LyX. Pdf and eps files (such as mobius.eps) still don't display 
>> within LyX ('Error converting to loadable format') and 
>> typesetting still fails.
>> 
>> I tried exporting the LyX user manual to LaTeX(plain) and typesetting the 
>> resulting TeX file in TeXShop. That actually works, 
>> except cross references break ('see section ??' in the resulting pdf). But 
>> the pdf and eps files that are problematic in LyX typeset 
>> in TeXShop.
>> 
>> What am I missing?
>> 
>> -- Rich
>> 
>> 
>> On Sat, Feb 4, 2012 at 2:47 PM, Richard Talley  wrote:
>> I had been running MacTex 2009 and Lyx 1.6.8. and using them extensively for 
>> technical documentation and homework assignments.
>> 
>> I upgraded this morning to MacTex 2011 (using the Tex Live Utility to bring 
>> all the packages up to date) and Lyx 2.0.2.
>> 
>> I tried to create a pdf of the UserGuide (located in 
>> /Applications/LyX.app/Contents/Resources/doc/ - opens as read only)
>> 
>> Four eps files are generating 'Error converting to loadable format' in the 
>> LyX document. The LaTeX error dialog shows:
>> 
>> Package pdftex.def Error: File 
>> `34_Applications_LyX_app_Contents_Resources_doc_clipart_mobius.pdf}
>> 
>> Using draft setting for this image.
>> Try typing  to proceed.
>> If that doesn't work, type X  to quit.
>> 
>> 
>> - OR -
>> 
>> Package pdftex.def Error: File 
>> `42_Applications_LyX_app_Contents_Resources_doc_clipart_escher-lsd.pdf}}
>> \hfill{}\subfloat[\label{f...
>> 
>> 
>> So my system doesn't seem to be converting eps files correctly into pdfs for 
>> LyX to use. Any suggestions for troubleshooting? I've saved the complete 
>> LaTeX log, but it's huge and I'm not sure what's relevant.
>> 
>> -- Rich
>> MacBook Pro/OS X 10.6.8
>> 
>> 
> 
> 

Re: errors typesetting UserGuide.lyx

[Rich Talley]

Thanks. As convert is now working, I'll put off installing software I
probably don't actually need. I am able to convert the problematic files
(such as mobius.eps) to pngs at the command line using convert manually.
The problem appears to be that my installation of LyX is not using convert.

As one of the wiki pages recommend, I ran this command:

lyx -dbg graphics

A bunch of graphic formats are listed as loadable. Pdf files are not; is
this correct?

I confirmed that I only have one copy of convert and that it's in my path.

I looked at LyX -> Preferences -> File Handling -> Converters -> EPS -> PNG

This shows 'convert $$i $$o', which I believe is correct.

I show only two PDF converters, PDF(ps2pdf) to EPS and to Postscript.
Should there be more?


-- Rich



On Sun, Feb 5, 2012 at 7:40 PM, Jens Nöckel  wrote:

> Assuming convert is really the problem, perhaps you can try a different
> imagemagick installation.
>
> Two options would be Macports,
> http://www.macports.org/install.php
> or Fink,
> http://www.finkproject.org/download/index.php?phpLang=en
>
> You only need one of these. Most people seem to choose Macports nowadays,
> but it really doesn't matter for your purposes.
> After following the installation instructions for one of these package
> managers, you can then install imagemagick by typing either
> sudo port install imagemagick
> (for Macports)
> or
> fink install imagemagick
> (for Fink).
>
> This won't interfere with the MacTeX installation, so it can't hurt to
> try. I have used both methods and found convert to work fine.
>
> Jens
>
> On Feb 5, 2012, at 5:41 PM, Richard Talley wrote:
>
> So I found a problem with the 'convert' utility (part of ImageMagick
> 6.6.9) that MacTex 2011 installs. The installation fails to install the
> necessary xml files that 'convert' needs to function correctly at the
> command line.
>
> Over at the macosx-tex mailing list, Dick Koch provided a link to the
> necessary xml files with this comment:
>
> "We supply convert mainly for tex4html, thinking that users familiar with
> the Unix version
> will want to install the full ImageMagick. So the conversion you are using
> was never tested."
>
> So I got 'convert' working at the command line. Unfortunately, this turned
> out to be a red herring. I still can't typeset LyX's user manual
> from within LyX. Pdf and eps files (such as mobius.eps) still don't
> display within LyX ('Error converting to loadable format') and
> typesetting still fails.
>
> I tried exporting the LyX user manual to LaTeX(plain) and typesetting the
> resulting TeX file in TeXShop. That actually works,
> except cross references break ('see section ??' in the resulting pdf). But
> the pdf and eps files that are problematic in LyX typeset
> in TeXShop.
>
> What am I missing?
>
> -- Rich
>
>
> On Sat, Feb 4, 2012 at 2:47 PM, Richard Talley wrote:
>
>> I had been running MacTex 2009 and Lyx 1.6.8. and using them extensively
>> for technical documentation and homework assignments.
>>
>> I upgraded this morning to MacTex 2011 (using the Tex Live Utility to
>> bring all the packages up to date) and Lyx 2.0.2.
>>
>> I tried to create a pdf of the UserGuide (located in
>> /Applications/LyX.app/Contents/Resources/doc/ - opens as read only)
>>
>> Four eps files are generating 'Error converting to loadable format' in
>> the LyX document. The LaTeX error dialog shows:
>>
>> Package pdftex.def Error: File
>> `34_Applications_LyX_app_Contents_Resources_doc_clipart_mobius.pdf}
>>
>> Using draft setting for this image.
>> Try typing  to proceed.
>> If that doesn't work, type X  to quit.
>>
>>
>> - OR -
>>
>> Package pdftex.def Error: File
>> `42_Applications_LyX_app_Contents_Resources_doc_clipart_escher-lsd.pdf}}
>> \hfill{}\subfloat[\label{f...
>>
>>
>> So my system doesn't seem to be converting eps files correctly into pdfs
>> for LyX to use. Any suggestions for troubleshooting? I've saved the
>> complete LaTeX log, but it's huge and I'm not sure what's relevant.
>>
>> -- Rich
>> MacBook Pro/OS X 10.6.8
>>
>>
>
>

Re: errors typesetting UserGuide.lyx

[Jens Nöckel]

Assuming convert is really the problem, perhaps you can try a different 
imagemagick installation. 

Two options would be Macports,
http://www.macports.org/install.php
or Fink, 
http://www.finkproject.org/download/index.php?phpLang=en

You only need one of these. Most people seem to choose Macports nowadays, but 
it really doesn't matter for your purposes. 
After following the installation instructions for one of these package 
managers, you can then install imagemagick by typing either 
sudo port install imagemagick
(for Macports)
or
fink install imagemagick
(for Fink).

This won't interfere with the MacTeX installation, so it can't hurt to try. I 
have used both methods and found convert to work fine.

Jens

On Feb 5, 2012, at 5:41 PM, Richard Talley wrote:

> So I found a problem with the 'convert' utility (part of ImageMagick 6.6.9) 
> that MacTex 2011 installs. The installation fails to install the necessary 
> xml files that 'convert' needs to function correctly at the command line.
> 
> Over at the macosx-tex mailing list, Dick Koch provided a link to the 
> necessary xml files with this comment:
> 
> "We supply convert mainly for tex4html, thinking that users familiar with the 
> Unix version 
> will want to install the full ImageMagick. So the conversion you are using 
> was never tested."
> 
> So I got 'convert' working at the command line. Unfortunately, this turned 
> out to be a red herring. I still can't typeset LyX's user manual 
> from within LyX. Pdf and eps files (such as mobius.eps) still don't display 
> within LyX ('Error converting to loadable format') and 
> typesetting still fails.
> 
> I tried exporting the LyX user manual to LaTeX(plain) and typesetting the 
> resulting TeX file in TeXShop. That actually works, 
> except cross references break ('see section ??' in the resulting pdf). But 
> the pdf and eps files that are problematic in LyX typeset 
> in TeXShop.
> 
> What am I missing?
> 
> -- Rich
> 
> 
> On Sat, Feb 4, 2012 at 2:47 PM, Richard Talley  wrote:
> I had been running MacTex 2009 and Lyx 1.6.8. and using them extensively for 
> technical documentation and homework assignments.
> 
> I upgraded this morning to MacTex 2011 (using the Tex Live Utility to bring 
> all the packages up to date) and Lyx 2.0.2.
> 
> I tried to create a pdf of the UserGuide (located in 
> /Applications/LyX.app/Contents/Resources/doc/ - opens as read only)
> 
> Four eps files are generating 'Error converting to loadable format' in the 
> LyX document. The LaTeX error dialog shows:
> 
> Package pdftex.def Error: File 
> `34_Applications_LyX_app_Contents_Resources_doc_clipart_mobius.pdf}
> 
> Using draft setting for this image.
> Try typing  to proceed.
> If that doesn't work, type X  to quit.
> 
> 
> - OR -
> 
> Package pdftex.def Error: File 
> `42_Applications_LyX_app_Contents_Resources_doc_clipart_escher-lsd.pdf}}
> \hfill{}\subfloat[\label{f...
> 
> 
> So my system doesn't seem to be converting eps files correctly into pdfs for 
> LyX to use. Any suggestions for troubleshooting? I've saved the complete 
> LaTeX log, but it's huge and I'm not sure what's relevant.
> 
> -- Rich
> MacBook Pro/OS X 10.6.8
> 
> 

Re: errors typesetting UserGuide.lyx

[Richard Talley]

So I found a problem with the 'convert' utility (part of ImageMagick 6.6.9)
that MacTex 2011 installs. The installation fails to install the necessary
xml files that 'convert' needs to function correctly at the command line.

Over at the macosx-tex mailing list, Dick Koch provided a link to the
necessary xml files with this comment:

"We supply convert mainly for tex4html, thinking that users familiar with
the Unix version
will want to install the full ImageMagick. So the conversion you are using
was never tested."

So I got 'convert' working at the command line. Unfortunately, this turned
out to be a red herring. I still can't typeset LyX's user manual
from within LyX. Pdf and eps files (such as mobius.eps) still don't display
within LyX ('Error converting to loadable format') and
typesetting still fails.

I tried exporting the LyX user manual to LaTeX(plain) and typesetting the
resulting TeX file in TeXShop. That actually works,
except cross references break ('see section ??' in the resulting pdf). But
the pdf and eps files that are problematic in LyX typeset
in TeXShop.

What am I missing?

-- Rich


On Sat, Feb 4, 2012 at 2:47 PM, Richard Talley wrote:

> I had been running MacTex 2009 and Lyx 1.6.8. and using them extensively
> for technical documentation and homework assignments.
>
> I upgraded this morning to MacTex 2011 (using the Tex Live Utility to
> bring all the packages up to date) and Lyx 2.0.2.
>
> I tried to create a pdf of the UserGuide (located in
> /Applications/LyX.app/Contents/Resources/doc/ - opens as read only)
>
> Four eps files are generating 'Error converting to loadable format' in the
> LyX document. The LaTeX error dialog shows:
>
> Package pdftex.def Error: File
> `34_Applications_LyX_app_Contents_Resources_doc_clipart_mobius.pdf}
>
> Using draft setting for this image.
>
> Try typing  to proceed.
>
> If that doesn't work, type X  to quit.
>
>
>
> - OR -
>
>
> Package pdftex.def Error: File
> `42_Applications_LyX_app_Contents_Resources_doc_clipart_escher-lsd.pdf}}
>
> \hfill{}\subfloat[\label{f...
>
>
>
> So my system doesn't seem to be converting eps files correctly into pdfs
> for LyX to use. Any suggestions for troubleshooting? I've saved the
> complete LaTeX log, but it's huge and I'm not sure what's relevant.
>
>
> -- Rich
>
> MacBook Pro/OS X 10.6.8
>
>
>

errors typesetting UserGuide.lyx

[Richard Talley]

I had been running MacTex 2009 and Lyx 1.6.8. and using them extensively
for technical documentation and homework assignments.

I upgraded this morning to MacTex 2011 (using the Tex Live Utility to bring
all the packages up to date) and Lyx 2.0.2.

I tried to create a pdf of the UserGuide (located in
/Applications/LyX.app/Contents/Resources/doc/ - opens as read only)

Four eps files are generating 'Error converting to loadable format' in the
LyX document. The LaTeX error dialog shows:

Package pdftex.def Error: File
`34_Applications_LyX_app_Contents_Resources_doc_clipart_mobius.pdf}

Using draft setting for this image.

Try typing  to proceed.

If that doesn't work, type X  to quit.



- OR -


Package pdftex.def Error: File
`42_Applications_LyX_app_Contents_Resources_doc_clipart_escher-lsd.pdf}}

\hfill{}\subfloat[\label{f...



So my system doesn't seem to be converting eps files correctly into pdfs
for LyX to use. Any suggestions for troubleshooting? I've saved the
complete LaTeX log, but it's huge and I'm not sure what's relevant.


-- Rich

MacBook Pro/OS X 10.6.8

Re: question and proposal re citations causing errors

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 27/01/12 10:20, Wolfgang Engelmann wrote:
> I wonder whether the following could be done for Lyx without too
> much trouble:
> 
> Often I found to get an error message after inserting a reference
> (with an uncompatible coding, e.g.). It takes quite some time to
> trace it to the specific citation, if a larger number of references
> are cited.

I had these wrong encoding issues very often - and they are horrible.
A much better approach would be to check if the characters in the .bib
files are compatible with the encoding selected, and highlights the
characters (and where they occur in the bib file!).

This could be done via a tool which could also be used for other files.

This would probably be much easier to implement then individually
disabling the references - and also spot errors which you haven't
encountered yet.

Cheers,

Rainer

> 
> Lyx allows under outline to switch to 'list of citations'. If one
> could mark the citation(s!!, i.e. marking a bunch of citations 
> simultaneously) assumed to cause the error directly in the list and
> takes these citations temporarily out (by, lets say, a right mouse
> click, and perhaps lyx puts these citations in a lyx note), a test
> run of lyx would show quickly which citations are causing the
> errror. An other click would switch back to the original
> situation.
> 
> It would certainly be much faster as compared to putting the
> citations manually in a Lyx note for the trial.
> 
> The same could perhaps be done for other lists or even the table of
>  contents.
> 
> 
> Wolfgang
> 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8icIQACgkQoYgNqgF2egpP1QCfbIhpxDA81V8Dov8QRt93fvm0
YJcAn2QMNeXouPOZPrmZpFJPsKVI50cW
=sj9X
-END PGP SIGNATURE-

question and proposal re citations causing errors

[Wolfgang Engelmann]

I wonder whether the following could be done for Lyx without too much 
trouble:

Often I found to get an error message after inserting a reference (with an 
uncompatible coding, e.g.). It takes quite some time to trace it to the 
specific citation, if a larger number of references are cited.

Lyx allows under outline to switch to 'list of citations'.
If one could mark the citation(s!!, i.e. marking a bunch of citations 
simultaneously) assumed to cause the error directly in the list and takes 
these citations temporarily out (by, lets say, a right mouse click, and 
perhaps lyx puts these citations in a lyx note), a test run of lyx would 
show quickly which citations are causing the errror. An other click would 
switch back to the original situation.

It would certainly be much faster as compared to putting the citations 
manually in a Lyx note for the trial.

The same could perhaps be done for other lists or even the table of 
contents.


Wolfgang