Reason found: Re: ! LaTeX Error: Command \footref already defined

[Wolfgang Engelmann]

Due to Herbert Voss's help it turned out that my home folder contained a 
texmf folder (Debian) which apparently interfered with the texlive stuff 
in  /usr/local/texlive/2021/


Wolfgang

Am 27.07.21 um 12:27 schrieb Herbert Voss:



Am 27.07.21 um 11:19 schrieb Wolfgang Engelmann:

Has somebody bumped into this error:

! LaTeX Error: Command \footref already defined.,
   Or name \end... illegal, see p.192 of the manual.

It has probably to do with the preamble in my lyx document (Koma 
script book), but I can't find the culprit


The logfile should list the last loaded package.



It occurs still in a document which I have stripped to one single 
reference and the BibLaTeX generated Bibliography, nothing else


Show the log file

Herbert

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

Re: ! LaTeX Error: Command \footref already defined

[Wolfgang Engelmann]

Am 27.07.21 um 12:27 schrieb Herbert Voss:



Am 27.07.21 um 11:19 schrieb Wolfgang Engelmann:

Has somebody bumped into this error:

! LaTeX Error: Command \footref already defined.,
   Or name \end... illegal, see p.192 of the manual.

It has probably to do with the preamble in my lyx document (Koma 
script book), but I can't find the culprit


The logfile should list the last loaded package.



It occurs still in a document which I have stripped to one single 
reference and the BibLaTeX generated Bibliography, nothing else


Show the log file

Herbert

It is a long log file
Easier to send the lyx file (only one reference and a .) and the bib 
file (only one reference).

Wolfgang


TEST-Error.lyx
Description: application/lyx
% Encoding: UTF-8

@Book{Engelmann2016,
  author= {Engelmann, W. and Witte, K. H.},
  date  = {2016},
  title = {Wie man eine biologische {U}hr stoppen kann: {S}ingularit\"atspunkt},
  publisher = {Universität Tübingen},
}

@Comment{jabref-meta: databaseType:biblatex;}
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: ! LaTeX Error: Command \footref already defined

[Herbert Voss]

Am 27.07.21 um 11:19 schrieb Wolfgang Engelmann:

Has somebody bumped into this error:

! LaTeX Error: Command \footref already defined.,
   Or name \end... illegal, see p.192 of the manual.

It has probably to do with the preamble in my lyx document (Koma 
script book), but I can't find the culprit


The logfile should list the last loaded package.



It occurs still in a document which I have stripped to one single 
reference and the BibLaTeX generated Bibliography, nothing else


Show the log file

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

Re: LaTeX Error: File `symbols.tex' not found

[Saša Janiška]

On Tue, 1 Sep 2020 15:19:50 +0200
Kornel Benko  wrote:

> It must be one of your private files.
> Nothing to be found in texlive ...

Ahh, thanks a lot!! I completely forgot about it...and was not working with
LyX/LaTeX for quite some time considering to possibly switch to ConTeXt.

> Probably something in the latex preamble of the master file.

Yes, it is file refrenced in the preamble to make it easier for me to use
Unicode astro-symbols, but which somehow disappeared. :-)



Sincerely,
Gour

-- 
In this endeavor there is no loss or diminution,
and a little advancement on this path can protect
one from the most dangerous type of fear.


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

Re: LaTeX Error: File `symbols.tex' not found

[Kornel Benko]

Am Tue, 1 Sep 2020 15:00:41 +0200
schrieb Saša Janiška :

> Hello,
> 
> I am trying to typeset some old study notes of mine - document consisting of
> master document and several chapters, but I get the error mentioned in the
> Subject:
> 
> The snippet of the log file is:
> 
> [...]
> Package hyperref Info: Hyper figures OFF on input line 6411.
> Package hyperref Info: Link nesting OFF on input line 6416.
> Package hyperref Info: Hyper index ON on input line 6419.
> Package hyperref Info: backreferencing OFF on input line 6426.
> Package hyperref Info: Link coloring OFF on input line 6431.
> Package hyperref Info: Link coloring with OCG OFF on input line 6436.
> Package hyperref Info: PDF/A mode OFF on input line 6441.
> LaTeX Info: Redefining \ref on input line 6481.
> LaTeX Info: Redefining \pageref on input line 6485.
> \Hy@abspage=\count198
> \c@Item=\count199
> \c@Hfootnote=\count266
> )
> Package hyperref Info: Driver (autodetected): hluatex.
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hluatex.def
> File: hluatex.def 2019/06/12 v6.88h Hyperref driver for luaTeX
> \Fld@listcount=\count267
> \c@bookmark@seq@number=\count268
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty
> Package: rerunfilecheck 2016/05/16 v1.8 Rerun checks for auxiliary files (HO)
> Package uniquecounter Info: New unique counter `rerunfilecheck' on input line 
> 28
> 2.
> )
> \Hy@SectionHShift=\skip58
> )
> 
> ! LaTeX Error: File `symbols.tex' not found.

It must be one of your private files.
Nothing to be found in texlive ...

...
> 
> The strange thing is that if I 'compile' each chapter on its own, everything 
> is
> fine, but attempt with the complete document yields the above error.
> 
> Any clue?

Probably something in the latex preamble of the master file.

> I'm using LyX-2.3.5.2 on Fedora (fc32) Linux, but same thing does happen with
> 2.4.0pre as well as with other TeX engines..

Kornel



pgpN8hckVkeMV.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: LaTeX Error: Too many math alphabets used in version normal.

[Guenter Milde]

On 2019-08-06, Patrick Dupre wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> Hello,

> I got the message:

> LaTeX Error: Too many math alphabets used in version normal.

> How can I fix the issue?

This limitation is lifted in LuaTeX, so compiling with LuaTeX instead of
pdfTeX is a possible solution.

In principle, LuaTeX works fine with traditional TeX fonts and LuX supports
this well. 

However, some 3rd party packages check for the TeX engine
(pdftex/xetex/luatex) and assume Unicode-encoded "non-TeX fonts" are used
with the latter two. This may lead to errors in complex documents.

Günter

Re: LaTeX Error: Too many math alphabets used in version normal.

[Patrick Dupre]

Hello,

Even setting: \newcommand\bmmax{0}
does not help.

It is really annoying. How to solve this issue?
Why such limitation. I am using Latex for 30 years, and it is the first 
time that I am stuck.

Thank for any help.

> > Hello,
> > 
> > I got the message:
> > 
> > LaTeX Error: Too many math alphabets used in version normal.
> > 
> > How can I fix the issue?
> 
> See
> https://texfaq.org/FAQ-manymathalph
> 
> Jürgen
> 
> > Thank
> > 
> > See the log file.
> > 
> > =
> > ==
> >  Patrick DUPRÉ | | email: 
> > pdu...@gmx.com
> >  Laboratoire interdisciplinaire Carnot de Bourgogne
> >  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
> >  Tel: +33 (0)380395988
> > =
> > ==
>

Re: LaTeX Error: Too many math alphabets used in version normal.

[Patrick Dupre]

Actually, now, I get:
 LaTeX Error: Too many symbol fonts declared.
which is a bit different

> \newcommand\bmmax{3}
> \newcommand{\hmmax}{0}
> \usepackage{bm}
> 
> 
> >
> > Am Dienstag, den 06.08.2019, 16:35 +0200 schrieb Patrick Dupre:
> > > Hello,
> > > 
> > > I got the message:
> > > 
> > > LaTeX Error: Too many math alphabets used in version normal.
> > > 
> > > How can I fix the issue?
> > 
> > See
> > https://texfaq.org/FAQ-manymathalph
> > 
> > Jürgen
> > 
> > > Thank
> > > 
> > > See the log file.
> > > 
> > > =
> > > ==
> > >  Patrick DUPRÉ | | email: 
> > > pdu...@gmx.com
> > >  Laboratoire interdisciplinaire Carnot de Bourgogne
> > >  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
> > >  Tel: +33 (0)380395988
> > > =
> > > ==
> >
>

Re: LaTeX Error: Too many math alphabets used in version normal.

[Patrick Dupre]

Thank for the suggestion. But it does help.

I tried both, but I get the same behavior.

\newcommand\bmmax{3}
\newcommand{\hmmax}{0}
\usepackage{bm}


>
> Am Dienstag, den 06.08.2019, 16:35 +0200 schrieb Patrick Dupre:
> > Hello,
> > 
> > I got the message:
> > 
> > LaTeX Error: Too many math alphabets used in version normal.
> > 
> > How can I fix the issue?
> 
> See
> https://texfaq.org/FAQ-manymathalph
> 
> Jürgen
> 
> > Thank
> > 
> > See the log file.
> > 
> > =
> > ==
> >  Patrick DUPRÉ | | email: 
> > pdu...@gmx.com
> >  Laboratoire interdisciplinaire Carnot de Bourgogne
> >  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
> >  Tel: +33 (0)380395988
> > =
> > ==
>

Re: LaTeX Error: Too many math alphabets used in version normal.

[Jürgen Spitzmüller]

Am Dienstag, den 06.08.2019, 16:35 +0200 schrieb Patrick Dupre:
> Hello,
> 
> I got the message:
> 
> LaTeX Error: Too many math alphabets used in version normal.
> 
> How can I fix the issue?

See
https://texfaq.org/FAQ-manymathalph

Jürgen

> Thank
> 
> See the log file.
> 
> =
> ==
>  Patrick DUPRÉ | | email: 
> pdu...@gmx.com
>  Laboratoire interdisciplinaire Carnot de Bourgogne
>  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
>  Tel: +33 (0)380395988
> =
> ==


signature.asc
Description: This is a digitally signed message part

Re: Latex Error: There's no line here to end

[edu Gpl]

Thank you, i sloved this probem by google.
Best regards

بتاريخ ٠٢‏/٠٦‏/٢٠١٧ ٣:٥٦ م، كتب "edu Gpl" :

> Dear Lyx users
> I hope you can help me in this problem in Local Layout.
>
> Errors:
> Latex Error: There's no line here to end
>
> Description:
> \begin{evaluate}
>
> Your command was ignored.
> Type  Ito replace it with another command,
> orto continue without it
>
> please see lyx file in attachments.
>
>
>
>
>
>

Re: Latex Error.

[Guenter Milde]

Dear Gordon,

thank you for the report.
Trying to reproduce your problem...

On 2017-01-14, gordon cooper wrote:
...


> There was the problem, a Hyperlink with a irreconcilable character, a
> beginning itemize dot, like this :

> • http://www.debian.org/doc/FAQ/ch-pkgtools.en.html

This was in an URL inset or Hyperlink inset, right?

> Had a recent mysterious error when trying an Lyx to pdf conversion.
> The same Lyx file converted to html immediately, no errors. 

How about XeTeX or LuaTeX with "non-TeX" (Unicode) fonts? 
Works here.

> I had a coding error, ignored by one converter. A look at the source
> code was not a success.

This leads me to the assumption that you have set the inputencoding
(Document>Settings>Language>Encoding) to "Unicode (utf8)".

IMO, this is a good choice but not much tested on LyX unfortunately as LyX
uses mixed 8-bit encodings by default wit 8-bit "TeX fonts".

With the default encoding, the Source Pane shows the problematic character
in red. 

> The program reported a Latex error but gave no error report.

Here, with utf8 encoding, the error report said "tex capacity exceeded"
while with an 8-bit encoding the error report was the more meaningfull
"could not find LaTeX command for character ...".


Also, inserting non-working Unicode characters into an URL inset is
blocked while copying from somewhere works (but fails later).

Interestingly, some high-bit characters (like äöü) work fine, others are
mangled (ß becomes \T1\ss in the output) others are blocked (e.g. °) (I
suppose, because it is "forced" in lib/unicodesymbols).


The problem here is to prevent the wast of time you experienced without
blocking valid use cases (e.g. export to HTML or with "non-TeX fonts").

Günter

Re: LaTeX Error: Cannot determine size of graphic

[Scott Kostyshak]

Hi Patrick,

You sent the same email 2 days ago to which I responded. Did you get
the response? Are you subscribed to the list?

On Mon, Aug 31, 2015 at 6:02 PM, Patrick Dupre  wrote:

> Is there anyway to fix this issue by asking to lyx to read the
> graphic size without to have to leave lyx?

If you right-click and choose "Reload" does that work?

Scott

Re: LaTeX Error: Cannot determine size of graphic

[Rich Shepard]

On Tue, 1 Sep 2015, Patrick Dupre wrote:


In lyx 2.1.4 (fedora 22) but also with other previous versions, if one
edits a file containing a figure (i.e. a .eps file for example) which is
missing, lyx says "file not found". This is normal. Now, if we update the
directory with the right file (we can even browse it from lyx), lyx
continues to says "file not found" will it is here.


Patrick,

  That's very strange and has never happened here. Sometimes I re-arrange
directories so the embedded figures are not in the path they were the last
time that document was loaded in LyX. But, when I used the 'Browse' feature
to specify the correct directory, the figure loads and there are no issues
with saving, previewing, or compiling the file.

  Without a small example we cannot determine just where the source of the
issue is to be found.

Rich

Re: LaTeX Error: \begin{Large} on input line 23 ended by \end{document}.

[Jürgen Spitzmüller]

Am Montag 06 Juli 2015, 20:43:05 schrieb Steve Litt:
> I looked at a .tex file created by LyX in November 2013, and that LaTeX
> file used \begin and \end to express homegrown environments. When did
> this change?
> 
> So what are all of you doing about this kind of error? I can't be the
> only one.

If you need an environment in the LaTeX output, you need to define the lyx 
layout as an environment (LatexType Environment, not LatexType Command).

See attached (fixed) layout.

Jürgen
#% Do not delete the line below; configure depends on this
#  \DeclareLaTeXClass[book]{bug_example}



Input stdclass.inc
#Format 11
Input book.layout

Preamble
\newenvironment{proverbL}{\par~\\[0.2ex]\begin{itshape}\begin{Large}}{\end{Large}\end{itshape}~\\[0.3ex]}

EndPreamble

Style Proverb
LatexName   proverbL
LatexType   Environment
Font 
Series   Medium
Size Larger
Shape   Italic
EndFont
End

Re: LaTEX Error: Keyval.sty not found.

[Jürgen Spitzmüller]

educoach wrote:
> Hallo,
> 
> ich habe LyX neu installiert.
> 
> Wenn ich ein Dokument erstelle und dann  auf "Aktualisieren" gehe, erscheint
> folgende Fehlermeldung: LaTEX Error: Keyval.sty not found.
> 
> Was ist zu tun.

http://wiki.lyx.org/FAQ/LaTeXErrors#file-not-found

HTH
Jürgen

> 
> Mit herzlichem Dank
> 
> Uwe

Re: LaTeX Error: \begin{thebibliography} on input line 1 ended by \end{document}.

[KIM Musak]

Oh, Okay. will do that.
Thanks very much

Rgds
Kamarul


On Tue, Jan 21, 2014 at 10:59 PM, Richard Heck  wrote:

> On 01/21/2014 12:01 AM, KIM Musak wrote:
>
>> Dear all,
>>
>> I recently changed the page layout in the document setting (from default
>> format to Height 4 cm and width 4cm). When I tried to view the pdf these
>> are the errors I have received :
>>
>> --
>> Missing $ inserted.
>> Misplaced alignment tab character &.
>> Missing $ inserted.
>> LaTeX Error: \begin{thebibliography} on input line 1 ended by
>> \end{document}.
>> 
>>
>> No PDF output produced. I have changed to default (Document Setting, Page
>> Layout, Page Format) but it still refused to change.
>>
>
> That looks like a URL that isn't properly encoded. Check your bibliography.
>
> Richard
>
>

