You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This plugin would be brilliant and indispensable, but now it is despicable!
Why can't the
"Export Type" be made relative to the "Set Namespace"? - rather than some larger unknown concept that seems to generate the entire file with all pages? Then maybe it would be easier and not fail because fewer pages will be processed. This setup is just plain brain dead.
Set Namespace: opencpn:opencpn_user_manual:toc_offline_plugins_manual Parent Namespace to export: opencpn:opencpn_user_manual:toc_offline_plugins_manual Export Type: Provide a setting here that is RELATIVE to the SET NAMESPACE, such as
"All subnamespaces from "toc_offline_plugins_manual" down"
"Specified depth from "**"toc_offline_plugins_manual" down" Depth: say 5
Currently the plugin is NOT doing this! It is starting at the very top at "openpn:opencpn_user_manual" and working its way down. I don't need or want all that for this operation.
Furthermore using
Render: ckedit or xhtml it still runs through all 311 pages and fails at page 60.
I only need 48 pages to complete for the plugins manual.
When making PDF docs, - The links should be made internal for offline use, the plugin is making the PDF pages but the links are not being properly made. This appears to work for xhtml and ckedit when doing html exports.
EXCLUDES: Also we need a nice big full page area to allow us to organize and SEE all excludes!
ADDITIONALLY: Am I supposed to EXCLUDE all pages that I don't want exported just because this stupid plugin isn't smart enough to export only pages relative to the "SET NAMESPACE"?
These problems have been around long enough so someone should have fixed them!
I've certainly reported them for at least two years.
I have reported my recent experiments here:
https://forum.dokuwiki.org/thread/15645
There is a list of issues in this post.
The text was updated successfully, but these errors were encountered: