[Checkins] SVN: grok/trunk/doc/reference/ Fix reSTy markup

Philipp von Weitershausen philikon at philikon.de
Thu Jan 18 13:30:36 EST 2007


Log message for revision 72097:
  Fix reSTy markup
  

Changed:
  U   grok/trunk/doc/reference/core.tex
  U   grok/trunk/doc/reference/directives.tex

-=-
Modified: grok/trunk/doc/reference/core.tex
===================================================================
--- grok/trunk/doc/reference/core.tex	2007-01-18 18:08:56 UTC (rev 72096)
+++ grok/trunk/doc/reference/core.tex	2007-01-18 18:30:35 UTC (rev 72097)
@@ -21,9 +21,10 @@
         \item Scan the module for known components: models, adapters,
               utilities, views, traversers, templates and subscribers.
 
-        \item Check whether a directory with file system templates exists
-        (``<modulename>_templates''). If it exists, load the file system
-        templates into the template registry for this module.
+        \item Check whether a directory with file system templates
+              exists (\file{<modulename>_templates}).  If it exists,
+              load the file system templates into the template
+              registry for this module.
 
         \item Determine the module context. 
 
@@ -38,8 +39,8 @@
     \begin{enumerate}
         \item Grok the package as a module.
 
-        \item Check for a static resource directory (``static'') and register
-              it if it exists.
+        \item Check for a static resource directory (\file{static})
+          and register it if it exists.
 
         \item Recursively grok all sub-modules and sub-packages.
 

Modified: grok/trunk/doc/reference/directives.tex
===================================================================
--- grok/trunk/doc/reference/directives.tex	2007-01-18 18:08:56 UTC (rev 72096)
+++ grok/trunk/doc/reference/directives.tex	2007-01-18 18:30:35 UTC (rev 72097)
@@ -31,9 +31,9 @@
 XXX insert directive description here (first: define the name, second: describe
 the default behaviour if the directive isn't given)
 
-A resource directory is created when a package contains a directory with the
-name ``\file{static}''.  All files from this directory become accessible from a
-browser under the URL
+A resource directory is created when a package contains a directory
+with the name \file{static}.  All files from this directory become
+accessible from a browser under the URL
 \file{http://<servername>/++resource++<packagename>/<filename>}.
 
 \begin{bf}Example:\end{bf} The package \module{a.b.c} is grokked and contains a
@@ -41,9 +41,10 @@
 stylesheet will be available via
 \file{http://<servername>/++resource++a.b.c/example.css}.
 
-\begin{notice}A package can never have both a ``static'' directory and a Python module
-with the name ``static.py'' at the same time. grok will remind you of this
-conflict when grokking a package by displaying an error message.
+\begin{notice}A package can never have both a \file{static} directory
+  and a Python module with the name \file{static.py} at the same
+  time. grok will remind you of this conflict when grokking a package
+  by displaying an error message.
 
 \end{notice}
 



More information about the Checkins mailing list