Re: LaTeX Error: \begin{thebibliography} on input line 1 ended by \end{document}.

[Richard Heck]

On 01/21/2014 12:01 AM, KIM Musak wrote:

Dear all,

I recently changed the page layout in the document setting (from 
default format to Height 4 cm and width 4cm). When I tried to view the 
pdf these are the errors I have received :


--
Missing $ inserted.
Misplaced alignment tab character &.
Missing $ inserted.
LaTeX Error: \begin{thebibliography} on input line 1 ended by 
\end{document}.



No PDF output produced. I have changed to default (Document Setting, 
Page Layout, Page Format) but it still refused to change.


That looks like a URL that isn't properly encoded. Check your bibliography.

Richard

Re: Latex error in viewing all my documents

[Paul A . Rubin]

In case you missed it, have a look at
http://comments.gmane.org/gmane.editors.lyx.general/80614. You may need to
install some language packages from TeXLive.

Paul

Re: LaTeX Error: File `subscript.sty' not found.

[Paul A . Rubin]

If you need the \textsubscript command, I think you can get it by installing the
fixltx2e package, which I believe can be installed through the MiKTeX package
manager.

Paul

Re: LaTeX Error: File `subscript.sty' not found.

[Rafa]

 I have done this 5 steps:

1. download file subscript.sty from
> http://ctan.org/tex-archive/macros/latex/contrib/fragments.
> 
> 
> 
> 
> 2. Create new folder 'Subscript' in your MiKTeX installation folder (e.g.
C:\Program Files\MiKTeX 2.9\tex\latex)
> 
> 
> 
> 
> 3. Copy the file subscript.sty to the folder 'Subscript.
> 
> 
> 4. Execute as root this comand: mktexlsr


5. Reconfigure LyX.

I do not get succesful result.

Thank you at all.

Re: Latex error: Environment subequations undefined

[hubert_cumberdale]

HL2050 wrote
> 
> Hello, I used "\begin{subequations}"  and "\end{subequations}" to have
> equations in between. It worked on my two earlier research papers using
> LyX 1.6 mac os snow leopard. But suddenly the same way stopped working in
> a new LyX file. I just can't figure it out. No clue at all. Can anyone
> help. Thanks.
> 

You just have to *uncheck* the box "Use AMS math package automatically" and
then check "Use AMS math package" in Document -> Settings... -> Math
Options. Then Apply. Worked for me in LyX 2.0.3 with "article (SPIE
Proceedings)" Document Class.



--
View this message in context: 
http://lyx.475766.n2.nabble.com/Latex-error-Environment-subequations-undefined-tp4421640p7580152.html
Sent from the LyX - Users mailing list archive at Nabble.com.

Re: LaTeX Error: Undefined color `BLACK'.

[Julien Rioux]

On 24/01/2012 11:42 PM, Moritz Deecke wrote:

Hallo liebe Lyx-Nutzer und -Entwickler,

ich habe folgendes Problem (Lyx, 2.0.2., Mac OSX 10.6.8.):

Wenn ich eine Textausgabe machen möchte, erscheint folgende Fehlermeldung.
"LaTeX Error: Undefined color `BLACK'."
Dies ist der Fall, seitdem ich den Seitenstil "ausgefallen" aktiviert habe (ich 
möchte fancyheaders benutzen, um die Titel in den Kopfzeilen anzupassen).

Das wäre es eigentlich schon. Seitdem ich die neue Version von Lyx installiert 
habe erscheint auch immer eine Fehlermeldung (über Pfad, Kodierung, utf8), die 
aber eine anscheinend gute Ausgabe des Dokuments nicht verhindert hat.

Für Hilfe wäre ich sehr dankbar.

Beste Grüße

Moritz


Hi,

This is a bug in latex when you convert to uppercase letters (typically 
in a title or section heading). You can work around it by defining a 
`COLOR' for every `color' that exists. In your document preamble:


\definecolor{BLACK}{gray}{0}

Or in this case you could also select the offending text and use the 
character style settings to `reset' the color to default (black).


Cheers,
Julien

Re: LaTeX Error: Undefined color `BLACK'.

[Dr Eberhard Lisse]

I would propose you ask question on an English speaking mailing
list/news group in English.

It also helps to ask LaTeX questions in LaTeX Newsgroups.

Off hand I would think that BLACK is not like Black or even black.

greetings, el


on 2012-01-25 06:42 Moritz Deecke said the following:
> Hallo liebe Lyx-Nutzer und -Entwickler,
> 
> ich habe folgendes Problem (Lyx, 2.0.2., Mac OSX 10.6.8.):
> 
> Wenn ich eine Textausgabe machen möchte, erscheint folgende
> Fehlermeldung.  "LaTeX Error: Undefined color `BLACK'."  Dies ist
> der Fall, seitdem ich den Seitenstil "ausgefallen" aktiviert habe
> (ich möchte fancyheaders benutzen, um die Titel in den Kopfzeilen
> anzupassen).
> 
> Das wäre es eigentlich schon.  Seitdem ich die neue Version von
> Lyx installiert habe erscheint auch immer eine Fehlermeldung
> (über Pfad, Kodierung, utf8), die aber eine anscheinend gute
> Ausgabe des Dokuments nicht verhindert hat.
> 
> Für Hilfe wäre ich sehr dankbar.
> 
> Beste Grüße
> 
> Moritz

Re: LaTeX Error: File `subscript.sty\' not found.

[Murat Yildizoglu]

Hi Roel,

A step is missing in Sergey's instructions : between 3 and 4 you must
refresh Latex's package lists, it is called texhash. If I remember well,
MikTex comes with a utility-configuration program in which you can refresh
the package list. Otherwise, the new package will not be known to Latex,
hence to Lyx, even if you reconfigure.

You can also do it manually : open a terminal as administrator and execute
the following line in it: mktexlsr. It should grind for some time and stop.
Then if you reconfigure, stop and start again Lyx, it should see the new
package.

Murat

2011/11/1 Roel Schipper - CITG 

>  Hello Sergey,
>
> ** **
>
> I have tried this, and manually put the subscript.sty file in the latex
> folder as you described. After reconfiguring and looking in LyX under the
> menu Tools - TeX Information - LaTeX styles, subscript.sty is still not
> visible however. When I want to view the PDF it still comes back with the
> abovementioned error. 
>
> ** **
>
> On my desktop, where the problem occurs, I run LyX and MikTeX 2.9 under
> Windows 7. On my small HP netbook, where I use XP, the problem does not
> occur… However, brewing a PDF on that small machine takes a long time. I
> remember having lots of difficulties with administrator/user rights when
> installing LyX 2.0 on both machines. Probably there is a slight difference
> between both installations.
>
> ** **
>
> I have a workaround by using math for subscripts now.
>
> ** **
>
> Kindly,
>
> Roel
>
> ** **
>
> *From:* Churilov Sergey [mailto:curi...@gf.ukim.edu.mk]
> *Sent:* vrijdag 28 oktober 2011 22:30
> *To:* lyx-users@lists.lyx.org
> *Cc:* H.R.Schipper@
> *Subject:* LaTeX Error: File `subscript.sty\' not found. 
>
> ** **
>
> Hi Roel,
>
>  
>
> I came across this problem recently and I solved it like this:
>
> 1. download file subscript.sty from
> http://ctan.org/tex-archive/macros/latex/contrib/fragments.
>
> 2. Create new folder 'Subscript' in your MiKTeX installation folder (e.g.
> C:\Program Files\MiKTeX 2.9\tex\latex)
>
> 3. Copy the file subscript.sty to the folder 'Subscript.
>
> 4. Reconfigure LyX.
>
>  
>
> I am using MiKTeX 2.9 and LyX 2.9 on WinXP. This procedure solved my
> problem.
>
> I hope it can be useful in your case.
>
>  
>
> Regards,
>
> Sergey
>



-- 
Prof. Murat Yildizoglu

Université Montesquieu Bordeaux IV
GREThA (UMR CNRS 5113)
Avenue Léon Duguit
33608 Pessac cedex
France

yi...@u-bordeaux4.fr

http://yildizoglu.info

http://www.twitter.com/yildizoglu

RE: LaTeX Error: File `subscript.sty\' not found.

[Roel Schipper - CITG]

Hello Sergey,

I have tried this, and manually put the subscript.sty file in the latex folder 
as you described. After reconfiguring and looking in LyX under the menu Tools - 
TeX Information - LaTeX styles, subscript.sty is still not visible however. 
When I want to view the PDF it still comes back with the abovementioned error.

On my desktop, where the problem occurs, I run LyX and MikTeX 2.9 under Windows 
7. On my small HP netbook, where I use XP, the problem does not occur... 
However, brewing a PDF on that small machine takes a long time. I remember 
having lots of difficulties with administrator/user rights when installing LyX 
2.0 on both machines. Probably there is a slight difference between both 
installations.

I have a workaround by using math for subscripts now.

Kindly,
Roel

From: Churilov Sergey [mailto:curi...@gf.ukim.edu.mk]
Sent: vrijdag 28 oktober 2011 22:30
To: lyx-users@lists.lyx.org
Cc: H.R.Schipper@
Subject: LaTeX Error: File `subscript.sty\' not found.

Hi Roel,

I came across this problem recently and I solved it like this:
1. download file subscript.sty from 
http://ctan.org/tex-archive/macros/latex/contrib/fragments.
2. Create new folder 'Subscript' in your MiKTeX installation folder (e.g. 
C:\Program Files\MiKTeX 2.9\tex\latex)
3. Copy the file subscript.sty to the folder 'Subscript.
4. Reconfigure LyX.

I am using MiKTeX 2.9 and LyX 2.9 on WinXP. This procedure solved my problem.
I hope it can be useful in your case.

Regards,
Sergey

Re: LaTeX Error: File `subscript.sty' not found in MikTeX

[Keith Roberts]

On Thu, 27 Oct 2011, Richard Heck wrote:


To: Roel Schipper - CITG 
From: Richard Heck 
Subject: Re: LaTeX Error: File `subscript.sty' not found in MikTeX

On 10/27/2011 05:40 AM, Roel Schipper - CITG wrote:


Dear Lyx users,



I am using Lyx 2.0 under Windows Vista to update a course reader which
I wrote in version 1.6. I have used sub- and superscripts outside of
the Math environment. When I want to make a PDF, Lyx comes back with
the error “! LaTeX Error: File `subscript.sty' not found.” I have
updated MikTeX and also tried to copy the file “subscript.sty” in the
TeX directory, reconfigured Lyx, but without results.




Someone who uses MikTeX can probably help here. You should be able to
install subscript.sty through the package manager. If you do it
manually, you need (a) to copy it to the right sort of folder and (b)
then to tell MikTeX to update the TeX database.


Hi Richard. I'm new to using LyX on Windows Vista, and from 
what I've seen of MiKTeX, it can be configured to 
automatically install any missing TeX packages on-the-fly.


http://www.miktex.org/about

"Integrated package management"

"MiKTeX's integrated package manager installs missing 
components from the Internet, if required.


For example, the LaTeX directive

\usepackage{memoir}

would trigger the installer, if the memoir package is not 
already installed.


This unique feature allows you to keep your computer 
clutter-free: only install packages you actually need."


It might need to be set in MikTeX's options for it to 
work.


Kind Regards,

Keith

---
Websites:
http://www.karsites.net
http://www.php-debuggers.net
http://www.raised-from-the-dead.org.uk

All email addresses are challenge-response protected with
TMDA [http://tmda.net]
---

Re: LaTeX Error: File `subscript.sty' not found in MikTeX

[Richard Heck]

On 10/27/2011 05:40 AM, Roel Schipper - CITG wrote:
>
> Dear Lyx users,
>
>  
>
> I am using Lyx 2.0 under Windows Vista to update a course reader which
> I wrote in version 1.6. I have used sub- and superscripts outside of
> the Math environment. When I want to make a PDF, Lyx comes back with
> the error “! LaTeX Error: File `subscript.sty' not found.” I have
> updated MikTeX and also tried to copy the file “subscript.sty” in the
> TeX directory, reconfigured Lyx, but without results.
>
>  
>
Someone who uses MikTeX can probably help here. You should be able to
install subscript.sty through the package manager. If you do it
manually, you need (a) to copy it to the right sort of folder and (b)
then to tell MikTeX to update the TeX database.

Richard

Re: LaTeX Error 'expl3.sty'

[Liviu Andronic]

On Sun, Jul 31, 2011 at 10:55 PM,   wrote:
> Dear LYX Users,
>
> As suggested by Liviu, I tried to install a package "l3experimental" through 
> MiKTex Options but I am getting a problem. While registering the root 
> directory (C:\Local TeX Files) in MiKTeX options, I received a message as 
> "Windows API error 5: Access is denied". My laptop has 32-bit windows system.
>
Only guessing, try to install the package using Admin privileges.
Liviu


> This is creating a problem while converting my lyx document.
>
> It will be a great for me if you give any advice,
>
> Thanking You,
>
> Regards,
>
> Shyam
> Sweden
>
>
> -Original Message-
> From: Liviu Andronic [mailto:landronim...@gmail.com]
> Sent: Sunday, July 31, 2011 8:10 AM
> To: srlp...@gmail.com
> Cc: lyx-users@lists.lyx.org
> Subject: Re: LaTeX Error 'expl3.sty'
>
> On Sun, Jul 31, 2011 at 1:44 AM,   wrote:
>> When I try to View [PDF(XeTex)] of my lyx file, I am getting a xetex Errors
>> as LaTeX Errors: `expl3.sty’ not found. I also tried to install it through
>> Miktex Package Manager, but I received a MiKTeX Problem Report as Unknown
>> archieve file size and it did not work. So, I cannot covert my LYX document
>> into PDF.
>>
>> Could you please suggest me to resolve the problem?
>>
> Try installing l3experimental. See [1][2].
> Liviu
>
> [1] http://ctan.org/pkg/chemnum
> [2] http://ctan.org/pkg/l3experimental
>
>



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

RE: LaTeX Error 'expl3.sty'

[srlprrn]

Dear LYX Users,

As suggested by Liviu, I tried to install a package "l3experimental" through 
MiKTex Options but I am getting a problem. While registering the root directory 
(C:\Local TeX Files) in MiKTeX options, I received a message as "Windows API 
error 5: Access is denied". My laptop has 32-bit windows system.

This is creating a problem while converting my lyx document. 

It will be a great for me if you give any advice,

Thanking You,

Regards,

Shyam 
Sweden


-Original Message-
From: Liviu Andronic [mailto:landronim...@gmail.com] 
Sent: Sunday, July 31, 2011 8:10 AM
To: srlp...@gmail.com
Cc: lyx-users@lists.lyx.org
Subject: Re: LaTeX Error 'expl3.sty'

On Sun, Jul 31, 2011 at 1:44 AM,   wrote:
> When I try to View [PDF(XeTex)] of my lyx file, I am getting a xetex Errors
> as LaTeX Errors: `expl3.sty’ not found. I also tried to install it through
> Miktex Package Manager, but I received a MiKTeX Problem Report as Unknown
> archieve file size and it did not work. So, I cannot covert my LYX document
> into PDF.
>
> Could you please suggest me to resolve the problem?
>
Try installing l3experimental. See [1][2].
Liviu

[1] http://ctan.org/pkg/chemnum
[2] http://ctan.org/pkg/l3experimental

Re: LaTeX Error 'expl3.sty'

[Liviu Andronic]

On Sun, Jul 31, 2011 at 1:44 AM,   wrote:
> When I try to View [PDF(XeTex)] of my lyx file, I am getting a xetex Errors
> as LaTeX Errors: `expl3.sty’ not found. I also tried to install it through
> Miktex Package Manager, but I received a MiKTeX Problem Report as Unknown
> archieve file size and it did not work. So, I cannot covert my LYX document
> into PDF.
>
> Could you please suggest me to resolve the problem?
>
Try installing l3experimental. See [1][2].
Liviu

[1] http://ctan.org/pkg/chemnum
[2] http://ctan.org/pkg/l3experimental

Re: LaTeX Error: File `ulem.sty' not found

[Pavel Sanda]

Jose Quesada wrote:
> yes, but not the latex3 packages:
> (in any case, I fixed it with texhash, thanks to Liviu and the list)

and do you have set latex USE flag when emerging lyx? texhash is done
automatically for you then...

pavel

Re: LaTeX Error: File `ulem.sty' not found

[Jose Quesada]

yes, but not the latex3 packages:
(in any case, I fixed it with texhash, thanks to Liviu and the list)
# es dev-texlive/texlive-latex
>>  @@ Searching...
>>  @@ Package: dev-texlive/texlive-latex-2010 branch: 5, [
repo_sabayonlinux.org]
>>  Available:  version: 2010 ~ tag: NoTag ~ revision: 0
>>  Installed:  version: 2010 ~ tag: NoTag ~ revision: 0
>>  Slot:   0
>>  Homepage:   http://www.tug.org/texlive/
>>  Description:TeXLive Basic LaTeX packages
>>  License:GPL-2 LPPL-1.3
>>  @@ Package: dev-texlive/texlive-latex3-2010 branch: 5, [
repo_sabayonlinux.org]
>>  Available:  version: 2010 ~ tag: NoTag ~ revision: 0
>>  Installed:  version: Not installed ~ tag: N/A ~ revision:
N/A
>>  Slot:   0
>>  Homepage:   http://www.tug.org/texlive/
>>  Description:TeXLive LaTeX3 packages
>>  License:GPL-2 LPPL-1.3
>>  @@ Package: dev-texlive/texlive-latexextra-2010 branch: 5, [
repo_sabayonlinux.org]
>>  Available:  version: 2010 ~ tag: NoTag ~ revision: 0
>>  Installed:  version: Not installed ~ tag: N/A ~ revision:
N/A
>>  Slot:   0
>>  Homepage:   http://www.tug.org/texlive/
>>  Description:TeXLive LaTeX supplementary packages
>>  License:BSD GPL-1 GPL-2 GPL-3 LGPL-2 LPPL-1.2 LPPL-1.3
as-is public-domain
>>  @@ Package: dev-texlive/texlive-latexrecommended-2010 branch: 5, [
repo_sabayonlinux.org]
>>  Available:  version: 2010 ~ tag: NoTag ~ revision: 0
>>  Installed:  version: 2010 ~ tag: NoTag ~ revision: 0
>>  Slot:   0
>>  Homepage:   http://www.tug.org/texlive/
>>  Description:TeXLive LaTeX recommended packages
>>  License:GPL-1 GPL-2 LPPL-1.2 LPPL-1.3 as-is
public-domain
>>   Keywords:   dev-texlive/texlive-latex
>>   Found:  4 entries


On Mon, Dec 13, 2010 at 1:38 AM, Pavel Sanda  wrote:

> Jose Quesada wrote:
> > Thanks Liviu.
> > The package is not there. Do you think this is a bug? If so, I'll fill it
> on
> > my distro's tracker.
>
> do you have dev-texlive/texlive-latex installed?
> pavel
>



-- 
Best,
-Jose

Jose Quesada, PhD.
Research scientist,
Max Planck Institute,
Center for Adaptive Behavior and Cognition,
Berlin
http://www.josequesada.name/
http://twitter.com/Quesada

Re: LaTeX Error: File `ulem.sty' not found

[Pavel Sanda]

Jose Quesada wrote:
> Thanks Liviu.
> The package is not there. Do you think this is a bug? If so, I'll fill it on
> my distro's tracker.

do you have dev-texlive/texlive-latex installed?
pavel

Re: LaTeX Error: File `ulem.sty' not found

[Liviu Andronic]

On Sun, Dec 12, 2010 at 12:03 PM, Jose Quesada  wrote:
> Looking at the source, I see:
>
> % Added by lyx2lyx
> %  for proper underlining
> \PassOptionsToPackage{normalem}{ulem}
> \usepackage{ulem}
>
> I don't think I use it, but if lyx2lyx inserts it, I'll need it anytime I
> open a lyx doc produced with an older lyx, which is often...
>
> It may be simpler to download it to /usr/share/texmf-dist/tex/latex/
>
Did you update your LaTeX config after doing so? Check Help >
Customisation > 5.1 > point 4 (but it'd be a good idea to read
attentively the entire section).

Liviu


> and hit
> reconfigure.
> EDIT: I just did that, lyx still complains that it's not there. Why is
> lyx2lyx adding this? (if it is!)
> Even comenting it out:
> %\PassOptionsToPackage{normalem}{ulem}
> %\usepackage{ulem}
>
>  will keep complaining...
>
> Thanks
> -Jose
>
> On Sun, Dec 12, 2010 at 10:42 AM, Liviu Andronic 
> wrote:
>>
>> On Sun, Dec 12, 2010 at 10:35 AM, Jose Quesada  wrote:
>> > Thanks Liviu.
>> > The package is not there. Do you think this is a bug? If so, I'll fill
>> > it on
>> > my distro's tracker.
>> >
>> I'd first try a 'locate ulem' to see if there are problems with some
>> LaTeX configs. Otherwise, if possible, try searching on-line your
>> distro's packages and see which one contains (should contain)
>> ulem.sty. Last resort, make sure that you actually need to use "funny"
>> underlining in Text style (wavy, double, and so on).
>>
>> Regards
>> Liviu
>>
>>
>>
>> > Right now, there's no error anymore, but no output (pdf or anything
>> > else)
>> > whatsoever...
>> >
>> > -J
>> >
>> > On Sun, Dec 12, 2010 at 10:28 AM, Liviu Andronic
>> > 
>> > wrote:
>> >>
>> >> On Sun, Dec 12, 2010 at 9:53 AM, Jose Quesada 
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > I'm on sabayon 5.4, using package dev-texlive/texlive-latex-2010 and
>> >> > lyx
>> >> > 2.0
>> >> > svn.
>> >> >
>> >> > When pressing the pdflatex button, I get:
>> >> >
>> >> > LaTeX Error: File `ulem.sty' not found
>> >> >
>> >> This should normally come with texlive-latex-base (on Ubuntu).
>> >>
>> >>
>> >> http://packages.ubuntu.com/search?searchon=contents&keywords=ulem.sty&mode=exactfilename&suite=maverick&arch=any
>> >>
>> >> Try Tools > Reconfigure, then Tools > TeX Info > Styles and check that
>> >> it's in the list. Regards
>> >> Liviu
>> >>
>> >>
>> >> > I think this was working before. I'm no latex expert; and this may be
>> >> > package-related but...
>> >> >
>> >> > Do you know what is going on? I've attached the entire log just in
>> >> > case.
>> >> >
>> >> > Thanks!
>> >> >
>> >> > -Jose
>> >> >
>> >> > PS: this happens with KOMA article and article; I haven't tried all
>> >> > templates, though.
>> >> >
>> >> >
>> >> > This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010)
>> >> > (format=pdflatex
>> >> > 2010.11.20) 12 DEC 2010 09:41
>> >> >
>> >> > entering extended mode
>> >> >
>> >> > restricted \write18 enabled.
>> >> >
>> >> > %&-line parsing enabled.
>> >> >
>> >> > **exist.de.16.tex
>> >> >
>> >> > (./exist.de.16.tex
>> >> >
>> >> > LaTeX2e <2009/09/24>
>> >> >
>> >> > Babel  and hyphenation patterns for english, dumylang,
>> >> > nohyphenation,
>> >> > lo
>> >> >
>> >> > aded.
>> >> >
>> >> > (/usr/share/texmf-dist/tex/latex/koma-script/scrartcl.cls
>> >> >
>> >> > Document Class: scrartcl 2010/09/17 v3.07 KOMA-Script document class
>> >> > (article)
>> >> >
>> >> > (/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
>> >> >
>> >> > Package: scrkbase 2010/09/17 v3.07 KOMA-Script package
>> >> > (KOMA-Script-dependent b
>> >> >
>> >> > asics and keyval usage)
>> >> >
>> >> > (/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
>> >> >
>> >> > Package: scrbase 2010/09/17 v3.07 KOMA-Script package
>> >> > (KOMA-Script-independent
>> >> >
>> >> > basics and keyval usage)
>> >> >
>> >> > (/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
>> >> >
>> >> > Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
>> >> >
>> >> > \...@toks@=\toks14
>> >> >
>> >> > ) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
>> >> >
>> >> > Package: scrlfile 2009/03/25 v3.03 KOMA-Script package (loading
>> >> > files)
>> >> >
>> >> > Package scrlfile, 2009/03/25 v3.03 KOMA-Script package (loading
>> >> > files)
>> >> >
>> >> > Copyright (C) Markus Kohm
>> >> >
>> >> > ))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
>> >> >
>> >> > Package: tocbasic 2010/09/14 v3.06a KOMA-Script package (handling
>> >> > toc-files)
>> >> >
>> >> > )
>> >> >
>> >> > Package tocbasic Info: omitting babel extension for `toc'
>> >> >
>> >> > (tocbasic) because of feature `nobabel' available
>> >> >
>> >> > (tocbasic) for `toc' on input line 115.
>> >> >
>> >> > Package tocbasic Info: omitting babel extension for `lof'
>> >> >
>> >> > (tocbasic) because of feature `nobabel' available
>> >> >
>> >> > (tocbasic) for `lof' on input line 116.
>> >> >
>> >> > Package tocbasic Info: omitting babel extension for `lot'
>> >> >
>> >> > (tocbasic) because o

