Looking for writing-related posts? Check out my new writing blog, www.larrykollar.com!

Monday, April 10, 2017 2 comments

The Brass Mechanism, episode 6

Part 1 | Part 2 | Part 3 | Part 4 | Part 5

Difference engine
Image source: Wikimedia Commons
“Eh, that kettle heats up fast,” said Chakan. “Should be ready.” He fetched the kettle, scooped a healthy pinch of tea leaves into the cups, then brought it all to the table on a tray. “Our honored guest,” he said, pouring Brinla’s tea.

Brinla nodded, then took another cup and poured for Liana. “My gracious host.”

Finally, Liana poured a cup for Chakan. “The love of my heart, and the father of our child.”

“Love and friendship,” said Brinla, raising her cup. “A toast always worth drinking to.”

After Liana first, and having a farm of their own second, Chakan thought the tea ceremony might be his favorite thing about life in the Matriarchy. Woman or man, everyone poured each other’s tea. Liana had once told him that if he, a common and foreign-born man, were to take tea with the Queen, even she would pour his tea after he poured hers. All serve in the Matriarchy, the consul had told him, back before he left the Reach, and two years of living here had not shown him different.

“So,” said Brinla, “this thing you dug up. It is truly from Camac That Was?”

“So Chakan believes,” Liana replied.

“Aye. See these numbers?” Chakan pointed to the bottom display. “That’s today’s date, according to the old calendar. When we dug it up, it was showing a date from twenty-four hundred years ago. It was in a stone box, coated with pitch and sealed up. I can’t imagine it could have survived so well otherwise.”

“May I ask a question of it?”

“Of course,” Liana chirped, before Chakan could utter a word.

“Love, I should start spreading that fertilizer before it gets too dark,” Chakan said quickly.

“Go and do. I’ll join you soon.”

Brinla waited until Chakan was outside before speaking. “He seemed nervous.”

“Not a word,” Liana replied. “But I think he’s a little superstitious. He thinks the date the mechanism showed, when we dug it up, was the eve of The Madness.”

“That would be enough to frighten anyone,” said Brinla. “Perhaps the owner buried it before fleeing, thinking she could recover it once she returned? In any case, I suppose fertilizing the field is a chore that needs doing.”

“Yar. But your question? I’ll turn the crank. You twist these knobs while you ask it.”

Brinla took her place at the machine, gripping the knobs. “Will our flock prosper this year?” she asked, as Liana turned the crank.

“Zero three eight, nine two four, five four seven,” Liana read the display. “Now we consult the list.”

The wolf prowls without
Vigilance is no error
Beware the weak house.

Liana looked at her neighbor. “What does that tell you?”

“It tells me I need to get my lout of a husband to shore up that gods-forsaken chicken coop,” Brinli replied. “I’ve been after him about that for a while now.” She stood. “You have a good man, Liana. Even if he is a foreigner. May he continue to bless you.”


“And maybe if Brinla treated him like a partner, instead of a servant, he wouldn’t find ways to vex her so often,” Liana concluded. “Truly, do we spread this so thin?”

“Aye,” said Chakan, sprinkling fertilizer on the rows. “Too much, and it’ll kill the seedlings. Indeed, if we don’t get rain in two days, we’ll have to irrigate to help our crop along.”

“The mechanism said we wouldn’t have drought.”

“Aye, but a few days without rain doesn’t make a drought. A few dry days right now can be a bad thing, though.”

“I see.” Liana scattered compost on the adjacent row. “Husband… after we finish this, could you go to Brinla’s and help Mirthan strengthen their chicken pen?”

“I suppose.” Chakan clucked at the ox to move the cart up. “Is this about that… thing we dug up?”

“Yar. Brinla asked if her flock would prosper. It warned of wolves and weak houses.”

“Aye. I’ll bring a jug of ale and we can make the wind after we finish with the pen. You know, Brinla’s got a bit of a loose tongue. We’ll soon have all the folk around here coming to ask questions of the mechanism. When are we taking it to the sages?”

Liana sighed. “We’ll have to go to market in a week. We can take it then. Maybe you’re right, Chakan. Brinla said you’re a good man, and she speaks true. Your instincts are talking, and I need to stop ignoring that. So when we go to market, we’ll be shut of this.”

“That thing does worry at me, love. But we’ll ask the sages to tell us what becomes of it, aye?”

continued…

Monday, April 03, 2017 1 comment

The Brass Mechanism, episode 5

Part 1 | Part 2 | Part 3 | Part 4

