[LON-CAPA-cvs] cvs: loncom /html/adm/help ext_examples.library ext_examples.problem
raeburn
raeburn at source.lon-capa.org
Wed Feb 26 10:41:39 EST 2014
raeburn Wed Feb 26 15:41:39 2014 EDT
Modified files:
/loncom/html/adm/help ext_examples.problem ext_examples.library
Log:
- Fix spelling, improve wording, ensure consistent case usage and punctuation.
- Fix typo in tag name, and add missing tags.
-------------- next part --------------
Index: loncom/html/adm/help/ext_examples.problem
diff -u loncom/html/adm/help/ext_examples.problem:1.2 loncom/html/adm/help/ext_examples.problem:1.3
--- loncom/html/adm/help/ext_examples.problem:1.2 Fri Aug 9 10:53:00 2013
+++ loncom/html/adm/help/ext_examples.problem Wed Feb 26 15:41:38 2014
@@ -3,29 +3,29 @@
<startouttext />
<hr />
Some things to do with &EXT() inside of a homework problem.<br />
-Any data that shows up in the 'all submissions with details' view in problem grades is available, as is the current value of some parameters.
+Any data that show up in the 'all submissions with details' view in problem grades are available, as are the current values of some parameters.
<table border="1">
<tr><th>Incantation</th><th>result</th><th>Explanation</th></tr>
<tr><td>user.resource.resource.<partid>.<responseid>.submission</td><td>&EXT('user.resource.resource.0.12.submission')</td>
- <td>text of the most recent submission</td></tr>
+ <td>Text of the most recent submission</td></tr>
<tr><td>user.resource.resource.<partid>.<responseid>.awarddetail</td><td>&EXT('user.resource.resource.0.12.awarddetail')</td>
- <td>Detail of how the most recent submission was graded. </td></tr>
+ <td>Details of how the most recent submission was graded</td></tr>
<tr><td>user.resource.1:resource.<partid>.<responseid>.submission</td><td>&EXT('user.resource.1:resource.0.12.submission')</td>
- <td>text of the submission on the first submission to the problem. The '1:' is not neccessarily the first try on the problem, rather it referes to the first 'transaction' in the data for this problem. Take a look at problem grades for a problem with the submissions view set to 'all submissions with details'.</td></tr>
+ <td>Text of the submission on the first submission to the problem. The '1:' is not necessarily the first try on the problem, rather it refers to the first 'transaction' in the data for this problem. Take a look at problem grades for a problem with the submissions view set to 'all submissions with details'.</td></tr>
<tr><td>user.resource.resource.<partid>.tries</td><td>&EXT('user.resource.resource.0.tries')</td>
<td>current number of tries on the problem</td></tr>
<tr><td>user.resource.resource.<partid>.solved</td><td>&EXT('user.resource.resource.0.solved')</td>
<td>current status of the problem</td></tr>
<tr><td>user.resource.resource.<partid>.awarded</td><td>&EXT('user.resource.resource.0.awarded')</td>
- <td>A floating point number between 0 and 1 inclusive, that is the percentage of the weight for this problem.</td></tr>
+ <td>A floating point number between 0 and 1 inclusive, that is the percentage of the weight for this problem.</td></tr>
<tr><td>user.resource.resource.<partid>.award</td><td>&EXT('user.resource.resource.0.award')</td>
- <td>Detailed award of the most recent part was graded. (This will be one of the <responseid>'s <tt>awarddetail</tt></td></tr>
+ <td>Detailed award determined by how the most recently graded part was graded. (This will be one of the <responseid>'s <tt>awarddetail</tt>).</td></tr>
</table>
<hr />
-You can get access to the current values of some parameters. But these only work reliably in a published problem that is in a course. <br />
+You can get access to the current values of some parameters. But these only work reliably in a published problem which is in a course. <br />
<table border="1">
-<tr><th>Incantation</th><th>result</th><th>Explanation</th></tr>
+<tr><th>Incantation</th><th>Result</th><th>Explanation</th></tr>
<tr><td>resource.<partid>.<responseid>.tolerance</td><td>&EXT('resource.0.12.tolerance')</td>
<td>Current setting of the tolerance parameter for the particular response.</td></tr>
<tr><td>resource.<partid>.maxtries</td><td>&EXT('resource.0.maxtries')</td>
Index: loncom/html/adm/help/ext_examples.library
diff -u loncom/html/adm/help/ext_examples.library:1.2 loncom/html/adm/help/ext_examples.library:1.3
--- loncom/html/adm/help/ext_examples.library:1.2 Tue Feb 28 23:03:23 2006
+++ loncom/html/adm/help/ext_examples.library Wed Feb 26 15:41:38 2014
@@ -1,14 +1,14 @@
<library>
-<startoutext />
+<startouttext />
Some things to do with &EXT()<br />
<table border="1">
-<tr><th>Incantation</th><th>result</th><th>Explanation</th></tr>
+<tr><th>Incantation</th><th>Result</th><th>Explanation</th></tr>
<tr><td>request.filename</td><td>&EXT('request.filename')</td>
<td>full internal path of the current resource</td></tr>
<tr><td>request.uri</td><td>&EXT('request.uri')</td>
- <td>Uri of the currently viewed resource</td></tr>
+ <td>URI of the currently viewed resource</td></tr>
<tr><td>request.state</td><td>&EXT('request.state')</td>
- <td>state of the resource, eith construct or publish</td></tr>
+ <td>state of the resource, either: construct or published</td></tr>
<tr><td>user.name</td><td>&EXT('user.name')</td>
<td>username of user</td></tr>
<tr><td>user.domain</td><td>&EXT('user.domain')</td>
@@ -16,37 +16,37 @@
<tr><td>user.course.sec</td><td>&EXT('user.course.sec')</td>
<td>Users's Course Section</td></tr>
<tr><td>environment.firstname</td><td>&EXT('environment.firstname')</td>
- <td>User's firstname</td></tr>
+ <td>User's first name</td></tr>
<tr><td>environment.middlename</td><td>&EXT('environment.middlename')</td>
<td>User's middle name</td></tr>
<tr><td>environment.lastname</td><td>&EXT('environment.lastname')</td>
- <td>User's lastname</td></tr>
+ <td>User's last name</td></tr>
<tr><td>environment.generation</td><td>&EXT('environment.generation')</td>
<td>Jr., Sr., III, etc.</td></tr>
<tr><td>environment.screenname</td><td>&EXT('environment.screenname')</td>
- <td>User screen name (name that appears in FDBK postings)</td></tr>
+ <td>User's screen name (name that appears in discussion postings)</td></tr>
<tr><td>environment.nickname</td><td>&EXT('environment.nickname')</td>
- <td>User nick name. (Name the user prefers to be called in person</td></tr>
+ <td>User's nickname. (Name the user prefers to be called in person)</td></tr>
<tr><td>environment.id</td><td>&EXT('environment.id')</td>
- <td>user id number</td></tr>
+ <td>User's student/employee ID number</td></tr>
<tr><td>request.browser.version</td><td>&EXT('request.browser.version')</td>
- <td>Version of the users Browser</td></tr>
+ <td>Version of the user's browser</td></tr>
<tr><td>request.browser.type</td><td>&EXT('request.browser.type')</td>
<td>What type of browser is the user using</td></tr>
<tr><td>course.description</td><td>&EXT('course.decription')</td>
- <td>Decriptive name for a course</td></tr>
+ <td>Descriptive name for a course</td></tr>
<tr><td>course.num</td><td>&EXT('course.num')</td>
<td>Internal Course Identifier</td></tr>
<tr><td>course.url</td><td>&EXT('course.url')</td>
<td>Current course toplevel map.</td></tr>
<tr><td>query.*</td><td></td>
- <td>query.* allows access to the passed in form parameters</td></tr>
+ <td>query.* allows access to ny passed-in form parameters</td></tr>
<tr><td>query.grade_target</td><td>&EXT('query.grade_target')</td>
<td>Ignore this. It isn't generally useful.</td></tr>
</table>
Other things:
<table border="1">
-<tr><th>Incantation</th><th>result</th><th>Explanation</th></tr>
+<tr><th>Incantation</th><th>Result</th><th>Explanation</th></tr>
<tr><td>$external::target</td>
<td><display>$external::target</display></td>
<td>Whether we are printing (tex) or viewing on screen (web)</td></tr>
@@ -61,21 +61,21 @@
<td>The current status of the problem
<table>
<tr><td>CLOSED</td>
- <td>either before opendate or between due and answer date</td></tr>
+ <td>either before opendate or between duedate and answerdate</td></tr>
<tr><td>CAN_ANSWER</td></tr>
<tr><td>CANNOT_ANSWER</td>
- <td>still open but either exhausted tries has the problem correct or has been excused</td></tr>
+ <td>still open but either exhausted tries, has the problem correct, or has been excused</td></tr>
<tr><td>SHOW_ANSWER </td>
<td>after answerdate</td></tr>
</table>
and some rare states that if they occur the problem isn't shown (you can safely ignore these):
<table>
<tr><td>NOT_YET_VIEWED</td>
- <td>limited view period being used and student hasn't 'checked out' the problem yet</td></tr>
+ <td>limited view period being used and student hasn't "checked out" the problem yet</td></tr>
<tr><td>INVALID_ACCESS</td>
- <td>ip restrictions in effect and user is at a banned IP </td></tr>
+ <td>IP restrictions in effect, and user's IP address is not allowed access</td></tr>
<tr><td>UNAVAILABLE</td>
- <td>network problems are occuring</td></tr>
+ <td>network problems are occurring</td></tr>
</table>
<tr><td>$external::randomseed</td>
More information about the LON-CAPA-cvs
mailing list