Would be great to an enhanced floating within tables.

I regularly use tables, and right now I don't have any control on how rows are handled that would float across two pages. Currently, they are just put on the next page an leave an empty space on the prior page.

Would be great to an enhanced floating within tables.

I regularly use tables, and right now I don't have any control on how rows are handled that would float across two pages. Currently, they are just put on the next page an leave an empty space on the prior page.

Currently, the enterprise-level Adobe LiveCycle ES product allows users to embed advanced DRM restrictions to their PDFs - printing, copying, and time limits are all supported. A major component of this is a 'policy server' which can be set up locally or by Adobe to monitor the ongoing usage of DRM-enabled PDFs. The end user is notified via a dialogue box that the author of the file is monitoring its usage.

Given the explosive growth of personal publishing via the web (ebooks, blogging, etc), I think there's a great case for making these capabilities available to non-enterprise content authors. You could easily set up a web services situation that would allow a blogger to pay a monthly fee for the ability to monitor and better restrict his/her ebook usage.

Another example: a small business publishes a short guide/ebook that they wish to license out to other organizations. For a small monthly fee, the licensee can print as many copies as they want of the ebook. By allowing that licens

1. Provide complete control of document versions in a hierarchical stack 
2. Users can access the complete version history of a document and view the content of previous versions
3. Users can send a guest user a single "static" document link, when a document is updated on Acrobat.com that guest user will automatically view the latest version of that document (regardless of how many changes where made to the original  --- since the link always points to the latest version.
4. Implementing a hierarchical stack will prevent updates to 'older' document version by limiting the initial view to only the most up-to-date version; while still allowing the user to access/view older document versions as needed.
5. Document versions should include: last updated by "name"; date/time stamp
6. Set Up "levels of permissions" on a document or folder: view only, edit, delete, etc...
7. Allow files to be stored and grouped in folders and subfolders, also with static hyperlinks, and permission levels
8. Allow customized sorting of d

Just like you have with an SCM system, it would be cool to have version control capabilities in Buzzword.  So you'd be able to visually compare two versions of a document and see what has changed from version to version.  Then if you wanted to you could rollback to a previous version of merge two versions.  This becomes necessary when you have multiple people editing the same document.  Sometimes the document changes, but I don't have a good grasp on exactly what has changed since the last time or who made the changes.  I would want to see who made what changes when and then take actions as necessary.

This would be similar to how eRoom maintains document edit history or how P4 does source control. 

This will allow a user to view doc history, diff, revert etc. 

For shared documents document history will also maintain history of which user made which change, who has viewed the document, edited the document, is yet to see (if the document is shared explicitly with a set of people).

This will set the stage, after more features are added, to provide an alternate to eRoom, Confluence etc.