Veronica Berglyd Olsen
54 lines
3.7 KiB
Plaintext
54 lines
3.7 KiB
Plaintext
%%~name: Making a Scene
|
||
%%~path: 6a2d6d5f4f401/636b6aa9b697b
|
||
%%~kind: NOVEL/DOCUMENT
|
||
%%~hash: c1a75b18145e49e5e71b5284f66a261207da37d0
|
||
%%~date: Unknown/2025-06-16 12:49:10
|
||
### Making a Scene
|
||
|
||
@tag: Scene
|
||
@pov: Jane
|
||
@char: John, Jane
|
||
@location: Earth
|
||
@mention: Space
|
||
|
||
%Story.Resolution: You can describe the scene structure with story comments.
|
||
%Note.Consistency: You can also make notes about things like consistency of the story.
|
||
|
||
A scene is defined by a level three heading, like the one at the top of this page. The scene will be assigned to the chapter preceding it in the project tree. The scene document can be sorted after the chapter document, or as a child of the chapter. Both result in the same output in the end, so it is a matter of preference.
|
||
|
||
Each paragraph in the scene is separated by a blank line. The text supports minimal formatting, like **bold**, _italic_ and **_bold italic_**. You can also ~~strike through~~ text. There is **some support for _nested_ emphasis**, but there are some known limitations. If the ==syntax highlighter== doesn’t show it correctly, the export tool will not either.
|
||
|
||
For special formatting aside from standard emphasis, you can use “shortcodes”. Here we have super[sup]script[/sup] and sub[sub]script[/sub], and [b]part[/b]ial bold too, which ends in the middle of a word. The shortcodes also support [u]underline[/u], and you can [m]highlight text as well[/m].
|
||
|
||
In addition, the editor supports automatic formatting of “quotes”, both double and ‘single’. Depending on the syntax highlighter settings and colour theme, these can be in different colours. “You can of course use **bold** and _italic_ text inside of quotes too.”
|
||
|
||
If you have the need for it, you can also add text that can be automatically replaced by other text when you generate a preview or export the project. Now, let’s auto-replace this A with <A>, and this C with <C>. While <E> is just <E>. Press Ctrl+R to see what this looks like in the view pane. The list of auto-replaced text is set in Project Settings.
|
||
|
||
You can also add URLs like http://www.example.com to the text.
|
||
|
||
The editor also supports non breaking spaces, and the spell checker accepts long dashes—like this—as valid word separators. Regular dashes are also supported – and can be automatically inserted when typing two hyphens.
|
||
|
||
Thin spaces and thin non-breaking spaces are also supported from the Insert menu, and can be used to separate numbers from their units, like: 25 kg.[footnote:f4xr5]
|
||
|
||
%Footnote.f4xr5: Using a non-breaking space is the correct way to separate a number from its unit. This ensures that line wrapping does not split the two.
|
||
|
||
#### Some Section Here
|
||
|
||
If you need to split a scene file up into further pieces, you can do so with the level four heading, like the one above this paragraph. This is referred to as a “section” in the documentation.
|
||
|
||
Both scene and section titles can be left out of the final exported document. The formatting of titles can be selected from the Build Novel Project dialog. You can also have them replaced with scene separators like “* * *”.
|
||
|
||
#### Text Alignment and Indentation
|
||
|
||
The text by default will have the left or justified alignment in the main text files in your project. You can also specify alignment for a specific paragraph by “pushing” it away from an edge with a set of ‘>>’ or ‘<<’ symbols, like so:
|
||
|
||
This text is left-aligned. <<
|
||
|
||
>> This text is right-aligned.
|
||
|
||
>> This text is centred. <<
|
||
|
||
You can indent a paragraph from both the left and right margin with ‘>’ and ‘<’ symbols.
|
||
|
||
> This paragraph is indented from both the left margin and the right margin. This is useful for when you want to quote a large chunk of text for instance. <
|