Difference engine
Image source: Wikimedia Commons
“Will our child be healthy?” Liana asked, twisting the knobs atop the mechanism. Chakan turned the crank, wishing they had just given the thing over to the sages. Following the instructions to advance the mechanism’s calendar one day, they started planting corn yesterday afternoon, then spent today finishing the work. Now it was evening once again, and tomorrow would be a day of rest. Not that either one planned to get much rest, but…

Chakan refused to watch the numbers spinning, but heard the click as each one fell into place, sealing the fate of their child for good or ill.

“It’s done,” Liana told him.

“Oh. Ah.” Chakan had been turning the crank without realizing it was spinning freely.

“Three two one, six six three, zero three nine,” Liana read the display. “Let’s look it up.”

“All right.” Chakan tried to keep his voice light as he consulted the book.

Duty rewarded
There is no error in rest
Beware violence.

“What do you make of it?”

Liana looked over the numbers, checking her husband’s work, then sat lost in thought for a long time. “It sounds like I should pay close attention to the Healer,” she said. “And to not pick fights or wrestle lids off stone boxes.” She grinned at Chakan. “Rest when I can. That should not be too hard for a while.”

“Aye. Seed’s in the ground, now. When we see signs of rain, we’ll spread the fertilizer. Other than that? Until the corn’s sprouting, we care for the oxen, forage, and tend the kitchen garden.” Chakan found the latter a wonder—a garden that could be picked year-round. True, the winter offerings were roots and sour greens; but a dollop of fat gave the greens some flavor and local herbalists claimed they were good for the constitution. A brief walk would take them to unclaimed land, where they could forage. Northerners like Chakan found the southern coastal lands almost obscenely abundant with edible plants and small game.

“Then it’s settled,” said Liana, taking his hand. “I should rest. You can see that I sleep all night.”


A few days went by before they saw rain coming, but they were never truly idle. Between foraging, seeing to their garden and animals, and frequent romps in bed, they kept busy.

When Chakan saw the clouds building, he went out to the barn and turned the compost heap before pitching the bottom layers into a field wagon. Compost was something he had learned of in his roustabout days, and had brought the knowledge with him to Queensport. Local farmers, finding their waste could easily become free fertilizer, quickly took up the practice as well.

The heap was odorous, especially in summer, but not so much on cool spring mornings like this one. “Rain will come, tonight or on the morrow,” he told the oxen, munching hay in their stalls. “We’ll spread this mess on the field before it gets here.”

But when he went into the house to get Liana, he found their neighbor Brinla sitting at the table. “Peace and harmony,” he said automatically, putting the heel of his hand to his forehead and giving her a nod.

“All peace unto you, Chakan,” Brinla replied, hand over heart. “I had a surplus of eggs this week, and eggs are good for a woman with child, so I thought I would bring Liana a few and catch up on news.”

“Thank’ee for the eggs, and you’re welcome here as always. Would you like some tea? We have Queensport Black, and I believe Two Rivers Red.”

“Red would be good.”

Chakan looked at his wife, who nodded. “Red it is, then.” He stoked up the fireplace—it was yet cool enough to want at least some heat in the house—and hung the pot over the flames.

“So Liana tells me the two of you dug up this fascinating piece of machinery,” Brinla told Chakan as he returned to the kitchen to check on their tea supply. “And it tells the future?”

“I know not if it truly tells the future,” Chakan replied, satisfied that they had enough red tea. “But it does seem to give useful advice about matters when queried. We should be turning it over to the sages soon. Let them puzzle out the truth of it.”

“How does it work?”

“You turn these knobs while you ask your question,” Liana explained. “Someone turns the crank for you. Then you match the numbers against a list to see the answer.”

continued…

Monday, March 27, 2017 2 comments

The Brass Mechanism, episode 4

Part 1 | Part 2 | Part 3

Difference engine
Image source: Wikimedia Commons
Chakan began to object, but stopped. Two years living in the Matriarchy, and he still found himself having to shake old attitudes. But deferring to his wife was a small price to pay for… for everything. Not only for their land, but for Liana. Her letters had raised his hopes, and getting to know her had proven reality greater than his hope. She was headstrong, aye, but better that than a woman who waited to be told what to think. Besides, she listened to his advice about farming, and mostly let him make the decisions for the farm work. If ever a man had found his ideal… “Aye. Fair enough,” he said.

“We’ll have a care,” Liana assured him. “What should we ask about first?”

“Eh. What crops will be worthwhile to plant. ‘Twould save us a mickle of work if we’re gonna face drought or blight this season.”

