70d74e675f
- Rename project name and package: novelWriter -> UmbraEdit, novelwriter -> umbraedit - Rename entry script novelWriter.py -> UmbraEdit.py - Rename package directory novelwriter/ -> umbraedit/ - Rename i18n translation sources nw_*.ts -> ue_*.ts - Rename packaging files (appdata, project xml template) - Update all imports, references, docs, workflows, tests and build config - Update pyproject.toml project name, GUI script and URLs - Preserve full upstream git history; origin repointed below
1.3 KiB
+++ name = "Basic Formatting" parent = "7031beac91f75" handle = "6a2d6d5f4f401" class = "NOVEL" layout = "DOCUMENT" textHash = "469808b1602e18df6e59abc5007cb5cf47217c58" createdDate = "Unknown" updatedDate = "2025-11-01 16:15:49" +++
Basic Formatting
% Any document or note can be given a tag that you can reference from another document or note. These tags have to be unique across the entire project. You can define a new tag for each heading in a document.
@tag: Formatting
% You can add your own comments anywhere in your text. Comments are never included in the word count, and you can select to include or exclude them from your manuscript.
%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.
% The part after the dot in your story or note comment is a keyword of your choosing.
The headings define the story structure. Two # symbols means a chapter, and three means a scene. Adding the exclamation point changes the formatting of the heading in your manuscript. For chapters, it means they are excluded from chapter number generation. See the ‘Interlude’ file for an example.
This document is understood by UmbraEdit as a chapter. You can add scene document below it either as child documents or just below it on the same level.