|
2 | 2 | <html> |
3 | 3 | <body> |
4 | 4 |
|
5 | | -<h2>Release Notes for 1.5.4</h2> |
| 5 | +<h2>Release Notes for 1.6 Beta 1</h2> |
6 | 6 | <p><i>Released on 4 January 2022</i></p> |
7 | 7 |
|
8 | | -<p>This is a bugfix release that fixes an issues with rendering HTML from a document, either in |
9 | | -the viewer or the build tool, when there is a greater or lesser than symbol in a text block that |
10 | | -isn't a plain text paragraph, like for instance a comment or a heading. Any such document would |
11 | | -fail to render.</p> |
| 8 | +<p>This is a beta release of the next release version, and is intended for testing purposes. Please |
| 9 | +be careful when using this version on live writing projects, and make sure you take frequent |
| 10 | +backups.</p> |
| 11 | +<p>Please check the changelog for an overview of changes. The full release notes will be added to |
| 12 | +the final release.</p> |
12 | 13 |
|
13 | 14 | <p><i>See also the <a href="https://github.com/vkbo/novelWriter/releases">Releases</a> page.</i></p> |
14 | 15 |
|
15 | | -<hr/> |
16 | | - |
17 | | -<h2>Release Notes for 1.5.3</h2> |
18 | | -<p><i>Released on 31 December 2021</i></p> |
19 | | - |
20 | | -<p>This is a bugfix release that fixes two cosmetic issues. The first fix resolves and issue with |
21 | | -the emphasis of partition or chapter items in the project tree not changing when the item is |
22 | | -changed to a scene item. The second fix changes how the Create Root Folder submenu works. Instead |
23 | | -of disabling the menu entries that are no longer available, they are instead removed. Disabled menu |
24 | | -entries are not displayed correctly in all colour themes.</p> |
25 | | - |
26 | | -<hr/> |
27 | | - |
28 | | -<h2>Release Notes for 1.5.2</h2> |
29 | | -<p><i>Released on 12 December 2021</i></p> |
30 | | - |
31 | | -<p>This is a bugfix release that fixes two issues. The first is an issue with an error in the HTML |
32 | | -output if a paragraph has alignment or indentation tags while at the same time containing |
33 | | -emphasised text. The second is an issue where the application cannot load a project with spell |
34 | | -checking enabled if there is something wrong with the spell check package.</p> |
35 | | - |
36 | | -<hr/> |
37 | | - |
38 | | -<h2>Release Notes for 1.5.1</h2> |
39 | | -<p><i>Released on 23 October 2021</i></p> |
40 | | - |
41 | | -<p>This is a bugfix release that fixes two issues. One related to the Project Details dialog |
42 | | -missing its translated labels for non-English languages, and a fix concerning switching focus to |
43 | | -the project tree when the Novel tab is visible. If the Novel tab is selected, the focus shift now |
44 | | -correctly gives focus to the Novel tree.</p> |
45 | | - |
46 | | -<hr/> |
47 | | - |
48 | | -<h2>Release Notes for 1.5</h2> |
49 | | -<p><i>Released on 19 September 2021</i></p> |
50 | | - |
51 | | -<p>This release reduces the number of document layouts from eight to two. The full list of changes |
52 | | -is described in the "Novel Document Layouts" section below.</p> |
53 | | -<p>Due to this change, the main project file for your projects will need to be updated when you |
54 | | -first open them in novelWriter 1.5. This is done automatically. The index is updated as well. When |
55 | | -this conversion is done, you can no longer open the project in an older version of novelWriter.</p> |
56 | | -<p>You may also have to make a handful of changes in your novel documents as novelWriter will not |
57 | | -make any automated changes to your actual text. However, the changes are minimal and in any case |
58 | | -only affects the way your manuscript looks like when exported via the Build Novel Project tool. |
59 | | -These details are also described below.</p> |
60 | | -<p>From this release on, Debian packages will be provided for Mint, Ubuntu and Debian users. A new |
61 | | -<a href="https://launchpad.net/~vkbo/+archive/ubuntu/novelwriter">PPA</a> has also been created. |
62 | | -This allows users to install and update novelWriter automatically on these Linux distros.</p> |
63 | | - |
64 | | -<h4>Novel Document Layouts</h4> |
65 | | -<p>The main change in this release is the significant simplification of document layouts. |
66 | | -Previously, there were seven different layouts available for novel documents, in addition to the |
67 | | -one layout for project notes. The original intention of these layouts were partially to define some |
68 | | -default formatting behaviour when exporting your project, and partially as a way to indicate |
69 | | -whether a specific document was a partition, chapter or scene.</p> |
70 | | -<p>With this release, all the seven layouts for novel documents have been merged into a single |
71 | | -layout called simply "Novel Document". The other layout, "Project Note", remains unchanged. The |
72 | | -functionality provided by the various novel layouts have been implemented in other ways, and a few |
73 | | -new formatting codes have been added to accommodate the formatting functionality lost with the |
74 | | -removal of the layouts. They are all available in the Format and Insert menus.</p> |
75 | | -<p>The changes you need to make to your project should be limited to altering a handful of titles |
76 | | -and maybe insert a page break code here and there. The only title formats you need to update are |
77 | | -those for the main novel title and for your unnumbered chapters, if you have any.</p> |
78 | | -<p>Novel titles need to be altered from "# Novel Title" to "#! Novel Title" and unnumbered chapters |
79 | | -from "## Chapter Name" or "## *Chapter Name" to "##! Chapter Name". That is all. For inserting page |
80 | | -breaks, you can add a single line with the command "[NEW PAGE]" where you want the break to be |
81 | | -inserted. As before, page breaks are automatically inserted in front of all partition and chapter |
82 | | -titles.</p> |
83 | | -<p>You will find these changes described in more detail in the documentation in the |
84 | | -"<a href="https://novelwriter.readthedocs.io/en/latest/usage_projectformat.html#a-prjfmt-1-3">Format 1.3 Changes</a>" |
85 | | -section. |
86 | | - |
87 | | -<h4>GUI Changes</h4> |
88 | | -<p>Due to the above changes, the GUI has been altered a bit. The main changes are in the project |
89 | | -tree. These changes are also reflected in the details panel below the project tree, and to a lesser |
90 | | -extent in the Outline tab.</p> |
91 | | -<p>The layouts were previously a way to indicate the purpose of a specific novel document, like |
92 | | -whether it was a chapter or scene. With these layouts gone, the distinction is instead indicated by |
93 | | -other visual means.</p> |
94 | | -<p>The project index will now record the level of the first header of your document, and select a |
95 | | -different icon for documents with a partition, chapter or scene header. These are colour coded as |
96 | | -green, red, and blue respectively. The project notes have also received a new icon, with a yellow |
97 | | -colour code. Due to this change, the grey icon themes have been removed.</p> |
98 | | -<p>In addition, novel documents with a partition or chapter header will have the document label |
99 | | -viewed as bold and underlined. This feature can be disabled in Preferences if you want a cleaner |
100 | | -look in the project tree.</p> |
101 | | - |
102 | | -<h4>Other Changes</h4> |
103 | | -<p>Several improvements have been made to the project index, which means the index will be |
104 | | -automatically rebuilt when you open a project for the first time in the new version. You will get a |
105 | | -notification about this.</p> |
106 | | -<p>The ODT export tool has also been improved. The code that writes out text paragraphs has been |
107 | | -rewritten and now conforms more closely to the Open Document standard. Most of these improvements |
108 | | -will not be noticeable to you as a user, but you may notice that the exported document will now |
109 | | -allow multiple consecutive spaces. Previously, two spaces, or more, would be concatenated into a |
110 | | -single space in the exported document.</p> |
111 | | -<p>The internal spell check tool has been removed. If you want spell checking, you must install the |
112 | | -Spell Enchant tool. The internal spell checker was only ever added because the Python package for |
113 | | -Spell Enchant was not available on 64-bit Windows. This was corrected over a year ago. The main |
114 | | -issue with the internal spell checker was that it only included English, and the large dictionary |
115 | | -files had to be shipped with novelWriter.</p> |
116 | | -<p>Finally, a PDF version of the documentation should now be shipped with your install package. If |
117 | | -it is available, a "User Manual (PDF)" option should be visible in the Help menu. This should give |
118 | | -you access to the documentation also when you don't have an active internet connection.</p> |
119 | | - |
120 | 16 | </body> |
121 | 17 | </html> |
0 commit comments