taskjuggler 3.6.0 → 3.7.2

data/manual/Tutorial

@@ -13,7 +13,7 @@ grow larger. The complete tutorial example comes with your
 TaskJuggler software installation. You can use the following command
 to find the base directory of the example projects.
 
-  ruby19 -e "puts Gem::Specification.find_by_name('taskjuggler').gem_dir"
+  ruby -e "puts Gem::Specification.find_by_name('taskjuggler').gem_dir"
 
 The file for the tutorial project is called
 ''''examples/Tutorial/tutorial.tjp''''. You can use any plain text
@@ -31,7 +31,7 @@ will result in longer scheduling times and higher memory consumption.
 
 <[example file="tutorial" tag="header1"]>
 
-All TaskJuggler properties have a unique ID ,a name, and a set of
+All TaskJuggler properties have a unique ID, a name, and a set of
 optional attributes. The name must always be specified. The ID can be
 omitted if you never have to reference the property from another
 context. If you omit the ID, TaskJuggler will automatically generate a
@@ -75,7 +75,7 @@ The [[currency]] attribute specifies the unit of all currency values.
 <[example file="tutorial" tag="currency"]>
 
 Because each culture has its own way of specifying dates and numbers,
-the format for these are configurable.  Use the [[timeformat]]
+the format for these is configurable.  Use the [[timeformat]]
 attribute to specify the default format for dates. This format is used
 for reports, it does not affect the way you specify dates in the
 project files. Here you always need to use the [[date|TaskJuggler date
@@ -148,7 +148,7 @@ does not do any resource assignments to tasks.
 
 Use the [[leaves]] attribute to define a global holiday. Global
 holidays may have a name and must have a date or date range. Other leaves for
-individual resources or groups of resources can be defines similarly.
+individual resources or groups of resources can be defined similarly.
 
 === Macros ===
 
@@ -189,6 +189,8 @@ In order not to get lost with all the various amounts, we declare 3
 [[account|accounts]] to credit the amounts to. We create one account
 for the development costs, one for the documentation costs, and one
 for the customer payments.
+Actually, there is a fourth account consisting of two accounts nested
+into it.
 
 <[example file="tutorial" tag="accounts"]>
 
@@ -308,7 +310,7 @@ should be allocated to the task. The task won't finish before the
 resources could be allocated long enough to reach the specified
 effort. Tasks with ''''length'''' or ''''duration'''' criteria and
 allocated resources will last exactly as long as requested. Resources
-will be allocated only if available. It's possible that such a tasks
+will be allocated only if available. It's possible that such a task
 ends up with no allocations at all if the resources are always
 assigned to other tasks for that period. Each task can only have one
 of the three duration criteria. Container tasks may never have a
@@ -331,7 +333,7 @@ and end criteria of a task, or one of them and a duration
 specification. The start and end criteria can either be fixed dates or
 relative dates. Relative dates are specifications of the type ''task B
 starts after task A has finished''. Or in other words, task B depends
-on task A. In this example the spec task depends on a subtasks of the
+on task A. In this example the spec task depends on a subtask of the
 deliveries task. We have not specified it yet, but it has the local ID
 ''''start''''.
 
@@ -347,7 +349,7 @@ specification task would be ''''AcSo.spec''''.
 Relative IDs always start with one or more exclamation marks. Each
 exclamation mark moves the scope to the next enclosing task. So
 ''''!deliveries.start'''' is expanded to ''''AcSo.deliveries.start''''
-since ''''AcSo'''' is the enclosing task of deliveries. Relative task
+since ''''AcSo'''' is the enclosing task of ''''deliveries''''. Relative task
 IDs are a little bit confusing at first, but have a real advantage
 over absolute IDs.  Sooner or later you want to move tasks around in
 your project and then it's a lot less likely that you have to fix
@@ -362,7 +364,7 @@ We use the [[priority]] attribute to mark the importance of
 the tasks. 500 is the default priority of top-level tasks. Setting the
 priority to 1000 marks the task as most important task, since the
 possible range is 1 (not important at all) to 1000 (ultimately
-important). priority is an attribute that is passed down to subtasks
+important). ''''priority'''' is an attribute that is passed down to subtasks
 if specified before the subtasks' declaration. So all subtasks of
 software have a priority of 1000 as well, unless they have their own
 priority definition.
@@ -486,7 +488,7 @@ scheduled. But no reports would be generated to visualize the results.
 
 === Visualizing the Project ===
 
-To see and share the project data you reports can be generated. You
+To see and share the project data, reports can be generated. You
 can generate any number of reports and you can select from a variety
 of report types and output formats. To have a report generated after
 the project scheduling has been completed, you need include a report
@@ -645,7 +647,7 @@ For HTML output, the reference is a click-able link to the referenced
 report file.
 
 For the [[footer]] we can proceed accordingly. We just add a few more
-paragraphs of text the describe certain aspects of the project. By
+paragraphs of text to describe certain aspects of the project. By
 putting it all together, we end up with the following report
 definition.
 
@@ -653,7 +655,7 @@ definition.
 
 The generated report can be found
 [http://www.taskjuggler.org/tj3/examples/Tutorial/Overview.html
-here]. It servers as an entry page for the other reports. While it
+here]. It serves as an entry page for the other reports. While it
 already contains some references, a navigator bar would be handy as
 well. Fortunately, there is a block generator called 'navigator' to
 take care of this. But before we can include the navigator in the

