On 3 May 2002, at 22:37, Sven Neumann wrote:

we'd like to do a 1.2.4 release soon. There are a few things you can do to help us with this task:

How soon is soon (ballpark figure)?

On 3 May 2002, at 23:00, Sven Neumann wrote:

"Branko Collin" writes:

we'd like to do a 1.2.4 release soon. There are a few things you can do to help us with this task:

How soon is soon (ballpark figure)?

as soon as possible. Actually Yosh wanted to it a while ago but the number of bugs I've put on the 1.2.4 milestone delayed it until now.

Ah, OK. I cannot squeeze the translation work I was planning to do (planning to ask someone else to do, to be precise) in 'as soon as possible'. That's why I asked. :-)

fre 2002-05-03 klockan 22.37 skrev Sven Neumann:

- If you are a translator or would like to help with translations, check http://sven.gimp.org/1.2/i18n.html to see if your language needs work.

Hmm, if you want to make sure that all translators get this info, then it perhaps should be sent to gnome-i18n@gnome.org too.

Cheers, Christian

On Fri, May 03, 2002 at 11:12:12PM +0200, Sven Neumann wrote:

I didn't say how soon it will be possible. This depends on a lot of things, mostly http://bugs.gimp.org/stable-milestone/.

#77283 was actually fixed for 1.2.x already, but I've just done the extra stuff to mark it FIXED in both trees. Six to go :)

Nick.

Correct. My error. Sorry.

Christian

lör 2002-05-04 klockan 01.57 skrev Sven Neumann:

Hmm, if you want to make sure that all translators get this info, then it perhaps should be sent to gnome-i18n@gnome.org too.

IIRC, I've sent a mail announcing the 1.2.4 release to gnome-i18n list a few weeks ago.

On Fri, May 03, 2002 at 10:37:37PM +0200, Sven Neumann wrote:

- Look through the list of open bugs for the 1.2.4 milestone (a quick way to get there is http://bugs.gimp.org/stable-milestone/). Some of these bugs need comments. Of course patches to fix them are highly appreciated.

I'd like to comment on bug #79754. Some time ago I built a GIMP 1.2.2 RPM for SUSE. There was a gimp-fontset.patch included:

--- app/text_tool.c.orig Sat Jan 27 16:29:16 2001 +++ app/text_tool.c Sat Jan 27 16:31:50 2001 @@ -607,7 +607,7 @@
gdk_error_warnings = 0;
gdk_error_code = 0;
#ifndef GDK_WINDOWING_WIN32
- font = gdk_font_load (fontname);
+ font = gdk_fontset_load (fontname); if (!font)
{
g_message (_("Font '%s' not found."), fontname); @@ -838,7 +838,7 @@
gdk_error_warnings = 0;
gdk_error_code = 0;
#ifndef GDK_WINDOWING_WIN32
- font = gdk_font_load (fontname);
+ font = gdk_fontset_load (fontname); if (!font)
return FALSE;

The problem was: It did not work. If I entered umlauts into the (dynamic) text tool, the text got truncated there (although they showed up fine in the preview). (I used the "C" locale, not de_DE or something).

I talked a bit with Daniel Egger but we didn't come to a clear solution. If I find the time, I'll check out CVS today and give check whether the problem persists.

I tracked down the problem to gdk_measure_text which called XmbTextExtens which in turn returned the wrong width (truncated at first umlaut).

I'm just telling that story to point out that fontset support might be a hairy issue and hard to get right.

Bye, Tino.

Do you want to do anything about the print software for 1.2.4? We've just released our 4.2.1 release, which is much better than the 4.0.5 that you're using.

From: Sven Neumann
Date: 04 May 2002 13:54:06 +0200

Robert L Krawitz writes:

> Do you want to do anything about the print software for 1.2.4? We've > just released our 4.2.1 release, which is much better than the 4.0.5 > that you're using.

actually we wanted to integrate gimp-print-4.2 into gimp-1.3 first. Then, with some experience, do the same change for 1.2. Until now we haven't come around to do so. Perhaps we should indeed consider to update gimp-print in the stable branch.

How do you suggest should we proceed? Should we depend on libgimpprint or would it be a good idea to ship gimp-1.2.4 with the whole thing?

I'd much rather you link to libgimpprint, and I thought that that's what we had decided. The 4.2.1 version of the plugin, which is presumably what you'd use, had no changes whatsoever over 4.2.0; that code base is rock stable. 4.2.2 will offer a useful quality upgrade (a new dither algorithm) for people printing photos, but that will be a library-only upgrade. 4.2.3 may require a plugin upgrade to get some new functionality that we're discussing, but the 4.2.0 plugin will work with 4.2.3, it just won't have that new functionality.

One option might be to distribute Gimp-print as an extra (mirror the distribution of the latest 4.2 release).

From: Sven Neumann
Date: 06 May 2002 15:48:27 +0200

Robert L Krawitz writes:

> I'd much rather you link to libgimpprint, and I thought that that's > what we had decided.

so far we've only considered that for gimp-1.3, but the more I think about it the more I have to agree that we should do it for gimp-1.2.4. The only problem I see is that we will force packagers to change the package dependencies. I've opened a bug report for this issue (http://bugzilla.gnome.org/show_bug.cgi?id=80941). If you'd like to comment on this subject, please attach your comment there.

OK.