I was wondering if anyone knew if it was possible to open up the folio file after bundling and change some of the assets?
Basically the PNG compression for MSO's is ridiculous so it adds a stupid amount of data weight to the folios,
I can see into the folio package but this means expanding it, with no way to rebundle...
So.. I was wondering if you could get into the folio file change the PNG's to those of a lower file size but leave the folio package undamaged?
@Tim – basically the folio file is a zip archive file.
You could experiment with that.
Should I recommend that?
There is the danger that you wreck your folio and have to built it anew…
For testing purposes?
Sure, give it a try…
And report back here how it went…
I will give it a go and let you know how it goes,
I'm struggling to find the folio files stored locally, I've followed the path to "local store" on one machine, but on my laptop where I run Lion I get stuck at
Library > Preference > then I cannot find Stage Manager
Uploading/Exporting your folios as PDF instead of PNG's from Indesign to dashboard will make the folio size very light. Try this and see the difference. Otherwise in my opinion, trying to manipulate the folios after built is not a good idea. You can certainly try and do the testing though :-)
I understand that yes, but my point is after we set the document to export as PDF, Multi-State Objects and certain interactivity is written by inDesign as PNG - which become very data heavy files - So my original question was after exporting folio's as PDF and finding that PNG's are packaged, is there anyway to change them to a lighter file type after
but apparently not
@Tim – strange, that you cannot find the User/Library/Preferences/StageManager.BD followed by a large string with numbers a dot and a number.
You can't edit folios after the fact as you're trying to do.
@Bob Bringhurst – why is that? Any technical reasons? A folio file seems nothing but a special zip-file one could open with eg. Springy…
Or is there a deep relationship with the afc.db file one would destroy after editing?
I can't speak for why this is the behavior, but there is a checksum on the exported zip. If you unzip the package, edit some things, and rezip, Viewer Builder will not recognize it as a valid package.
Thanks for the insight guys, you've saved me a bit of testing!!!
regarding why there is a checksum I also presume that security is a large issue - if someone could rezip a folio with something naughty inside it the adobe server might not be too happy but anyway - the process of unzipping and rezipping is only an option because the content bundler doesn't have enough export options for MSO to keep the data weight down at the minute, I'm sure something will happen soon to rectify that!