cvs: smarty /docs/en language-snippets.ent /docs/en/programmers/api-functions api-display.xml api-fetch.xml

didou		Tue Apr 20 07:37:05 2004 EDT

  Modified files:              
    /smarty/docs/en	language-snippets.ent 
    /smarty/docs/en/programmers/api-functions	api-display.xml 
                                             	api-fetch.xml 
  Log:
  another entity
  
http://cvs.php.net/diff.php/smarty/docs/en/language-snippets.ent?r1=1.1&r2=1.2&ty=u
Index: smarty/docs/en/language-snippets.ent
diff -u smarty/docs/en/language-snippets.ent:1.1 smarty/docs/en/language-snippets.ent:1.2
--- smarty/docs/en/language-snippets.ent:1.1	Tue Apr 20 07:27:15 2004
+++ smarty/docs/en/language-snippets.ent	Tue Apr 20 07:37:05 2004
@@ -1,4 +1,4 @@
-<!-- $Revision: 1.1 $ -->
+<!-- $Revision: 1.2 $ -->
 
 <!ENTITY note.parameter.merge '<note>
  <title>Technical Note</title>
@@ -9,3 +9,16 @@
   of PHP which wipes out numerical keys and renumbers them.
  </para>
 </note>'>
+
+<!ENTITY parameter.compileid '<para>
+ As an optional third parameter, you can pass a <parameter>compile_id</parameter>. 
+ This is in the event that you want to compile different versions of
+ the same template, such as having separate templates compiled
+ for different languages. Another use for compile_id is when you
+ use more than one $template_dir but only one $compile_dir. Set
+ a separate <parameter>compile_id</parameter> for each $template_dir, otherwise
+ templates of the same name will overwrite each other. You can
+ also set the <link
+ linkend="variable.compile.id">$compile_id</link> variable once
+ instead of passing this to each call to this function.
+</para>'>
http://cvs.php.net/diff.php/smarty/docs/en/programmers/api-functions/api-display.xml?r1=1.2&r2=1.3&ty=u
Index: smarty/docs/en/programmers/api-functions/api-display.xml
diff -u smarty/docs/en/programmers/api-functions/api-display.xml:1.2 smarty/docs/en/programmers/api-functions/api-display.xml:1.3
--- smarty/docs/en/programmers/api-functions/api-display.xml:1.2	Sun Apr 18 15:22:55 2004
+++ smarty/docs/en/programmers/api-functions/api-display.xml	Tue Apr 20 07:37:05 2004
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
 <refentry id="api.display">
  <refnamediv>
   <refname>display</refname>
@@ -20,17 +20,7 @@
    cache id. See the <link linkend="caching">caching
    section</link> for more information.
   </para>
-  <para>
-   As an optional third parameter, you can pass a compile id. This
-   is in the event that you want to compile different versions of
-   the same template, such as having separate templates compiled
-   for different languages. Another use for compile_id is when you
-   use more than one $template_dir but only one $compile_dir. Set
-   a separate compile_id for each $template_dir, otherwise
-   templates of the same name will overwrite each other. You can
-   also set the <link linkend="variable.compile.id">$compile_id</link>
-   variable once instead of passing this to each call to display().
-  </para>
+  &parameter.compileid;
   <example>
    <title>display</title>
    <programlisting role="php">
http://cvs.php.net/diff.php/smarty/docs/en/programmers/api-functions/api-fetch.xml?r1=1.2&r2=1.3&ty=u
Index: smarty/docs/en/programmers/api-functions/api-fetch.xml
diff -u smarty/docs/en/programmers/api-functions/api-fetch.xml:1.2 smarty/docs/en/programmers/api-functions/api-fetch.xml:1.3
--- smarty/docs/en/programmers/api-functions/api-fetch.xml:1.2	Sun Apr 18 15:22:55 2004
+++ smarty/docs/en/programmers/api-functions/api-fetch.xml	Tue Apr 20 07:37:05 2004
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
 <refentry id="api.fetch">
  <refnamediv>
   <refname>fetch</refname>
@@ -21,18 +21,7 @@
    cache id. See the <link linkend="caching">caching
    section</link> for more information.
   </para>
-  <para>
-   As an optional third parameter, you can pass a compile id. This
-   is in the event that you want to compile different versions of
-   the same template, such as having separate templates compiled
-   for different languages. Another use for compile_id is when you
-   use more than one $template_dir but only one $compile_dir. Set
-   a separate compile_id for each $template_dir, otherwise
-   templates of the same name will overwrite each other. You can
-   also set the <link
-   linkend="variable.compile.id">$compile_id</link> variable once
-   instead of passing this to each call to fetch().
-  </para>
+  &parameter.compileid;
   <para>
    <example>
     <title>fetch</title>

-- 
Smarty CVS Mailing List (http://cvs.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php