Hi all again,
I'm attaching an updated version of the pango patch. I've rewritten
the pango/xft object creation/cleanup code for good and I've fixed a
couple of subtle bugs (that probably would never manifest themselves,
anyway) that were in the original code.
But most important I've added (optio
Additionnally, pango pulls by force harfbuzz which is a c++
object oriented brain damaged component. That would make dwm hard
dependent... on c++!
However I did a _partial_ port of harfbuzz with C... but hey.
--
Sylvain
On Mon, 30 Dec 2013 16:58:14 -0200
Carlos Pita wrote:
> Of course, that's what I was asking for. I wouldn't use dwm anymore if
> you let me commit this into the mainline :).
If you committed it into mainline I wouldn't be able to guarantee your
personal security.
Cheers
FRIGN
--
FRIGN
> However, I would suggest to add this patch to the optional patches and
> not to mainline due to several reasons:
Of course, that's what I was asking for. I wouldn't use dwm anymore if
you let me commit this into the mainline :).
Regards
--
Carlos
On Mon, 30 Dec 2013 16:11:11 -0200
Carlos Pita wrote:
> (...)
Hi Carlos,
a very interesting patch indeed.
However, I would suggest to add this patch to the optional patches and
not to mainline due to several reasons:
1) Not everyone needs char-by-char font-resolution
2) Pango is an additional
On Mon, Dec 30, 2013 at 1:11 PM, Carlos Pita wrote:
> I find pango a better option than xft because it supports chains of
> fallback fonts out of the box, so you can use -for example- iconic
> fonts as your second family
Amazing. Hadn't realized this (hadn't looked very hard either). Thanks for th
Hi,
I would like to contribute the attached patch against dwm-6.0. It's an
improved version of another one I've found in the web: it better
follows the suckless code conventions and, more important, the
vertical alignment of the rendered text has been corrected.
I find pango a better option than
