https://bugs.documentfoundation.org/show_bug.cgi?id=155640

⁨خالد حسني⁩ <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |NOTOURBUG
             Status|REOPENED                    |RESOLVED

--- Comment #8 from ⁨خالد حسني⁩ <[email protected]> ---
(In reply to Jon Ten from comment #6)
> thanks
> So are you are saying that the pdf writer eg Firefox is creating mappings to
> ligature characters (glyphs) and that a pdf reader will simply render them
> but Draw does not, as it wants to show single characters, so maps them to
> U+FFFD?

PDF has mapping from glyphs to characters so that text extraction (searching,
copying) work. When importing PDF as editable text we use this mapping, we
can’t use glyphs. The mapping is faulty in this PDF which is the responsibility
of PDF producer.


> If this is so why not convert back from the glyph code to the 2 characters
> represented as presumably they are identifiable (see
> https://www.unicode.org/charts/PDF/UFB00.pdf)?

There is no such thing as glyph code, fonts contain glyphs in arbitrary order
and have mapping from Unicode code points to glyph indices.

> OR are you saying that the pdf just has U+FFFD for ligatures. If so how does
> the pdf reader access the glyphs? And if it can why can Draw not do this? 

PDF works with glyph indices, so to render the PDF a PDF viewer simply renders
the specified glyph from the font embedded in the PDF.

PDF also provides a reverse map from glyph indices to Unicode code points, to
be used for text extraction. If the mapping is faulty, there is no way to
retrieve the textual content. You can try coping these words from any PDF
reader and you will get the same replacement character because this what the
PDF indicates as the textual representation of these glyphs.

If you want a faithful rendering of the PDF, insert it as image. If you want
faithful editing of PDF (not importing it as text), you should try a dedicated
PDF editor.

Please do not re-open, if there still a LibreOffice issue after discussion, we
will re-open the issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to