I think that restoring generation of a valid POT file needs to be a top priority goal for WebKitGTk+. It has been two years since a valid POT was generated, and that should not be considered acceptable. This is having a significant impact on downstream projects and users in other languages.
This is not going to be fixed by just filing a bug against intltool. cjl On Tue, Oct 2, 2012 at 2:09 PM, Martin Robinson <[email protected]> wrote: > Hi al! We recently released WebKitGTK+ 1.10, and as I understand it, > the next release will be 2.0. With that in mind, I think it's time to > start planning for the release. Here are some things that I've been > thinking about: > > * Drop support for GTK+ 2. By the time we release WebKitGTK+ 2.x, GTK+ > 3 will have been released for 2 years. > > * Depending on whether or not GStreamer 1.0 is released, drop support > for versions before 1.0. > > * Stop depending on unstable libsoup APIs. The suggestion here is to > simply work to make unstable libsoup APIs stable. > > * After the WebKitGTK+ 2.0, freeze all dependencies until WebKitGTK+ > 3.x. This is useful, because distributions can ship newer versions of > WebKitGTK+ in older releases. This eliminates the pain of maintaining > a stable WebKit branch for years, which is likely next to impossible. > > --Martin > _______________________________________________ > webkit-gtk mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo/webkit-gtk _______________________________________________ webkit-gtk mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-gtk
