Description: When i open a file in libreoffice draw, some of the letters look awkward duplicated Steps to Reproduce: 1.Open the file in firefox 2.Open the file in libreoffice draw Actual Results: The file renders incorrectly in libreoffice draw Expected Results: File should render as it does on firefox nightly Reproducible: Always User Profile Reset: Yes Additional Info: Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Created attachment 193196 [details] File rendered by libreoffice draw
Created attachment 193197 [details] File rendered by firefox nightly
Created attachment 193198 [details] PDF in question
Confirm with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2887ffbf240aa70330cb50bf810170cf9c896405 CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Jumbo Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Hmm, so how does the PDF look if you Insert as image, using the pdfium project lib based filter? We'll read the PDF, using poppler and write to a Cairo surface then interpreting the PDF into a series of ODF draw objects. If fonts are missing/mislabeled within the PDF, a font substitution occurs in creating the draw text box objects. We don't necessarily use an embedded font subset. Also, we depend on poppler to split the text spans--in this case looks like we're getting a "double struck" affect bcz of some word bound issue. Letters are being repeated between words of the text spans and then not lining up when rendered as draw text boxes. If you need fidelity to the source PDF, insert (currently need to split pages of the PDF) as image. If you just need the content of the PDF to work with as ODF draw objects, with some loss of layout, then open the PDF. LibreOffice is not a PDF editor.
Same issue as in bug 101155. *** This bug has been marked as a duplicate of bug 101155 ***