Would anyone be able to quickly summarise the subtle differences (apart from having the option to enable pinch/zoom) between these folio types. I have a multi-folio app on Newsstand which uses JPG folios but am keen to switch to PDF for the next issue. We use all overlay types and want to target problems early! Thanks
Thanks Bob. There was something in one of Johannes threads that prompted me to post. File size is always of huge importance so looking forward to shedding a couple of pounds from my app. So all overlays function correctly etc?
Here are the differences between PDF and JPG/PNG articles that I'm aware of:
* PDF is not supported for Smooth Scrolling articles, even if you specify the PDF image format. For memory reasons, JPG or PNG is used instead. Enabling PDF for Smooth Scrolling articles is on the roadmap.
* It sometimes takes a moment for a PDF article to come into focus, especially on the iPad 1. With iOS 5.1, this load delay is rare, at least in my experience.
* PDF articles are not supported on Android devices. If a folio includes a single PDF article, it won't load in the viewer on a mobile device.
* Pages in PDF articles can pinch & zoom if enabled in Viewer Builder.
* The thumbnail previews of PDF articles do not appear in the Folio Producer Editor.
* Overlays should look and function the same whether PDF, JPG, or PNG. When you zoom in on an overlay in a PDF article, pixelation might be noticeable, but that's expected.
Unfortunatley I'm not seeing any benefit when creating PDF folios. Infact they appear to weigh more that my JPG/high folios.
Here's a grab from Acrobat.com of duplicate, single article folios (minimal interactivity with severl MSO's performing show/hide functions and a few hyperlinks to the HTMLResources which don't work!?).
The JPG one is smaller in size…
I haven't published with PDF folios yet, I was testing a HD rendition on a 2048 folio set to PDF (same single article as you see here) and it showed a download weight of 21mb.
I can only assume I'm doing something very wrong or I have troubled system.
DPS tool versions are all up to date.
InDesgin version - CS5.5 (188.8.131.524)
PDF doesn't work with Smooth Scrolling articles. Here's a link that explains all the differences I'm aware of:
Hi Martin, I'm getting it from Acrobat.com. Access it from the DPS dashboard. Should be top right, icon that looks like four little squares. One of the drop downs will be Acrobat. If you've published our are holding any folios you can find them there, just right click and turn on file into.
Is there an easy way to convert an article that has been previously uploaded as PDF, to PNG/JPG? It seems like I have to delete and upload again fresh.
I have uploaded many articles and think I should have selected PNG/Automatic - but all the properties have been carefully entered.
If I understand your question correctly - PDF's with overlays are supported starting from v.18, see here:
This is a question to everyone, now more tricky one:
In case of PDF folios, can there be a better way to create internal cross-links (navto), other than making them manually?
I mean, if these links (such as footnotes, indexes, etc) were already created in InDesign, and will remain if document is exported as regular PDF, maybe they can be somehow inherited by PDF folio articles?
Serge, there really isn't special PDF abilities. PDF is really just an image format in this scenario. It adds pinch to zoom over the other formats, and that's it. Not to say that'll always be the case, but that's the current case.
No, that is not my question. I'll elaborate: the pdf format render beautiful text and vector imagery - but only if this text/illustrations aren't in an overlay. If you put text within a scrollable frame, it is turned into an image (png or jpeg, don't know, but guess png). If you do a slideshow of a bunch of vector logos, they are all turned into pixel images. If you turn a graphic containing text into a button, the text is also pixelised. So ... when zooming in, 'static' text is beautiful pdf, overlay text is pixels. So, will Adobe change this, and render overlay content as pdf?