Nabble - Gimpwin Users

Gimp2.6 not starting in Vista (g_asii_strtoull cannot be located in dll libglib-2.0-0.dll)

2009-07-19T01:34:58Z

Hi
How can I fix this error with wind.exe (& then if close out of this many other .exe error message boxes pop up also)to get GIMP to start in Vista please?
(I saw a message on sourceforge help on this but noone had replied-so unhelpful! Perhaps someone else has posted a solution here but I have looked and cannot find it?!).

Error message wind.exe
>>>The procedure entry point g_ascii_strtoull could not be located in the dynamic link library libglib-2.0-0.dll<<<

I look forward to help, thanks

help information/ which version

2008-10-10T05:08:23Z

Hello

I am very new to gimp and a complete beginner, i just wanted to know , when you press "help" to go to the help pages, are they for the latest version 2.6.0

as an example, i was trying to follow the help pages to crop an image, and after you have clicked and dragged the part of the image you want, it says a crop and resize information dialog box pops up, but this did not happen, and i was left bewildered as to what i should do next.

as i said complete beginner, it all looks over-powering at the moment

windows xp--------gimp 2.6.0

Re: " Error Starting Ghostscript"

2008-09-13T13:44:47Z

I had the same problems as you and setting the path did not work. I set the environment variable GS_PROG to:

C:\Program Files\gs\gs8.63\bin\gswin32.exe

That fixed it.

Let me know if you need the 'how to' on that.

LaMark Lee wrote:

Hello, I've tried to import a .eps format vector image and it would not
allow me. I got a message saying Error starting ghostscript. Make sure
that ghostscript is installed and if necessary use the environment
variable us_prog to tell Gimp about it's location. (Failed to execute
child process No such file or directory). Could not interpret. Failed.
Encapsulated postscript image plug-In could not open image ( I don't
know what ghostscript, environment variable, and postscript is/mean).
Does any of this look familiar. Do you know of a solution, if not any
other groups/mailing list I can submit this inquiry to. I'm using
windows vista premium w/ Gimp 2.4.7 if it helps at all. Contact me
whenever you get a chance. Thanks!

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-10T16:49:39Z

> And yet you chose to pick a quarrel without first
> informing yourself on what the email even said?

Oh, just fuck off, will you?

--tml

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-10T14:07:49Z

From: "Tor Lillqvist" <tml@...>
Date: Wed, 10 Sep 2008 21:57:58 +0300

>> Did you even bother to read to the bottom of my
>> original answer,

>Not really, no.

And yet you chose to pick a quarrel without first
informing yourself on what the email even said?

You do know that this is not even in the first dozen
times you've done this to someone here!!

xanthian.

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-10T11:57:58Z

> Did you even bother to read to the bottom of my
> original answer,

Not really, no.

--tml

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-10T11:40:28Z

> From: "Tor Lillqvist" <tml@...>
> Date: Wed, 10 Sep 2008 10:01:28 +0300

>>> Xanthian, instead of just talking in general,
>>> could you give some concrete examples of how one
>>> needs to take printer model specific quirks into
>>> account when using the Win32 printing related
>>> APIs?

>> Not likely, 20 years later.

> But Win32 did not exist 20 years ago.

So? Once again you are entirely out of line.

Did you even bother to read to the bottom of my
original answer, or did you just return some snippy
comment out of meanness of spirit?

The unethical competition tactics and sloppy
software development and software quality control
habits at Microsoft, have existed since it was
founded. The realities of a marketplace where some
potential software targets (both hardware and other
software, like browsers) have too small a market
share for first party and third party developers to
spend time catering to them, has existed since the
first third party software was created.

The limitations of standards to define now and
forever what such a software target's interface must
be able to convey and how to take correct and full
advantages of that software target's quirks and
features beyond the standard, have all existed since
before Microsoft existed.

The problem addressing a diverse marketplace of
software interface targets with a single interface
component isn't an operating system specific
problem, it isn't even a software-specific problem;
the same issues occur for making bags full of
assorted gaskets cater for all the faucets that
buyers might have in their homes.

The intention of my original answer was just to warn
the original author that users of GIMP, and thus
downstream users of GTK+, should not expect for free
the same coverage of printer types that can be put
into commercial software by the expenditure of very
large effort and very large expense by big
companies, so that some personal printers might well
_never_ be covered by GIMP. The end result is the
usual advice: save the GIMP image in a file, import
it to some program with better printing
capabilities, and print it from there.