“So we plant nothing if the mechanism predicts a bad growing season?”

“Ah, nay.” Chakan embraced his wife. “We’ll plant crops that won’t need as much water. They won’t fetch a high price at market, but they’ll beat a failed corn crop.”

“Sensible. But we’ll need to get all these numbers and their phrases written down to make sense of it anyway. Let’s get to work.”

Working by the light of their lamps, they kept on through the night. By the time they looked up, the first light of day was struggling through the windows. Some of the pages in the old book had torn, but they had faithfully transcribed the entire thing.

“Ah,” Chakan grumbled, dropping the quill and shaking his hand. “I’m cramping from elbow to fingertip here.”

“I’d like to see a scribe do better,” Liana soothed, rubbing his arm. “A sweet potato will help with the cramping. We got one left. I’ll cook it up with some sausage for ya, then we’ll get some sleep.”

Afternoon sun streaming into the bedroom window had Chakan sitting up quickly. “Ah, the day’s more’n half-gone,” he muttered, throwing back the covers.

“Soft, soft,” said Liana, putting a hand on his shoulder. “If we don’t get the planting started today, we’ll start tomorrow. One day more or less won’t hurt matters. And we’re going to consult our mechanical Oracle first, remember?”

“Oh, aye.” He yielded to Liana’s gentle pressure, lying down once again.

“How’s your hand?” she asked.

“Better. It might actually grip something.” He reached and gave Liana a gentle squeeze.

“Mmmm. I think my husband is awake.” She reached down. “Indeed he is.”

Some time later, they sat at the table, eating their lunch—strips of marinated meat with a bland local cheese, wrapped with salad greens in flatbread—eyeing the strange mechanism they had wrested from the middle of their field.

“So the book says you grip the knobs atop the thing and twist ‘em, while you ask your question,” said Chakan. “Then you turn the crank clockwise until it no longer resists.”

“And you interpret its answer from the numbers it shows,” Liana added. “Seems simple enough. So you ask the question, I’ll spin the crank, eh?”

Chakan grasped the knobs atop the mechanism. “Should we plant corn this year?” he asked, twisting the knobs as he spoke.

Liana turned the crank, watching the numbers spin across the upper display. One by one, the numbers stopped spinning. Finally, the last number fell into place and the crank spun freely. “It’s done,” she said.

“Aye. Four one one, eight zero nine, two four seven.” Chakan turned to his transcript, and thumbed through the pages.

A plan is well laid
Sun and rain come in their time
Work is rewarded.

“It sounds like we should just plant our corn like we planned.”

“That’s a relief.” Liana grimaced. “Necessity. We can start planting afterwards.”

Chakan watched her rush for the privy, then started for the barn. But before he left the house, he turned around and went back to the brass mechanism. His sketch was in the sheaf of paper that made up his transcription, and he took it out to have a look. “One zero four, zero seven two, two nine eight,” he muttered. He thumbed through the tables, jotting down the meaning on a piece of scrap, then checked it again.

An ill wind blows strong
All empires fall in their time
The hidden prosper.

“Gods. If this thing were buried on the eve of The Madness… gods.” He tucked the scrap into the sheaf, then slipped outside and trotted to the barn. Maybe work would help him forget the dark prophecy.

continued

Tuesday, March 21, 2017 No comments

Tech Tuesday: Roll Your Own Writing System, part 6: Jekyll


The series rolls to an end…

In Part 1, we had a look at Markdown and the five or six formatting symbols that cover 97% of written fiction. Part 2 showed how you can use Markdown without leaving the comfort of Scrivener. Part 3 began exploring eBook publishing using files generated from both Scrivener and directly from MultiMarkdown. Part 4 provided a brief overview to a different tool called Pandoc that can convert your output to a wider variety of formats, and is one way to create print documents for beta readers or even production. Part 5 described how to use MultiMarkdown’s transclusion feature to include boilerplate information in an output-agnostic way, and how to use metadata variables to automatically set up front matter.

Scrivener is an excellent writing tool, and we have seen how using it with MultiMarkdown only makes it better. But there are conditions where abandoning the GUI for a completely text-based writing system just makes sense. For example, you might want to go to a minimalist, distraction-free environment. You may want to move to a completely open-source environment. Or you might need to collaborate with someone else on a project, and Scrivener really isn’t made for that.

Don’t Hyde from Jekyll


