2a3,5
> <title>
> 2.4.1.  Scheduling an Individual Meeting
> </title>
4a8,22
> <a name="Scheduling an Individual Meeting">
> <h4>
> 2.4.1.  Scheduling an Individual Meeting
> </h4>
> </a>
> <p>
> The scenario in this section illustrates an individual user scheduling a
> meeting with a few other users.  More advanced forms of group scheduling are
> covered in
> <a href="group-meeting-scheduling.html">
> Section 2.5.
> </a>
> </p><p>
> When the user selects <tt>Meeting</tt> in the <tt>Schedule</tt> menu, the
> system displays the dialog shown in Figure 29.
5a24,35
> <br>
> <br>
> <hr>
> <a name="Figure Meeting scheduling dialog">
> <p align=center>
> <img src="images/meeting-dialog.gif">
> </p>
> <p align=center> Figure 29:  Meeting scheduling dialog.  </p>
> <hr>
> </a>
> <br>
> <br>
6a37,70
> </p><p>
> <em>Sketch of the remainder:
> <ul>
> <li>
> The user selects possible dates, start times, recurring, location, and
> attendees.
> <li>
> The other fields need not be filled in yet.
> <li>
> When user presses 'OK', system responds with summary list of possible dates and
> times.
> <li>
> The user responds with a selection from the list.
> <li>
> The system then displays the confirmed meeting, as shown in Figure 30
> 
> <br>
> <br>
> <hr>
> <a name="Figure Meeting scheduling dialog">
> <p align=center>
> <img src="images/meeting-confirmation.gif">
> </p>
> <p align=center> Figure 30:  Meeting scheduling dialog.  </p>
> <hr>
> </a>
> <br>
> <br>
> 
> <li>
> If some fields yet need to be filled, the user does so and presses 'OK'.</em>
> </ul>
> 
>