All of these are ongoing realities, not stuff that
needs detailed example. In GIMP, the user is
_already_ complaining about GIMP not working as
expected. Nor do the problems with MS-Windows need
separate and detailed documenting by me, they are
the stuff of legends. See my just prior posted
message to the group for just one more example of
the horror of currently sold Microsoft software.

xanthian.

Re: Re: " Error Starting Ghostscript"

2008-09-10T11:15:45Z

> From: LaMark Lee <lemark_lee@...>
> Date: Tue, 9 Sep 2008 12:20:37 -0700 (PDT)

> Hello, it's me again. I installed the latest
> version of ghostscipt as you recommended, it's
> exactly where you said it would be. Then typed
> specifications in path bar and for some reason it
> won't work. I've restared my computer, double
> checked and retyped exe folder text in path bar
> and it doesn't work. Got any other suggestions.
> Contact me whenever you get a chance. Thank you.

"It won't work" doesn't do much to help people help
you. Exactly which error messages or incorrect
behavior did you see this time, and exactly what did
you do to try to access a postscript file with GIMP
this time, in obsessive detail?

Also, we need to see what you have now in the "PATH"
environmental variable. From the Start Menu, open
"run", run "command", in command run "path", use the
upper left corner mark and copy commands to cut and
paste the answer to "path" and report it back to
this group.

Oops, even though it should, that doesn't work
correctly, even if you use command to run path, and
divert its output to a file

path > c:\path.txt

the answer is both abbreviated with "~"s and
truncated to the width of the command widow (grr),
even though it isn't _going_ to the command window:

PATH=c:\PROGRA~1\IMAGEM~1.4-Q;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\ATITEC~1\ATICON~1;C:\PROGRA~

[Ask me why I rant constantly about the hideous
software quality of Microsoft Windows.]

You'll have to find another way to get the right
answer.

