<?xml version="1.0" ?>

<kc>

<title>Gimp Traffic</title>

<author contact="mailto:alexh@dowco.com">Alex Harford</author>

<issue num="20" date="06 May 2000 00:00:00 -0800" />

<intro>

<p>Kernel Cousin Gimp is back after a brief hiatus.</p>

<p>Yosh announced another 1.2pre beta.  It can be found at <a
href="ftp://ftp.gimp.org/pub/gimp/v1.1/v1.1.21/">ftp://ftp.gimp.org/pub/gimp/v1.1/v1.1.21/</a>.</p>

<stats posts="61" size="201" contrib="27" multiples="14" lastweek="2">

<person posts="10" size="47" who="quinet@gamers.org (Raphael Quinet)" />
<person posts="6" size="23" who="Marc Lehmann &lt;pcg@goof.com&gt;" />
<person posts="5" size="17" who="Sven Neumann &lt;neumanns@uni-duesseldorf.de&gt;" />
<person posts="4" size="8" who="Jon Winters &lt;winters@obscurasite.com&gt;" />
<person posts="3" size="9" who="Michael J. Hammel &lt;mjhammel@graphics-muse.org&gt;" />
<person posts="3" size="8" who="Tuomas Kuosmanen &lt;tigert@gimp.org&gt;" />
</stats>

</intro>

<section
  title="Export Behaviour of the PNM plugin"
  subject="pnm plugin"
  archive=""
  posts="6"
  startdate="02 May 2000 00:00:00 -0800"
  enddate="03 May 2000 00:00:00 -0800"
>

<mention>Nick Lamb</mention>
<mention></mention>
<mention>Martin Weber</mention>
<mention>Marc Lehmann</mention>

<p>DrMartin.Weber wrote the list to say that the <quote who="Dr Martin Weber">he
pnm plugin can read the pnm, ppm, pbm and pgm format, but it cannot save to
ppm, pbm and pgm.</quote></p>

<p>Several people were confused, because their Gimp seemed to produce the correct
results.  Marc Lehmann wrote that he was unable to create pgm or pbm files.
When he tried to create a pgm, the file was actually a ppm.  Kevin Turner
replied:</p>

<quote who="Kevin Turner">

<p>that's not what "file" thinks about the attached files:</p>

<p>
<ul>

<li>pudding.pgm:  PGM image text</li>
<li>pudding2.pgm: PGM "rawbits" image data</li>

</ul>
</p>

</quote>

<p>Marc acheived his result by taking a gif, converting to greyscale, and
saving it. This resulted in a ppm. Nick Lamb wrote that his Gimp seemed to
create the appropriate files with this method.</p>

<p>There were no more messages in this thread, hopefully we will see a fix if it
was needed.</p>

</section>

<section
  title="Glib and GTK+ requirements"
  subject="Gimp now requires Glib 1.2.7?"
  archive=""
  posts="2"
  startdate="02 May 2000 00:00:00 -0800"
  enddate="02 May 2000 00:00:00 -0800"
>

<mention></mention>

<p>Pierre Rochefort reported that <quote who="Pierre Rochefort">I got the
sources out of CVS and tried to compile. I have Glib 1.2.6 installed and it
used to work fine (up until this morning). Has the requirement changed in
regards to Glib?</quote></p>

<p>Raphael Quinet replied that <quote who="Raphael Quinet">the current version
of the Gimp requires glib-1.2.7 and gtk+-1.2.7. It is very likely that the
final release will require gtk+-1.2.8 (not released yet) because some dnd
bugs have been fixed recently in gtk.</quote></p>

</section>

<section
  title="Gimp 1.1.21 Build Fails on Non-Linux Systems"
  subject="Gimp 1.1.21 build fails under Solaris because of Linuxisms"
  archive=""
  posts="3"
  startdate="02 May 2000 00:00:00 -0800"
  enddate="02 May 2000 00:00:00 -0800"
>

<mention></mention>

<p>Raphael Quinet found a problem with the latest version of the Gimp:</p>

<quote who="Raphael Quinet">

<p>I just downloaded 1.1.21 and I tried to compile
it under Solaris. The build breaks early while compiling libgimp, with the
following error:</p>

<pre>
gimp.c: In function `gimp_main':
gimp.c:202: `SA_NOMASK' undeclared (first use in this function)
gimp.c:202: (Each undeclared identifier is reported only once
gimp.c:202: for each function it appears in.)
make[2]: *** [gimp.lo] Error 1
make[2]: Leaving directory `/Local/build/gimp-1.1.21/libgimp'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/Local/build/gimp-1.1.21'
make: *** [all-recursive-am] Error 2
</pre>

</quote>

<p>He continued, saying that the call to "SA_NOMASK" was a historical Linux
call, and should really be SA_NODEFER. He provided a patch, solving the
problem for Solaris and likely most other Unixes.</p>

<p>Michael Natterer was apologetic.  <quote who="Michael Natterer">I'm about to
commit this. It seems I made Gimp unworkable for all systems except Linux...
argh, 1 day before a release.</quote></p>

<p>There were no more messages in this thread.</p>

</section>

<section
  title="JPG Plugin Crashing the Gimp"
  subject="1.1.21 crashing trying to save a .jpg"
  archive=""
  posts="6"
  startdate="03 May 2000 00:00:00 -0800"
  enddate="03 May 2000 00:00:00 -0800"
>

<mention></mention>

Jon Winters had some problems with the JPEG plugin.

<quote who="Jon Winters">

<p>Tonight I opened an image, did a re-size, then went to "save as" a
.jpg. When I move the "Quality" slider Gimp crashes. :-\</p>

<p>Is it my system or the Gimp?</p>

</quote>

<p>Several people noted that there were problems with the Preview code when the
Quality was set very low, but this was not the case.</p>

<p>Michael Natterer discovered that it was the Gimp causing the crashes.
<quote who="Michael Natterer">layers_dialog_idle_set_layer_focus() was the
problem.  cvs Gimp should work nicely.</quote></p>

</section>

<section
  title="Changes To gimp_tips.txt"
  subject="Proposal for new gimp_tips.txt"
  archive=""
  posts="6"
  startdate="04 May 2000 00:00:00 -0800"
  enddate="06 May 2000 00:00:00 -0800"
>

<mention></mention>
<mention>Raphael Quinet</mention>

<p>Raphael Quinet posted an updated version of the gimp_tips.txt file.  He
asked if there were any suggestions on improving his work. Various people
had some small suggestions. Garry R. Osgood suggested changing the tip about
the background layer to <quote who="Garry R. Osgood">The "Background" layer
lacks transparency. This is why it does not accept layer masks and remains
"anchored" at the bottom of the layer stack, a backdrop for transparent
layers. But you may add transparency to the Background by right-clicking in
the layers dialog and selecting Add Alpha Channel."</quote></p>

</section>

</kc>