Re: LaTeX Error: File `ulem.sty' not found

[Liviu Andronic]

On Sun, Dec 12, 2010 at 10:35 AM, Jose Quesada  wrote:
> Thanks Liviu.
> The package is not there. Do you think this is a bug? If so, I'll fill it on
> my distro's tracker.
>
I'd first try a 'locate ulem' to see if there are problems with some
LaTeX configs. Otherwise, if possible, try searching on-line your
distro's packages and see which one contains (should contain)
ulem.sty. Last resort, make sure that you actually need to use "funny"
underlining in Text style (wavy, double, and so on).

Regards
Liviu



> Right now, there's no error anymore, but no output (pdf or anything else)
> whatsoever...
>
> -J
>
> On Sun, Dec 12, 2010 at 10:28 AM, Liviu Andronic 
> wrote:
>>
>> On Sun, Dec 12, 2010 at 9:53 AM, Jose Quesada  wrote:
>> > Hi,
>> >
>> > I'm on sabayon 5.4, using package dev-texlive/texlive-latex-2010 and lyx
>> > 2.0
>> > svn.
>> >
>> > When pressing the pdflatex button, I get:
>> >
>> > LaTeX Error: File `ulem.sty' not found
>> >
>> This should normally come with texlive-latex-base (on Ubuntu).
>>
>> http://packages.ubuntu.com/search?searchon=contents&keywords=ulem.sty&mode=exactfilename&suite=maverick&arch=any
>>
>> Try Tools > Reconfigure, then Tools > TeX Info > Styles and check that
>> it's in the list. Regards
>> Liviu
>>
>>
>> > I think this was working before. I'm no latex expert; and this may be
>> > package-related but...
>> >
>> > Do you know what is going on? I've attached the entire log just in case.
>> >
>> > Thanks!
>> >
>> > -Jose
>> >
>> > PS: this happens with KOMA article and article; I haven't tried all
>> > templates, though.
>> >
>> >
>> > This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010)
>> > (format=pdflatex
>> > 2010.11.20) 12 DEC 2010 09:41
>> >
>> > entering extended mode
>> >
>> > restricted \write18 enabled.
>> >
>> > %&-line parsing enabled.
>> >
>> > **exist.de.16.tex
>> >
>> > (./exist.de.16.tex
>> >
>> > LaTeX2e <2009/09/24>
>> >
>> > Babel  and hyphenation patterns for english, dumylang,
>> > nohyphenation,
>> > lo
>> >
>> > aded.
>> >
>> > (/usr/share/texmf-dist/tex/latex/koma-script/scrartcl.cls
>> >
>> > Document Class: scrartcl 2010/09/17 v3.07 KOMA-Script document class
>> > (article)
>> >
>> > (/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
>> >
>> > Package: scrkbase 2010/09/17 v3.07 KOMA-Script package
>> > (KOMA-Script-dependent b
>> >
>> > asics and keyval usage)
>> >
>> > (/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
>> >
>> > Package: scrbase 2010/09/17 v3.07 KOMA-Script package
>> > (KOMA-Script-independent
>> >
>> > basics and keyval usage)
>> >
>> > (/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
>> >
>> > Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
>> >
>> > \...@toks@=\toks14
>> >
>> > ) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
>> >
>> > Package: scrlfile 2009/03/25 v3.03 KOMA-Script package (loading files)
>> >
>> > Package scrlfile, 2009/03/25 v3.03 KOMA-Script package (loading files)
>> >
>> > Copyright (C) Markus Kohm
>> >
>> > ))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
>> >
>> > Package: tocbasic 2010/09/14 v3.06a KOMA-Script package (handling
>> > toc-files)
>> >
>> > )
>> >
>> > Package tocbasic Info: omitting babel extension for `toc'
>> >
>> > (tocbasic) because of feature `nobabel' available
>> >
>> > (tocbasic) for `toc' on input line 115.
>> >
>> > Package tocbasic Info: omitting babel extension for `lof'
>> >
>> > (tocbasic) because of feature `nobabel' available
>> >
>> > (tocbasic) for `lof' on input line 116.
>> >
>> > Package tocbasic Info: omitting babel extension for `lot'
>> >
>> > (tocbasic) because of feature `nobabel' available
>> >
>> > (tocbasic) for `lot' on input line 117.
>> >
>> > Class scrartcl Info: File `scrsize11pt.clo' used instead of
>> >
>> > (scrartcl) file `scrsize11.clo' to setup font sizes on input line 121
>> >
>> > 0.
>> >
>> > (/usr/share/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
>> >
>> > File: scrsize11pt.clo 2010/09/17 v3.07 KOMA-Script font size class
>> > option
>> > (11pt
>> >
>> > )
>> >
>> > ) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
>> >
>> > Package: typearea 2010/09/17 v3.07 KOMA-Script package (type area)
>> >
>> > Package typearea, 2010/09/17 v3.07 KOMA-Script package (type area)
>> >
>> > Copyright (C) Frank Neukam, 1992-1994
>> >
>> > Copyright (C) Markus Kohm, 1994-
>> >
>> > \...@bcor=\skip41
>> >
>> > \...@div=\count79
>> >
>> > \...@hblk=\skip42
>> >
>> > \...@vblk=\skip43
>> >
>> > \...@temp=\skip44
>> >
>> > Package typearea Info: These are the values describing the layout:
>> >
>> > (typearea) DIV = 10
>> >
>> > (typearea) BCOR = 0.0pt
>> >
>> > (typearea) \paperwidth = 597.50793pt
>> >
>> > (typearea) \textwidth = 418.2pt
>> >
>> > (typearea) DIV departure = -6%
>> >
>> > (typearea) \evensidemargin = 17.3562pt
>> >
>> > (typearea) \oddsidemargin = 17.3562pt
>> >
>> > (typearea) \paperheight = 845.04694pt
>> >
>> > (typearea) \textheight = 595.80026pt
>> >
>> > (typearea) \top

Re: LaTeX Error: File `ulem.sty' not found

[Jose Quesada]

Thanks Liviu.
The package is not there. Do you think this is a bug? If so, I'll fill it on
my distro's tracker.
Right now, there's no error anymore, but no output (pdf or anything else)
whatsoever...

-J

On Sun, Dec 12, 2010 at 10:28 AM, Liviu Andronic wrote:

> On Sun, Dec 12, 2010 at 9:53 AM, Jose Quesada  wrote:
> > Hi,
> >
> > I'm on sabayon 5.4, using package dev-texlive/texlive-latex-2010 and lyx
> 2.0
> > svn.
> >
> > When pressing the pdflatex button, I get:
> >
> > LaTeX Error: File `ulem.sty' not found
> >
> This should normally come with texlive-latex-base (on Ubuntu).
>
> http://packages.ubuntu.com/search?searchon=contents&keywords=ulem.sty&mode=exactfilename&suite=maverick&arch=any
>
> Try Tools > Reconfigure, then Tools > TeX Info > Styles and check that
> it's in the list. Regards
> Liviu
>
>
> > I think this was working before. I'm no latex expert; and this may be
> > package-related but...
> >
> > Do you know what is going on? I've attached the entire log just in case.
> >
> > Thanks!
> >
> > -Jose
> >
> > PS: this happens with KOMA article and article; I haven't tried all
> > templates, though.
> >
> >
> > This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010)
> (format=pdflatex
> > 2010.11.20) 12 DEC 2010 09:41
> >
> > entering extended mode
> >
> > restricted \write18 enabled.
> >
> > %&-line parsing enabled.
> >
> > **exist.de.16.tex
> >
> > (./exist.de.16.tex
> >
> > LaTeX2e <2009/09/24>
> >
> > Babel  and hyphenation patterns for english, dumylang,
> nohyphenation,
> > lo
> >
> > aded.
> >
> > (/usr/share/texmf-dist/tex/latex/koma-script/scrartcl.cls
> >
> > Document Class: scrartcl 2010/09/17 v3.07 KOMA-Script document class
> > (article)
> >
> > (/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
> >
> > Package: scrkbase 2010/09/17 v3.07 KOMA-Script package
> > (KOMA-Script-dependent b
> >
> > asics and keyval usage)
> >
> > (/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
> >
> > Package: scrbase 2010/09/17 v3.07 KOMA-Script package
> > (KOMA-Script-independent
> >
> > basics and keyval usage)
> >
> > (/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
> >
> > Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
> >
> > \...@toks@=\toks14
> >
> > ) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
> >
> > Package: scrlfile 2009/03/25 v3.03 KOMA-Script package (loading files)
> >
> > Package scrlfile, 2009/03/25 v3.03 KOMA-Script package (loading files)
> >
> > Copyright (C) Markus Kohm
> >
> > ))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
> >
> > Package: tocbasic 2010/09/14 v3.06a KOMA-Script package (handling
> toc-files)
> >
> > )
> >
> > Package tocbasic Info: omitting babel extension for `toc'
> >
> > (tocbasic) because of feature `nobabel' available
> >
> > (tocbasic) for `toc' on input line 115.
> >
> > Package tocbasic Info: omitting babel extension for `lof'
> >
> > (tocbasic) because of feature `nobabel' available
> >
> > (tocbasic) for `lof' on input line 116.
> >
> > Package tocbasic Info: omitting babel extension for `lot'
> >
> > (tocbasic) because of feature `nobabel' available
> >
> > (tocbasic) for `lot' on input line 117.
> >
> > Class scrartcl Info: File `scrsize11pt.clo' used instead of
> >
> > (scrartcl) file `scrsize11.clo' to setup font sizes on input line 121
> >
> > 0.
> >
> > (/usr/share/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
> >
> > File: scrsize11pt.clo 2010/09/17 v3.07 KOMA-Script font size class option
> > (11pt
> >
> > )
> >
> > ) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
> >
> > Package: typearea 2010/09/17 v3.07 KOMA-Script package (type area)
> >
> > Package typearea, 2010/09/17 v3.07 KOMA-Script package (type area)
> >
> > Copyright (C) Frank Neukam, 1992-1994
> >
> > Copyright (C) Markus Kohm, 1994-
> >
> > \...@bcor=\skip41
> >
> > \...@div=\count79
> >
> > \...@hblk=\skip42
> >
> > \...@vblk=\skip43
> >
> > \...@temp=\skip44
> >
> > Package typearea Info: These are the values describing the layout:
> >
> > (typearea) DIV = 10
> >
> > (typearea) BCOR = 0.0pt
> >
> > (typearea) \paperwidth = 597.50793pt
> >
> > (typearea) \textwidth = 418.2pt
> >
> > (typearea) DIV departure = -6%
> >
> > (typearea) \evensidemargin = 17.3562pt
> >
> > (typearea) \oddsidemargin = 17.3562pt
> >
> > (typearea) \paperheight = 845.04694pt
> >
> > (typearea) \textheight = 595.80026pt
> >
> > (typearea) \topmargin = -25.16531pt
> >
> > (typearea) \headheight = 17.0pt
> >
> > (typearea) \headsep = 20.40001pt
> >
> > (typearea) \topskip = 11.0pt
> >
> > (typearea) \footskip = 47.60002pt
> >
> > (typearea) \baselineskip = 13.6pt
> >
> > (typearea) on input line 1134.
> >
> > )
> >
> > \...@part=\count80
> >
> > \...@section=\count81
> >
> > \...@subsection=\count82
> >
> > \...@subsubsection=\count83
> >
> > \...@paragraph=\count84
> >
> > \...@subparagraph=\count85
> >
> > \abovecaptionskip=\skip45
> >
> > \belowcaptionskip=\skip46
> >
> > \...@pti@n...@sid@b...@x=\box26
> >
> > \...@figure=\cou

Re: LaTeX Error: File `ulem.sty' not found

[Liviu Andronic]

On Sun, Dec 12, 2010 at 9:53 AM, Jose Quesada  wrote:
> Hi,
>
> I'm on sabayon 5.4, using package dev-texlive/texlive-latex-2010 and lyx 2.0
> svn.
>
> When pressing the pdflatex button, I get:
>
> LaTeX Error: File `ulem.sty' not found
>
This should normally come with texlive-latex-base (on Ubuntu).
http://packages.ubuntu.com/search?searchon=contents&keywords=ulem.sty&mode=exactfilename&suite=maverick&arch=any

Try Tools > Reconfigure, then Tools > TeX Info > Styles and check that
it's in the list. Regards
Liviu


