Re: LyX 2.3.0 - display of int
Andrew Parsloe wrote: > >Is someone else around running lyx on Qt>5.7 on different OS than on suse? > >What are current windows versions use? > > > >Pavel > My 2.3.0 (not quite Riki's final version) uses Qt 5.10.1. Integrals > display correctly. That's good news, meaning it might be something specific either to qt 5.9 or opensuse config. Pavel
Re: LyX 2.3.0 - display of int
On 30/08/2018 4:00 a.m., Pavel Sanda wrote: M.B. Schiekel wrote: I agree with your bet, Pavel :-) In my last email with my suggested workaraound I wrote: I compiled LyX-2.3.0 on an openSUSE-Leap-15.0 system with QT-4.8.7 . And hey, all integrals are displayed right :-) So this integral-display-bug will be most likely in the LyX-2.3.0 interaction with Qt-5.9.4. Now for LyX-users of openSUSE-Leap-15.0 with KDE-Plasma-5.12.5 and Qt-5.9.4 this is an unpleasant news, because Leap-15.0 and KDE-Plasma is meant to be stable and to get a long-term-support. And not every LyXer likes to search all needed devl-libs and to compile LyX. If there is open interest of the LyX-community I can offer my LyX-2_3_0.rpm on an openSUSE-Leap-15.0 system with QT-4.8.7 . It would be interesting to see in which version exactly the rendering breaks. I have Qt 5.7.1 (debian stable) and rendering looks OK. In other words you might get advantages of Qt 5, just use 5.7 instead of 5.9... If on the other hand you see your problems even with, say 5.7.1, than it's not generic Qt problem, but something suse-related. Is someone else around running lyx on Qt>5.7 on different OS than on suse? What are current windows versions use? Pavel My 2.3.0 (not quite Riki's final version) uses Qt 5.10.1. Integrals display correctly. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: LyX 2.3.0 - display of int
M.B. Schiekel wrote: > I agree with your bet, Pavel :-) > In my last email with my suggested workaraound I wrote: > > I compiled LyX-2.3.0 on an openSUSE-Leap-15.0 system with QT-4.8.7 > > . And hey, all integrals are displayed right :-) So this > > integral-display-bug will be most likely in the LyX-2.3.0 > > interaction with Qt-5.9.4. > > Now for LyX-users of openSUSE-Leap-15.0 with KDE-Plasma-5.12.5 and > Qt-5.9.4 this is an unpleasant news, because Leap-15.0 and KDE-Plasma > is meant to be stable and to get a long-term-support. And not every > LyXer likes to search all needed devl-libs and to compile LyX. > If there is open interest of the LyX-community I can offer my > LyX-2_3_0.rpm on an openSUSE-Leap-15.0 system with QT-4.8.7 . It would be interesting to see in which version exactly the rendering breaks. I have Qt 5.7.1 (debian stable) and rendering looks OK. In other words you might get advantages of Qt 5, just use 5.7 instead of 5.9... If on the other hand you see your problems even with, say 5.7.1, than it's not generic Qt problem, but something suse-related. Is someone else around running lyx on Qt>5.7 on different OS than on suse? What are current windows versions use? Pavel
Re: LyX 2.3.0 - display of int
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 29.08.2018 um 14:00 schrieb Pavel Sanda: > [bernhard]: > 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on an > older openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with > Qt-5.6.2 and TeXLive 2016. Result: /int, /iint, /iiint, > /nt, /ioint - all are displayed correctly by LyX. > > 2. And as before: LyX-2.3.0 and LyX-2.2.4 on a > openSUSE-Leap-15.0 system with KDE-Plasma 5.12.5 with > Qt-5.9.4 and TeXLive 2017, i.e. 2017.20170520-lp150.8.2. > Result: /int, /iint, /iiint, /nt, /ioint - all are > displayed faultily by LyX, i.e. top of the integral is > bottom of the line (see png-file). > ... [Pavel] The problem might be that with newer version Qt again > (cf bug #8493) changed how it interprets .ttf files, so either our > rendering would need to change or ttf file would need change. Or > both. ... Thank you Pavel, and again thank you Scott! I agree with your bet, Pavel :-) In my last email with my suggested workaraound I wrote: > I compiled LyX-2.3.0 on an openSUSE-Leap-15.0 system with QT-4.8.7 > . And hey, all integrals are displayed right :-) So this > integral-display-bug will be most likely in the LyX-2.3.0 > interaction with Qt-5.9.4. Now for LyX-users of openSUSE-Leap-15.0 with KDE-Plasma-5.12.5 and Qt-5.9.4 this is an unpleasant news, because Leap-15.0 and KDE-Plasma is meant to be stable and to get a long-term-support. And not every LyXer likes to search all needed devl-libs and to compile LyX. If there is open interest of the LyX-community I can offer my LyX-2_3_0.rpm on an openSUSE-Leap-15.0 system with QT-4.8.7 . kind regards, bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- iF0EARECAB0WIQR1oo94k6dUHpHERdOxOsCN/2xXCgUCW4agawAKCRCxOsCN/2xX CoP/AJ9rcG0mTpuIsEqg8W9t2WfycT58aQCfSnoDLfo7khutyA/tAzfntCmN44Y= =tXU+ -END PGP SIGNATURE-
Re: LyX 2.3.0 - display of int
M.B. Schiekel wrote: > >>> 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on an > >>> older openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with > >>> Qt-5.6.2 and TeXLive 2016. Result: /int, /iint, /iiint, > >>> /nt, /ioint - all are displayed correctly by LyX. > >>> > >>> 2. And as before: LyX-2.3.0 and LyX-2.2.4 on a > >>> openSUSE-Leap-15.0 system with KDE-Plasma 5.12.5 with Qt-5.9.4 > >>> and TeXLive 2017, i.e. 2017.20170520-lp150.8.2. Result: /int, > >>> /iint, /iiint, /nt, /ioint - all are displayed faultily by > >>> LyX, i.e. top of the integral is bottom of the line (see > >>> png-file). > >>> > >>> Now I think, the TeXLive-2017-fonts might be faulty. Does > >>> anybody here work with the above mentioned TeXLive 2017 > >>> version and has no problems with /int ?? My bet is that the problem you see is related to Qt version and has nothing to do with TeXLive. Our integrals in mathed are painted through the font files you discovered below: > >> $ apt-file list fonts-lyx fonts-lyx: > >> /usr/share/doc/fonts-lyx/NEWS.Debian.gz fonts-lyx: > >> /usr/share/doc/fonts-lyx/NEWS.gz fonts-lyx: > >> /usr/share/doc/fonts-lyx/ReadmeBaKoMa4LyX.txt fonts-lyx: > >> /usr/share/doc/fonts-lyx/changelog.Debian.gz fonts-lyx: > >> /usr/share/doc/fonts-lyx/copyright fonts-lyx: > >> /usr/share/fonts/truetype/lyx/cmex10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/cmmi10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/cmr10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/cmsy10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/esint10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/eufm10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/msam10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/msbm10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/rsfs10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/stmary10.ttf fonts-lyx: > >> /usr/share/fonts/truetype/lyx/wasy10.ttf The problem might be that with newer version Qt again (cf bug #8493) changed how it interprets .ttf files, so either our rendering would need to change or ttf file would need change. Or both. According to my experience Qt devs are unfortunately not communicative about related problems and opening bug about font rendering in Qt bug tracker won't likely change much. > How can I tell LyX to use for integrals the display-font esint10.ttf > instead of wasy10.ttf? The file you are looking for is lib/symbols, each glyph has it's separate entry. Pavel
Re: LyX 2.3.0 - display of int [Workaround]
On Sun, Aug 26, 2018 at 03:26:32PM -0400, Scott Kostyshak wrote: > On Sun, Aug 26, 2018 at 08:37:18PM +0200, M.B. Schiekel wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Am 22.08.2018 um 18:23 schrieb M.B. Schiekel: > > > [bernhard] 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on > > > an older openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with > > > Qt-5.6.2 and TeXLive 2016. Result: /int, /iint, /iiint, /nt, > > > /ioint - all are displayed correctly by LyX. > > > > > > 2. And as before: LyX-2.3.0 and LyX-2.2.4 on a openSUSE-Leap-15.0 > > > system with KDE-Plasma 5.12.5 with Qt-5.9.4 and TeXLive 2017, i.e. > > > 2017.20170520-lp150.8.2. Result: /int, /iint, /iiint, /nt, > > > /ioint - all are displayed faultily by LyX, i.e. top of the > > > integral is bottom of the line (see png-file). ... > > > > > > Hi Scott, Kornel, Ricardo, > > and all other interested friends, > > > > now I've carried on to fool around and have found a workaround, that > > will do for me. > > I compiled LyX-2.3.0 on an openSUSE-Leap-15.0 system with QT-4.8.7 . > > And hey, all integrals are displayed right :-) > > > > So this integral-display-bug will be most likely in the LyX-2.3.0 > > interaction with Qt-5.9.4. > > Thanks for reporting back this workaround. Hopefully we can figure out > the root cause eventually. Cor (now CC'd), There are two openSUSE users, Bernhard, and Ricardo, who are seeing a strange bug with the LyX display of \int. Can you take a look at this thread and see if you can reproduce? Bernhard found a workaround, which was compiling with Qt 4, but it would be nice to figure out the core issue. Thanks, Scott signature.asc Description: PGP signature
Re: LyX 2.3.0 - display of int [Workaround]
On Sun, Aug 26, 2018 at 08:37:18PM +0200, M.B. Schiekel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am 22.08.2018 um 18:23 schrieb M.B. Schiekel: > > [bernhard] 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on > > an older openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with > > Qt-5.6.2 and TeXLive 2016. Result: /int, /iint, /iiint, /nt, > > /ioint - all are displayed correctly by LyX. > > > > 2. And as before: LyX-2.3.0 and LyX-2.2.4 on a openSUSE-Leap-15.0 > > system with KDE-Plasma 5.12.5 with Qt-5.9.4 and TeXLive 2017, i.e. > > 2017.20170520-lp150.8.2. Result: /int, /iint, /iiint, /nt, > > /ioint - all are displayed faultily by LyX, i.e. top of the > > integral is bottom of the line (see png-file). ... > > > Hi Scott, Kornel, Ricardo, > and all other interested friends, > > now I've carried on to fool around and have found a workaround, that > will do for me. > I compiled LyX-2.3.0 on an openSUSE-Leap-15.0 system with QT-4.8.7 . > And hey, all integrals are displayed right :-) > > So this integral-display-bug will be most likely in the LyX-2.3.0 > interaction with Qt-5.9.4. Thanks for reporting back this workaround. Hopefully we can figure out the root cause eventually. Scott signature.asc Description: PGP signature
Re: LyX 2.3.0 - display of int [Workaround]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 22.08.2018 um 18:23 schrieb M.B. Schiekel: > [bernhard] 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on > an older openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with > Qt-5.6.2 and TeXLive 2016. Result: /int, /iint, /iiint, /nt, > /ioint - all are displayed correctly by LyX. > > 2. And as before: LyX-2.3.0 and LyX-2.2.4 on a openSUSE-Leap-15.0 > system with KDE-Plasma 5.12.5 with Qt-5.9.4 and TeXLive 2017, i.e. > 2017.20170520-lp150.8.2. Result: /int, /iint, /iiint, /nt, > /ioint - all are displayed faultily by LyX, i.e. top of the > integral is bottom of the line (see png-file). ... Hi Scott, Kornel, Ricardo, and all other interested friends, now I've carried on to fool around and have found a workaround, that will do for me. I compiled LyX-2.3.0 on an openSUSE-Leap-15.0 system with QT-4.8.7 . And hey, all integrals are displayed right :-) So this integral-display-bug will be most likely in the LyX-2.3.0 interaction with Qt-5.9.4. Thank all of you, who tried to help - kind regards, bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAluC814ACgkQsTrAjf9sVwrccQCgnkW212rmkaC4kGeryoUQ/HSA PfYAoNseNcA8oOsffmLRF08BQ75DK4+z =hH0I -END PGP SIGNATURE-
Re: LyX 2.3.0 - display of int
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 25.08.2018 um 17:21 schrieb Ricardo Berlasso: > ... I also have problems with int display in 2.3.0 (openSUSE 15.1). > When looking at LyX's fonts I can see what's shown in the > attachment. > > Regards, Ricardo Hi Ricardo, welcome in our group of LyX openSUSE Leap 15.0 victims :-) I think, you're working with 15.0, because there is no 15.1 version out. Our research until now showed, that this seems to be a problem of the openSUSE Leap 15.0 environment, because the LyX_screefonts (\int, ...) in LyX 2.2.4 and 2.3.0 are working correct in openSUSE Leap 42.3 . Might be TeXLive 2018 will bring some help, but I've tried not yet. Might be it's a KDE-Plasma-fault, or anything other, ... The generated PDF is pleasingly Ok. Any suggestions are welcome :-) bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- iF0EARECAB0WIQR1oo94k6dUHpHERdOxOsCN/2xXCgUCW4GHnAAKCRCxOsCN/2xX CrHLAJ0RsKnX6NG+twoc+Eis3WD4PHipnQCbBxvqMwLlg6EEJ7wvhbhQWAsTAwU= =TMSX -END PGP SIGNATURE-
Re: LyX 2.3.0 - display of int
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 25.08.2018 um 17:09 schrieb Kornel Benko: > ... 'Times New Roman' is not 'Latin Modern Roman' ... Hi Kornel, right :-) Changing from 'Times New Roman' to 'Latin Modern Roman' resulted in no change, so I restored my original 'Times New Roman'. But for you I made lyx -dbg font again with 'Latin Modern Roman' :-) Cheers, bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- iF0EARECAB0WIQR1oo94k6dUHpHERdOxOsCN/2xXCgUCW4GD5gAKCRCxOsCN/2xX CpjEAJ9RKOhxCXR4RVy+P197wjLCYD+T3wCgo+GfCbXvnBdbd3Xb4n+KxJv1wf8= =QUPu -END PGP SIGNATURE- munish@linux-cq7k:~> lyx -dbg font Festlegen des Test-Levels auf font Testen von ,font` (Schrift-Handhabung) GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/cmex10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/cmmi10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/cmr10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/cmsy10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/esint10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/eufm10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/msam10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/msbm10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/rsfs10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/stmary10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/wasy10.ttf OK GuiFontLoader.cpp (356): Font 'Roman, Medium, Upright, Normal, none, Emphasis Off, Underline Off, Strike out Off, Cross out Off, Double underline Off, Wavy underline Off, Noun Off, ' matched by Latin Modern Roman GuiFontLoader.cpp (362): This font is NOT an exact match GuiFontLoader.cpp (364): XFLD: unknown GuiFontLoader.cpp (368): The font has size: 15 GuiFontLoader.cpp (186): Looking for font family eufm10 ... GuiFontLoader.cpp (169): got: eufm10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family cmsy10 ... GuiFontLoader.cpp (169): got: cmsy10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family cmmi10 ... GuiFontLoader.cpp (169): got: cmmi10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family cmr10 ... GuiFontLoader.cpp (169): got: cmr10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family cmex10 ... GuiFontLoader.cpp (169): got: cmex10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family msam10 ... GuiFontLoader.cpp (169): got: msam10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family msbm10 ... GuiFontLoader.cpp (169): got: msbm10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family wasy10 ... GuiFontLoader.cpp (169): got: wasy10 [unknown] GuiFontLoader.cpp (201): Trying normal wasy10 ... GuiFontLoader.cpp (169): got: wasy10 [unknown] GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (206): normal! GuiFontLoader.cpp (186): Looking for font family stmary10 ... GuiFontLoader.cpp (169): got: stmary10 [unknown] GuiFontLoader.cpp (201): Trying normal stmary10 ... GuiFontLoader.cpp (169): got: stmary10 [unknown] GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (206): normal! GuiFontLoader.cpp (186): Looking for font family esint10 ... GuiFontLoader.cpp (169): got: esint10 [unknown] GuiFontLoader.cpp (201): Trying normal esint10 ... GuiFontLoader.cpp (169): got: esint10 [unknown] GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (206): normal! GuiFontLoader.cpp (356): Font 'Roman, Medium, Italic, Normal, none, Emphasis Off, Underline Off, Strike out Off, Cross out Off, Double underline Off, Wavy underline Off, Noun Off, ' matched by Latin Modern Roman GuiFontLoader.cpp (362): This font is NOT an exact match GuiFontLoader.cpp (364): XFLD: unknown GuiFontLoader.cpp (368): The font has size: 15 GuiFontLoader.cpp (186): Looking for font family esint10 ... GuiFontLoader.cpp (169): got: esint10 [unknown] GuiFontLoader.cpp (201): Trying normal esint10 ... GuiFontLoader.cpp (169): got: esint10 [unknown] GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (206): normal! GuiFontLoader.cpp (356): Font 'esint, Medium, Upright, Normal, none, Emphasis Off, Underline Off, Strike out Off, Cross out Off, Double underline Off, Wavy underline Off, Noun Off, ' matched by esint10 GuiFontLoader.cpp (362): This font is NOT an exact match GuiFontLoader.cpp (364): XFLD: unknown GuiFontLoader.cpp (368): The font has size: 15 Save document?
Re: LyX 2.3.0 - display of int
Am Samstag, 25. August 2018 16:41:20 CEST schrieb M.B. Schiekel : > GuiFontLoader.cpp (356): Font 'Roman, Medium, Upright, Normal, none, Emphasis > Off, Underline Off, Strike out Off, Cross out Off, Double underline Off, Wavy > underline Off, Noun Off, ' matched by > Times New Roman > 'Times New Roman' is not 'Latin Modern Roman' Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX 2.3.0 - display of int
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > ... You could look at the output from: > > lyx -dbg font > > Maybe it provides clues. Hi Scott, thank you for your kind reply. I added the output of lyx -dbg font . Might be you see more in this output than me ? Cheers, bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- iF0EARECAB0WIQR1oo94k6dUHpHERdOxOsCN/2xXCgUCW4FqigAKCRCxOsCN/2xX CoosAJ0TaePxf2QFprJP2betqRHvT2U8OwCePl8PGMzpqVIdVld9J4u6O+r13DM= =Hwh0 -END PGP SIGNATURE- lyx -dbg font Festlegen des Test-Levels auf font Testen von ,font` (Schrift-Handhabung) GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/cmex10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/cmmi10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/cmr10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/cmsy10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/esint10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/eufm10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/msam10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/msbm10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/rsfs10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/stmary10.ttf OK GuiFontLoader.cpp (250): Adding font /usr/share/lyx/fonts/wasy10.ttf OK GuiFontLoader.cpp (356): Font 'Roman, Medium, Upright, Normal, none, Emphasis Off, Underline Off, Strike out Off, Cross out Off, Double underline Off, Wavy underline Off, Noun Off, ' matched by Times New Roman GuiFontLoader.cpp (362): This font is NOT an exact match GuiFontLoader.cpp (364): XFLD: unknown GuiFontLoader.cpp (368): The font has size: 15 GuiFontLoader.cpp (186): Looking for font family eufm10 ... GuiFontLoader.cpp (169): got: eufm10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family cmsy10 ... GuiFontLoader.cpp (169): got: cmsy10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family cmmi10 ... GuiFontLoader.cpp (169): got: cmmi10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family cmr10 ... GuiFontLoader.cpp (169): got: cmr10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family cmex10 ... GuiFontLoader.cpp (169): got: cmex10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family msam10 ... GuiFontLoader.cpp (169): got: msam10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family msbm10 ... GuiFontLoader.cpp (169): got: msbm10 GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (196): lyx! GuiFontLoader.cpp (186): Looking for font family wasy10 ... GuiFontLoader.cpp (169): got: wasy10 [unknown] GuiFontLoader.cpp (201): Trying normal wasy10 ... GuiFontLoader.cpp (169): got: wasy10 [unknown] GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (206): normal! GuiFontLoader.cpp (186): Looking for font family stmary10 ... GuiFontLoader.cpp (169): got: stmary10 [unknown] GuiFontLoader.cpp (201): Trying normal stmary10 ... GuiFontLoader.cpp (169): got: stmary10 [unknown] GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (206): normal! GuiFontLoader.cpp (186): Looking for font family esint10 ... GuiFontLoader.cpp (169): got: esint10 [unknown] GuiFontLoader.cpp (201): Trying normal esint10 ... GuiFontLoader.cpp (169): got: esint10 [unknown] GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (206): normal! GuiFontLoader.cpp (356): Font 'Roman, Medium, Italic, Normal, none, Emphasis Off, Underline Off, Strike out Off, Cross out Off, Double underline Off, Wavy underline Off, Noun Off, ' matched by Times New Roman GuiFontLoader.cpp (362): This font is NOT an exact match GuiFontLoader.cpp (364): XFLD: unknown GuiFontLoader.cpp (368): The font has size: 15 GuiFontLoader.cpp (186): Looking for font family esint10 ... GuiFontLoader.cpp (169): got: esint10 [unknown] GuiFontLoader.cpp (201): Trying normal esint10 ... GuiFontLoader.cpp (169): got: esint10 [unknown] GuiFontLoader.cpp (176): got it GuiFontLoader.cpp (206): normal! GuiFontLoader.cpp (356): Font 'esint, Medium, Uprigh
Re: LyX 2.3.0 - display of int
On Sat, Aug 25, 2018 at 11:43:37AM +0200, M.B. Schiekel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am 23.08.2018 um 18:13 schrieb Kornel Benko: > > ... That is a problem. The preferences there apply only to > > text-fonts. We don't have yet preferences for math font in > > lyx-display. Could be made a feature request though. OTOH, some > > fonts have own math fonts. Try for instance to use Latin Modern > > Roman as your serif font. This changes here the display of math > > formulas, so there is hope. ... > > > Hi, Kornel > > thank you for your answer, but unfortunately your suggestion didn't > worked. > Now I've fooled around and tried this & that, even a plain vanilla > installation of openSUSE Leap 15.0, but nothing worked. > Any other ideas are welcome :-) You could look at the output from: lyx -dbg font Maybe it provides clues. Scott
Re: LyX 2.3.0 - display of int
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 23.08.2018 um 18:13 schrieb Kornel Benko: > ... That is a problem. The preferences there apply only to > text-fonts. We don't have yet preferences for math font in > lyx-display. Could be made a feature request though. OTOH, some > fonts have own math fonts. Try for instance to use Latin Modern > Roman as your serif font. This changes here the display of math > formulas, so there is hope. ... Hi, Kornel thank you for your answer, but unfortunately your suggestion didn't worked. Now I've fooled around and tried this & that, even a plain vanilla installation of openSUSE Leap 15.0, but nothing worked. Any other ideas are welcome :-) Cheers, bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- iF0EARECAB0WIQR1oo94k6dUHpHERdOxOsCN/2xXCgUCW4EkwwAKCRCxOsCN/2xX Cim4AKDTJSRoVev0+bHNZpH0gNkZta5qMwCfWRvKPxMY3NTZfAILO6/AyGJTZ2A= =jPHl -END PGP SIGNATURE-
Re: LyX 2.3.0 - display of int
Am Donnerstag, 23. August 2018 17:50:30 CEST schrieb M.B. Schiekel : > Am 23.08.2018 um 08:36 schrieb Kornel Benko: > > Am Mittwoch, 22. August 2018 21:07:38 CEST schrieb Scott Kostyshak > > : > >> On Wed, Aug 22, 2018 at 06:23:48PM +0200, M.B. Schiekel wrote: > >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > >>> > >>> Am 18.08.2018 um 23:48 schrieb M.B. Schiekel: > ... Now I downloaded the sources of lyx-2.3.0 and lyx-2.2.4 > and compiled. ... Result: I got this \int display-error in > 2.3.0 and also in 2.2.4. This seems to indicate for me, that > the change of KDE-Plasma 5.8 with Qt-5.8.x in openSUSE Leap > 42.3 to KDE-Plasma 5.12.5 with Qt-5.9.4 in openSUSE Leap 15.0 > might be the cause of this trouble :-( ... > >>> > >>> > >>> Hi Scott, hi friends, > >>> > >>> 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on an > >>> older openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with > >>> Qt-5.6.2 and TeXLive 2016. Result: /int, /iint, /iiint, > >>> /nt, /ioint - all are displayed correctly by LyX. > >>> > >>> 2. And as before: LyX-2.3.0 and LyX-2.2.4 on a > >>> openSUSE-Leap-15.0 system with KDE-Plasma 5.12.5 with Qt-5.9.4 > >>> and TeXLive 2017, i.e. 2017.20170520-lp150.8.2. Result: /int, > >>> /iint, /iiint, /nt, /ioint - all are displayed faultily by > >>> LyX, i.e. top of the integral is bottom of the line (see > >>> png-file). > >>> > >>> Now I think, the TeXLive-2017-fonts might be faulty. Does > >>> anybody here work with the above mentioned TeXLive 2017 > >>> version and has no problems with /int ?? > >> > >> Hi Bernhard, > >> > >> Good investigation. I just realized one thing that might be > >> relevant. On Ubuntu, the "lyx" package depends on a package > >> "fonts-lyx". Perhaps one of the fonts in there would solve your > >> problem? I really don't know if it's likely to help, but it might > >> be worth a short. Here are the contents of "fonts-lyx" package: > >> > >> $ apt-file list fonts-lyx fonts-lyx: > >> /usr/share/doc/fonts-lyx/NEWS.Debian.gz fonts-lyx: ... > >> /usr/share/fonts/truetype/lyx/wasy10.ttf > >> > >> Best, > >> > >> Scott > >> > > > > FWIW, cmake build installs this files under > > /usr/local/share/lyx2.3/fonts/ and the installed lyx uses this > > path, see Tools->Preferences...->Paths->TEXINPUTS prefix: > > > > Kornel > > > > Hi Scott, hi Kornel, > > thank both of you for your kind replies. In openSUSE installations the > LyX-font directory is /usr/share/lyx/fonts > There I find the fonts > - esint10.ttf : seems to be aligned Ok, > - wasy10.ttf : with all integrals gone down, > seems to be a feature, not a bug :-) > > How can I tell LyX to use for integrals the display-font esint10.ttf > instead of wasy10.ttf? > Preferences -> Look & Feel -> Screen fonts > seems not to be the right place? That is a problem. The preferences there apply only to text-fonts. We don't have yet preferences for math font in lyx-display. Could be made a feature request though. OTOH, some fonts have own math fonts. Try for instance to use Latin Modern Roman as your serif font. This changes here the display of math formulas, so there is hope. > Cheers and regards, > bernhard > > Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX 2.3.0 - display of int
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 23.08.2018 um 08:36 schrieb Kornel Benko: > Am Mittwoch, 22. August 2018 21:07:38 CEST schrieb Scott Kostyshak > : >> On Wed, Aug 22, 2018 at 06:23:48PM +0200, M.B. Schiekel wrote: >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> >>> Am 18.08.2018 um 23:48 schrieb M.B. Schiekel: ... Now I downloaded the sources of lyx-2.3.0 and lyx-2.2.4 and compiled. ... Result: I got this \int display-error in 2.3.0 and also in 2.2.4. This seems to indicate for me, that the change of KDE-Plasma 5.8 with Qt-5.8.x in openSUSE Leap 42.3 to KDE-Plasma 5.12.5 with Qt-5.9.4 in openSUSE Leap 15.0 might be the cause of this trouble :-( ... >>> >>> >>> Hi Scott, hi friends, >>> >>> 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on an >>> older openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with >>> Qt-5.6.2 and TeXLive 2016. Result: /int, /iint, /iiint, >>> /nt, /ioint - all are displayed correctly by LyX. >>> >>> 2. And as before: LyX-2.3.0 and LyX-2.2.4 on a >>> openSUSE-Leap-15.0 system with KDE-Plasma 5.12.5 with Qt-5.9.4 >>> and TeXLive 2017, i.e. 2017.20170520-lp150.8.2. Result: /int, >>> /iint, /iiint, /nt, /ioint - all are displayed faultily by >>> LyX, i.e. top of the integral is bottom of the line (see >>> png-file). >>> >>> Now I think, the TeXLive-2017-fonts might be faulty. Does >>> anybody here work with the above mentioned TeXLive 2017 >>> version and has no problems with /int ?? >> >> Hi Bernhard, >> >> Good investigation. I just realized one thing that might be >> relevant. On Ubuntu, the "lyx" package depends on a package >> "fonts-lyx". Perhaps one of the fonts in there would solve your >> problem? I really don't know if it's likely to help, but it might >> be worth a short. Here are the contents of "fonts-lyx" package: >> >> $ apt-file list fonts-lyx fonts-lyx: >> /usr/share/doc/fonts-lyx/NEWS.Debian.gz fonts-lyx: >> /usr/share/doc/fonts-lyx/NEWS.gz fonts-lyx: >> /usr/share/doc/fonts-lyx/ReadmeBaKoMa4LyX.txt fonts-lyx: >> /usr/share/doc/fonts-lyx/changelog.Debian.gz fonts-lyx: >> /usr/share/doc/fonts-lyx/copyright fonts-lyx: >> /usr/share/fonts/truetype/lyx/cmex10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/cmmi10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/cmr10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/cmsy10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/esint10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/eufm10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/msam10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/msbm10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/rsfs10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/stmary10.ttf fonts-lyx: >> /usr/share/fonts/truetype/lyx/wasy10.ttf >> >> Best, >> >> Scott >> > > FWIW, cmake build installs this files under > /usr/local/share/lyx2.3/fonts/ and the installed lyx uses this > path, see Tools->Preferences...->Paths->TEXINPUTS prefix: > > Kornel > Hi Scott, hi Kornel, thank both of you for your kind replies. In openSUSE installations the LyX-font directory is /usr/share/lyx/fonts There I find the fonts - esint10.ttf : seems to be aligned Ok, - wasy10.ttf : with all integrals gone down, seems to be a feature, not a bug :-) How can I tell LyX to use for integrals the display-font esint10.ttf instead of wasy10.ttf? Preferences -> Look & Feel -> Screen fonts seems not to be the right place? Cheers and regards, bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlt+18YACgkQsTrAjf9sVwpCBwCgzYMCWcVyogd5vCBVE6sWD1Y1 E6QAnjwjt9b7YQo0WFs23MqSm9ZIwvhA =0/X6 -END PGP SIGNATURE-
Re: LyX 2.3.0 - display of int
Am Mittwoch, 22. August 2018 21:07:38 CEST schrieb Scott Kostyshak : > On Wed, Aug 22, 2018 at 06:23:48PM +0200, M.B. Schiekel wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Am 18.08.2018 um 23:48 schrieb M.B. Schiekel: > > > ... Now I downloaded the sources of lyx-2.3.0 and lyx-2.2.4 and > > > compiled. ... Result: I got this \int display-error in 2.3.0 and > > > also in 2.2.4. This seems to indicate for me, that the change of > > > KDE-Plasma 5.8 with Qt-5.8.x in openSUSE Leap 42.3 to KDE-Plasma > > > 5.12.5 with Qt-5.9.4 in openSUSE Leap 15.0 might be the cause of > > > this trouble :-( ... > > > > > > Hi Scott, hi friends, > > > > 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on an older > > openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with Qt-5.6.2 and > > TeXLive 2016. > > Result: /int, /iint, /iiint, /nt, /ioint - all are displayed > > correctly by LyX. > > > > 2. And as before: > > LyX-2.3.0 and LyX-2.2.4 on a openSUSE-Leap-15.0 system with KDE-Plasma > > 5.12.5 with Qt-5.9.4 and TeXLive 2017, i.e. 2017.20170520-lp150.8.2. > > Result: /int, /iint, /iiint, /nt, /ioint - all are displayed > > faultily by LyX, i.e. top of the integral is bottom of the line (see > > png-file). > > > > Now I think, the TeXLive-2017-fonts might be faulty. > > Does anybody here work with the above mentioned TeXLive 2017 version > > and has no problems with /int ?? > > Hi Bernhard, > > Good investigation. I just realized one thing that might be relevant. On > Ubuntu, the "lyx" package depends on a package "fonts-lyx". Perhaps one > of the fonts in there would solve your problem? I really don't know if > it's likely to help, but it might be worth a short. Here are the > contents of "fonts-lyx" package: > > $ apt-file list fonts-lyx > fonts-lyx: /usr/share/doc/fonts-lyx/NEWS.Debian.gz > fonts-lyx: /usr/share/doc/fonts-lyx/NEWS.gz > fonts-lyx: /usr/share/doc/fonts-lyx/ReadmeBaKoMa4LyX.txt > fonts-lyx: /usr/share/doc/fonts-lyx/changelog.Debian.gz > fonts-lyx: /usr/share/doc/fonts-lyx/copyright > fonts-lyx: /usr/share/fonts/truetype/lyx/cmex10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/cmmi10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/cmr10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/cmsy10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/esint10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/eufm10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/msam10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/msbm10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/rsfs10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/stmary10.ttf > fonts-lyx: /usr/share/fonts/truetype/lyx/wasy10.ttf > > Best, > > Scott > FWIW, cmake build installs this files under /usr/local/share/lyx2.3/fonts/ and the installed lyx uses this path, see Tools->Preferences...->Paths->TEXINPUTS prefix: Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX 2.3.0 - display of int
On Wed, Aug 22, 2018 at 06:23:48PM +0200, M.B. Schiekel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am 18.08.2018 um 23:48 schrieb M.B. Schiekel: > > ... Now I downloaded the sources of lyx-2.3.0 and lyx-2.2.4 and > > compiled. ... Result: I got this \int display-error in 2.3.0 and > > also in 2.2.4. This seems to indicate for me, that the change of > > KDE-Plasma 5.8 with Qt-5.8.x in openSUSE Leap 42.3 to KDE-Plasma > > 5.12.5 with Qt-5.9.4 in openSUSE Leap 15.0 might be the cause of > > this trouble :-( ... > > > Hi Scott, hi friends, > > 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on an older > openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with Qt-5.6.2 and > TeXLive 2016. > Result: /int, /iint, /iiint, /nt, /ioint - all are displayed > correctly by LyX. > > 2. And as before: > LyX-2.3.0 and LyX-2.2.4 on a openSUSE-Leap-15.0 system with KDE-Plasma > 5.12.5 with Qt-5.9.4 and TeXLive 2017, i.e. 2017.20170520-lp150.8.2. > Result: /int, /iint, /iiint, /nt, /ioint - all are displayed > faultily by LyX, i.e. top of the integral is bottom of the line (see > png-file). > > Now I think, the TeXLive-2017-fonts might be faulty. > Does anybody here work with the above mentioned TeXLive 2017 version > and has no problems with /int ?? Hi Bernhard, Good investigation. I just realized one thing that might be relevant. On Ubuntu, the "lyx" package depends on a package "fonts-lyx". Perhaps one of the fonts in there would solve your problem? I really don't know if it's likely to help, but it might be worth a short. Here are the contents of "fonts-lyx" package: $ apt-file list fonts-lyx fonts-lyx: /usr/share/doc/fonts-lyx/NEWS.Debian.gz fonts-lyx: /usr/share/doc/fonts-lyx/NEWS.gz fonts-lyx: /usr/share/doc/fonts-lyx/ReadmeBaKoMa4LyX.txt fonts-lyx: /usr/share/doc/fonts-lyx/changelog.Debian.gz fonts-lyx: /usr/share/doc/fonts-lyx/copyright fonts-lyx: /usr/share/fonts/truetype/lyx/cmex10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/cmmi10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/cmr10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/cmsy10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/esint10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/eufm10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/msam10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/msbm10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/rsfs10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/stmary10.ttf fonts-lyx: /usr/share/fonts/truetype/lyx/wasy10.ttf Best, Scott signature.asc Description: PGP signature
Re: LyX 2.3.0 - display of int
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 18.08.2018 um 23:48 schrieb M.B. Schiekel: > ... Now I downloaded the sources of lyx-2.3.0 and lyx-2.2.4 and > compiled. ... Result: I got this \int display-error in 2.3.0 and > also in 2.2.4. This seems to indicate for me, that the change of > KDE-Plasma 5.8 with Qt-5.8.x in openSUSE Leap 42.3 to KDE-Plasma > 5.12.5 with Qt-5.9.4 in openSUSE Leap 15.0 might be the cause of > this trouble :-( ... Hi Scott, hi friends, 1. now I managed to compile LyX-2.3.0 and LyX-2.2.4 on an older openSUSE-Leap-42.3 system with KDE-Plasma-5.8.7 with Qt-5.6.2 and TeXLive 2016. Result: /int, /iint, /iiint, /nt, /ioint - all are displayed correctly by LyX. 2. And as before: LyX-2.3.0 and LyX-2.2.4 on a openSUSE-Leap-15.0 system with KDE-Plasma 5.12.5 with Qt-5.9.4 and TeXLive 2017, i.e. 2017.20170520-lp150.8.2. Result: /int, /iint, /iiint, /nt, /ioint - all are displayed faultily by LyX, i.e. top of the integral is bottom of the line (see png-file). Now I think, the TeXLive-2017-fonts might be faulty. Does anybody here work with the above mentioned TeXLive 2017 version and has no problems with /int ?? Thank you - kind regards, bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlt9jhQACgkQsTrAjf9sVwppxQCggmJ0zOogSyVsyiE8f1Wt+t+C iEcAmwWiaQIM+uXx95R5pftVkv534UXt =G1oB -END PGP SIGNATURE-
Re: LyX 2.3.0 - display of int
On Sat, Aug 18, 2018 at 11:48:53PM +0200, M.B. Schiekel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > ... Are you able to compile LyX? If so, you could see if the bug is > > still there in 2.3.1dev and in master. Also, if it is still there, > > you could do a bisect to find out which commit caused it. Since I > > can't reproduce on 2.3.x or current master, I'm not sure what else > > to suggest. > > > > There's also a possibility that the change is not due to a change > > in the LyX code but to using a newer Qt version. Perhaps when > > upgrading your system, the Qt libs got updated also? > > > Hi Scott, > > again thank you for your kind reply. > Now I downloaded the sources of lyx-2.3.0 and lyx-2.2.4 and compiled. > Version 2.3.1dev I didn't found. > Result: I got this \int display-error in 2.3.0 and also in 2.2.4. > This seems to indicate for me, that the change of KDE-Plasma 5.8 with > Qt-5.8.x in openSUSE Leap 42.3 to KDE-Plasma 5.12.5 with Qt-5.9.4 in > openSUSE Leap 15.0 might be the cause of this trouble :-( > > Any idea? I'm currently using Qt 5.9.5 and I don't see the issue you see with 2.3.0. Hopefully others around here will have an idea of how to proceed. Alternatively, you might want to wait a week or so until 2.3.1 is released and see if that somehow magically fixes things. Best, Scott signature.asc Description: PGP signature
Re: LyX 2.3.0 - display of int
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > ... Are you able to compile LyX? If so, you could see if the bug is > still there in 2.3.1dev and in master. Also, if it is still there, > you could do a bisect to find out which commit caused it. Since I > can't reproduce on 2.3.x or current master, I'm not sure what else > to suggest. > > There's also a possibility that the change is not due to a change > in the LyX code but to using a newer Qt version. Perhaps when > upgrading your system, the Qt libs got updated also? Hi Scott, again thank you for your kind reply. Now I downloaded the sources of lyx-2.3.0 and lyx-2.2.4 and compiled. Version 2.3.1dev I didn't found. Result: I got this \int display-error in 2.3.0 and also in 2.2.4. This seems to indicate for me, that the change of KDE-Plasma 5.8 with Qt-5.8.x in openSUSE Leap 42.3 to KDE-Plasma 5.12.5 with Qt-5.9.4 in openSUSE Leap 15.0 might be the cause of this trouble :-( Any idea? Thank you - cheers, bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- iF0EARECAB0WIQR1oo94k6dUHpHERdOxOsCN/2xXCgUCW3iUPQAKCRCxOsCN/2xX CkwBAKDB0clTkLJ/mgSWOP3/cEQN4SFrzwCgzya0xF8aDa17C4bIu+pOM27w0Vk= =ZOvQ -END PGP SIGNATURE-
Re: LyX 2.3.0 - display of int
On Fri, Aug 17, 2018 at 08:53:33PM +0200, M.B. Schiekel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am 17.08.2018 um 17:23 schrieb Scott Kostyshak: > > ...If you are feeling inspired, it would be helpful if you could go > > back through your old bugs that are not marked as fixed (let me > > know if you need help finding these) and say whether you can still > > reproduce them with 2.3.0. > > > Hi Scott, > > thank you for your kind reply. > > 1. As soon as I find time I'll check my old bug-reports with 2.3.0 :-) Great! > 2. > >> - and whoosh: all integrals in mathmode in the LyX-display are > >> gone down a half line (in the PDF-file it's Ok). Any suggestion? > > > > https://www.mail-archive.com/search?l=mid&q=20180131222631.xhlo3g4svsksfi5z%40steph > > I'm not sure, if that's the same problem - so I've added a little > screenshot. This behavior is the same in every math-mode I tested: > inline, display, AMS-xx-environment. hmmm I'm not sure either. > > If I remember correctly, part of the change was fixed for 2.3.1 > > (I'm not sure about this though). > > Is 2.3.1 already available? Not yet. Are you able to compile LyX? If so, you could see if the bug is still there in 2.3.1dev and in master. Also, if it is still there, you could do a bisect to find out which commit caused it. Since I can't reproduce on 2.3.x or current master, I'm not sure what else to suggest. There's also a possibility that the change is not due to a change in the LyX code but to using a newer Qt version. Perhaps when upgrading your system, the Qt libs got updated also? Best, Scott signature.asc Description: PGP signature
Re: LyX 2.3.0 - display of int
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 17.08.2018 um 17:23 schrieb Scott Kostyshak: > ...If you are feeling inspired, it would be helpful if you could go > back through your old bugs that are not marked as fixed (let me > know if you need help finding these) and say whether you can still > reproduce them with 2.3.0. Hi Scott, thank you for your kind reply. 1. As soon as I find time I'll check my old bug-reports with 2.3.0 :-) 2. >> - and whoosh: all integrals in mathmode in the LyX-display are >> gone down a half line (in the PDF-file it's Ok). Any suggestion? > https://www.mail-archive.com/search?l=mid&q=20180131222631.xhlo3g4svsksfi5z%40steph I'm not sure, if that's the same problem - so I've added a little screenshot. This behavior is the same in every math-mode I tested: inline, display, AMS-xx-environment. > If I remember correctly, part of the change was fixed for 2.3.1 > (I'm not sure about this though). Is 2.3.1 already available? Cheers, bernhard - -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/ -BEGIN PGP SIGNATURE- iF0EARECAB0WIQR1oo94k6dUHpHERdOxOsCN/2xXCgUCW3cZpQAKCRCxOsCN/2xX Cp/mAJ9N81FIb4mUTJ+YzXfXF6rx7bEyvwCgwfvgrwa2kV3kx5H+LH+FZ+oU10o= =gj2Y -END PGP SIGNATURE-
Re: LyX 2.3.0 - display of int
Hi Bernhard, Thanks for your nice email. Comments are in-line below. On Fri, Aug 17, 2018 at 01:37:42PM +0200, M.B. Schiekel wrote: > The last time I read and wrote on lyx-users was in 2012, and now and > then I got a message of a resolved minor bug from our hardworking > developers. Again thank all of you! That is good to hear! Those emails are from the LyX bug tracker right? If you are feeling inspired, it would be helpful if you could go back through your old bugs that are not marked as fixed (let me know if you need help finding these) and say whether you can still reproduce them with 2.3.0. > Now I upgraded my openSUSE from Leap-42.3 with LyX-2.2.3 > to Leap 15.0 with LyX-2.3.0 - and whoosh: > all integrals in mathmode in the LyX-display are gone down a half line > (in the PDF-file it's Ok). Any suggestion? I believe you are reporting the same change reported here: https://www.mail-archive.com/search?l=mid&q=20180131222631.xhlo3g4svsksfi5z%40steph If I remember correctly, part of the change was fixed for 2.3.1 (I'm not sure about this though). Best, Scott signature.asc Description: PGP signature
LyX 2.3.0 - display of int
Hi everybody, first of all want to thank the LyX-community for our wonderful LyX-program! I'm doing my mathematical physics with LyX since the 1.0 versions :-) The last time I read and wrote on lyx-users was in 2012, and now and then I got a message of a resolved minor bug from our hardworking developers. Again thank all of you! Now I upgraded my openSUSE from Leap-42.3 with LyX-2.2.3 to Leap 15.0 with LyX-2.3.0 - and whoosh: all integrals in mathmode in the LyX-display are gone down a half line (in the PDF-file it's Ok). Any suggestion? Thank you very much, bernhard -- Homepage: https://www.mb-schiekel.de/ GnuPG: http://p80.pool.sks-keyservers.net/
