I have a bunch of images in which I need to export each one as png files with heights 32,48,72, and 96.
Is there a way to automate this process?

mickeydog wrote:I have a bunch of images in which I need to export each one as png files with heights 32,48,72, and 96.
Is there a way to automate this process?

Yes, in a command line, type:

Replace the both of the 32 in the above for different sizes.

Thanks for your reply.

If I interpret that statement correctly, it will set both the width and height to 32, correct?
In my case, I want the height to be 32, but width will vary. So can I do this:

and the width will be proportionally changed?

I think it will but there is nothing I can find in the documentation that says it will. Try It To See (TITS).

Ok, I'm trying it but can't execute the command Inkscape, saying Command not found. I'm on OS X, so in the .profile I added Applications folder to the PATH:

but that didn't help. Do you happen to work on OS X and know what to do ?

If I add /Applications/Inkscape.app/Contents/MacOS/ to the PATH in .profile, I can then execute Inkscape from the command line

mickeydog wrote:If I add /Applications/Inkscape.app/Contents/MacOS/ to the PATH in .profile, I can then execute Inkscape from the command line

It won't work like this with the bundled Mac OS X application.


This will:

1. Use this script inside the application bundle to run inkscape on the command with arguments:

   Code: Select all

   /Applications/Inkscape.app/Contents/Resources/script
   (this is a shell script wrapper which correctly sets up the environment for the inkscape binary included in the application bundle)
2. Always reference files with absolute path names (that's a limitation due to the bundle architecture, and differs from how inkscape is used on the command line on other platforms, or with regular command line builds on OS X)
3. Ignore warnings like e.g.

   Code: Select all

   Setting Language: .UTF-8

(process:75235): Gtk-WARNING **: Locale not supported by C library.
   Using the fallback 'C' locale.

   They usually are harmless and do not affect the result.

Example:

Tip: Instead of appending to $PATH in ~/.profile, create an alias to the script (in ~/.bashrc):

Thanks for all the help! This was much more involved than I had thought it would be.

I have a fairly long script now. It looks something like this:


It basically works, but it is erratic in that some of the files get created and some don't. I wonder if I have to wait for the completion of one line before starting to execute the next. Is this the problem? and if so, how do I wait for a command line to complete?

You could try something like this. This is for the bash(1) shell.


Note that each of the PNG files have their size as part of the file name.

>>Note that each of the PNG files have their size as part of the file name.
That is undesirable in this situation and I am not sure that this addresses whatever issue I'm having. Please explain if it does. The script really looks more like below, in which exported files of the same name are written to different directories.