[Gimp-user] OT GTK/SuSE/Gimp question

2005-06-04 Thread Eric P
This is probably way off topic for this ML (so please ignore if you 
want), but it started w/the Gimp, so what hell...


I compiled new versions of atk/glib2/gtk2/pango in order to start 
checking out the 2.3 series of the Gimp.


Everything went fine.  I removed the old atk/glib2/gtk2/pango RPMs along 
w/their respected devel RPMs.  I then make installed (via checkinstall) 
all the new GTK and friends, so I now have lovely round RPMs of each 
package installed.  Now I compiled Gimp 2.3.0, and, yet again, all went 
well.


However, when I run YAST now, it insists on reinstalling the old GTK 
(and friends) devel RPMs.  Of course, I don't want to do that as the new 
header files are already installed.  The RPMs I created (with 
checkinstall) contain the header files.  The RPM packages just weren't 
broken out into 2 RPMs per package (i.e., binary RPM and devel RPM) like 
SuSE and other distros tend to do.


Any tips on this dilemma?

Thanks for reading,
Eric P

Ps. I'm running SuSE 9.2 pro
___
Gimp-user mailing list
Gimp-user@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] OT GTK/SuSE/Gimp question

2005-06-04 Thread BandiPat
On Saturday 04 June 2005 11:44 am, Eric P wrote:
 This is probably way off topic for this ML (so please ignore if you
 want), but it started w/the Gimp, so what hell...

 I compiled new versions of atk/glib2/gtk2/pango in order to start
 checking out the 2.3 series of the Gimp.

 Everything went fine.  I removed the old atk/glib2/gtk2/pango RPMs
 along w/their respected devel RPMs.  I then make installed (via
 checkinstall) all the new GTK and friends, so I now have lovely round
 RPMs of each package installed.  Now I compiled Gimp 2.3.0, and, yet
 again, all went well.

 However, when I run YAST now, it insists on reinstalling the old GTK
 (and friends) devel RPMs.  Of course, I don't want to do that as the
 new header files are already installed.  The RPMs I created (with
 checkinstall) contain the header files.  The RPM packages just
 weren't broken out into 2 RPMs per package (i.e., binary RPM and
 devel RPM) like SuSE and other distros tend to do.

 Any tips on this dilemma?

 Thanks for reading,
 Eric P

 Ps. I'm running SuSE 9.2 pro
=

Eric,
Did you get any conflicts or dependencies when trying to install the new 
rpms?  I would guess you have a mismatch of sorts and that is why YaST2 
wants to put things right.  You can go into YaST2 software module and 
select those files you installed to set them as protected, so YaST2 
doesn't complain continually.  If you have been running YOU to stay 
updated, your glib2 files  pango files should be adequate to run Gimp 
newer versions, mine is.  I don't have any trouble compiling the newer 
Gimp builds either.  Here are presently installed 9.2 versions:
glib2-devel-2.6.3-9
glib2-2.6.3-9
glib2-doc-2.6.3-9

pango-devel-1.4.1-3
pango-1.4.1-3
pango-doc-1.4.1-3

regards,
Patrick

-- 
--- KMail v1.8 --- SuSE Linux Pro v9.2 ---
  Registered Linux User #225206
There's no problem so awful that you can't
add some guilt to it and make it even worse!  ...Calvin  Hobbes
___
Gimp-user mailing list
Gimp-user@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] Gimp no longer works !

2005-06-04 Thread Karine Delvare
On Sat, 04 Jun 2005 18:42:55 +0200
Olivier Lecarme [EMAIL PROTECTED] wrote:

 By the way, what is the use of the Device Status dialog?

The Device Status dialog shows you every device that can be used as a pointer 
in The GIMP, along with what tool this device is using (and also : foreground 
and background colors, brush, pattern, and gradient), which means all these 
settings will change accordingly when you switch device. It also indicates 
which device is currently in use, as only one can be at a time.

It can be of great help when you don't understand what is happening when you 
pick a device (like when you wonder why a lot of things seems to change without 
you clicking anywhere, or when I hit a known bug where I couldn't switch back 
to the core pointer).

-- 
Karine Delvare
http://edhel.nerim.net/
___
Gimp-user mailing list
Gimp-user@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


[Gimp-user] need help with scanned images

2005-06-04 Thread ivan lópez

hi,

I'm scanning a booklet with the intention of making a PDF version of it.

The booklet is printed on green paper and I'm having problems with the 
readability of the text. If you look at:


http://textzi.net/cosas/07.png

you'll see that the letters get a white edge around them that makes 
them a bit hard to read. Do you have any suggestions for changing this 
with the Gimp? Or should this be fixed directly when I scan the images? 
If so, how?


thanks in advance,

ivan

http://textzi.net

___
Gimp-user mailing list
Gimp-user@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] need help with scanned images

2005-06-04 Thread Carol Spears
On Sat, Jun 04, 2005 at 09:03:51PM -0500, ivan l??pez wrote:
 hi,
 
 I'm scanning a booklet with the intention of making a PDF version of it.
 
 The booklet is printed on green paper and I'm having problems with the 
 readability of the text. If you look at:
 
 http://textzi.net/cosas/07.png
 
 you'll see that the letters get a white edge around them that makes 
 them a bit hard to read. Do you have any suggestions for changing this 
 with the Gimp? Or should this be fixed directly when I scan the images? 
 If so, how?
 
playing with the levels helped a lot.

then i went on to make a mask and apply this to the original.

after only a few minutes with the image, it seems to be easier to read:
http://carol.gimp.org/files/07.xcf

carol

___
Gimp-user mailing list
Gimp-user@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user