I don't think putting <literal> inside a <link> is very good, please choose one or the other.
Regards, Philip On Sat, 1 Feb 2003, Martin Samesch wrote: > samesch Sat Feb 1 12:33:04 2003 EDT > > Modified files: > /phpdoc/en/reference/session reference.xml > Log: > added tags > > Index: phpdoc/en/reference/session/reference.xml > diff -u phpdoc/en/reference/session/reference.xml:1.29 >phpdoc/en/reference/session/reference.xml:1.30 > --- phpdoc/en/reference/session/reference.xml:1.29 Sun Jan 26 10:19:02 2003 > +++ phpdoc/en/reference/session/reference.xml Sat Feb 1 12:33:04 2003 > @@ -1,5 +1,5 @@ > <?xml version="1.0" encoding="iso-8859-1"?> > -<!-- $Revision: 1.29 $ --> > +<!-- $Revision: 1.30 $ --> > <reference id="ref.session"> > <title>Session handling functions</title> > <titleabbrev>Sessions</titleabbrev> > @@ -72,8 +72,9 @@ > addditional protections -- this usually comes at a price, reduced > convenience for the user. For example, if you want to protect users from > simple social engineering tactics, you need to enable > - session.use_only_cookies. In that case, cookies must be enabled > - unconditionally on the user side, or sessions will not work. > + <literal>session.use_only_cookies</literal>. In that case, > + cookies must be enabled unconditionally on the user side, or > + sessions will not work. > </para> > <para> > There are several ways to leak an existing session id to third parties. > @@ -162,7 +163,7 @@ > are accessible like any other variables. > <example> > <title> > - Registering a variable with $_SESSION. > + Registering a variable with <varname>$_SESSION</varname>. > </title> > <programlisting role="php"> > <