Jekyll is the most popular static site generator. You write in Markdown—Jekyll’s particular flavor, which is similar to MultiMarkdown in many ways—and if Jekyll is running, it automatically converts your pages to HTML as soon as you save. It even includes a built-in web server so you can see what the changes look like.

If you’re on a Mac, installation is almost too easy. Drop to a command line, enter gem install jekyll bundler, and watch a lot of weird stuff scroll by. It’s as easy on Linux, if you have Ruby 2.0 or newer installed. On the Microsoft thing, there are some specific instructions to follow (I installed it on my work PC, no problem).

Once it’s installed, get going by following the quick-start instructions.

Organizing


Unlike Scrivener, organizing your project is on you. But there are a couple things that might help:

Each story or project should live in its own folder. Within that folder, tag each chapter or scene with a number to put everything in its proper sequence. For example:

100_chapter_1.md
110_arrival.md
120_something_happens.md
200_chapter_2.md
210_more_stuff_happens.md

It’s a good idea to increment by 10 as you create new scenes, in case you need to insert a scene between two existing ones later. To move a scene, change its number. If you have more than nine chapters, use four-digit numbers for the sequence. (If you need five-digit numbers, you should seriously consider turning that epic into a series of novels.)

Differences from MultiMarkdown


Like MultiMarkdown, Jekyll’s flavor of Markdown supports variables and transclusion. But there are a couple differences. In Jekyll, variables look like MultiMarkdown’s transclusion:

{{ page.title }}

You can draw variables from the page’s metadata, or from the _config.yml configuration file (in which case you replace page with site).

Transclusion is a function of the Liquid templating language, built into Jekyll. To include a file:

{% include.relative file.md %}

You can also use include instead of include.relative to pull files from the _includes directory. By using Liquid, you can specify parameters to do different things, effectively creating your own extensions.

For example, here’s how you might do section breaks:

<p class="sectionbrk">
  {% if include.space %}&nbsp;{% else %}&bull; &bull; &bull;{% endif %}
</p>

So if you just enter {% include secbrk.html %}, you get three bullets. To get a blank line, enter {% include secbrk.html space="true" %} instead.

Also like MultiMarkdown, Jekyll supports a metadata block at the beginning of a file. While they look very similar, Jekyll uses YAML format for its metadata. The upshot is, a Jekyll file begins and ends its metadata with a line of three or more dashes, like this:

---
title: The Sordid Tale of Woe
author: Henrietta Jekyll
permalink: /sordid/sordid_tale.html
---

Certain metadata tags are special to Jekyll. For example, permalink specifies the name and location of the HTML file Jekyll creates from the Markdown source. Another important tag, layout, can be used to choose a template. You can set the default layout in the configuration file, then use a second configuration file to override it for doing things like publishing.

Git Out


Jekyll is also a blogging tool. Your posts go into a special directory, _posts, and have a specific naming convention. Two additional metadata tags are important:

date:   2017-03-21 07:00:00 -0500
categories: writing technology

The date entry specifies the date and time your post goes live on the generated site. The categories entry lets you tag each post for easier searches.

But all that’s just pixels on the screen unless you have a place to put your site. That’s where Github Pages comes in. You can upload your Jekyll files to Github Pages, and it automatically updates your site when it finds new or changed content. This is pretty useful, but it’s even more useful when you’re working with other people. Everyone has their own copy of the source files on their own computers, and they can each push (update) their changes as needed.

Now What?


I hope I’ve given you some ideas for new ways of looking at your writing, and how to make the publishing part more efficient and more collaborative.

The rest… is up to you. I’d love to see your own ideas in the comments.

Monday, March 20, 2017 No comments

The Brass Mechanism, episode 3

Part 1 | Part 2

Difference engine
Image source: Wikimedia Commons
Liana set their prize on the table, and they stepped back to take a look. It was a strange-looking device, but even folk with a basic education could see it was some kind of machine. All brass gears, spindles, and fittings it was, with a few flecks of the wood that had once covered it still clinging to the supports. It sported a crank on the right side, the wooden handgrip long gone. A row of numbers dominated the front of the device: 104 072 298. Below was a smaller set of numbers: 98 1812. It had a faint odor of oil and decay.

“So what do those mean?” Chakan asked, pointing at the numbers.

“Maybe the answer is in here.” Liana opened the book, watching to see if the pages would crumble at a touch. “Have a care with this, but it might survive our perusals.” She turned up the title page; it felt brittle but did not fall to pieces. “Using the Prediction Calculator,” she read. “What in the Fourth Hell?”

“This hunk of metal tells the future?” Chakan gave the device an incredulous look. “Ha, the Queen would want to get her hands on this, then.”

