Author: d.plentz Date: 2008-08-12 11:42:10 -0400 (Tue, 12 Aug 2008) New Revision: 15038 Modified: core/trunk/documentation/manual/old/pt-BR/src/main/docbook/content/tutorial1.xml core/trunk/documentation/manual/src/main/docbook/en-US/content/component_mapping.xml core/trunk/documentation/manual/src/main/docbook/es-ES/content/component_mapping.po core/trunk/documentation/manual/src/main/docbook/es-ES/content/transactions.po core/trunk/documentation/manual/src/main/docbook/es-ES/content/tutorial.po core/trunk/documentation/manual/src/main/docbook/fr-FR/content/component_mapping.po core/trunk/documentation/manual/src/main/docbook/fr-FR/content/transactions.po core/trunk/documentation/manual/src/main/docbook/fr-FR/content/tutorial.po core/trunk/documentation/manual/src/main/docbook/ja-JP/content/component_mapping.po core/trunk/documentation/manual/src/main/docbook/ja-JP/content/transactions.po core/trunk/documentation/manual/src/main/docbook/ja-JP/content/tutorial.po core/trunk/documentation/manual/src/main/docbook/ko-KR/content/component_mapping.po core/trunk/documentation/manual/src/main/docbook/ko-KR/content/transactions.po core/trunk/documentation/manual/src/main/docbook/ko-KR/content/tutorial.po core/trunk/documentation/manual/src/main/docbook/pot/content/component_mapping.pot core/trunk/documentation/manual/src/main/docbook/pt-BR/content/component_mapping.po core/trunk/documentation/manual/src/main/docbook/pt-BR/content/transactions.po core/trunk/documentation/manual/src/main/docbook/pt-BR/content/tutorial.po core/trunk/documentation/manual/src/main/docbook/zh-CN/content/component_mapping.po core/trunk/documentation/manual/src/main/docbook/zh-CN/content/transactions.po core/trunk/documentation/manual/src/main/docbook/zh-CN/content/tutorial.po Log: [HHH-3080] Oject typo Modified: core/trunk/documentation/manual/old/pt-BR/src/main/docbook/content/tutorial1.xml =================================================================== --- core/trunk/documentation/manual/old/pt-BR/src/main/docbook/content/tutorial1.xml 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/old/pt-BR/src/main/docbook/content/tutorial1.xml 2008-08-12 15:42:10 UTC (rev 15038) @@ -1,6 +1,6 @@ -<?xml version='1.0' encoding="UTF-8"?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> - +<?xml version='1.0' encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> + <chapter id="tutorial"> <title>Introdu&#x00E7;&#x00E3;o ao Hibernate</title> @@ -1444,7 +1444,7 @@ That's it, the servlet is complete. A request to the servlet will be processed in a single <literal>Session</literal> and <literal>Transaction</literal>. As earlier in the standalone application, Hibernate can automatically bind these - ojects to the current thread of execution. This gives you the freedom to layer + objects to the current thread of execution. This gives you the freedom to layer your code and access the <literal>SessionFactory</literal> in any way you like. Usually you'd use a more sophisticated design and move the data access code into data access objects (the DAO pattern). See the Hibernate Wiki for more Modified: core/trunk/documentation/manual/src/main/docbook/en-US/content/component_mapping.xml =================================================================== --- core/trunk/documentation/manual/src/main/docbook/en-US/content/component_mapping.xml 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/en-US/content/component_mapping.xml 2008-08-12 15:42:10 UTC (rev 15038) @@ -126,7 +126,7 @@ <para> Like all value types, components do not support shared references. In other words, two persons could have the same name, but the two person objects would contain two independent - name ojects, only "the same" by value. The null value semantics of a component are + name objects, only "the same" by value. The null value semantics of a component are <emphasis>ad hoc</emphasis>. When reloading the containing object, Hibernate will assume that if all component columns are null, then the entire component is null. This should be okay for most purposes. Modified: core/trunk/documentation/manual/src/main/docbook/es-ES/content/component_mapping.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/es-ES/content/component_mapping.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/es-ES/content/component_mapping.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -197,7 +197,7 @@ msgid "" "Like all value types, components do not support shared references. In other " "words, two persons could have the same name, but the two person objects " -"would contain two independent name ojects, only \"the same\" by value. The " +"would contain two independent name objects, only \"the same\" by value. The " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "reloading the containing object, Hibernate will assume that if all component " "columns are null, then the entire component is null. This should be okay for " Modified: core/trunk/documentation/manual/src/main/docbook/es-ES/content/transactions.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/es-ES/content/transactions.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/es-ES/content/transactions.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -1464,7 +1464,7 @@ msgid "" "Clearly, manual version checking is only feasible in very trivial " "circumstances and not practical for most applications. Often not only single " -"instances, but complete graphs of modified ojects have to be checked. " +"instances, but complete graphs of modified objects have to be checked. " "Hibernate offers automatic version checking with either an extended " "<literal>Session</literal> or detached instances as the design paradigm." msgstr "" Modified: core/trunk/documentation/manual/src/main/docbook/es-ES/content/tutorial.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/es-ES/content/tutorial.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/es-ES/content/tutorial.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -2936,7 +2936,7 @@ "That's it, the servlet is complete. A request to the servlet will be " "processed in a single <literal>Session</literal> and <literal>Transaction</" "literal>. As earlier in the standalone application, Hibernate can " -"automatically bind these ojects to the current thread of execution. This " +"automatically bind these objects to the current thread of execution. This " "gives you the freedom to layer your code and access the " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "more sophisticated design and move the data access code into data access " @@ -2945,7 +2945,7 @@ "That's it, the servlet is complete. A request to the servlet will be " "processed in a single <literal>Session</literal> and <literal>Transaction</" "literal>. As earlier in the standalone application, Hibernate can " -"automatically bind these ojects to the current thread of execution. This " +"automatically bind these objects to the current thread of execution. This " "gives you the freedom to layer your code and access the " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "more sophisticated design and move the data access code into data access " Modified: core/trunk/documentation/manual/src/main/docbook/fr-FR/content/component_mapping.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/fr-FR/content/component_mapping.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/fr-FR/content/component_mapping.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -164,7 +164,7 @@ msgid "" "Like all value types, components do not support shared references. In other " "words, two persons could have the same name, but the two person objects " -"would contain two independent name ojects, only \"the same\" by value. The " +"would contain two independent name objects, only \"the same\" by value. The " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "reloading the containing object, Hibernate will assume that if all component " "columns are null, then the entire component is null. This should be okay for " Modified: core/trunk/documentation/manual/src/main/docbook/fr-FR/content/transactions.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/fr-FR/content/transactions.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/fr-FR/content/transactions.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -1494,7 +1494,7 @@ msgid "" "Clearly, manual version checking is only feasible in very trivial " "circumstances and not practical for most applications. Often not only single " -"instances, but complete graphs of modified ojects have to be checked. " +"instances, but complete graphs of modified objects have to be checked. " "Hibernate offers automatic version checking with either an extended " "<literal>Session</literal> or detached instances as the design paradigm." msgstr "" Modified: core/trunk/documentation/manual/src/main/docbook/fr-FR/content/tutorial.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/fr-FR/content/tutorial.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/fr-FR/content/tutorial.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -2669,7 +2669,7 @@ "That's it, the servlet is complete. A request to the servlet will be " "processed in a single <literal>Session</literal> and <literal>Transaction</" "literal>. As earlier in the standalone application, Hibernate can " -"automatically bind these ojects to the current thread of execution. This " +"automatically bind these objects to the current thread of execution. This " "gives you the freedom to layer your code and access the " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "more sophisticated design and move the data access code into data access " Modified: core/trunk/documentation/manual/src/main/docbook/ja-JP/content/component_mapping.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/ja-JP/content/component_mapping.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/ja-JP/content/component_mapping.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -162,7 +162,7 @@ msgid "" "Like all value types, components do not support shared references. In other " "words, two persons could have the same name, but the two person objects " -"would contain two independent name ojects, only \"the same\" by value. The " +"would contain two independent name objects, only \"the same\" by value. The " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "reloading the containing object, Hibernate will assume that if all component " "columns are null, then the entire component is null. This should be okay for " Modified: core/trunk/documentation/manual/src/main/docbook/ja-JP/content/transactions.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/ja-JP/content/transactions.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/ja-JP/content/transactions.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -1418,7 +1418,7 @@ msgid "" "Clearly, manual version checking is only feasible in very trivial " "circumstances and not practical for most applications. Often not only single " -"instances, but complete graphs of modified ojects have to be checked. " +"instances, but complete graphs of modified objects have to be checked. " "Hibernate offers automatic version checking with either an extended " "<literal>Session</literal> or detached instances as the design paradigm." msgstr "" Modified: core/trunk/documentation/manual/src/main/docbook/ja-JP/content/tutorial.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/ja-JP/content/tutorial.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/ja-JP/content/tutorial.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -2598,7 +2598,7 @@ "That's it, the servlet is complete. A request to the servlet will be " "processed in a single <literal>Session</literal> and <literal>Transaction</" "literal>. As earlier in the standalone application, Hibernate can " -"automatically bind these ojects to the current thread of execution. This " +"automatically bind these objects to the current thread of execution. This " "gives you the freedom to layer your code and access the " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "more sophisticated design and move the data access code into data access " Modified: core/trunk/documentation/manual/src/main/docbook/ko-KR/content/component_mapping.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/ko-KR/content/component_mapping.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/ko-KR/content/component_mapping.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -162,7 +162,7 @@ msgid "" "Like all value types, components do not support shared references. In other " "words, two persons could have the same name, but the two person objects " -"would contain two independent name ojects, only \"the same\" by value. The " +"would contain two independent name objects, only \"the same\" by value. The " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "reloading the containing object, Hibernate will assume that if all component " "columns are null, then the entire component is null. This should be okay for " Modified: core/trunk/documentation/manual/src/main/docbook/ko-KR/content/transactions.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/ko-KR/content/transactions.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/ko-KR/content/transactions.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -1413,7 +1413,7 @@ msgid "" "Clearly, manual version checking is only feasible in very trivial " "circumstances and not practical for most applications. Often not only single " -"instances, but complete graphs of modified ojects have to be checked. " +"instances, but complete graphs of modified objects have to be checked. " "Hibernate offers automatic version checking with either an extended " "<literal>Session</literal> or detached instances as the design paradigm." msgstr "" Modified: core/trunk/documentation/manual/src/main/docbook/ko-KR/content/tutorial.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/ko-KR/content/tutorial.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/ko-KR/content/tutorial.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -2616,7 +2616,7 @@ "That's it, the servlet is complete. A request to the servlet will be " "processed in a single <literal>Session</literal> and <literal>Transaction</" "literal>. As earlier in the standalone application, Hibernate can " -"automatically bind these ojects to the current thread of execution. This " +"automatically bind these objects to the current thread of execution. This " "gives you the freedom to layer your code and access the " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "more sophisticated design and move the data access code into data access " Modified: core/trunk/documentation/manual/src/main/docbook/pot/content/component_mapping.pot =================================================================== --- core/trunk/documentation/manual/src/main/docbook/pot/content/component_mapping.pot 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/pot/content/component_mapping.pot 2008-08-12 15:42:10 UTC (rev 15038) @@ -136,7 +136,7 @@ #. Tag: para #: component_mapping.xml:70 #, no-c-format -msgid "Like all value types, components do not support shared references. In other words, two persons could have the same name, but the two person objects would contain two independent name ojects, only \"the same\" by value. The null value semantics of a component are <emphasis>ad hoc</emphasis>. When reloading the containing object, Hibernate will assume that if all component columns are null, then the entire component is null. This should be okay for most purposes." +msgid "Like all value types, components do not support shared references. In other words, two persons could have the same name, but the two person objects would contain two independent name objects, only \"the same\" by value. The null value semantics of a component are <emphasis>ad hoc</emphasis>. When reloading the containing object, Hibernate will assume that if all component columns are null, then the entire component is null. This should be okay for most purposes." msgstr "" #. Tag: para Modified: core/trunk/documentation/manual/src/main/docbook/pt-BR/content/component_mapping.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/pt-BR/content/component_mapping.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/pt-BR/content/component_mapping.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -162,7 +162,7 @@ msgid "" "Like all value types, components do not support shared references. In other " "words, two persons could have the same name, but the two person objects " -"would contain two independent name ojects, only \"the same\" by value. The " +"would contain two independent name objects, only \"the same\" by value. The " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "reloading the containing object, Hibernate will assume that if all component " "columns are null, then the entire component is null. This should be okay for " Modified: core/trunk/documentation/manual/src/main/docbook/pt-BR/content/transactions.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/pt-BR/content/transactions.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/pt-BR/content/transactions.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -1454,7 +1454,7 @@ msgid "" "Clearly, manual version checking is only feasible in very trivial " "circumstances and not practical for most applications. Often not only single " -"instances, but complete graphs of modified ojects have to be checked. " +"instances, but complete graphs of modified objects have to be checked. " "Hibernate offers automatic version checking with either an extended " "<literal>Session</literal> or detached instances as the design paradigm." msgstr "" Modified: core/trunk/documentation/manual/src/main/docbook/pt-BR/content/tutorial.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/pt-BR/content/tutorial.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/pt-BR/content/tutorial.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -2652,7 +2652,7 @@ "That's it, the servlet is complete. A request to the servlet will be " "processed in a single <literal>Session</literal> and <literal>Transaction</" "literal>. As earlier in the standalone application, Hibernate can " -"automatically bind these ojects to the current thread of execution. This " +"automatically bind these objects to the current thread of execution. This " "gives you the freedom to layer your code and access the " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "more sophisticated design and move the data access code into data access " Modified: core/trunk/documentation/manual/src/main/docbook/zh-CN/content/component_mapping.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/zh-CN/content/component_mapping.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/zh-CN/content/component_mapping.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -161,7 +161,7 @@ msgid "" "Like all value types, components do not support shared references. In other " "words, two persons could have the same name, but the two person objects " -"would contain two independent name ojects, only \"the same\" by value. The " +"would contain two independent name objects, only \"the same\" by value. The " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "reloading the containing object, Hibernate will assume that if all component " "columns are null, then the entire component is null. This should be okay for " Modified: core/trunk/documentation/manual/src/main/docbook/zh-CN/content/transactions.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/zh-CN/content/transactions.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/zh-CN/content/transactions.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -1318,7 +1318,7 @@ msgid "" "Clearly, manual version checking is only feasible in very trivial " "circumstances and not practical for most applications. Often not only single " -"instances, but complete graphs of modified ojects have to be checked. " +"instances, but complete graphs of modified objects have to be checked. " "Hibernate offers automatic version checking with either an extended " "<literal>Session</literal> or detached instances as the design paradigm." msgstr "" Modified: core/trunk/documentation/manual/src/main/docbook/zh-CN/content/tutorial.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/zh-CN/content/tutorial.po 2008-08-12 15:21:42 UTC (rev 15037) +++ core/trunk/documentation/manual/src/main/docbook/zh-CN/content/tutorial.po 2008-08-12 15:42:10 UTC (rev 15038) @@ -2496,7 +2496,7 @@ "That's it, the servlet is complete. A request to the servlet will be " "processed in a single <literal>Session</literal> and <literal>Transaction</" "literal>. As earlier in the standalone application, Hibernate can " -"automatically bind these ojects to the current thread of execution. This " +"automatically bind these objects to the current thread of execution. This " "gives you the freedom to layer your code and access the " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "more sophisticated design and move the data access code into data access "