Gustavo Noronha (kov)

This time, I won’t bother too much with release announcement. Xan has done that job for us =D. The good news that preceeded this release by about a week is that now both me and Xan are reviewers for the GTK+ port, so we are able to approve patches, too, along with the already existing reviewers. This may help our port move forward more quickly. If you think your patch is an easy review, or urgent, do catch us on IRC, and let us know, since our port has quite a backlog, and it may be sometime before our scanning of the list catches your entry =).

Thanks to everyone who contributed to this release. I am sure there are many rough edges to sharpen on the new features, so come test and report bugs, (and provide patches if possible =)) please!

Como disse a Lu, estamos nos mudando para o Rio. Está sendo uma experiência interessante, até o momento, e acabou fazendo eu ficar mais perto de 2 pessoas queridas que vieram pra cá antes de mim: minha irmã Laura e meu amigo Gabriel. Isso também significa que eu estou em busca de um apartamento bacana, 2 quartos, pra morar perto do Botafogo, então se alguém souber de algum me diga =D.

Tenho outras boas notícias pra falar sobre (como o fato de eu ter virado reviewer do WebKitGTK+!), mas vou deixar para outros posts!

So, we are still mostly able to keep our release each two weeks promise. For this release we have two big additions to the ’support’ side of the project: translations support, and gtk-doc support. The former is made of the usual makefile rules used by gettext-enabled projects with a rework to fit in the non-recursive build process of WebKitGTK+. The later is not as well integrated yet, so you have to go manually to WebKit/gtk/docs and type make, but not before editing WebKit/gtk/webkit/webkitprivate.cpp and adding a call to g_thread_init(NULL); to webkit_init(). You get the idea, we need help in polishing this one.

As for code, Xan Lopez has been doing some serious work on accessibility support, using ATK. After the a11y hackfest he landed a number of patches moving forward in this direction. It looks like we will be able to meet the requirements for becoming blessed for use by GNOME. We also got a nice printing API, that allows applications to stop using the nasty hack that would send a print() call through javascript. They are also able to control/monitor the print process, or automate it, so that no print dialog is shown, if they wish.

That’s it, come join the party =D. Now, for 1.1.6, I’m hoping Diego finishes the spelling check patch, and it would be awesome to have Jan’s proper error reporting!

Or ‘WebKitGTK+ gains localization support’! Continuing our quest to finish off old bugs, and plug the bigger and more visible missing holes in functionality, a lot of work went into making WebKitGTK+ l10n-capable. This work has been committed today. This means we will now be able to translate things like dialogs, context menus, form elements, and any other string that makes sense to translate and is generated by WebKitGTK+.

Don’t be fooled by the fact that the context menu is talking about spell checking, by the way. This is still something we do not support, and is only there because Epiphany doesn’t override WebKitGTK+’s default context menus. I know that diegoe is working on it, though.