RE: LyX 2.4 & MikTeX problem

[Kees Zeelenberg]

> Van: lyx-users  Namens Richard Kimberly Heck
> Verzonden: zondag 2 juni 2024 02:14
> Aan: lyx-users@lists.lyx.org
> Onderwerp: Re: LyX 2.4 & MikTeX problem
> On 6/1/24 15:34, Paul Rubin wrote:
> On 6/1/24 15:13, Bernt Lie via lyx-users wrote:
> ...
> It's because of this sort of problem, which seems to arise constantly, that 
> we stopped recommending MiKTeX.
> Riki

It seems to me LyX should not favor one distribution over another if  there is 
only cursory and occasional information about using them with LyX. I do not 
wish to complain in a similar fashion about TeXLive, but one may easily find 
problems with TeXLive on Windows; see e.g. 
https://tug.org/pipermail/tex-live/2024-May/thread.html. Twice in one month! So 
perhaps it is best to maintain a neutral view on LyX's website.

Kees


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

RE: color names make trouble

[Kees Zeelenberg]

On Sun, Apr 14, 2024 at 8:33 AM Andreas Plihal via lyx-users < 
 lyx-users@lists.lyx.org> wrote:

 

I have largely isolated the error (I am attaching the associated file). Now I'm 
faced with the fact that the error is apparently caused by the color names 
(RubineRed, Gray etc.) that I've been using without any problems for over a 
year! What is suddenly going on in the LYX/LATEX world?

 

Andreas

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

 

Andreas,

 

I'm not sure what's happening from your side, but if I disable the fonts you 
have and change "Gray" to "gray", then the line renders for me.

 

Thanks,

Joel 

 

In xcolor, Gray (with first letter in uppercase) is a color model, not a color. 
This can be changed by the option “svgnames” or by the option “dvipsnames”. 
Since here xolor is called by tikz, it is best to give this as an option to the 
documentclass. This worked for me, with pdflatex.

 

Kees

 

 

 

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

RE: Problematik: fehlender Eintrag \begin{document} stört output der Datei als Pdf

[Kees Zeelenberg]

With several letter classes this error message may indicate that a required 
field, e.g. the sender's name, is missing or that fields are in the wrong 
order. Another error message in such cases is "No line to end here". Some 
letter classes are very particular about these required fields.
Probably the best way is to start from a template. In LyX, you may do this from 
File / New from template ... / Letters / Koma Script Letter. The template with 
the default values compiles successfully to pdf, with LyX-2.4.0-RC3 under 
Windows.
Also, you might want to take a look at 
https://wiki.lyx.org/Examples/KomaLetter2, where you will find several LyX 
templates for the Koma letter class. 

Kees

> -Oorspronkelijk bericht-
> Van: lyx-users  Namens kauf_dich--- via lyx-
> users
> Verzonden: zondag 18 februari 2024 14:07
> Aan: lyx-users@lists.lyx.org
> Onderwerp: Problematik: fehlender Eintrag \begin{document} stört output der
> Datei als Pdf
> 
> Hallo,
> 
> ich nutze LyX seit über 10 Jahren und schreibe damit meine bürokratischen 
> Briefe.
> Es ist sehr hilfreich für nicht Mathematiker/ Physiker/ Atomtechniker/
> Programmierende/ Besserwisser ein Programm wie LyX zu nutzen. Ich nutze das
> veraltete DINBrief und versuche es neuerdings mit KOMA letter. Es gab und gibt
> immer wieder Ausgabefehler - eines Fehlers namens "! LaTeX Error: Missing
> \begin{document}.". Dadurch kann ich meine Briefe nicht/ nicht mehr als pdf
> outputten.
> 
> Ich habe schon sehr sehr sehr viele Forenbeiträge gelesen. Keiner behandelt
> explicit das Thema LyX und den fehlenden "! LaTeX Error:
> Missing \begin{document}." Part in DIN Brief und Komaletter. Es gibt auch
> praktisch keine Anleitungen (englische, deutsche, französische Foren 
> durchsucht),
> wie diese Problematik in/ mit LyX lösbar ist.
> 
> So "traue" ich mich in die Mailinglist zu schreiben, da alles andere keinen 
> Sinn
> mehr ergibt.
> 
> Schön wäre es eine konkrete Anwort, oder Nachfragen zu erhalten ohne das
> elitäre Gequatsche das Ihr alle kennt, wenn ein Noob eine Frage im Forum 
> stellt
> und alle erstmal die Frage ignorieren und ihre ungefragten Weltsichten
> propagieren müssen.
> 
> genutztes System:
> Linux Mint 20.3
> LyX 2.3.6.1
> 
> Toll wäre, wenn LyX einen da an die Hand nehmen würde und eine einfache
> Ersetzung/ Einfügung der nötigen Programmierung anbieten würde.
> 
> Vielen Dank für jegliche Hilfe
> Ole
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users

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

RE: refstyle and amsmath

[Kees Zeelenberg]

Van: lyx-users  Namens Jürgen Spitzmüller
Verzonden: donderdag 1 februari 2024 10:22



Am Do., 1. Feb. 2024 um 08:20 Uhr schrieb Jürgen Spitzmüller :

FYI version 0.6. of refstyle, now on CTAN and soon distributed via the
package managers, will contain the fix of this issue.

 

The new version still does not completely work. I have reported it. Here is the 
needed fix of the fix:

…

Let's hope Danie takes care of this soon, as well.

 

He has, and refstyle now works OK, also in more complicated documents, with 
export both to Pdf-pdflatex and to Pdf-luatex, and also with the autonum 
package.

Thanks!

 

Kees

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

refstyle and amsmath

[Kees Zeelenberg]

