[jboss-cvs] JBossAS SVN: r92186 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR.

[jboss-cvs-commits at lists.jboss.org]

Author: ldelima at redhat.com
Date: 2009-08-10 02:57:47 -0400 (Mon, 10 Aug 2009)
New Revision: 92186

Modified:
   projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/The_CMP_Engine.po
Log:
translation finished

Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/The_CMP_Engine.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/The_CMP_Engine.po	2009-08-10 06:56:25 UTC (rev 92185)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/The_CMP_Engine.po	2009-08-10 06:57:47 UTC (rev 92186)
@@ -8,7 +8,7 @@
 "Project-Id-Version: The_CMP_Engine\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
 "POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-08-10 16:56+1000\n"
+"PO-Revision-Date: 2009-08-10 16:57+1000\n"
 "Last-Translator: \n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -8326,7 +8326,7 @@
 #: The_CMP_Engine.xml:2655
 #, no-c-format
 msgid "Type Mapping"
-msgstr "Type Mapping"
+msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2656
@@ -8337,22 +8337,18 @@
 "content model for the type-mapping element is given in <xref linkend="
 "\"Type_Mapping-The_jbosscmp_jdbc_type_mapping_element_content_model.\"/>."
 msgstr ""
-"Customization of a database is done through the <literal>type-mapping</"
-"literal> section of the <literal>jbosscmp-jdbc.xml</literal> descriptor. The "
-"content model for the type-mapping element is given in <xref linkend="
-"\"Type_Mapping-The_jbosscmp_jdbc_type_mapping_element_content_model.\"/>."
 
 #. Tag: title
 #: The_CMP_Engine.xml:2661
 #, no-c-format
 msgid "The jbosscmp-jdbc type-mapping element content model."
-msgstr "The jbosscmp-jdbc type-mapping element content model."
+msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2669
 #, no-c-format
 msgid "The elements are:"
-msgstr "The elements are:"
+msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2674
@@ -8363,10 +8359,6 @@
 "mapping by the <literal>datasource-mapping</literal> elements found in "
 "defaults and entity."
 msgstr ""
-"<emphasis role=\"bold\">name</emphasis>: This required element provides the "
-"name identifying the database customization. It is used to refer to the "
-"mapping by the <literal>datasource-mapping</literal> elements found in "
-"defaults and entity."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2679
@@ -8377,28 +8369,24 @@
 "create a row lock on the selected rows. The template must support three "
 "arguments:"
 msgstr ""
-"<emphasis role=\"bold\">row-locking-template</emphasis>: This required "
-"element gives the <literal>PreparedStatement</literal> template used to "
-"create a row lock on the selected rows. The template must support three "
-"arguments:"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2684
 #, no-c-format
 msgid "the select clause"
-msgstr "the select clause"
+msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2689
 #, no-c-format
 msgid "the from clause. The order of the tables is currently not guaranteed"
-msgstr "the from clause. The order of the tables is currently not guaranteed"
+msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2694
 #, no-c-format
 msgid "the where clause"
-msgstr "the where clause"
+msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2699
@@ -8408,9 +8396,6 @@
 "empty. The most common form of row locking is select for update as in: "
 "<literal>SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE</literal>."
 msgstr ""
-"If row locking is not supported in select statement this element should be "
-"empty. The most common form of row locking is select for update as in: "
-"<literal>SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE</literal>."
 
 #. Tag: para
 #: The_CMP_Engine.xml:2704
@@ -8421,10 +8406,6 @@
 "create a primary key constraint in the create table statement. The template "
 "must support two arguments"
 msgstr ""
-"<emphasis role=\"bold\">pk-constraint-template</emphasis>: This required "
-"element gives the <literal>PreparedStatement</literal> template used to "
-"create a primary key constraint in the create table statement. The template "
-"must support two arguments"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2709
@@ -8433,14 +8414,12 @@
 "Primary key constraint name; which is always <literal>pk_{table-name}</"
 "literal>"
 msgstr ""
-"Primary key constraint name; which is always <literal>pk_{table-name}</"
-"literal>"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2714
 #, no-c-format
 msgid "Comma separated list of primary key column names"
-msgstr "Comma separated list of primary key column names"
+msgstr ""
 
 #. Tag: para
 #: The_CMP_Engine.xml:2719
@@ -8450,9 +8429,6 @@
 "statement this element should be empty. The most common form of a primary "
 "key constraint is: <literal>CONSTRAINT ?1 PRIMARY KEY (?2)</literal>"
 msgstr ""
-"If a primary key constraint clause is not supported in a create table "
-"statement this element should be empty. The most common form of a primary "
-"key constraint is: <literal>CONSTRAINT ?1 PRIMARY KEY (?2)</literal>"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2724
@@ -8462,9 +8438,6 @@
 "template used to create a foreign key constraint in separate statement. The "
 "template must support five arguments:"
 msgstr ""
-"<emphasis role=\"bold\">fk-constraint-template</emphasis>: This is the "
-"template used to create a foreign key constraint in separate statement. The "
-"template must support five arguments:"
 
 #. Tag: para
 #: The_CMP_Engine.xml:2729