> I think this was working before. I'm no latex expert; and this may be
> package-related but...
>
> Do you know what is going on? I've attached the entire log just in case.
>
> Thanks!
>
> -Jose
>
> PS: this happens with KOMA article and article; I haven't tried all
> templates, though.
>
>
> This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) (format=pdflatex
> 2010.11.20) 12 DEC 2010 09:41
>
> entering extended mode
>
> restricted \write18 enabled.
>
> %&-line parsing enabled.
>
> **exist.de.16.tex
>
> (./exist.de.16.tex
>
> LaTeX2e <2009/09/24>
>
> Babel  and hyphenation patterns for english, dumylang, nohyphenation,
> lo
>
> aded.
>
> (/usr/share/texmf-dist/tex/latex/koma-script/scrartcl.cls
>
> Document Class: scrartcl 2010/09/17 v3.07 KOMA-Script document class
> (article)
>
> (/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
>
> Package: scrkbase 2010/09/17 v3.07 KOMA-Script package
> (KOMA-Script-dependent b
>
> asics and keyval usage)
>
> (/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
>
> Package: scrbase 2010/09/17 v3.07 KOMA-Script package
> (KOMA-Script-independent
>
> basics and keyval usage)
>
> (/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
>
> Package: keyval 1999/03/16 v1.13 key=value parser (DPC)
>
> \...@toks@=\toks14
>
> ) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
>
> Package: scrlfile 2009/03/25 v3.03 KOMA-Script package (loading files)
>
> Package scrlfile, 2009/03/25 v3.03 KOMA-Script package (loading files)
>
> Copyright (C) Markus Kohm
>
> ))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
>
> Package: tocbasic 2010/09/14 v3.06a KOMA-Script package (handling toc-files)
>
> )
>
> Package tocbasic Info: omitting babel extension for `toc'
>
> (tocbasic) because of feature `nobabel' available
>
> (tocbasic) for `toc' on input line 115.
>
> Package tocbasic Info: omitting babel extension for `lof'
>
> (tocbasic) because of feature `nobabel' available
>
> (tocbasic) for `lof' on input line 116.
>
> Package tocbasic Info: omitting babel extension for `lot'
>
> (tocbasic) because of feature `nobabel' available
>
> (tocbasic) for `lot' on input line 117.
>
> Class scrartcl Info: File `scrsize11pt.clo' used instead of
>
> (scrartcl) file `scrsize11.clo' to setup font sizes on input line 121
>
> 0.
>
> (/usr/share/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
>
> File: scrsize11pt.clo 2010/09/17 v3.07 KOMA-Script font size class option
> (11pt
>
> )
>
> ) (/usr/share/texmf-dist/tex/latex/koma-script/typearea.sty
>
> Package: typearea 2010/09/17 v3.07 KOMA-Script package (type area)
>
> Package typearea, 2010/09/17 v3.07 KOMA-Script package (type area)
>
> Copyright (C) Frank Neukam, 1992-1994
>
> Copyright (C) Markus Kohm, 1994-
>
> \...@bcor=\skip41
>
> \...@div=\count79
>
> \...@hblk=\skip42
>
> \...@vblk=\skip43
>
> \...@temp=\skip44
>
> Package typearea Info: These are the values describing the layout:
>
> (typearea) DIV = 10
>
> (typearea) BCOR = 0.0pt
>
> (typearea) \paperwidth = 597.50793pt
>
> (typearea) \textwidth = 418.2pt
>
> (typearea) DIV departure = -6%
>
> (typearea) \evensidemargin = 17.3562pt
>
> (typearea) \oddsidemargin = 17.3562pt
>
> (typearea) \paperheight = 845.04694pt
>
> (typearea) \textheight = 595.80026pt
>
> (typearea) \topmargin = -25.16531pt
>
> (typearea) \headheight = 17.0pt
>
> (typearea) \headsep = 20.40001pt
>
> (typearea) \topskip = 11.0pt
>
> (typearea) \footskip = 47.60002pt
>
> (typearea) \baselineskip = 13.6pt
>
> (typearea) on input line 1134.
>
> )
>
> \...@part=\count80
>
> \...@section=\count81
>
> \...@subsection=\count82
>
> \...@subsubsection=\count83
>
> \...@paragraph=\count84
>
> \...@subparagraph=\count85
>
> \abovecaptionskip=\skip45
>
> \belowcaptionskip=\skip46
>
> \...@pti@n...@sid@b...@x=\box26
>
> \...@figure=\count86
>
> \...@table=\count87
>
> \bibindent=\dimen102
>
> ) (/usr/share/texmf-dist/tex/latex/base/fontenc.sty
>
> Package: fontenc 2005/09/27 v1.99g Standard LaTeX package
>
> (/usr/share/texmf-dist/tex/latex/base/t1enc.def
>
> File: t1enc.def 2005/09/27 v1.99g Standard LaTeX file
>
> LaTeX Font Info: Redeclaring font encoding T1 on input line 43.
>
> )) (/usr/share/texmf-dist/tex/latex/base/inputenc.sty
>
> Package: inputenc 2008/03/30 v1.1d Input encoding file
>
> \inp...@prehook=\toks15
>
> \inp...@posthook=\toks16
>
> (/usr/share/texmf-dist/tex/latex/base/latin9.def
>
> File: latin9.def 2008/03/30 v1.1d Input encoding file
>
> )) (/usr/share/texmf-d

Re: Latex error

[Jürgen Spitzmüller]

Guenter Milde wrote:
> With pleasure (attached).

Excellent, thanks. I'll have a look at it soon.

Jürgen

Re: Latex error

[Guenter Milde]

On 2010-11-15, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:

>> Some comments: 

>> * Does  

>>   # InternalEncoding   

>>   relate to a font-encoding switch with Babel? 

> yes.

>>   Then it should be true also for e.g. languages with cyrillic script
>>   (even if T2A - T2C are standard font encodings, the font-encoding
>>   switch is hard-coded in Babel and interferes with XeTeX/LuaTeX).

> This bool is currently (only) used in
> Paragraph::Private::latexSpecialChar to avoid the use of latexSpecialT1
> when such a language is used within a T1- encoded document. It cures
> some bug, but I do not remember right now which one.

> It might be that we need to add some more languages, yes. But we will
> have to re-check first if it really is necessary.

So I suppose it might rather indicate a non-standard (i.e. non T*)
font encoding which has problems with "fake" symbols like

  \DeclareTextCommandDefault{\textcopyright}{\textcircled{c}}

that expect an ASCII char to output itself. 
The name of this key should reflect this (if my assumption proves true).


>> * Encoding(not with XeTeX/LuaTeX)

>>   is the default of the LaTeX source (for LaTeX the "input encoding").
>>   The keyword name should reflect this (in our Unicode-times) rather
>>   restricted meaning. (I prefer utf-8 as default LaTeX input encoding
>>   if the users locale indicates utf-8 is in use on the system, but this
>>   is yet another change.)

> I'm not sure I understand you here. The encoding is not the default, it is 
> used whenever we switch to said language.

Only, if the LyX output encoding is "Default", which translates to 
"use the language-default encodings for each language".

I argue that the use of multiple encodings in one file results in a
"unfriendly" LaTeX source. It does save some bytes but makes it very
hard to view/edit and impossible to re-encode the source.

This might be required for "pre-Unicode" CJK or Arabic, but is bad for
languages using Latin, Greek, and Cyrillic scripts.


> And for classic LaTeX, I thing we should stick with these encodings for
> now. I don't consider inputenc's utf8 support mature enough.  

I would remove the iso-* and koi-* encoding settings.

inputencs utf8 support is rudimentary but actually quite mature. It even
avoids bugs in older encodings (like the conversion of the micro sign µ
to a mathematical \mu). Combined with LyX's strong Unicode->LaTeX support
it makes for a good choice on a UTF-8-based system.

>> * Language codes:

>>   the "best current practice" for language codes on the Web advises to
>>   use country codes only if necessary to disambiguate.
>>   http://www.rfc-editor.org/rfc/bcp/bcp47.txt
>>   http://www.w3.org/International/articles/language-tags/

>>   I suggest to drop the country codes whenever the default variant of a
>>   language is used.

> I'm not sure. We need these codes, amongst others, for the spellchecker and 
> the thesaurus. Changing the codes right now could break working things.

Than this should be documented.

> As said, I do not want to change more than necessary at this point of the 
> development cycle. Refinements can be done for LyX 2.1.

OK.

Günter

Re: Latex error

[Jürgen Spitzmüller]

Some comments:

Guenter Milde wrote:
> +Language ancientgreek
> + GuiName "Greek (ancient)"
> + PolyglossiaName greek
> + PolyglossiaOpts variant=ancient
> + LangCodegrc
> +End

Please do not add new languages now. This would be a file format change (needs 
lyx2lyx conversion etc.). For now, we'll stick with the currently supported 
languages.

(you can add the new languages if you comment them out).

> @@ -96,7 +115,7 @@ Language austrian
>   GuiName "German (Austria, old spelling)"
>   BabelName   austrian
>   Encodingiso8859-15
> - LangCodede_AT
> + LangCodede_AT_1901
>  End

This will break aspell

> -# german does not use a country code (due to the variety)
>  Language german
>   GuiName "German (old spelling)"
>   BabelName   german
> + PolyglossiaName german
> + PolyglossiaOpts spelling=old,babelshorthands=true
>   Encodingiso8859-15
> - LangCodede
> - LangVariety alt
> + LangCodede_DE_1901
> + # LangVariety alt
>  End

Likewise. And please do not comment out the variety. This is a crucial feature 
(in order to spellcheck old and new German orthography within one document 
with aspell)!

Jürgen

Re: Latex error

[Jürgen Spitzmüller]

Guenter Milde wrote:
> And here is the diff.

Please send a real attachment (diff or whole file), An inline diff is not very 
useful.

Jürgen

Re: Latex error

[Jürgen Spitzmüller]

Guenter Milde wrote:
> Done.

Great. Could you send the file?

> Some comments: 
> 
> * Does  
>   
>   # InternalEncoding   
>   
>   relate to a font-encoding switch with Babel? 

yes.

>   Then it should be true also for e.g. languages with cyrillic script
>   (even if T2A - T2C are standard font encodings, the font-encoding
>   switch is hard-coded in Babel and interferes with XeTeX/LuaTeX).

This bool is currently (only) used in Paragraph::Private::latexSpecialChar to 
avoid the use of latexSpecialT1 when such a language is used within a T1-
encoded document. It cures some bug, but I do not remember right now which 
one.

It might be that we need to add some more languages, yes. But we will have to 
re-check first if it really is necessary.

> * Encoding(not with XeTeX/LuaTeX)
>   
>   is the default of the LaTeX source (for LaTeX the "input encoding").
>   The keyword name should reflect this (in our Unicode-times) rather
>   restricted meaning. (I prefer utf-8 as default LaTeX input encoding
>   if the users locale indicates utf-8 is in use on the system, but this
>   is yet another change.)

I'm not sure I understand you here. The encoding is not the default, it is 
used whenever we switch to said language.

And for classic LaTeX, I thing we should stick with these encodings for now. I 
don't consider inputenc's utf8 support mature enough.  

> * Language codes:
> 
>   the "best current practice" for language codes on the Web advises to
>   use country codes only if necessary to disambiguate.
>   http://www.rfc-editor.org/rfc/bcp/bcp47.txt
>   http://www.w3.org/International/articles/language-tags/
>   
>   I suggest to drop the country codes whenever the default variant of a
>   language is used.

I'm not sure. We need these codes, amongst others, for the spellchecker and 
the thesaurus. Changing the codes right now could break working things.

As said, I do not want to change more than necessary at this point of the 
development cycle. Refinements can be done for LyX 2.1.

> Günter

Jürgen

Re: Latex error

[Guenter Milde]

On 2010-11-15, Guenter Milde wrote:
> On 2010-11-15, Guenter Milde wrote:
>> On 2010-11-15, Jürgen Spitzmüller wrote:

>>> Maybe. Don't know. I think I would prefer them to be enabled with
>>> German (I always use them quite excessively). But then, I have not yet
>>> used polyglossia myself.

 However, in any case might it be better to provide a PolyglossiaOpts
 keyword, even if it is not used in the first version of the new file...

>>> I guess we should go for the PolyglossiaOpts right away.

> Done.

And here is the diff.

Günter

Exec: git 'diff' 'languages' 2>&1
Dir: /usr/local/src/lyx/lib/

diff --git a/lib/languages b/lib/languages
index ff87033..449ea3a 100644
--- a/lib/languages
+++ b/lib/languages
@@ -7,7 +7,9 @@
 # Language 
 #  GuiName""
 #  BabelName  
-#  Encoding   
+#  PolyglossiaName
+#  PolyglossiaOpts
+#  Encoding(not with XeTeX/LuaTeX)
 #  InternalEncoding   
 #  RTL
 #  AsBabelOptions 
@@ -21,8 +23,12 @@
 #  EndPostBabelPreamble
 # End
 #
-# Omitted elements will be treated as empty
-# (omitted AsBabelOptions, RTL and InternalEncoding as "false")
+# LangCode: code according to Best Current Practice (BCP 47)
+#   http://www.rfc-editor.org/rfc/bcp/bcp47.txt
+#   http://www.w3.org/International/articles/language-tags/
+#   http://www.iana.org/assignments/language-subtag-registry
+#
+# Omitted elements will be treated as empty or (if boolean) "false".
 #
 
 
@@ -33,6 +39,7 @@
 Language ignore
GuiName "Ignore"
BabelName   ignore
+   PolyglossiaName ignore
Encodingiso8859-1
LangCodeignore
 End
@@ -57,6 +64,7 @@ End
 Language albanian
GuiName "Albanian"
BabelName   albanian
+   PolyglossiaName albanian
Encodingiso8859-2
LangCodesq_AL
 End
@@ -64,10 +72,19 @@ End
 Language american
GuiName "English (USA)"
BabelName   american
+   PolyglossiaName english
+   PolyglossiaOpts variant=american
Encodingiso8859-15
LangCodeen_US
 End
 
+Language ancientgreek
+   GuiName "Greek (ancient)"
+   PolyglossiaName greek
+   PolyglossiaOpts variant=ancient
+   LangCodegrc
+End
+
 # FIXME: dummy babel language for arabic_arabtex to be able
 # to switch the language the way of the ArabTeX-package
 Language arabic_arabtex
@@ -81,6 +98,7 @@ End
 Language arabic_arabi
GuiName "Arabic (Arabi)"
BabelName   arabic
+   PolyglossiaName arabic
Encodingcp1256
RTL true
LangCodear_SA
@@ -88,6 +106,7 @@ End
 
 Language armenian
GuiName "Armenian"
+   PolyglossiaName armenian
Encodingarmscii8
LangCodehy_AM
 End
@@ -96,7 +115,7 @@ Language austrian
GuiName "German (Austria, old spelling)"
BabelName   austrian
Encodingiso8859-15
-   LangCodede_AT
+   LangCodede_AT_1901
 End
 
 Language naustrian
@@ -109,6 +128,7 @@ End
 Language bahasa
GuiName "Indonesian"
BabelName   bahasa
+   PolyglossiaName bahasai
Encodingiso8859-15
LangCodeid_ID
 End
@@ -116,6 +136,7 @@ End
 Language bahasam
GuiName "Malay"
BabelName   bahasam
+   PolyglossiaName bahasam
Encodingiso8859-15
LangCodems_MY
 End
@@ -123,6 +144,7 @@ End
 Language basque
GuiName "Basque"
BabelName   basque
+   PolyglossiaName basque
Encodingiso8859-15
LangCodeeu_ES
 End
@@ -137,6 +159,7 @@ End
 Language brazilian
GuiName "Portuguese (Brazil)"
BabelName   brazil
+   PolyglossiaName brazil
Encodingiso8859-15
LangCodept_BR
 End
@@ -144,6 +167,7 @@ End
 Language breton
GuiName "Breton"
BabelName   breton
+   PolyglossiaName breton
Encodingiso8859-15
LangCodebr_FR
 End
@@ -151,6 +175,8 @@ End
 Language british
GuiName "English (UK)"
BabelName   british
+   PolyglossiaName english
+   PolyglossiaOpts variant=british
Encodingiso8859-15
LangCodeen_GB
 End
@@ -158,6 +184,7 @@ End
 Language bulgarian
GuiName "Bulgarian"
BabelName   bulgarian
+   PolyglossiaName bulgarian
Encodingcp1251
LangCodebg_BG
 End
@@ -165,6 +192,8 @@ End
 Language canadian
GuiName "English (Canada)"
BabelName   canadian
+   # PolyglossiaName english
+   # PolyglossiaOpts variant=canadian
Encodi

Re: Latex error

[Guenter Milde]

On 2010-11-15, Guenter Milde wrote:
> On 2010-11-15, Jürgen Spitzmüller wrote:

>> Maybe. Don't know. I think I would prefer them to be enabled with
>> German (I always use them quite excessively). But then, I have not yet
>> used polyglossia myself.

>>> However, in any case might it be better to provide a PolyglossiaOpts
>>> keyword, even if it is not used in the first version of the new file...

>> I guess we should go for the PolyglossiaOpts right away.

Done.

Some comments: 

* Does  
  
  # InternalEncoding   
  
  relate to a font-encoding switch with Babel? 
  
  Then it should be true also for e.g. languages with cyrillic script
  (even if T2A - T2C are standard font encodings, the font-encoding
  switch is hard-coded in Babel and interferes with XeTeX/LuaTeX).

* Encoding(not with XeTeX/LuaTeX)
  
  is the default of the LaTeX source (for LaTeX the "input encoding").
  The keyword name should reflect this (in our Unicode-times) rather
  restricted meaning. (I prefer utf-8 as default LaTeX input encoding
  if the users locale indicates utf-8 is in use on the system, but this
  is yet another change.)
  
* Language codes:

  the "best current practice" for language codes on the Web advises to
  use country codes only if necessary to disambiguate.
  http://www.rfc-editor.org/rfc/bcp/bcp47.txt
  http://www.w3.org/International/articles/language-tags/
  
  I suggest to drop the country codes whenever the default variant of a
  language is used.
  
Günter

Re: Latex error

[Jürgen Spitzmüller]

Guenter Milde wrote:
> BTW: We could do without the new keyword
>   
> AsBabelOptions  
> 
>  if we always call babel with the language options and
>  additionally append them to the document options if the 
>  "add to documentoptions" box is checked.
>  
>  This would be in line with the polyglossia call, where the 
>  languages must always be specified with the \setdefaultlanguage and
>  \setotherlanguage macros but other packages might expect the babel
>  name in the documentoptions.

Maybe. I don't touch this now, though, since I remember Uwe struggling a lot 
to get it right.

(I thought too, however, that the languages should also be passed globally 
notwithstanding the request to do so locally; thus, packages such as varioref 
get the languages information; but this is for later).

Jürgen

Re: Latex error

[Guenter Milde]

On 2010-11-15, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> Where do I find this new file?

> in trunk. Also here:
> http://www.lyx.org/trac/browser/lyx-devel/trunk/lib/languages

>> (I did an update of my trunk clone but lyx/lib/languages is still in
>> the old format.)

> it is supposed to be the new format as of r36285. You probably haven't
> updated correctly.

Indeed, using `git svn rebase` instead of `git svn fetch` did the trick
(I locally changed "languages" sometimes in the past).

So I'll work on this as fast as possible.

...

>> This depends. For example, you can also use

>>   ... convenient shortcuts for loading languages with specific options:

>>   ‣ ogerman = german with option ‘spelling=old’)  

>> i.e.  PolyglossiaName   ogerman

> I do not find these shortcuts documented in the current manual (v1.2.0a).

They are in v1.2.0 but vanished in v1.2.a :-(

> I think I prefer to use the syntax suggested in the manual.

Yes, this is the save option.

>> "babelshorthands" have the warning:

>>   NB: is feature has not been mu tested and should be considered
>>   experimental.

...

> Maybe. Don't know. I think I would prefer them to be enabled with
> German (I always use them quite excessively). But then, I have not yet
> used polyglossia myself.

>> However, in any case might it be better to provide a PolyglossiaOpts
>> keyword, even if it is not used in the first version of the new file...

> I guess we should go for the PolyglossiaOpts right away.

OK.


BTW: We could do without the new keyword
  
AsBabelOptions  

 if we *always* call babel with the language options and
 *additionally* append them to the document options if the 
 "add to documentoptions" box is checked.
 
 This would be in line with the polyglossia call, where the 
 languages must always be specified with the \setdefaultlanguage and
 \setotherlanguage macros but other packages might expect the babel
 name in the documentoptions.


Günter
 
 
 
 

Re: Latex error

[Jürgen Spitzmüller]

Guenter Milde wrote:
> Where do I find this new file?

in trunk. Also here:
http://www.lyx.org/trac/browser/lyx-devel/trunk/lib/languages

> (I did an update of my trunk clone but lyx/lib/languages is still in
> the old format.)

it is supposed to be the new format as of r36285. You probably haven't updated 
correctly.

> > Looking at the polyglossia manual, I learned that we will also need  
> > PolyglossiaOpts. E.g.
> > 
> > Language german
> >
> >  GuiName   "German (old spelling)"
> >  BabelName german
> >  PolyglossiaName   german
> >  PolyglossiaOpts   "spelling=old,babelshorthands=true"
> >  Encoding  iso8859-15
> >  LangCode  de_DE
> >
> > End
> 
> This depends. For example, you can also use
> 
>   ... convenient shortcuts for loading languages with specific options:
>   
>   ‣ ogerman = german with option ‘spelling=old’)  
> 
> i.e.  PolyglossiaName   ogerman

I do not find these shortcuts documented in the current manual (v1.2.0a).
I think I prefer to use the syntax suggested in the manual.

> "babelshorthands" have the warning:
> 
>   NB: is feature has not been mu tested and should be considered
>   experimental.
> 
> Are babelshorthands used by LyX or only accessible via ERT?

Only accessible via ERT. But I think they are crucial for some languages. For 
German, I consider them crucial.

> In the second case we do not need to activate them via GUI but leave
> this to the user preamble.

Maybe. Don't know. I think I would prefer them to be enabled with German (I 
always use them quite excessively). But then, I have not yet used polyglossia 
myself.
  
> However, in any case might it be better to provide a PolyglossiaOpts
> keyword, even if it is not used in the first version of the new file...

I guess we should go for the PolyglossiaOpts right away.

Jürgen

Re: Latex error

[Guenter Milde]

On 2010-11-15, Jürgen Spitzmüller wrote:
> Jürgen Spitzmüller wrote:

>> I have now submitted a new languages file format to trunk. You could help
>> if  you added the polyglossia names there. The syntax would look like:

>> Language ngerman
>> GuiName "German"
>> BabelName   ngerman
>> PolyglossiaName german
>> Encodingiso8859-15
>> LangCodede_DE
>> End

Where do I find this new file?

(I did an update of my trunk clone but lyx/lib/languages is still in
the old format.)

> Looking at the polyglossia manual, I learned that we will also need  
> PolyglossiaOpts. E.g.

> Language german
>  GuiName   "German (old spelling)"
>  BabelName german
>  PolyglossiaName   german
>  PolyglossiaOpts   "spelling=old,babelshorthands=true"
>  Encoding  iso8859-15
>  LangCode  de_DE
> End

This depends. For example, you can also use

  ... convenient shortcuts for loading languages with specific options:
  
  ‣ ogerman = german with option ‘spelling=old’)  

i.e.  PolyglossiaName   ogerman

"babelshorthands" have the warning:

  NB: is feature has not been mu tested and should be considered
  experimental.

Are babelshorthands used by LyX or only accessible via ERT?

In the second case we do not need to activate them via GUI but leave
this to the user preamble.
  
However, in any case might it be better to provide a PolyglossiaOpts
keyword, even if it is not used in the first version of the new file...

Günter

Re: Latex error

[Jürgen Spitzmüller]

Jürgen Spitzmüller wrote:
> Günter,
> 
> I have now submitted a new languages file format to trunk. You could help
> if  you added the polyglossia names there. The syntax would look like:
> 
> Language ngerman
> GuiName "German"
> BabelName   ngerman
> PolyglossiaName german
> Encodingiso8859-15
> LangCodede_DE
> End

Looking at the polyglossia manual, I learned that we will also need  
PolyglossiaOpts. E.g.

Language german
 GuiName   "German (old spelling)"
 BabelName german
 PolyglossiaName   german
 PolyglossiaOpts   "spelling=old,babelshorthands=true"
 Encoding  iso8859-15
 LangCode  de_DE
End

Jürgen

Re: Latex error

[Jürgen Spitzmüller]

Guenter Milde wrote:
> I volunteer to prepare a "languages-polyglossia" (or similar called) file.

Günter,

I have now submitted a new languages file format to trunk. You could help if 
you added the polyglossia names there. The syntax would look like:

Language ngerman
GuiName "German"
BabelName   ngerman
PolyglossiaName german
Encodingiso8859-15
LangCodede_DE
End

If a language is not yet supported by polyglossia, just omit the 
PolyglossiaName entry. This means that you also must specify a PolyglossiaName 
if it is identical to the BabelName.

Jürgen

Re: Latex error

[Pavel Sanda]

Guenter Milde wrote:
> If changing is really planned (before 2.0?)

looking at the list nowadays it seems that even basics of xetex support awake
avalanche, so some xetex improvements have my ok for 2.0 if they come timely.
its basically whether Juergen find some time to look at.

pavel

Re: Latex error

[Guenter Milde]

On 2010-11-12, Jürgen Spitzmüller wrote:
> Jean-Marc Lasgouttes wrote:
>> And turn this language file into a format like layout files, so that  
>> humans can read it...

> Good idea ...

Maybe YAML format?

OTOH, the format is the same as used in unicodedata, so it could be
said to be a LyX config format.


If changing is really planned (before 2.0?), I'd wait with adding
polyglossia-names until it's done and I know how the file should look
like.


Günter

Re: Latex error

[Jürgen Spitzmüller]

Jean-Marc Lasgouttes wrote:
> And turn this language file into a format like layout files, so that  
> humans can read it...

Good idea ...

Jürgen

Re: Latex error

[Jean-Marc Lasgouttes]

Le 12 nov. 10 à 10:29, Jürgen Spitzmüller a écrit :
I volunteer to prepare a "languages-polyglossia" (or similar  
called) file.


I think the former is the way to go: add another column to the  
existing

languages file with the polyglossia terms.


And turn this language file into a format like layout files, so that  
humans can read it...


JMarc

Re: Latex error

[Jürgen Spitzmüller]

Guenter Milde wrote:
> LyX-relevant differences between polyglossia and babel:

Thanks, I put your notes here:
http://wiki.lyx.org/Devel/Polyglossia

> The "latex options" should be ignored (or replaced by "polyglossia
> options")

are there any "polyglossia options"?

> For use with polyglossia, we could consider either
> 
>  * a modified copy of "languages"
> 
>  * a second file only containing the languages with changes overwriting
>the "languages" settings.
> 
>(shorter, but how can we disable languages then?)
> 
> 
> I volunteer to prepare a "languages-polyglossia" (or similar called) file.

I think the former is the way to go: add another column to the existing 
languages file with the polyglossia terms.

> Günter

Jürgen

Re: Latex error

[Guenter Milde]

On 2010-11-09, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:

> Günter, could you set up a document with this comparision and outline exactly
> where polyglossia and babel differ (in terms of what LyX must output/can
> support)?

> I do not have time to dive into the polylossia documentation right now,
> but if your statement is correct, it would be probably easier than I
> thought, and the documentation would help implementing it.

LyX-relevant differences between polyglossia and babel:

Package setup
=

Babel:

  \usepackage[,]{babel}

  * the language options can be given as global document options or
in the babel call.

  * the *last* language becomes the document language.

Polyglossia:

  \usepackage{polyglossia}
  \setdefaultlanguage{}
  \setotherlanguages{}

  * The language options must be given in setup macros after loading
polyglossia.

(Earlier versions allowed also language-options with the *first*
language as document language, but this has been deprecated since
long and removed in the current polyglossia version.)

  * Possibly, still add the document language (with the "babel name") to
the documentoptions if the "global" check box is checked (for use by
other packages).

Alternatively, disable this check box with XeTeX documents and
teach the users to add the document language "by hand" to the
custom document options.


Languages file
===

Some languages are not (yet) supported by polyglossia:

  'af':   'afrikaans',
  'de_at':'naustrian',
  'de_at_1901':   'austrian',
  'fr_ca':'canadien',
  'grc_ibycus':   'ibycus', (Greek Ibycus encoding)
  'sr-latn':  'serbian script=latin'
  'vi':   'vietnam',


Some languages are new or differently named:

  # code  Polyglossia-name   comment
  'cop':  'coptic',
  'de':   'german', # new spelling (de_1996)
  'de_1901':  'ogerman', # old spelling
  'dsb':  'lsorbian',
  'el_polyton':   'polygreek',
  'fa':   'farsi',
  'grc':  'ancientgreek',
  'hsb':  'usorbian',
  'sh-cyrl':  'serbian', # Serbo-Croatian, Cyrillic script
  'sh-latn':  'croatian', # Serbo-Croatian, Latin script
  'sq':   'albanian',
  'sr':   'serbian', # Cyrillic script (sr-cyrl)
  'th':   'thai',

The "encoding" field of the "languages" is irrelevant: 

 always use UTF-8 (xetex)
 
The "latex options" should be ignored (or replaced by "polyglossia
options")

For use with polyglossia, we could consider either 

 * a modified copy of "languages"
 
 * a second file only containing the languages with changes overwriting
   the "languages" settings.
   
   (shorter, but how can we disable languages then?)
   

I volunteer to prepare a "languages-polyglossia" (or similar called) file.

Günter
 

Re: Latex error

[Guenter Milde]

On 2010-11-09, Uwe Stöhr wrote:
> Am 08.11.2010 23:22, schrieb Jean-Marc Lasgouttes:

>> Are we sure that it is needed on a document basis?

> Yes.


>> Now that I think of it, what is the exact effect of "use babel"? Just
>> the usepackage, or more?

> It adds \usepackage{babel} but also adds the used languages as option
> list for the \documentclass command. 

or the babel package, depending on the "global" check-box setting.

> The last language in this option
> list is the document language. When turning off-babel the document
> language is English and the \documentclass command has no language
> options.

... unless you add them via Document>Settings>Class Options>Custom


Günter

Re: Latex error

[Jacob Bishop]

Perhaps without adding a high amount of useful information, I just want to
voice support for this. While writing my thesis, I had to disable the babel
package since there were incompatibilities with the thesis template I was
using.

I feel that making this configurable on a per-document basis is definitely
the right way to go. I also think Richard's suggestion

"What would really be best is if we had a central place, in
Document>Settings, where all such things could be set, for every package we
automatically load. Maybe a combo box listing them, and then when you choose
it, three radio buttons: Load Always, Load As Needed, Load Never. Right now,
we have quite a few such settings scattered about in different places, for
the math packages and other things. But users are always asking for finer
control of package loading with almost every package we load."

would provide a very nice solution.

Just my two bits.

Jacob

Re: Latex error

[Richard Heck]

On 11/08/2010 05:22 PM, Jean-Marc Lasgouttes wrote:

Le 8 nov. 10 à 20:29, Richard Heck a écrit :

On 11/07/2010 11:45 PM, Uwe Stöhr wrote:

Am 07.11.2010 21:59, schrieb Richard Heck:

Shouldn't "Use babel" really be a document setting, rather than a 
preference?


Yes, definitively. Babel needs to be deactivated for some document 
classes and can cause troubles when using XeTeX. XeTeX has its own 
babel replacement and it might be possible that both can interfere.



I'll do this.


Are we sure that it is needed on a document basis? When I see how the 
global language

settings are not going away while being clearly a hack, I have doubts.

Isn't it enough to disable it with XeTeX and use Provide babel 1 when 
needed?


My sense, from the conversations here, is that there are times when one 
wants to load some package in the preamble and one needs to disable the 
automatic loading of babel. One could do "Provide babel 1" in the local 
layout, but that's asking a lot of users. In this particular case, the 
layout file really should use that, but it was format 2, so it's clear 
why it doesn't.


What would really be best is if we had a central place, in 
Document>Settings, where all such things could be set, for every package 
we automatically load. Maybe a combo box listing them, and then when you 
choose it, three radio buttons: Load Always, Load As Needed, Load Never. 
Right now, we have quite a few such settings scattered about in 
different places, for the math packages and other things. But users are 
always asking for finer control of package loading with almost every 
package we load.


Richard

Re: Latex error

[Jürgen Spitzmüller]

Guenter Milde wrote:
> The language switching code in the document is nearly the same. It's the
> preamble code that differs:

Günter, could you set up a document with this comparision and outline exactly 
where polyglossia and babel differ (in terms of what LyX must output/can 
support)?

I do not have time to dive into the polylossia documentation right now, but if 
your statement is correct, it would be probably easier than I thought, and the 
documentation would help implementing it.

Jürgen

Re: Latex error

[Uwe Stöhr]

Am 08.11.2010 23:22, schrieb Jean-Marc Lasgouttes:


Yes, definitively. Babel needs to be deactivated for some document classes and 
can cause troubles
when using XeTeX. XeTeX has its own babel replacement and it might be possible 
that both can
interfere.


I'll do this.


Are we sure that it is needed on a document basis?


Yes.


When I see how the global language settings are not going away while being 
clearly a hack, I have doubts.


What do you mean?


Isn't it enough to disable it with XeTeX and use Provide babel 1 when needed?


No, this issue is independent of XeTeX. It must be possible to turn off babel 
for each document.


Now that I think of it, what is the exact effect of "use babel"? Just the 
usepackage,
or more?


It adds \usepackage{babel} but also adds the used languages as option list for the \documentclass 
command. The last language in this option list is the document language. When turning off-babel the 
document language is English and the \documentclass command has no language options.


regards Uwe

Re: Latex error

[Jean-Marc Lasgouttes]

Le 8 nov. 10 à 20:29, Richard Heck a écrit :

On 11/07/2010 11:45 PM, Uwe Stöhr wrote:

Am 07.11.2010 21:59, schrieb Richard Heck:

Shouldn't "Use babel" really be a document setting, rather than a  
preference?


Yes, definitively. Babel needs to be deactivated for some document  
classes and can cause troubles when using XeTeX. XeTeX has its own  
babel replacement and it might be possible that both can interfere.



I'll do this.


Are we sure that it is needed on a document basis? When I see how the  
global language

settings are not going away while being clearly a hack, I have doubts.

Isn't it enough to disable it with XeTeX and use Provide babel 1 when  
needed?


Now that I think of it, what is the exact effect of "use babel"? Just  
the usepackage,

or more?

JMarc

Re: Latex error

[Guenter Milde]

On 2010-11-08, Jürgen Spitzmüller wrote:
> Uwe Stöhr wrote:
>> We should consider do do this for 2.0 because the users-list is full 
>> with requests of XeTeX and we already implemented basic support.
>> Jürgen, what do you think, will you have time to implement support for 
>> polyglossia?

> No. And I would rather postpone it, since the language handling is deeply 
> entangled with the code. 

The language switching code in the document is nearly the same. It's the
preamble code that differs:

-\usepackage[british,french,ngerman,english]{babel}
+\usepackage{polyglossia}
+\setdefaultlanguage{english}
+\setotherlanguages{german,british,french}

OTOH, there is a different set of supported languages and some languages
have different names:

# Additionally supported or differently named languages:
language_codes.update({
# code  Polyglossia-name   comment
'cop':  'coptic',
'de':   'german', # new spelling (de_1996)
'de_1901':  'ogerman', # old spelling
'dsb':  'lsorbian',
'el_polyton':   'polygreek',
'fa':   'farsi',
'grc':  'ancientgreek',
'hsb':  'usorbian',
'sh-cyrl':  'serbian', # Serbo-Croatian, Cyrillic script
'sh-latn':  'croatian', # Serbo-Croatian, Latin script
'sq':   'albanian',
'sr':   'serbian', # Cyrillic script (sr-cyrl)
'th':   'thai',
# zh-latn:  ???# Chinese Pinyin
})
# Languages without Polyglossia support:
for key in ('af',   # 'afrikaans',
'de_at',# 'naustrian',
'de_at_1901',   # 'austrian',
'fr_ca',# 'canadien',
'grc_ibycus',   # 'ibycus', (Greek Ibycus encoding)
'sr-latn',  # 'serbian script=latin'
'vi'):  # 'vietnam',
del(language_codes[key])


Also, polyglossia is said to be working with XeTeX only, not with
LuaTeX while the newest fontspec supports both engines.

As an alternative, we could consider "Unicode-safe" Babel *.ldf files
for e.g. Russian, Greek, ...
Unfortunately, babel is not very actively maintained but also not free
for adoption.

Günter

Re: Latex error

[Richard Heck]

On 11/07/2010 11:45 PM, Uwe Stöhr wrote:

Am 07.11.2010 21:59, schrieb Richard Heck:

Shouldn't "Use babel" really be a document setting, rather than a 
preference?


Yes, definitively. Babel needs to be deactivated for some document 
classes and can cause troubles when using XeTeX. XeTeX has its own 
babel replacement and it might be possible that both can interfere.



I'll do this.




Uwe, do you know if layouts can disable babel, with e.g.:
Provides babel 1


This is not yet implemented but is easy to do (the same way we do for 
natbib in line 734 of LaTeXFeatures.cpp.). If we implement babel as 
document option we should also implement this.



It looks like this is already there, in fact.

...
bool const use_babel = features.useBabel() && 
!tclass.provides("babel");

if (use_babel) {
language_options << features.getLanguages();
if (!language->babel().empty()) {
if (!language_options.str().empty())
language_options << ',';
language_options << language->babel();
}
...

rh

Re: Latex error

[Sandhya]

Thank you so much. I broke my head over it for days, I guess I should have
sought the experts' help way before :) Thanks again.

On Sun, Nov 7, 2010 at 9:45 PM, Uwe Stöhr  wrote:

> Am 07.11.2010 21:59, schrieb Richard Heck:
>
>
>  Shouldn't "Use babel" really be a document setting, rather than a
>> preference?
>>
>
> Yes, definitively. Babel needs to be deactivated for some document classes
> and can cause troubles when using XeTeX. XeTeX has its own babel replacement
> and it might be possible that both can interfere.
>
>
>  If so, we can still get this into 2.0.
>>
>
> Fine with me but Pavel needs to give his OK for such a last minute change.
>
>
>  Uwe, do you know if layouts can disable babel, with e.g.:
>> Provides babel 1
>>
>
> This is not yet implemented but is easy to do (the same way we do for
> natbib in line 734 of LaTeXFeatures.cpp.). If we implement babel as document
> option we should also implement this.
>
> Can you please take over implemented this as I'm currently too busy?
>
> regards Uwe
>

Re: Latex error

[Uwe Stöhr]

Am 08.11.2010 08:05, schrieb Guenter Milde:


XeTeX has its own babel replacement and it might be possible that both
can interfere.


The babel replacement (the "polyglossia" package) not only can, but
*does* interfere with babel. But, just like babel, it needs to be
loaded explicitely, so this will only show, if you do, e.g.

   \usepackage{polyglossia}
   \setdefaultlanguage{english}
   \setotherlanguages{german,british,french}

in the LaTeX preamble (hopefully, a future LyX will do this
automatically for XeTeX export).


We should consider do do this for 2.0 because the users-list is full 
with requests of XeTeX and we already implemented basic support.
Jürgen, what do you think, will you have time to implement support for 
polyglossia?


regards Uwe

Re: Latex error

[Pavel Sanda]

Uwe Stöhr wrote:
> Yes, definitively. Babel needs to be deactivated for some document classes 
> and can cause troubles when using XeTeX. XeTeX has its own babel 
> replacement and it might be possible that both can interfere.
>
>> If so, we can still get this into 2.0.
>
> Fine with me but Pavel needs to give his OK for such a last minute change.

on the first sight it looks simple enough.
not for beta1 though.

pavel

Re: Latex error

[Guenter Milde]

On 2010-11-08, Uwe Stöhr wrote:
> Am 07.11.2010 21:59, schrieb Richard Heck:

>> Shouldn't "Use babel" really be a document setting, rather than a
>> preference?

> Yes, definitively. Babel needs to be deactivated for some document
> classes and can cause troubles when using XeTeX. 

Seconded.

>> If so, we can still get this into 2.0.

This would be very good indeed.

> XeTeX has its own babel replacement and it might be possible that both
> can interfere.

The babel replacement (the "polyglossia" package) not only can, but
*does* interfere with babel. But, just like babel, it needs to be
loaded explicitely, so this will only show, if you do, e.g. 

  \usepackage{polyglossia}
  \setdefaultlanguage{english}
  \setotherlanguages{german,british,french}

in the LaTeX preamble (hopefully, a future LyX will do this
automatically for XeTeX export).


Günter

Re: Latex error

[Uwe Stöhr]

Am 07.11.2010 21:59, schrieb Richard Heck:


Shouldn't "Use babel" really be a document setting, rather than a preference?


Yes, definitively. Babel needs to be deactivated for some document classes and can cause troubles 
when using XeTeX. XeTeX has its own babel replacement and it might be possible that both can interfere.



If so, we can still get this into 2.0.


Fine with me but Pavel needs to give his OK for such a last minute change.


Uwe, do you know if layouts can disable babel, with e.g.:
Provides babel 1


This is not yet implemented but is easy to do (the same way we do for natbib in line 734 of 
LaTeXFeatures.cpp.). If we implement babel as document option we should also implement this.


Can you please take over implemented this as I'm currently too busy?

regards Uwe

Re: Latex error

[Richard Heck]

On 11/07/2010 10:08 AM, Uwe Stöhr wrote:

Am 06.11.2010 05:23, schrieb Sandhya:

I am using the IJCGA Latex class and Lyx layout files from the LyX 
wiki page

on MacOSX. I copied the *.cls and *.layout files to ~/tex/latex/ and
/Library/Application Support/LyX-1.6/layouts/ respectively. I also
reconfigured LyX. Now when I use the sample LyX document, it 
terminates with

an error:

LaTeX Error: Unknown option `english' for package `graphics'.


This is because LyX uses the package babel by default. This packages 
is necessary if you write non-English documents or English documents 
containing text in other languages. Many article classes don't accept 
babel because they are English-only. So to get it work, go to the LyX 
preferences and uncheck there in the language settings the option "Use 
babel".


But note: it is strongly recommended to re-enable the babel option for 
all other documents you write with LyX.


Shouldn't "Use babel" really be a document setting, rather than a 
preference? If so, we can still get this into 2.0.


Uwe, do you know if layouts can disable babel, with e.g.:
Provides babel 1
??

rh

Re: Latex error

[Uwe Stöhr]

Am 06.11.2010 05:23, schrieb Sandhya:


I am using the IJCGA Latex class and Lyx layout files from the LyX wiki page
on MacOSX. I copied the *.cls and *.layout files to ~/tex/latex/ and
/Library/Application Support/LyX-1.6/layouts/ respectively. I also
reconfigured LyX. Now when I use the sample LyX document, it terminates with
an error:

LaTeX Error: Unknown option `english' for package `graphics'.


This is because LyX uses the package babel by default. This packages is necessary if you write 
non-English documents or English documents containing text in other languages. Many article classes 
don't accept babel because they are English-only. So to get it work, go to the LyX preferences and 
uncheck there in the language settings the option "Use babel".


But note: it is strongly recommended to re-enable the babel option for all other documents you write 
with LyX.


regards Uwe

Re: Latex error in

[Richard Heck]

On 11/06/2010 12:23 AM, Sandhya wrote:

Hi all

I am using the IJCGA Latex class and Lyx layout files from the LyX 
wiki page on MacOSX. I copied the *.cls and *.layout files to 
~/tex/latex/ and /Library/Application Support/LyX-1.6/layouts/ 
respectively. I also reconfigured LyX. Now when I use the sample LyX 
document, it terminates with an error:


LaTeX Error: Unknown option `english' for package `graphics'.

I am unable to figure out a way of solving this. I have not used Latex 
before, and am stuck here. It would be great if you could give me some 
suggestions in this regard. Thanks in advance.



This layout file is very old, by the way.

I'm not sure I fully understand what's causing this bug, but perhaps 
someone else will. Even the totally trivial file attached throws this 
error. I think the problem is that they do this:


\InputIfFileExists{epsfig.sty}{...}{...}

This seems to have the effect that epsfig.sty tries to process all the 
options that have been passed to the document class, including, in this 
case, "english". That ends up getting passed to graphics.sty somewhere 
down the road, and it chokes. So the problem here is with the class 
file. That is not really the right way to do things.


Richard



t.tex
Description: TeX document

Re: Latex error entering addresses

[Uwe Stöhr]

Am 12.04.2010 13:36, schrieb YURENA MENDOZA:


Lyx tells me an error when I enter the addresses (I have two different
ones) of the authors just below the names of the authors of a paper. I have
these addresses as as "address" in preliminary section . Exactly the message
is as follows: The control sequence at the end of the top line

of your error message was never \def'ed. If you have 


Can you please provide a _small_ LyX file showing the problem?

regards Uwe

Re: Latex error entering addresses

[Paul A. Rubin]

On 4/12/2010 7:36 AM, YURENA MENDOZA wrote:

Hi,
Lyx tells me an error when I enter  the addresses (I have two different
ones) of the authors just below the names of the authors of a paper. I have
these addresses as as "address" in preliminary section . Exactly the message
is as follows: 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."


Thank you



It would be best if you could post a LyX document with just the title 
page (including authors and addresses).  Feel free to change the 
authors' identities if you wish, so long as the test document produces 
the error message.


/Paul

Re: Latex error: Environment subequations undefined

[Uwe Stöhr]

Hwan Lin schrieb:


Attached is a LyX file that cannot go with subequations. Please have a
look and help me.


Why haven't you followed my advice to set the AMS option as I wrote? Doing this, subequations will 
be known by LaTeX as I explained.


Besides this, there were was a mistake: You set the paragraph of the subequation formula to 
left-aligned. Doing this is not allowed when using subequations. (I'll add this info to the Math 
manual.)


I'll attached your fixed file in a private message.

---
Two hints:
You don't need to use TeX code for vertical spaces; LyX supports them via the menu 
Insert->Formatting->vertical space.
You also don't need to use TeX code to insert characters like the copyright sign ©. You can insert 
them via the menu Insert->Special characters->Symbols.


regards Uwe

Re: Latex error: Environment subequations undefined

[Uwe Stöhr]

Hwan Lin schrieb:


From my other papers, on math options, it was set at "use AMS math
package automatically."  These papers worked perfectly with
subequations.

The current paper that bothers  me also has the same math option as
above-mentioned. I don't understand why it can not deal with
subequations.


But I have explained you why this is the case in my email.


Even odd was when I changed the math option from "use AMS math package
automatically" to "use AMS math package", it worked with some
subequations, but it did not for some other subequations.


Can you please provide a _small_ LyX example file where it doesn't work?

regards Uwe

Re: Latex error: Environment subequations undefined

[Hwan Lin]

Hello, Uwe,

Thanks for your kindness.

>From my other papers, on math options, it was set at "use AMS math
package automatically."  These papers worked perfectly with
subequations.

The current paper that bothers  me also has the same math option as
above-mentioned. I don't understand why it can not deal with
subequations.

Even odd was when I changed the math option from "use AMS math package
automatically" to "use AMS math package", it worked with some
subequations, but it did not for some other subequations.

I used Lyx 1.6.5 on Mac OS Snow Leopard.

Can any one help?





On Tue, Jan 19, 2010 at 1:28 PM, Uwe Stöhr  wrote:
> HL2050 schrieb:
>
>> Hello, I used "\begin{subequations}" and "\end{subequations}" to have
>> equations in between. It worked on my two earlier research papers using
>> LyX
>> 1.6 mac os snow leopard. But suddenly the same way stopped working in a
>> new
>> LyX file. I just can't figure it out.
>
> You need to assure that you have set in the LyX document settings the math
> option "Use AMS math package".
> (I guess that in your other research papers you used the option "Use AMS
> math package". This worked because you had other AMS constructs in your file
> that LyX directly supports. In this case the AMS LaTeX-packages were
> automatically loaded. subequations are not yet directly supported, therefore
> the AMS-package are not automatically loaded.)
>
> regards Uwe
>

Re: Latex error: Environment subequations undefined

[Uwe Stöhr]

HL2050 schrieb:


Hello, I used "\begin{subequations}" and "\end{subequations}" to have
equations in between. It worked on my two earlier research papers using LyX
1.6 mac os snow leopard. But suddenly the same way stopped working in a new
LyX file. I just can't figure it out.


You need to assure that you have set in the LyX document settings the 
math option "Use AMS math package".
(I guess that in your other research papers you used the option "Use AMS 
math package". This worked because you had other AMS constructs in your 
file that LyX directly supports. In this case the AMS LaTeX-packages 
were automatically loaded. subequations are not yet directly supported, 
therefore the AMS-package are not automatically loaded.)


regards Uwe

RE: Latex error

[Ingar Pareliussen]

Hi Sølvi,

Sadly these things happen and they are also sadly difficult to
find where it goes wrong, when you have complex documents these
things are more likely to happen. Even if I do not know what have
gone wrong it is likely that an environment is not properly ended.
As an example you might have included one of your child-documents
as a title-environment instead of standard-environment. But there are
many possibilities.

You know your child documents work. Start a new Master-document and
add small pieces from your old master-document to you get the error.
I hope it then will be obvious whats wrong. If not try to make
a minimal sample (with the error) and post it to the list.

I'm going on a holiday now, (to Stavanger by coincidence ;)) but
there are many people that can help you on the list.

Ingar

Re: LaTeX Error: File `prettyref.sty' not found.

[Niko Schwarz]

thanks! i had setup miktex for automatic package installation. but the ftp
server was offline and miktex silently failed.
so, now i changed the ftp server and it worked.

cheers,

niko

2008/12/3 Jürgen Spitzmüller <[EMAIL PROTECTED]>

> Niko Schwarz wrote:
>
> > why does it say that?
>
> because prettyref.sty is not installed on your computer.
>
> > what can i do about it?
>
> Install it :-)
>
> Grab it here:
> http://ctan.org/tex-archive/macros/latex/contrib/prettyref
>
> or try to get it via your package manager (probably the MikTeX package
> manager).
>
> Jürgen
>
> BTW the problem with prettyref, which is used by LyX for formatted cross
> references, was that it had an unclear license, so many TeX distributions
> excluded it. Recently, the license issue was sorted out, so the package will
> most likely be reincluded in the distros.
>
>
>

Re: LaTeX Error: File `prettyref.sty' not found.

[Jürgen Spitzmüller]

Niko Schwarz wrote:

> why does it say that? 

because prettyref.sty is not installed on your computer.

> what can i do about it?

Install it :-)

