On 05/12/2013 07:48 AM, Janet Little wrote:

Recently installed Gimp. Could someone step me through how to change the settings so Gimp no longer opens my pdf files? I see the issue mentioned on the web but the solutions are for a person more computer literate than me. They also seemed to mostly relate to Ubuntu and wanting Evince to open pdf. I have Windows 7 with Chrome & Firefox browsers, and adobe reader. Tried looking here - sorry if I missed it.

Could you right-click on a PDF file and use the "Open With" menu to choose Adobe Reader (or some other PDF reader) as the application to use? When doing that, make sure the "use as default application" (or similarly phrased) check box is checked.

Peace...

Tom

/When we dance, you have a way with me,
Stay with me... Sway with me.../

On 12.05.2013 17:22, Tom Williams wrote:

On 05/12/2013 07:48 AM, Janet Little wrote:

Recently installed Gimp. Could someone step me through how to change the settings so Gimp no longer opens my pdf files? I see the issue mentioned on the web but the solutions are for a person more computer literate than me. They also seemed to mostly relate to Ubuntu and wanting Evince to open pdf. I have Windows 7 with Chrome & Firefox browsers, and adobe reader. Tried looking here - sorry if I missed it.

Could you right-click on a PDF file and use the "Open With" menu to choose Adobe Reader (or some other PDF reader) as the application to use? When doing that, make sure the "use as default application" (or similarly phrased) check box is checked.

I found
http://www.thewindowsclub.com/change-file-associations-windows

when searching for "windows 7 file associations". At a glance, it seems to be pretty straightforward.

HTH,
Michael

Hi,

I am Windows7 64 bits my OS is in French so may be I am not using the corresponding English/US terms

- Left Click on the Start button (at the bottom left of the screen), - The corresponding start windows opens, then Left click on "Configuration Panel"
- A new windows appears. Search for "Default Program" which is just located under "Program and funtionnalities"
- A new windows appears with four selectable options. Left click on the second one from the top "associate a type of file or a protocole with a specific program"
- lets some time to your computer for displaying all the associations then with the lift search for ".pdf".
- When you find it, then you shall find GIMP in regard, then select the line with a left click.
- Look at the top of the windows on the right hand side, you will find a button displaying "change the program". Left click on it. - A new windows appears, in which you should find the Adobe Reader program. IF SO
- You just have to left click on it then click on the OK Button and the windows will close.
- Now aside .pdf Adobe Acrobat Document will appear and the things are done. - Close the windows with a left click on the button located on the bottom right handside, then close other windows and check if everything is OK in opening a .pdf cocument.
IF ADOBE READER PROGRAM does not appear as above, then the thing are a bit more complicated :
- verify that the box to be ticked just under the Recommanded Programs window named "use always the selected program to open this type of document" is ticked.
- Then left click on the "Search" button located just aside. - A New window appears which contains the "Program Files" : on the left you will see the organization of your "C" Hard disk which is supporting the Operating System and all Programs and in most cases the documents ; on the right, you will see the details of the directory which is selected in the left part.
Then it depends if you are using a 32 bits or a 64 bits Windows 7. If it is a 32 bits you are in the right location i.e. "Program Files". If you are using a 64 bits, you have to select Program Files (x86) : use the lift down and left click on "Program Files (x86). - At the top of the right part (sub-window), you will see : Adobe. left click twice on it, then you might have one or two reader : Reader 9.0 or Reader 10.0
- Left click twice on the higher reader you have, in my case Reader 10.0. - you will see four directories : esl, Reader, Resource, Setup Files - Left click twice on Reader directory to look at the details - You will find a .exe named "AcroRd32.exe" - select it with a left click then left click on the "Open" button at the bottom right of the window.
- The .exe shall appear in the "change program" windows, then click on OK and it is done.
- Proceed as above to verify the things.

Hope it will help

Regards

Paul

-----Message d'origine----- From: Janet Little
Sent: Sunday, May 12, 2013 4:48 PM
To: gimp-user-list@gnome.org
Subject: [Gimp-user] PDF

