[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Font hinting: suggestion to consistently restrict its usage to UI
From:       Benoit Jacob <jacob.benoit.1 () gmail ! com>
Date:       2009-09-30 4:11:10
Message-ID: d9f848520909292111k35c121d5jf569c12e54ed559e () mail ! gmail ! com
[Download RAW message or body]

2009/9/29 Benoit Jacob <jacob.benoit.1@gmail.com>:
> 2009/9/29 Albert Astals Cid <aacid@kde.org>:
>> You said you are not a font expert yet you claim this is because of font
>> hinting. I see a logic problem here. I'm not a font expert so i really don't
>> know if this is because of hinting or not. And no, you are not the first
>> person to complain yet noone seems to scratch his itch.
>
> I can't say whether font hinting is the _only_ problem, that's true.
> Reading this comment,
>
> http://slangkamp.wordpress.com/2009/09/29/kword-font-rendering/#comment-99
>
> it seems that the ideal solution would involve fixing the Qt backend
> of poppler. What do you think of this comment?
>
> Suppose that I volunteer for trying to do that. Where do I start?

OK, so here's where I am.

- Okular uses poppler-qt4.

- It seems that Poppler-qt4 always  uses a Splash backend, indeed I
found this in poppler-qt4 sources:

	case Document::ArthurBackend:
	// create a splash backend even in case of the Arthur Backend
	case Document::SplashBackend:
	{

- So I started looking at the Splash backend sources and I have
comments. But i'll move this discussion to a poppler mailing list!

Thanks for your patience, and, see ?! I can do more than talking ;)

Benoit
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]