[Plone-docs] PloneBook/en ch5.rst,1.2,1.3

[<zo...@us...>]

Update of /cvsroot/plone-docs/PloneBook/en
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5676/en

Modified Files:
	ch5.rst 
Log Message:
Make the request/message example more obvious

Index: ch5.rst
===================================================================
RCS file: /cvsroot/plone-docs/PloneBook/en/ch5.rst,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** ch5.rst	8 Sep 2004 23:50:56 -0000	1.2
--- ch5.rst	29 Nov 2004 22:05:55 -0000	1.3
***************
*** 331,335 ****
  
   1+2 = *3*
!  
  To see an example of a path traversal, print the logo of your Plone site. You can include an expression in the logo of your Plone site by adding the following to your page template:
  
--- 331,335 ----
  
   1+2 = *3*
! 
  To see an example of a path traversal, print the logo of your Plone site. You can include an expression in the logo of your Plone site by adding the following to your page template:
  
***************
*** 487,491 ****
   </p>
  
! Here, the paragraph with the text for a message will be rendered only if the *request* variable has an attribute and it resolves to *true*. Being able to test for a condition is pointless if the opposite condition can't be tested for; this is what the not expression allows. The *not:* prefix inverts the statement, so *not: request/message* resolves to *true* if the request variable message resolves to *false*.
  
  In TAL, the following evaluates to *false*:
--- 487,491 ----
   </p>
  
! Here, the paragraph with the text for a message will be rendered only if the *request* variable has an attribute and it resolves to *true* (ie: the length of message is greater than zero). Being able to test for a condition is pointless if the opposite condition can't be tested for; this is what the not expression allows. The *not:* prefix inverts the statement, so *not: request/message* resolves to *true* if the request variable message resolves to *false* (ie: the length of message is zero). In this case the *request* variable, *message* will still need to exist.
  
  In TAL, the following evaluates to *false*: