Changes between Version 1 and Version 2 of XmlFormat

Timestamp:

May 21, 2007, 3:07:49 PM (18 years ago)

Author:

Nicolas

Comment:

A few formatting tweaks (added monospacing)

XmlFormat

@@ -92 +92 @@
 fopen(physical_name, "r")
 }}}
-        In this example, open_name is 'input'. It is mapped, at runtime, to a path that includes the filename ('foobar' in the example above).
+        In this example, `open_name` is 'input'. It is mapped, at runtime, to a path that includes the filename ('foobar' in the example above).
  main_program::
         Relevant only for files associated with application versions. It indicates that this file is the application's main program.
  copy_file::
-        Use this if your application doesn't use boinc_resolve_filename() to make logical to physical filenames (for example, executables without source code). If present on an input file, BOINC will copy the file to the slot directory before starting the application. If present on an output file, BOINC will move the file from the slot directory to the project directory after the application has finished.
+        Use this if your application doesn't use `boinc_resolve_filename()` to make logical to physical filenames (for example, executables without source code). If present on an input file, BOINC will copy the file to the slot directory before starting the application. If present on an output file, BOINC will move the file from the slot directory to the project directory after the application has finished.
  optional::
         Use this for output files that may not be created by the application. Otherwise, missing output files are treated as an error.
@@ -102 +102 @@
 
 == App versions ==
-Each entry in the app version table includes an XML document describing the files that make up the application version:
+Each entry in the `app_version` table includes an XML document describing the files that make up the application version:
 {{{
 <file_info>