View Single Post
Posts: 192 | Thanked: 5 times | Joined on Nov 2005 @ Eugene, Oregon
#10
I'd like to suggest that the people maintaining and updating Maemo need to be a little more agressive with giving us updates. This is especially important for allowing a large number of X apps that were written to use the X core fonts. The subset of X that's implemented on the 770 breaks (i.e., drops compatibility with) the X core fonts we are required to upgrade our X apps from the X core fonts to the Freetype fonts supported by the FreeType2, fontconfig and Xft. In a world where you (i.e., the people behind the Maemo project) take something away (X core font compatibility) you need to give something in return (i.e., a tutorial on how to replace X core fonts with Freetype2 fonts and a frequent release schedule of all of the components necessary to write X apps using the FreeType 2 fonts, the Freetype library, the fontconfig library and the Xft library).

There are a mountain of fixes to things that are broken in a more more recent version of the FreeType project with a HUGE amount of fixes, a devel release of the Fontconfig project with a HUGE amount of fixes, the current version (since a year ago, already) of the Xft library.

In the world of UNIX, Linux, BSD & X it has long been a rule that when you release something new and better that it doesn't break what people are using. Microsoft may do that but that's not the way it's done over on this side of the valley. To repeat, Maemo developers - if you're going to 'break' something (core X font support) then you need to give something back, or else a lot of applications are no longer going to work. There's frustration all around that the apps for the 770 aren't appearing fast enough and that the old apps no longer work. How about updating the Maemo packages in at least these three areas? There is a LOT about these packages that is broken until you do this and I am personally really frustrated that unless and until you all make the effort to upgrade these packages then I am wasting good money to try to make my software work on top of a small mountain of broken library code that, even though it's been fixed, you guys haven't bothered to upgrade to it.