Re: [Gimp-user] cant win, or break even and what are the rules anyway.

2004-05-03 Thread Owen
On Mon, 03 May 2004 10:26:24 +0100
david [EMAIL PROTECTED] wrote:

 Hi
 
 I have been downloading devel packages and some of the problems have 
 gone, apart from
 checking for gimpprint-config... no
 checking for GIMP-PRINT - version = 4.2.0... no
 *** The gimpprint-config script installed by GIMP-PRINT could not be found
 *** If GIMP-PRINT was installed in PREFIX, make sure PREFIX/bin is in
 *** your path, or set the GIMPPRINT_CONFIG environment variable to the
 *** full path to gimpprint-config.
 configure: error:
 *** Check for libgimpprint failed. You can download it from
 *** http://gimp-print.sourceforge.net/ or you can build without it by 
 passing
 *** --disable-print to configure (but you won't be able to print then).
 
 I have the correct gimpprint installed.  But is not recognised.

Do you have a file  gimpprint-config?  Where is it?

If not I think you need to install libgimpprint1-devel-4.2.XXX.mdk where XXX is your 
version number off your CD


Owen





 





___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] cant win, or break even and what are the rules anyway.

2004-05-03 Thread Sven Neumann
Hi,

david [EMAIL PROTECTED] writes:

 *** Check for libgimpprint failed. You can download it from
 *** http://gimp-print.sourceforge.net/ or you can build without it by
 passing
 *** --disable-print to configure (but you won't be able to print then).
 
 I have the correct gimpprint installed.  But is not recognised.
 
 [EMAIL PROTECTED] david]$ rpm -qa | grep gimp
 gimp-1.2.5-10mdk
 libgimp1.2_1-devel-1.2.5-10mdk
 libgimp1.2-1.2.5-10mdk
 libgimp1.2_1-1.2.5-10mdk
 xsane-gimp-0.92-1mdk
 gimpprint-4.2.6-14mdk
 libgimpprint1-4.2.6-14mdk

Looks like you are missing the libgimpprint development package. You
can't compile any code using the gimpprint library without having the
development package installed that contains the headers and the
gimpprint-config script.

 Did you adjust the PKG_CONFIG_PATH environment variable as
 suggested in the configure output?

 I do not understand this.

Please read the pkg-config manpage then.


Sven
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] Basic GIMP compilation question

2004-05-03 Thread Sven Neumann
Hi,

Barton Bosch [EMAIL PROTECTED] writes:

 I am running a Red Hat 9.0 system that currently has GIMP 1.2.3
 installed on it.  I'd like to check out 2.0 and have been trying to
 figure out how to get it together.  I haven't compiled much large,
 involved software yet so I am running into some fundamental questions.

I strongly suggest you don't compile GIMP from source then but use a
precompiled binary. http://xach.com/ has RPMs for RedHat 9.0.
Unfortunately not 2.0.1 yet but you could at least install all the
dependencies from there and compile only GIMP. That will save you some
major troubles. Getting all the dependencies compiled from source
requires a good deal of experience building software from source.

 Secondly, in the GIMP ftp directory I saw a patch for 2.0.1. What is
 this patch for and do I need it?

It's the patch to update gimp-2.0.0 to gimp-2.0.1. Useful for people
who downloaded gimp-2.0.0 earlier.


Sven
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] Basic GIMP compilation question

2004-05-03 Thread Barton Bosch
Sven Neumann wrote:
Hi,

Barton Bosch [EMAIL PROTECTED] writes:


I am running a Red Hat 9.0 system that currently has GIMP 1.2.3
installed on it.  I'd like to check out 2.0 and have been trying to
figure out how to get it together.  I haven't compiled much large,
involved software yet so I am running into some fundamental questions.


I strongly suggest you don't compile GIMP from source then but use a
precompiled binary. http://xach.com/ has RPMs for RedHat 9.0.
Unfortunately not 2.0.1 yet but you could at least install all the
dependencies from there and compile only GIMP. That will save you some
major troubles. Getting all the dependencies compiled from source
requires a good deal of experience building software from source.
Thanks for the quick response and the link to the RPMs.  Those 
should be very helpful.  Did I miss this on gimp.org somehow?



