[prev in list] [next in list] [prev in thread] [next in thread] 

List:       smarty-cvs
Subject:    [SMARTY-CVS] cvs: smarty /docs/es getting-started.xml language-defs.ent language-snippets.ent  /docs
From:       "Messju Mohr" <messju () php ! net>
Date:       2004-10-07 19:42:10
Message-ID: cvsmessju1097178129 () cvsserver
[Download RAW message or body]

messju		Thu Oct  7 15:42:10 2004 EDT

  Added files:                 
    /smarty/docs/es	language-defs.ent language-snippets.ent 

  Modified files:              
    /smarty/docs/es	getting-started.xml 
    /smarty/docs/es/designers/language-basic-syntax	
                                                   	language-syntax-comments.xml 
    /smarty/docs/es/programmers/plugins	plugins-block-functions.xml 
  Log:
  fixed build
  
  
http://cvs.php.net/diff.php/smarty/docs/es/getting-started.xml?r1=1.1&r2=1.2&ty=u
Index: smarty/docs/es/getting-started.xml
diff -u smarty/docs/es/getting-started.xml:1.1 smarty/docs/es/getting-started.xml:1.2
--- smarty/docs/es/getting-started.xml:1.1	Thu Oct  7 14:50:42 2004
+++ smarty/docs/es/getting-started.xml	Thu Oct  7 15:42:08 2004
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.1 $ -->
+<!-- $Revision: 1.2 $ -->
 <part id="getting.started">
  <title>Iniciando</title>
 
@@ -165,7 +165,7 @@
    </example>
    <para>
     Smarty utiliza una constante de PHP llamada <link
-    linkend="constant.smarty.dir">SMARTY_DIR</A> que es la ruta para 
+    linkend="constant.smarty.dir">SMARTY_DIR</link> que es la ruta para 
     el directorio de la biblioteca de Smarty. Basicamente, si su 
     aplicación puede encontrar el archivo <emphasis>Smarty.class.php
     </emphasis>, usted no necesita definir SMARTY_DIR, Smarty lo 
http://cvs.php.net/diff.php/smarty/docs/es/designers/language-basic-syntax/language-syntax-comments.xml?r1=1.1&r2=1.2&ty=u
                
Index: smarty/docs/es/designers/language-basic-syntax/language-syntax-comments.xml
diff -u smarty/docs/es/designers/language-basic-syntax/language-syntax-comments.xml:1.1 \
                smarty/docs/es/designers/language-basic-syntax/language-syntax-comments.xml:1.2
                
--- smarty/docs/es/designers/language-basic-syntax/language-syntax-comments.xml:1.1	Thu \
                Oct  7 14:50:49 2004
+++ smarty/docs/es/designers/language-basic-syntax/language-syntax-comments.xml	Thu \
Oct  7 15:42:08 2004 @@ -1,10 +1,10 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.1 $ -->
+<!-- $Revision: 1.2 $ -->
 <sect1 id="language.syntax.comments">
  <title>Comentarios</title>
  <para>
   Los comentarios en los templates son cercados por asteriscos, y por 
-  los delimitadores, así:<br> {* este es un comentario *}.
+  los delimitadores, así: {* este es un comentario *}.
   Los comentarios en Smarty no son mostrados en la salida final del
   template. 
   Estos son usados para hacer notas internas dentro del template.
http://cvs.php.net/diff.php/smarty/docs/es/programmers/plugins/plugins-block-functions.xml?r1=1.1&r2=1.2&ty=u
                
Index: smarty/docs/es/programmers/plugins/plugins-block-functions.xml
diff -u smarty/docs/es/programmers/plugins/plugins-block-functions.xml:1.1 \
                smarty/docs/es/programmers/plugins/plugins-block-functions.xml:1.2
--- smarty/docs/es/programmers/plugins/plugins-block-functions.xml:1.1	Thu Oct  7 \
                14:50:51 2004
+++ smarty/docs/es/programmers/plugins/plugins-block-functions.xml	Thu Oct  7 \
15:42:08 2004 @@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.1 $ -->
+<!-- $Revision: 1.2 $ -->
    <sect1 id="plugins.block.functions"><title>Block Functions</title>
     <funcsynopsis>
      <funcprototype>
@@ -46,7 +46,7 @@
 
     <para>
      El parámetro <parameter>&amp;$repeat</parameter> es pasado por
-     referencia para la funci&oacuten de implementación y proporciona
+     referencia para la funci&oacute;n de implementación y proporciona
      la posibilidad de controlar cuantas veces será mostrado el bloque.
      Por default <parameter>$repeat</parameter> es <literal>true</literal>
      en la primera llamada de la block-function (etiqueta de apertura del 

http://cvs.php.net/co.php/smarty/docs/es/language-defs.ent?r=1.1&p=1
Index: smarty/docs/es/language-defs.ent
+++ smarty/docs/es/language-defs.ent
<!-- $Revision: 1.1 $ -->

<!ENTITY SMARTYManual      "Smarty Manual">
<!ENTITY SMARTYDesigners   "Smarty For Template Designers">
<!ENTITY SMARTYProgrammers "Smarty For Programmers">
<!ENTITY Appendixes        "Appendixes">

http://cvs.php.net/co.php/smarty/docs/es/language-snippets.ent?r=1.1&p=1
Index: smarty/docs/es/language-snippets.ent
+++ smarty/docs/es/language-snippets.ent
<!-- $Revision: 1.1 $ -->

<!ENTITY note.parameter.merge '<note>
 <title>Technical Note</title>
 <para>
  The <parameter>merge</parameter> parameter respects array keys, so if
  you merge two numerically indexed arrays, they may overwrite each other
  or result in non-sequential keys. This is unlike the array_merge() function
  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>'>

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


[prev in list] [next in list] [prev in thread] [next in thread]