Created attachment 152014 [details]
this is the odt format. reproduce the problem using the file> export as> export as pdf
Hello, I think there is a bug in libreoffice with persian language. I'm trying to write a technical text in libreoffice in farsi(persian) language. whenever i try to have inline formulas, like lambda/4 or L_r it is shown very poorly in final pdf. (it is not shown correctly). I don't use any extensions but the default formula editor of libreoffice and I export it as pdf by libreoffice default. could any developer please see this? I don't have this problem in open office but it exists in libreoffice. I don't have this problem with english language either. it just happens when I try to type persian. the problem doesnt exist in the odt format. just when I try to convert it to pdf. (which is important btw)
as I said the .odt format doesn't have problem. the PDF format is corrupt. to reproduce do this: File > Export as > Export as PDF.
Created attachment 152026 [details]
PDF export output LO 18.104.22.168 on Linux
Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac
CPU threads: 4; OS: Linux 4.9; UI render: default; VCL: gtk3;
Locale: he-IL (en_IL); UI-Language: en-US
It seems like the 'L' is horizontally shifted to the left of where it's supposed to appear, beyond some kind of rectangle boundary so that its left part is not rendered.
Created attachment 152027 [details]
Document whose PDF export exhibits the bug
This occurs both with Hebrew and with Farsi, and both when the paragraph is LTR and RTL (although the "run" containing the inline equation is RTL where the bug manifests).
Created attachment 152028 [details]
PDF export output of bug-152773 using LO 22.214.171.124 on Linux
This is the output we get.
Seeing this on AMD64, while original author sees this on IA32. Too bad the platform drop-down isn't multiple-choice...
This Bug is not even touched after I reported it in the new version of LO, Please Fix this.
Regression introduced by https://cgit.freedesktop.org/libreoffice/core/commit/?id=302af8c2da58719844d22483b65a9fe5b3674684, which is the same as in bug
*** This bug has been marked as a duplicate of bug 115967 ***