[Libreoffice-ux-advise] [Bug 85295] FILEOPEN: Import/preserve embedded fonts from pdf

2022-02-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=85295

V Stuart Foote  changed:

   What|Removed |Added

 Status|REOPENED|UNCONFIRMED
 Ever confirmed|1   |0
   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org

--- Comment #12 from V Stuart Foote  ---
(In reply to Timur from comment #11)
> I don't know why this was closed. Bug (unfortunelly) may remain open for
> years/decades but I don't support WontFix. 
> I see often similar reports "PDF doesn't look good", where submitters are
> surely not satisfied with any explanation that keeps wrong look. 
> 
> Some more examples are attachment 165948 [details] from bug 137128 where
> AvenirLTStd-Heavy is in PDF but AvenirLTStd in LO and attachment 178037
> [details] from bug 147178 where ArialMT is in PDF but Arial in LO.

Michael S. in comment 9 is correct. Unless the creator of the PDF intentionally
and legally embeds the entire font, only a subset of the actual glyphs used in
the document are available in the PDF.  That is the vast majority of PDFs that
LO users would be importing or inserting.

While possible to parse and fully load a fully embedded font, it would be
unreliable and error prone as there is no real standard for doing so across the
many PDF generators.

Insertion to canvas via pdfium libs is a non-issue, leaving import "opening"
into a ODG drawing where internal PDF font naming is notoriously fickle--all
meaning that what we do now on import is appropriate. And for the few PDF that
actually embed a full font, we are safe to ignore the practice.

LibreOffice is NOT a PDF editor, and we have adjusted the PDF form handling to
use only the "builtin" PDF reader fonts [1] on export.  We have no obligation
to  do more with font handling for what is intended to be a non-editable
presentation format--doing more only disappoints users who discover neither
their imported nor their exported PDF retain fidelity to the original source
font.

IMHO => WF was and remains the correct resolution to avoid unreasonable user
expectation of what is a low frequency usage. Not worth any dev effort.

=-ref-=
[1] for bug 50879 - https://gerrit.libreoffice.org/c/core/+/99032

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 85295] FILEOPEN: Import/preserve embedded fonts from pdf

2022-02-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=85295

Timur  changed:

   What|Removed |Added

 CC||j...@vansomeren.co.uk

--- Comment #13 from Timur  ---
*** Bug 147178 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Libreoffice-ux-advise] [Bug 85295] FILEOPEN: Import/preserve embedded fonts from pdf

2022-02-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=85295

Heiko Tietze  changed:

   What|Removed |Added

   Keywords|needsUXEval |
 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #14 from Heiko Tietze  ---
AFAIU, we do not use the few glyphs stored in the PDF because it's not a
complete font and editing wont be possible. Makes sense to me. If the PDF
contains the whole font we should use it, on the other hand.

I suggest to show an infobar if a font was not shipped with the PDF. Something
like "Fonts in this document have been replaced. For full editing capabilities
please ask the original author to embed the whole font." 
(Me concerns the list of bugs in c0 regarding the issue.)

And we should provide options to export the font because it's our mission to
make documents readable cross-platform and cross-applications. According [1]
the open font spec knows: No embedding, Print and preview, Editable,
Installable. And MSO allows to save fonts respectively.

[1]
https://www.microsoft.com/en-us/microsoft-365/blog/2015/07/06/document-font-embedding-demystified/

-- 
You are receiving this mail because:
You are on the CC list for the bug.