“This text is hard to make out. They must not have written the same way we do. ‘Accurate predictions… to ensure, against the stars shall you calibrate.’ What?”

“Sounds like Low Speech. Outside of Phylok you get, so the farmers talk.”

Liana took a moment to parse her husband’s explanation. “Ah. So the ancients all talked the same way? I see. This is saying you calibrate this thing against the stars to get accurate predictions.”

“It uses the stars to make predictions? Outlandish. Shipmasters use the stars to tell where they are on the sea, but I’ve never heard of anyone using them to predict the future.”

“Eh. I never heard Low Speech until you used it just now.”

“If the ancients used the stars to predict the future,” Chakan mused, “the sages would find this thing useful indeed.”

“Ah!” Liana cursed as the page tore. “Bring some paper, love. If these gods-forsaken pages come apart on us, we can preserve what they say for the sages.”

“The sages won’t be pleased with our destroying the originals. But if we’re going to puzzle this thing out, it’s the best we can do.” He paused. “Liana… perhaps we should give this over. Let the sages ruin the book. Knowin’ the future could be a fearful business.”

“Could be some profit in it, love. Besides, we found it. We pulled it out of our field. You got the box open. We’ll do the best we can, and that will have to be good enough. Here, write down the numbers it’s showing. Maybe we can puzzle out their meaning later.”

“Aye. Then we’ll sow tomorrow?”

“If the Creator brings us another day of dry weather, indeed. Don’t you have those numbers written down yet?”

“I’m sketching the whole works.” Chakan slid the paper to his wife.

“How do you do that so well, and so quickly?” she asked. In less time than it takes to drink a cup of tea, Chakan had sketched a fair likeness of the mechanism, with Liana looking on. He had drawn a look of wisdom and revealed knowledge on her face.

“A knack. I don’t get to exercise it often.”

“I like this. We should put it in a frame. Then we’ll wait for dark, and calibrate this… this thing. But let’s copy the instructions while we’re waiting.”

“If we don’t destroy the pages along the way.”

“Hoy, I got an idea.” Liana took another sheet of paper and slid it in between the next two pages in the book. “Maybe this will help.” She gently turned the page. “Ha, it worked! Now here’s what it says…”


The night was clear enough to see the stars, and they followed the instructions to calibrate the device. They twisted knobs and pointers on the top of the mechanism as directed, then held their breath as Chakan turned the crank counter-clockwise. One turn, two turns… then the odd clicking noises inside the mechanism ceased and the crank spun freely as the instructions said it would.

They took their prize back inside and looked it over. “Hoy,” said Chakan, “the numbers along the bottom are different, now. Now it’s 84 4269.

“Eh. I think it’s forty-two something by the old Camac calendar,” Liana mused. “And it’s pretty close to the eighty-fourth day of the year. Maybe that’s today’s date.”

“Then this thing has been in the ground a long time, waitin’ for us to dig it up.” Chakan looked at his sketch. Eighteen-twelve. Gods… that mighta been the year of The Madness.”

“Wouldn’t that be something?”

“Liana… let’s give this over to the sages. We’re messin’ with somethin’ that got buried at the worst time ever. Or just before. What was that first set of numbers? One oh-four?” Chakan consulted his transcripts. “First and third groups use the same numbers. An ill wind blows strong. Makes me wonder what the rest of it means.”

“It won’t bring back The Madness, love. That was a good twenty-four centuries ago. We’ve reset it for modern times, and we’ll make some use of it. Then we’ll give it over. Fair enough?”

continued…

Wednesday, March 15, 2017 2 comments

Kneecapped 2017, an update

Tonya, Queen of Kneecaps
image source: about.com
When we last left this, the knee had started improving around the time I went to the doc. The day after, the pain decided a brief vacation was all it needed… then the left knee decided to join the fun.

Reality the Crutch has been missing for some time now, but we have a metal adjustable cane laying around, so I adopted it instead to get around. Things were still pretty painful last Tuesday, when I went to the orthopedist. He looked at the X-rays and decided we needed an MRI. I asked him for some happy pills, and he wrote a prescription for hydrocodone+acetaminophen right away. I’d been popping ibuprofen like candy for a while, and it was keeping things manageable through the day, so I figured I could continue that and save the happy pills for night time (the pharmacist said that was OK).

So for the next few night, it was two happy pills before bedtime, wait an hour for them to kick in, sleep like a log until they wore off around 4am, then one more to get me through the rest of the night. Not the best sleep I ever had, but better than what I’d been getting.