Recently installed Gimp. Could someone step me through how to change the settings so Gimp no longer opens my pdf files? I see the issue mentioned on the web but the solutions are for a person more computer literate than me. They also seemed to mostly relate to Ubuntu and wanting Evince to open pdf. I have Windows 7 with Chrome & Firefox browsers, and adobe reader. Tried looking here - sorry if I missed it.

Hi,

Does anyone on the list here, have any actual knowledge & or experience building GIMP 2.8x on Linux Debian Squeeze? My current version of GIMP is 2.6.1.

Some questions I have (for example) are: Do I /really/ have to uninstall the old version...? Any dependency issues (conflicts, etc.) ? Any way to get the (newer) dependencies by means of the terminal? Will I be able to actually do this (i.e.,/ do a working build with this version/)?

Thanks much for any pointers.

Henry

On Sun, May 12, 2013 at 12:36 PM, Henry W. Peters wrote:

Does anyone on the list here, have any actual knowledge & or experience building GIMP 2.8x on Linux Debian Squeeze? My current version of GIMP is 2.6.1.

Some questions I have (for example) are: Do I /really/ have to uninstall the old version...? Any dependency issues (conflicts, etc.) ? Any way to get the (newer) dependencies by means of the terminal? Will I be able to actually do this (i.e.,/ do a working build with this version/)?

I have 2.6 and 2.8 on the a Mint (like Ubuntu/Debian) system.

There's a build script floating around somewhere, but I can't seem to find it now (and it required heavy modification, at least for my system anyway).

There's this:
http://wiki.gimp.org/index.php/Hacking:Building/Linux

I think the biggest thing to remember is to remember to prefix everything with /opt or /home/YOU/gimp/ - ie *not* put it into /usr or /usr/local/.

'apt-get build-dep gimp' should bring in several -dev packages you'll need. The rest will need to be compiled and installed in /opt or wherever.

It's been some months since I went through this - I'm probably forgetting a few things, but the short answer is yes, you can compile and install 2.8 without removing 2.6. There are quite a dew deps to work through, but keep the additions outside of your system path and you should be fine.

HTH,
Chris

On 12.05.2013 19:36, Henry W. Peters wrote:

Thanks much for any pointers.

Please don't hijack threads - your mail will appear two levels deep in the thread about changing the PDF file associations for some users.

