Reproog/novelWriter
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Release 1.5 Beta 1 (#858)

Browse Source 
* Bump version to 1.5-beta1 and update changelog and release notes
This commit is contained in:
Veronica Berglyd Olsen
2021-08-22 11:35:06 +02:00
committed by GitHub
parent 7a80e6a55c
commit 80911af4d2
8 changed files with 284 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files
nw/__init__.py
+3 -3
View File
@@ -61,9 +61,9 @@ __license__ = "GPLv3"
__author__ = "Veronica Berglyd Olsen"
__maintainer__ = "Veronica Berglyd Olsen"
__email__ = "code@vkbo.net"
__version__ = "1.5-alpha0"
__hexversion__ = "0x010500a0"
__date__ = "2021-07-27"
__version__ = "1.5-beta1"
__hexversion__ = "0x010500b1"
__date__ = "2021-08-22"
__status__ = "Stable"
__domain__ = "novelwriter.io"
__url__ = "https://novelwriter.io"
nw/assets/text/release_notes.htm
+61 -51
View File
@@ -2,60 +2,70 @@
<html>
<body>
<h2>Release Notes for 1.4.1</h2>
<p><i>Released on 27 July 2021</i></p>
<h2>Release Notes for 1.5 Beta 1</h2>
<p><i>Released on 22 August 2021</i></p>
<p>This release fixes a couple of minor issue with some of the dialog boxes. The fix was
accidentally left out of release 1.4.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<h4>Novel Document Layouts</h4>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Novel titles need to be altered from "<span class="alt"># Novel Title</span>" to
"<span class="alt">#! Novel Title</span>" and unnumbered chapters from "<span class="alt">##
Chapter Name</span>" or "<span class="alt">## *Chapter Name</span>" to "<span class="alt">##!
Chapter Name</span>". That is all. For inserting page breaks, you can add a single line with the
command "<span class="alt">[NEW PAGE]</span>" where you want the break to be inserted. As before,
page breaks are automatically inserted in front of all partition and chapter titles.</p>
<p>You will find these changes described in more detail the documentation in the
"<a href="https://novelwriter.readthedocs.io/en/latest/usage_projectformat.html#a-prjfmt-1-3">Format
1.3 Changes</a>" section.</p>
<h4>GUI Changes</h4>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<h4>Other Changes</h4>
<p>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.</p>
<p>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.</p>
<p><i>See also the <a href="https://github.com/vkbo/novelWriter/releases">Releases</a> page.</i></p>
<hr/>
<h2>Release Notes for 1.4</h2>
<p><i>Released on 27 July 2021</i></p>
<p>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.</p>
<h3>Internationalisation</h3>
<p>Translation files have been added for Simplified Chinese by Qianzhi Long.</p>
<h3>Line Breaks</h3>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<h3>Text Alignment and Indentation</h3>
<p>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.</p>
<p>The logic of the syntax is as follows:</p>
<p>A single angle bracket will push the text away from the edge it points away from. Therefore, a
single '&gt;' before the paragraph, or a single '&lt;' after the paragraph, will add indentation on
the respective side. It's perfectly valid to do this on both sides at the same time.</p>
<p>A double set of angle brackets will push the text all the way towards the opposite side.
Therefore, a double set of '&gt;&gt;' before the paragraph will indicate right alignment, and a
double set of '&lt;&lt;' after the paragraph will force left alignment. Also here both can be used
at the same time, which results in the paragraph being centred.</p>
<p>Format menu entries and keyboard shortcuts have been added so that you don't have to memorise
these codes.</p>
</body>
</html>
nw/assets/text/release_notes_1.4.htm
+61
View File
@@ -0,0 +1,61 @@
<!DOCTYPE html public "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<body>
<h2>Release Notes for 1.4.1</h2>
<p><i>Released on 27 July 2021</i></p>
<p>This release fixes a couple of minor issue with some of the dialog boxes. The fix was
accidentally left out of release 1.4.</p>
<p><i>See also the <a href="https://github.com/vkbo/novelWriter/releases">Releases</a> page.</i></p>
<hr/>
<h2>Release Notes for 1.4</h2>
<p><i>Released on 27 July 2021</i></p>
<p>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.</p>
<h3>Internationalisation</h3>
<p>Translation files have been added for Simplified Chinese by Qianzhi Long.</p>
<h3>Line Breaks</h3>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<h3>Text Alignment and Indentation</h3>
<p>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.</p>
<p>The logic of the syntax is as follows:</p>
<p>A single angle bracket will push the text away from the edge it points away from. Therefore, a
single '&gt;' before the paragraph, or a single '&lt;' after the paragraph, will add indentation on
the respective side. It's perfectly valid to do this on both sides at the same time.</p>
<p>A double set of angle brackets will push the text all the way towards the opposite side.
Therefore, a double set of '&gt;&gt;' before the paragraph will indicate right alignment, and a
double set of '&lt;&lt;' after the paragraph will force left alignment. Also here both can be used
at the same time, which results in the paragraph being centred.</p>
<p>Format menu entries and keyboard shortcuts have been added so that you don't have to memorise
these codes.</p>
</body>
</html>
nw/constants.py
+1 -1
View File
@@ -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
nw/dialogs/about.py
+6
View File
@@ -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)