Grab it here:
http://ctan.org/tex-archive/macros/latex/contrib/prettyref

or try to get it via your package manager (probably the MikTeX package manager).

Jürgen

BTW the problem with prettyref, which is used by LyX for formatted cross 
references, was that it had an unclear license, so many TeX distributions 
excluded it. Recently, the license issue was sorted out, so the package will 
most likely be reincluded in the distros.

Re: LaTeX Error with Curriculum Vitae (European)

[Max Nabble]

Jeby wrote:
> "\usepackage
>{geometry}
> The package inputenc has already been loaded with options:
>   [utf8x]
> There has now been an attempt to load it with options
>   [latin9]
> Adding the global options:
>   utf8x,latin9
> to your \documentclass declaration may fix this.
> Try typingto proceed."

Go to LyX -> Document -> Settings -> Language and set the encoding to utf8x
if it is not already set. That should help. Generally, I recommend always to
use utf8x (or other unicode), other encodings are older and therefore more
limited and why should you limit yourself?

Max
-- 
View this message in context: 
http://n2.nabble.com/LaTeX-Error-with-Curriculum-Vitae-%28European%29-tp1330429p1336567.html
Sent from the LyX - Users mailing list archive at Nabble.com.

Re: LaTeX Error with Curriculum Vitae (European)