If you want to start a new topic, please compose a new message to the gimp-user-list@gnome.org list mail address (and make sure that you're subscribed).

--
Thanks,
Michael

Hi
Some time ago i tried both compiling Gimp 2.8 on Squeeze, and installing Debian Testing ... to see what's wrong with my attempt to compile Gimp 2.8.

To make long thing short - problems with compilation are caused by dependencies of Gimp 2.8 dependencies. At some moment You end up with upgrading gcc and half other system libraries. If only You can install wheezy it should solve most of Your troubles.

There is one possible workaround: one user of this mailing list approached similar problem on FreeBSD. Solution was building Gimp and all it's dependencies in jail.
This way system was stable and Gimp 2.8 had all needed dependencies inside jail. Unfortunately i can't remember where this instruction was and whether it can be ported to Debian.

Dominik

2013/5/12, Chris Mohler :

On Sun, May 12, 2013 at 12:36 PM, Henry W. Peters wrote:

Does anyone on the list here, have any actual knowledge & or experience building GIMP 2.8x on Linux Debian Squeeze? My current version of GIMP is 2.6.1.

Some questions I have (for example) are: Do I /really/ have to uninstall the
old version...? Any dependency issues (conflicts, etc.) ? Any way to get the
(newer) dependencies by means of the terminal? Will I be able to actually do
this (i.e.,/ do a working build with this version/)?

I have 2.6 and 2.8 on the a Mint (like Ubuntu/Debian) system.

There's a build script floating around somewhere, but I can't seem to find it now (and it required heavy modification, at least for my system anyway).

There's this:
http://wiki.gimp.org/index.php/Hacking:Building/Linux

I think the biggest thing to remember is to remember to prefix everything with /opt or /home/YOU/gimp/ - ie *not* put it into /usr or /usr/local/.

'apt-get build-dep gimp' should bring in several -dev packages you'll need. The rest will need to be compiled and installed in /opt or wherever.

It's been some months since I went through this - I'm probably forgetting a few things, but the short answer is yes, you can compile and install 2.8 without removing 2.6. There are quite a dew deps to work through, but keep the additions outside of your system path and you should be fine.

HTH,
Chris
_______________________________________________ gimp-user-list mailing list
gimp-user-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-user-list

Dominik Tabisz

Thanks all for your replies ON THIS (as far as I know) NEW THREAD (& Michael, I am a subscriber).

It sounds like building 2.8 on Debian Squeeze is a (too) shaky proposition... as I do use it with some regularity, I should probably wait until the Debian packager & programmers resolve some of the dependency issues... (?) But I will persist, somehow/way...

I should have mentioned earlier, that my only desire is to have a stable/workable version of GIMP... I hesitate to uninstall 2.6.1 because of POSSIBLE issues regarding removals that might damage my system... namely 'gnome-office,' & I am just totally in the dark regarding what that piece of software is... but it sounds like something to do w/ the gui of the desktop... (advise appreciated here too).

Henry

On 05/12/2013 03:14 PM, Dominik Tabisz wrote:

Hi
Some time ago i tried both compiling Gimp 2.8 on Squeeze, and installing Debian Testing ... to see what's wrong with my attempt to compile Gimp 2.8.

To make long thing short - problems with compilation are caused by dependencies of Gimp 2.8 dependencies. At some moment You end up with upgrading gcc and half other system libraries. If only You can install wheezy it should solve most of Your troubles.

There is one possible workaround: one user of this mailing list approached similar problem on FreeBSD. Solution was building Gimp and all it's dependencies in jail.
This way system was stable and Gimp 2.8 had all needed dependencies inside jail. Unfortunately i can't remember where this instruction was and whether it can be ported to Debian.

Dominik

2013/5/12, Chris Mohler:

On Sun, May 12, 2013 at 12:36 PM, Henry W. Peters wrote:

Does anyone on the list here, have any actual knowledge& or experience building GIMP 2.8x on Linux Debian Squeeze? My current version of GIMP is 2.6.1.

Some questions I have (for example) are: Do I /really/ have to uninstall the
old version...? Any dependency issues (conflicts, etc.) ? Any way to get the
(newer) dependencies by means of the terminal? Will I be able to actually do
this (i.e.,/ do a working build with this version/)?

I have 2.6 and 2.8 on the a Mint (like Ubuntu/Debian) system.

There's a build script floating around somewhere, but I can't seem to find it now (and it required heavy modification, at least for my system anyway).

There's this:
http://wiki.gimp.org/index.php/Hacking:Building/Linux

I think the biggest thing to remember is to remember to prefix everything with /opt or /home/YOU/gimp/ - ie *not* put it into /usr or /usr/local/.

'apt-get build-dep gimp' should bring in several -dev packages you'll need. The rest will need to be compiled and installed in /opt or wherever.

It's been some months since I went through this - I'm probably forgetting a few things, but the short answer is yes, you can compile and install 2.8 without removing 2.6. There are quite a dew deps to work through, but keep the additions outside of your system path and you should be fine.

HTH,
Chris

On 05/12/2013 02:44 PM, Michael Schumacher wrote:

Please don't hijack threads - your mail will appear two levels deep in the thread about changing the PDF file associations for some users.

If you want to start a new topic, please compose a new message to the gimp-user-list@gnome.org list mail address (and make sure that you're subscribed).

--
Thanks,
Michael

* Henry W. Peters [05-12-13 15:48]:

Thanks all for your replies ON THIS (as far as I know) NEW THREAD (& Michael, I am a subscriber).

It sounds like building 2.8 on Debian Squeeze is a (too) shaky proposition... as I do use it with some regularity, I should probably wait until the Debian packager & programmers resolve some of the dependency issues... (?) But I will persist, somehow/way...

I should have mentioned earlier, that my only desire is to have a stable/workable version of GIMP... I hesitate to uninstall 2.6.1 because of POSSIBLE issues regarding removals that might damage my system... namely 'gnome-office,' & I am just totally in the dark regarding what that piece of software is... but it sounds like something to do w/ the gui of the desktop... (advise appreciated here too).

Henry

On 05/12/2013 03:14 PM, Dominik Tabisz wrote:

Hi
Some time ago i tried both compiling Gimp 2.8 on Squeeze, and installing Debian Testing ... to see what's wrong with my attempt to compile Gimp 2.8.

To make long thing short - problems with compilation are caused by dependencies of Gimp 2.8 dependencies. At some moment You end up with upgrading gcc and half other system libraries. If only You can install wheezy it should solve most of Your troubles.

There is one possible workaround: one user of this mailing list approached similar problem on FreeBSD. Solution was building Gimp and all it's dependencies in jail.
This way system was stable and Gimp 2.8 had all needed dependencies inside jail. Unfortunately i can't remember where this instruction was and whether it can be ported to Debian.

Dominik

2013/5/12, Chris Mohler:

On Sun, May 12, 2013 at 12:36 PM, Henry W. Peters wrote:

Does anyone on the list here, have any actual knowledge& or experience building GIMP 2.8x on Linux Debian Squeeze? My current version of GIMP is 2.6.1.

Some questions I have (for example) are: Do I /really/ have to uninstall the
old version...? Any dependency issues (conflicts, etc.) ? Any way to get the
(newer) dependencies by means of the terminal? Will I be able to actually do
this (i.e.,/ do a working build with this version/)?

I have 2.6 and 2.8 on the a Mint (like Ubuntu/Debian) system.

There's a build script floating around somewhere, but I can't seem to find it now (and it required heavy modification, at least for my system anyway).

There's this:
http://wiki.gimp.org/index.php/Hacking:Building/Linux

I think the biggest thing to remember is to remember to prefix everything with /opt or /home/YOU/gimp/ - ie *not* put it into /usr or /usr/local/.

'apt-get build-dep gimp' should bring in several -dev packages you'll need. The rest will need to be compiled and installed in /opt or wherever.

It's been some months since I went through this - I'm probably forgetting a few things, but the short answer is yes, you can compile and install 2.8 without removing 2.6. There are quite a dew deps to work through, but keep the additions outside of your system path and you should be fine.

HTH,
Chris

On 05/12/2013 02:44 PM, Michael Schumacher wrote:

Please don't hijack threads - your mail will appear two levels deep in the thread about changing the PDF file associations for some users.

If you want to start a new topic, please compose a new message to the gimp-user-list@gnome.org list mail address (and make sure that you're subscribed).

--
Thanks,
Michael

But you have not started a *new* thread but merely changed the subject and at that not for this post but several previous to this.

You are still "hijacking" the PDF thread

see: http://wahoo.no-ip.org/~pat/HijackedThread.jpg

(paka)Patrick Shanahan       Plainfield, Indiana, USA      HOG # US1244711
http://wahoo.no-ip.org        Photo Album: http://wahoo.no-ip.org/gallery2
http://en.opensuse.org                           openSUSE Community Member
Registered Linux User #207535                    @ http://linuxcounter.net

Hi,

before we now begin a big off-topic mess and hassle, I simply started a new thread for this topic. Please continue your discussion there.

Kind regards,

Sven

The "thread" is all yours... I have no idea of what you are speaking of ("started a new thread"), apparently, I do not understand the "rules" here...

I have been doing email/listserve boards for quite a few years... never ran into this problem... & it DEFINITELY was not my intent to "hijack" ANYTHING. Would appreciate (also) if people would not be so hasty to such JUDGEMENTS, which means, though I'm truly sorry to disrupt anyone's reasonable conversation, I'm not apologizing for doing something which I did/do not know.

Henry
P.s., I could have been pointed to where the agreed (presumably) protocols reside...

On 05/12/2013 04:35 PM, scl wrote:

Hi,

before we now begin a big off-topic mess and hassle, I simply started a new thread for this topic. Please continue your discussion there.

Kind regards,

Sven

On 13.05.2013 00:35, Henry W. Peters wrote:

I have been doing email/listserve boards for quite a few years... never ran into this problem...

See https://mail.gnome.org/archives/gimp-user-list/2013-May/thread.html - your message appears as a reply to a mail in the PDF file association thread.

You must have hit reply (there's a corresponding In-Reply-To: header) instead of
composing a new message. Note that changing the subject is not sufficient to start a new thread.

HTH,
Michael