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
The idea behind the "Print entire section" feature us great. I was researching it for the purpose of PDF creation where it makes it easy to use whatever PDF converter you like, even automation, in an elegant way. Unfortunately, I found out a pretty major deficiency - it keeps the links unchanged, meaning they point to pages outside the _print page. It doesn't make a difference when printing on paper, but when printing to PDF (which, I guess, is far more common nowadays), it means loosing functionality and context. This, with the presence of broken links, makes the resulting PDF completely unfit for professional use like handing over to customers.
What would it take to redo the links so that they work within the context of the monolithic _print page?
I understand this might not be everybody's cup of tee, so it could be a configuration option.
It will require generating ids for headings that don't already have them. For the anchor links, simply dropping the URL part preceding the hash sign won't do, as multiple of the original pages might use the same ids. These will have to be replaced by autogenerated UUIDs or prefixed/suffixed with something to make them unique.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
DL;DR: Need working links in print mode.
Long version:
The idea behind the "Print entire section" feature us great. I was researching it for the purpose of PDF creation where it makes it easy to use whatever PDF converter you like, even automation, in an elegant way. Unfortunately, I found out a pretty major deficiency - it keeps the links unchanged, meaning they point to pages outside the
_print
page. It doesn't make a difference when printing on paper, but when printing to PDF (which, I guess, is far more common nowadays), it means loosing functionality and context. This, with the presence of broken links, makes the resulting PDF completely unfit for professional use like handing over to customers.What would it take to redo the links so that they work within the context of the monolithic
_print
page?I understand this might not be everybody's cup of tee, so it could be a configuration option.
It will require generating
id
s for headings that don't already have them. For the anchor links, simply dropping the URL part preceding the hash sign won't do, as multiple of the original pages might use the sameid
s. These will have to be replaced by autogenerated UUIDs or prefixed/suffixed with something to make them unique.Beta Was this translation helpful? Give feedback.
All reactions