Secondly, in the GIMP ftp directory I saw a patch for 2.0.1. What is
this patch for and do I need it?

It's the patch to update gimp-2.0.0 to gimp-2.0.1. Useful for people
who downloaded gimp-2.0.0 earlier.
Oh, ok, good to know.

Barton

___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] cant win, or break even and what are the rules anyway.

2004-05-03 Thread david
Hi

Thanks for the help and suggestions.  I finally have got past the 
./configure stage with no problems.

Do you have a file 	gimpprint-config	?  Where is it?

If not I think you need to install libgimpprint1-devel-4.2.XXX.mdk where XXX is your version number off your CD

Actually I could not find the libgimpprint-devel that matched.  I tried 
one higher, then one lower.  The lower worked.

But once again thanks.

david
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


[Gimp-user] picture orientation

2004-05-03 Thread David A Iacobellis
I recently purchased a Nikon D70 camera.  After getting the camera I upgraded 
GIMP to 2.0.1.  When I take a picture with the camera oriented horizontal I 
have no problems.  When I take a picture with the camera oriented vertical I 
have discovered a puzzling glitch.

The camera automatically orients vertical photos vertical on the built in 
viewer for quick viewing instead of horizontal.  After downloading the images 
to my computer kuickshow will also automatically orient the untouched 
vertical photos vertical.  If I open the vertical photos in GIMP the photos 
are horizontal (as they should be).  I went ahead and rotated a couple of the 
images to get them vertical in GIMP and saved them.  Now in kuickshow the 
GIMP modified vertical photos are horizontal in the opposite direction.

What causes the camera and kuickshow to automatically orient the vertical 
photos and is there anyway to get GIMP to do the same or get kuickshow to 
stop doing it?

Any help will be appreciated,

Dave
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] picture orientation

2004-05-03 Thread David A Iacobellis
On Monday 03 May 2004 05:54 pm, Nem W Schlecht wrote:

Thanks everybody for some great advice and ideas.

Dave

 David A Iacobellis e-mailed me on Mon May  3 14:51:55 2004
 (Re: [Gimp-user] picture orientation)

 I recently purchased a Nikon D70 camera.  After getting the camera I
  upgraded GIMP to 2.0.1.  When I take a picture with the camera oriented
  horizontal I have no problems.  When I take a picture with the camera
  oriented vertical I have discovered a puzzling glitch.
 
 The camera automatically orients vertical photos vertical on the built in
 viewer for quick viewing instead of horizontal.  After downloading the
  images to my computer kuickshow will also automatically orient the
  untouched vertical photos vertical.  If I open the vertical photos in
  GIMP the photos are horizontal (as they should be).  I went ahead and
  rotated a couple of the images to get them vertical in GIMP and saved
  them.  Now in kuickshow the GIMP modified vertical photos are horizontal
  in the opposite direction.
 
 What causes the camera and kuickshow to automatically orient the vertical
 photos and is there anyway to get GIMP to do the same or get kuickshow to
 stop doing it?

 There is an EXIF tag that describes the orientation of the photo.  When you
 open/rotate/save in the Gimp, it does *NOT* modify this EXIF header, so
 kuickshow is re-rotating it (as it thinks it needs to, since the
 Orientation tag is still in the EXIF header).

 Get jhead which has a nice option to remove the EXIF orientation tag
 (-norot).  Also, you should use jpegtran to rotate your image - not the
 Gimp (as loading it, rotating it, and then saving it will reduce the
 quality - jpegtran can rotate it with no loss).

 jpegtran comes with the JPEG library

 jhead is available here:  http://www.sentex.net/~mwandel/jhead/

 Actually, jhead can call jpegtran for you, so you may just want to do
 this once you transfer images from your camera:

 for i in *.jpg
 do
   jhead -autorot -norot $i
 done
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


[Gimp-user] Gimp CinePaint

2004-05-03 Thread Wayne Maeda
There's an interesting article about the GIMP, CinePaint, and the CinePaint 
developers here:

http://www.linuxdevcenter.com/pub/a/linux/2004/04/29/cinepaint.html
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] picture orientation

2004-05-03 Thread David Neary
Hi,

David A Iacobellis wrote:
 What causes the camera and kuickshow to automatically orient the vertical 
 photos and is there anyway to get GIMP to do the same or get kuickshow to 
 stop doing it?

When you take photos and set the orientation (horizontal or
vertical) in your camera, that information is saved in the exif
header in the image file. Then when your viewing application
opens this file, they read that header and rotate the image
appropriately for viewing.

When you open the image in the GIMP, that information is not used
before presenting the image. And when you rotate the image, the
exif header is not modified. So when you save your jpg again, the
same exif header (saying that the image should be rotated 90
degrees) is saved with the image.

Then when you open the image in your viewer, the image which you
rotated is again automatically rotated by your viewer, 90
degrees. Which you don't want.

The only way to avoid this problem currently is to destroy the
exif data saved in the header of your file. That way, your image
viewer will not do any automatic adjustments based on it.

The better long-term solution would be to either (1) have the
image loading affected in the GIMP by this header, or (2)
over-write this setting at write time, so that what you save in
the GIMP is what you see everywhere else.

Neither of these are currently possible in the GIMP.

Cheers,
Dave.

-- 
   David Neary,
   Lyon, France
  E-Mail: [EMAIL PROTECTED]
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


[Gimp-user] Re: [Gimp-developer] Screenshots

2004-05-03 Thread Sven Neumann
Hi,

David Neary [EMAIL PROTECTED] writes:

 I was just looking for some nice looking screenshots to show off
 on the GUADEC GIMP pages, and the best ones are all on
 developer.gimp.org

The problem with the screenshots on dgo is that they are screenshots
of the 1.3.x development version. Most of them clearly don't look like
2.0. It shouldn't be too difficult to redo these shots with an
uptodate version. I am sure people will happily donate their
screenshots.

 It would be really cool to have lots  lots of screenshots of the
 GIMP on www.gimp.org. Could someone from the web team take
 responsibility for this and publish an e-mail address where
 screenshots can be sent to be included on the site, please?
 
 In the meantime, I will link to screenshots on dgo.

I'd like to remove the dgo screenshots sooner or later and replace
them with screenshots of the CVS version. But of course I'll leave
them online until more screenshots are available from www.gimp.org.


Sven
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


[Gimp-user] More GIMP compilation questions

2004-05-03 Thread Barton Bosch
Thanks to the link to the Red Hat 9.0 RPMs (kudos to xach) I've 
gotten my system updated far enough to attempt to compile gimp 
2.0.1 from source.  I've compiled and installed many of the 
optional packages as well.

I am running into a couple of warning messages though, re: 
gtkhtml2 and the html help browser, laa/aa_printf, and llcms and 
the color proof module.  FYI, for the time being I am 
configuring with the --disable-print option.  Here is the 
relevant ./configure output:

checking for aa_printf in -laa... no
configure: WARNING: *** AA plug-in will not be built (AA library 
not found) ***
...
checking for libgtkhtml-2.0 = 2.0.0... Package libgtkhtml-2.0 
was not found in
the pkg-config search path.
Perhaps you should add the directory containing `libgtkhtml-2.0.pc'
to the PKG_CONFIG_PATH environment variable
configure: WARNING: *** Help browser plug-in will not be built 
(GtkHtml2 not found) ***
...
checking for cmsCreate_sRGBProfile in -llcms... no
configure: WARNING: *** color proof module will not be built 
(lcms not found or
unuseable) ***

I've checked my repositories for unistalled packages and their 
devel couterparts, done a good bit of googling for further 
packages/tar balls to download and install but no joy.

Anyone have a solution?

Thanks,

Barton

___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user


Re: [Gimp-user] picture orientation

2004-05-03 Thread Timothy E. Jedlicka - wrk
As mentioned, the exif header info in the jpg is telling kuickshow how to 
rotate the image. After editing in Gimp, you can use jpegtran to change the 
exif info (to not rotate).
jpegtran -rotate 90 file.jpg  newfile.jpg

this is a lossless conversion, only effecting the exif header.
-
Timothy Jedlicka, [EMAIL PROTECTED], 1-630-713-4436, AOL-IM=bonzowork
Network Entomologist, Lucent Technologies, Testers For Hire


___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user