Bug 691838 - Mupdf doesn't show the character "u"
Summary: Mupdf doesn't show the character "u"
Status: RESOLVED FIXED
Alias: None
Product: MuPDF
Classification: Unclassified
Component: mupdf (show other bugs)
Version: unspecified
Hardware: PC Linux
: P4 normal
Assignee: Tor Andersson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-15 16:52 UTC by Marco Pessotto
Modified: 2011-02-02 15:53 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---


Attachments
the letter "u" is not shown in the second row (15.26 KB, application/pdf)
2010-12-15 16:52 UTC, Marco Pessotto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Pessotto 2010-12-15 16:52:57 UTC
Created attachment 7029 [details]
the letter "u" is not shown in the second row

In the attached pdf, created with ConTeXt and luatex 0.65 and the fonts latin modern, the letter "u" of the bold variant is not shown. However, all the other viewers (xpdf, gv, okular, evince, acroreader) don't complain.

Probably it's a font related issue, because the problem shows up only with the latin modern font, but I have to start somewhere, so I'm reporting this to you first and in case I'll forward to other components involved (luatex and lmodern). 

I'm using the binaries downloaded from http://mupdf.com/download/mupdf-0.7-linux-i386.tar.gz

Thanks for MuPDF. It rocks.

Just for the record, the pdf originates from this ConTeXt code, created with luatex 0.65

\starttext
abcdefghjkilmnopqrstuvwxyz

\bf abcdefghjkilmnopqrstuvwxyz

\it abcdefghjkilmnopqrstuvwxyz
\stoptext
Comment 1 Ken Sharp 2010-12-15 17:02:26 UTC
FWIW this doesn't happen with MuPDF 0.6, nor an unknown version from December 2009. Looks like it was introduced with 0.7.
Comment 2 Tor Andersson 2010-12-15 17:55:16 UTC
I get this warning from freetype with the binary on the download page:

warning: freetype load glyph (gid 109): broken file

Same with both the linux and windows versions.

A fresh compile of mupdf 0.7 does not exhibit any problems.

It could be a problem with the version of freetype used in
the 0.7 binary release. There were a few CFF related bugs in
that version of freetype.
Comment 3 Marco Pessotto 2010-12-15 18:37:04 UTC
I've recompiled mupdf and the problem indeed goes away. Thanks for your attention. AFAIC you can close this bug.