[Uwe Stöhr]

Jeby schrieb:


I've a problem with
Curriculum Vitae (European) document class, when I try to export/visualize
it as PDF I obtain this error:

LaTeX Error: Option clash for package inputenc.


Then you seem to use the encoding utf8x for your document in an forbidden way. Without the 
problematic file, I cannot guess what the problem might be.


Besides this, LyX comes in its "examples" folder with the example LyX file "europeCV.lyx". If you 
haven't used this already I recommend to start with this one and fill it with your personal data.


regards Uwe

Re: latex error when using 'presentation (slides)'

[Paul A. Rubin]

Thorsten Kemper wrote:

Dear LyX community,

I have just started using LyX when writing my final thesis, so apologies in
advance if the answer to my question may be straightforward. I have really
tried to find out whether my question has been addressed before in the mail
archive, but couldn't find anything.

Here's the problem: I want to prepare a presentation using the document
classes 'presentation (slides)' or 'presentation (beamer)', but everytime I
click pdflatex an error message pops up telling me "Undefined control
sequence. Missing number, treated as zero."

Can anybody please help me out?



All sorts of errors can cause LaTeX to issue either of those error 
messages (and they are, I think, distinct errors).  Can you post a 
minimal example where you get this?


/Paul

Re: LaTeX error, \prevdepth with Figure

[David Hewitt]

Answering my own question, but I think this could be considered a bug, or at
least picky behavior that causes problems that are really, really hard to
find!

I worked through a backup file that worked piece by piece to find the
problem. It had nothing to do with Figures per se, which made it hard to
find (that's where I figured the problem would be given the LaTeX errors
below).

The trouble was that I had a \thispagestyle{blah} after a chapter title that
was set in the 'addsec' environment (this is KOMA-Script book). The
pagestyle ERT box was on its own line between the title and the next addsec
environment, the real one with the section heading. Changing the environment
in LyX associated with that ERT box to 'standard' fixed the problems.

A bug in behavior? I don't know. I think I might have had the ERT box inline
just before the text for the section heading, then hit enter at some point
to get it on its own line - easier to find when browsing the LyX file. That
such a simple change could bomb the whole compilation is annoying for sure,
but maybe it's just something to be aware of (I am now!).

Thanks