data/manual/html/Day_To_Day_Juggling.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>Day_To_Day_Juggling</title>
@@ -24,7 +24,7 @@
   <div style="width:90%; margin-left:5%; margin-right:5%"><div class="manual">
     <h1 class="manual" id="Day_To_Day_Juggling">7 Day To Day Juggling</h1>
     <h2 class="manual" id="Working_with_multiple_scenarios">7.1 Working with multiple scenarios</h2>
-    <p class="manual">To analyze the impact that a small variation can have on a project, TaskJuggler supports an unlimited amount of scenarios. Each additional scenario is a slight derivation of the it's parent. The task tree structure needs to be the same for all scenarios, but most attributes can vary from one scenario to another. Several report types support comparative listing of multiple <a href="scenarios.html">scenarios</a>.</p>
+    <p class="manual">To analyze the impact that a small variation can have on a project, TaskJuggler supports an unlimited amount of scenarios. Each additional scenario is a slight derivation of it's parent. The task tree structure needs to be the same for all scenarios, but most attributes can vary from one scenario to another. Several report types support comparative listing of multiple <a href="scenarios.html">scenarios</a>.</p>
     <p class="manual">By default, TaskJuggler knows about one scenario, called <code class="manual">plan</code>. The name of this scenario can be changed just like you can add more scenarios in the <a href="project.html">project</a> section of your project files.</p>
     <div class="codeframe"><pre class="code">project "Example" 2007-05-29 - 2007-07-01 {
   timezone "America/Denver"
@@ -119,7 +119,7 @@
      <li>
       <b>Time sheets</b>: Every project contributor needs to fill out a <a href="timesheet.html">time sheet</a> once a week. To simplify this task as much as possible, a template will be send out by email. The template already lists all tasks that were planned for this week to work on with the respective effort values and end dates. It also provides sections for textual status reports. The contributor needs to review and complete the time sheet and has to send it back via email. TaskJuggler validates the submission and returns an email with either an error message or a nicely formatted version of the time sheet.</li>
      <li>All time sheets must be submitted by a certain deadline, e. g. midnight on Sunday. TaskJuggler will then compile a summary report and sent it out to a list of interested parties. It will also detect missing time sheets and will send out a reminder to those contributors that have not submitted their report.</li>
-     <li>On Monday the project managers need to review the time sheets and update the plan accordingly. TaskJuggler can compile a list changes compared to the plan. This makes it easy to update the plan according to the actual progress that was made. The closer the actuals match the plan the less work this is. The project managers now generate bookings for the last week and add them to the database with previous bookings. Doing so, will prevent changes to the plan to affect the past. Only the future will be modified.</li>
+     <li>On Monday the project managers need to review the time sheets and update the plan accordingly. TaskJuggler can compile a list of changes compared to the plan. This makes it easy to update the plan according to the actual progress that was made. The closer the actuals match the plan the less work this is. The project managers now generate bookings for the last week and add them to the database with previous bookings. Doing so will prevent changes to the plan to affect the past. Only the future will be modified.</li>
      <li>Once the plan has been updated, managers will receive their status sheet templates per email. Each manager will get the information for the tasks that they are <a href="responsible.html">responsible</a> for. To consolidate the information for the next manager in the reporting chain they can moderate the reports in three ways. Consolidated manager reports are called dashboard reports.</li>
      <ol>
       <li>A status report for a task can be removed from the dashboard.</li>
@@ -312,18 +312,18 @@ include</a> this file at the end of your project header section.</p>
     <p class="manual">The booking file must be <a href="include.properties.html">included</a> at the end of your main project file.</p>
     <p class="manual">In case there are still some discrepancies between the booking data and the actual assignments of the resources, you can edit the booking file to correct the data.</p>
     <p class="manual">The next time you run <code class="manual">tj3</code> with your project, all assignments prior to the date in the project header file will be taken only from the bookings file. All assignments after this date will be determined by the scheduler according to your provided constraints.</p>
-    <p class="manual">When you run <code class="manual">tj3 --freeze</code> again, it will update the header and booking files. Since you have included your booking file, any modifications you have made, will be preserved. That is, the actual data will be preserved, not the formatting since the file will be completely re-generated again.</p>
+    <p class="manual">When you run <code class="manual">tj3 --freeze</code> again, it will update the header and booking files. Since you have included your booking file, any modifications you have made will be preserved. That is, the actual data will be preserved, not the formatting since the file will be completely re-generated again.</p>
     <h3 class="manual" id="Status_Sheets">7.7.1 Status Sheets</h3>
     <p class="manual">For larger projects with many contributors the flood of time sheets can become hard to manage. Higher level managers are usually not interested in all the details as long as the project executes according to plan. To keep the managers on each level informed with the proper amount and content TaskJuggler provides the concept of status sheets.</p>
     <p class="manual">To use status sheets, the reporting chains must be reflected in the task hierarchy of the project. The <a href="responsible.html">responsible</a> attribute must be used to assign tasks to managers. Leaf tasks or whole sub trees must be assigned to the lowest level of management. The responsibility for one or more level of parent tasks must be assigned to the next level of managers and so on.</p>
     <p class="manual">When all time sheets have been submitted, the reports for all tasks are sent to the responsible managers for these tasks. The information is generated by the <code class="manual">tj3ss_sender</code> program and is called a status report template. Each manager will get one template that includes the status reports for the tasks they are responsible for.</p>
-    <p class="manual">It's not the managers task to prepare the report for the next level of management. To do this, the manager has 3 options:</p>
-    <ul><li>Forward the status report of a task directly to the next level. The original authorship can be keep or removed. The content can also be edited if needed.</li></ul>
+    <p class="manual">It's the managers task to prepare the report for the next level of management. To do this, the manager has 3 options:</p>
+    <ul><li>Forward the status report of a task directly to the next level. The original authorship can be kept or removed. The content can also be edited if needed.</li></ul>
     <ul><li>Similar reports for a task or a whole task sub-tree can be combined into just one report. To achieve this a new task report must be created for the parent tasks of these lower-level tasks. This will replace all reports for sub tasks with this newly created report.</li></ul>
     <ul><li>A task report can simply be removed from the status report.</li></ul>
     <p class="manual">The status sheet template is designed to perform all three actions in a simple manner. The original reports are commented out. To remove a report, it needs to be uncommented and the headline must be set to an empty string. To change a report, the text must be edited after the comment marks have been removed. To create a summary report for a group of tasks, a new report for the common parent task must be created.</p>
     <h3 class="manual" id="The_Status_Sheet_Template_Sender">7.7.2 The Status Sheet Template Sender</h3>
-    <p class="manual">To send out the time sheets, the command <code class="manual">tj3ts_sender</code> must be used. It will use the <code class="manual">tj3client</code> program to do retrieve the necessary data from the TaskJuggler server.</p>
+    <p class="manual">To send out the time sheets, the command <code class="manual">tj3ts_sender</code> must be used. It will use the <code class="manual">tj3client</code> program to retrieve the necessary data from the TaskJuggler server.</p>
     <p class="manual">Before the program can be used, a new section must be added to the TaskJuggler configuration file.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">_statussheets:
   projectId: prj
@@ -341,7 +341,7 @@ include</a> this file at the end of your project header section.</p>
     <p class="manual">By sending an email to statussheet-request@taskjuggler.your_company.com and putting their resource ID in the subject of the email, managers will receive an email with the status sheet template. The email will be sent to the email address in the project plan, not the sender of the request email.</p>
     <p class="manual">The setup described here only works for first-level managers. By adding more email addresses, this can easily be extended for more levels of management. You just need to make sure that <code class="manual">tj3ss_sender</code> is called with the proper parameters to change the resource selection and end date.</p>
     <h3 class="manual" id="The_Status_Sheet_Receiver">7.7.4 The Status Sheet Receiver</h3>
-    <p class="manual">Similarly to the time sheets a the completed status sheets must be send back by email. We already described how the necessary email aliases should be configured. For status sheets the address <code class="manual">statussheets@taskjuggler.your_company.com</code> can be used.</p>
+    <p class="manual">Similarly to the time sheets, the completed status sheets must be send back by email. We already described how the necessary email aliases should be configured. For status sheets the address <code class="manual">statussheets@taskjuggler.your_company.com</code> can be used.</p>
     <p class="manual">The incoming emails will then be forwarded to the <code class="manual">tj3ss_receiver</code> program that will process them. To use it, you first need to add the following settings to the <code class="manual">statussheets</code> section of your TaskJuggler configuration file:</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">_statussheets:
   projectId: prj
@@ -360,6 +360,6 @@ include</a> this file at the end of your project header section.</p>
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/Getting_Started.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>Getting_Started</title>
@@ -59,6 +59,6 @@ accounts</a>, <a href="resource.html">resources</a>, <a href="task.html">tasks</
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/How_To_Contribute.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>How_To_Contribute</title>
@@ -90,6 +90,6 @@ rake gem
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/Installation.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>Installation</title>
@@ -54,7 +54,7 @@
     <p class="manual">This will download and install the latest version from the <a href="http://rubygems.org/gems/taskjuggler" target="_top">RubyGems.org</a> site.</p>
     <h4 class="manual" id="Installation_into_a_local_Directory">2.2.1.2 Installation into a local Directory</h4>
     <p class="manual">If you don't want to install TaskJuggler for all users on the system, you can also install it into your home or data directory. This does not require root or admin permissions.</p>
-    <p class="manual">The following steps are describe the installation on a Linux system with the bash shell. You may have to use slightly different commands on a different operating system.</p>
+    <p class="manual">The following steps describe the installation on a Linux system with the bash shell. You may have to use slightly different commands on a different operating system.</p>
     <p class="manual">Create a new directory <code class="manual">taskjuggler</code> in your $HOME directory for the installation to go into.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1"> mkdir taskjuggler
 </pre></div>
@@ -71,7 +71,7 @@
     <div class="manual" codesection="1"><pre class="manual" codesection="1"> export GEM_HOME=${HOME}/taskjuggler
 </pre></div>
     <p class="manual">The last two settings should also be added to your .profile file to make them permanent.</p>
-    <p class="manual">That's it. You now should be run TaskJuggler.</p>
+    <p class="manual">That's it. You now should run TaskJuggler.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1"> tj3 --version
 </pre></div>
     <h3 class="manual" id="The_manual_way">2.2.2 The manual way</h3>
@@ -101,7 +101,7 @@
     <p class="manual">Then checkout the source code with the following command</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">git clone git@github.com/taskjuggler/TaskJuggler.git
 </pre></div>
-    <p class="manual">Make sure, you have removed all previously installed instances of TaskJuggler from your system before doing so. It is a common mistake to have an old version of the TaskJuggler installed and then use parts of the old and new version together.</p>
+    <p class="manual">Make sure you have removed all previously installed instances of TaskJuggler from your system before doing so. It is a common mistake to have an old version of the TaskJuggler installed and then use parts of the old and new version together.</p>
     <p class="manual">If your Ruby installation does not come with the <a href="http://rake.rubyforge.org" target="_top">Rake</a> build tool, you need to install it now.</p>
     <p class="manual">If you are interested in a code coverage analysis, you need to also install the <a href="http://eigenclass.org/hiki.rb?rcov" target="_top">rcov</a> code coverage analysis tool. This tool is not needed for most developers. You can safely ignore the warning during rake builds if you don't have it installed.</p>
     <p class="manual">The following command will create a gem package from the source code.</p>
@@ -155,7 +155,7 @@ export PATH=${PATH}:${TASKJUGGLER_DIR}/bin
     <p class="manual">Log out and back in again. Now</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1"> which ruby
 </pre></div>
-    <p class="manual">should show return the path to the link to your <code class="manual">${HOME}/bin/ruby</code>. You now have the latest Ruby installed and are ready to use TaskJuggler.</p>
+    <p class="manual">should return the path to the link to your <code class="manual">${HOME}/bin/ruby</code>. You now have the latest Ruby installed and are ready to use TaskJuggler.</p>
     <p class="manual">As a final step, you need to install the <code class="manual">mail</code> and <code class="manual">term-ansicolor</code> gems.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1"> sudo gem19 install mail term-ansicolor
 </pre></div>
@@ -163,7 +163,7 @@ export PATH=${PATH}:${TASKJUGGLER_DIR}/bin
     <div class="manual" codesection="1"><pre class="manual" codesection="1"> sudo gem19 install taskjuggler
 </pre></div>
     <h2 class="manual" id="Installing_the_Vim_Support">2.7 Installing the Vim Support</h2>
-    <p class="manual">TaskJuggler can be used with any text editor that supports UTF-8 text file editing. If you don't have a preference yet, we recommend to try the <a href="http://www.vim.org" target="_top">Vim</a> text editor. It's a very powerful editor and it has been customized for better integration with TaskJuggler. This section describes, how to activate and use the Vim integration. Vim is provided by pretty much any Linux distribution and also works well on MacOX and Windows. See the web page for how to install it if you don't have it yet.</p>
+    <p class="manual">TaskJuggler can be used with any text editor that supports UTF-8 text file editing. If you don't have a preference yet, we recommend to try the <a href="http://www.vim.org" target="_top">Vim</a> text editor. It's a very powerful editor and it has been customized for better integration with TaskJuggler. This section describes how to activate and use the Vim integration. Vim is provided by pretty much any Linux distribution and also works well on MacOX and Windows. See the web page for how to install it if you don't have it yet.</p>
     <p class="manual">This section describes the integration on Linux. Please see the <a href="How_To_Contribute.html">How_To_Contribute</a> section if you want to contribute the description for another OS.</p>
     <p class="manual">If you have never customized Vim, you need to create a few directories first.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1"> cd ${HOME}
@@ -173,7 +173,7 @@ export PATH=${PATH}:${TASKJUGGLER_DIR}/bin
     <p class="manual">Then copy the syntax file <code class="manual">tjp.vim</code> into the vim syntax directory. The following command works if you have installed TaskJuggler as a gem with the system provided Ruby. For other cases, you may have to modify it accordingly.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1"> cp `gem contents taskjuggler | fgrep tjp.vim` .vim/syntax
 </pre></div>
-    <p class="manual">Now we have to make sure, Vim detects the file. Edit the <code class="manual">.vim/filetype.vim</code> file to contain the following section.</p>
+    <p class="manual">Now we have to make sure Vim detects the file. Edit the <code class="manual">.vim/filetype.vim</code> file to contain the following section.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">augroup filetypedetect
 au BufNewFile,BufRead *.tjp,*.tji               setf tjp
 augroup END
@@ -200,6 +200,6 @@ augroup END
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/Intro.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>Intro</title>
@@ -99,6 +99,6 @@
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/List_Attributes.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>List_Attributes</title>
@@ -40,7 +40,7 @@
 }
 </pre></div>
     <p class="manual">In this example, task <code class="manual">T3</code> has the flags <code class="manual">f1</code> and <code class="manual">f2</code> assigned.</p>
