My bias towards pdf is possibly because I'm not the primary coder of our product. Therefore quite often if I am writing code I need to check the documentation and read the information to make sure understood it correctly. For example if I was looking to use the command distinct values. In the V 11 documentation PDF you could go to the table of contents and look up the command and the page number. In the new version you cannot do this there is no list of commands in the current pdf docs.
The new versions of the documentation be HTML or PDF are simply not as good as the old ones. The fonts are poor particularly if you are longsighted like me. Navigating the HTML versions is not as good as PDF. The main reason is as you navigate through the hierarchical list you lose the ability to expand and collapse the bookmarks. Therefore you are continually having to go back through the hierarchy to read another command. With the PDF version the bookmarks are way better than anything in HTML. This improves the readability. It is such a simple issue to generate the PDF documentation with decent fonts I am perplexed as to why this is not been done. Paul -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