David Hewitt wrote:
> 
> This is a new one for me. I'm hoping this rings a bell with someone. I'm
> on LyX 1.5.3 on WinXP. I've updated my MikTeX packages, refreshed the file
> name database and updated formats, then reconfigured LyX, to no avail.
> 
> The file was producing glorious PDFs this morning. I didn't make anything
> more than minor edits and some hours later LaTeX now throws a fit about
> the Figures when compiling. Nothing changed with the Figures. I've had odd
> LaTeX errors show up with other little tweaks I inserted, but I can't find
> anything for this one.
> 
> LaTeX gets through run #1, BibTeX finishes, and run #2 throws the
> following errors, repeated in this order for each Figure float in the
> document. It also throws a hissy on the Table float, but I think it's all
> related so I'll go with this for now.
> 
> - Improper \prevdepth
> + \end{figure}
>   
> You can refer to \spacefactor only in horizontal mode;
> you can refer to \prevdepth only in vertical mode; and
> neither of these is meaningful inside \write. So
> I'm forgetting what you said and using zero instead.
> 
> - You can't use `\prevdepth' in horizontal mode
> + \end{figure}
>   
> Sorry, but I'm not programmed to handle this case;
> I'll just pretend that you didn't ask for it.
> If you're in the wrong mode, you might be able to
> return to the right one by typing `I}' or `I$' or `I\par'.
> 
> - Missing number, treated as zero
> + \end{figure}
>   
> A number should have been here; I inserted `0'.
> (If you can't figure out why I needed to see a number,
> look up `weird error' in the index to The TeXbook.)
> 
> 
> -Illegal unit of measure (pt inserted)
> +  \end{figure}
>   
> Dimensions can be in units of em, ex, in, pt, pc,
> cm, mm, dd, cc, nd, nc, bp, or sp; but yours is a new one!
> I'll assume that you meant to say pt, for printer's points.
> To recover gracefully from this error, it's best to
> delete the erroneous units; e.g., type `2' to delete
> two letters. (See Chapter 27 of The TeXbook.)
> 
> ...
> 
> The preview source for the first Figure float looks like this:
> 
> % Preview source code for paragraph 23
> 
> \begin{center}
> %
> \begin{figure}
> \begin{centering}
> \includegraphics[width=5in]{Figures/landingsCBSAC}
> \par\end{centering}
> 
> \caption[Commercial landings of blue crab in Chesapeake Bay,
> 1945-2006]{\label{Fig:landingshistory}History of commercial landings of
> blue
> crab in Chesapeake Bay, 1945-2006 (data from
> \citealt{cbsac2007advreport}).}
> 
> 
> 
> \end{figure}
> 
> \par\end{center}
> 
> 
> Thanks for any help,
> Dave
> 


-
David Hewitt
Virginia Institute of Marine Science
http://www.vims.edu/fish/students/dhewitt/
-- 
View this message in context: 
http://www.nabble.com/LaTeX-error%2C-%5Cprevdepth-with-Figure-tp15705637p15716599.html
Sent from the LyX - Users mailing list archive at Nabble.com.

Re: latex error with use of code listing

[cedricg]

Hello,

I've looked around and learned that there is an incompatibility between  
the 'listings' and the 'babel' package.
A sort of fix to avoid the LAtex error message I was speaking in my  
previous message is to load the 'listings' package before the 'babel' one,  
like reported here :

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373605#42

But, I've found that for me the fix is the exact opposit : loading the  
'babel'  then  after the 'listings' package fix the problem. Well??...


So, the better solution I've found with Lyx for now is to desactivate the  
'babel' package!


cedric.

On Thu, 14 Feb 2008 02:57:31 +0100, <[EMAIL PROTECTED]> wrote:


Hello,

I'm using the 'code listing' box and found some random unpredictable  
error message while generating the document to DVI, PS or PDF.

The Latex messages are some of the following :
Incomplete \iffalse: all text was ignored after line 1000
Forbidden control sequence found while scanning text of \write.

I've looked at the Latex inline viewer but didn't found anything  
suspect. The problem is anoying because when this happen you dont know  
which code listing box is wrong and the culprit box is not always the  
latest edited and it end with using verbatim,...


I'm using Lyx 1.5.3 on ubuntu 7.10, Lyx is version 3.141592.

cedricg.




--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Re: Latex error "Missing \endcsname inserted"

[Falk Sticken]

Solved. I used 'Paragraph' for paragraphs, but this style is only for
paragraph titles.
bye,
Falk Sticken

Re: LaTeX Error: Command \thm already defined.

[lyxCompilerError]

Just got it! Thanks for your help!

I was using ams* files, so I went into those files and deleted the offending
theorem definitions. It now compiles just fine. (-:

Thanks again!
-- 
View this message in context: 
http://www.nabble.com/LaTeX-Error%3A-Command-%5Cthm-already-defined.-tf4950056.html#a14177368
Sent from the LyX - Users mailing list archive at Nabble.com.

Re: LaTeX Error: Command \thm already defined.

[Paul A. Rubin]

lyxCompilerError wrote:
How do I force LyX 1.5.2 to redefining the theorem environment? 


I'm required to use stacs.cls as my document class (and am not allowed to
modify this file). Stacs.cls defines the theorem environment, and this
conflicts with LyX wanting to automatically add (another) theorem
environment. So, how do I force LyX to stop adding this redundant theorem
environment?

Summary:
* LyX always inserts this command into the TEX file.
\newtheorem{thm}{Theorem}[section]

* I need to stop LyX from doing this.


What layout file are you using with stacs.cls?  Did you create one 
yourself?  In particular, are you loading AMS stuff (either 
intentionally or because your layout file is a derivative of an AMS 
layout file)?  LyX doesn't add the newtheorem definition willy-nilly; 
there must be something either in your layout file, your document 
options or your preamble that is causing it.


/Paul

Re: LaTeX Error: no \title given

[Jean-Marc Lasgouttes]

"Emanuele Osimo" <[EMAIL PROTECTED]> writes:

> Hello,
> I'm a mac Lyx user with no experience.
> Every time I write a document and then try to export it into pdf, a
> window appears that states "LaTeX Error: no \title given".
> How can I solve this problem?
> Attached there is an example

It seems that you have added a Data (Date?) environment in your
document. Title, Date and Author are considered as part of a title and
LaTeX complains that this title is not complete.

JMarc

Re: LaTeX Error: no \title given

[G. Milde]

On 26.11.07, Emanuele Osimo wrote:
> I'm a mac Lyx user with no experience.
> Every time I write a document and then try to export it into pdf, a
> window appears that states "LaTeX Error: no \title given".
> How can I solve this problem?
> Attached there is an example

It looks like you have in your document a paragraph in a style that creates
a title page (or title block). You can try

* to add a title, or 
* find out which paragraph needs to be removed or get a different style if
  you do not want a title.

It would be helpfull to have a minimal lyx file that exhibits this
behaviour as attachment.

Guenter

Re: LaTeX Error: Too many unprocessed floats.

[Bob Lounsbury]

Thanks for the info. I randomly figured it because I put some page
breaks in between the figures since they were each a page.

Thanks again,
Bob

On 6/25/07, Les Denham <[EMAIL PROTECTED]> wrote:

On Monday 25 June 2007 14:09, Bob Lounsbury wrote:
> I'm trying to complete my thesis in the next few weeks. I just
> inserted 20 floating/sideways figures, which is one figure per page.
> However, when I do this I get the error in the subject line along with
> a bunch of other errors.
>
>
> Is there something I can adjust? Is there a limit to the number of
> figures you can have in a document? This seems odd to me.

Latex has a limit of 18 on the number of pending floats.  To get around this,
insert the latex command:

\clearpage

at intervals through your document where a new page makes sense to force the
display of pending floats.

See http://tug.org/TeXnik/mainFAQ.cgi?file=floats/floats#unprocessed


--
Les

~~
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

Re: LaTeX Error: Too many unprocessed floats.

[Les Denham]

On Monday 25 June 2007 14:09, Bob Lounsbury wrote:
> I'm trying to complete my thesis in the next few weeks. I just
> inserted 20 floating/sideways figures, which is one figure per page.
> However, when I do this I get the error in the subject line along with
> a bunch of other errors.
>
>
> Is there something I can adjust? Is there a limit to the number of
> figures you can have in a document? This seems odd to me.

Latex has a limit of 18 on the number of pending floats.  To get around this, 
insert the latex command:

\clearpage

at intervals through your document where a new page makes sense to force the 
display of pending floats.

See http://tug.org/TeXnik/mainFAQ.cgi?file=floats/floats#unprocessed


-- 
Les

~~
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

Re: Latex error on graphics insert (LyX 1.3.7)

[Bennett Helm]

On Jan 28, 2006, at 2:04 PM, Georg Baum wrote:


Am Samstag, 28. Januar 2006 19:47 schrieb Marc D.:

There is now no preferences file in the Library->Application Support-

LyX

directory. However, LyX.app/Contents/Resources/lyx
in the dmg file I just downloaded has the following:

\format "pdf" "pdf" "PDF (pdflatex)" ""
\format "pdf2" "pdf" "PDF (ps to pdf)" ""

This also appears in preferences where I've installed LyX.app.

So may I suggest that if this is so wrong that the distribution
itself needs to be fixed, since I can guarantee that I had
nothing to do with these settings.


OK finally we have found the problem. You are absolutely right, this
should not be like that.
Bennett, could you please correct the installer?
Maybe this is also the reason for
http://bugzilla.lyx.org/show_bug.cgi?id=2127 ?


Yes ... it appears to be my mistake somewhere along the line. But  
those two lines have been in the LyX/Mac default preferences for a  
while and haven't caused a problem before. Moreover, deleting those  
lines from within the LyX.app bundle -- i.e., the default LyX/Mac  
preferences -- does not affect bug 2127 substantially. (I'll post new  
comments on bugzilla so we have them there: .)


Bennett


--
Bennett Helm
Department of Philosophy
Franklin & Marshall College
P. O. Box 3003
Lancaster, PA 17604-3003
Voice: (717) 291-4392
Fax: (717) 291-4369

Re: Latex error on graphics insert (LyX 1.3.7)

[Georg Baum]

Am Samstag, 28. Januar 2006 19:43 schrieb Herbert Voss:
> ok ok, my question was why it is _wrong_! It is wrong
> in a logical way, but it should work without LyX internal
> errors, right?

Yes. But it might have lead Marc to think that he is converting via 
pdflatex when he actually used ps2pdf. I think there are no more 
misunderstandings now :-)


Georg

Re: Latex error on graphics insert (LyX 1.3.7)

[Georg Baum]

Am Samstag, 28. Januar 2006 19:47 schrieb Marc D.:
> There is now no preferences file in the Library->Application Support- 
>  >LyX
> directory. However, LyX.app/Contents/Resources/lyx
> in the dmg file I just downloaded has the following:
> 
> \format "pdf" "pdf" "PDF (pdflatex)" ""
> \format "pdf2" "pdf" "PDF (ps to pdf)" ""
> 
> This also appears in preferences where I've installed LyX.app.
> 
> So may I suggest that if this is so wrong that the distribution
> itself needs to be fixed, since I can guarantee that I had
> nothing to do with these settings.

OK finally we have found the problem. You are absolutely right, this 
should not be like that.
Bennett, could you please correct the installer?
Maybe this is also the reason for 
http://bugzilla.lyx.org/show_bug.cgi?id=2127 ?


Georg

Re: Latex error on graphics insert (LyX 1.3.7)

[Marc D.]

On 28 Jan 06, at 08:33, Georg Baum wrote:


Am Samstag, 28. Januar 2006 17:14 schrieb Marc D.:
The defaults do not seem to work under MacOSX, in that they  
specify xpdf

rather than "open" to view files. This is probably fine if the user
is using XWindows subsystem to run LyX, but not if the user wants
to run LyX under the MacOS GUI. The only changes I
made to the defaults were to lyxrc to change xpdf to open.
(yes, I could have just specified those two lines in lyxrc.
Instead I elected to just copy lyxrc.default and change those
2 lines. It should have resulted in the same thing.)


I did not talk about the viewer settings. Of course you can set  
them to

"open", and it should work. I meant these two lines (found by Paul):

\format "pdf" "pdf" "PDF (pdflatex)" ""
\format "pdf2" "pdf" "PDF (ps to pdf)" ""

These are wrong! Read Pauls explanation if it is not clear why.


Georg



OK, I have completed a full reinstall (I'm getting VERY good at this!)

LyX 1.3.7 on MacOSX 10.4.4.
Downloaded from http://wiki.lyx.org/LyX/LyXOnMac?from=LyX.Mac

LaTeX install from MacTeX.dmg downloaded from Tug was not touched.

OK. I have deleted LyX, deleted all the preferences
Library->Application Support->LyX (actually deleted the whole directory)
I then reinstalled LyX from a fresh download.

Opened my a1.lyx that worked before...

LyX does a whole bunch of stuff on the console, creating the
Library/Application Support/LyX directory and doing some self
configuration.

When I try View -> PDF (ps to pdf) it doesn't display the images.

Under Layout->Document->Packages, Postscript driver was set to dvips.
This was AFTER resetting it in the document previously, as documented
previous in this thread.

So I manually reset "dvips" back to default, apply...

View -> PDF (ps to pdf) now works fine and display my images.

There is now no preferences file in the Library->Application Support- 
>LyX

directory. However, LyX.app/Contents/Resources/lyx
in the dmg file I just downloaded has the following:

\format "pdf" "pdf" "PDF (pdflatex)" ""
\format "pdf2" "pdf" "PDF (ps to pdf)" ""

This also appears in preferences where I've installed LyX.app.

So may I suggest that if this is so wrong that the distribution
itself needs to be fixed, since I can guarantee that I had
nothing to do with these settings.

regards,
Marc

Re: Latex error on graphics insert (LyX 1.3.7)

[Herbert Voss]

Georg Baum wrote:

Am Samstag, 28. Januar 2006 18:07 schrieb Herbert Voss:


Georg Baum wrote:


\format "pdf" "pdf" "PDF (pdflatex)" ""
\format "pdf2" "pdf" "PDF (ps to pdf)" ""

These are wrong! Read Pauls explanation if it is not clear why.


??? Why are these lines _wrong_?



Read it in Pauls mail. Short version: They are wrong because the comments 
("pdflatex" and "ps to pdf") don't match the converters. The defaults are


ok ok, my question was why it is _wrong_! It is wrong
in a logical way, but it should work without LyX internal
errors, right?

Herbert



\Format pdf   pdf  "PDF (ps2pdf)"   P
\Format pdf2  pdf  "PDF (pdflatex)" F
\Format pdf3  pdf  "PDF (dvipdfm)"  m
\converter pspdf  "ps2pdf13 $$i" ""
\converter latex pdf2 "pdflatex $$i" "latex"
\converter dvi   pdf3 "dvipdfm $$i" ""

Re: Latex error on graphics insert (LyX 1.3.7)

[Georg Baum]

Am Samstag, 28. Januar 2006 18:07 schrieb Herbert Voss:
> Georg Baum wrote:
> > \format "pdf" "pdf" "PDF (pdflatex)" ""
> > \format "pdf2" "pdf" "PDF (ps to pdf)" ""
> > 
> > These are wrong! Read Pauls explanation if it is not clear why.
> 
> ??? Why are these lines _wrong_?

Read it in Pauls mail. Short version: They are wrong because the comments 
("pdflatex" and "ps to pdf") don't match the converters. The defaults are

\Format pdf   pdf  "PDF (ps2pdf)"   P
\Format pdf2  pdf  "PDF (pdflatex)" F
\Format pdf3  pdf  "PDF (dvipdfm)"  m
\converter pspdf  "ps2pdf13 $$i" ""
\converter latex pdf2 "pdflatex $$i" "latex"
\converter dvi   pdf3 "dvipdfm $$i" ""


Georg