Am 09.07.2018 um 20:16 schrieb Richard Kimberly Heck:

Due to a bug in MiKTeX, installation of LyX 2.3.0 can sometimes
cause the MiKTeX installation to be corrupted. We highly recommend
that MiKTeX users update to the latest version *before* installing LyX
2.3.0. (If you run into problems, the solution will be to uninstall MiKTeX
and then re-install.)

Dear LyX colleagues,

at first apologies for being off so long I had an accident hindering me to use keyboards.

I missed of course the recent LyX development. Nevertheless I explained several times until May why such an announcement breaks the fundamental understanding I have for the LyXWinInstaller. As I already wrote, my goal is that everybody is able to get a fully functional LyX by using the installer. My 70+ year old mother was the first person reporting me a problem and as consequence I found a big bug in MiKTeX. That was fixed long ago and with the installer for LyX 2.3.0 my mother got her LyX repaired. So perfect for me but not for you. Now you tell people to update MiKTeX. How should they do this? Does my mother know what MiKTeX is? Of course not. I visited her recently and told her about. We tried tried to update MiKTeX on her old PC (where there is still the old MiKTeX from 2017). At first she failed but also for me running the MiKTeX update service did not lead to the current MiKTeX (seems to be another bug of the old MiKTeX setup). So your announcement is not helpful for average users.

I took always care for average users because experienced users know how to fix problems in there own by googling, writing mails to the lists etc. Average users are just users without all the background knowledge one needs to update e.g. MiKTeX. I understood that your focus is to please experienced users. Since I cannot live with such a decision that would my own mother left alone with problems she doesn't understand and cannot solve, I decided to release LyXWinInstaller as my own project.
I hope that this way LyX can also be used by average users under Windows.

regards Uwe

Reply via email to