FA+
Shop
A lot of people like to their stories as PDFs, so they have more control over formatting. But when you're creating a PDF, you're not typing, you're typesetting, and if you want it to look good you're going to have to learn some basics about typography. Here's a quick guide.
1736
Views
16
Comments
56
Favorites
General
Rating
LibreOffice uses a bit of an Autocorrect feature, so if you go into Tools > AutoCorrect > AutoCorrect Options and hit the "Replace" tab, you'll see a whole list. For example, an em-dash is ":---:" (colon-dash-dash-dash-colon).
Most Linux distributions will let you change a modifier key to be the "dead key" or "compose" key. This is useful for international letters, where to type "uber" with an umlat, you hold down compose, shift, and type the ", release, then type the u. It autocombines.
And finally, Markdown is styled to be read in plain text, so it tends to lose a lot in the actual writing phase as you're using a text editor, not a word processor. In certain cases, this helps out with concentration as you're just writing... but then you add a layout and editing phase. LibreOffice will read Markdown but you can define custom styles and such by using a command-line tool called Pandoc. This is how I've been doing a lot of my writing lately.
There's no mention of the differences between devices. This is maybe academic for publishing on, lets be honest, a bit of a dinosaur of a site like FA, but my PDFs have fairly huge margins specifically because I find it more pleasant to read on a phone. Is this just a space where trade-offs are inevitable? Am I thinking about this wrong? Thoughts?
For that, I use a tool called Jutoh. It's trialware, but the price for it is fairly cheap. It'll take a Word DOCX, point out issues that would pop out on ePubs, help you correct them, and compile the final product. Testing them out or ing them to a eReader (Kobo for instance, or some older Kindles)? I use Calibre for that.
Yes, HTML in some ways is a good compromise across display devices because it inherently gives the browser final say as to the exact formatting. There's a reason that e-book formats use a form of HTML as their substrate. PDF is what you want if you want complete control of the formatting, but that's best if you know exactly how it's going to be displayed.
For posting stuff here, I usually use BBCode, because that gets handled inline and shows up on the web page, and there are a few other undocumented things like multiple daches getting turned into a horizontal rule on the page, like so:For bigger stuff at home I still have a soft spot for LaTeX, and I'm glad to see it got a callout in your document.
Lately, for my longer stories, I've been ing a PDF with a separately formatted TXT version for that same kind of reason of clicking through. The PDF has sat in my gallery with navigation links to adjacent chapters, a link to the alternate TXT submission, and a link to the table of contents submission for easy navigation across the whole body.
Though, for one-off stories I tend to just do a TXT version and call it a day.