length.html in taskjuggler-3.7.1

- old
+ new

@@ -1,7 +1,7 @@
 <!DOCTYPE html>
-<!-- This file has been generated by tj3man v3.6.0 -->
+<!-- This file has been generated by tj3man v3.7.1 -->
 <html lang="en" xml:lang="en">
  <head>
   <title>length</title>
   <meta content="text/html; charset=utf-8" http-equiv="Content-Type"/>
   <meta content="IE=9" http-equiv="X-UA-Compatible"/>
@@ -39,11 +39,11 @@
      <tr align="left">
       <td class="tag">Purpose</td>
       <td class="descr" colspan="2"><div>
         <p>Specifies the duration of this task as working time, not calendar time. 7d means 7 working days, or 7 times 8 hours (assuming default settings), not one week.</p>
         <p>A task with a length specification may have resource allocations. Resources are allocated when they are available. There is no guarantee that the task will get any resources allocated. The availability of resources has no impact on the duration of the task. A time slot where none of the specified resources is available is still considered working time, if there is no global vacation and global working hours are defined accordingly.</p>
-        <p>For the length calculation, the global working hours and the global leaves matter unless the task has <a href="shifts.task.html">shifts</a> assigned. In the latter case the working hours and leaves of the shift apply for the specified period to determine if a slot is working time or not. If a resource has additinal working hours defined, it's quite possible that a task with a length of 5d will have an allocated effort larger than 40 hours. Resource working hours only have an impact on whether an allocation is made or not for a particular time slot. They don't effect the resulting duration of the task.</p>
+        <p>For the length calculation, the global working hours and the global leaves matter unless the task has <a href="shifts.task.html">shifts</a> assigned. In the latter case the working hours and leaves of the shift apply for the specified period to determine if a slot is working time or not. If a resource has additional working hours defined, it's quite possible that a task with a length of 5d will have an allocated effort larger than 40 hours. Resource working hours only have an impact on whether an allocation is made or not for a particular time slot. They don't effect the resulting duration of the task.</p>
         <p>Tasks may not have subtasks if this attribute is used. Setting this attribute will reset the <a href="duration.html">duration</a>, <a href="effort.html">effort</a> and <a href="milestone.html">milestone</a> attributes.</p>
        </div></td>
      </tr>
      <tr align="left">
       <td class="tag">Syntax</td>
@@ -99,8 +99,8 @@
     <td style="text-align:center; width:30%;"><a href="toc.html">Table Of Contents</a></td>
     <td style="text-align:right; width:35%;">&gt;&gt; <a href="limits.html">limits</a> &gt;&gt;</td>
    </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>