taskjuggler 0.0.10 → 0.0.11

data/lib/{TjpSyntaxRules.rb → taskjuggler/TjpSyntaxRules.rb}

@@ -18,6 +18,16 @@ class TaskJuggler
 # necessary but make the file more readable and receptable to syntax folding.
 module TjpSyntaxRules
 
+  def rule_absoluteTaskId
+    pattern(%w( !taskIdUnverifd ), lambda {
+      id = (@taskprefix.empty? ? '' : @taskprefix + '.') + @val[0]
+      if (task = @project.task(id)).nil?
+        error('unknown_abs_task', "Unknown task #{id}", @sourceFileInfo[0])
+      end
+      task
+    })
+  end
+
   def rule_account
     pattern(%w( !accountHeader !accountBody ), lambda {
        @property = @property.parent
@@ -856,7 +866,19 @@ EOT
 
   def rule_exportHeader
     pattern(%w( _export !optionalID $STRING ), lambda {
-      newReport(@val[1], @val[2], :export, sourceFileInfo)
+      report = newReport(@val[1], @val[2], :export, sourceFileInfo)
+
+      # By default, we export all scenarios.
+      scenarios = Array.new(@project.scenarios.items) { |i| i }
+      scenarios.delete_if { |sc| !@project.scenario(sc).get('enabled') }
+      report.set('scenarios', scenarios)
+      # Show all tasks, sorted by seqno-up.
+      report.set('hideTask', LogicalExpression.new(LogicalOperation.new(0)))
+      report.set('sortTasks', [ [ 'seqno', true, -1 ] ])
+      # Show all resources, sorted by seqno-up.
+      report.set('hideResource',
+                  LogicalExpression.new(LogicalOperation.new(0)))
+      report.set('sortResources', [ [ 'seqno', true, -1 ] ])
     })
     arg(1, 'file name', <<'EOT'
 The name of the report file to generate. It must end with a .tjp or .tji
@@ -903,6 +925,18 @@ EOT
                          { 'vacation' => 'Include vacations',
                            'workinghours' => 'Include working hours' })
 
+    pattern(%w( _scenarios !scenarioIdList ), lambda {
+      # Don't include disabled scenarios in the report
+      @val[1].delete_if { |sc| !@project.scenario(sc).get('enabled') }
+      @property.set('scenarios', @val[1])
+    })
+    doc('scenarios.export', <<'EOT'
+List of scenarios that should be included in the report. By default, all
+scenarios will be included. This attribute can be used to limit the included
+scenarios to a defined list.
+EOT
+       )
+
     pattern(%w( _taskattributes !exportableTaskAttributes ), lambda {
       @property.set('taskAttributes', @val[1])
     })
@@ -922,6 +956,12 @@ EOT
                            'note' => 'Include notes',
                            'priority' => 'Include priorities',
                            'responsible' => 'Include responsible resource' })
+
+    pattern(%w( _timezone !validTimeZone ), lambda {
+      @property.set('timezone', @val[1])
+    })
+    doc('timezone.export',
+        "Set the time zone to be used for all dates in the report.")
   end
 
   def rule_exportBody
