Great job, Bob / Henseler

I believe that next DPS could give us the option to choose the pinch/zoom in articles

Because, some publishers dosen´t want to use zoom and now PDF format always get zoom.

Regards

Sure! I forgot it

Jim,

yes I am pretty sure this changed with v19. I think I can remember that

text wasnt sharp until you zoomed in a little.

v19 definetly does show text fine and crisp — unfortunately, the viewer

isn't approved yet by apple, so you should wait to update if you are no pro

& enterprise customer.

—Johannes

Thanks Bob for so clearly answering my question.

Much appreciated!
Paul

I just had the same issue as Casey.

Built a 2048 layout. Created the 2048 folio and a 1024 rendition. The 1024 shows up solo on the iPad2. At first the 2048 shows up solo on the iPad3, but then after restarting the custom viewer, the 1024 appears there as well.

Any advice on what Im doing wrong (Im new to renditions)?

Casey Jensen wrote:
 
I also noticed, using renditions on at least one occasion, that after you download a folio (say the 2048x1536 rendition on an iPad3, as an example.), the next time you launch your Content Viewer/it refreshes library, the other rendition suddenly becomes available. Why is this? And would this happen in a Production Viewer/App as well?
(It is happening with one of my 2 rendition examples.)

UPDATE: Updating seems to have done the trick.

Thanks for the speedy reply, Casey. Also glad to know Im not the only one working on a too sunny Saturday!

I thought I had the latest, but I gues not. Thanks again!

dw

Casey Jensen wrote:

 

It was a bug that has subsequently been patched. If you re-build with the latest v19 viewer from Viewer Builder, you shouldn't run into the issue. (what I've been told -- haven't confirmed it yet.)

I've noticed a big difference in PDF text between Drop 18 and Drop 19 viewers. Drop 18 viewers seem to behave as you described - the text still looks like crap unless you zoom in slightly and force a redraw.

On drop 19, on the other hand, text looks pretty crisp in general. The last I checked the public content viewer is still drop 18.

I still need to do more testing on the iPad 3 but as DPS trainer I am looking at many of the projects I have created with delegates over the past couple of months specifically for the iPad1/2 and I am seriously struggling to see any significant differences on the iPad 3. I accept there are differences but for the 'man in the street' to spot them it will be difficult. I am working on one personel project that I am planning to publish via the Single Edition option and was concerned that I would have to rebuild the project to accommodate the iPad 3 viewers, well on close examination the answer is no, it looks just as good on an iPad 3 as it does on an iPad 1 - the articles are in standard format, not pdf but I am using a lot of vector based components.

I tested a new article on both iPad2 and 3.

I'm using v19 producer tools

Document: 1024x768

Folio: 2048x1536

Both folio and article image format: PDF

No interactivities what so ever

Previewed on my own v19 viewer

I took a screenshot of what I get:

http://www.japan-square.be/newsletter/bart/retina.PNG

When you zoom in just a tad, the ipad3 refreshes and shows crisp text. But if you don't it stays as pixelated. And you really see it.

http://www.japan-square.be/newsletter/bart/zoom.PNG

(Be sure to copy/paste the url in the browser so the forum doesn't scale it down.)

I was expecting pixelated images, but nice text.

Seeing Johannes Henseler's iPad3 tests on this forum, I was imagining the same quality... Can someone tell me if I'm missing something? I am willing to accept that this is normal and the problem is just my expectations ;-)

But I just need to be sure for when I'm giving support to our DPS customers.

Thank you

I was doing an iPad3 "exclusive" test because it was the first time using the 2048x1536 folio format. But if I understand correctly:

- text should look fine (if it's PDF)

- images can look awesome (if they're given the right amount of pixels, which in this case is not)

I reinstalled my viewer builder and am recreating my v19 viewer, just to be sure. After that I'll retry.

Thanks for the quick update, Bob.