Released on 27 July 2021
+Released on 22 August 2021
-This release fixes a couple of minor issue with some of the dialog boxes. The fix was -accidentally left out of release 1.4.
+This is a beta release of the next release version, and is intended for testing purposes. Please +be careful when using this version on live writing projects, and make sure you make frequent +backups.
+This release introduces a new project file format, which has been given a file format version +1.3. The project file and index is updated automatically when you open the project, which means you +can no longer open it in an older version of novelWriter.
+You may also have to make a handful of changes in your novel documents as these are not updated +automatically. However, the changes are minimal and in any case only affects the way your +manuscript looks like when exported via the Build Novel Project tool. The details are described +below.
+ +The main change in this release is the significant simplification of document layouts. +Previously, there were seven different layouts available for novel documents, in addition to the +one layout for project notes. The original intention of these layouts were partially to define some +default formatting behaviour when exporting your project, and partially a way to indicate whether a +specific document was a partition, chapter or scene.
+With this release, all the seven layouts for novel documents have been merged into a single +layout called simply "Novel Document". The other layout for "Project Note" remains unchanged. The +functionality provided by the various novel layouts have been implemented in other ways, and a few +new formatting codes have been added to accommodate the formatting functionality lost with the +removal of the layouts. They are all available in the Format and Insert menu.
+The changes you need to make to your project should be limited to altering a handful of titles +and maybe insert a page break code here and there. The only title formats you need to update are +those for the main novel title and for your unnumbered chapters, if you have any.
+Novel titles need to be altered from "# Novel Title" to +"#! Novel Title" and unnumbered chapters from "## +Chapter Name" or "## *Chapter Name" to "##! +Chapter Name". That is all. For inserting page breaks, you can add a single line with the +command "[NEW PAGE]" where you want the break to be inserted. As before, +page breaks are automatically inserted in front of all partition and chapter titles.
+You will find these changes described in more detail the documentation in the +"Format +1.3 Changes" section.
+ +Due to the above changes, the GUI has been altered a bit. The main changes are in the project +tree. These changes are also reflected in the details panel below the project tree, and to a lesser +extent in the Outline tab.
+The layouts were previously a way to indicate the purpose of a specific novel document, like +whether it was a chapter or scene. With these layouts gone, the distinction is instead indicated by +other visual means.
+The project index will now record the level of the first header of your document, and select a +different icon for documents with a partition, chapter or scene header. These are colour coded as +green, red and blue respectively. This only works for the coloured icon themes. The project notes +have also received a new icon, with a yellow colour code.
+In addition, novel documents with a partition or chapter header will have the document label +viewed as bold and underlined. This feature can be disabled in Preferences if you want a cleaner +look in the project tree.
+ +Several improvements have been made to the project index, which means the index will be +automatically rebuilt when you open a project for the first time in the new version. You will get a +notification about this.
+The ODT export tool has also been improved. The code that writes out text paragraphs has been +rewritten and now conforms more closely to the Open Document standard. Most of these improvements +will not be noticeable to you as a user, but you may notice that the exported document will now +allow multiple consecutive spaces. Previously, two spaces, or more, would be concatenated into a +single space in the exported document.
See also the Releases page.
-Released on 27 July 2021
- -This release contains some new features and a lot of code refactoring. Among the main new -features is paragraph alignment and indentation. Regular line breaks within paragraphs are now also -supported. The changes are described in more detail below.
- -Translation files have been added for Simplified Chinese by Qianzhi Long.
- -The way line breaks inside paragraphs work has been changed. A single line break is now treated -as a proper line break and will show up in the document viewer and exported documents. A single -line break does not start a new paragraph, but forces a break inside the paragraph like a Shift + -Enter does in most rich text editors. Two line breaks is still needed to start a new paragraph.
-The old syntax of adding two spaces at the end of a line to force a line break within a -paragraph will still work as before, so there is no need to change your existing text if you've -used this feature. However, there is a new highlighting feature that will show you where in the -text you have redundant spaces. If you are used to having double spaces between sentences, you may -want to switch off this highlighting feature in Preferences as it will also detect those.
-A helper function has been added to the Format menu that can look through a paragraph and remove -line breaks in case you've been using line breaks inside your existing text under the assumption -that the exporter and viewer will ignore them.
-I hope this change will not be too inconvenient. I believe the new behaviour will make more -sense for most people. Especially considering some of the feedback I've gotten on how line breaks -work. The original implementation was following the Markdown standard, but since novelWriter is not -a proper Markdown editor and instead just borrows from Markdown, this behaviour always seemed a bit -unnecessary.
- -The default text alignment is left or justified based on your preferences. For documents with -the layout set to Title Page or Partitions, the default is centred. However, sometimes you may -want to override this default. A new set of codes have therefore been added to allow specifying -alignment as well as additional text margins on individual paragraphs.
-The logic of the syntax is as follows:
-A single angle bracket will push the text away from the edge it points away from. Therefore, a -single '>' before the paragraph, or a single '<' after the paragraph, will add indentation on -the respective side. It's perfectly valid to do this on both sides at the same time.
-A double set of angle brackets will push the text all the way towards the opposite side. -Therefore, a double set of '>>' before the paragraph will indicate right alignment, and a -double set of '<<' after the paragraph will force left alignment. Also here both can be used -at the same time, which results in the paragraph being centred.
-Format menu entries and keyboard shortcuts have been added so that you don't have to memorise -these codes.
- diff --git a/nw/assets/text/release_notes_1.4.htm b/nw/assets/text/release_notes_1.4.htm new file mode 100644 index 00000000..e2b2bc36 --- /dev/null +++ b/nw/assets/text/release_notes_1.4.htm @@ -0,0 +1,61 @@ + + + + +Released on 27 July 2021
+ +This release fixes a couple of minor issue with some of the dialog boxes. The fix was +accidentally left out of release 1.4.
+ +See also the Releases page.
+ +Released on 27 July 2021
+ +This release contains some new features and a lot of code refactoring. Among the main new +features is paragraph alignment and indentation. Regular line breaks within paragraphs are now also +supported. The changes are described in more detail below.
+ +Translation files have been added for Simplified Chinese by Qianzhi Long.
+ +The way line breaks inside paragraphs work has been changed. A single line break is now treated +as a proper line break and will show up in the document viewer and exported documents. A single +line break does not start a new paragraph, but forces a break inside the paragraph like a Shift + +Enter does in most rich text editors. Two line breaks is still needed to start a new paragraph.
+The old syntax of adding two spaces at the end of a line to force a line break within a +paragraph will still work as before, so there is no need to change your existing text if you've +used this feature. However, there is a new highlighting feature that will show you where in the +text you have redundant spaces. If you are used to having double spaces between sentences, you may +want to switch off this highlighting feature in Preferences as it will also detect those.
+A helper function has been added to the Format menu that can look through a paragraph and remove +line breaks in case you've been using line breaks inside your existing text under the assumption +that the exporter and viewer will ignore them.
+I hope this change will not be too inconvenient. I believe the new behaviour will make more +sense for most people. Especially considering some of the feedback I've gotten on how line breaks +work. The original implementation was following the Markdown standard, but since novelWriter is not +a proper Markdown editor and instead just borrows from Markdown, this behaviour always seemed a bit +unnecessary.
+ +The default text alignment is left or justified based on your preferences. For documents with +the layout set to Title Page or Partitions, the default is centred. However, sometimes you may +want to override this default. A new set of codes have therefore been added to allow specifying +alignment as well as additional text margins on individual paragraphs.
+The logic of the syntax is as follows:
+A single angle bracket will push the text away from the edge it points away from. Therefore, a +single '>' before the paragraph, or a single '<' after the paragraph, will add indentation on +the respective side. It's perfectly valid to do this on both sides at the same time.
+A double set of angle brackets will push the text all the way towards the opposite side. +Therefore, a double set of '>>' before the paragraph will indicate right alignment, and a +double set of '<<' after the paragraph will force left alignment. Also here both can be used +at the same time, which results in the paragraph being centred.
+Format menu entries and keyboard shortcuts have been added so that you don't have to memorise +these codes.
+ + + diff --git a/nw/constants.py b/nw/constants.py index c0c978da..9f7ff031 100644 --- a/nw/constants.py +++ b/nw/constants.py @@ -66,7 +66,7 @@ class nwLists(): FREE_CLASS = {nwItemClass.ARCHIVE, nwItemClass.TRASH} # Deprecated nwItemLayout entries - DEP_LAYOUT = ("TITLE", "PAGE", "BOOK", "PARTITION", "UNNUMBERED", "CHAPTER", "SCENE", "STORY") + DEP_LAYOUT = ("TITLE", "PAGE", "BOOK", "PARTITION", "UNNUMBERED", "CHAPTER", "SCENE") # END Class nwLists diff --git a/nw/dialogs/about.py b/nw/dialogs/about.py index b3763026..d6f74ff5 100644 --- a/nw/dialogs/about.py +++ b/nw/dialogs/about.py @@ -268,6 +268,9 @@ class GuiAbout(QDialog): "a {{" " color: rgb({hColR},{hColG},{hColB});" "}}\n" + ".alt {{" + " color: rgb({kColR},{kColG},{kColB});" + "}}\n" "td {{" " padding-right: 0.8em;" "}}\n" @@ -275,6 +278,9 @@ class GuiAbout(QDialog): hColR=self.theParent.theTheme.colHead[0], hColG=self.theParent.theTheme.colHead[1], hColB=self.theParent.theTheme.colHead[2], + kColR=self.theTheme.colKey[0], + kColG=self.theTheme.colKey[1], + kColB=self.theTheme.colKey[2], ) self.pageAbout.document().setDefaultStyleSheet(styleSheet) self.pageNotes.document().setDefaultStyleSheet(styleSheet) diff --git a/sample/nwProject.nwx b/sample/nwProject.nwx index 1cfb4a20..068e7e4a 100644 --- a/sample/nwProject.nwx +++ b/sample/nwProject.nwx @@ -1,13 +1,13 @@ -