@@ -970,6 +1010,29 @@ EOT
     doc('reference.extend', <<'EOT'
 Extend the property with a new attribute of type reference. A reference is a
 URL and an optional text that will be shown instead of the URL if needed.
+EOT
+       )
+    arg(2, 'name', 'The name of the new attribute. It is used as header ' +
+                   'in report columns and the like.')
+
+    pattern(%w( _richtext !extendId $STRING !extendOptionsBody ), lambda {
+      # Extend the propertySet definition and parser rules
+      if extendPropertySetDefinition(RichTextAttribute, nil)
+        @ruleToExtendWithScenario.addPattern(TextParser::Pattern.new(
+          [ '_' + @val[1], '$STRING' ], lambda {
+            @property[@val[0], @scenarioIdx] =
+              newRichText(@val[1], @sourceFileInfo[1])
+          }))
+      else
+        @ruleToExtend.addPattern(TextParser::Pattern.new(
+          [ '_' + @val[1], '$STRING' ], lambda {
+            @property.set(@val[0], newRichText(@val[1], @sourceFileInfo[1]))
+          }))
+      end
+    })
+    doc('richtext.extend', <<'EOT'
+Extend the property with a new attribute of type [[Rich_Text_Attributes|Rich
+Text]].
 EOT
        )
     arg(2, 'name', 'The name of the new attribute. It is used as header ' +
@@ -1090,8 +1153,11 @@ EOT
     pattern(%w( _flags !flagList ), lambda {
       @val[1].each do |flag|
         unless @property['flags', @scenarioIdx].include?(flag)
-          @property['flags', @scenarioIdx] =
-            @property['flags', @scenarioIdx] + @val[1]
+          # We allow multiple instances of flag definitions.
+          begin
+            @property['flags', @scenarioIdx] += @val[1]
+          rescue AttributeOverwrite
+          end
         end
       end
     })
@@ -1305,7 +1371,7 @@ EOT
     optional
     repeatable
 
-    pattern(%w( _accountprefix !taskId ), lambda {
+    pattern(%w( _accountprefix !accountId ), lambda {
       @accountprefix = @val[1].fullId
     })
     doc('accountprefix', <<'EOT'
@@ -1316,7 +1382,7 @@ EOT
     )
     arg(1, 'account ID', 'The absolute ID of an already defined account')
 
-    pattern(%w( _reportprefix !taskId ), lambda {
+    pattern(%w( _reportprefix !reportId ), lambda {
       @reportprefix = @val[1].fullId
     })
     doc('reportprefix', <<'EOT'
@@ -1828,7 +1894,8 @@ EOT
       if @scanner.macroDefined?(@val[1])
         warning('marco_redefinition', "Redefining macro #{@val[1]}")
       end
-      @scanner.addMacro(Macro.new(@val[1], @val[2], @sourceFileInfo[0]))
+      @scanner.addMacro(TextParser::Macro.new(@val[1], @val[2],
+                                              @sourceFileInfo[0]))
     })
     doc('macro', <<'EOT'
 Defines a text fragment that can later be inserted by using the specified ID.
@@ -2335,10 +2402,10 @@ EOT
 
     pattern(%w( _now !date ), lambda {
       @project['now'] = @val[1]
-      @scanner.addMacro(Macro.new('now', @val[1].to_s,
-                                  @sourceFileInfo[0]))
-      @scanner.addMacro(Macro.new('today', @val[1].to_s(@project['timeFormat']),
-                                  @sourceFileInfo[0]))
+      @scanner.addMacro(TextParser::Macro.new('now', @val[1].to_s,
+                                              @sourceFileInfo[0]))
+      @scanner.addMacro(TextParser::Macro.new(
+        'today', @val[1].to_s(@project['timeFormat']), @sourceFileInfo[0]))
     })
     doc('now', <<'EOT'
 Specify the date that TaskJuggler uses for calculation as current
@@ -2376,7 +2443,7 @@ EOT
     })
 
     pattern(%w( !timezone ), lambda {
-      @project['timezone'] = @val[1]
+      @val[0]
     })
 
     pattern(%w( _timingresolution $INTEGER _min ), lambda {
@@ -2453,6 +2520,8 @@ EOT
 The project property is mandatory and should be the first property
 in a project file. It is used to capture basic attributes such as
 the project id, name and the expected time frame.
+
+Be aware that the dates for the project period default to UTC times. See [[interval2]] for details.
 EOT
        )
   end
@@ -2724,7 +2793,7 @@ EOT
       if attributeDefinition.scenarioSpecific
         attr = @property[@val[1], 0]
       else
-        attr = @propert.get(@val[1])
+        attr = @property.get(@val[1])
       end
       unless attr.is_a?(Array)
         error('purge_no_list',
@@ -2966,6 +3035,26 @@ EOT
     singlePattern('_index')
     descr('The index of the item based on the nesting hierachy')
 
+    singlePattern('_inputs')
+    descr(<<'EOT'
+A list of milestones that are a prerequiste for the current task. For
+container tasks it will also include the inputs of the child tasks. Inputs may
+not have any predecessors.
+
+The list can be customized by the [listmode.column listmode] attribute. The
+following modes are supported:
+
+# ID
+# Name
+# Name (ID)
+# ID: Name
+# ID (Date)
+# Name (Date)
+# Name (ID) Date ''(This is the default)''
+# ID: Name Date
+EOT
+         )
+
     singlePattern('_journal')
     descr(<<'EOT'
 The journal entries for the task or resource for the reported interval.
@@ -3144,7 +3233,8 @@ EOT
     singlePattern('_targets')
     descr(<<'EOT'
 A list of milestones that depend on the current task. For container tasks it
-will also include the targets of the child tasks.
+will also include the targets of the child tasks. Targets may not have any
+follower tasks.
 
 The list can be customized by the [listmode.column listmode] attribute. The
 following modes are supported:
@@ -3154,8 +3244,8 @@ following modes are supported:
 # Name (ID)
 # ID: Name
 # ID (Date)
-# Name (Date) ''(This is the default)''
-# Name (ID) Date
+# Name (Date)
+# Name (ID) Date ''(This is the default)''
 # ID: Name Date
 EOT
          )
@@ -3331,7 +3421,11 @@ EOT
       @property.set('scenarios', @val[1])
     })
     doc('scenarios', <<'EOT'
-List of scenarios that should be included in the report.
+List of scenarios that should be included in the report. By default, only the
+top-level scenario will be included. You can use this attribute to include
+data from the defined set of scenarios. Not all reports support reporting data
+from multiple scenarios. They will only include data from the first one in the
+list.
 EOT
        )
 
@@ -3378,6 +3472,17 @@ EOT
       @property.set('timeFormat', @val[0])
     })
 
+    pattern(%w( _timezone !validTimeZone ), lambda {
+      @property.set('timezone', @val[1])
+    })
+    doc('timezone.report', <<'EOT'
+Sets the time zone used for all dates in the report. This setting is ignored
+if the report is embedded into another report. Embedded in this context means
+the report is part of another generated report. It does not mean that the
+report definition is a sub report of another report definition.
+EOT
+       )
+
     pattern(%w( !reportTitle ))
   end
 
@@ -3731,15 +3836,15 @@ EOT
        )
 
     pattern(%w( _booking !resourceBooking ))
-    doc('booking', <<'EOT'
+    doc('booking.resource', <<'EOT'
 The booking attribute can be used to report completed work. This can be part
 of the necessary effort or the whole effort. When the scenario is scheduled in
 [[projection]] mode, TaskJuggler assumes that only the work reported with
 bookings has been done up to now. It then schedules a plan for the still
 missing effort. All task with bookings must be scheduled in ''''asap'''' mode.
 
-This attribute is also used within export reports to describe the details of a
-scheduled project.
+Bookings are only valid in the scenario they have been defined in. They will
+not be passed to any other scenario.
 
 The sloppy attribute can be used when you want to skip non-working time or
 other allocations automatically. If it's not given, all bookings must only
@@ -3750,9 +3855,14 @@ work. This attribute is not really intended to specify completed effort by
 hand. Usually, booking statements are generated by [[export]] reports. The
 [[sloppy.booking|sloppy]] and [[overtime.booking|overtime]] attributes are
 only kludge for users who want to write them manually.
+Bookings can be used to report already completed work by specifying the exact
+time intervals a certain resource has worked on this task.
+
+Bookings can be defined in the task or resource context. If you move tasks
+around very often, put your bookings in the task context.
 EOT
        )
-    also(%w( scheduling ))
+    also(%w( scheduling booking.task ))
     example('Booking')
 
     pattern(%w( !fail ))
@@ -3852,7 +3962,7 @@ By default, the scheduler assigns resources to task beginning with the project
 start date. If the scenario is switched to projection mode, no assignments
 will be made prior to the current date or the date specified by [[now]]. In
 this case, TaskJuggler assumes, that all assignements prior to the
-current date have been provided by [[booking]] statements.
+current date have been provided by [[booking.task]] statements.
 EOT
        )
   end
@@ -4487,6 +4597,25 @@ EOT
     repeatable
     optional
 
+    pattern(%w( _adopt !taskList ), lambda {
+      @val[1].each do |task|
+        @property.adopt(task)
+      end
+    })
+    doc('adopt.task', <<'EOT'
+Add a previously defined task to the sub-tasks of this task. This can be used
+to create virtual sub projects that contain of task trees that were defined as
+sub tasks of other tasks. Adopted tasks don't inherit anything from their step
+parents. However, the adopting task is scheduled to fit all adopted childs as
+well.
+
+The adopting task and the adopted task must not share a common top-level task.
+Adopted tasks may not have overlaping sub trees.
+
+'''This feature is experimental right now. Don't use it!'''.
+EOT
+       )
+
     pattern(%w( !journalEntry ))
 
     pattern(%w( _note $STRING ), lambda {
@@ -4686,6 +4815,10 @@ EOT
     singlePattern('$ID')
   end
 
+  def rule_taskList
+    listRule('moreTasks', '!absoluteTaskId')
+  end
+
   def rule_taskPeriod
     pattern(%w( _period !valInterval), lambda {
       @property['start', @scenarioIdx] = @val[1].start
@@ -4730,10 +4863,33 @@ EOT
 
     pattern(%w( _booking !taskBooking ))
     doc('booking.task', <<'EOT'
+The booking attribute can be used to report completed work. This can be part
+of the necessary effort or the whole effort. When the scenario is scheduled in
+[[projection]] mode, TaskJuggler assumes that only the work reported with
+bookings has been done up to now. It then schedules a plan for the still
+missing effort. All task with bookings must be scheduled in ''''asap'''' mode.
+
+Bookings are only valid in the scenario they have been defined in. They will
+not be passed to any other scenario.
+
+The sloppy attribute can be used when you want to skip non-working time or
+other allocations automatically. If it's not given, all bookings must only
+cover working time for the resource.
+
+The booking attributes is designed to capture the exact amount of completed
+work. This attribute is not really intended to specify completed effort by
+hand. Usually, booking statements are generated by [[export]] reports. The
+[[sloppy.booking|sloppy]] and [[overtime.booking|overtime]] attributes are
+only kludge for users who want to write them manually.
 Bookings can be used to report already completed work by specifying the exact
 time intervals a certain resource has worked on this task.
+
+Bookings can be defined in the task or resource context. If you move tasks
+around very often, put your bookings in the task context.
 EOT
        )
+    also(%w( booking.resource ))
+    example('Booking')
 
     pattern(%w( _charge !number !chargeMode ), lambda {
       checkContainer('charge')
@@ -4760,9 +4916,12 @@ EOT
         mode = :perDiem
         amount = @val[1] / 7.0
       end
-      @property['charge', @scenarioIdx] =
-        @property['charge', @scenarioIdx] +
-        [ Charge.new(amount, mode, @property, @scenarioIdx) ]
+      # Multiple 'charge' attributes are allowed.
+      begin
+        @property['charge', @scenarioIdx] +=
+          [ Charge.new(amount, mode, @property, @scenarioIdx) ]
+      rescue AttributeOverwrite
+      end
     })
     doc('charge', <<'EOT'
 Specify a one-time or per-period charge to a certain account. The charge can
@@ -4796,9 +4955,9 @@ EOT
 
     pattern(%w( _depends !taskDepList ), lambda {
       checkContainer('depends')
-      @property['depends', @scenarioIdx] =
-        @property['depends', @scenarioIdx] + @val[1]
       begin
+        @property['depends', @scenarioIdx] =
+          @property['depends', @scenarioIdx] + @val[1]
         @property['forward', @scenarioIdx] = true
       rescue AttributeOverwrite
       end
@@ -4813,10 +4972,7 @@ EOT
         )
     example('Depends1')
     pattern(%w( _duration !calendarDuration ), lambda {
-      checkContainer('duration')
-      @property['duration', @scenarioIdx] = @val[1]
-      @property['effort', @scenarioIdx] = 0
-      @property['length', @scenarioIdx] = 0
+      setDurationAttribute('duration', @val[1])
     })
     doc('duration', <<'EOT'
 Specifies the time the task should last. This is calendar time, not working
@@ -4832,14 +4988,11 @@ EOT
     also(%w( effort length ))
 
     pattern(%w( _effort !workingDuration ), lambda {
-      checkContainer('effort')
       if @val[1] <= 0.0
         error('effort_zero', "Effort value must be larger than 0",
               @sourceFileInfo[1], @property)
       end
-      @property['effort', @scenarioIdx] = @val[1]
-      @property['duration', @scenarioIdx] = 0
-      @property['length', @scenarioIdx] = 0
+      setDurationAttribute('effort', @val[1])
     })
     doc('effort', <<'EOT'
 Specifies the effort needed to complete the task. An effort of 4d can be done
@@ -4867,13 +5020,14 @@ EOT
       end
     })
     doc('end', <<'EOT'
-The end date of the task. When specified for the top-level (default) scenario
-this attributes also implicitly sets the scheduling policy of the tasks to
-alap.
+The end attribute provides a guideline to the scheduler when the task should
+end. It will never end later, but it may end earlier when allocated
+resources are not available that long. When an end date is provided for a
+container task, it will be passed down to ALAP task that don't have a well
+defined end criteria.
 
-If no end date is given for a task and the end is not specified by a
-dependency on another task, or by a start date plus a duration, the end date
-will be inherited from the enclosing tasks or the project end date.
+Setting an end date will implicitely set the scheduling policy for this task
+to ALAP.
 EOT
        )
     example('Export', '1')
@@ -4899,23 +5053,29 @@ EOT
     pattern(%w( !fail ))
 
     pattern(%w( _length !workingDuration ), lambda {
-      checkContainer('length')
-      @property['length', @scenarioIdx] = @val[1]
-      @property['duration', @scenarioIdx] = 0
-      @property['effort', @scenarioIdx] = 0
+      setDurationAttribute('length', @val[1])
     })
     doc('length', <<'EOT'
-Specifies the time the task occupies the resources. This is working time, not
-calendar time. 7d means 7 working days, not one week. Whether a day is
-considered a working day or not depends on the defined working hours and
-global vacations. A task with a length specification may have resource
-allocations. Resources are allocated when they are available. The availability
-has no impact on the duration of the task. A day where none of the specified
-resources is available is still considered a working day, if there is no
-global vacation or global working time defined.
+Specifies the global working time to be used for this task. The value is
+specified in working time, not calendar time. 7d means 7 working days, or 7
+times 8 hours (assuming default settings), not one week.
+
+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.
+
+For the length calculation, only the global working hours and the global
+vacations matter. 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.
 
 Tasks may not have subtasks if this attribute is used. Setting this attribute
-will reset the [[duration]] and [[effort]] attributes.
+will reset the [[duration]], [[effort]] and [[milestone]] attributes.
 EOT
        )
     also(%w( duration effort ))
@@ -4952,8 +5112,7 @@ EOT
        )
 
     pattern(%w( _milestone ), lambda {
-      checkContainer('limits')
-      @property['milestone', @scenarioIdx] = true
+      setDurationAttribute('milestone')
     })
     doc('milestone', <<'EOT'
 Turns the task into a special task that has no duration. You may not specify a
@@ -5002,9 +5161,9 @@ EOT
 
     pattern(%w( _precedes !taskPredList ), lambda {
       checkContainer('precedes')
-      @property['precedes', @scenarioIdx] =
-        @property['precedes', @scenarioIdx] + @val[1]
       begin
+        @property['precedes', @scenarioIdx] =
+          @property['precedes', @scenarioIdx] + @val[1]
         @property['forward', @scenarioIdx] = false
       rescue AttributeOverwrite
       end
@@ -5172,13 +5331,14 @@ EOT
       end
     })
     doc('start', <<'EOT'
-The start date of the task. When specified for the top-level (default)
-scenario this attribute also implicitly sets the scheduling policy of the task
-to asap.
+The start attribute provides a guideline to the scheduler when the task should
+start. It will never start earlier, but it may start later when allocated
+resources are not available immediately. When a start date is provided for a
+container task, it will be passed down to ASAP task that don't have a well
+defined start criteria.
 
-If no start date is given for a task and the start is not specified by a
-dependency on another task, or by an end date plus a duration, the start date
-will be inherited from the enclosing tasks or the project start date.
+Setting a start date will implicitely set the scheduling policy for this task
+to ASAP.
 EOT
        )
     also(%w( end period.task maxstart minstart scheduling ))
@@ -5361,15 +5521,15 @@ The intended use for time sheets is to have all resources report a time sheet
 every day, week or month. All time sheets can be added to the project plan.
 The status information is always used to determin the current status of the
 project. The [[work]], [[remaining]] and [[end.timesheet|end]] attributes are
-ignored if there are also [[booking|bookings]] for the resource in the time
-sheet period. The non-ignored attributes of the time sheets
-will be converted into [[booking]] statements internally. These bookings can
-then be [[export|exported]] into a file which can then be added to the project
-again. This way, you can use time sheets to incrementally record progress of
-your project. There is a possibility that time sheets conflict with other data
-in the plan. In case TaskJuggler cannot automatically resolve them, these
-conflicts have to be manually resolved by either changing the plan or the time
-sheet.
+ignored if there are also [[booking.task|bookings]] for the resource in the
+time sheet period. The non-ignored attributes of the time sheets will be
+converted into [[booking.task|booking]] statements internally. These bookings
+can then be [[export|exported]] into a file which can then be added to the
+project again. This way, you can use time sheets to incrementally record
+progress of your project. There is a possibility that time sheets conflict
+with other data in the plan. In case TaskJuggler cannot automatically resolve
+them, these conflicts have to be manually resolved by either changing the plan
+or the time sheet.
 
 The status messages are interpreted as [[journalentry|journal entries]]. The
 alert level will be evaluated and the current state of the project can be put
@@ -5474,19 +5634,16 @@ EOT
 
   def rule_timezone
     pattern(%w( _timezone !validTimeZone ), lambda{
-      ENV['TZ'] = @project['timezone'] = @val[1]
+      TjTime.setTimeZone(@val[1])
+      @project['timezone'] = @val[1]
     })
     doc('timezone', <<'EOT'
-Sets the default time zone of the project. All times that have no time
-zones specified will be assumed to be in this time zone. The value must be a
-string just like those used for the TZ environment variable. Most
-Linux systems have a command line utility called tzselect to lookup
-possible values.
+Sets the default time zone of the project. All dates and times that have no
+time zones specified will be assumed to be in this time zone. If no time zone
+is specified for the project, UTC is assumed.
 
-The project start and end time are not affected by this setting. You
-have to explicitly state the time zone for those dates or the system defaults
-are assumed. Using the TZ environment variable is the recommended way to
-specify the time zone for your project.
+The project start and end time are not affected by this setting. They are
+always considered to be UTC unless specified differently.
 
 In case the specified time zone is not hour-aligned with UTC, the
 [[timingresolution]] will automatically be decreased accordingly. Do not
@@ -5629,10 +5786,10 @@ EOT
     })
     doc('priority.timesheet', <<'EOT'
 The priority is a value between 1 and 1000. It is used to determine the
-sequence of task when converting [[work]] to [[booking|bookings]]. Tasks that
-need to finish earlier in the period should have a high priority, tasks that
-end later in the period should have a low priority. For tasks that don't get
-finished in the reported period the priority should be set to 1.
+sequence of task when converting [[work]] to [[booking.task|bookings]]. Tasks
+that need to finish earlier in the period should have a high priority, tasks
+that end later in the period should have a low priority. For tasks that don't
+get finished in the reported period the priority should be set to 1.
 EOT
        )
 
@@ -5641,8 +5798,8 @@ EOT
     })
     doc('remaining', <<'EOT'
 The remaining effort for the task. This value is ignored if there are
-[[booking|bookings]] for the resource that overlap with the time sheet period.
-If there are no bookings, the value is compared with the [[effort]]
+[[booking.task|bookings]] for the resource that overlap with the time sheet
+period.  If there are no bookings, the value is compared with the [[effort]]
 specification of the task. If there a mismatch between the accumulated effort
 specified with bookings, [[work]] and [[remaining]] on one side and the
 specified [[effort]] on the other, a warning is generated.
@@ -5660,10 +5817,11 @@ EOT
     })
     doc('work', <<'EOT'
 The amount of time that the resource has spend with the task during the
-reported period. This value is ignored when there are [[booking|bookings]] for
-the resource overlapping with the time sheet period. If there are no bookings,
-TaskJuggler will try to convert the work specification into bookings
-internally before the actual scheduling is started.
+reported period. This value is ignored when there are
+[[booking.task|bookings]] for the resource overlapping with the time sheet
+period. If there are no bookings, TaskJuggler will try to convert the work
+specification into bookings internally before the actual scheduling is
+started.
 
 Every task listed in the time sheet needs to have a work attribute. The total
 accumulated work time that is reported must match exactly the total working
@@ -5705,7 +5863,8 @@ EOT
   def rule_valDate
     pattern(%w( !date ), lambda {
       if @val[0] < @project['start'] || @val[0] > @project['end']
-        error('date_in_range', "Date must be within the project time frame " +
+        error('date_in_range',
+              "Date #{@val[0]} must be within the project time frame " +
               "#{@project['start']}  - #{@project['end']}",
               @sourceFileInfo[0])
       end
@@ -5908,8 +6067,7 @@ EOT
           @property['workinghours', @scenarioIdx] = wh
         end
       end
-      wh.timezone = @property.nil? ? @project['timezone'] :
-                    @property['timezone', @scenarioIdx]
+      wh.timezone = @project['timezone']
       7.times { |i| wh.setWorkingHours(i, @val[2]) if @val[1][i] }
     })
   end