Searching through the forums, I found a bunch of nice tips by AmberV regarding styles, including defining your own.
I am interested in defining styles by semantic meaning (the whole dividing content and style thing). Working in Mellel, for example, I have a style for book titles, and another for transliterated words (in LaTeX, I’ve defined these in the preamble as well).
If I was to define styles in the Cocoa-included editor’s style sheet (cmd-r, then “other” under the ‘styles’ tab on the left), would there then be a way to have these translated upon export? From my rather rudimentary experimenting, it doesn’t appear so: exporting as RTF, then opening the RTF file in a text editor (Subethaedit) showed that there was no mention of my semantically-titled “style” in the markup.
So, if that is the case…here comes my “wish” (we are in the wish list forum):
A user-definable style palette; or (semantic) style sheet; or (semantic) highlighting. Scrivener is already actually already half-way there, already has a few features that do kind of do this. Let me explain.
Yes, I know Scrivener is not a word processor. I don’t want it to be either. But when working with very long, structured documents (which, after all the card-shuffling, Scrivener excels in), I need to keep tabs of all my semantically-induced styling. And with Scrivener’s built-in ability to export to so many file types (either directly, such as RTF, or through MMD, such as HTML, LaTeX, etc.) it would seem to me that a semantic-based style definition would make most sense.
I mean, in a way, this is already there with footnotes and annotations: when exporting, both the RTF exporter and the MMD know that a footnote is a footnote, and translate/export it correctly.
Let’s say that we were able to define the annotation to do something, to be something else. Or the highlights: where a blue highlight would mean “transliterated word”, a green one “book title” (both of which are usually italicized). Then, when export comes around, the exporters (such as the MMD one, or the built-in exporters) could be tweaked to translate and preserve these meanings, just as Scrivener currently does with the “highlighting” that is the graphic footnotes field.
This would all assist in Scrivener being the app for long, structured writing of the academic and technical variety. I know this wasn’t the original intention of Scrivener, but the writing environment it currently has seems so well suited for for academic and technical writing with such an addition. (And, no, I don’t mean for 1.2).