I don't think anyone is going to storm out of the meeting over it though. I'm often presented with a paper copy of a presentation which is all in black and white yet the presentation was given in colour and somehow I manage to scrape though. Even when people don't bother putting legends on their graphs (and most don't).


That could be an issue admittedly, if you were hoping to edit the object on the iPad. If you weren't, presuming the objects at least remain correct in relation to each other therefore the effect would be fairly minimal. If it actually displaces parts of the group in the import process then obviously it's a massive pain in the rear.


I generally find automatically generated ToC's need tinkering with anyway so I tend to leave them to the end. So, for me at least, a document I was part way through editing wouldn't have a ToC to mess up.


Yep, this is a problem. Losing content (as oppose to just munging it in some way) surely isn't something two products from the same company using the same file format should do between them.

Jon

No, but it looks naff and amateurish if the printout looks "better" than the live demonstration...


Yep, or just before the presentation, you notice that the "object" is overlapping a bit of text, having to move dozens or hundreds of objects a few pixels, instead of a single object would be a pain.


I've been using ToCs in Word since the early 90s and can't say I've ever really experienced any problems with them...

So true.

Fair enough. It does illustrate a little though that the impact of the limitations of iPad iWorks maybe quite... granular depending on exactly what features of the apps you generally use, which I assume stems from what sort of content you're creating.

TBH I've never really seen Pages as a tool for creating heavyweight documents - you wouldn't want to write a book or technical manual with it, although you could do a novella or magazine. Nor would (I suspect) you want to be doing that sort of thing on an iPad either.

It does seem odd though that two versions of the same application from the same company running on what is effectively the same OS do have differences. You'd think a lot of it was purely being done in Core Image or Core text, which you'd immediately assume was pretty much hardware independent.

Jon