cvs: smarty /docs/en/designers/language-builtin-functions language-function-config-load.xml

"Mehdi Achour" <[email protected]>
Newsgroups gmane.comp.php.cvs.smarty
Message-ID <cvsdidou1082308707@cvsserver>
didou		Sun Apr 18 13:18:27 2004 EDT

  Modified files:              
    /smarty/docs/en/designers/language-builtin-functions	
                                                        	language-function-config-load.xml 
  Log:
  WS

-- 
Smarty CVS Mailing List (http://cvs.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
didou-20040418131827.txt (text/plain, 8 KB)
http://cvs.php.net/diff.php/smarty/docs/en/designers/language-builtin-functions/language-function-config-load.xml?r1=1.2&r2=1.3&ty=u
Index: smarty/docs/en/designers/language-builtin-functions/language-function-config-load.xml
diff -u smarty/docs/en/designers/language-builtin-functions/language-function-config-load.xml:1.2 smarty/docs/en/designers/language-builtin-functions/language-function-config-load.xml:1.3
--- smarty/docs/en/designers/language-builtin-functions/language-function-config-load.xml:1.2	Wed Apr 14 11:53:39 2004
+++ smarty/docs/en/designers/language-builtin-functions/language-function-config-load.xml	Sun Apr 18 13:18:26 2004
@@ -1,78 +1,77 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.2 $ -->
-		<sect1 id="language.function.config.load">
-			<title>config_load</title>
-            <informaltable frame="all">
-                <tgroup cols="5">
-                <colspec colname="param" align="center" />
-                <colspec colname="type" align="center" />
-                <colspec colname="required" align="center" />
-                <colspec colname="default" align="center" />
-                <colspec colname="desc" />
-                <thead>
-                    <row>
-                        <entry>Attribute Name</entry>
-                        <entry>Type</entry>
-                        <entry>Required</entry>
-                        <entry>Default</entry>
-                        <entry>Description</entry>
-                    </row>
-                </thead>
-                <tbody>
-                    <row>
-                        <entry>file</entry>
-                        <entry>string</entry>
-                        <entry>Yes</entry>
-                        <entry><emphasis>n/a</emphasis></entry>
-                        <entry>The name of the config file to include</entry>
-                    </row>
-                    <row>
-                        <entry>section</entry>
-                        <entry>string</entry>
-                        <entry>No</entry>
-                        <entry><emphasis>n/a</emphasis></entry>
-                        <entry>The name of the section to load</entry>
-                    </row>
-                    <row>
-                        <entry>scope</entry>
-                        <entry>string</entry>
-                        <entry>no</entry>
-                        <entry><emphasis>local</emphasis></entry>
-                        <entry>
-						How the scope of the loaded variables are treated,
-						which must be one of local, parent or global. local
-						means variables are loaded into the local template
-						context. parent means variables are loaded into both
-						the local context and the parent template that called
-						it. global means variables are available to all
-						templates.
-						</entry>
-                    </row>
-                    <row>
-                        <entry>global</entry>
-                        <entry>boolean</entry>
-                        <entry>No</entry>
-                        <entry><emphasis>No</emphasis></entry>
-                        <entry>
-						Whether or not variables are visible to the parent
-						template, same as scope=parent. NOTE: This attribute is
-						deprecated by the scope attribute, but still supported.
-						If scope is supplied, this value is ignored.
-						</entry>
-                    </row>
-                </tbody>
-                </tgroup>
-            </informaltable>
-			<para>
-			This function is used for loading in variables from a
-			configuration file into the template.
-            See <link linkend="config.files">Config Files</link> for more
-            info.
-			</para>
-<example>
-<title>function config_load</title>
-
-<programlisting>
+<!-- $Revision: 1.3 $ -->
+<sect1 id="language.function.config.load">
+ <title>config_load</title>
+ <informaltable frame="all">
+  <tgroup cols="5">
+   <colspec colname="param" align="center" />
+   <colspec colname="type" align="center" />
+   <colspec colname="required" align="center" />
+   <colspec colname="default" align="center" />
+   <colspec colname="desc" />
+   <thead>
+    <row>
+     <entry>Attribute Name</entry>
+     <entry>Type</entry>
+     <entry>Required</entry>
+     <entry>Default</entry>
+     <entry>Description</entry>
+    </row>
+   </thead>
+   <tbody>
+    <row>
+     <entry>file</entry>
+     <entry>string</entry>
+     <entry>Yes</entry>
+     <entry><emphasis>n/a</emphasis></entry>
+     <entry>The name of the config file to include</entry>
+    </row>
+    <row>
+     <entry>section</entry>
+     <entry>string</entry>
+     <entry>No</entry>
+     <entry><emphasis>n/a</emphasis></entry>
+     <entry>The name of the section to load</entry>
+    </row>
+    <row>
+     <entry>scope</entry>
+     <entry>string</entry>
+     <entry>no</entry>
+     <entry><emphasis>local</emphasis></entry>
+     <entry>
+      How the scope of the loaded variables are treated,
+      which must be one of local, parent or global. local
+      means variables are loaded into the local template
+      context. parent means variables are loaded into both
+      the local context and the parent template that called
+      it. global means variables are available to all
+      templates.
+     </entry>
+    </row>
+    <row>
+     <entry>global</entry>
+     <entry>boolean</entry>
+     <entry>No</entry>
+     <entry><emphasis>No</emphasis></entry>
+     <entry>
+      Whether or not variables are visible to the parent
+      template, same as scope=parent. NOTE: This attribute is
+      deprecated by the scope attribute, but still supported.
+      If scope is supplied, this value is ignored.
+     </entry>
+    </row>
+   </tbody>
+  </tgroup>
+ </informaltable>
+ <para>
+  This function is used for loading in variables from a
+  configuration file into the template.
+  See <link linkend="config.files">Config Files</link> for more
+  info.
+ </para>
+ <example>
+  <title>function config_load</title>
+  <programlisting>
 <![CDATA[
 {config_load file="colors.conf"}
 
@@ -80,31 +79,31 @@
 <title>{#pageTitle#}</title>
 <body bgcolor="{#bodyBgColor#}">
 <table border="{#tableBorderSize#}" bgcolor="{#tableBgColor#}">
-	<tr bgcolor="{#rowBgColor#}">
-		<td>First</td>
-		<td>Last</td>
-		<td>Address</td>
-	</tr>
+   <tr bgcolor="{#rowBgColor#}">
+      <td>First</td>
+      <td>Last</td>
+      <td>Address</td>
+   </tr>
 </table>
 </body>
 </html>
 ]]>
-</programlisting>
-</example>
-			<para>
-            Config files may also contain sections. You can load variables from
-            within a section with the added attribute
-            <emphasis>section</emphasis>.
-			</para>
-            <para>
-            NOTE: <emphasis>Config file sections</emphasis> and the built-in
-            template function called <emphasis>section</emphasis> have nothing
-            to do with each other, they just happen to share a common naming
-            convention.
-            </para>
-<example>
-<title>function config_load with section</title>
-<programlisting>
+  </programlisting>
+ </example>
+ <para>
+  Config files may also contain sections. You can load variables from
+  within a section with the added attribute
+  <emphasis>section</emphasis>.
+ </para>
+ <para>
+  NOTE: <emphasis>Config file sections</emphasis> and the built-in
+  template function called <emphasis>section</emphasis> have nothing
+  to do with each other, they just happen to share a common naming
+  convention.
+ </para>
+ <example>
+  <title>function config_load with section</title>
+  <programlisting>
 <![CDATA[
 {config_load file="colors.conf" section="Customer"}
 
@@ -112,17 +111,17 @@
 <title>{#pageTitle#}</title>
 <body bgcolor="{#bodyBgColor#}">
 <table border="{#tableBorderSize#}" bgcolor="{#tableBgColor#}">
-	<tr bgcolor="{#rowBgColor#}">
-		<td>First</td>
-		<td>Last</td>
-		<td>Address</td>
-	</tr>
+   <tr bgcolor="{#rowBgColor#}">
+      <td>First</td>
+      <td>Last</td>
+      <td>Address</td>
+   </tr>
 </table>
 </body>
 </html>
 ]]>
-</programlisting>
-</example>
+  </programlisting>
+ </example>
 </sect1>
 
 <!-- Keep this comment at the end of the file
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.