# HG changeset patch
# User paulb
# Date 1121433565 0
# Node ID 804198fd391785372d7eb30fdbe741ac33b826f5
# Parent  ad2f2acea58a19b6a8e5e9e974da17d7ad6347ab
[project @ 2005-07-15 13:19:25 by paulb]
Added Konqueror note.
Reformatted to 78 characters.

diff -r ad2f2acea58a -r 804198fd3917 README.txt
--- a/README.txt	Thu Jul 14 22:54:44 2005 +0000
+++ b/README.txt	Fri Jul 15 13:19:25 2005 +0000
@@ -1,36 +1,36 @@
 Warnings:
 
-  * Mozilla/Firefox will not allow the XMLHttpRequest in-page updates to
-    function unless the application URL defined within the Configurator
-    application (and other relevant applications) matches the URL at which
-    the browser finds the application.
+  * Various browsers (eg. Mozilla/Firefox, Konqueror) will not allow the
+    XMLHttpRequest in-page updates to function unless the application URL
+    defined within the Configurator application (and other relevant
+    applications) matches the URL at which the browser finds the application.
 
 --------
 
 Steps for making a new application:
 
-  1. Design a template, adding forms and fields. In the beginning, it is not
-     that important to use the correct names in each of the fields - these
-     will be added later.
+ 1. Design a template, adding forms and fields. In the beginning, it is not
+    that important to use the correct names in each of the fields - these
+    will be added later.
 
-  2. Add structural template attributes such as template:element,
-     template:attribute and template:value so that the fields sit in
-     different parts of the input document format being modelled. Replace
-     the field names with special functions such as template:field-name().
-     For buttons which add and remove parts of the input document, employ
-     selector notation and the template:this-position() function.
+ 2. Add structural template attributes such as template:element,
+    template:attribute and template:value so that the fields sit in different
+    parts of the input document format being modelled. Replace the field
+    names with special functions such as template:field-name(). For buttons
+    which add and remove parts of the input document, employ selector
+    notation and the template:this-position() function.
 
-  3. Where multiple choice fields are employed, input documents must be
-     transformed so that the multiple choice options are included in the
-     output. This can be achieved using documents containing the different
-     option values and transformations which insert those values into the
-     input document.
+ 3. Where multiple choice fields are employed, input documents must be
+    transformed so that the multiple choice options are included in the
+    output. This can be achieved using documents containing the different
+    option values and transformations which insert those values into the
+    input document.
 
-  4. To produce the output document, the template needs preparing first so
-     that an output stylesheet is produced; then, the output stylesheet is
-     applied to the processed input document utilising various extension
-     functions which produce the computed field names in the final output
-     document.
+ 4. To produce the output document, the template needs preparing first so
+    that an output stylesheet is produced; then, the output stylesheet is
+    applied to the processed input document utilising various extension
+    functions which produce the computed field names in the final output
+    document.
 
 Recommendations: