Bug Hunting Session
Bug 123234 - Missing characters while exporting to PDF using certain fonts (IM fell from arch user repository)
Summary: Missing characters while exporting to PDF using certain fonts (IM fell from a...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
4.2.0.4 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, filter:pdf, regression
Depends on:
Blocks: PDF-Export
  Show dependency treegraph
 
Reported: 2019-02-07 19:20 UTC by tamius.han
Modified: 2019-04-15 15:59 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of the issue (313.71 KB, image/png)
2019-02-07 19:22 UTC, tamius.han
Details
Sample document (4.64 MB, application/vnd.oasis.opendocument.text)
2019-02-07 19:25 UTC, tamius.han
Details
Sample document gets rendered as this (26.11 KB, application/pdf)
2019-02-07 19:26 UTC, tamius.han
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tamius.han 2019-02-07 19:20:24 UTC
When exporting to PDF, certain special characters (žščć) do not appear in exported PDF.

Said characters are definitely supported by the font, though, as Writer (and every other program for that matter) renders them without a problem. They only go missing when exporting to PDF.
Comment 1 tamius.han 2019-02-07 19:22:11 UTC
Created attachment 148987 [details]
Screenshot of the issue
Comment 2 tamius.han 2019-02-07 19:25:52 UTC
Created attachment 148988 [details]
Sample document
Comment 3 tamius.han 2019-02-07 19:26:51 UTC
Created attachment 148989 [details]
Sample document gets rendered as this
Comment 4 tamius.han 2019-02-07 19:27:50 UTC
IM Fell fonts are provided by otf-im-fell-types package in AUR (arch user repository): https://aur.archlinux.org/packages/otf-im-fell-types/
Comment 5 Durgapriyanka 2019-02-08 16:16:41 UTC
Thank you for reporting the bug. I can confirm the bug present in

Version: 6.3.0.0.alpha0+
Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
Comment 6 Xisco Faulí 2019-02-12 17:38:15 UTC
Also reproduced in

Version: 5.2.0.0.alpha0+
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.15; Render: default; 

Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e

but not in

Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Comment 7 Buovjaga 2019-02-12 19:59:28 UTC
(In reply to Xisco Faulí from comment #6)
> but not in
> 
> Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)

Weird: I repro in oldest of 41max, oldest of 43all (+ last36onmaster).
Comment 8 Buovjaga 2019-04-15 15:59:24 UTC
Repro in oldest commit of win32-4.3