another entity

docs/en/language-snippets.ent

@@ -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>'>

docs/en/programmers/api-functions/api-display.xml

@@ -20,17 +20,7 @@
    cache id. See the <link linkend="caching">caching
    section</link> for more information.
   </para>
-  <para>
+  &parameter.compileid;
-   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>
   <example>
    <title>display</title>
    <programlisting role="php">

docs/en/programmers/api-functions/api-fetch.xml

@@ -21,18 +21,7 @@
    cache id. See the <link linkend="caching">caching
    section</link> for more information.
   </para>
-  <para>
+  &parameter.compileid;
-   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>
   <para>
    <example>
     <title>fetch</title>