After a few days of improved sleep and lots of inactivity, both knees started getting better. From experience, I know this is the dangerous phase of a knee problem—it’s way too easy, now that you can get around without tons of pain, to overdo it and go right back to where you started. So I rested as much as possible, moved when I had to. Icing started doing what it should, so I went back to doing it, alternating knees as needed.

The MRI was on Monday, and was anti-climatic. Laid on a pallet, knees propped up, moved as little as possible while this big round thing spent 20 or 30 minutes making weird noises. Today was the interpretation. Long story short, he wants to do a full replacement. There’s a lot of crud in there, and roto-rooting it won’t take care of it. Due to long-scheduled travel, this isn't going to happen until May, but in two months I will post Tonya for the last time.

Tuesday, March 14, 2017 No comments

Tech Tuesday: Roll Your Own Writing System, part 5: Reuse

The series rolls on…

In Part 1, we had a look at Markdown and the five or six formatting symbols that cover 97% of written fiction. Part 2, showed how you can use Markdown without leaving the comfort of Scrivener. Part 3 began exploring eBook publishing using files generated from both Scrivener and directly from MultiMarkdown. Part 4 provided a brief overview to a different tool called Pandoc that can convert your output to a wider variety of formats, and is one way to create print documents for beta readers or even production.

Way back in Part 2, we used Scrivener to embed HTML separators between scenes and for internal scene breaks. As we saw last week, that doesn’t work when you need to output to a different format. As it turns out, there’s a way to work around that by using MultiMarkdown’s transclusion mechanism. Transclusion and metadata variables provide the capability for reuse, pulling common boilerplate files from a library.

Inclusion… Transclusion?


Transclusion is a technical term, but it’s easy enough to explain. You use it to embed another Markdown file into your document, like you might include a graphics file. A function like this is essential when you’re maintaining a collection of technical documents, because you can reuse common sections or passages—write them once, store them in a library of common files, and then changing one of the source documents automatically updates all the documents that use it. For fiction writing, it’s a good way to pull in all those boilerplate files (about the author, front matter, etc.) that you need for each book.

To transclude a boilerplate file, put this on its own line:

{{myfile.md}}

When you run multimarkdown, it pulls in the contents of myfile.md and processes it.

Now here’s where it gets fun. Say you really need to be able to output to both HTML and OpenOffice. Instead of embedding HTML that gets ignored in the OpenOffice conversion, or vice versa, you can use a wildcard:

{{myfile.*}}

Now, when you output to HTML, multimarkdown transcludes the file myfile.html. When you want OpenOffice, it uses myfile.fodt. You just have to supply the files with the right extensions and content, and you’re off to the races! You can use this in the Separators in Scrivener to choose the right markup for your output.

A few caveats for fodt transclusion: You cannot use entities like &bull; or &#8026; to specify special characters. You have to enter them as characters. If you only have one line to add, you don’t need to put any OpenOffice markup in the fodt file—plain text is fine, but use the right extension so multimarkdown knows which file to use.

If you want to reuse transcluded files with other documents, you can add another line to the metadata:

Transclude Base: /path/to/your/files

You can use a relative path like ../boilerplate, but it’s safer to specify the entire path in case you move the file to some other location.

Does the Front Matter?


But transcluding boilerplate files is only the beginning. Especially for front matter, you need to change at least the title for each book. Fortunately, MultiMarkdown has that covered.

In Scrivener’s Compile window, the last entry is Meta-Data. Back in Part 3, you used this to specify a CSS file for HTML output. Scrivener pre-fills entries for the Title and Author, but you can add anything else you want here. All the metadata ends up at the beginning of the file, where MultiMarkdown can process it further.

So you might have a block that looks like this:

Title: Beyond All Recognition
Subtitle: The Foobar Chronicles, Book 1
Author: Marcus Downs
Copyright: 2017
Publisher: High Press UR

Create a title page that looks like this (for HTML output):

<div style="text-align:center" markdown="1">
**[%title]**

**[%subtitle]**

by  
[%author]

Copyright [%copyright] [%author]. All rights reserved.

Published by [%publisher]
</div>

![](logo.png)

{{TOC}}

Instant front matter! The {{TOC}} construct inserts a table of contents, another Multimarkdown feature.

Now What?


Now you know how to include boilerplate files in your book, and how to automatically put the right text in each output format.

Next week… it’s something completely different to wrap up the series.

LinkWithin

Related Posts Plugin for WordPress, Blogger...