Bug 3429 - [kpdf] fontconfig fixes from kpdf
Summary: [kpdf] fontconfig fixes from kpdf
Status: RESOLVED FIXED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Kristian Høgsberg
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 3427
  Show dependency treegraph
 
Reported: 2005-05-30 03:35 UTC by Kristian Høgsberg
Modified: 2005-07-28 15:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
fontconfig code from kpdf (7.47 KB, patch)
2005-05-30 03:38 UTC, Kristian Høgsberg
Details | Splinter Review

Description Kristian Høgsberg 2005-05-30 03:35:01 UTC
(from Albert:)

Hi, here comes our fontconfig patch, i see poppler has inherited from evince a 
fontconfig function that xpdf does not have, but i think ours is better, i 
explain the reasons:

 - The fontconfig code in poppler right now is not able to use winddings font 
i have installed in my system to properly render · (a dot) in 
http://usuarios.lycos.es/tsdgeos/test.pdf and instead it renders Ÿ (Y with 
dieresis) while our code does.

 - FcNameParse does not works with pdf font names, we have a custom parsing 
function. 
As a example use the attached test program, compiling normally and then 
compiling with option -D WEIRD_FUN then do
./fonttest fontname 
and last line says the font that will be used, using FcNameParse and 
CourierNew,Bold (font name present in the above pdf) i get
File: /usr/share/fonts/ttf/vera/Vera.ttf
but using -D WEIRD_FUN i get
File: /usr/share/fonts/ttf/vera/VeraBd.ttf
that is obviously better.

If you need winddings.ttf grab it at
http://usuarios.lycos.es/tsdgeos/wingding.ttf

Albert
Comment 1 Kristian Høgsberg 2005-05-30 03:38:50 UTC
Created attachment 2793 [details] [review]
fontconfig code from kpdf
Comment 2 Kristian Høgsberg 2005-05-30 03:39:23 UTC
Jeff suggests using the PDF font descriptor dicts when available.
Comment 3 Kristian Høgsberg 2005-07-30 01:23:33 UTC
This is in CVS now.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.