PHK wrote: ↑Sun Jun 07, 2026 10:16 am
@gwideman.
The manual tends (i) to lag update enhancements and (ii) is not 100% comprehensive.
I appreciate you taking the time to comment, and it's good to hear the level of affection you have for the product -- that's a good sign.
That said, this is hardly a "latest enhancement" -- the forum thread that I referenced that displayed the parent-child bookmark rules feature (but didn't explain how to operate it) is from October 2020. That's 23 internet years ago!
PHK wrote: ↑Sun Jun 07, 2026 10:16 am
With regard to (ii), in fairness there are so many subtle capabilities of the product which I hope you as new user will come to appreciate,
Within the "Generate Bookmarks", the ability to impose a hierarchy on them is a core requirement, not a "subtle capability".
Sure, I can appreciate in-depth features (and there is much to like about PDF-XChange), but I also appreciate that wonderful features that are both missing discoverablity in the UI, and are not documented, might as well not be there for users, such as myself, who will use many different software packages as occasional tools.
> that it might be too much for a completely comprehensive manual. IMHO, the Manual strikes a fair
> balance between comprehensiveness and bloat. The Bible is somewhat like that. Or vice versa.
[/quote]
Well, it's a bit off topic, but.... the manual, while quite lengthy and detailed (despite omitting the crucial info on this particular topic) could be slimmed down considerably by editing out a lot of needless visual noise and repetition, such as "The Page Zoom toolbar is used to determine the zoom level", or documentation of the many buttons on a dialog, consisting of bullet points all starting with "Click [named button] to..." Probably we don't need to be told that Click is the way to operate a button, and meanwhile, the actual function, the thing the user might be looking to do, is visually buried later in the sentence... though, disappointingly, the eye, having found the actual content, discovers it's little more than a repetition of the name of the button.
That style of documentation follows an algorithm (explicit or implicit) to conscientiously ensure something is said about every single conspicuous element on the UI. But it doesn't coherently organize the presentation around typical workflow that the user might reasonably want to perform, and describe what considerations there are, and what steps with which UI elements would be involved to accomplish the task. So, good job mentioning every UI element. But this (a) leaves it up to the user to figure out how to compose UI steps into a complete accomplishment, and (b) fails to uncover areas where
information for completing the task has been overlooked.
This is the situation with the Generate Bookmarks docs. There is no discussion of "when you generate bookmarks from text, here are typical workflows you would follow [blah blah blah] ... and you will probably want multiple levels of bookmarks, which you can arrange using these UI maneuvers". Instead, there's no obvious UI element associated with making the bookmarks hierarchical (for example indent arrows), so the "document every UI element" doc procedure didn't find anything to document. (Obviously a bit of speculation on my part... from other experiences!)
Regardless, it is what it is, and I'll continue to refine my "appreciation" as I go along
Thanks again for your encouraging comments.