Some time ago there was a discussion on the list about refstyle in
combination with amsmath, leading to error messages from refstyle. It
appears refstyle is now loaded after amsmath, but this now leads to messages
like "LaTeX Warning: Reference `ab' on page 1 undefined on input line 39"
from the enclosed LyX file 'testref.lyx'. It seems that this is related to
the LaTeX line "\AtBeginDocument{\providecommand\eqref[1]{\ref{eq:#1}}}",
which is added by LyX in 'testref.tex'. This line does not have any effect,
so that e.g. \eqref{ab}  is interpreted as \ref{ab}  instead of \ref{eq:ab}.
Replacing this line with
\AtBeginDocument{\DeclareRobustCommand{\eqref}[1]{\textup{\tagform@{\ref{eq:
#1} (as in amsmath), the LaTeX file 'testref_robust.tex' compiles
without problems.

 

Kees

 



testref.lyx
Description: application/lyx


testref.tex
Description: Binary data


testref.pdf
Description: Adobe PDF document


testref_robust.pdf
Description: Adobe PDF document


testref_robust.tex
Description: Binary data
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

RE: Adding accented character in JabRef

[Kees Zeelenberg]

Herbert Voss wrote:
> However, you should be able to insert directly ã

Isn't this only possible with either a keyboard that has the symbol directly or 
a keyboard with dead keys?

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

RE: Trouble with quote (") character on LyX 2.3.6.2 (2021-01-07)

[Kees Zeelenberg (kzStats) via lyx-users]

> -Oorspronkelijk bericht-
> Van: lyx-users  Namens Kornel Benko via lyx-
> users
> Verzonden: woensdag 6 april 2022 14:23
> Aan: lyx-users@lists.lyx.org
> CC: Kornel Benko 
> Onderwerp: Re: Trouble with quote (") character on LyX 2.3.6.2 (2021-01-07)
> 
> Am Wed, 6 Apr 2022 13:56:58 +0200
> schrieb "Kees Zeelenberg \(kzStats\)" :
> 
> > Now with the attachment.
> >
> > > -Oorspronkelijk bericht-
> > > Van: Kees Zeelenberg (kzStats) 
> > > Verzonden: woensdag 6 april 2022 13:56
> > > Aan: 'lyx-users@lists.lyx.org' 
> > > CC: 'Kornel Benko' 
> > > Onderwerp: RE: Trouble with quote (") character on LyX 2.3.6.2
> > > (2021-01-07)
> > >
> > > > -Oorspronkelijk bericht-
> > > > Van: lyx-users  Namens Kornel
> > > > Benko via lyx- users
> > > > Verzonden: woensdag 6 april 2022 12:54
> > > > Aan: lyx-users@lists.lyx.org
> > > > CC: Kornel Benko 
> > > > Onderwerp: Re: Trouble with quote (") character on LyX 2.3.6.2
> > > > (2021-01-07)
> > > >
> > > > Am Wed, 6 Apr 2022 12:24:40 +0200
> > > > schrieb "Kees Zeelenberg \(kzStats\) via lyx-users"  us...@lists.lyx.org>:
> > > >
> > > > > > > > On MS-Windows 11 with LyX 2.3.6.1 and the US international
> > > > > > > > keyboard search and replace " works fine. I haven't tested the
> export.
> > > > > > > >
> > > > > > > > Best,
> > > > > > > >
> > > > > > > > Kees
> > > > > > > >
> > > > > > >
> > > > > > > Unfortunately, this might be just due to the international
> > > > > > > keyboard not being fully supported in LyX
> > > > (https://www.lyx.org/trac/ticket/10377).
> > > > > > > (You might want to fix the quotes in your documents...)
> > > > > > >
> > > > > > > Best,
> > > > > > > Daniel
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > It should not matter, on each keyboard there is '"'.
> > > > > > (If you insert in a German document e.g. 'eine "Klammer"', you
> > > > > > get 'eine „Klammer“' in lyx)
> > > > > >
> > > > > > Kornel
> > > > > >
> > > > > > --
> > > > >
> > > > > Should this ("Klammer" -> „Klammer“) also work with a US
> > > > > International keyboard? At least, I could not get it work, not
> > > > > with language German, Dutch,
> > > > English.
> > > > >
> > > > > Kees
> > > > >
> > > > >
> > > >
> > > > I am using US International keyboard. And here it works.
> > > > The lyx code looks like this:
> > > >
> > > > \begin_layout Standard
> > > > eine
> > > > \begin_inset Quotes gld
> > > > \end_inset
> > > >
> > > > Klammer
> > > > \begin_inset Quotes grd
> > > > \end_inset
> > > >
> > > >
> > > > \end_layout
> > > >
> > > > As you can see, there is 'gld' and 'grd'. In order to match are
> > > > both converted to '"' at search time. But this is done for advanced 
> > > > search
> only.
> > > >
> > > > Kornel
> > > >
> > > Using "q"  and ``a''  I get
> > >
> > > \begin_layout Standard
> > > eine "q"
> > > \end_layout
> > >
> > > \begin_layout Standard
> > > und
> > > \end_layout
> > >
> > > \begin_layout Standard
> > > eine ``a''
> > > \end_layout
> > >
> > > See the attachment for the complete lyx file
> 
> Your mwe is created with lyx2.3. I have changed the handling for lyx2.4.
> 
>   Kornel
> 

Thanks for clearing this up!

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

RE: Trouble with quote (") character on LyX 2.3.6.2 (2021-01-07)

[Kees Zeelenberg (kzStats) via lyx-users]

> -Oorspronkelijk bericht-
> Van: lyx-users  Namens Kornel Benko via lyx-
> users
> Verzonden: woensdag 6 april 2022 12:54
> Aan: lyx-users@lists.lyx.org
> CC: Kornel Benko 
> Onderwerp: Re: Trouble with quote (") character on LyX 2.3.6.2 (2021-01-07)
> 
> Am Wed, 6 Apr 2022 12:24:40 +0200
> schrieb "Kees Zeelenberg \(kzStats\) via lyx-users" :
> 
> > > > > On MS-Windows 11 with LyX 2.3.6.1 and the US international
> > > > > keyboard search and replace " works fine. I haven't tested the export.
> > > > >
> > > > > Best,
> > > > >
> > > > > Kees
> > > > >
> > > >
> > > > Unfortunately, this might be just due to the international
> > > > keyboard not being fully supported in LyX
> (https://www.lyx.org/trac/ticket/10377).
> > > > (You might want to fix the quotes in your documents...)
> > > >
> > > > Best,
> > > > Daniel
> > > >
> > > >
> > >
> > > It should not matter, on each keyboard there is '"'.
> > > (If you insert in a German document e.g. 'eine "Klammer"', you get
> > > 'eine „Klammer“' in lyx)
> > >
> > >   Kornel
> > >
> > > --
> >
> > Should this ("Klammer" -> „Klammer“) also work with a US International
> > keyboard? At least, I could not get it work, not with language German, 
> > Dutch,
> English.
> >
> > Kees
> >
> >
> 
> I am using US International keyboard. And here it works.
> The lyx code looks like this:
> 
> \begin_layout Standard
> eine
> \begin_inset Quotes gld
> \end_inset
> 
> Klammer
> \begin_inset Quotes grd
> \end_inset
> 
> 
> \end_layout
> 
> As you can see, there is 'gld' and 'grd'. In order to match are both 
> converted to
> '"' at search time. But this is done for advanced search only.
> 
>   Kornel
> 
Using "q"  and ``a''  I get

\begin_layout Standard
eine "q"
\end_layout

\begin_layout Standard
und
\end_layout

\begin_layout Standard
eine ``a''
\end_layout

See the attachment for the complete lyx file

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

RE: Trouble with quote (") character on LyX 2.3.6.2 (2021-01-07)

[Kees Zeelenberg (kzStats) via lyx-users]

Now with the attachment.

> -Oorspronkelijk bericht-
> Van: Kees Zeelenberg (kzStats) 
> Verzonden: woensdag 6 april 2022 13:56
> Aan: 'lyx-users@lists.lyx.org' 
> CC: 'Kornel Benko' 
> Onderwerp: RE: Trouble with quote (") character on LyX 2.3.6.2 (2021-01-07)
> 
> > -Oorspronkelijk bericht-
> > Van: lyx-users  Namens Kornel Benko
> > via lyx- users
> > Verzonden: woensdag 6 april 2022 12:54
> > Aan: lyx-users@lists.lyx.org
> > CC: Kornel Benko 
> > Onderwerp: Re: Trouble with quote (") character on LyX 2.3.6.2
> > (2021-01-07)
> >
> > Am Wed, 6 Apr 2022 12:24:40 +0200
> > schrieb "Kees Zeelenberg \(kzStats\) via lyx-users" 
> > :
> >
> > > > > > On MS-Windows 11 with LyX 2.3.6.1 and the US international
> > > > > > keyboard search and replace " works fine. I haven't tested the 
> > > > > > export.
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > Kees
> > > > > >
> > > > >
> > > > > Unfortunately, this might be just due to the international
> > > > > keyboard not being fully supported in LyX
> > (https://www.lyx.org/trac/ticket/10377).
> > > > > (You might want to fix the quotes in your documents...)
> > > > >
> > > > > Best,
> > > > > Daniel
> > > > >
> > > > >
> > > >
> > > > It should not matter, on each keyboard there is '"'.
> > > > (If you insert in a German document e.g. 'eine "Klammer"', you get
> > > > 'eine „Klammer“' in lyx)
> > > >
> > > > Kornel
> > > >
> > > > --
> > >
> > > Should this ("Klammer" -> „Klammer“) also work with a US
> > > International keyboard? At least, I could not get it work, not with
> > > language German, Dutch,
> > English.
> > >
> > > Kees
> > >
> > >
> >
> > I am using US International keyboard. And here it works.
> > The lyx code looks like this:
> >
> > \begin_layout Standard
> > eine
> > \begin_inset Quotes gld
> > \end_inset
> >
> > Klammer
> > \begin_inset Quotes grd
> > \end_inset
> >
> >
> > \end_layout
> >
> > As you can see, there is 'gld' and 'grd'. In order to match are both
> > converted to '"' at search time. But this is done for advanced search only.
> >
> > Kornel
> >
> Using "q"  and ``a''  I get
> 
> \begin_layout Standard
> eine "q"
> \end_layout
> 
> \begin_layout Standard
> und
> \end_layout
> 
> \begin_layout Standard
> eine ``a''
> \end_layout
> 
> See the attachment for the complete lyx file


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

RE: Trouble with quote (") character on LyX 2.3.6.2 (2021-01-07)

[Kees Zeelenberg (kzStats) via lyx-users]

> > > On MS-Windows 11 with LyX 2.3.6.1 and the US international keyboard
> > > search and replace " works fine. I haven't tested the export.
> > >
> > > Best,
> > >
> > > Kees
> > >
> >
> > Unfortunately, this might be just due to the international keyboard
> > not being fully supported in LyX (https://www.lyx.org/trac/ticket/10377).
> > (You might want to fix the quotes in your documents...)
> >
> > Best,
> > Daniel
> >
> >
> 
> It should not matter, on each keyboard there is '"'.
> (If you insert in a German document e.g. 'eine "Klammer"', you get  'eine
> „Klammer“' in lyx)
> 
>   Kornel
> 
> --

Should this ("Klammer" -> „Klammer“) also work with a US International 
keyboard? At least, I could not get it work, not with language German, Dutch, 
English.

Kees


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

RE: RE: Trouble with quote (") character on LyX 2.3.6.2 (2021-01-07)

[Kees Zeelenberg (kzStats) via lyx-users]

> On 2022-04-05 18:37, Kees Zeelenberg (kzStats) via lyx-users wrote:
> > On MS-Windows 11 with LyX 2.3.6.1 and the US international keyboard
search
> and replace " works fine.
> > I haven't tested the export.
> >
> 
> Unfortunately, this might be just due to the international keyboard not
being
> fully supported in LyX (https://www.lyx.org/trac/ticket/10377).
> (You might want to fix the quotes in your documents...)

Yes, I forgot! Indeed I now remember why I still use the old-fashioned ``
and ''

Kees

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

RE: Trouble with quote (") character on LyX 2.3.6.2 (2021-01-07)

[Kees Zeelenberg (kzStats) via lyx-users]

> 
> a) While I can write it in LyX, I cannot search for it. I can put it into the 
> search
> box, but the LyX editor will not find quote marks in the document. (I know 
> that
> under Document" -> Settings I can choose various types of quote signs; I left 
> it
> to the standard, which (in German) means typographic quote marks.
> 
> 
> Andreas
> --
On MS-Windows 11 with LyX 2.3.6.1 and the US international keyboard search and 
replace " works fine.
I haven't tested the export.

Best,

Kees

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

RE: Installing LyX 2.3.6.1 on Linux MInt 20.3 with TeXLive 2021

[Kees Zeelenberg (kzStats) via lyx-users]

> -Oorspronkelijk bericht-
> Van: lyx-users  Namens Graeme via
lyx-users
> Verzonden: vrijdag 4 maart 2022 00:00
> Aan: lyx-users List 
> Onderwerp: Installing LyX 2.3.6.1 on Linux MInt 20.3 with TeXLive 2021
> 
> c) Is there a way to install LyX 2.3.6.1 without installing the TeXLive
> 2019 dependencies? (I'd prefer not to have to compile LyX 2.3.6.1 from
> source.)

You could follow the advice at https://tug.org/texlive/debian.html#vanilla
(Mint is a derivative of Ubuntu, which itself is a derivative of Debian),
and build a dummy package for texlive (2019), which tricks the Mint Package
Manager and the LyX installer into believing texlive is installed.
I think you can also use 2021 instead of 2019 for this dummy package if
texlive-2021 is not installed from a deb-package.

Kees


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

RE: Biblatex missing characters in Libertinus

[Kees Zeelenberg (kzStats)]

> -Oorspronkelijk bericht-
> Van: lyx-users  Namens Wolfgang Engelmann
> Verzonden: vrijdag 3 december 2021 11:13
> Aan: lyx-users@lists.lyx.org
> Onderwerp: Re: Biblatex missing characters in Libertinus
> 
> Ups,
> here the log file, the first one was empty.
> Wolfgang

The latest stix2fonts seem to be called STIXTwootf, so with "Two" instead 
of "2", and have suffixes (Regular, etc).  With 
\setmathfont{STIXTwoMath-Regular.otf} in the preamble, the LyX-file compiles 
well and shows the correct pdf output, whereas with \setmathfont{STIX2Math.otf} 
it fails.

Kees


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

Re: LyX 2.3.5.2 Relesed

[Kees Zeelenberg]

> Op 2 aug. 2020 om 17:59 heeft Paul A. Rubin  het 
> volgende geschreven:
> 
> On 8/2/20 1:31 AM, Liviu Andronic wrote:
>>> On 6/30/20, Richard Kimberly Heck  wrote:
>>> Public release of LyX version 2.3.5.2
>>> =
>>> 
>> I've uploaded Ubuntu packages to the PPA:
>> https://launchpad.net/~lyx-devel/+archive/ubuntu/release
>> 
>> The packages are now built with Qt5, so please report back if you
>> encounter any issues.
>> 
>> Regards,
>> Liviu
>> 
>> ...
>> 
>>> Thanks Liviu! The update went through this morning, and the new version is 
>>> working fine on my system (Mint 19.3). As always, we Mint/Ubuntu users 
>>> appreciate your efforts.
> 
> Paul
> 
> -- 
> 

Seconded. Much appreciated. 

Kees

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

Re: Can't upgrade LyX on Focal Fossa

[Kees Zeelenberg]

Liviu Andronic schreef op wo 22-07-2020 om 10:27 [-0700]:
> 
> > It seems Qt4 is no longer supplied on Focal.
> > 
> Yes, for Ubuntu Focal, Qt4 was removed from the Ubuntu repositories.
> To install LyX, you will also need to add the ppa:rock-core/qt4 PPA
> to
> your sources (https://launchpad.net/~rock-core/+archive/ubuntu/qt4).
> 
> 
> I've now added a note on this on the PPA.
> 
> Regards,
> Liviu

But is it not possible to compile with Qt5? The default version in the
repository (2.3.4.2) is already based on Qt5.

Best,

Kees

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

Re: Can't upgrade LyX on Focal Fossa

[Kees Zeelenberg]

Liviu Andronic schreef op wo 22-07-2020 om 08:34 [-0700]:
> 
> 
> I've now uploaded a new build dropping the libboost-signals-dev
> dependency, and it looks like it worked. Can someone with access to
> Focal test if they can now install LyX from the PPA?
> 
> Thank you,
> Liviu

Thanks for compiling. Synaptic (on Linux Mint 20) aborts installing
LyX from the PPA with the messages: 
Vereisten: libqtcore4 (>=4:4.8.0) but it is not installable
Vereisten: libqtgui4 (>=4:4.8.0) but it is not installable
Vereisten: libqt4-svg  but it is not installable

It seems Qt4 is no longer supplied on Focal.

Best,
Kees

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

Re: no accents with dead keys

[Kees Zeelenberg]

Op 12-07-2020 om 22:02 schreef jorge hernando:

Hallo
  I have one PC with english keyboard (US international with dead 
keys) and another one with spanish keyboard (Castilian Spanish with 
dead keys) both with fedora 32 (since a couple of days) and lyx 
2.3.5.2. In both PC have the same problem: the accents work perfectly 
(e.g. á is " 'a ") when in a terminal, opening nedit, ooffice, etc. 
but in lyx not only it doesn't work, the dead key is really dead: if I 
type ' in lyx it doesn't type anything but, there is at least one 
exception, when saving a file, I can type a name with accents (?)


Using the "US International keyboard with dead keys", I can create 
accented letters in the usual way, e.g. "e gives ë, etc. This works both 
in Linux Mint 20 with LyX 2.3.4.2 and Windows 10 with LyX 2.3.5.2. The 
system language is Dutch (nl_nl) in both cases.


I can get the ç (c with cedilla), with Alt R + ,

Kees

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

Re: Can't upgrade LyX on Focal Fossa

[Kees Zeelenberg]

Op 12-07-2020 om 00:06 schreef Paul A. Rubin:

...

Is anybody else having problems upgrading to 2.3.5.1 for Focal via the 
PPA?


In the right-hand corner of the ppa-page 
(https://launchpad.net/~lyx-devel/+archive/ubuntu/release) you see that 
the amd64 version, which you probably want to install, failed to build. 
So there is no update, and Synaptic etc correctly see this.

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

Re: FW: Problems using Bibtex with lyx.

[Kees Zeelenberg]

Op 12-06-2020 om 12:44 schreef Mike Reeks:

 Still no reference list.


Well, this is what I get, with LyX-2.3.4.2 and MikTeX on Linux Mint: 
Lyx_example1.pdf without any changes in the settings, and 
Lyx_example2.pdf with in LyX the language code set to Unicode (utf8). 
Both do have references. So there must be something else in your setup 
that causes the problem.





Sent from Yahoo Mail for iPhone 
<https://overview.mail.yahoo.com/?.src=iOS>


On Friday, June 12, 2020, 11:37 am, Mike Reeks  
wrote:


I’ll give it a go Kees. Thanks


Sent from Yahoo Mail for iPhone
<https://overview.mail.yahoo.com/?.src=iOS>

On Friday, June 12, 2020, 10:06 am, Kees Zeelenberg  wrote:


Op 11-06-2020 om 17:18 schreef Paul A. Rubin:
On 6/11/20 7:36 AM, Mike Reeks wrote:

  ...

*From: *Mike Reeks <mailto:mike.re...@yahoo.com>
*Sent: *11 June 2020 10:45
*To: *lyx-users-subscr...@lists.lyx.org
<mailto:lyx-users-subscr...@lists.lyx.org>
*Subject: *Problems using Bibtex with lyx. Help!!

I have used bibtex generated bibliography with access to an
appropriates bibtex database of references in all my lyx files
that cite references.

Upto now I have had no problems. I usually generate a pdf file
in the lyx document conversion. Now for some unknown reason
when converting a lyx file toa  pdf file or any other file the
reference list  is missing in the document conversion and the
reference in the text are not recognised and appear as [?]. I
have no idea what has caused the problem. Why it was working
before and not now since as far as I am aware I have done
nothing.  It happens on all my lyx files. I attach a simple
example lyx file, the latex file and the pdf conversion file
and the bib reference file. I would be very grateful if
someone could shed some light as to what is going on. Its a
really annoying. I am writing a review article using lyx which
is about 6o pages long

Best regards

Mike Reeks

Sent from Mail
<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10


When I compile your MWE, I get both references printed, but
the second reference is garbled and causes a warning message
in the LaTeX log. It appears that the citation was copied from
a PDF file and pasted into the BibTeX database (either
directly or through a program such as JabRef). If you open the
.bib database in a plain text editor and cursor through the
title of the Tian & Ahmad paper, you'll see that the first two
letters of "flows" count as one character (due to kerning in
the PDF file). Similarly, the two f's in "different" are
actually one character.

There's probably a smarter way to fix it, but all else failing
you can run through the database and retype anything that
generates a complaint in the LaTeX log.

Paul


Same here, on MS-Windows with MikTeX. As an alternative to
Paul's suggestion, you might  set the language coding to utf8
(in LyX: Document / Settings / Language / other)

Kees




Lyx_example1.pdf
Description: Adobe PDF document


Lyx_example2.pdf
Description: Adobe PDF document
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: FW: Problems using Bibtex with lyx.

[Kees Zeelenberg]

Op 11-06-2020 om 17:18 schreef Paul A. Rubin:

On 6/11/20 7:36 AM, Mike Reeks wrote:


...

*From: *Mike Reeks 
*Sent: *11 June 2020 10:45
*To: *lyx-users-subscr...@lists.lyx.org 


*Subject: *Problems using Bibtex with lyx. Help!!

I have used bibtex generated bibliography with access to an 
appropriates bibtex database of references in all my lyx files that 
cite references.


Upto now I have had no problems. I usually generate a pdf file in the 
lyx document conversion. Now for some unknown reason when converting 
a lyx file toa  pdf file or any other file the reference list  is 
missing in the document conversion and the reference in the text are 
not recognised and appear as [?]. I have no idea what has caused the 
problem. Why it was working before and not now since as far as I am 
aware I have done nothing.  It happens on all my lyx files. I attach 
a simple example lyx file, the latex file and the pdf conversion file 
and the bib reference file. I would be very grateful if someone could 
shed some light as to what is going on. Its a really annoying. I am 
writing a review article using lyx which is about 6o pages long


Best regards

Mike Reeks

Sent from Mail  for 
Windows 10



When I compile your MWE, I get both references printed, but the second 
reference is garbled and causes a warning message in the LaTeX log. It 
appears that the citation was copied from a PDF file and pasted into 
the BibTeX database (either directly or through a program such as 
JabRef). If you open the .bib database in a plain text editor and 
cursor through the title of the Tian & Ahmad paper, you'll see that 
the first two letters of "flows" count as one character (due to 
kerning in the PDF file). Similarly, the two f's in "different" are 
actually one character.


There's probably a smarter way to fix it, but all else failing you can 
run through the database and retype anything that generates a 
complaint in the LaTeX log.


Paul

Same here, on MS-Windows with MikTeX. As an alternative to Paul's 
suggestion, you might  set the language coding to utf8 (in LyX: Document 
/ Settings / Language / other)


Kees

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

Re: LyX 2.3.5

[Kees Zeelenberg]

Op 10-06-2020 om 11:20 schreef Bernt Lie:


Hm… your advice under point A:…

  * Use a different adm name from my standard user name when I install
programs?

Yes: login under your standard name (ordinary user), and Windows will 
ask for an administrator password when you try to install.
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

RE: LyX 2.3.5

[Kees Zeelenberg (kzStats)]

Van: lyx-users  Namens Bernt Lie
Verzonden: woensdag 10 juni 2020 09:58
Aan: parubi...@gmail.com; lyx-users@lists.lyx.org
Onderwerp: RE: LyX 2.3.5

 

So… I have uninstalled both MikTeX and LyX, and try to re-install them.

 

With MikTeX, I do the following:

 

1.  Choose to install it under directory 
“C:\\Program_Files\MikTeX\MikTeX_2_9” instead of the default location 
(“…\AppData\Local\Programs\MikTeX 2.9\”)
2.  Settings: Preferred paper size – A4, Install missing pagackages 
on-the-fly: Yes
3.  After MikTeX has installed packages, I check for updates. There were 8 
updates, which I installed from “A random package repository on the internet”. 

 

Next, I install LyX 2.3.5:

4.  I install LyX in directory “C:\Program_Files\LyX\LyX_2_3”
5.  The LyX installer finds MikTeX at 
“C:\Program_Files\MikTeX\MikTeX_2_9\miktex\bin\x64”. 

 

6.  LyX takes some time to install, and downloads some missing packages:

 



7.  When LyX has been installed, I try to open a template. Result:



 

I do a search for file IEEEtran.cls, and it is there:



 

 

Questions:

A.  Why doesn’t LyX find this file?
B.  Is the problem that I have not chosen the default installation path of 
LyX and/or MikTeX?

 

[KZLG] 

I just had the same error earlier this morning. From my experience:

A.  Probably because the filename database has not been updated. This may 
happen when you install MikTeX as an administrator (user who has administrative 
rights), but call LyX as that same user but without invoking his administrative 
rights; or if you have followed some variant of this.
In general, it is best to install as an administrator but call your 
applications as an ordinary user (i.e. user without any administrative rights), 
and so keep a strict difference between the two types of users.
B.  Perhaps. You might try it if you cannot follow the advice under A.

 

Kees

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

Re: LyX: No textclass is found ??

[Kees Zeelenberg]

Op 28-05-2020 om 09:37 schreef Bernt Lie:


As far as I know, I have installed everything the way I used to do.

I notice one difference. On my old computer, MikTeX is given path 
(System variables):


  * C:\Program Filex (x86)\MikTeX 2.9\miktex\bin\

while on the new computer, MikTeX is given path (User variables for …):

  * C:\Users\...AppData\Local\Programs\MiKTeX 2.9\miktex\bin\x64\


Questions:

 1. Any reasons for this change in path?
 2. What can I do to fix the set-up? (Note: during installation of
LyX, LyX apparently detected the correct path on the new machine.)


1. You must have installed MikTeX as ordinary user, not as administrator.

1. Is C:\Users\...AppData\Local\Programs\MiKTeX 2.9\miktex\bin\x64\ in 
your Path?


2. You could uninstall MikTeX and install as administrator.

2. Did you reconfigure LyX?

Best,

Kees

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

Re: Archaic Greek?

[Kees Zeelenberg]

Op 19-04-2020 om 20:07 schreef Bernd:


PS:

I found a promising Unicode font (Aegean https://dn-works.com/ufas/ 
), but I cannot get the alternative 
glyphs to work.


For example, I tried 
{\fontspec{Aegean}[StylisticSet=8,CharacterVariant=7:2]̈}, but I 
always get standard glyph...



Did you compile with LuaLaTex or XeLaTeX?
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

RE: Some issues with the latest update of MikTeX

[Kees Zeelenberg (kzStats)]

-Oorspronkelijk bericht-
Van: lyx-users  Namens Baris Erkus
Verzonden: donderdag 7 november 2019 09:10
Aan: lyx-users@lists.lyx.org
Onderwerp: Some issues with the latest update of MikTeX

> 
> LyX reported that iftex.sty was missing. I checked MikTeX and indeed iftex 
> package was somehow not loaded in the package list, > which is awkward since 
> I have installed "all" MikTeX packages and everything is expected to be 
> there. It does not make sense
>  MikTeX remove some standard packages during a MikTeX update.
> ...
> Please do not install the latest MikTeX update till you make sure it is safe 
> to do so.

On my machine (Windows 10, x64, LyX 2.3.3, MikTeX installed as administrator in 
C:\Program Files) everything still works fine after updating the MikTeX 
packages. The location of the iftex package has been changed: it is now in 
tex\generic instead of tex\latex; the latex\iftex folder is now indeed empty, 
but the generic\iftex folder is full. I did not have to reconfigure LyX, 
iftex.sty is still found when included in the preamble.
Perhaps somehow the MikTeX file name database was not refreshed?




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

RE: Reuse MikTeX from Win10 in WSL

[Kees Zeelenberg (kzStats)]

Thanks for sharing - this is interesting. Did you turn off the option on the 
Linux side to install automatically missing modules (assuming that such an 
option exists there, too)? One of the nice things about MikTeX in Windows is 
that the modules are loaded dynamically inside of LaTeX (or even LyX). TeXLive 
has huge "chunks" for modules (via apt-get), at least as far as I can tell. 

 

If you turn it on, then missing packages might be installed twice. I am not 
sure if you can configure MikTeX such that packages are installed in the common 
package directory (if I remember correctly, you cannot move it up above the 
Linux root directories in the MixTeX console).  If you turn it off, then you 
must either install the packages by hand or switch to Windows, which may not be 
such a problem when using WSL. You might also try to add the Linux package 
directory to the list of root directories under Windows; I haven’t tried this 
but perhaps it works.

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

RE: Reuse MikTeX from Win10 in WSL

[Kees Zeelenberg (kzStats)]

Van: lyx-users  Namens Cris Fuhrman
Verzonden: dinsdag 15 oktober 2019 15:15
Aan: LyX Users 
Onderwerp: Reuse MikTeX from Win10 in WSL

 

The trouble is that, like many things WSL, I wind up with two installations of 
the same library (MikTeX from Win 10 and TexLive from Ubuntu install of LyX). I 
know a MikTeX exists for Ubuntu, so I got to thinking maybe I could configure 
it to point to the Win 10 installation.

 

Yes, this is possible; that is to say I once did this under a dual boot of W10 
and Lubuntu. Install MikTeX in the usual way under one system, say W10, then 
install the basics under the other system, WSL, and add the W10 install TEXMF 
root directory, where the packages are, as user root directory under WSL.  Of 
course, in this construct, packages can only be updated under W10.

It should also be possible to share between TeXLive and MikTeX in a similar way.

I don’t do this anymore, since HD are cheap nowadays. 

 

 

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

Re: Is latest Windows 10 (1809 prior to 1903-not installed) Update breaking Lyx 2.33 and MikTex?

[Kees Zeelenberg]

Op 14-07-19 om 19:20 schreef Richard Kimberly Heck:

On 7/14/19 12:26 PM, Brian Davis wrote:

without more information. But contrary to what someone said here, MikTeX
has an annoying habit of updating itself in the background and breaking
things. We've seen it time and time again. The list archives are full of
such problems.


I have been using MikTeX for over 15 years (with LyX for over 10 years), 
and have never experienced such an automatic update that some have 
ascribed to it. To make sure, I have checked on the MikTeX issue 
tracker, with the following outcome. A user can configure MikTeX to 
install on the fly LaTeX-packages that are required by his/her document. 
But MikTeX does never update automatically its executables or packages 
that have previously been installed; this has to be done manually 
through the MikTeX console. 
(https://github.com/MiKTeX/miktex/issues/342#issuecomment-512218341)


In the past LyX was available in a bundle with MikTeX. During install, 
the LyX-installer did update MikTeX; so it was not MikTeX, but the 
LyX-installer that did the update, and caused problems.

Re: Is latest Windows 10 (1809 prior to 1903-not installed) Update breaking Lyx 2.33 and MikTex?

[Kees Zeelenberg]

Op 12-07-19 om 21:36 schreef Brian Davis:

@Andrew Parsloe

I tried installing I3backend and "Reconfigure" / Restart Lyx and no dice.

I also checked for article.cls and MikTeX states Itxbase is installed 
but LyX states it is still unavailable.


Any other packages? that you may have also installed?

Thx
B


MikTeX comes with its own kpsewhich. You may check whether MikTeX can 
find e.g. article.cls by giving the command (in a command prompt 
window): kpsewhich article.cls


Kees

Re: Is latest Windows 10 (1809 prior to 1903-not installed) Update breaking Lyx 2.33 and MikTex?

[Kees Zeelenberg]

Op 12-07-19 om 19:29 schreef Richard Kimberly Heck:

On 7/12/19 11:07 AM, Pavel Sanda wrote:


Sounds like MikTeX updated packages in background :)

Sounds like an old and very sad story.

Riki


MikTeX never updates packages by itself (in the background); you must 
always do that actively yourself through the MikTeX console.


Kees

Re: LyX installation problems on Windows 10.

[Kees Zeelenberg]

Op 08-04-19 om 12:55 schreef 장지웅(수학과):


I posted the result of new try in the same link:

https://tex.stackexchange.com/questions/483668/installing-lyx-no-textclass-is-found?noredirect=1#comment1222832_483668

Thanks,
Jiwoong Jang


Sometimes these problems occur when one of miktex and lyx has been 
installed as administrator and the other as ordinary user (i.e. a user 
without administrative rights). In my experience it is best to install 
both as administrator; but whenever you need to reconfigure lyx, you 
must then start it as administrator.



Best,


Kees

Re: configuration fails

[Kees Zeelenberg]

In my experience these configuration failures occur either when one of 
LyX and MikTeX (or TeXLive) has been installed as administrator and the 
other as ordinary user, or when one is installed under Windows and the 
other under another OS. Since Cygwin acts in some ways as an OS, in 
particular in its use of Unix-type file paths, this may indeed be the 
cause of your problems.


However, for using LyX, there is no need to install Cywgin. The normal 
Windows LyX with Windows MikTeX or TeXLive is sufficient. You do not 
need to uninstall Cygwin, just install either Windows LyX with Windows 
MikTeX or TeXLive, or Cygwin LyX with Cywgin TeXLive.


Cheers,

Kees

Op 06-03-19 om 20:34 schreef Patrick Dupre:

I guess that I have the answer.
lyx-2.3.2-cygwin.tar.gz 


has not been installed.
But configure.py  should have detected it!
===
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
===
*Sent:* Wednesday, March 06, 2019 at 8:29 PM
*From:* "Patrick Dupre" 
*To:* "Richard Kimberly Heck" 
*Cc:* "Kornel Benko" , lyx-users@lists.lyx.org
*Subject:* Re: configuration fails

I am sorry for the confusion.
none of the files exist on the computer.
Anyway. I do not think that it is the issue.
It seems that the py file terminates normally.
Is checkTeXPaths  executed?
 it seems that the output windows_style_tex_paths is not set
is it because the statement is false?
if os.name == 'nt' or sys.platform == 'cygwin':
why test only nt and cygwin ?
cygwin is not installed, it does not seems that we need cygwin for lyx.
Could you confirm it?
checkOtherEntries does not provide any information
lyx_kpsewhich may be not set to true
I will check about
    checkModulesConfig()
    checkCiteEnginesConfig()
    checkXTemplates()
    checkLatexConfig()
    removeTempFiles()
later after the os issue has need clarified.
*Sent:* Wednesday, March 06, 2019 at 7:43 PM
*From:* "Richard Kimberly Heck" 
*To:* "Patrick Dupre" , "Kornel Benko" 
*Cc:* lyx-users@lists.lyx.org
*Subject:* Re: configuration fails
On 3/6/19 8:27 AM, Patrick Dupre wrote:

Hello,

The configuration stop at
DEBUG: Removing file a b.tex
DEBUG: Removing file a b.log
DEBUG: Failed to remove file texput.log

Actually, any of the 3 files exists on the computer

Sorry, do you mean these files do exist, or that they do not exist? If 
they do exist, what directory are they in?



I can comment these lines in the python file, but it does not help.
Actually, the rest of the file is not executed!

I check on the permissions of the Lyx and Miktex files. But I do
not see
any thing wrong.

One possibility is that this is some kind of file-locking issue. We've 
seen this kind of thing on Windows before, though with temporary files.


Riki

Re: you say install latest version of MiKTeX before installing LyX - what is the minimal version needed?

[Kees Zeelenberg]

Op 13-10-18 om 19:58 schreef Paul Johnson:

The only critical flaw in TeXLive we have encountered is that it does
not include texi2pdf. Because of that absence, the R team is still
devoted to MikTeX as a part of the tool chain to build/use R for
windows. I spent a while trying to figure out how to compile texi2pdf
on Windows and gave up. (It appears to me the efforts to make open
source things work on windows are fraught with danger. The Windows
test system here has 5 or 6 different Cygwin-based installations and
the path is a tangled web of incompatible libraries and executables.
Sorry, that's just a Unix guy in foreign territory whining.)


texi2pdf is a script around makeinfo. MikTeX does not have texi2pdf / 
makeinfo either. Probably MikTeX is used because it has texify. It is 
true that texify is able to call makeinfo. But from looking at the 
source at https://github.com/MiKTeX/miktex, it appears that it does this 
only if a certain option for that is given on the command line of 
texify; and if makeinfo is then not available,  texify quits.


So it might well be that what texify actually does, is to run latex, 
bibtex etc. several times; and for that it is indeed very handy. There 
may be an alternative for this in TeXLive or elsewhere. If not, then it 
would probably be quite easy to compile texify. In any case, its source 
code is GPL.


As far as I recall, texipdf / makeinfo is only needed for documents 
written in an older version of the TeXInfo format. But if it is really 
needed, then it is easy to compile for Windows, since from the sources 
at GnuWin32, it appears that it compiles without changes on Windows, 
with the mingw compiler or with the VisualC++ compiler. It is even 
easier to compile on Linux with a cross compiler for Windows; so no need 
for Cygwin.


Kees

RE: Windows + TeXLive + LyX 2.3.0

[Kees Zeelenberg]

>I actually checked that on linux distros under my hands (most importnantly 
>debian)
>before triggering this debate and it turned out that miktex was not by default 
>in 
>the repositories, so proper miktex install goes far beyond few clicks
> in various package installers...

That is indeed a disadvantage. But there are separate MikTeX repositories for 
Ubuntu and for Debian. See: https://miktex.org/howto/install-miktex-unx
My own experience was that after adding these to the (Linux) package source 
list, MikTeX was quite easy to install.

Best,

Kees

RE: Windows + TeXLive + LyX 2.3.0

[Kees Zeelenberg]

>1. increased document interoperability between architectures because both
>  Linux and Mac use preferably TeX Live (MacTeX is redistribution of
>  TeX Live if I read their pages right, CMIIW).

Both MikTeX and TeXLive use the same sources, so there is no functional 
difference. They only differ in the GUI and the updating process, and in my 
experience MikTeX is here much more mature and easy to use than TeXLive. In 
fact, it would even be much better if LyX were to switch to MikTeX on Linux.

>2. the instalation time of first install of MiKTeX (including triggered
>   online updates via configure) is *horrific*. As I wrote in some earlier
>   email, it took >1 hour to get LyX+MiKTeX working on clean Win machine
>   mainly because of MiKTeX package handling (and our reconfigure:).

Installation time is mainly so long because LyX installs each missing package 
separately, and has to call the MikTeX package manager (mpm) each time. But by 
using the –install option, mpm can also install more than one package, either  
from a package list on the command line or from a list in a file, and then 
works much faster. The whole process would then probably take only a few 
minutes. See https://docs.miktex.org/manual/mpm.html for more details.

Best,

Kees

Re: The tortured release of 2.3.0 Windows binaries

[Kees Zeelenberg]

I may be wrong but my understanding of the discussion is that we are moving
towards a situation where LyX can only be installed if the latest MikTeX is
or has been installed. If this is so, then I have some doubts whether this
is wise and practical:

2018-05-14 11:08 GMT+02:00 Bernt Lie :

> A slight update on my indicated procedure in #2: I am, of course, no
> developer and no computer scientist. So let me indicate some understanding
> also for decisions made on things I don't understand.
>
> Suppose... updating MikTeX leads to the following:
> * the latest MikTeX is not backwards compatible, i.e., documents that used
> to work stop working -- that would be a pain for the guy who provides the
> Windows installation,
> * installing the latest MikTeX leads to wiping out currently installed
> templates, etc. for journals, conferences, etc., so that these must be
> reinstalled -- probably something that some people would find a pain, and
> bitch about,
> * installing the latest MikTeX has proved to be problematic for some
> versions of Windows (e.g., some users tend to prefer Windows 7 and refuse
> to update to Windows 10, etc., etc.).
>
>
Precisely for these and similar reasons, it is not wise to require updating
MikTeX to the latest one. The latest one is usually not the one that was
current at the time LyX was compiled and the installer created. So we can
never guarantee that LyX works with the latest MikTeX, and therefore we
should not require updating to the latest one. Instead the procedure
followed until 2.2.3 works always. That is: there are two installers. The
first one installs only LyX, and it is up to the user to ensure that he has
a working and compatible TeX installation, whether that is the latest
MikTeX, an earlier MikTeX, TeX Live, or another one. The second one
installs LyX + MikTeX; users choosing this installer should be warned that
LyX may cease to work correctly, if they update or otherwise change the
MikTeX installation, and that MikTex should remain frozen.

Moreover there is now a TeX Live distribution for Windows, and if we
require MikTeX (that is, if the installer refuses to install unless MikTeX
is installed), this would be a great barrier to users who favor TeX Live.


> In summary: I understand some caution if the guy who provides the Windows
> installation may come in a situation that makes many users "mad". That is
> never a good situation.
>

I agree. Requiring to update to the latest MikTeX could possibly lead to a
lot of questions to the maintainer.

Cheers,

Kees

Re: possible issue with newtxmath?

[Kees Zeelenberg (iPad)]

2017-01-20 23:23 GMT+01:00 Guenter Milde :

>
> * Generally (i.e. with document classes that do not select a font), I
> recommend
>
>   - Latin Modern with standard AMS math, or
>
>   - Times or Palatino or Linux Libertine with newtxmath, or
>
>   - Fourier (the Fourier package combines the Utopia text font with its
> own math fonts).
>
>
> Günter
>
> I have had good results with the stix package and the stix fonts. They
contain a large number of mathematical symbols, whcih fit in nicely with
Times Roman..

Kees