Glad to see you got it working PC... Congrats!

If a earthquake now stroke Microsoft headquarties and a big roasting hole devours Bill Gates and all the 7 kinfolk , that may mean that my curses had some pratical effects

On a level, on the OS layer accessible by enviromenthal path controls "Program Files" is the only to be real, all its alias used on computer sold in not english speaking country are unknown.

But on the other level on the layer accessible to most of software is "program Files" that doesn't exist, and only the local translation, the alias used in not english computer it is the only that will work.

I hope that the Hell offers a adeguate punishment for who design and who approve such design

Partha a new problem show up :
moving back gimp 2.6 nothing works anymore now is gimp 2.6 that can't found its own dll

i suppose i may solve installing the portable version of 2.6 but doing that i would not be able to use python filters (it seems that in the portable support for python is just disabled )

And i believe this a additional reason to explore the possibility to pack 2.7.2 as a portable app

PC,

I believe this is related to what you posted before about not having any path variables set. Gimp 2.6 is no different in terms of installation. It is probably installed in Program Files and you have to make the same changes for it that you did for gimp 2.7.2. Is what I say here correct on your computer? Where is gimp 2.6 installed on your computer?

That was the same gimp that was working before i just moved out on a storage disk and moved back after installing 2.7

Anyway as always portable apps are the solution to solve this without headaches

Just installed gimp2.6.11 portable and now everthing works as a charm

Only pain portable has support for python disabled

And again i believe that repack 2.7 as portable will avoid to others the pain to have to first remove the stable gimp, then fight with enviromental variables, then have to edit py-something files and so on...
really the portable solved all in a heartbeat,
and gimpportable is done exactly with the same binary is just a different way to package

Hi,

I have seen screen shorts of GIMP 2.7.2 by Rod here with the FX-foundry, Fu-script in the main menu bar.

How can I also have them in there?

Installing the scripts as in the stable version

PC is correct just download the FX-Foundry script package and install all the SCM files in your scripts folder as normal.All the scripts are written to create that menu item.
You can download the script batch here -
http://sourceforge.net/projects/gimpfx- ... p/download

Oh i believe i can get you setup with Python PC.
Take a look at how gimp-2.7.2 is setup for python inside its sub directories and you will figure it out too i am certain.If you need help PM me.

Partha uploaded a new 64 bit version "portable"
that for me solved all problems (and remove the need to edit path and files )

Very cool
I was going to say i could upload my setup, but it's 32 bit anyways.
Glad to hear all is good.

Hi,

Thanx the info and the link. I will try that.

Anyone here know why GIMP 2.7x can't open SVG files? Any solutions.

As an added plus try and make your new doc the same size as your svg you will be opening.

Not all SVGs are path only rod (have fills too). For GIMP 2.6.11 (and previous versions that support SVG), all I had to do was drag an SVG into GIMP.

you are right the file svg plugin is vanished
I suppose was already MIA in the code used by Partha to compile

I may be wrong , not sure how confront the 2 list, but confronting with what i see in 2.6,
i believe some other file conversion plugin went missed in 2.7.3

I think the file-svg needs to be re-compiled for 2.7.3
As well as a new librsvg.dll for it too.

I asked Partha about this on his comments board.Maybe he will look into it.
Cross your fingers.

The Gimp 2.7.3 missing file file-svg.exe.
His addition necessitates the complete much libraries: libinitl; libgimpui, libcroco, libxml, libgsf, librsvg (and more )....
After they complete (all in Program Files \ ... \ plug-ins) it works (although with the message)