[ajax4jsf-svn-commits] JBoss Ajax4JSF SVN: r278 - trunk/docs/userguide/en/src/main/docbook/modules.
ajax4jsf-svn-commits at lists.jboss.org
ajax4jsf-svn-commits at lists.jboss.org
Mon Jun 25 08:30:04 EDT 2007
Author: smukhina
Date: 2007-06-25 08:30:04 -0400 (Mon, 25 Jun 2007)
New Revision: 278
Modified:
trunk/docs/userguide/en/src/main/docbook/modules/AUGWADParams.xml
trunk/docs/userguide/en/src/main/docbook/modules/a4jUGenvsettings.xml
trunk/docs/userguide/en/src/main/docbook/modules/a4jUGevcp.xml
trunk/docs/userguide/en/src/main/docbook/modules/a4jUGfaq.xml
trunk/docs/userguide/en/src/main/docbook/modules/a4jUGskinnability.xml
trunk/docs/userguide/en/src/main/docbook/modules/a4jUGstart.xml
trunk/docs/userguide/en/src/main/docbook/modules/a4jUGtechreqs.xml
trunk/docs/userguide/en/src/main/docbook/modules/a4jUGusingAJAX.xml
Log:
Language mistakes correction
Modified: trunk/docs/userguide/en/src/main/docbook/modules/AUGWADParams.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/AUGWADParams.xml 2007-06-22 17:30:59 UTC (rev 277)
+++ trunk/docs/userguide/en/src/main/docbook/modules/AUGWADParams.xml 2007-06-25 12:30:04 UTC (rev 278)
@@ -30,7 +30,7 @@
<entry>org.ajax4jsf.LOGFILE</entry>
<entry>none</entry>
<entry>
- Is an URL to an application or a container log file (if possible). If this parameter is set, content from the given URL will be shown on a <emphasis role="italic"><property>Debug</property></emphasis> error page in the <emphasis role="italic"><property>iframe</property></emphasis> window
+ The is an URL to an application or a container log file (if possible). If this parameter is set, a content from the given URL will be shown on a <emphasis role="italic"><property>Debug</property></emphasis> error page in the <emphasis role="italic"><property>iframe</property></emphasis> window
</entry>
</row>
<row>
@@ -39,7 +39,7 @@
<entry>
Is a comma-separated list of custom <emphasis role="italic"><property>"ViewHandler"</property></emphasis> instances
for inserting in chain. Handlers are inserted in the given order. So must be used if the order of them is important.
- No need to define ajax4jsf handler there - it will be always the first.
+ No need to define ajax4jsf handler there, as it will be always the first.
</entry>
</row>
<row>
@@ -53,7 +53,7 @@
<entry>org.ajax4jsf.ENCRYPT_RESOURCE_DATA</entry>
<entry>false</entry>
<entry>
- For generated resources, such as encrypt generation data, it's encoded in the resource URL. For example, URL for an image generated from the <emphasis role="italic"><property>mediaOutput</property></emphasis> component contains a name of a generation method, since for a hacker attack, it is possible to create a request for any JSF baked beans or other attributes. To prevent such attacks, set this parameter to "true" in critical applications (works with JRE > 1.4)
+ For generated resources, such as encrypt generation data, it's encoded in the resource URL. For example, URL for an image generated from the <emphasis role="italic"><property>mediaOutput</property></emphasis> component contains a name of a generation method, since for a hacker attack, it is possible to create a request for any JSF baked beans or other attributes. To prevent such attacks, set this parameter to true in critical applications (works with JRE > 1.4)
</entry>
</row>
<row>
@@ -107,7 +107,7 @@
<entry>forceparser</entry>
<entry>true</entry>
<entry>
- Forces parsing by a filter <emphasis role="italic"><property>HTML</property></emphasis> syntax checker on any JSF page. If "false", only AJAX responses are parsed to syntax check and conversion to well-formed XML. Setting to "false" improve performance, but can provide visual effects on AJAX updates
+ Forces parsing by a filter <emphasis role="italic"><property>HTML</property></emphasis> syntax checker on any JSF page. If false, only AJAX responses are parsed to syntax check and conversion to well-formed XML. Setting to false improve performance, but can provide visual effects on AJAX updates
</entry>
</row>
</tbody>
Modified: trunk/docs/userguide/en/src/main/docbook/modules/a4jUGenvsettings.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/a4jUGenvsettings.xml 2007-06-22 17:30:59 UTC (rev 277)
+++ trunk/docs/userguide/en/src/main/docbook/modules/a4jUGenvsettings.xml 2007-06-25 12:30:04 UTC (rev 278)
@@ -79,7 +79,7 @@
important job. </para>
<note>
<title>Note:</title>
- <para>In this case you don't have to define <property>FaceletViewHandler</property> in the
+ <para>In this case you don't have to define <property>FaceletViewHandler</property> in the
WEB-INF/faces-config.xml.</para>
</note>
</section>
@@ -190,6 +190,6 @@
</section>
<section id="Portlet Support">
<title>Portlet Support</title>
- <para><property>Portlets</property> have support since version Ajax4jsf 1.1.1. Provide your feedback on compatible with Ajax4jsf if you have problems.</para>
+ <para><property>Portlets</property> have support since version Ajax4jsf 1.1.1. Provide your feedback on compatible with Ajax4jsf if you face some problems.</para>
</section>
</chapter>
Modified: trunk/docs/userguide/en/src/main/docbook/modules/a4jUGevcp.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/a4jUGevcp.xml 2007-06-22 17:30:59 UTC (rev 277)
+++ trunk/docs/userguide/en/src/main/docbook/modules/a4jUGevcp.xml 2007-06-25 12:30:04 UTC (rev 278)
@@ -19,8 +19,8 @@
</para>
<formalpara>
<title>Compatibility</title>
- <para>Make sure that you are using <property>Rich Faces version 2.0</property> and
- higher, earlier versions contain built-in Ajax4jsf kernel and can't be used together
- with new Ajax4jsf versions. </para>
+ <para>Make sure you are using <property>Rich Faces version 2.0</property> and
+ higher, earlier versions contain built-in Ajax4jsf kernel and can't be used together
+ with new Ajax4jsf versions.</para>
</formalpara>
</chapter>
Modified: trunk/docs/userguide/en/src/main/docbook/modules/a4jUGfaq.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/a4jUGfaq.xml 2007-06-22 17:30:59 UTC (rev 277)
+++ trunk/docs/userguide/en/src/main/docbook/modules/a4jUGfaq.xml 2007-06-25 12:30:04 UTC (rev 278)
@@ -14,7 +14,7 @@
<title>FAQ</title>
<section id="DecidingWhatToChangeOnTheServerSide">
<?dbhtml filename="DecidingWhatToChangeOnTheServerSide.html"?>
- <title>Deciding what to change on the server side</title>
+ <title>What should I change on the server side</title>
<para>
As it was mentioned <ulink url="index.html#DecideWhatToChange">before</ulink>, the list of zones to be reRendered can be specified
as EL expression. But there is a question that must be specified more exactly.
@@ -31,7 +31,7 @@
<section id="CheckSendingRequestConditions.CustomJavaScriptBeforeRequest.OnSubmitAttribute">
<?dbhtml filename="CheckSendingRequestConditions.CustomJavaScriptBeforeRequest.OnSubmitAttribute.html"?>
- <title>Check sending request conditions. Custom JavaScript before request. OnSubmit attribute</title>
+ <title>How to check sending request conditions? Custom JavaScript before request. OnSubmit attribute</title>
<para>
To check on the client some terms of request sending, The <emphasis role="italic">
<property>"onSubmit</property>
@@ -112,7 +112,7 @@
</section>
<section id="InvokeOnComponentUsingWithJSF1.2">
<?dbhtml filename="InvokeOnComponentUsingWithJSF1.2.html"?>
- <title>InvokeOnComponent using with JSF 1.2</title>
+ <title>Is it possible to use InvokeOnComponent with JSF 1.2?</title>
<para>
Ajax4jsf currently does not use <emphasis role="italic">invokeOnComponent</emphasis> because of the 2 reasons:
</para>
@@ -147,7 +147,7 @@
</section>
<section id="FilterUsageDamagesAnApplicationLayout">
<?dbhtml filename="FilterUsageDamagesAnApplicationLayout.html"?>
- <title>Filter usage damages an application layout</title>
+ <title>Why does filter usage damage an application layout?</title>
<para>Ajax4jsf uses <property>filters</property> for correction of xhtml code received on an AJAX response,
because when a response is recieved from the server, Ajax4jsf makes direct changes in
DOM tree and browser doesn't make any corrections in generated xhtml. There
@@ -233,7 +233,7 @@
<section id="IgnoreDupResponsesAndRequestDelay">
<?dbhtml filename="IgnoreDupResponsesAndRequestDelay.html"?>
- <title>IgnoreDupResponses and requestDelay </title>
+ <title>How to use IgnoreDupResponses and requestDelay </title>
<para>The <emphasis role="italic">
<property>"IgnoreDupResponses"</property>
</emphasis> attribute appeared from 1.0.4 RC1 version and is used on the
@@ -254,7 +254,7 @@
<section id="RefreshImage">
<?dbhtml filename="RefreshImage.html"?>
- <title>Unable to refresh an image using "a4j:support"</title>
+ <title>How to refresh an image using "a4j:support"</title>
<para>For information see discussion about this problem on the <ulink url="http://jboss.com/index.html?module=bb&op=viewtopic&t=105995">Ajax4Jsf Users Forum.
</ulink>
</para>
@@ -264,7 +264,7 @@
<section id="EventQueueUsage">
<?dbhtml filename="EventQueueUsage.html"?>
- <title>EventQueue usage</title>
+ <title>How to use EventQueue</title>
<para>The <emphasis role="italic">
<property>"EventQueue"</property>
</emphasis> attribute defines the query name where the requests are saved
@@ -290,7 +290,7 @@
<section id="SeveralStatusOnPage">
<?dbhtml filename="SeveralStatusOnPage.html"?>
- <title>Can I have several "a4j:status" component on one page?</title>
+ <title>Can I have several "a4j:status" components on one page?</title>
<para>Yes, you can. For more information see example on
<ulink url="http://livedemo.exadel.com/a4j-status/">JBoss Ajax4jsf Online Demos</ulink>.
</para>
@@ -361,15 +361,15 @@
<section id="JSCallPropblemsInInclude">
<?dbhtml filename="JSCallPropblemsInInclude.html"?>
- <title>JavaScript call not work in "a4j:include"</title>
- <para>For information see discussion about this problem on the <ulink url="http://jboss.com/index.html?module=bb&op=viewtopic&t=104317">Ajax4Jsf Users Forum.
+ <title>Why does JavaScript call don't work in "a4j:include"?</title>
+ <para>For more information see discussion on this problem on the <ulink url="http://jboss.com/index.html?module=bb&op=viewtopic&t=104317">Ajax4Jsf Users Forum.
</ulink>
</para>
</section>
<section id="ResourceNotRegisteredException">
<?dbhtml filename="ResourceNotRegisteredException.html"?>
- <title>ResourceNotRegistered Exception</title>
+ <title>What does ResourceNotRegistered Exception mean?</title>
<para>Ajax4jsf registers its resources (scripts, images) after an application is accessed and then accesses it via a generated URL. During an application development when a developer constantly updates it on the server, it could happen that Ajax4jsf re-registers its resources after every server restart and a browser tries to access them via cashed URL.</para>
Modified: trunk/docs/userguide/en/src/main/docbook/modules/a4jUGskinnability.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/a4jUGskinnability.xml 2007-06-22 17:30:59 UTC (rev 277)
+++ trunk/docs/userguide/en/src/main/docbook/modules/a4jUGskinnability.xml 2007-06-25 12:30:04 UTC (rev 278)
@@ -14,7 +14,7 @@
<title>Built-in skinnability in Ajax4jsf</title>
<para>Ajax4jsf gives an opportunity to incorporate <property>skinnability</property> into UI
- design. With this framework you can easily use named skin parameters in
+ design. With this framework you can easily use named skin parameters in
properties files to control the appearance of the skins that are applied
consistently to a whole set of components. You can look at examples of
predefined skins at:</para>
@@ -25,7 +25,7 @@
</simplelist>
<para>
You may simply control the look-and-feel of your application by using the <property>skinnability</property> service
- of the Ajax4jsf framework. With the means of this service you can define the same style for rendering
+ of the Ajax4jsf framework. With the means of this service you can define the same style for rendering
standard JSF components and custom JSF components built with the help of Ajax4jsf.
</para>
<para>To find out more on <property>skinnability</property> possibilities, follow these
@@ -53,8 +53,8 @@
</renderer>]]></programlisting>
</listitem>
<listitem>
- Finally, you need to place a properties file with skin parameters
- into the class path root. There are two requirements for the properties
+ Finally, you need to place a properties file with skin parameters
+ into the class path root. There are two requirements for the properties
file:
<itemizedlist>
<listitem>
Modified: trunk/docs/userguide/en/src/main/docbook/modules/a4jUGstart.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/a4jUGstart.xml 2007-06-22 17:30:59 UTC (rev 277)
+++ trunk/docs/userguide/en/src/main/docbook/modules/a4jUGstart.xml 2007-06-25 12:30:04 UTC (rev 278)
@@ -78,7 +78,7 @@
</listitem>
<listitem>
- <para>Add the following line to each JSP page of your application where you are going to bring in AJAX functionality.</para>
+ <para>Add the following line for each JSP page of your application where you are going to bring in AJAX functionality.</para>
<programlisting role="XML"> <![CDATA[<%@ taglib uri="https://ajax4jsf.dev.java.net/ajax" prefix="a4j"%>]]></programlisting>
<para>For XHTML pages:</para>
<programlisting role="XML"><xmlns:a4j="https://ajax4jsf.dev.java.net/ajax"></programlisting>
@@ -249,8 +249,6 @@
your browser at
<ulink url="http://localhost:8080/a4jEchoText/echo.jsf">http://localhost:8080/a4jEchoText/echo.jsf</ulink>
</para>
-
-
</section>
</section>
</chapter>
Modified: trunk/docs/userguide/en/src/main/docbook/modules/a4jUGtechreqs.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/a4jUGtechreqs.xml 2007-06-22 17:30:59 UTC (rev 277)
+++ trunk/docs/userguide/en/src/main/docbook/modules/a4jUGtechreqs.xml 2007-06-25 12:30:04 UTC (rev 278)
@@ -108,7 +108,7 @@
Conqueror 3 and higher
</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't mean incompatibility.</para>
<para>We appreciate your feedback on platforms and browsers that aren't in the list
but are compatible with Ajax4jsf. It helps us to keep the list up-to-date.</para>
</section>
Modified: trunk/docs/userguide/en/src/main/docbook/modules/a4jUGusingAJAX.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/modules/a4jUGusingAJAX.xml 2007-06-22 17:30:59 UTC (rev 277)
+++ trunk/docs/userguide/en/src/main/docbook/modules/a4jUGusingAJAX.xml 2007-06-25 12:30:04 UTC (rev 278)
@@ -139,7 +139,7 @@
<property><a4j:support></property>
</emphasis> tags.
</para>
- <para>All these tags hide the usual JavaScript activities that are required for an XMHttpRequest
+ <para>All these tags hide the usual JavaScript activities that are required for an XMHttpRequest
object building and an AJAX request sending. Also, they allow you to decide which components of
your JSF page are to be re-rendered as a result of the AJAX response (you can list the
IDs of these components in the "reRender" attribute).
@@ -189,12 +189,12 @@
<listitem>
<emphasis role="italic">
<property>"EventsQueue"</property>
- </emphasis> is a queue that stores the next request.
+ </emphasis> is a queue that stores the next request.
</listitem>
<listitem>
<emphasis role="italic">
<property>"LimitToList"</property>
- </emphasis> attribute is used for regulate updatable regions. Setting
+ </emphasis> attribute is used to regulate updatable regions. Setting
it to true limits the updatable areas only to ones specified in a
reRender list, in other case all Output Panels of the region are updated.
</listitem>
More information about the ajax4jsf-svn-commits
mailing list