What worked for me is to capture the output of path
within the "vim" editor [http://www.vim.org] into
the file currently being edited, by using the vim
command mode command

:r !path

which gives the full unabbreviated contents of the
"PATH" environmental variable:

PATH=c:\program files\imagemagick-6.3.4-q16;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\GTK\2.0\bin;C:\Program Files\QuickTime\QTSystem\

[I'm not about to guess why the same Microsoft
command, "path", gives differently shaped answers
depending on the context from which you run it.]

I'm not showing you either of those to show you what
the Ghostscript entry will look like, I don't have
it in there, in my case, I'm just showing you what
the output that gimpwin-ers need to see looks
like, so that we can be sure you added the right
stuff to the "PATH" environmental variable's paths
to search and order of searching for executables
line.

Also provide a full path listing of the location of
the Ghostscript executable as you installed it
(probably somewhere in "c:\program files\" and the
full path listings of any dynamic link libraries
that it may use, so that we may compare them to what
you put into the path of execution line.

Once that information is back here, others will be
better able to help you than I am, since I don't use
GIMP on postscript files.

xanthian.

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-10T00:01:28Z

>> Xanthian, instead of just talking in general, could
>> you give some concrete examples of how one needs to
>> take printer model specific quirks into account when
>> using the Win32 printing related APIs?

> Not likely, 20 years later.

But Win32 did not exist 20 years ago.

--tml

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-09T16:32:09Z

> From: "Tor Lillqvist" <tml@...>
> Date: Tue, 9 Sep 2008 16:56:22 +0300

>>> I thought the whole point of the Windows GDI was
>>> that the programmer didn't have to know what the
>>> backend printer and its driver was.

>> Well, first of all because Microsoft came very late
>> to the game of establishing a standard driver
>> interface. [...]

> Xanthian, instead of just talking in general, could
> you give some concrete examples of how one needs to
> take printer model specific quirks into account when
> using the Win32 printing related APIs?

Not likely, 20 years later.

>> [Of course, that kind of failure has long ago been
>> made unnecessary by Posix and other standards.

> Please note that despite POSIX and all, the printing
> interface on various Unixes is far from
> standardized. GTK+ has for Unix two different
> printing backends: cups and lpr. I am sure that
> there are many not that uncommon Unix variants that
> those haven't actually been tested on.

That's not the level at which Posix standardizes.

> --tml

xanthian.

Re: Re: " Error Starting Ghostscript"

2008-09-09T12:20:37Z

Hello, it's me again. I installed the latest version of ghostscipt as you recommended, it's exactly where you said it would be. Then typed specifications in path bar and for some reason it won't work. I've restared my computer, double checked and retyped exe folder text in path bar and it doesn't work. Got any other suggestions. Contact me whenever you get a chance. Thank you.

----- Original Message ----
From: Elliot Nesterman <elliot@...>
To: gimpwin-users@...
Sent: Monday, September 8, 2008 4:17:42 PM
Subject: [gimpwin-users] Re: " Error Starting Ghostscript"

eps files are in PostScript format, eps stands for Encapsulated
PostScript. PostScript is a printer language developed and licensed by
Apple.
Ghostscript is a free PostScript interpreter. With Ghostscript installed
a Windows box that does not have a licensed PostScript interpreter can
view and manipulate PostScript files.

You will need administrator privileges to your machine to install
ghostscript and edit the Path statement.

Get Ghostscript here:
http://sourceforge. net/project/ showfiles. php?group_ id=1897
grab the latest, GPL Ghostscript 8.63, and install it.
IMPORTANT - Make a note of where Ghostscript installs (usually
c:\program files\gs)

You will then need to add the path to the executable to your PATH
environment variable. This is not a scary as it sounds.
Right Click on My Computer on your Desktop.
Click Properties.
click on the Advanced tab.
click the Environment Variables button towards the bottom.
In the lower window scroll down to Path.
click on Edit.
at the end of the line add a semicolon then the path to the ghostcript
exe folder, ;c:\path-to- ghostscript\ release-number\ bin
f'rinstance ;c:\program files\gs\gs8. 63\bin
click OK.
click OK.

Now you can open eps files with GIMP.

lemark_lee wrote:

> Hello, I've tried to import a .eps format vector image and it would not
> allow me. I got a message saying Error starting ghostscript. Make sure
> that ghostscript is installed and if necessary use the environment
> variable us_prog to tell Gimp about it's location. (Failed to execute
> child process No such file or directory). Could not interpret. Failed.
> Encapsulated postscript image plug-In could not open image ( I don't
> know what ghostscript, environment variable, and postscript is/mean).
> Does any of this look familiar. Do you know of a solution, if not any
> other groups/mailing list I can submit this inquiry to. I'm using
> windows vista premium w/ Gimp 2.4.7 if it helps at all. Contact me
> whenever you get a chance. Thanks!
>

--
Elliot Nesterman
elliot@ajoure. net
Standard Disclaimers Apply
------------ --------- --------- --------- --------- --------- -
The closer you are to the code, the happier you are.
- Ancient Geek Proverb
------------ --------- --------- --------- --------- --------- -

[Non-text portions of this message have been removed]

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-09T06:56:22Z

>> I thought the whole point of the Windows GDI was
>> that the programmer didn't have to know what the
>> backend printer and its driver was.

> Well, first of all because Microsoft came very late
> to the game of establishing a standard driver
> interface. [...]

Xanthian, instead of just talking in general, could you give some
concrete examples of how one needs to take printer model specific
quirks into account when using the Win32 printing related APIs?

> [Of course, that kind of failure has long ago been
> made unnecessary by Posix and other standards.

Please note that despite POSIX and all, the printing interface on
various Unixes is far from standardized. GTK+ has for Unix two
different printing backends: cups and lpr. I am sure that there are
many not that uncommon Unix variants that those haven't actually been
tested on.

--tml

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-09T06:31:17Z

To: gimpwin-users@...
From: Hedley Finger <hfinger@...>
Date: Tue, 09 Sep 2008 09:29:55 +1000

Kent:

>> The implementation team has to choose just what
>> range of printers in what printer families it
>> will support, and then cater to all their quirks,
>> at the architecture, design, implementation, and
>> testing stages.

> I thought the whole point of the Windows GDI was
> that the programmer didn't have to know what the
> backend printer and its driver was. The
> programmer makes the print output write to the GDI
> and the printer manufacturer's driver honours the
> calls made by the GDI. Why does this sound too
> simple?

Well, first of all because Microsoft came very late
to the game of establishing a standard driver
interface. The AmigaOS, for example, had such a
standard "out of the box"; Microsoft was somewhere
post MS-DOS and well into the MS-Windows family of
OSen before the idea finally penetrated that
standard programming interfaces were useful to
hardware manufacturers as well as (possibly
competitors to Microsoft) software creators. Of
course, that "standard" interface didn't do much
good if the vendor of each OS established a
_different_ programming interface standard, which
then became the situation. It is only when the
standards become collective ANSI or ISO standards
that they start to be useful.

Second, standards become minimal interfaces,
constraining new product features. Also, obeying or
disobeying standards becomes a tactical marketing
decision.

If a manufacturer wants to differentiate its product
[or if it wants to get a "vendor lock" on its
customers], then it will "extend" its product beyond
the standard, creating new capabilities, that are
in turn only useful if the OS vendor cooperates and
supports the class of devices, device by device
separately.

Alternately, the monopolist may deliberately
misapply the standard, as Microsoft does essentially
100% of the time to make stuff like Internet
Explorer impossible to script in W3C standard HTML.

[You _want that_ as a near monopoly vendor, because
then the products created will have to be tailored
by the vast cloud of software cobblers specifically
to match your interface, will have to use a
non-standard set of features catering only to you.

Those non-standard features to make up for the
ideosyncracies of interfacing with your monopolist
product then won't work on the competing products
that obey the standards precisely, except by
extra effort to include some form of conditional
execution, so expensive to create that the result
quite often succeeds iin driving your competitors
out of business even though their behavior is the
"correct" one. It just happens to be business
suicide.]

For example, you'll see this very often in website
HTML code at commercial sites, that the first thing
that is done is to detect the customer's browser
type, and then serve web pages dynamically catering
to that browser type, or alternately serve static
web pages with a mess of internal conditional
execution scripting (think JavaScript) to cater for
each supported browser type. If browser vendors all
stuck to implementing all of and exactly the well
known and published standards, none of that
conditional execution would be necessary.

The moral lesson there using a well known example is
that just because you have a standard in writing
like HTML 4.01, doesn't mean the problem of dealing
with "stuff", say, printers, case by case depending
on the manufacturer and model, has been overcome.

However, given all that, Tor tells us that GTK+ is
broken for MS-Windows at a much more fundamental
level than that.

[Of course, that kind of failure has long ago been
made unnecessary by Posix and other standards. If
Microsoft actually supported existing standards,
that kind of failure couldn't be a problem, the
interfaces would behave just like the Linux ones do,
just as Posix and other standards say they should
do. That, however, would make the OS an unimportant
detail of what a buyer wants in a computer, and
Microsoft, who gets rich selling its OS, would go
broke as the customer found it to work just like the
free OSen do.]

Or so I believe.

xanthian.

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-08T16:29:55Z

Kent:

> The implementation team has to choose just what
> range of printers in what printer families it will
> support, and then cater to all their quirks, at the
> architecture, design, implementation, and testing
> stages.

I thought the whole point of the Windows GDI was that the programmer
didn't have to know what the backend printer and its driver was. The
programmer makes the print output write to the GDI and the printer
manufacturer's driver honours the calls made by the GDI. Why does this
sound too simple?

Regards,
Hedley

--

Hedley Finger

28 Regent Street Camberwell VIC 3124 Australia
Tel. +61 3 9809 1229 Fax. (call phone first)
Mob. (cell) +61 412 461 558
Email. "Hedley Finger" <hfinger@...>

Re: " Error Starting Ghostscript"

2008-09-08T14:16:27Z

eps files are in PostScript format, eps stands for Encapsulated
PostScript. PostScript is a printer language developed and licensed by
Apple.
Ghostscript is a free PostScript interpreter. With Ghostscript installed
a Windows box that does not have a licensed PostScript interpreter can
view and manipulate PostScript files.

You will need administrator privileges to your machine to install
ghostscript and edit the Path statement.

Get Ghostscript here:
http://sourceforge.net/project/showfiles.php?group_id=1897
grab the latest, GPL Ghostscript 8.63, and install it.
IMPORTANT - Make a note of where Ghostscript installs (usually
c:\program files\gs)

You will then need to add the path to the executable to your PATH
environment variable. This is not a scary as it sounds.
Right Click on My Computer on your Desktop.
Click Properties.
click on the Advanced tab.
click the Environment Variables button towards the bottom.
In the lower window scroll down to Path.
click on Edit.
at the end of the line add a semicolon then the path to the ghostcript
exe folder, ;c:\path-to-ghostscript\release-number\bin
f'rinstance ;c:\program files\gs\gs8.63\bin
click OK.
click OK.

Now you can open eps files with GIMP.

lemark_lee wrote:

--
Elliot Nesterman
elliot@...
Standard Disclaimers Apply
-----------------------------------------------------------
The closer you are to the code, the happier you are.
- Ancient Geek Proverb
-----------------------------------------------------------

Re: " Error Starting Ghostscript"

2008-09-08T13:50:57Z

Ghostscript is a PDF document program. You have to have it installed on your system to get GIMP to open it. Think of it as an "open source Adobe Acrobat Reader/writer" program.

Vodor....

vodor1@... ; thielensan2@...
vyzzhor@... ; thielensan@...
dennisthielen@...
http://xianz.com/vodor1; http://360.yahoo.com/vodor1

--- On Mon, 9/8/08, lemark_lee <lemark_lee@...> wrote:

From: lemark_lee <lemark_lee@...>
Subject: [gimpwin-users] " Error Starting Ghostscript"
To: gimpwin-users@...
Date: Monday, September 8, 2008, 1:32 PM

Hello, I've tried to import a .eps format vector image and it would not
allow me. I got a message saying Error starting ghostscript. Make sure
that ghostscript is installed and if necessary use the environment
variable us_prog to tell Gimp about it's location. (Failed to execute
child process No such file or directory). Could not interpret. Failed.
Encapsulated postscript image plug-In could not open image ( I don't
know what ghostscript, environment variable, and postscript is/mean).
Does any of this look familiar. Do you know of a solution, if not any
other groups/mailing list I can submit this inquiry to. I'm using
windows vista premium w/ Gimp 2.4.7 if it helps at all. Contact me
whenever you get a chance. Thanks!

[Non-text portions of this message have been removed]

" Error Starting Ghostscript"

2008-09-08T13:32:00Z

Hello, I've tried to import a .eps format vector image and it would not
allow me. I got a message saying Error starting ghostscript. Make sure
that ghostscript is installed and if necessary use the environment
variable us_prog to tell Gimp about it's location. (Failed to execute
child process No such file or directory). Could not interpret. Failed.
Encapsulated postscript image plug-In could not open image ( I don't
know what ghostscript, environment variable, and postscript is/mean).
Does any of this look familiar. Do you know of a solution, if not any
other groups/mailing list I can submit this inquiry to. I'm using
windows vista premium w/ Gimp 2.4.7 if it helps at all. Contact me
whenever you get a chance. Thanks!

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-08T12:38:13Z

Try this:
Open the original file in Gimp, and when it is on the screen. click on image, and then scale image. In the dialog box that opens, choose inches in the pixes/inches box, and change the width to the width of the paper you have to print on. Make sure the height will fit, too. If not, change the height to what will fit, and the width will follow.
Then click on scale. Then print. -Joe Ward
----- Original Message -----
From: Hedley Finger
To: GIMP, Windows
Cc: GIMP, General
Sent: Sunday, September 07, 2008 10:58 PM
Subject: [gimpwin-users] Gimp won't reduce graphics to Print Size on printing

My sister-in-law sent me some JPEG photo files that displayed rather
large on the monitor and clearly were not going to fit the photo paper I
had available. I opened both Image Size and Print Size and changed the
resolution from 90dpi to 300dpi, whereupon the millimetre dimensions
reduced sufficiently to fit the paper.

The RGB --> CMYK printer is an Epson CX6900F multifunction that has a
page preview function. When the photos were printed, the preview showed
only a small area from the upper left corner, i.e. the size/resolution
information saved in the JPEG files had been totally ignored.
Eventually I had to use (blush!) Microsoft Photo Editor, a freebie that
comes with Windows XP.

What is going on?

Windows XP SP3, Gimp 2.4.6

Regards,
Hedley

--

Hedley Finger

28 Regent Street Camberwell VIC 3124 Australia
Tel. +61 3 9809 1229 Fax. (call phone first)
Mob. (cell) +61 412 461 558
Email. "Hedley Finger" <hfinger@...>

[Non-text portions of this message have been removed]

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-08T11:12:13Z

> Please notice that printing is essentially a device
> dependent operation, and a real nightmare to
> implement well even for very large shrink-wrap
> software development corporations.

Sure, if you want to do it extremely well, you probably might want to
take some device-specific quirks into consideration for some known
special cases.

That is not the problem with GIMP (or GTK+ actually) printing on
Windows, though. It is just broken in much more generic ways. No
device-specific knowledge is needed to make it work better.

> The implementation team has to choose just what
> range of printers in what printer families it will support,

Sorry, but this is misinformation. Flashback from Windows 3.x?

> It's a bit of a shame that MS-Windows, the world's
> majority operating system, is such a pig to program
> within, lacking most of what experienced programmers
> expect in the way of software development tools,

Of course, that is not true at all. Surely the majority of experienced
programmers *today* are experienced with Microsoft's Visual Studio? To
them it is Unix in general and Linux in particular that lack what they
("experienced programmers") expect in the way of software development
tools, i.e., Microsoft Visual Studio. Old school programmers like me
(and you?) who come from a Unix background, and still recall when Make
was a new and interesting invention, are definitely a minority.

--tml

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-08T10:54:16Z

From: Cline Frasier <misty34@...>
Date: Mon, 08 Sep 2008 06:32:13 -0400

> This printing problem is a bug in Windows version
> of Gimp 2.4.6 and 2.4.7. The only way I've been
> able to print from these versions is to experiment
> with the dpi setting in the printer dialog that
> comes up when printing. I posted the problem with
> 2.4.6 on the Gimp bug reporting list and it was
> verified as a bug. How the bug manifests itself
> during printing is a little different in 2.4.7,
> but it is still there.

Please notice that printing is essentially a device
dependent operation, and a real nightmare to
implement well even for very large shrink-wrap
software development corporations.

The implementation team has to choose just what
range of printers in what printer families it will
support, and then cater to all their quirks, at the
architecture, design, implementation, and testing
stages.

It's a bit much to expect that software built by
volunteer labor is going to match the stuff built
with big money corporate funding.

I'm guessing that someone somewhere will _always_
find that printing in GIMP doesn't work on their
particular printer, because GTK+ has not yet covered
that particular piece of hardware's quirks.

All that said, GTK+ has the opportunity to become a
"pretty good" printer library, just because it is
being used as a library by several different
application programs, focusing more attention on its
limitations.

It's a bit of a shame that MS-Windows, the world's
majority operating system, is such a pig to program
within, lacking most of what experienced programmers
expect in the way of software development tools,
that most of the open source software is developed
under *nix instead, with MS-Windows compatability
and porting almost always an afterthought.

xanthian, printer driver implementation battles:
been there, done that, Software Publishing
Corporation (makers of "Harvard Graphics"),
1988-1989.

Re: Re: Windows does not recognize file type

2008-09-08T10:39:10Z

To: gimpwin-users@...
From: Michael Rudas <m_p_rudas@...>
Date: Sun, 7 Sep 2008 20:29:27 -0700 (PDT)
Subject: [gimpwin-users] Re: Windows does not recognize file type

--- Ed (Horsefly) wrote:

>> I downloaded Gimp Help but it has a .tar file and
>> Windows will not open it.

Except for a few files which MS-Windows recognizes
as executables or dynamic link libraries, this is
conceptually the wrong viewpoint.

Windows doesn't really "open" files; the contents of
most file types are opaque to MS-Windows.

Instead, Windows keeps a table of matchups between
file extension tags and installed application
programs to handle those tagged file types.

When you tell Windows to "open" a file, what it does
instead is hand a link/handle for the file to the
application program matched to that file type, and
that application program, which does understand the
file's contents, "opens" the file.

So, if Ed had installed 7-Zip, and assigned the .tar
file tag to be opened by 7-Zip, then that's what
would happen when a *.tar file was "opened"; 7-Zip
would open it, not MS-Windows.

Similarly if Ed had installed the MS-Windows port of
the Unix tar program, and assigned it the .tar file
type to handle, opening a *.tar file would invoke
the tar program. Arguably this is a better choice,
tar has a _lot_ of options. I doubt 7-Zip has
implemented them all.

ScienceMikey wrote:
> The utility "7-Zip" handles TAR files ...
> <http://www.7-Zip.org>

You apparently missed the larger issue that Ed
downloaded the wrong files, per tml. There is
an installer for the GIMP help files that will save
Ed all that effort, so Ed shouldn't have to be
messing with the tar files, which are both not the
documentation anyway, but the raw data from which
the documents are constructed, and also not files
intended for end user consumption.

xanthian.

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-08T03:32:13Z

This printing problem is a bug in Windows version of Gimp 2.4.6 and
2.4.7. The only way I've been able to print from these versions is to
experiment with the dpi setting in the printer dialog that comes up when
printing. I posted the problem with 2.4.6 on the Gimp bug reporting list
and it was verified as a bug. How the bug manifests itself during
printing is a little different in 2.4.7, but it is still there.

Cline

Tor Lillqvist wrote:

>
> > changed the resolution from 90dpi to 300dpi, whereupon the
> millimetre dimensions
> > reduced sufficiently to fit the paper.
>
> I doubt that is necessary. The "dpi" (should be ppi) information
> inside image files is just for information, no software needs to
> actually use it. Any software that is good at printing will have
> options to ignore any "dpi" setting in the file anyway, and offer
> possibilities to scale the image to fit the paper, etc. (I assume this
> is possible in GIMP, too, but then printing in GIMP on Windows is
> broken anyway, read on.)
>
> > Eventually I had to use (blush!) Microsoft Photo Editor, a freebie that
> > comes with Windows XP.
>
> Nothing to blush about. If it works, use it. Printing on Windows is
> known to be broken in various ways in GTK+ 2.12 (GTK+ is the toolkit
> that GIMP uses). It is hopefully better in GTK+ 2.14. Until you have a
> GIMP where printing works reliably, by all means, use another
> application to print your images. If printing out images is the main
> thing you use GIMP for, and you print several times a day, GIMP is
> probably the wrong application for you anyway.
>
> --tml
>
>

[Non-text portions of this message have been removed]

Re: Gimp won't reduce graphics to Print Size on printing

2008-09-07T23:14:05Z

> changed the resolution from 90dpi to 300dpi, whereupon the millimetre dimensions
> reduced sufficiently to fit the paper.

I doubt that is necessary. The "dpi" (should be ppi) information
inside image files is just for information, no software needs to
actually use it. Any software that is good at printing will have
options to ignore any "dpi" setting in the file anyway, and offer
possibilities to scale the image to fit the paper, etc. (I assume this
is possible in GIMP, too, but then printing in GIMP on Windows is
broken anyway, read on.)

> Eventually I had to use (blush!) Microsoft Photo Editor, a freebie that
> comes with Windows XP.

Nothing to blush about. If it works, use it. Printing on Windows is
known to be broken in various ways in GTK+ 2.12 (GTK+ is the toolkit
that GIMP uses). It is hopefully better in GTK+ 2.14. Until you have a
GIMP where printing works reliably, by all means, use another
application to print your images. If printing out images is the main
thing you use GIMP for, and you print several times a day, GIMP is
probably the wrong application for you anyway.

--tml

Re: Windows does not recognize file type

2008-09-07T20:29:27Z

I just realized that I left out some useful information in my earlier post on this subject, so this is a re-post with the missing information added at the end. Sorry about that...

--- Ed (Horsefly) wrote:

> I downloaded Gimp Help but it has a .tar file
> and Windows will not open it.

The utility "7-Zip" handles TAR files and a LOT more (including a bare-bones-but-useful file manager) -- one of the reasons it's the very first thing I install on EVERY Windows-based PC that I touch.

After installation, go to the Tools-->Options menu, check "Select All" then deselect .ISO -- click "OK" and you are good-to-go (it can look inside .iso files, a useful feature but you don't want it to be the default tool for them).

<http://www.7-Zip.org>

Added:
the 7-Zip file manager bypasses Windows Explorer. While this means that some functions provided by Explorer are not available, this CAN be useful; Explorer sometimes "lies" about the file system. 7-Zip's file-copy mode is sometimes faster than Windows' own, as well. The function key [F9] toggles the single-pane / dual-pane file-view modes. I usually use the dual-pane view.

~~ ScienceMikey

Gimp won't reduce graphics to Print Size on printing

2008-09-07T19:58:36Z

My sister-in-law sent me some JPEG photo files that displayed rather
large on the monitor and clearly were not going to fit the photo paper I
had available. I opened both Image Size and Print Size and changed the
resolution from 90dpi to 300dpi, whereupon the millimetre dimensions
reduced sufficiently to fit the paper.

The RGB --> CMYK printer is an Epson CX6900F multifunction that has a
page preview function. When the photos were printed, the preview showed
only a small area from the upper left corner, i.e. the size/resolution
information saved in the JPEG files had been totally ignored.
Eventually I had to use (blush!) Microsoft Photo Editor, a freebie that
comes with Windows XP.

What is going on?

Windows XP SP3, Gimp 2.4.6

Regards,
Hedley

--

Hedley Finger

28 Regent Street Camberwell VIC 3124 Australia
Tel. +61 3 9809 1229 Fax. (call phone first)
Mob. (cell) +61 412 461 558
Email. "Hedley Finger" <hfinger@...>

Re: Re: Windows does not recognize file type

2008-09-06T11:51:11Z

> The utility "7-Zip" handles TAR files

In this case unpacking the tar (or tar.bz2, actually, I think) file
will not help, though. What the tar file sontains is the *sources* of
the documentation, as a myriad of files in an XML format that is not
useful for end-users.

Sure, the text on the http://www.gimp.org/downloads/ page (from which
I guess the original poster found what he thought were "help files")
could be made even more explicit to avoid confusion...

--tml

Re: Re: Windows does not recognize file type

2008-09-06T10:46:02Z

thank you so much, i will load those programs right away.

----- Original Message ----
From: Michael Rudas <m_p_rudas@...>
To: gimpwin-users@...
Sent: Friday, September 5, 2008 7:05:14 PM
Subject: [gimpwin-users] Re: Windows does not recognize file type

--- Ed (Horsefly) wrote:

> I downloaded Gimp Help but it has a .tar file
> and Windows will not open it.

The utility "7-Zip" handles TAR files and a LOT more (including a bare-bones-but- useful file manager) -- one of the reasons it's the very first thing I install on EVERY Windows-based PC that I touch.

After installation, go to the Tools-->Options menu, check "Select All" then deselect .ISO -- click "OK" and you are good-to-go (it can look inside .iso files, a useful feature but you don't want it to be the default tool for them).

http://www.7- Zip.org

~~ ScienceMikey

[Non-text portions of this message have been removed]

Re: new to gimp

2008-09-06T10:45:06Z

thank you very much!

----- Original Message ----
From: Sonny Vaughn <wood_n_rose@...>
To: gimpwin-users@...
Sent: Saturday, September 6, 2008 3:31:31 AM
Subject: Re: [gimpwin-users] new to gimp

What helped me most were the podcasts on Meet The Gimp. I started with the older ones and now I'm hooked on Gimp.

--- On Fri, 9/5/08, brandy_march <ima_biggirl_ now@yahoo. com> wrote:

From: brandy_march <ima_biggirl_ now@yahoo. com>
Subject: [gimpwin-users] new to gimp
To: gimpwin-users@ yahoogroups. com
Date: Friday, September 5, 2008, 6:56 PM

hello all.
I was wondering if there was anyone who could help me get a feel for
using the gimp program.

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

Re: new to gimp

2008-09-06T05:15:01Z

--- In gimpwin-users@..., "brandy_march"
<ima_biggirl_now@...> wrote:
>
> hello all.
> I was wondering if there was anyone who could help me get a feel for
> using the gimp program.
>

meetthegimp.org/ and "Beginning Gimp from Novice to
Professional (2nd edition is out now I think)" by Akkana Peck are two
excellent sources of info.

Re: new to gimp

2008-09-06T03:31:31Z

What helped me most were the podcasts on Meet The Gimp. I started with the older ones and now I'm hooked on Gimp.

--- On Fri, 9/5/08, brandy_march <ima_biggirl_now@...> wrote:

From: brandy_march <ima_biggirl_now@...>
Subject: [gimpwin-users] new to gimp
To: gimpwin-users@...
Date: Friday, September 5, 2008, 6:56 PM

hello all.
I was wondering if there was anyone who could help me get a feel for
using the gimp program.

[Non-text portions of this message have been removed]

Re: Windows does not recognize file type

2008-09-05T19:05:14Z

--- Ed (Horsefly) wrote:

> I downloaded Gimp Help but it has a .tar file
> and Windows will not open it.

The utility "7-Zip" handles TAR files and a LOT more (including a bare-bones-but-useful file manager) -- one of the reasons it's the very first thing I install on EVERY Windows-based PC that I touch.

After installation, go to the Tools-->Options menu, check "Select All" then deselect .ISO -- click "OK" and you are good-to-go (it can look inside .iso files, a useful feature but you don't want it to be the default tool for them).

http://www.7-Zip.org

~~ ScienceMikey

new to gimp

2008-09-05T16:56:32Z

hello all.
I was wondering if there was anyone who could help me get a feel for
using the gimp program.

Re: Windows does not recognize file type

2008-09-05T07:55:16Z

You need to download "gimp-help-2-2.4.0-eng-setup.exe" from the windows
download area. Look for instructions about where it goes. I don't
remember those.

Ed wrote:
>
> I downloaded Gimp Help but it has a .tar file and windows will not
> open. How do I change the file to something windows will open so I can
> get the help files to open in Windows.
>
>

[Non-text portions of this message have been removed]

Windows does not recognize file type

2008-09-05T06:55:57Z

I downloaded Gimp Help but it has a .tar file and windows will not
open. How do I change the file to something windows will open so I can
get the help files to open in Windows.

Re: Question about posting a book

2008-09-01T07:26:23Z

> Von: "origininc" <origininc@...>

> I would like to know which person/developer to contact to sell my book on the "BOOKS ABOUT GIMP"
> page. If someone can please contact me at my personal e-mail it would
> be greately appreciated. My personal e-mail is chpkn@....

The gimp-developer mailing list would be a better place to discuss this.
You should be a bit more precise about the 'to sell my book on the "BOOKS ABOUT GIMP" page' part, though - what exactly do you have in mind?

Regards,
Michael

--
Psssst! Schon das coole Video vom GMX MultiMessenger gesehen?
Der Eine für Alle: http://www.gmx.net/de/go/messenger03