Sorry to jump very late in this threat, only saw it today.
I don't use LyX for math, so that part I don't know anything about, but
I use openSUSE and maintain LyX there, so I am interested to get this right.
By default I disable all texlive fonts for the UI by linking the
58-texlive-* config files in /etc/fonts/avail.d to /etc/fonts/conf.d (on
openSUSE Tumbleweed the first directory is now in
/usr/share/fontconfig/avail.d). As far as I can see the esint fonts are
working nicely in LyX. Enabling those fonts by removing those
58-texlive-* files again by removing them from /etc/fonts/conf.d has the
result that I see what Bernhart saw, I think.
If the cause is how LyX is packaged in openSUSE, please file a bug in
the openSUSE bugzilla. If it's mentioned here, the chance is I'll miss it.
BTW: the LyX fonts are packaged in /usr/share/lyx/fonts and not linked
in any way to /usr/share/fonts.
Thanks,
Cor
Op 25-08-2020 om 11:22 schreef M.B. Schiekel:
Am 24.08.20 um 18:02 schrieb Jean-Marc Lasgouttes:
After a longer discussion here I found, that the cause of this problem
was the interaction of LyX with QT5-Qt-5.9.4. Then I compiled LyX with
QT4 and this workaround was fine for me.
Now with LyX 2.3.5.2 there is the same problem with QT5-5.12.7 and again
...
Unfortunately, it is not my failing memory that prevented from fixing
the bug. Since I cannot reproduce it, it is difficult for me to do
something about it.
Let's start by a shot in the dark: does it make a difference to set the
environment variable QT_HARFBUZZ to "old" ?
Even if it does, I suspect it will not be enough for a long-term fix.
Did I understand correctly that you can compile LyX? Does it mean that
you can try a patch too? A possibility is that Qt does not like (ass
Pavel noted) to have a font with a character at position 1 (which is
where \int lives in esint10 font). We would have to duplicate the
character somewhere else in the font.
...
Hi Jean-Marc,
thank you for your kind reply. This morning I tried to compile LyX
2.3.5.2 with your suggested environment-variable
export QT_HARFBUZZ=old ,
and yes, it works, all integral-signs are Ok.
Did I understand correctly that you can compile LyX? Does it mean that
you can try a patch too?
Well, I can compile LyX. Concerning an patch I can try - depends if this
patch will automatically change the sources, because I don't want to
make changes in the sources by hand :-)
So far, so good. And many thanks for all your wonderful LyX-work!
bernhard
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
