I've automated via actions and a macro to save out a single PSD setup for animation as a GIF in 11 different languages. The languages are defined within the source PSDs on layers. There are about 70 PSDs in total with different dimensions (same animation) but different composition based on dimensions - The actions turn on and off said layers and export.
Actions:
Turn off layer (language one)
Turn on layer (language two)
>Export (with dialog on)
Macro takes over and appends an underscore and a 2 character code for language like _EN at the end of the file name for language. Then saves.
The actions repeat until the full run of languages are exported. 11 in total for 70+ PSDs
My biggest hangup is that I have to save the GIFs to a particular file size limit - Like 300kb for example. So for each PSD with a particular dimension - I set up the file previous to exporting, then "Save for Web", Optimize, and click Done to bake the optimization into the PSD. Which works great. All I have to do then is run my action once and run a macro - then sit back until it completes. What I have noticed is that having to have the dialog window come up for "Save for Web" can take at times, minutes to fully show as it tries to preview. Which eats up a lot of time throughout the entire process.
The problem I face is that I have to invoke the "Save for Web" dialog box for each language so that the macro can take over, and append the lang code at the end of the filename along with keeping the baked in optimization setting for each PSD.
I have used the ScriptListener to see whats going on to try and script some of this process to bypass the "Save for Web" dialog window. But every time I try to test it out based on the JS that's spit out.. The baked in optimization settings are no longer used.
I'm not looking for someone to write the code for me, but rather some direction on how I could potentially achieve a more streamlined way. That said I'm not a coder, but am not afraid to get my hands dirty.
If I could remove the use of macros for file naming and the "save for web" dialog window I could shave hours off this daunting process. I have used variable datasets for another case where just text is changed, and when exporting animated GIF without any file size limitations - I was able to generate updated PSDs, and export animated GIFs (with no use of the "save for web" dialog window) in under 10 minutes. So it got me thinking I could potentially refine my other process further and save heaps of time. There doesn't seem to be a lot of information with scripting the "Save for Web" for animated GIFs with saved settings. Any information on this would be greatly appreciated.
Thanks!
Chris