bohoomil / fontconfig-ultimate

freetype2-infinality run-time settings => infinality compatible fontconfig => infinality-bundle
453 stars 38 forks source link

Font kerning with PDF created with Microsoft Office 2013 #68

Open orschiro opened 9 years ago

orschiro commented 9 years ago

Hi @bohoomil ,

I encounter a font kerning issue with a PDF that has been created using Microsoft Office 2013. I use Evince to display the PDF which looks as follows:

screenshot

Information about the PDF (download):

pdfinfo transition\ training\ day\ 2015_Programme.pdf
Author:         Marijke de Pous
Creator:        Microsoft® Word 2013
Producer:       Microsoft® Word 2013
CreationDate:   Thu Jan  8 11:16:22 2015
ModDate:        Thu Jan  8 11:16:22 2015
Tagged:         yes
UserProperties: no
Suspects:       no
Form:           none
JavaScript:     no
Pages:          1
Encrypted:      no
Page size:      594.96 x 842.04 pts (A4)
Page rot:       0
File size:      84394 bytes
Optimized:      no
PDF version:    1.5

Used version of fontconfig-ultimate:

~ ❯ pkg-grep infina
cairo-infinality-ultimate 1.14.0-2
fontconfig-infinality-ultimate 2.11.1-24
freetype2-infinality-ultimate 2.5.5-1
lib32-cairo-infinality-ultimate 1.14.0-2
lib32-fontconfig-infinality-ultimate 2.11.1-3
lib32-freetype2-infinality-ultimate 2.5.5-1

Can you confirm this issue?

Thankfully,

Robert

bohoomil commented 9 years ago

Yes, but this has nothing to do with Infinality, freetype2 and the like: there are neither embedded fonts in the document, nor any other fonts (in ttf/otf/t1/… format) that pdffonts could identify (you could use Evince -> Properties… -> Fonts to check this out). It can't be even converted to an editable text document (in any format, be it doc, rtf, txt). The content must have been written as an image with anti-aliasing information Evince can't read (Zathura can, though). All in all: not a font related issue.

orschiro commented 9 years ago

there are neither embedded fonts in the document, nor any other fonts (in ttf/otf/t1/… format) that

Thanks for mentioning! I didn't think about that possibility.

The content must have been written as an image with anti-aliasing information Evince can't read (Zathura can, though)

Tested Zathura and can confirm that it properly displays the PDF. I will use it for now whenever Evince fails to show a PDF properly.

All in all: not a font related issue.

Apologise for bothering with a non-related issue...

Robert