[richfaces-svn-commits] JBoss Rich Faces SVN: r1370 - trunk/docs/userguide/en/src/main/docbook/modules.

richfaces-svn-commits at lists.jboss.org richfaces-svn-commits at lists.jboss.org
Thu Jun 28 09:15:16 EDT 2007


Author: smukhina
Date: 2007-06-28 09:15:15 -0400 (Thu, 28 Jun 2007)
New Revision: 1370

Modified:
   trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml
   trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml
   trunk/docs/userguide/en/src/main/docbook/modules/RFCidesupport.xml
   trunk/docs/userguide/en/src/main/docbook/modules/RFCsetwebappl.xml
   trunk/docs/userguide/en/src/main/docbook/modules/RFCtechreqs.xml
Log:
English language and xml markup correction

Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml	2007-06-28 13:13:06 UTC (rev 1369)
+++ trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml	2007-06-28 13:15:15 UTC (rev 1370)
@@ -50,7 +50,7 @@
       change all interrelating values, otherwise your interface can appear a
       bit clumsy. The chances of such an interface coming about is very high,
       as CSS editing usually becomes the duty of a general developer who
-      doesn't necessarily have much knowledge of user interface design.</para>
+      doesn&apos;t necessarily have much knowledge of user interface design.</para>
 
       <para>Moreover, if a customer wishes to have an interface look-and-feel
       that can be adjusted on-the-fly by an end user, your work is multiplied,
@@ -66,8 +66,8 @@
       synchronized fashion without messing up user interface
       consistency.</para>
 
-      <para>The <property>skinnability</property> feature can't completely
-      replace standard CSS and certainly doesn't eliminate its usage.
+      <para>The <property>skinnability</property> feature can&apos;t completely
+      replace standard CSS and certainly doesn&apos;t eliminate its usage.
       <property>Skinnability</property> is a high-level extension of standard
       CSS, which can be used together with regular CSS declarations. You can
       also refer to skin parameters in CSS via JSF Expression Language. You

Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml	2007-06-28 13:13:06 UTC (rev 1369)
+++ trunk/docs/userguide/en/src/main/docbook/modules/RFCfaq.xml	2007-06-28 13:15:15 UTC (rev 1370)
@@ -384,14 +384,14 @@
         <section>
                 <?dbhtml filename="Isthereawaytocapturetherowdata"?>
                 <title>Is there a way to capture the rowdata of dataTable and rich:subTable?</title>
-                <para> For information you can see discussion about this problem on the <ulink
+                <para> For necessary information you can see discussion about this problem on the <ulink
                         url="http://jboss.com/index.html?module=bb&amp;op=viewtopic&amp;t=111965"
                         >RichFaces Users Forum</ulink></para>
         </section>
         
         <section>
                 <?dbhtml filename="Isitpossibletouse thedatascroller"?>
-                <title>Is it possible to use datascroller without it&apos;s table border and styles (to show only links)?</title>
+                <title>Is it possible to use datascroller without its table border and styles (to show only links)?</title>
                 <para> It&apos; necessary to redefine rich* classes for example like this:</para>
                 <programlisting role="JAVA"><![CDATA[.rich-datascr-button { 
 border: 0px; 

Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCidesupport.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/RFCidesupport.xml	2007-06-28 13:13:06 UTC (rev 1369)
+++ trunk/docs/userguide/en/src/main/docbook/modules/RFCidesupport.xml	2007-06-28 13:15:15 UTC (rev 1370)
@@ -14,6 +14,6 @@
 	</keywordset>
 </chapterinfo>
   <title>IDE Support</title>
-  <para><ulink url="http://www.exadel.com/web/portal/products/ExadelStudioPro">Exadel Studio 4.0.4</ulink> is an <property>IDE</property> that provides full support for Java Server Faces, Exadel RichFaces, Ajax4jsf, Facelets, Struts, and other Web technologies. In addition to this, it seamlessly combines visual and source-oriented development approaches. One of the special support features for <property>Ajax4jsf</property> and <property>RichFaces</property> is that they are both available as project "capabilities". These project capabilities can be added to any existing JSF project to make the project an Ajax4jsf or RichFaces JSF project by automatically adding libraries and modifying configuration files as required.</para>
+  <para><ulink url="http://www.exadel.com/web/portal/products/ExadelStudioPro">Exadel Studio 4.0.4</ulink> is an <property>IDE</property> that provides full support for Java Server Faces, Exadel RichFaces, Ajax4jsf, Facelets, Struts, and other Web technologies. In addition to this, it seamlessly combines visual and source-oriented development approaches. One of the special support features for <property>Ajax4jsf</property> and <property>RichFaces</property> is that they are both available as project &quot;capabilities&quot;. These project capabilities can be added to any existing JSF project to make the project an Ajax4jsf or RichFaces JSF project by automatically adding libraries and modifying configuration files as required.</para>
 </chapter>
 

Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCsetwebappl.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/RFCsetwebappl.xml	2007-06-28 13:13:06 UTC (rev 1369)
+++ trunk/docs/userguide/en/src/main/docbook/modules/RFCsetwebappl.xml	2007-06-28 13:15:15 UTC (rev 1370)
@@ -17,7 +17,7 @@
   <para>Using the Rich Faces library doesn&apos;t require a major change of
   approach in how you set up a Web application, but a few steps are necessary,
   mostly for setting up the Ajax4jsf framework. When you just add RichFaces
-  capability to an existing project, the behavior of the application doesn't
+  capability to an existing project, the behavior of the application doesn&apos;t
   change.</para>
 
   <section id="Installation">

Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCtechreqs.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/RFCtechreqs.xml	2007-06-28 13:13:06 UTC (rev 1369)
+++ trunk/docs/userguide/en/src/main/docbook/modules/RFCtechreqs.xml	2007-06-28 13:15:15 UTC (rev 1370)
@@ -135,7 +135,7 @@
       <listitem>Safari 2.0</listitem>
 
     </itemizedlist>
-    <para>This list is composed basing on reports received from our users. We assume the list can be incomplete and absence of your environment in the list doesn't mean incompatibility.</para>
+    <para>This list is composed basing on reports received from our users. We assume the list can be incomplete and absence of your environment in the list doesn&apos;t mean incompatibility.</para>
     <para>We appreciate your feedback on platforms and browsers that aren&apos;t in the list but are compatible with RichFaces. It helps us to keep the list up-to-date.</para>
   </section>
 </chapter>
\ No newline at end of file




More information about the richfaces-svn-commits mailing list