https://bugs.documentfoundation.org/show_bug.cgi?id=165396
--- Comment #10 from Eyal Rozenberg <[email protected]> --- (In reply to V Stuart Foote from comment #8) > But ideally it doesn't even come from a fallback, instead we should try > harder to use the embedded subset font glyphs recorded to Font directories > in the PDF. That is a separate issue. Naturally, if one uses glyphs with the same metrics, one gets the same dimensions. This bug is about when that does not happen, for any reason. The reason may be us misidentifying the font, but it might also be that it's a Type-1 font, which we don't support on principle (as I have recently been told). > If we were able to better use the subset fonts when filter imported (poppler > -> cairo object) then only additional edits/changes to the draw text shapes > might need fallback font. > > But suspect that would be a lot of dev effort for minimal returns > ... > the current filter import of > PDF text objects to runs within Draw text shapes is really not too bad The returns would be _massive_, not minimal. It is very often the difference between imported PDFs looking like disarrayed junk and properly-laid-out text. Just think of the case of justified paragraphs of text; you can look at the same document as an example. Right now, we mess them up. Which is exactly "too bad". > LibreOffice is not a PDF editor I do believe that discussion is settled: * https://www.youtube.com/watch?v=98yX0JRHFbQ * https://events.documentfoundation.org/libreoffice-conference-2023/talk/JDSEVU/ plus, a "PDF editor" as you would define it could not even have this bug, but the only thing it would do is stick to the exact structure of the PDF. -- You are receiving this mail because: You are the assignee for the bug.