-    <p class="manual">The same works for scenarios as well. Even though the syntax may not look like inheritance is at play the scenario <code class="manual">s2</code> inherits all values from <code class="manual">s1</code>.</p>
+    <p class="manual">The same works for scenarios as well. Even though the syntax may not look like inheritance is at play, the scenario <code class="manual">s2</code> inherits all values from <code class="manual">s1</code>.</p>
     <div class="codeframe"><pre class="code">project "List attributes" 2014-04-06 +1m {
   scenario s1 "S1" {
     scenario s2 "S2"
@@ -71,6 +71,6 @@ task "T4" {
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/Reporting_Bugs.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>Reporting_Bugs</title>
@@ -44,6 +44,6 @@
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/Rich_Text_Attributes.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>Rich_Text_Attributes</title>
@@ -85,7 +85,7 @@ This is a '''''italic and bold''''' word.
     <p class="manual">In some situations, it is desirable to not interpret certain markup sequences and reproduce the text verbatim. Such text must be enclosed in nowiki tags.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">&lt;nowiki&gt; This is not '''bold''' text. &lt;/nowiki&gt;
 </pre></div>
-    <p class="manual">You can also insert raw HTML code by enclosing it in <b>&lt;html&gt;...&lt;/html&gt;</b> tags. For all other output formats, this content will be ignored. There is also no error checking if the code is valid! Use this feature very carefully.</p>
+    <p class="manual">You can also insert raw HTML code by enclosing it in <b>&lt;html&gt;...&lt;/html&gt;</b> tags. For all other output formats, this content will be ignored. There is also no error checking whether the code is valid! Use this feature very carefully.</p>
     <h3 class="manual" id="Block_and_Inline_Generators">5.4.3 Block and Inline Generators</h3>
     <p class="manual">Block and inline generators are a very powerful extension that allow you to insert arbitrarily complex content. Block generators create a text block whereas inline generators generate an element that fits inside a text paragraph.</p>
     <p class="manual">Block generators use the following syntax:</p>
@@ -120,7 +120,7 @@ This is a '''''italic and bold''''' word.
     <ul><li>
       <code class="manual">id</code> : ID of a defined report</li></ul>
     <ul><li>
-      <code class="manual">attributes</code>: A set of attributes that override the original attributes of the referenced report. All report attributes are supported. Since the value of attributes already must be enclosed by single or double quotes, all single or double quotes contained in the string must be escaped with backslashes. This feature enables reports with content that is customized based on where they have been referenced from. It requires the reports to be dynamically generated and is only available when used with the <code class="manual">tj3d</code> web server. The <code class="manual">tj3</code> application will ignore the attributes setting.</li></ul>
+      <code class="manual">attributes</code>: A set of attributes that override the original attributes of the referenced report. All report attributes are supported. Since the values of attributes already must be enclosed by single or double quotes, all single or double quotes contained in the string must be escaped with backslashes. This feature enables reports with content that is customized based on where they have been referenced from. It requires the reports to be dynamically generated and is only available when used with the <code class="manual">tj3d</code> web server <code class="manual">tj3webd</code>. The <code class="manual">tj3</code> application will ignore the attributes setting.</li></ul>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">taskreport "All" {
   formats html
   columns name { 
@@ -163,7 +163,7 @@ taskreport taskRep "Task" {
     <ul><li>
       <code class="manual">currencyformat</code> : The <a href="currencyformat.html">currencyformat</a> used to format currency values.</li></ul>
     <p class="manual">The query generator inserts any requested value from the project, a task or a resource.</p>
-    <p class="manual">Queries are context aware. Depending on the context where the query is used, certain or all of the above parameters have already predefined values. When used in the header section of a report, the context does not provide a property or scope property. Start and end dates as well the formatting options are taken from the report context. But when used e. g. in <a href="celltext.column.html">celltext.column</a> the cell provides, that property and the attribute and possibly even the scope property.</p>
+    <p class="manual">Queries are context aware. Depending on the context where the query is used, certain or all of the above parameters have already predefined values. When used in the header section of a report, the context does not provide a property or scope property. Start and end dates as well the formatting options are taken from the report context. But when used e. g. in <a href="celltext.column.html">celltext.column</a>, the cell provides that property and the attribute and possibly even the scope property.</p>
    </div></div>
   <br/>
   <hr/>
@@ -174,6 +174,6 @@ taskreport taskRep "Task" {
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/Software.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>Software</title>
@@ -23,7 +23,7 @@
   <br/>
   <div style="width:90%; margin-left:5%; margin-right:5%"><div class="manual">
     <h1 class="manual" id="The_TaskJuggler_Software">6 The TaskJuggler Software</h1>
-    <p class="manual">After the installation of a software package the first questions that most users have is <i>"How do I run it?"</i>. Many users expect to find an icon on their desktop or an entry in the start menu hierarchy. Don't bother looking for them, you won't find any for TaskJuggler. As we have mentioned before, TaskJuggler is a command line program. All the components are started from a shell by typing in the command name.</p>
+    <p class="manual">After the installation of a software package the first question that most users have is <i>"How do I run it?"</i>. Many users expect to find an icon on their desktop or an entry in the start menu hierarchy. Don't bother looking for them, you won't find any for TaskJuggler. As we have mentioned before, TaskJuggler is a command line program. All the components are started from a shell by typing in the command name.</p>
     <p class="manual">This chapter describes the most important TaskJuggler commands and how to use them. If you haven't used command line programs before, don't worry - you will quickly get used to it.</p>
     <h2 class="manual" id="tj3">6.1 <code class="manual">tj3</code>
     </h2>
@@ -74,7 +74,7 @@ shift.timesheet
     <p class="manual">The same information that is available in your shell is also available in your web browser.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">tj3man --html &lt;keyword&gt;
 </pre></div>
-    <p class="manual">The latter defaults to using the <a href="http://www.mozilla.com/en-US/firefox/new/" target="_top">Mozilla Firefox</a> web browser . Please see</p>
+    <p class="manual">The latter defaults to using the <a href="http://www.mozilla.com/en-US/firefox/new/" target="_top">Mozilla Firefox</a> web browser. Please see</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">tj3man --help
 </pre></div>
     <p class="manual">how to use a different browser. If you omit the keyword, you will get this user manual (browser).</p>
@@ -82,7 +82,7 @@ shift.timesheet
     </h2>
     <p class="manual">
      <code class="manual">tj3d</code> is the TaskJuggler daemon. It is a program that runs in the background, disconnected from your shell to provide certain services. It can generate reports on demand and processes incoming time sheets or status reports.</p>
-    <p class="manual">Depending on the size of your project the scheduling time can take several minutes or more. Since all operations need to be done on the data of a scheduled project, it makes sense to have this data readily available. This is the job of the TaskJuggler server or daemon in Linux lingo. The program is called <code class="manual">tj3d</code>. When started, it automatically disconnects from the terminal and runs in the background. All interactions with the server are done via the TCP/IP protocol. For security reasons, only connections from the same machine (localhost) are accepted. To get access all clients must provide an authentication key. A TaskJuggler server can serve any number of projects. Once a project has been loaded successfully, clients can retrieve the data in form of reports. Projects are identified by their project ID. If a newly added project has the same ID such as an already loaded project, the new project will replace the old project once it was scheduled successfully. Before you start the server, you need to provide a configuration file with some basic settings.</p>
+    <p class="manual">Depending on the size of your project the scheduling time can take several minutes or more. Since all operations need to be done on the data of a scheduled project, it makes sense to have this data readily available. This is the job of the TaskJuggler server or daemon in Linux lingo. The program is called <code class="manual">tj3d</code>. When started, it automatically disconnects from the terminal and runs in the background. All interactions with the server are done via the TCP/IP protocol. For security reasons, only connections from the same machine (localhost) are accepted. To get access, all clients must provide an authentication key. A TaskJuggler server can serve any number of projects. Once a project has been loaded successfully, clients can retrieve the data in form of reports. Projects are identified by their project ID. If a newly added project has the same ID as an already loaded project, the new project will replace the old project once it was scheduled successfully. Before you start the server, you need to provide a configuration file with some basic settings.</p>
     <p class="manual">All taskjuggler components can use the same TaskJuggler configuration file. The format is a simple plain text format that follows the <a href="http://www.yaml.org/" target="_top">YAML specification</a>. The file should be called <code class="manual">.taskjugglerrc</code> or <code class="manual">taskjuggler.rc</code>. The settings are structured by sections. Section names always start with an underscore.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">_global:
   authKey: topsecret
@@ -100,7 +100,7 @@ shift.timesheet
      <li>3: Like 2, but additionally with information messages</li>
      <li>4: Like 3, but additionally with debug messages</li>
     </ul>
-    <p class="manual">The configuration file will be searched in the current directory, the current user's home directory or <code class="manual">/etc</code>. You can also explicitly tell the server where to find the configuration file with the <code class="manual">-c</code> option. See</p>
+    <p class="manual">The configuration file will be searched for in the current directory, the current user's home directory or <code class="manual">/etc</code>. You can also explicitly tell the server where to find the configuration file with the <code class="manual">-c</code> option. See</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">tj3d --help
 </pre></div>
     <p class="manual">for details.</p>
@@ -134,7 +134,7 @@ shift.timesheet
   authKey: topsecret
   webServerPort: 8080
 </pre></div>
-    <p class="manual">To access the HTML reports point your web browser to <code class="manual">http://localhost:8080/taskjuggler</code>. This assumes that the server is running on your local machine. You will then see a list of all loaded projects. Click on the project name to get a list of all reports for this project.</p>
+    <p class="manual">To access the HTML reports, point your web browser to <code class="manual">http://localhost:8080/taskjuggler</code>. This assumes that the server is running on your local machine. You will then see a list of all loaded projects. Click on the project name to get a list of all reports for this project.</p>
     <p class="manual"><i>WARNING: Please be aware that the web server when you have started it can be accessed by anybody on your local machine and by anybody that can reach your machine over the network! It will serve all reports of all projects that are hosted by the TaskJuggler daemon.</i></p>
    </div></div>
   <br/>
@@ -146,6 +146,6 @@ shift.timesheet
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/TaskJuggler_2x_Migration.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>TaskJuggler_2x_Migration</title>
@@ -66,6 +66,6 @@ applied</a> to certain resources.</li></ul>
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/TaskJuggler_Internals.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>TaskJuggler_Internals</title>
@@ -27,7 +27,7 @@
     <h2 class="manual" id="How_the_Scheduler_works">8.1 How the Scheduler works</h2>
     <p class="manual">It's important to understand that the scheduler implementation is not an optimization algorithm. It does not search a solution space and evaluates various alternative results against each other. This has been tried, but for any real-world project, the solution space becomes unmanageable and scheduling runs took hours to complete.</p>
     <p class="manual">Instead, we use a heuristic to decide when each task gets its resources assigned. This heuristic is certainly not perfect but has shown good results with fairly moderate computation costs. The following sections contain an overview of the scheduling algorithm. Users are also encouraged to read the actual source code. It can be found in <code class="manual">Project.rb</code>, <code class="manual">TaskScenario.rb</code>, <code class="manual">ResourceScenario.rb</code> and <code class="manual">Allocation.rb</code>. All these files can be found in the <code class="manual">lib/taskjuggler</code> directory. You can also browse the sources on <a href="https://github.com/taskjuggler/TaskJuggler" target="_top">github</a>.</p>
-    <p class="manual">The scheduler needs to determine the start and end date for all tasks that don't have such dates yet. To deal with multiple concurrent time zones, all time related events are stored internally as UTC time.Additionally, it allocates resources to tasks. All events such as start or end of a task, or allocation of a resource can only happen aligned with the <a href="timingresolution.html">timing resolution</a>. This determines the smallest possible allocation period that we call a time slot. The duration of the slot can be set by the user. Possible values are 5, 10, 15, 30 and 60 minutes.</p>
+    <p class="manual">The scheduler needs to determine the start and end date for all tasks that don't have such dates yet. To deal with multiple concurrent time zones, all time related events are stored internally as UTC time. Additionally, it allocates resources to tasks. All events such as start or end of a task, or allocation of a resource can only happen aligned with the <a href="timingresolution.html">timing resolution</a>. This determines the smallest possible allocation period that we call a time slot. The duration of the slot can be set by the user. Possible values are 5, 10, 15, 30 and 60 minutes.</p>
     <p class="manual">TaskJuggler keeps a scoreboard for each time slot for each leaf resource. Each scoreboard entry specifies whether the resource is unassigned, assigned to a specific task or on leave. This explains why the project duration and number of allocated resources determines the memory usage of the scheduler.</p>
     <p class="manual">For the scheduling of the project, the scheduler only looks at leave tasks that are not milestones. Container tasks and milestones are scheduled once all necessary information is available. During the scheduling process, leave tasks can have 3 different states.</p>
     <ol>
@@ -38,14 +38,14 @@
      <li>
       <code class="manual">Scheduling completed</code>: The task has a start and end date and resources have been assigned for all time slots.</li>
     </ol>
-    <p class="manual">The goal of the scheduler is to transfer all tasks in the completed state. Until this goal has been reached, at least one tasks needs to be in the ready state. If that's not the case, the project schedule cannot be determined and an error is raised. In case there are more than one task in the ready state, we need to have a well defined priority of the tasks. This is necessary since those ready tasks may compete for the same resource in the same time slot.</p>
+    <p class="manual">The goal of the scheduler is to transfer all tasks in the completed state. Until this goal has been reached, at least one task needs to be in the ready state. If that's not the case, the project schedule cannot be determined and an error is raised. In case there are more than one task in the ready state, we need to have a well defined priority of the tasks. This is necessary since those ready tasks may compete for the same resource in the same time slot.</p>
     <p class="manual">The priority can be directly influenced by the user with the <a href="priority.html">priority</a> attribute. This user-defined priority always trumps the other internal criteria described below. In case two tasks have the same priority, an additional measure is used. This measure is called path criticalness. The path criticalness is calculated for each leaf task. The path criticalness is a measure for how important the task is to keep the overall project duration (start of first task to end of last task) to a minimum.</p>
     <p class="manual">To determine the path criticalness, we first need to determine the resource criticalness first. This is a measure for how likely the tasks that have this resource in their allocation list will actually get the resource. A resource criticalness larger than 1.0 means that statistically, at least one tasks will not get enough of this resource. This is just a statistical measure based on the total requested allocations and the number of available work time.</p>
     <p class="manual">Once we have determined the criticalness of all allocated resources, we can calculate the criticalness of each individual task. This really only matters for <a href="effort.html">effort</a> based tasks. These really need their allocations to be finished within a limited amount of time. For <a href="length.html">length</a> and <a href="duration.html">duration</a> tasks, the allocations are by definition optional. The user can still influence the allocation to length and duration tasks by adjusting the priority appropriately. However, there is no guarantee that such tasks will ever get any resources assigned. The criticalness of an effort based task is defined as the average of the criticalness of the resources allocated to this task.</p>
     <p class="manual">We also assign a criticalness to milestones. Based on their priority a criticalness between 0 and 2.0 is assigned. This is done to reflect the user perception that milestones are usually some important goal of the project.</p>
     <p class="manual">The final step is now the computation of the path criticalness for each effort-based leaf task. For each possible chain of task (path) that is going through a task, the sum of the criticalness values of the tasks of the path is computed. The largest sum is the path criticalness of that task.</p>
-    <p class="manual">This heuristic will favor allocations to task with critical resources and long dependency chains. As a result, the critical paths of the project are tried to be kept short. The user can use the <b>criticalness</b> and <b>pathcriticalness</b> <a href="columnid.html">columns</a> to review the respective values for he project's tasks and resources.</p>
-    <p class="manual">When the criticalness and pathcriticalness for all leaf resources and tasks has been determined, the leaf tasks are sorted by priority (hight to low), then by pathcricialness (high to low) and then by the index (low to high). In a loop that is terminated when all tasks have been scheduled or an error condition has been detected, the first task that is ready for scheduling is completely scheduled. This means that resources are allocated for all time slots and missing dates are being computed. The newly determined end (for ASAP tasks) or start (for ALAP tasks) date is then propagated to dependent tasks, milestones or parent tasks if needed. This can result in other tasks becoming ready for scheduling and the list is searched again for the first task that is ready for scheduling to be scheduled.</p>
+    <p class="manual">This heuristic will favor allocations to tasks with critical resources and long dependency chains. As a result, the critical paths of the project are tried to be kept short. The user can use the <b>criticalness</b> and <b>pathcriticalness</b> <a href="columnid.html">columns</a> to review the respective values for he project's tasks and resources.</p>
+    <p class="manual">When the criticalness and pathcriticalness for all leaf resources and tasks has been determined, the leaf tasks are sorted by priority (high to low), then by pathcricialness (high to low) and then by the index (low to high). In a loop that is terminated when all tasks have been scheduled or an error condition has been detected, the first task that is ready for scheduling is completely scheduled. This means that resources are allocated for all time slots and missing dates are being computed. The newly determined end (for ASAP tasks) or start (for ALAP tasks) date is then propagated to dependent tasks, milestones or parent tasks if needed. This can result in other tasks becoming ready for scheduling and the list is searched again for the first task that is ready for scheduling to be scheduled.</p>
     <p class="manual">A task can only be scheduled when it is ready for scheduling. This means that at least the start date for the scheduling process must be known. For ASAP (As Soon As Possible) tasks, the scheduler start date is the start date of the task. For ALAP (As Late As Possible) tasks the scheduler start date is the end date of the task. ASAP task will be scheduled from start to end, ALAP tasks from end to start. This is important to understand as resource assignments for each time slot will be determined in this order.</p>
     <p class="manual">Mixing ASAP and ALAP tasks in the same project is supported but should be used very carefully. It can lead to situations where a lower priority tasks that is earlier in the scheduling process ready for scheduling takes away resources from a higher prioritized task that competes for the same resources. This condition is known is priority inversion. If the scheduler detects such a situation, a warning is generated.</p>
    </div></div>
@@ -58,6 +58,6 @@
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>

data/manual/html/The_TaskJuggler_Syntax.html

@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.2 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>The_TaskJuggler_Syntax</title>
@@ -35,7 +35,7 @@
     <p class="manual">List of predefined options are enclosed in brackets, the options separated by a vertical bar.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">keyword ( foo | bar | foobar )
 </pre></div>
-    <p class="manual">Some keywords take one or more arguments. These are known as list attributes. The arguments are comma separated. The tree dots in the syntax description mean that the sequence before the dots can be repeated if needed. Inheritable list attributes will append the new list values to the inherited list. Use can use the <a href="purge.html">purge</a> attribute to clear the list before assigning new values to the list attribute.</p>
+    <p class="manual">Some keywords take one or more arguments. These are known as list attributes. The arguments are comma separated. The three dots in the syntax description mean that the sequence before the dots can be repeated if needed. Inheritable list attributes will append the new list values to the inherited list. Use can use the <a href="purge.html">purge</a> attribute to clear the list before assigning new values to the list attribute.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">keyword arg1 [, arg2 ... ]
 </pre></div>
     <p class="manual">Variable arguments are further described in the <i>Arguments</i> section of the keyword syntax table. The name is listed immediately followed by the type of the variable argument. The supported types and their meaning is described in the following sections.</p>
@@ -46,7 +46,7 @@
     <h3 class="manual" id="INTEGER">5.1.3 INTEGER</h3>
     <p class="manual">An integer is any natural number, e. g. <code class="manual">0</code>, <code class="manual">1</code>, <code class="manual">2</code> and so on.</p>
     <h3 class="manual" id="STRING">5.1.4 STRING</h3>
-    <p class="manual">Strings are character sequences that are enclosed by special character marks. There are three different marks supported. For short strings that fit on one lines, you can either use single or double quotes.</p>
+    <p class="manual">Strings are character sequences that are enclosed by special character marks. There are three different marks supported. For short strings that fit on one line, you can either use single or double quotes.</p>
     <div class="manual" codesection="1"><pre class="manual" codesection="1">'This is a single quoted string.'
 "This is a double quoted string."
 </pre></div>
@@ -64,7 +64,7 @@
   -&gt;8-
 </pre></div>
     <h2 class="manual" id="Predefined_Macros">5.2 Predefined Macros</h2>
-    <p class="manual">TaskJuggler supports a few predefined macros. These are available after the project header. They values correspond to the values provided in the project header.</p>
+    <p class="manual">TaskJuggler supports a few predefined macros. These are available after the project header. Their values correspond to the values provided in the project header.</p>
     <ul>
      <li>
       <code class="manual">projectstart</code> The start date of the project.</li>
@@ -76,7 +76,7 @@
       <code class="manual">today</code> Identical to <code class="manual">now</code> but formatted according to the <a href="timeformat.html">timeformat</a> setting of the current context.</li>
     </ul>
     <h2 class="manual" id="Environment_Variable_Expansions">5.3 Environment Variable Expansions</h2>
-    <p class="manual">By using the $(VAR) syntax, you can insert the value of the environment variable name VAR. The name of the variable must consists only of uppercase ASCII letters, underscore or decimal digits.</p>
+    <p class="manual">By using the $(VAR) syntax, you can insert the value of the environment variable name VAR. The name of the variable must consist only of uppercase ASCII letters, underscores or decimal digits.</p>
    </div></div>
   <br/>
   <hr/>
@@ -87,6 +87,6 @@
    </tr></table>
   <hr/>
   <br/>
-  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
+  <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div>
  </body>
 </html>