OK… it seems I have my Chrome browser’s “translate…” setting to “always translate spanish”… so it is just happening automagically. But this setting doesn’t seem to apply to the preview window, so that just appears as untranslated Spanish.
-e
I haven’t yet given the TiddlyTools version a spin, but have spent some time looking at the button code as posted on the other thread (We need a core macro similar to the toc macro to transclude all hierarchical content - #3 by EricShulman)… and tweaking it to accommodate various additional needs.
Disclaimer: I’m not the target market for this plugin (since I already have complex solutions for various print-oriented workflows), but I’ll share my notes in case it’s helpful for others.
Still, I thought I’d follow up with the point that under some conditions, it may be more effective to set up a sequence to replace the story-river with your desired filter-set of tiddlers/nodes, hide the sidebar, and print from there. In particular, a solution that relies on packing content into a separate window may not be ideal if…
- If you need tiddlers to be differentially responsive to body template cascade (for example, being responsive to
code-body[yes]condition) - If you need to see caption rather than title (or otherwise render title with csacade)
- If you need tiddlers to print with templates beyond the basic body template (such as automatic tag templates showing content for
[<currentTiddler>tagging[]]even if it’s a virtual node), subtitle (could be important for printouts of documents where the modifier/modified fields need to be present for easily checking whether this printout really has the most up-to-date version of Tiddler XYZ), introduction/warning template that would appear above body, or feedback/notes/comments in a special view template that would normally appear below student work, etc. - If you rely on webfonts or other css-based solutions that (by default) would not appear in the separate window.
I hope all this is not taken to detract from the work by @EricShulman!
I think it simply shows how much “print a list of tiddlers” is not necessarily as straightforward as it sounds!
Although it’s not at all perfect, I’ll share the variant I was tinkering with. It surely is missing all the print-oriented goodies that show up in Eric’s thorough solution. The main difference (from the button-version in earlier post today) is that I’ve opted to transclude with {{||$:/core/ui/ViewTemplate/body}} and to add in some other (conditionally-framed) view templates. I also tucked each tiddler’s content into a details widget so that user can collapse a verbose or non-needed tiddler prior to printing (though it still has a page break before each tiddler, so it saves paper only if the collapsed tiddler is a multi-pager).
I’ve updated TiddlyTools/PrintTiddler with a new feature:
- Added a “date”
$checkboxto optionally display the current time/date in the bottom-left margin of each output page
-e
2 Likes