Are the contents of your divs images then?
No, they’re transcluded tiddlers with mixed content, with some wrapping information that I will eventually fold into the tiddlers. The CSS rotation applies to the entire <div>s.
If I pursue this (50-50 chance right now) I would like to make it so that I had a function with a filter parameter that used something like this:
<div class="print-brochure">
<$list filter="$filter$ +[limit[16]]" counter="page">
<div class={{{ [<counter>add[1]addprefix[brochure-page page-]] }}} >
<$transclude mode="block"/>
</div>
</$list>
</div>
This way the tiddlers don’t have to know anything about the brochure; they merely have to be small enough to comfortably fit inside the fixed dimensions they are given.
I’m using the same content I use on a web page, with two special classes: one used to hide some content from the brochure view, and the other to show it only there. I’m not thrilled with this, as it clutters up the tiddler, but I don’t want separate copies of the same material. Here’s an example:
As a member of the BOE for the past eight years, Shannon has volunteered
significant time to:
* negotiating the contracts for<span class="skip-in-brochure"> each of the
employees of AES, working with the individuals and unions;</span>
<span class="brochure-only">AES employees</span>;
* ...
so that on the web view, our candidate (who, as you might be able to tell from her prose is a lawyer), it reads
As a member of the BOE for the past eight years, Shannon has volunteered significant time to:
- negotiating the contracts for each of the employees of AES, working with the individuals and unions;
- …
But on the brochure it reads
As a member of the BOE for the past eight years, Shannon has volunteered significant time to:
- negotiating the contracts for AES employees;
- …
It’s not a wonderful solution to this issue, and I’d love to hear alternatives. But it works for now.
Overall, though, I think this will be a useful approach to creating various kinds of booklets… so long as you don’t want content to automatically flow between the pages.
Adding this in case it adds to the development. zine machine! uses grid-template-areas for the layout.
example: https://zine-machine.glitch.me/
source: Glitch :･ﾟ✧
2 Likes
It seems like you’re doing well. Even when you use a word processor, you usually have to determine content breaks manually.
Is the main difference between the two texts that the web version is longer? And it’s the awkward insertion of span tags that is the concern?
@pmario has a customised markup plugin that lets you define your own markup symbols (e.g. %%). I’m wondering if something like that could be used to apply the differences.
2 Likes
Right. I’m not worried about that for my own case, where each page is naturally its own tiddler, but some of the discussion above was about flowing text between the mini-pages.
Also, while you do have to determine them manually in a word processor, it’s much easier to simply type CTRL-Enter or backspace over it than to manually move content between two different tiddlers, often even in minor edits.
Yes and yes. Many of my mini-pages are the same between the two versions. But the longer ones have to be trimmed, and I don’t want to trim the web ones unnecessarily. I can’t think of a better way to maintain two closely related, but clearly different, texts. I was hoping someone else might have a better approach.
I was considering trying something like this, on my own, partly to better learn a part of TW that I don’t know anything about. But I was stopped by two thing: First, at the moment, it’s just a distraction from trying to get my brochure ready to print. Second, I’m not bothered too much by the markup mechanism. I’ve done HTML for more than 25 years. Throwing in a few extra <span>s isn’t worrisome. It’s the overall mechanism of the two intermingled versions I object to.
But thank you for the pointer. I may try it out, because while I don’t mind writing the text in this manner, reading it is less pleasant.
1 Like
That might help. I’ll have to check. The 90° rotations are my biggest banes. I think theoretically, this should be simpler than the matrices, using transform-origin, but I haven’t worked that out. This does show me something I really should have thought about: I could do the simpler 180° rotations if I printed in landscape mode! D’oh! Time pressure can really mess with me.
All of us I expect.
Exporting as html and importing to word or another wordprocessor for final print preperation is a desperate approach I have used in the past.
This is what I do with my shopping list. Copy/paste from TW. (Copy/Paste so that an existing template can be used). Format headers, align pages. It takes about 3 minutes.
Word processors understand physical pages and how to flow text from one page to another. So … they’re really a pragmatic choice.
That’s been my usual technique for similar non-TW situations. I thought I might be able to do better with the facilities offered by TW, and it looks like I can. I’ve gotten content for two of my three missing tiddlers. It will be trivial this evening to create a new version: close the other tiddlers and print. That’s much nicer than my usual paste-to-word-processor-and-fiddle-with-margins routine.
If I find time and mental capacity, I’ll try to wrap this together in a more useful format so others can use it too.
They are reasonable if the brochure (or whatever) is your main output. For me, the content is already in TW, so if I can get this to work, I can reuse it over the years for any small micro-paged content I want to print. The thing with these foldable brochures is that we need not only to flow content, but also to rotate and position it in different ways.
I’m referring to the process:
TW → WP → PDF → Script → PDF
If you can come up with a process that goes
TW → PDF
That’s super of course, but I seem to recall the reason I didn’t use the TW Classic kit much was exactly because of the overflow problem between tiddlers. (Back then we were able to download the flash executable, I think).
In your case, you probably have one-tiddler-one-person, which fits naturally with a multiple page output. But if your input is long form (e.g. a shopping list) then you’d have to redistribute the output every time you used it, since the contents will change weekly.
Did SplitTextIntoTiddlers every reach a level appropriate for flowing the content?
Absolutely. I don’t have any suggested TW fixes for when the content is supposed to flow from one container to another. I can think of a somewhat inefficient pure JS technique that might work, but a TW version is well beyond my current skills.
I am curious about these steps:
PDF → Script → PDF
What do they encompass?
1 Like