On Sun, 4 Apr 2004, Bob Jamison wrote:
Btw, in discussing the roadmap with bulia and mental, we decided to make the Pango adoption be the focus of the next release. Bulia pointed out that we have a number of still-open bugs and several RFE's that are dependent on having that.
Yaay! ;-) After looking at several of the last bugs in libnrtype, and the unicode problems, it seems clear that Pango is the way to go. We are already using Pango indirectly, so why not use it in our code? It seems pointless to write more code for libnrtype when it is apparent that the code is redundant and will be discarded later.
Right, it sounds like the time is ripe for this improvement. :-)
Are we using Pango through some of the other libraries?
What sort of approach do we want to take for doing this changeover? Is the Pango API parallel enough to libnrtype that we could just do function exchanges, or will it require more significant wrapperizing or rewriting? Is this the sort of work we could divide up amongst us all, or is it more of a 1-2 person tiger team type change?
Bryce