[jboss-cvs] JBossAS SVN: r97668 - in projects/docs/enterprise/5.0/RichFaces: de-DE and 5 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Dec 10 00:41:48 EST 2009
Author: xhuang at jboss.com
Date: 2009-12-10 00:41:45 -0500 (Thu, 10 Dec 2009)
New Revision: 97668
Added:
projects/docs/enterprise/5.0/RichFaces/de-DE/
projects/docs/enterprise/5.0/RichFaces/de-DE/Architecture_Overview.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Author_Group.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Book_Info.po
projects/docs/enterprise/5.0/RichFaces/de-DE/FAQ.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Getting_Started.po
projects/docs/enterprise/5.0/RichFaces/de-DE/IDE_Support.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Introduction.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Links_to_Resources.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Revision_History.po
projects/docs/enterprise/5.0/RichFaces/de-DE/RichFaces_Developer_Guide.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Settings.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Technical_Requirements.po
projects/docs/enterprise/5.0/RichFaces/es-ES/
projects/docs/enterprise/5.0/RichFaces/es-ES/Architecture_Overview.po
projects/docs/enterprise/5.0/RichFaces/es-ES/Author_Group.po
projects/docs/enterprise/5.0/RichFaces/es-ES/Book_Info.po
projects/docs/enterprise/5.0/RichFaces/es-ES/FAQ.po
projects/docs/enterprise/5.0/RichFaces/es-ES/Getting_Started.po
projects/docs/enterprise/5.0/RichFaces/es-ES/IDE_Support.po
projects/docs/enterprise/5.0/RichFaces/es-ES/Introduction.po
projects/docs/enterprise/5.0/RichFaces/es-ES/Links_to_Resources.po
projects/docs/enterprise/5.0/RichFaces/es-ES/Revision_History.po
projects/docs/enterprise/5.0/RichFaces/es-ES/RichFaces_Developer_Guide.po
projects/docs/enterprise/5.0/RichFaces/es-ES/Settings.po
projects/docs/enterprise/5.0/RichFaces/es-ES/Technical_Requirements.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/
projects/docs/enterprise/5.0/RichFaces/fr-FR/Architecture_Overview.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/Author_Group.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/Book_Info.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/FAQ.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/Getting_Started.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/IDE_Support.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/Introduction.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/Links_to_Resources.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/Revision_History.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/RichFaces_Developer_Guide.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/Settings.po
projects/docs/enterprise/5.0/RichFaces/fr-FR/Technical_Requirements.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/
projects/docs/enterprise/5.0/RichFaces/ja-JP/Architecture_Overview.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/Author_Group.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/Book_Info.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/FAQ.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/Getting_Started.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/IDE_Support.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/Introduction.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/Links_to_Resources.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/Revision_History.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/RichFaces_Developer_Guide.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/Settings.po
projects/docs/enterprise/5.0/RichFaces/ja-JP/Technical_Requirements.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/
projects/docs/enterprise/5.0/RichFaces/pt-BR/Architecture_Overview.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/Author_Group.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/Book_Info.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/FAQ.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/Getting_Started.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/IDE_Support.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/Introduction.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/Links_to_Resources.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/Revision_History.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/RichFaces_Developer_Guide.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/Settings.po
projects/docs/enterprise/5.0/RichFaces/pt-BR/Technical_Requirements.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/
projects/docs/enterprise/5.0/RichFaces/zh-CN/Architecture_Overview.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/Author_Group.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/Book_Info.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/FAQ.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/Getting_Started.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/IDE_Support.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/Introduction.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/Links_to_Resources.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/Revision_History.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/RichFaces_Developer_Guide.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/Settings.po
projects/docs/enterprise/5.0/RichFaces/zh-CN/Technical_Requirements.po
Log:
update po by publican 1.0
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/Architecture_Overview.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Architecture_Overview.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Architecture_Overview.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,1829 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Basic concepts of the RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces Framework is implemented as a component library that adds AJAX capabilities into existing pages. This means that you do not need to write any JavaScript code or replace existing components with new AJAX widgets. RichFaces enables page-wide AJAX support instead of the traditional component-wide support, so you can define areas of the page that will reflect changes made by AJAX events on the client."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram following shows the process in full:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Processing flow"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you use JSF tags to define sections of a JSF page that you wish to update with the results of an AJAX request. It also provides you with several options for sending AJAX requests to the server. You do not need to write any JavaScript or <literal>XMLHTTPRequest</literal> objects by hand — everything is done automatically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Architecture Overview"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following figure lists several important elements of the RichFaces Framework."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Core AJAX component structure"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Filter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To make the most of RichFaces, you should register a <literal>Filter</literal> in your application's <filename>web.xml</filename>. The <literal>Filter</literal> recognizes multiple request types. The sequence diagram in Figure 5.3 shows the differences in processing between a <emphasis>regular</emphasis> JSF request and an AJAX request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request processing sequence diagram"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In either case, the required static or dynamic resource information that your application requests is registered in the <literal>ResourceBuilder</literal> class."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When a resource request is issued, the RichFaces filter checks the <literal>Resource Cache</literal> for this resource. If it is present, the resource is returned to the client. Otherwise, the filter searches for the resource among those registered in the <literal>ResourceBuilder</literal>. If the resource is registered, the RichFaces filter requests that the <literal>ResourceBuilder</literal> creates (delivers) the resource."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram that follows illustrates the process of requesting a resource."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Resource request sequence diagram"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Action Components"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "AJAX Action components are used to send AJAX requests from the client side. There are a number of AJAX Action components, including <literal><a4j:commandButton></literal>, <literal><a4j:commandLink></literal>, <literal><a4j:poll></literal>, and <literal><a4j:support></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Containers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>AjaxContainer</literal> is an interface that defines an area on your JSF page that should be decoded during an AJAX request. <literal>AjaxViewRoot</literal> and <literal>AjaxRegion</literal> are both implementations of this interface."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JavaScript Engine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces JavaScript Engine runs on the client side, and updates different areas of your JSF page based on information from the AJAX response. This JavaScript code operates automatically, so there is no need to use it directly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors and Session Expiration Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you redefine the standard handlers responsible for processing exceptions. We recommend defining your own JavaScript, which will be executed when exceptional situations occur."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To execute your own code on the client in the event of an error during an AJAX request, you must redefine the standard <literal>A4J.AJAX.onError</literal> method like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function accepts the following as parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>req</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a parameter string of a request that calls an error"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>status</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the number of an error returned by the server"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>message</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for the given error"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, you can create your own handler that is called when timeouts, internal server errors, etc. occur."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Session Expired Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also redefine the <literal>onExpired</literal> framework method that is called on the <literal>SessionExpiration</literal> event."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Example:</emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function can take the following parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>loc</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the URL of the current page (can be updated on demand)"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>expiredMsg</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for display in the event of <literal>SessionExpiration</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customized <literal>onExpire</literal> handlers do not work under MyFaces. MyFaces handles exceptions by internally generating a debug page. To prevent this behavior, use the following:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skinnability"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you look at any CSS (Cascading Style Sheets) file in an enterprise application, you will notice how often the same color is noted. Standard CSS cannot define a particular colour abstractly as a panel header color, the background color of an active pop-up menu item, a separator color, etc. To define common interface styles, you must copy the same value multiple times, and the more interfaces you have, the more repetition is required."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, if you want to change the palette of an application, you must change all interrelating values, or your interface can appear clumsy. If a customer wants to be able to adjust their interface's look and feel in real time, you must be able to alter several CSS files, each of which will contain the same value multiple times."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve these problems with the <emphasis>skins</emphasis> that are built into and rully implemented in RichFaces. Every named skin has <emphasis>skin parameters</emphasis> that define a palette and other attributes of the user interface. By changing a few skin parameters, you can alter the appearance of dozens of components simultaneously, without interfering with interface consistency."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinnability</literal> feature cannot completely replace standard CSS, and does not eliminate its usage. Instead, it is a high-level extension of standard CSS that can be used in combination with regular CSS declarations. You can also refer to skin parameters in CSS through the JSF Expression Language. This lets you completely synchronize the appearance of all elements in your pages."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Using Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces <emphasis>skinnability</emphasis> is designed for use alongside:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "skin parameters defined in the RichFaces framework,"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "predefined CSS classes for components, and"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "user style classes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A component's color scheme can be applied to its elements using any of three style classes:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A default style class inserted into the framework"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This contains stle parameters that are linked to some constants from a skin. It is defined for every component and specifies a default level of representation. You can modify an application interface by changing the values of the skin parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A style class of skin extension"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This class name is defined for every component element, and inserted into the framework to let you define a class with the same name in your CSS files. This lets you easily extend the appearance of all components that use this class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "User style class"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use one of the <literal>styleClass</literal> parameters to define your own class for component elements. As a result, the appearance of one particular component is changed according to a CSS style parameter specified in the class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Example"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following is an example of a simple <emphasis>panel</emphasis> component:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This code generates a panel component on a page, which consists of two elements: a wrapper <literal><div></literal> element and a <literal><div></literal> element for the panel body with the specified style properties. The wrapper <literal><div></literal> element will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>dr-pnl</literal> is a CSS class that is specified in the framework via skin parameters:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>background-color</varname> is defined with <literal>generalBackgroundColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>border-color</varname> is defined with <literal>panelBorderColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change all colors for all panels on all pages by changing these skin parameter values. However, if you specify a <literal><rich:panel></literal> class on the page, its parameters are also acquired by all panels on this page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Developers can also change the style properties for panel. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous definition could add some style properties from <literal>customClass</literal> to one particular panel. As a result, we will get three styles:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skin Parameters Tables in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces provides eight predefined skin parameters (skins) at the simplest level of common customization:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "plain"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "emeraldTown"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "blueSky"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "wine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "japanCherry"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ruby"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "classic"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "deepMarine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To apply a skin, you must specify a skin name in the <varname>org.richfaces.SKIN</varname> context parameter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following table shows the values for each parameter in the <literal>blueSky</literal> skin:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Colors"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Parameter name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#BED6F8"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerGradientColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#F2F7FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#000000"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerWeightFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bold"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FFFFFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "11px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Arial, Verdana, sans-serif"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "additionalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#ECF4FE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowOpacity"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "panelBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "subBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C6DEFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabDisabledTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#8DB7F3"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "trimColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#D6E6FB"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FAE6B0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E5973E"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "selectControlColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E79A00"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0078D0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0090FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "visitedLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Fonts"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableFooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#cccccc"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableSubfooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#f1f1f1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C0C0C0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>plain</literal> skin was added in version 3.0.2. It has no parameters, and is important when embedding RichFaces components into existing projects with their own styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Creating and Using Your Own Skin File"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To create your own skin file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a file. In it, define skin constants to be used by style classes (see <xref linkend=\"SkinParametersTablesInRichFaces\" />). The name of the skin file should follow this format: <literal><name>.skin.properties</literal>. (For examples of this file, see the RichFaces predefined skin parameters: <literal>blueSky</literal>, <literal>classic</literal>, <literal>deepMarine</literal>, etc. These files are located in the <filename>richfaces-impl-xxxxx.jar</filename> archive in the <filename>/META-INF/skins</filename> folder."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the skin definition <literal><contex-param></literal> to the <filename>web.xml</filename> of your application, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place your <literal><name>.skin.properties</literal> file in either your <filename>/META-INF/skins</filename> or <filename>/WEB-INF/classes</filename> directory."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Built-in Skinnability in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you incorporate skins into your user interface (UI) design. This framework lets you use named skin parameters in your properties files to control skin appearance consistently across a set of components. You can see examples of predefined skins at: <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">http://livedemo.exadel.com/richfaces-demo/ </ulink>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Skins let you define a style in which to render standard JSF components and custom JSF components built with RichFaces. You can experiment with skins by following these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a custom render kit and register it in the <filename>faces-config.xml</filename> like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, create and register custom renderers for the component based on the look-and-feel predefined variables:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, place a properties file with skin parameters into the class path root. There are two requirements for the properties file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The file must be named <filename><replaceable>skinName</replaceable>.skin.properties</filename>. In this case, we would call it <literal>newskin.skin.properties</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The first line in this file should be <literal>render.kit=<replaceable>render-kit-id</replaceable></literal>. In this case, we would use <literal>render.kit=NEW_SKIN</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "More information about creating custom renderers can be found at: <ulink url=\"http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html\">http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Changing skin in runtime"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change skins during runtime by defining the following EL-expression in your <filename>web.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinBean</literal> code looks like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also set the <varname>skin</varname> property's initial value in the configuration file. To set <literal>classic</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also change the properties of the default skin. To do so, edit the properties of the default skin. The following shows you example page code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The above code will generate the following list of options:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Controls Skinning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This feature is designed to unify the look and feel of standard HTML elements and RichFaces components. Skinning can be applied to all controls on a page based on element names and attribute types (where applicable). This feature also provides a set of CSS styles that let skins be applied by assigning <literal>rich-*</literal> classes to particular elements, or to a container of elements that nests controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard Controls Skinning provides two levels of skinning: <emphasis>Basic</emphasis> and <emphasis>Extended</emphasis>. The level used depends on the browser type detected. If the browser type cannot be detected, <literal>Extended</literal> is used. However, if you want to explicitly specify the level to be applied, add a <varname></varname> context parameter to your <filename>web.xml</filename> and set the value to either <literal>basic</literal> or <literal>extended</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Basic</emphasis> level provides customization for only basic style properties. Basic skinning is applied to the following browsers:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in BackCompat mode (see <ulink url=\"http://msdn2.microsoft.com/en-us/library/ms533687(VS.85).aspx\">document.compatMode property in MSDN</ulink>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Extended</emphasis> level introduces a broader number of style properties on top of basic skinning, and is applied to browsers with rich visual styling control capabilities. The following browsers support Extended skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Mozilla Firefox"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in Standards-compliant mode (CSS1Compat mode)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following elements can be modified with skins:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>input</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>select</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>textarea</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>keygen</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>isindex</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>legend</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>fieldset</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>hr</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>a</literal> (together with the <literal>a:hover</literal>, <literal>a:visited</literal> pseudo-elements)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two ways to initialize skinning for standard HTML controls:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. This method implies that skinning style properties are applied per-element and attribute type (where applicable). No additional steps are required. See the <xref linkend=\"BasicLevel\" /> and <xref linkend=\"ExtendedLevel\" /> tables for elements to which skinning can be applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. When enabled, you are provided with a set of predefined CSS classes to apply skins to your HTML components."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enabling <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> provides you style classes that can be applied to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "basic elements nested within elements with a <emphasis>rich-container</emphasis> class. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements with a class name that corresponds to one of the basic element names or types are mapped with the <literal>rich-<elementName>[-<elementType>]</literal> scheme, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements are given classes depending upon their <literal>link</literal> type and pseudo-class name, for example, <literal>rich-link</literal>, <literal>rich-link-hover</literal>, <literal>rich-link-visited</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The predefined rich CSS classes provided can be used as classes for both basic and complex HTML elements."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code snippet shows several elements as an example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more thorough look at standard component skinning, we recommend exploring the CSS files located in the <filename>ui/core/src/main/resources/org/richfaces/</filename> directory of the RichFaces SVN repository."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex and legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "CSS Properties"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-size"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-family"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for hr"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:hover"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColorgeneralLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Elements Skin Bindings for .rich-input, .rich-select, .rich-textarea, .rich-keygen, .rich-isindex, .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-fieldset"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-hr"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-width"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-style"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "solid"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:hover"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin parameters/Value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "inset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-color"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "no-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-position"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px 1px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-edit"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "editBackgroundColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-error"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "warningBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding-left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "7px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button, .rich-button-disabled, .rich-button-over"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "2px 10px 2px 10px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "text-align"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "cursor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "pointer"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "repeat-x"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "top left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button-press"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bottom left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-container fieldset, .rich-fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "10px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-weight"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-form"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "0px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "margin"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Extended level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-image"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for button[type=button], button[type=reset], button[type=submit], input[type=reset], input[type=submit], input[type=button]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button[disabled], .rich-container *|button[disabled], .rich-button-disabled"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonDisabledBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for .rich-button-disabled, .rich-container button[type=\"button\"][disabled], .rich-button-button-disabled, .rich-container button[type=\"reset\"][disabled], .rich-button-reset-disabled, .rich-container button[type=\"submit\"][disabled], .rich-button-submit-disabled, .rich-container input[type=\"reset\"][disabled], .rich-input-reset-disabled, .rich-container input[type=\"submit\"][disabled], .rich-input-submit-disabled, .rich-container input[type=\"button\"][disabled], .rich-input-button-disabled"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *button[type=\"button\"][disabled], button[type=\"reset\"][disabled], button[type=\"submit\"][disabled], input[type=\"reset\"][disabled], input[type=\"submit\"][disabled], input[type=\"button\"][disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.InputBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for textarea[type=textarea], input[type=text], input[type=password], select"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea[disabled], .rich-container *|textarea[disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "textarea[type=\"textarea\"][disabled], input[type=\"text\"][disabled], input[type=\"password\"][disabled]"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The basic skinning level can fail if the <literal>ajaxPortlet</literal> is configured as follows:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Client-side Script for Extended Skinning Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Extended skinning of standard HTML controls is applied automatically: the browser type is detected, and if a browser does not fully support extended skinning, only basic skinning is applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are some problems with standard HTML controls in certain browsers (Opera and Safari) that may cause problems if you wish to skin your RichFaces components and standard HTML controls manually."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable skinnability, set the <varname>org.richfaces.LoadStyleStrategy</varname> parameter to <literal>NONE</literal> in your <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You should also include the style sheets that apply skins to RichFaces components and standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To work around the problem of extended skinning in Opera and Safari, the <filename>skinning.js</filename> client script is added to the RichFaces library. This detects the browser type and enables extended skinning only for browsers that fully support it."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Activate the script by inserting the following JavaScript into your page:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When no script-loading strategy is used and extended skinning is enabled, a warning message appears in the console."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also specify the <varname>media</varname> attribute in the <literal>link</literal> tag. This adds the <filename>extended_both.xcss</filename> style sheet to <literal>rich-extended-skinning</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include your style sheets to the page when automatic skinnability is disabled, add the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Base64 encoder now uses <literal>!</literal> instead of <literal>.</literal>, so remember to use the <literal>a4j/versionXXX</literal> resources prefix instead of <literal>a4j_versionXXX</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "XCSS File Format"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Cross-site Cascading Style Sheet (XCSS) files are the core of RichFaces component skinnability. XCSS is XML-formatted CSS that extends the skinning process. RichFaces parses the XCSS file containing all look and feel parameters of a particular component and compiles the information into a standard CSS file that can be recognized by a web browser."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The XCSS file contains CSS properties and skin parameter mappings. Mapping a CSS selector to a skin parameter can be done with <literal>< u:selector ></literal> and <literal>< u:style></literal> XML tags, which define the mapping structure, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "During processing, this code will be parsed and assembled into a standard CSS format, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>name</varname> attribute of <literal><u:selector></literal> defines the CSS selector, while the <varname>name</varname> attribute of the <literal><u:style></literal> tag defines the skin constant that is mapped to a CSS property. You can also use the <varname>value</varname> attribute of the <literal><u:style></literal> tag to assign a value to a CSS property."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "CSS selectors with identical skin properties can be included in a comma-separated list:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Plug-n-Skin</emphasis> lets you easily create, customize, and plug in a custom skin to your project. You can create skins based on the parameters of predefined RichFaces skins. Plug-n-Skin also lets you unify the appearance of rich controls with standard HTML elements. This section contains step-by-step instructions for creating your own skin with Plug-n-Skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, use Maven to create a template for your new skin. (You can find more information about configuring Maven for RichFaces in the <!-- #modify add info? --><ulink url=\"http://wiki.jboss.org/wiki/HowToConfigureMavenForRichFaces\">JBoss wiki article</ulink>. These Maven instructions can be copied and pasted into the command line interface to execute them."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Primary keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>archetypeVersion</varname> — indicates the RichFaces version; for example, <literal>3.3.1.GA</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>artifactId</varname> — the artifact ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>groupId</varname> — the group ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>version</varname> — the version of the project you create. By default, this is set to <literal>1.0.-SNAPSHOT</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This operation creates a directory named after your <literal>ARTIFACT-ID</literal>. The directory contains a template of the Maven project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following steps will guide you though creating of the skin itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Run the following command from the root directory of the Maven project. (This directory will contain your <filename>pom.xml</filename> file.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>name</varname> — defines the name of the new skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>package</varname> — the base package of the skin. By default, the project's <literal>groupId</literal> is used."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Additional optional keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — defines the name of the base skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>createExt</varname> — if set to <literal>true</literal>, extended CSS classes are added. For more information, please, see <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once these operations are complete, the following files and folders should have been created:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImage.java</filename> — the base class used to store images. Location: <filename>\\src\\main\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImageTest.java</filename> — a test version of a class that stores images. Location: <filename>\\src\\test\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>XCSS files</filename> — XCSS files define the new look of RichFaces components affected by the new skin. Location: \"\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.properties</filename> — a file that contains the new skin's properties. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following properties are used to configure the <filename>SKIN-NAME.properties</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — the name of the skin to be used as a basis for your own skin. The look of the skin you define will be affected by the new style properties."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>generalStyleSheet</varname> — a path to the style sheet (<filename>SKIN-NAME.xcss</filename>) that imports your component's style sheets to be modified by the new skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>extendedStyleSheet</varname> — the path to a style sheet that is used to unify the appearance of RichFaces components and standard HTML controls. For additional information, read <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>gradientType</varname> — a predefined property to set the type of gradient applied to the new skin. Possible values are <literal>glass</literal>, <literal>plastic</literal>, <literal>plain</literal>. More information on gradient implementation you can find further in this chapter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.xcss</filename> — an XCSS file that imports the component's XCSS files to be modified by the new skin. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>XCSS files</literal> — creates the XCSS files that determine styles for standard controls (<filename>extended_classes.xcss</filename> and <filename>extended.xcss</filename>), if the <varname>createExt</varname> key is set to <literal>true</literal>. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-ext.xcss</filename> — creates the <filename>SKIN-NAME-ext.xcss</filename> file that imports defining styles for standard controls if <varname>createExt</varname> is set to <literal>true</literal>. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-resources.xml</filename> — contains descriptions of all files listed previously. Location: <filename>src\\main\\config\\resources</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now start editing the XCSS files located in <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>. Assign new style properties to your selectors (listed in the XCSS files) in either of the following ways:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard CSS coding approach (that is, add CSS properties to the selectors). Remember that the selectors must be within <literal><f:verbatim> </f:verbatim></literal> tags. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "XCSS coding approach (the usual method of creating XCSS files in RichFaces). XCSS tags must be placed <emphasis>outside</emphasis> <literal><f:verbatim> </f:verbatim></literal> tags."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once you have performed these steps and edited the XCSS files, build the new skin and plug it into the project. To build the skin, execute the following command from the root directory of your skin project (the directory that contains your <filename>pom.xml</filename> file):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Plug-n-skin feature also has a number of predefined gradients. The following code can be used to apply a gradient:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>background-image</varname> CSS property is defined with <literal><f:resource f:key=\"org.richfaces.renderkit.html.CustomizeableGradient\"></literal>, which sets the gradient. The gradient type can be specified in the <filename>SKIN-NAME.properties</filename> with the <varname>gradientType</varname> property, which can be set to <literal>glass</literal>, <literal>plastic</literal>, or <literal>plain</literal>. The gradient can then be adjusted with the <varname>baseColor</varname>, <varname>gradientColor</varname>, <varname>gradientHeight</varname>, <varname>valign</varname> attributes, as seen in the previous code snippet."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now use your newly-created skin in your project by adding your new skin parameters to the <filename>web.xml</filename> file, and placing the JAR file containing your skin (located in the <filename>target</filename> directory of your skin project) in the <filename>\\WebContent\\WEB-INF\\lib\\</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Details of Usage"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This section covers some practical aspects of Plug-n-Skin implementation. We assume that you have read the section of the guide describing the Plug-n-Skin prototype creation process."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, we must create a new skin (as described in the previous section). The following creates a template of the new skin project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now browse the <filename>P-n-S</filename> directory to view the files and folders created."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use Maven to add all required files to the skin project, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As mentioned in the previous section, <!-- #modify '-D' typo? --><literal>-DbaseSkin</literal> defines the RichFaces built-in skin to use as a base, and <literal>-DcreateExt=true</literal>, which determines that the new skin will include XCSS files that unify the appearance of the rich components and the standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once your resources have been created, you can begin refining the newly-created skin. Begin by editing the rich components' XCSS files."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example of the Plug-n-Skin feature, we will edit some <literal><rich:calendar></literal> style attributes and some basic HTML controls. We will show you how to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor the background of the current day in the <literal><rich:calendar></literal>;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor a standard HTML submit button;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To edit <literal><rich:properties></literal>'s style properties, you must open the <filename>calendar.xcss</filename> file, located in <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the <filename>calendar.xcss</filename> file, find the <literal>.rich-calendar-today</literal> selector and amend it as follows:<literal>background-color: #075ad1;</literal>. This will change the background color of the current day."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next we will change the font style of a standard HTML <emphasis>submit</emphasis> button. Open the <filename>extended.xcss</filename> file from the <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename> directory and insert <literal>font-weight: bold;</literal> between the curly braces of these selectors, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The desired changes have now been made, and you can proceed to building the new <literal>PlugnSkinDemo</literal> skin and importing it into the project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Build the skin by executing <command>mvn clean install</command> from the <filename>P-n-S</filename> directory. This creates a <filename>target</filename> directory containing a JAR file with a newly-compiled skin. In our case, the file is named <filename>P-n-S-1.0.-SNAPSHOT.jar</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, import the new <literal>PlugnSkinDemo</literal> skin into your project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Copy the <filename>P-n-S-1.0.-SNAPSHOT.jar</filename> file to the <filename>\\WebContent\\WEB-INF\\lib\\</filename> directory."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the name of the new skin to the <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember, standard controls skinning must be enabled in <filename>web.xml</filename>. Add the following to enable standard controls skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The results of each alteration to the skin are shown in the figures that follow:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin feature in action."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "State Manager API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JSF has an advanced navigation mechanism that lets you define <emphasis>navigation</emphasis> from view to view. In a web application, navigation occurs when a user changes from one page to another by clicking on a button, a hyperlink, or another command component. There is no switch mechanism between some logical states of the same view. For example, in <emphasis>Login/Register dialog</emphasis>, an existing user signs in with his user name and password, but if a new user attempts to register, an additional field (<literal>Confirm</literal>) is displayed, and button labels and methods are changed when the user clicks the <guilabel>To register</guilabel> link:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Login Dialog"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Register Dialog"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>RichFaces State API</emphasis> lets you easily define a set of states for pages, and properties for these states."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>States</varname> class interfaces with a <property>map</property>, where the <methodname>keySet</methodname> defines the State name and the <methodname>entrySet</methodname> is a <varname>State</varname> <property>map</property>. The <varname>State</varname> <property>map</property> defines the properties, method bindings, or constant state variables of a key or object, where these values may change depending on the active State."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces State API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One of the most convenient features of the RichFaces State API is the ability to navigate between <varname>State</varname>s. The API implements changes in <varname>State</varname> through standard JSF navigation. When the action component returns an outcome, the JSF navigation handler (extended through the RichFaces State API) checks whether the outcome is registered as a <emphasis><varname>State</varname> change outcome</emphasis>. If <literal>true</literal>, the corresponding <varname>State</varname> is activated. If <literal>false</literal>, standard navigation handling is called."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Implement the RichFaces State API like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register the State Navigation Handler and the EL Resolver in your <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register an additional application factory in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register two managed beans in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One bean (<literal>config</literal>) defines and stores <varname>State</varname> as seen in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second bean, with the <literal>org.richfaces.ui.model.States</literal> type (<literal>state</literal>), contains the managed property <property>states</property>, which is bound to the first <literal>config</literal> bean."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use <property>state</property> bindings on the page, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To see complete example of the Login/Register dialog, see the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/stateAPI.jsf?c=stateAPI\">RichFaces Live Demo</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Identifying User Roles"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces also lets you check whether the logged-in user belongs to a certain <property>user role</property> with the <literal>rich:isUserInRole(Object)</literal> function. This function takes a String or a comma-delineated list of Strings, a Collection, etc. as arguments and returns a Boolean value."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example, imagine that you need to render some controls only for administrators. To do so, create an administrator role (<literal>admin</literal>) in your <filename>web.xml</filename> file. Then implement authorization that assigns the <literal>admin</literal> role to the user that has logged in as an administrator. Once this has been done, you can use the <literal>rich:isUserInRole(Object)</literal> function with the <varname>rendered</varname> attribute of any component. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Here, only a logged-in user with an <literal>admin</literal> role can see the text editor, which will not be rendered for users with other roles."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/Author_Group.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Author_Group.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Author_Group.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/Book_Info.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Book_Info.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Book_Info.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Developer Guide"
+msgstr ""
+
+#. Tag: subtitle
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/FAQ.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/FAQ.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/FAQ.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,989 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "FAQ"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find additional information on RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most important links for RichFaces can be found <ulink url=\"http://jboss.com/index.html?module=bb&op=viewtopic&t=104575\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where are the binary/source distributions for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Distributions are available from the <ulink url=\"http://labs.jboss.com/jbossrichfaces/downloads/\">JBoss RichFaces Download area</ulink>. The source distribution is found in the <filename>richfaces-ui-3.3.0-src.zip</filename> file. The binary distribution is in the <filename>richfaces-ui-3.3.0-bin.zip</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I manually build a RichFaces snapshot?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This <ulink url=\"http://labs.jboss.com/wiki/HowToBuildRichFacesSnapshotManually\"> wiki article</ulink> takes you through the process."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I configure Maven for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, download and install Maven. (Follow the instructions at <ulink url=\"http://maven.apache.org/download.html\">http://maven.apache.org/download.html</ulink>.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Open the <filename><Maven-Root>/conf/settings.xml</filename> file and add the following to the <literal><profile></literal> section:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following to the <literal><activeProfiles></literal> section:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is the structure of RichFaces SVN repository?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can see the structure in the RichFaces Repository Structure Overview in <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">this Wiki article</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I build <literal>richfaces-samples</literal> applications?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "he <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">RichFaces Repository Structure Overview</ulink> describes how to build <literal>richfaces-samples</literal> applications in Eclipse."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find a demo for RichFaces components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Online demo applications that showcase RichFaces features are available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also find a nightly build (in the WAR format) <ulink url=\"http://maven.exadel.com/org/richfaces/samples/richfaces-demo/3.1.0-SNAPSHOT/\">here</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Source Code (SVN) can be found <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-demo/\">in the JBoss RichFaces SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What causes the \"Prototype.Browser() function cannot be found\" error in RichFaces 3.1.0, and how do I fix it?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Your application probably uses an older version of Prototype from Tomahawk 1.1.6. RichFaces 3.1.0 uses the latest Prototype (1.5.1.1). Upgrade your version of Prototype to solve this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does the RichFaces library contain the <literal><rich:dataTable></literal> component as well as the <literal><h:dataTable></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dataTable></literal> component lets you use skins to change the look and feel of your data tables. You can see an example of the difference between these components at the <ulink url=\"http://livedemo.exadel.com/richfaces-art-datatable/\">RichFaces dataTable LiveDemo page</ulink>, or see the source code in the <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-art-datatable/\">SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I organize wizards with the <literal><rich:modalPanel></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place the <literal><a4j:include></literal> tag inside the <literal><rich:modalPanel></literal> and perform navigation inside it, as in the following example below:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I stop <literal>modalPanel</literal> closing when validation fails?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two methods available to fix this problem. The first is simply to remove the <literal>windowclose()</literal> method from the <literal>modalPanel</literal>, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that when an error presents, the panel will simply do nothing rather than closing the window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second method assumes that you use Facelets. Add the following to your <filename>default.xhtml</filename> template:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This invisible form will be refreshed on every postback, and contains a hidden field that determines the maximum severity in the message queue. If you add the following function to your JavaScript:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method reads the value of the hidden field to determine whether the last postback to the server generated any errors. This means that the <literal><a4j:commandLink></literal> or <literal><a4j:commandButton></literal> that submits your form will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method lets you easily adjust the behaviour of any JavaScript code depending on whether an error is present. See the <ulink url=\"http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4061517\">JBoss RichFaces forum</ulink> post for more information and variations on this method."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "When I use <literal>suggestionbox</literal> inside the <literal>modalPanel</literal>, the suggestion list sits behind the <literal>modalPanel</literal> and I cannot see it. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You are using an old version of RichFaces. Upgrade to the latest version to fix this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Does RichFaces work with Facelets?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes. Full Facelets support is one of RichFaces' primary features. The main <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\"> demo</ulink> is a Facelets-based application."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I create a dynamic menu with the <literal><rich:dropDownMenu></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:dropDownMenu></literal> is a standard JSF component, so creating a menu dynamically from the JavaScript code is the same as for any other JSF component."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I customize the look of a <literal>datascroller</literal> (the forward/back buttons) and replace them with images?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can. The <literal>datascroller</literal> component provides two controller groups for switching:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Page numbers</emphasis> so that you can switch to a particular page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Fast-switching</emphasis> controls: <literal>first</literal>, <literal>last</literal>, <literal>next</literal>, <literal>previous</literal>, <literal>fastforward</literal> and <literal>fastrewind</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create fast-switching controls by adding a <literal>facet</literal> component with the corresponding name:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also create disabled states with facets There are also facets used to create the disabled states: <literal>first_disabled</literal>, <literal>last_disabled</literal>, <literal>next_disabled</literal>, <literal>previous_disabled</literal>, <literal>fastforward_disabled</literal>, <literal>fastrewind_disabled</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I place simple links inside a menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include a link to an external URL, use the following approach:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see a demonstration of the <literal><rich:dropDownMenu></literal> component at the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/dropDownMenu.jsf\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal>dropDownMenu</literal> as a context menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dropDownMenu></literal> is not designed for use as a <literal>contextMenu</literal>. A <literal><rich:contextMenu></literal> component is planned for development, but is not scheduled for any currently planned version."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass my own parameters during a <literal>modalPanel</literal> opening or closing?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass your parameters during modalPanel opening or closing like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass any of your own parameters, except for the standard <literal>modalPanel</literal> parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I add a simple link to the tree node?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following simple code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Is it possible to place tabs upright in the <literal>tabPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, it is not. Try using the <literal>togglePanel</literal> instead; toggle controls can be placed anywhere in the layout."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use a <literal>commandButton</literal> within the <literal>modalPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two important rules to follow when using <literal>modalPanel</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if <literal>modalPanel</literal> has form elements (input or command elements), it must have its own form."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if the <literal>modalPanel</literal> contains a form, it must not be included in a higher-level form."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I define the currently selected tab?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I retrieve the current value from the <literal>inputNumberSlider</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can retrieve the value with the following approach:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How to apply skins to the standard input components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The answer could be found <ulink url=\"http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103494\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I remove the table border and styles from the <literal>datascroller</literal> and show only links?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To do this, you must redefine your rich* classes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I expand/collapse tree nodes from code?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/ExpandCollapseTreeNodes\">This Wiki article</ulink> has some useful information about expanding and collapsing tree nodes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the JavaScript API?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I load the Scriptaculous library?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To load the whole Scriptaculous library shipped with RichFaces, use the <literal><a4j:loadScript></literal> tag:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This command lets you load an integrated version of the library that includes all existing Scriptaculous files, <emphasis>except</emphasis> <filename>unittest.js</filename>. If you do not want to load the whole library, but wish to load a specific file (for example, <filename>effect.js</filename>), use the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you load the whole library, you do not need to load a particular file."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid the problem with text wrapping in <literal><rich:tab></literal> in Internet Explorer 7?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The problem lies with a tab height bug in IE7. (Tab height is correct in Firefox and in IE6.) To work around the bug, you can change the doctype declaration from:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see the <ulink url=\"http://jira.jboss.com/jira/browse/RF-1011\">JIRA Issue</ulink> for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the status of the <literal><rich:effect></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:effect></literal> has several callback methods such as <literal>beforeStart</literal> and <literal>afterFinish</literal>, which can be used to save the status. You can also see the <ulink url=\"http://wiki.github.com/madrobby/scriptaculous/core-effects\">Scriptaculous Core Effects</ulink> page for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I send an additional parameter to the server with <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This example code gives you one method:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the example, the <literal>onselect</literal> event sends the selected value to the server. You can pass additional fields of the selected object (which do not belong to the <literal>fetchvalue</literal> attribute) in the same way."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I set the border of <literal><rich:dataTable></literal> to 0px?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your CSS file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I dynamically create a <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is a working example:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What should I change on the server side?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The list of zones to be rerendered can be specified as an EL expression. The list of IDs is formed during the <literal>RENDER_RESPONSE</literal> <emphasis>beforePhase</emphasis>, so you can point the <literal>reRender</literal> to the <classname>Set</classname>, and fill it during a tracking request to form a list of areas which can be dynamically updated."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I check request conditions before sending a request?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To check the terms of sending a request on a client, add the <literal>onSubmit</literal> attribute to all components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this example, the <literal>doSomething()</literal> function is executed before the AJAX request, and if the function returns <literal>false</literal>, the request is not fired."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The behavior of our <literal>onsubmit</literal> attribute differs slightly from the standard <literal>onsubmit</literal>. Do not return <literal>true</literal> if you want to fire the request: <code><xxx><a4j:support event=\"onclick\" onsubmit=\"return true;\"></code> becomes <code><xxx onclick=\"return true;A4J.Submit(.... );\" ></code> and standard event processing is fired instead of the request. Only return <literal>false</literal> if your conditions were not completed, or set actions to be performed without any returned response if you do need to fire the request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What were the changes to the <varname>onComplete</varname> attribute after version 1.0?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To avoid conflict with other JavaScript attributes, we have changed the placement of a function during a Javascript call. Rather than inserting attribute contents (<code>oncomplete:anotherFunction(this)</code>), we make the function anonymous (<code>oncomplete:function(){anotherFunction(this);}</code>) so that you can insert a <emphasis>chain</emphasis> of statements into an attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The change also means that the <literal>this</literal> keyword will point to a parameter map instead of a control element. You can use <code>document.findElementById()</code> to retrieve references to this parameter map after a request is processed. Pages updated with AJAX will then reference a control removed from a DOM tree."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you are certain that your element will not be updated, you can add <literal>onsubmit</literal> to your <literal><a4j:support></literal> tag (or <literal>onclick</literal> to your <literal><a4j:commandLink/Button></literal> tag) to place a reference to a known variable, like so: <code><a4j:commandLink onclick=\"var myControl=this;\" oncomplete=\"anotherFunction(myControl)\"/></code>)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The onComplete syntax now follows this form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>event</literal> is a variable defining the location in which the JavaScript event that fires the request will be placed. <literal>data</literal> is a variable containing the deserialized value of the <varname>data</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use InvokeOnComponent with JSF 1.2?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not use <literal>invokeOnComponent</literal> for two reasons:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To retain compatibility with JSF 1.1 and MyFaces applications, since these are often used in corporate applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>invokeOnComponent</literal> works well when used to communicate between a Widget and a backed component, or to update the content of a rendered component. However, there are some limitations for more complicated use-cases implemented in RichFaces, such as making update decisions with application logic."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that you must update whole components (for example, an entire <literal>dataTable</literal>), but all AJAX core action components in that component will work correctly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid generating exceptions for the <literal><a4j:keepAlive></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember: the component stores beans in a serialized view. Your bean should implement <literal>java.io.Serializable</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "My form will not submit, or, my setter is not called after an AJAX request. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This can occur because of conversion or validation errors at submission time. To verify this, place the following update message inside a form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:message></literal> component has built-in AJAX support, and can be combined with the <ulink url=\"http://www.jsfone.com/blog/max_katz/2008/07/creating_jsf_phase_listener.html\">JSF Phase Tracker</ulink> to fix this issue, in some instances."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I create an <literal>a4j</literal> delayed render zone?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><a4j:support></literal> component has a <varname>requestDelay</varname> attribute, where you can define the delay period."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use IgnoreDupResponses and requestDelay?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>ignoreDupResponses</varname> ignores an AJAX request if a newer request exists. <varname>requestDelay</varname> defines the time delay on the client between compiling a request response and sending that response. You can find more information in <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use eventsQueue attribute?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>eventsQueue</literal> defines the name of the queue that will order upcoming AJAX requests. The queue makes certain that redundant requests are not sent. It is created and named by default. You can find more information in the section on <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use multiple <literal><a4j:status></literal> components on one page?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes, you can. You can find out more from the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/status.jsf?c=status\">JBoss RichFaces Online Demos</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal><a4j:region></literal> component inside the <literal><a4j:repeat></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, you cannot. The <literal><a4j:region></literal> component cannot work inside iteration components such as <literal><h:dataTable></literal> and <literal><a4j:repeat></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I disable skinnability?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You cannot disable skinnability, but you can use a special skin: <literal>plain</literal>. This skin has no parameters, and was created to enable you to embed RichFaces components into existing projects with their own predefined styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does my reRender fail when using hide/show components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Rerendering fails when RichFaces tries to update a component that is defined as hidden or rendered. When <literal>rendered=\"false\"</literal>, the component is not added to the DOM tree, so it cannot be updated (as per the limitations described in the AJAX Processing chapter)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The correct way to rerender a hidden or rendered component is to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Wrap the component that is to be hidden or rendered on AJAX in a wrapper component such as <literal><a4j:outputPanel></literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Set the <varname>reRender</varname> attribute on the wrapper component instead of on the component itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Fpr example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This ensures that the wrapper component presents in the DOM tree, which means that its contents can be updated dynamically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why am I seeing a <exceptionname>ResourceNotRegistered</exceptionname> Exception?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces registers its resources (for example, scripts and images) after an application is accessed, and then accesses these via a generated URL. During application development, when an application is constantly updated on the server, RichFaces may re-register its resources after every server restart, while the browser may attempt to access resources via a cached URL."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve this problem by updating the browser cache: press <keycap>CTRL</keycap>+<keycap>F5</keycap>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I reRender only a particular row(s) of a table?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>ajaxKeys</literal> attribute defines Strings that are updated after an AJAX request, and lets you update several child components separately without updating the whole page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable row selection in a scrollableDataTable using <literal>one and multi-selection rows mode</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable row selection in <literal>one and multi-selection rows mode</literal>, you must use the <varname>selection</varname> attribute. In the example code that follows, when a user submits the form, the current collection of objects selected by the user is placed in the object's property. Upon completion, the <literal><rich:modalPanel></literal> will be rendered with the selected data."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, you can create a managed bean like the one below. The <literal>takeSelection()</literal> method fills the <literal>selectedCars</literal> Array with data retrieved from the <varname>selection</varname>. The <literal>getSelectedCars()</literal> method returns <literal>selectedCars</literal> Array, which is then used to populate select rows of the <literal><rich:dataTable></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I select several rows in a <literal>scrollableDataTable</literal> and drag-and-drop them into a <literal>dataTable</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, to enable row selection, see the previous section on <xref linkend=\"RowSelectionInScrollableDataTable\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable the drag-and-drop function on a <literal>dataTable</literal>, use the <literal><rich:dragSupport></literal> and <literal><rich:dropSupport></literal> components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous example is also available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/scrollableDataTable.jsf\">RichFaces LiveDemo</ulink> site. Only one method is added where the dropped collection is stored:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of the <rich:simpleTogglePanel>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>opened</varname> attribute responsible for storing panel state, and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:simpleTogglePanel></literal> icon appears and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered between page views."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, create a managed bean like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of <rich:panelMenuGroup>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>expanded</varname> attribute and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:panelMenuGroup></literal> expands and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered across page views."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I highlight the rows of a dataTable on the mouseover event?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <literal>onRowMouseOver</literal> and <literal>onRowMouseOut</literal> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable selecting the row of a <literal><rich:dataTable></literal> when I click on it, even if I click within the bounds of an <literal><h:inputText></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following JavaScript function to enable row selection when you click on the row:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can then use <literal><a4j:support></literal> with <varname>event</varname> and <varname>onsubmit</varname> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I rerender table cells with <a4j:support>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To rerender table cells with <literal><a4j:support></literal>, set exact ID values for each component to be updated, and point this <varname>id</varname> to the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The value of the <varname>reRender</varname> attribute belonging to the <literal> <a4j:support></literal> tag defines the sections of the page that will be updated. In the previous example code, the only update made is to the <literal><h:outputText></literal> component in the footer, because its <literal>id</literal> value matches the value of the <varname>reRender</varname> attribute. You can update multiple elements on a page by listing their IDs as the value of the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I create dynamic columns?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create dynamic columns by using the <literal><rich:column></literal> with the <varname>rendered</varname> attribute. Set the value of the <varname>rendered</varname> attribute to match the ID of the dynamic cell, as in the following example code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you could create a managed bean, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use RichFaces with Trinidad?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of a basic <filename>web.xml</filename> file that integrates RichFaces with Trinidad."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why do I see a JavaScript conflict?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Richfaces 3.1.3 uses version 1.6.0 of the <filename> prototype.js</filename> instead of version 1.5.1, which has been used in earlier versions. The source of the conflict is that two versions of the prototype script are included. The first is included as a dependency of the toggle panel components, and the second is included explicitly as a link."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces 3.1.3 is bundled with the same scripts included in Prototype 1.6.0 and Scriptaculous 1.8.0:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Using Prototype with RichFaces components can be problematic because issues that were fixed in version 1.6.0 were not always patched in version 1.5.1. When version 1.5.1 is used, some RichFaces components will not work as expected."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with the Seam Framework?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To use the <literal><rich:fileUpload></literal> component with the Seam Framework, define initialization parameters for the Seam Filter in your <filename>web.xml</filename> file. The Seam Framework will then automatically set the component up for the AJAX4JSF filter at start-up time."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of defining initialization parameters:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with MyFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The order in which filters are defined and mapped in <filename>web.xml</filename> is important to integrating the <literal><rich:fileUpload></literal> component with MyFaces. The code sample that follows shows the correct order in which to define your filters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To ensure that this sequence wors correctly, map the extension filter on your Faces Servlet, not to <filename>*.jsf</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable optional object selection in <rich:suggestionbox>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:suggestionBox></literal> component provides features such as object selection. To store the selected items as objects to be accessed, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the <varname>usingSuggestObjects</varname> attribute to the <literal><rich:suggestionBox></literal> component, and define it as <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <varname>onobjectchange</varname> event attribute to store the currently-selected objects."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All of the selected objects are stored in the <literal>suggestion.SelectedItems</literal> Array. Each Array element contains <literal>text</literal> and <literal>object</literal> properties, so you can iterate this Array, retrieve objects that are not <literal>null</literal>, and retrieve the required property."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for ViewExpiredException?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This exception appears after your session has timed out. Because RichFaces 3.1 is intended for use with JavaServer Faces 1.1, <exceptionname>ViewExpiredException</exceptionname>s will not generate automatically when RichFaces is used with JavaServer Faces 1.2. To work around this limitation, add the following to your <filename>web.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for Request Errors and Session Expiration?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To redefine the standard handlers that are responsible for processing different exceptional situations, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add custom <literal>onError</literal> and <literal>onExpire</literal> handlers, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more detailed description of this process, see <xref linkend=\"RequestErrorsAndSessionExpirationHandling\" /> in the Developer Guide."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Custom <literal>onError</literal> and <literal>onExpire</literal> handlers will not work under MyFaces, because MyFaces handles exceptions with an internally-generated debug page. To prevent this behavior, use the following code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I add a cookie in an AJAX response?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The bean described below adds a cookie to an AJAX response:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you can define the cookie to be included as shown in the following example. After the <literal>test</literal> cookie is set, the value of that cookie will appear on a page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is new in AJAX4JSF 3.2.x?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces 3.2.x releases have some new features:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><a4j:portlet</literal> component has been <emphasis>deprecated</emphasis>, since JSR-301 defines a similar function for <literal>UIViewRoot</literal> components;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><rich:ajaxValidator></literal>, <literal><rich:beanValidator></literal> and <literal><rich:graphValidator></literal> validators have been added to provide different validation types."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I launch the RichFaces sample on the JBoss server?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To launch the RichFaces sample application on the JBoss server, add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass a Boolean value in the <rich:componentControl> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code shows you how to avoid requiring a Boolean value:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use <code>'block'</code> instead of <code>' '</code> to avoid <literal>invalid style</literal> CSS errors."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/Getting_Started.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Getting_Started.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,159 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Started with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This chapter tells you how to plug RichFaces components into a JSF application. The instructions are based on a simple <emphasis>JSF with RichFaces</emphasis> creation process, from downloading the required libraries to running the application in a browser. These instructions do not depend on the integrated development environment that is in use."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Simple JSF application with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> — the simple application — is similar to a typical <emphasis>hello world</emphasis> application, with one exception: the world of RichFaces will say \"Hello!\" to the user first."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a standard JSF 1.2 project named <literal>Greeter</literal>. Include all required libraries, and continue with the instructions that follow."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Adding RichFaces libraries into the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "From the <filename>RichFaces</filename> folder where you unzipped the RichFaces binary files, open the <filename>lib</filename>. This folder contains three <filename>*.jar</filename> files with API, UI, and implementation libraries. Copy these JARs from <filename>lib</filename> to the <filename>WEB-INF/lib</filename> directory of your <application>Greeter</application> JSF application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A JSF application with RichFaces assumes that the following JARs are available in the project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-beanutils-1.7.0.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-collections-3.2.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-digester-1.8.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-logging-1.0.4.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jhighlight-1.0.jar</filename>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering RichFaces in <filename>web.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "After you add the RichFaces libraries to the project, you must register them in the project <filename>web.xml</filename> file. Add the following to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For more information about RichFaces skins, read <xref linkend=\"Skinnability\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, your <filename>web.xml</filename> should look like this:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Managed bean"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <application>RichFaces Greeter</application> application needs a managed bean. In the project's <filename>JavaSource</filename> directory, create a new managed bean named <literal>user</literal> in the <literal>demo</literal> package. Place the following code in <filename>user</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering the bean in <filename>faces-cofig.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To register the <literal>user</literal> bean, add the following to the <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Greeter index.jsp"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> has only one JSP page. Create <filename>index.jsp</filename> in the root of <literal>WEB CONTENT</literal> folder and add the following to the JSP file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The application uses three RichFaces components: <emphasis role=\"bold\"><property><rich:panel></property></emphasis> is used as visual container for information; <emphasis role=\"bold\"><property><a4j:commandButton></property></emphasis> with built-in AJAX support lets a greeting be rendered dynamically after a response returns; and <emphasis role=\"bold\"><property><a4j:form></property></emphasis> helps the button to perform the action."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces tag library should be declared on each JSP page. For XHTML pages, add the following lines to declare your tag libraries:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Now, run the application on the server by pointing your browser to the <filename>index.jsp</filename> page: <literal>http://localhost:8080/Greeter/index.jsf</literal>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "\"RichFaces Greeter\" application"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Relevant Resources Links"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"https://www.redhat.com/apps/store/developers/jboss_developer_studio.html\">JBoss Developer Studio</ulink> includes tight integration with the RichFaces component framework. <!-- The following links might be useful for those who already use this IDE and RichFaces to develop applications, and for those who wish to improve their development process. -->"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/IDE_Support.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/IDE_Support.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/IDE_Support.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Integrated Development Environment Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is supported by both <ulink url=\"http://www.redhat.com/developers/rhds/index.html\">JBoss Developer Studio 1.0.0 GA</ulink> and <ulink url=\"http://www.jboss.org/tools/index.html\">Jboss Tools</ulink>. JBoss Developer Studio is a fully packaged Integrated Development Environment (IDE) that provides full support for Java Server Faces, RichFaces, Facelets, Struts and other Web technologies. It seamlessly combines visual and source-oriented development approaches. You can add JBoss Developer Studio capabilities to any JSF project by adding the appropriate libraries and modifying configuration files as required."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/Introduction.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Introduction.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Introduction.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,79 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is an open source framework that adds AJAX capability into existing JSF applications without resorting to JavaScript."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces leverages aspects of the JavaServer Faces (JSF) framework, including lifecycle, validation, conversion facilities, and management of static and dynamic resources. RichFaces components with built-in AJAX support and a highly customizable look-and-feel can be easily incorporated into JSF applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces allows you to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Experience the benefits of JSF while working with AJAX. RichFaces is fully integrated into the JSF lifecycle. Where other frameworks only allow access to the managed bean facility, RichFaces lets you access the action and value change listeners, and invokes server-side validators and converters during the AJAX request-response cycle."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add AJAX capabilities to existing JSF applications. The RichFaces framework provides two component libraries (Core AJAX and UI). The Core library adds AJAX functionality to existing pages, so you need not write any JavaScript or replace existing components with new AJAX components manually. RichFaces enables page-wide rather than component-wide AJAX support, giving you the opportunity to define events on the page. <!-- An event invokes an AJAX request and areas of the page which become synchronized with the JSF Component Tree after changing the data on the server by AJAX request in accordance with events fired on the client. -->"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily create different views with a variety of components, available out-of-the-box. The RichFaces UI library contains components for adding rich user interface (UI) features to JSF applications, providing you with a broad variety of AJAX-enabled components with extensive skins support. RichFaces components are designed to integrate seamlessly with other third-party component libraries, so you have more options when you develop applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Write your own rich components with built-in AJAX support. The Component Development Kit (CDK) is constantly being expanded. It includes both code generation and templating facilities and a simple JSP-like (JavaServer Pages) syntax, letting you create first-class rich components with built-in AJAX functionality."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Package resources with application Java classes. RichFaces provides advanced support for managing different resource types, including images, JavaScript code, and CSS stylesheets. The resource framework makes it easier to include these resources in JAR files with your custom component code."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily generate binary resources. The resource framework can generate images, sounds, Excel spreadsheets, etc. in real time, so you can, for example, create images with the Java Graphics 2D library and other similar resources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customize the look and feel of your user interface with skins-based technology. RichFaces lets you easily define and manage different color schemes and other user interface parameters by using named <emphasis>skin parameters</emphasis>. This means you can access UI parameters from JSP and Java code to adjust your UI in real time. RichFaces includes a number of predefined skins to kick-start your application's development, but it is easy to create your own custom skins."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Simultaneously create and test your components, actions, listeners, and pages. RichFaces will soon include an automated testing facility to generate test cases for your component as you develop it. The testing framework tests not only the components, but also any other server-side or client-side functionality, including JavaScript code — and it will do so <emphasis>without</emphasis> deploying the test application into the Servlet container."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces UI components can be implemented immediately, right out of the box. This saves development time and gives you immediate access to RichFaces web application development features, so experience with RichFaces is fast and easy to obtain."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/Links_to_Resources.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Links_to_Resources.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Links_to_Resources.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,74 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Links to information resources"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Links"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/portal/jbossrichfaces/\">JBoss RichFaces</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss Forum"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://jboss.com/index.html?module=bb&op=main&c=27\">JBoss Forums</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Wiki"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/wiki/RichFaces\">RichFaces Wiki</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Blog"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "<ulink url=\"http://jroller.com/page/a4j\">RichFaces Blog</ulink>"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/Revision_History.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Revision_History.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Revision_History.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: member
+#, no-c-format
+msgid "JIRA corrections."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/RichFaces_Developer_Guide.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/RichFaces_Developer_Guide.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/RichFaces_Developer_Guide.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/Settings.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Settings.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Settings.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,334 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Settings for different environments"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces includes support for all tags (components) included in the JavaServer Faces (JSF) specification. To add RichFaces capabilities to an existing JSF project, place the RichFaces libraries into the <filename>lib</filename> directory of the project, and add filter mapping. The behavior of the existing project does not change when you add RichFaces."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Application Descriptor Parameters"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not require that any parameters be defined in your <filename>web.xml</filename>, but the RichFaces parameters listed below will help you during the development process and increase the flexibility of your RichFaces applications."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.SKIN"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The name of a skin that is used in an application. Can be a literal string with a skin name or the EL expression (<literal>#{...}</literal>) associated with a String property (skin name) of a property of a <literal>org.richfaces.framework.skin</literal> type. In the latter case, that instance is used as the current skin."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadScriptStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces script files are loaded to the application. Possible values are <literal>ALL</literal>, <literal>DEFAULT</literal> and <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadStyleStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces style files are loaded into the application. Possible values are: <literal>ALL</literal>, <literal>DEFAULT</literal>, or <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.LOGFILE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "none"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The URL of an application or a container log file (if applicable). If this parameter is set, content from the given URL is shown on a Debug page in the <literal>iframe</literal> window."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.VIEW_HANDLERS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of <literal>ViewHandler</literal> instances for inserting in a view handler chain. These handlers are inserted before the RichFaces viewhandlers, in the order they are listed. In a Facelets application, you would declare <literal>com.sun.facelets.FaceletViewHandler</literal> here instead of in the <filename>faces-config.xml</filename> file."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.CONTROL_COMPONENTS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of special <emphasis>control case</emphasis> components, such as the messages bundle loader or an alias bean component. These handlers are provided via a reflection from the static field <literal>COMPONENT_TYPE</literal>. Encoding methods for these components are always called while rendering AJAX responses, even if a component has not been updated."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_RESOURCE_DATA"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "false"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "For generated resources (such as encrypt generation data), this is encoded in the resource URL. For example, the URL of an image generated by the <classname>mediaOutput</classname> component contains the name of a generation method. Since malicious code can exploit this to create a request for any JSF bean or attribute, this parameter should be set to <literal>true</literal> in critical applications. (This fix works with Java Runtime Environment 1.4.)"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_PASSWORD"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "random"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A password used to encrypt resource data. If this is not set, a random password is used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.COMPRESS_SCRIPT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "true"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "When defined, does not allow the frameword to reformat JavaScript files. This means that the debug feature cannot be used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URLs of all generated resources. This is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.GLOBAL_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/g"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URI of all global resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SESSION_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/s"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be used to track the sessions of generated resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.DEFAULT_EXPIRE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "86400"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the period (in seconds) for which resources are cached when they are streamed back to the browser."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SERIALIZE_SERVER_STATE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "If set to <literal>true</literal>, the component state (not the tree) will be serialized before it is stored in the session. This can be useful in applications with view state that is sensitive to model changes. Alternatively, use <literal>com.sun.faces.serializeServerState</literal> and <literal> org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</literal> parameters in their respective environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>org.richfaces.SKIN</literal> is used in the same way as <literal>org.ajax4jsf.SKIN</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "org.ajax4jsf.Filter Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "log4j-init-file"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "-"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A path (relative to the web application's context) to the <filename>log4j.xml</filename> configuration file. This can be used to set up per-application custom logging."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "enable-cache"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Enables caching of framework-generated resources (JavaScript, CSS, images, etc.). However, your cached resources will not be used when attempting to debug custom JavaScript or Styles."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "forcenotrf"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Forces all JSF pages to be parsed by a HTML syntax check filter. If set to <literal>false</literal>, only AJAX responses will be parsed and converted to well-formed XML. Setting this to <literal>false</literal> can improve performance, but may also cause unexpected information to be rendered during AJAX updates."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Sun JSF RI"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces works with JavaServer Faces 1.2_13 without needing to modify additional settings."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Facelets Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces has high-level support for Facelets, regardless of the version used. However, some JSF frameworks (including Faces) require that their own <literal>ViewHandler</literal> be listed first in the <literal>ViewHandler</literal> chain. RichFaces also requires that its <literal>AjaxViewHandler</literal> be listed first, but because it is installed first, no settings will need to be altered. Where multiple frameworks are used without RichFaces, you can use the <literal>VIEW_HANDLERS</literal> parameter to define the order in which the <literal>ViewHandler</literal>s are used. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This declares that while <literal>Facelets</literal> will officially be first, <literal>AjaxViewHandler</literal> will briefly be ahead of it to perform some small, important task."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this case, you need not define <literal>FaceletViewHandler</literal> in <filename>WEB-INF/faces-config.xml</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JBoss Seam Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is compatible with <application>JBoss Seam</application> and Facelets when run within JBoss Enterprise Application Server. No additional JARs are required. All you need to do is package the RichFaces library with your application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For <application>Seam 1.2</application>, your <filename>web.xml</filename> must be as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>Seam 2.x</application> supports RichFaces Filter, so your <filename>web.xml</filename> must look like this:"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/de-DE/Technical_Requirements.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Technical_Requirements.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Technical_Requirements.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,179 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Technical Requirements"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces</application> was developed with an open architecture to ensure that it was compatible with the widest possible variety of environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This is what you need to start working with <application>RichFaces 3.3.1</application>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JavaServer Faces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java Application Server <emphasis>or</emphasis> Servlet Container"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Browser (on client side)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Java Versions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JDK 1.5 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported JavaServer Faces Implementations and Frameworks"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun JSF-RI - 1.2_12"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "MyFaces 1.2.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Facelets 1.1.1 - 1.2"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Seam 1.2. - 2.1.0"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Servers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Apache Tomcat 5.5 - 6.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "BEA WebLogic 9.1 - 10.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Resin 3.1"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Jetty 6.1.x"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun Application Server 9 (J2EE 1.5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "GlassFish (J2EE 5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JBoss 4.2.x - 5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Websphere 7.0. and higher"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Geronimo 2.0 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Browsers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6.0 - 8.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Firefox 2.0 - 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera 8.5 - 9.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Google Chrome"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This list is composed from user reports of compatibility. We assume that this list is incomplete, so the absence of your environment from the list does not necessarily mean that it is incompatible with RichFaces."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "We appreciate your feedback about compatible platforms and browsers that are not listed here. This helps us keep the list up-to-date."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/Architecture_Overview.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/Architecture_Overview.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/Architecture_Overview.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,1829 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Basic concepts of the RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces Framework is implemented as a component library that adds AJAX capabilities into existing pages. This means that you do not need to write any JavaScript code or replace existing components with new AJAX widgets. RichFaces enables page-wide AJAX support instead of the traditional component-wide support, so you can define areas of the page that will reflect changes made by AJAX events on the client."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram following shows the process in full:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Processing flow"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you use JSF tags to define sections of a JSF page that you wish to update with the results of an AJAX request. It also provides you with several options for sending AJAX requests to the server. You do not need to write any JavaScript or <literal>XMLHTTPRequest</literal> objects by hand — everything is done automatically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Architecture Overview"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following figure lists several important elements of the RichFaces Framework."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Core AJAX component structure"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Filter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To make the most of RichFaces, you should register a <literal>Filter</literal> in your application's <filename>web.xml</filename>. The <literal>Filter</literal> recognizes multiple request types. The sequence diagram in Figure 5.3 shows the differences in processing between a <emphasis>regular</emphasis> JSF request and an AJAX request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request processing sequence diagram"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In either case, the required static or dynamic resource information that your application requests is registered in the <literal>ResourceBuilder</literal> class."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When a resource request is issued, the RichFaces filter checks the <literal>Resource Cache</literal> for this resource. If it is present, the resource is returned to the client. Otherwise, the filter searches for the resource among those registered in the <literal>ResourceBuilder</literal>. If the resource is registered, the RichFaces filter requests that the <literal>ResourceBuilder</literal> creates (delivers) the resource."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram that follows illustrates the process of requesting a resource."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Resource request sequence diagram"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Action Components"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "AJAX Action components are used to send AJAX requests from the client side. There are a number of AJAX Action components, including <literal><a4j:commandButton></literal>, <literal><a4j:commandLink></literal>, <literal><a4j:poll></literal>, and <literal><a4j:support></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Containers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>AjaxContainer</literal> is an interface that defines an area on your JSF page that should be decoded during an AJAX request. <literal>AjaxViewRoot</literal> and <literal>AjaxRegion</literal> are both implementations of this interface."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JavaScript Engine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces JavaScript Engine runs on the client side, and updates different areas of your JSF page based on information from the AJAX response. This JavaScript code operates automatically, so there is no need to use it directly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors and Session Expiration Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you redefine the standard handlers responsible for processing exceptions. We recommend defining your own JavaScript, which will be executed when exceptional situations occur."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To execute your own code on the client in the event of an error during an AJAX request, you must redefine the standard <literal>A4J.AJAX.onError</literal> method like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function accepts the following as parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>req</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a parameter string of a request that calls an error"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>status</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the number of an error returned by the server"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>message</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for the given error"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, you can create your own handler that is called when timeouts, internal server errors, etc. occur."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Session Expired Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also redefine the <literal>onExpired</literal> framework method that is called on the <literal>SessionExpiration</literal> event."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Example:</emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function can take the following parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>loc</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the URL of the current page (can be updated on demand)"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>expiredMsg</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for display in the event of <literal>SessionExpiration</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customized <literal>onExpire</literal> handlers do not work under MyFaces. MyFaces handles exceptions by internally generating a debug page. To prevent this behavior, use the following:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skinnability"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you look at any CSS (Cascading Style Sheets) file in an enterprise application, you will notice how often the same color is noted. Standard CSS cannot define a particular colour abstractly as a panel header color, the background color of an active pop-up menu item, a separator color, etc. To define common interface styles, you must copy the same value multiple times, and the more interfaces you have, the more repetition is required."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, if you want to change the palette of an application, you must change all interrelating values, or your interface can appear clumsy. If a customer wants to be able to adjust their interface's look and feel in real time, you must be able to alter several CSS files, each of which will contain the same value multiple times."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve these problems with the <emphasis>skins</emphasis> that are built into and rully implemented in RichFaces. Every named skin has <emphasis>skin parameters</emphasis> that define a palette and other attributes of the user interface. By changing a few skin parameters, you can alter the appearance of dozens of components simultaneously, without interfering with interface consistency."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinnability</literal> feature cannot completely replace standard CSS, and does not eliminate its usage. Instead, it is a high-level extension of standard CSS that can be used in combination with regular CSS declarations. You can also refer to skin parameters in CSS through the JSF Expression Language. This lets you completely synchronize the appearance of all elements in your pages."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Using Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces <emphasis>skinnability</emphasis> is designed for use alongside:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "skin parameters defined in the RichFaces framework,"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "predefined CSS classes for components, and"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "user style classes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A component's color scheme can be applied to its elements using any of three style classes:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A default style class inserted into the framework"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This contains stle parameters that are linked to some constants from a skin. It is defined for every component and specifies a default level of representation. You can modify an application interface by changing the values of the skin parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A style class of skin extension"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This class name is defined for every component element, and inserted into the framework to let you define a class with the same name in your CSS files. This lets you easily extend the appearance of all components that use this class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "User style class"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use one of the <literal>styleClass</literal> parameters to define your own class for component elements. As a result, the appearance of one particular component is changed according to a CSS style parameter specified in the class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Example"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following is an example of a simple <emphasis>panel</emphasis> component:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This code generates a panel component on a page, which consists of two elements: a wrapper <literal><div></literal> element and a <literal><div></literal> element for the panel body with the specified style properties. The wrapper <literal><div></literal> element will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>dr-pnl</literal> is a CSS class that is specified in the framework via skin parameters:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>background-color</varname> is defined with <literal>generalBackgroundColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>border-color</varname> is defined with <literal>panelBorderColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change all colors for all panels on all pages by changing these skin parameter values. However, if you specify a <literal><rich:panel></literal> class on the page, its parameters are also acquired by all panels on this page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Developers can also change the style properties for panel. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous definition could add some style properties from <literal>customClass</literal> to one particular panel. As a result, we will get three styles:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skin Parameters Tables in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces provides eight predefined skin parameters (skins) at the simplest level of common customization:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "plain"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "emeraldTown"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "blueSky"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "wine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "japanCherry"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ruby"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "classic"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "deepMarine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To apply a skin, you must specify a skin name in the <varname>org.richfaces.SKIN</varname> context parameter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following table shows the values for each parameter in the <literal>blueSky</literal> skin:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Colors"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Parameter name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#BED6F8"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerGradientColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#F2F7FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#000000"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerWeightFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bold"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FFFFFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "11px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Arial, Verdana, sans-serif"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "additionalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#ECF4FE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowOpacity"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "panelBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "subBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C6DEFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabDisabledTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#8DB7F3"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "trimColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#D6E6FB"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FAE6B0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E5973E"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "selectControlColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E79A00"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0078D0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0090FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "visitedLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Fonts"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableFooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#cccccc"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableSubfooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#f1f1f1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C0C0C0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>plain</literal> skin was added in version 3.0.2. It has no parameters, and is important when embedding RichFaces components into existing projects with their own styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Creating and Using Your Own Skin File"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To create your own skin file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a file. In it, define skin constants to be used by style classes (see <xref linkend=\"SkinParametersTablesInRichFaces\" />). The name of the skin file should follow this format: <literal><name>.skin.properties</literal>. (For examples of this file, see the RichFaces predefined skin parameters: <literal>blueSky</literal>, <literal>classic</literal>, <literal>deepMarine</literal>, etc. These files are located in the <filename>richfaces-impl-xxxxx.jar</filename> archive in the <filename>/META-INF/skins</filename> folder."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the skin definition <literal><contex-param></literal> to the <filename>web.xml</filename> of your application, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place your <literal><name>.skin.properties</literal> file in either your <filename>/META-INF/skins</filename> or <filename>/WEB-INF/classes</filename> directory."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Built-in Skinnability in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you incorporate skins into your user interface (UI) design. This framework lets you use named skin parameters in your properties files to control skin appearance consistently across a set of components. You can see examples of predefined skins at: <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">http://livedemo.exadel.com/richfaces-demo/ </ulink>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Skins let you define a style in which to render standard JSF components and custom JSF components built with RichFaces. You can experiment with skins by following these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a custom render kit and register it in the <filename>faces-config.xml</filename> like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, create and register custom renderers for the component based on the look-and-feel predefined variables:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, place a properties file with skin parameters into the class path root. There are two requirements for the properties file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The file must be named <filename><replaceable>skinName</replaceable>.skin.properties</filename>. In this case, we would call it <literal>newskin.skin.properties</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The first line in this file should be <literal>render.kit=<replaceable>render-kit-id</replaceable></literal>. In this case, we would use <literal>render.kit=NEW_SKIN</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "More information about creating custom renderers can be found at: <ulink url=\"http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html\">http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Changing skin in runtime"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change skins during runtime by defining the following EL-expression in your <filename>web.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinBean</literal> code looks like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also set the <varname>skin</varname> property's initial value in the configuration file. To set <literal>classic</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also change the properties of the default skin. To do so, edit the properties of the default skin. The following shows you example page code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The above code will generate the following list of options:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Controls Skinning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This feature is designed to unify the look and feel of standard HTML elements and RichFaces components. Skinning can be applied to all controls on a page based on element names and attribute types (where applicable). This feature also provides a set of CSS styles that let skins be applied by assigning <literal>rich-*</literal> classes to particular elements, or to a container of elements that nests controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard Controls Skinning provides two levels of skinning: <emphasis>Basic</emphasis> and <emphasis>Extended</emphasis>. The level used depends on the browser type detected. If the browser type cannot be detected, <literal>Extended</literal> is used. However, if you want to explicitly specify the level to be applied, add a <varname></varname> context parameter to your <filename>web.xml</filename> and set the value to either <literal>basic</literal> or <literal>extended</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Basic</emphasis> level provides customization for only basic style properties. Basic skinning is applied to the following browsers:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in BackCompat mode (see <ulink url=\"http://msdn2.microsoft.com/en-us/library/ms533687(VS.85).aspx\">document.compatMode property in MSDN</ulink>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Extended</emphasis> level introduces a broader number of style properties on top of basic skinning, and is applied to browsers with rich visual styling control capabilities. The following browsers support Extended skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Mozilla Firefox"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in Standards-compliant mode (CSS1Compat mode)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following elements can be modified with skins:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>input</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>select</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>textarea</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>keygen</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>isindex</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>legend</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>fieldset</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>hr</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>a</literal> (together with the <literal>a:hover</literal>, <literal>a:visited</literal> pseudo-elements)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two ways to initialize skinning for standard HTML controls:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. This method implies that skinning style properties are applied per-element and attribute type (where applicable). No additional steps are required. See the <xref linkend=\"BasicLevel\" /> and <xref linkend=\"ExtendedLevel\" /> tables for elements to which skinning can be applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. When enabled, you are provided with a set of predefined CSS classes to apply skins to your HTML components."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enabling <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> provides you style classes that can be applied to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "basic elements nested within elements with a <emphasis>rich-container</emphasis> class. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements with a class name that corresponds to one of the basic element names or types are mapped with the <literal>rich-<elementName>[-<elementType>]</literal> scheme, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements are given classes depending upon their <literal>link</literal> type and pseudo-class name, for example, <literal>rich-link</literal>, <literal>rich-link-hover</literal>, <literal>rich-link-visited</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The predefined rich CSS classes provided can be used as classes for both basic and complex HTML elements."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code snippet shows several elements as an example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more thorough look at standard component skinning, we recommend exploring the CSS files located in the <filename>ui/core/src/main/resources/org/richfaces/</filename> directory of the RichFaces SVN repository."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex and legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "CSS Properties"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-size"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-family"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for hr"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:hover"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColorgeneralLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Elements Skin Bindings for .rich-input, .rich-select, .rich-textarea, .rich-keygen, .rich-isindex, .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-fieldset"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-hr"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-width"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-style"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "solid"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:hover"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin parameters/Value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "inset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-color"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "no-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-position"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px 1px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-edit"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "editBackgroundColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-error"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "warningBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding-left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "7px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button, .rich-button-disabled, .rich-button-over"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "2px 10px 2px 10px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "text-align"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "cursor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "pointer"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "repeat-x"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "top left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button-press"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bottom left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-container fieldset, .rich-fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "10px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-weight"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-form"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "0px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "margin"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Extended level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-image"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for button[type=button], button[type=reset], button[type=submit], input[type=reset], input[type=submit], input[type=button]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button[disabled], .rich-container *|button[disabled], .rich-button-disabled"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonDisabledBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for .rich-button-disabled, .rich-container button[type=\"button\"][disabled], .rich-button-button-disabled, .rich-container button[type=\"reset\"][disabled], .rich-button-reset-disabled, .rich-container button[type=\"submit\"][disabled], .rich-button-submit-disabled, .rich-container input[type=\"reset\"][disabled], .rich-input-reset-disabled, .rich-container input[type=\"submit\"][disabled], .rich-input-submit-disabled, .rich-container input[type=\"button\"][disabled], .rich-input-button-disabled"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *button[type=\"button\"][disabled], button[type=\"reset\"][disabled], button[type=\"submit\"][disabled], input[type=\"reset\"][disabled], input[type=\"submit\"][disabled], input[type=\"button\"][disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.InputBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for textarea[type=textarea], input[type=text], input[type=password], select"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea[disabled], .rich-container *|textarea[disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "textarea[type=\"textarea\"][disabled], input[type=\"text\"][disabled], input[type=\"password\"][disabled]"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The basic skinning level can fail if the <literal>ajaxPortlet</literal> is configured as follows:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Client-side Script for Extended Skinning Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Extended skinning of standard HTML controls is applied automatically: the browser type is detected, and if a browser does not fully support extended skinning, only basic skinning is applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are some problems with standard HTML controls in certain browsers (Opera and Safari) that may cause problems if you wish to skin your RichFaces components and standard HTML controls manually."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable skinnability, set the <varname>org.richfaces.LoadStyleStrategy</varname> parameter to <literal>NONE</literal> in your <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You should also include the style sheets that apply skins to RichFaces components and standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To work around the problem of extended skinning in Opera and Safari, the <filename>skinning.js</filename> client script is added to the RichFaces library. This detects the browser type and enables extended skinning only for browsers that fully support it."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Activate the script by inserting the following JavaScript into your page:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When no script-loading strategy is used and extended skinning is enabled, a warning message appears in the console."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also specify the <varname>media</varname> attribute in the <literal>link</literal> tag. This adds the <filename>extended_both.xcss</filename> style sheet to <literal>rich-extended-skinning</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include your style sheets to the page when automatic skinnability is disabled, add the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Base64 encoder now uses <literal>!</literal> instead of <literal>.</literal>, so remember to use the <literal>a4j/versionXXX</literal> resources prefix instead of <literal>a4j_versionXXX</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "XCSS File Format"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Cross-site Cascading Style Sheet (XCSS) files are the core of RichFaces component skinnability. XCSS is XML-formatted CSS that extends the skinning process. RichFaces parses the XCSS file containing all look and feel parameters of a particular component and compiles the information into a standard CSS file that can be recognized by a web browser."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The XCSS file contains CSS properties and skin parameter mappings. Mapping a CSS selector to a skin parameter can be done with <literal>< u:selector ></literal> and <literal>< u:style></literal> XML tags, which define the mapping structure, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "During processing, this code will be parsed and assembled into a standard CSS format, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>name</varname> attribute of <literal><u:selector></literal> defines the CSS selector, while the <varname>name</varname> attribute of the <literal><u:style></literal> tag defines the skin constant that is mapped to a CSS property. You can also use the <varname>value</varname> attribute of the <literal><u:style></literal> tag to assign a value to a CSS property."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "CSS selectors with identical skin properties can be included in a comma-separated list:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Plug-n-Skin</emphasis> lets you easily create, customize, and plug in a custom skin to your project. You can create skins based on the parameters of predefined RichFaces skins. Plug-n-Skin also lets you unify the appearance of rich controls with standard HTML elements. This section contains step-by-step instructions for creating your own skin with Plug-n-Skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, use Maven to create a template for your new skin. (You can find more information about configuring Maven for RichFaces in the <!-- #modify add info? --><ulink url=\"http://wiki.jboss.org/wiki/HowToConfigureMavenForRichFaces\">JBoss wiki article</ulink>. These Maven instructions can be copied and pasted into the command line interface to execute them."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Primary keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>archetypeVersion</varname> — indicates the RichFaces version; for example, <literal>3.3.1.GA</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>artifactId</varname> — the artifact ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>groupId</varname> — the group ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>version</varname> — the version of the project you create. By default, this is set to <literal>1.0.-SNAPSHOT</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This operation creates a directory named after your <literal>ARTIFACT-ID</literal>. The directory contains a template of the Maven project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following steps will guide you though creating of the skin itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Run the following command from the root directory of the Maven project. (This directory will contain your <filename>pom.xml</filename> file.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>name</varname> — defines the name of the new skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>package</varname> — the base package of the skin. By default, the project's <literal>groupId</literal> is used."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Additional optional keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — defines the name of the base skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>createExt</varname> — if set to <literal>true</literal>, extended CSS classes are added. For more information, please, see <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once these operations are complete, the following files and folders should have been created:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImage.java</filename> — the base class used to store images. Location: <filename>\\src\\main\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImageTest.java</filename> — a test version of a class that stores images. Location: <filename>\\src\\test\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>XCSS files</filename> — XCSS files define the new look of RichFaces components affected by the new skin. Location: \"\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.properties</filename> — a file that contains the new skin's properties. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following properties are used to configure the <filename>SKIN-NAME.properties</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — the name of the skin to be used as a basis for your own skin. The look of the skin you define will be affected by the new style properties."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>generalStyleSheet</varname> — a path to the style sheet (<filename>SKIN-NAME.xcss</filename>) that imports your component's style sheets to be modified by the new skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>extendedStyleSheet</varname> — the path to a style sheet that is used to unify the appearance of RichFaces components and standard HTML controls. For additional information, read <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>gradientType</varname> — a predefined property to set the type of gradient applied to the new skin. Possible values are <literal>glass</literal>, <literal>plastic</literal>, <literal>plain</literal>. More information on gradient implementation you can find further in this chapter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.xcss</filename> — an XCSS file that imports the component's XCSS files to be modified by the new skin. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>XCSS files</literal> — creates the XCSS files that determine styles for standard controls (<filename>extended_classes.xcss</filename> and <filename>extended.xcss</filename>), if the <varname>createExt</varname> key is set to <literal>true</literal>. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-ext.xcss</filename> — creates the <filename>SKIN-NAME-ext.xcss</filename> file that imports defining styles for standard controls if <varname>createExt</varname> is set to <literal>true</literal>. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-resources.xml</filename> — contains descriptions of all files listed previously. Location: <filename>src\\main\\config\\resources</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now start editing the XCSS files located in <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>. Assign new style properties to your selectors (listed in the XCSS files) in either of the following ways:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard CSS coding approach (that is, add CSS properties to the selectors). Remember that the selectors must be within <literal><f:verbatim> </f:verbatim></literal> tags. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "XCSS coding approach (the usual method of creating XCSS files in RichFaces). XCSS tags must be placed <emphasis>outside</emphasis> <literal><f:verbatim> </f:verbatim></literal> tags."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once you have performed these steps and edited the XCSS files, build the new skin and plug it into the project. To build the skin, execute the following command from the root directory of your skin project (the directory that contains your <filename>pom.xml</filename> file):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Plug-n-skin feature also has a number of predefined gradients. The following code can be used to apply a gradient:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>background-image</varname> CSS property is defined with <literal><f:resource f:key=\"org.richfaces.renderkit.html.CustomizeableGradient\"></literal>, which sets the gradient. The gradient type can be specified in the <filename>SKIN-NAME.properties</filename> with the <varname>gradientType</varname> property, which can be set to <literal>glass</literal>, <literal>plastic</literal>, or <literal>plain</literal>. The gradient can then be adjusted with the <varname>baseColor</varname>, <varname>gradientColor</varname>, <varname>gradientHeight</varname>, <varname>valign</varname> attributes, as seen in the previous code snippet."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now use your newly-created skin in your project by adding your new skin parameters to the <filename>web.xml</filename> file, and placing the JAR file containing your skin (located in the <filename>target</filename> directory of your skin project) in the <filename>\\WebContent\\WEB-INF\\lib\\</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Details of Usage"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This section covers some practical aspects of Plug-n-Skin implementation. We assume that you have read the section of the guide describing the Plug-n-Skin prototype creation process."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, we must create a new skin (as described in the previous section). The following creates a template of the new skin project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now browse the <filename>P-n-S</filename> directory to view the files and folders created."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use Maven to add all required files to the skin project, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As mentioned in the previous section, <!-- #modify '-D' typo? --><literal>-DbaseSkin</literal> defines the RichFaces built-in skin to use as a base, and <literal>-DcreateExt=true</literal>, which determines that the new skin will include XCSS files that unify the appearance of the rich components and the standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once your resources have been created, you can begin refining the newly-created skin. Begin by editing the rich components' XCSS files."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example of the Plug-n-Skin feature, we will edit some <literal><rich:calendar></literal> style attributes and some basic HTML controls. We will show you how to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor the background of the current day in the <literal><rich:calendar></literal>;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor a standard HTML submit button;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To edit <literal><rich:properties></literal>'s style properties, you must open the <filename>calendar.xcss</filename> file, located in <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the <filename>calendar.xcss</filename> file, find the <literal>.rich-calendar-today</literal> selector and amend it as follows:<literal>background-color: #075ad1;</literal>. This will change the background color of the current day."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next we will change the font style of a standard HTML <emphasis>submit</emphasis> button. Open the <filename>extended.xcss</filename> file from the <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename> directory and insert <literal>font-weight: bold;</literal> between the curly braces of these selectors, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The desired changes have now been made, and you can proceed to building the new <literal>PlugnSkinDemo</literal> skin and importing it into the project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Build the skin by executing <command>mvn clean install</command> from the <filename>P-n-S</filename> directory. This creates a <filename>target</filename> directory containing a JAR file with a newly-compiled skin. In our case, the file is named <filename>P-n-S-1.0.-SNAPSHOT.jar</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, import the new <literal>PlugnSkinDemo</literal> skin into your project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Copy the <filename>P-n-S-1.0.-SNAPSHOT.jar</filename> file to the <filename>\\WebContent\\WEB-INF\\lib\\</filename> directory."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the name of the new skin to the <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember, standard controls skinning must be enabled in <filename>web.xml</filename>. Add the following to enable standard controls skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The results of each alteration to the skin are shown in the figures that follow:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin feature in action."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "State Manager API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JSF has an advanced navigation mechanism that lets you define <emphasis>navigation</emphasis> from view to view. In a web application, navigation occurs when a user changes from one page to another by clicking on a button, a hyperlink, or another command component. There is no switch mechanism between some logical states of the same view. For example, in <emphasis>Login/Register dialog</emphasis>, an existing user signs in with his user name and password, but if a new user attempts to register, an additional field (<literal>Confirm</literal>) is displayed, and button labels and methods are changed when the user clicks the <guilabel>To register</guilabel> link:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Login Dialog"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Register Dialog"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>RichFaces State API</emphasis> lets you easily define a set of states for pages, and properties for these states."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>States</varname> class interfaces with a <property>map</property>, where the <methodname>keySet</methodname> defines the State name and the <methodname>entrySet</methodname> is a <varname>State</varname> <property>map</property>. The <varname>State</varname> <property>map</property> defines the properties, method bindings, or constant state variables of a key or object, where these values may change depending on the active State."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces State API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One of the most convenient features of the RichFaces State API is the ability to navigate between <varname>State</varname>s. The API implements changes in <varname>State</varname> through standard JSF navigation. When the action component returns an outcome, the JSF navigation handler (extended through the RichFaces State API) checks whether the outcome is registered as a <emphasis><varname>State</varname> change outcome</emphasis>. If <literal>true</literal>, the corresponding <varname>State</varname> is activated. If <literal>false</literal>, standard navigation handling is called."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Implement the RichFaces State API like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register the State Navigation Handler and the EL Resolver in your <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register an additional application factory in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register two managed beans in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One bean (<literal>config</literal>) defines and stores <varname>State</varname> as seen in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second bean, with the <literal>org.richfaces.ui.model.States</literal> type (<literal>state</literal>), contains the managed property <property>states</property>, which is bound to the first <literal>config</literal> bean."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use <property>state</property> bindings on the page, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To see complete example of the Login/Register dialog, see the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/stateAPI.jsf?c=stateAPI\">RichFaces Live Demo</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Identifying User Roles"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces also lets you check whether the logged-in user belongs to a certain <property>user role</property> with the <literal>rich:isUserInRole(Object)</literal> function. This function takes a String or a comma-delineated list of Strings, a Collection, etc. as arguments and returns a Boolean value."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example, imagine that you need to render some controls only for administrators. To do so, create an administrator role (<literal>admin</literal>) in your <filename>web.xml</filename> file. Then implement authorization that assigns the <literal>admin</literal> role to the user that has logged in as an administrator. Once this has been done, you can use the <literal>rich:isUserInRole(Object)</literal> function with the <varname>rendered</varname> attribute of any component. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Here, only a logged-in user with an <literal>admin</literal> role can see the text editor, which will not be rendered for users with other roles."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/Author_Group.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/Author_Group.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/Author_Group.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/Book_Info.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/Book_Info.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/Book_Info.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Developer Guide"
+msgstr ""
+
+#. Tag: subtitle
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/FAQ.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/FAQ.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/FAQ.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,989 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "FAQ"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find additional information on RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most important links for RichFaces can be found <ulink url=\"http://jboss.com/index.html?module=bb&op=viewtopic&t=104575\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where are the binary/source distributions for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Distributions are available from the <ulink url=\"http://labs.jboss.com/jbossrichfaces/downloads/\">JBoss RichFaces Download area</ulink>. The source distribution is found in the <filename>richfaces-ui-3.3.0-src.zip</filename> file. The binary distribution is in the <filename>richfaces-ui-3.3.0-bin.zip</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I manually build a RichFaces snapshot?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This <ulink url=\"http://labs.jboss.com/wiki/HowToBuildRichFacesSnapshotManually\"> wiki article</ulink> takes you through the process."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I configure Maven for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, download and install Maven. (Follow the instructions at <ulink url=\"http://maven.apache.org/download.html\">http://maven.apache.org/download.html</ulink>.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Open the <filename><Maven-Root>/conf/settings.xml</filename> file and add the following to the <literal><profile></literal> section:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following to the <literal><activeProfiles></literal> section:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is the structure of RichFaces SVN repository?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can see the structure in the RichFaces Repository Structure Overview in <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">this Wiki article</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I build <literal>richfaces-samples</literal> applications?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "he <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">RichFaces Repository Structure Overview</ulink> describes how to build <literal>richfaces-samples</literal> applications in Eclipse."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find a demo for RichFaces components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Online demo applications that showcase RichFaces features are available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also find a nightly build (in the WAR format) <ulink url=\"http://maven.exadel.com/org/richfaces/samples/richfaces-demo/3.1.0-SNAPSHOT/\">here</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Source Code (SVN) can be found <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-demo/\">in the JBoss RichFaces SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What causes the \"Prototype.Browser() function cannot be found\" error in RichFaces 3.1.0, and how do I fix it?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Your application probably uses an older version of Prototype from Tomahawk 1.1.6. RichFaces 3.1.0 uses the latest Prototype (1.5.1.1). Upgrade your version of Prototype to solve this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does the RichFaces library contain the <literal><rich:dataTable></literal> component as well as the <literal><h:dataTable></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dataTable></literal> component lets you use skins to change the look and feel of your data tables. You can see an example of the difference between these components at the <ulink url=\"http://livedemo.exadel.com/richfaces-art-datatable/\">RichFaces dataTable LiveDemo page</ulink>, or see the source code in the <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-art-datatable/\">SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I organize wizards with the <literal><rich:modalPanel></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place the <literal><a4j:include></literal> tag inside the <literal><rich:modalPanel></literal> and perform navigation inside it, as in the following example below:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I stop <literal>modalPanel</literal> closing when validation fails?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two methods available to fix this problem. The first is simply to remove the <literal>windowclose()</literal> method from the <literal>modalPanel</literal>, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that when an error presents, the panel will simply do nothing rather than closing the window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second method assumes that you use Facelets. Add the following to your <filename>default.xhtml</filename> template:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This invisible form will be refreshed on every postback, and contains a hidden field that determines the maximum severity in the message queue. If you add the following function to your JavaScript:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method reads the value of the hidden field to determine whether the last postback to the server generated any errors. This means that the <literal><a4j:commandLink></literal> or <literal><a4j:commandButton></literal> that submits your form will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method lets you easily adjust the behaviour of any JavaScript code depending on whether an error is present. See the <ulink url=\"http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4061517\">JBoss RichFaces forum</ulink> post for more information and variations on this method."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "When I use <literal>suggestionbox</literal> inside the <literal>modalPanel</literal>, the suggestion list sits behind the <literal>modalPanel</literal> and I cannot see it. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You are using an old version of RichFaces. Upgrade to the latest version to fix this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Does RichFaces work with Facelets?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes. Full Facelets support is one of RichFaces' primary features. The main <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\"> demo</ulink> is a Facelets-based application."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I create a dynamic menu with the <literal><rich:dropDownMenu></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:dropDownMenu></literal> is a standard JSF component, so creating a menu dynamically from the JavaScript code is the same as for any other JSF component."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I customize the look of a <literal>datascroller</literal> (the forward/back buttons) and replace them with images?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can. The <literal>datascroller</literal> component provides two controller groups for switching:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Page numbers</emphasis> so that you can switch to a particular page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Fast-switching</emphasis> controls: <literal>first</literal>, <literal>last</literal>, <literal>next</literal>, <literal>previous</literal>, <literal>fastforward</literal> and <literal>fastrewind</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create fast-switching controls by adding a <literal>facet</literal> component with the corresponding name:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also create disabled states with facets There are also facets used to create the disabled states: <literal>first_disabled</literal>, <literal>last_disabled</literal>, <literal>next_disabled</literal>, <literal>previous_disabled</literal>, <literal>fastforward_disabled</literal>, <literal>fastrewind_disabled</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I place simple links inside a menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include a link to an external URL, use the following approach:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see a demonstration of the <literal><rich:dropDownMenu></literal> component at the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/dropDownMenu.jsf\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal>dropDownMenu</literal> as a context menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dropDownMenu></literal> is not designed for use as a <literal>contextMenu</literal>. A <literal><rich:contextMenu></literal> component is planned for development, but is not scheduled for any currently planned version."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass my own parameters during a <literal>modalPanel</literal> opening or closing?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass your parameters during modalPanel opening or closing like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass any of your own parameters, except for the standard <literal>modalPanel</literal> parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I add a simple link to the tree node?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following simple code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Is it possible to place tabs upright in the <literal>tabPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, it is not. Try using the <literal>togglePanel</literal> instead; toggle controls can be placed anywhere in the layout."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use a <literal>commandButton</literal> within the <literal>modalPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two important rules to follow when using <literal>modalPanel</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if <literal>modalPanel</literal> has form elements (input or command elements), it must have its own form."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if the <literal>modalPanel</literal> contains a form, it must not be included in a higher-level form."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I define the currently selected tab?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I retrieve the current value from the <literal>inputNumberSlider</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can retrieve the value with the following approach:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How to apply skins to the standard input components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The answer could be found <ulink url=\"http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103494\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I remove the table border and styles from the <literal>datascroller</literal> and show only links?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To do this, you must redefine your rich* classes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I expand/collapse tree nodes from code?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/ExpandCollapseTreeNodes\">This Wiki article</ulink> has some useful information about expanding and collapsing tree nodes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the JavaScript API?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I load the Scriptaculous library?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To load the whole Scriptaculous library shipped with RichFaces, use the <literal><a4j:loadScript></literal> tag:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This command lets you load an integrated version of the library that includes all existing Scriptaculous files, <emphasis>except</emphasis> <filename>unittest.js</filename>. If you do not want to load the whole library, but wish to load a specific file (for example, <filename>effect.js</filename>), use the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you load the whole library, you do not need to load a particular file."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid the problem with text wrapping in <literal><rich:tab></literal> in Internet Explorer 7?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The problem lies with a tab height bug in IE7. (Tab height is correct in Firefox and in IE6.) To work around the bug, you can change the doctype declaration from:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see the <ulink url=\"http://jira.jboss.com/jira/browse/RF-1011\">JIRA Issue</ulink> for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the status of the <literal><rich:effect></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:effect></literal> has several callback methods such as <literal>beforeStart</literal> and <literal>afterFinish</literal>, which can be used to save the status. You can also see the <ulink url=\"http://wiki.github.com/madrobby/scriptaculous/core-effects\">Scriptaculous Core Effects</ulink> page for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I send an additional parameter to the server with <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This example code gives you one method:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the example, the <literal>onselect</literal> event sends the selected value to the server. You can pass additional fields of the selected object (which do not belong to the <literal>fetchvalue</literal> attribute) in the same way."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I set the border of <literal><rich:dataTable></literal> to 0px?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your CSS file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I dynamically create a <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is a working example:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What should I change on the server side?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The list of zones to be rerendered can be specified as an EL expression. The list of IDs is formed during the <literal>RENDER_RESPONSE</literal> <emphasis>beforePhase</emphasis>, so you can point the <literal>reRender</literal> to the <classname>Set</classname>, and fill it during a tracking request to form a list of areas which can be dynamically updated."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I check request conditions before sending a request?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To check the terms of sending a request on a client, add the <literal>onSubmit</literal> attribute to all components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this example, the <literal>doSomething()</literal> function is executed before the AJAX request, and if the function returns <literal>false</literal>, the request is not fired."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The behavior of our <literal>onsubmit</literal> attribute differs slightly from the standard <literal>onsubmit</literal>. Do not return <literal>true</literal> if you want to fire the request: <code><xxx><a4j:support event=\"onclick\" onsubmit=\"return true;\"></code> becomes <code><xxx onclick=\"return true;A4J.Submit(.... );\" ></code> and standard event processing is fired instead of the request. Only return <literal>false</literal> if your conditions were not completed, or set actions to be performed without any returned response if you do need to fire the request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What were the changes to the <varname>onComplete</varname> attribute after version 1.0?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To avoid conflict with other JavaScript attributes, we have changed the placement of a function during a Javascript call. Rather than inserting attribute contents (<code>oncomplete:anotherFunction(this)</code>), we make the function anonymous (<code>oncomplete:function(){anotherFunction(this);}</code>) so that you can insert a <emphasis>chain</emphasis> of statements into an attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The change also means that the <literal>this</literal> keyword will point to a parameter map instead of a control element. You can use <code>document.findElementById()</code> to retrieve references to this parameter map after a request is processed. Pages updated with AJAX will then reference a control removed from a DOM tree."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you are certain that your element will not be updated, you can add <literal>onsubmit</literal> to your <literal><a4j:support></literal> tag (or <literal>onclick</literal> to your <literal><a4j:commandLink/Button></literal> tag) to place a reference to a known variable, like so: <code><a4j:commandLink onclick=\"var myControl=this;\" oncomplete=\"anotherFunction(myControl)\"/></code>)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The onComplete syntax now follows this form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>event</literal> is a variable defining the location in which the JavaScript event that fires the request will be placed. <literal>data</literal> is a variable containing the deserialized value of the <varname>data</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use InvokeOnComponent with JSF 1.2?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not use <literal>invokeOnComponent</literal> for two reasons:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To retain compatibility with JSF 1.1 and MyFaces applications, since these are often used in corporate applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>invokeOnComponent</literal> works well when used to communicate between a Widget and a backed component, or to update the content of a rendered component. However, there are some limitations for more complicated use-cases implemented in RichFaces, such as making update decisions with application logic."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that you must update whole components (for example, an entire <literal>dataTable</literal>), but all AJAX core action components in that component will work correctly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid generating exceptions for the <literal><a4j:keepAlive></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember: the component stores beans in a serialized view. Your bean should implement <literal>java.io.Serializable</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "My form will not submit, or, my setter is not called after an AJAX request. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This can occur because of conversion or validation errors at submission time. To verify this, place the following update message inside a form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:message></literal> component has built-in AJAX support, and can be combined with the <ulink url=\"http://www.jsfone.com/blog/max_katz/2008/07/creating_jsf_phase_listener.html\">JSF Phase Tracker</ulink> to fix this issue, in some instances."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I create an <literal>a4j</literal> delayed render zone?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><a4j:support></literal> component has a <varname>requestDelay</varname> attribute, where you can define the delay period."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use IgnoreDupResponses and requestDelay?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>ignoreDupResponses</varname> ignores an AJAX request if a newer request exists. <varname>requestDelay</varname> defines the time delay on the client between compiling a request response and sending that response. You can find more information in <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use eventsQueue attribute?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>eventsQueue</literal> defines the name of the queue that will order upcoming AJAX requests. The queue makes certain that redundant requests are not sent. It is created and named by default. You can find more information in the section on <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use multiple <literal><a4j:status></literal> components on one page?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes, you can. You can find out more from the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/status.jsf?c=status\">JBoss RichFaces Online Demos</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal><a4j:region></literal> component inside the <literal><a4j:repeat></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, you cannot. The <literal><a4j:region></literal> component cannot work inside iteration components such as <literal><h:dataTable></literal> and <literal><a4j:repeat></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I disable skinnability?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You cannot disable skinnability, but you can use a special skin: <literal>plain</literal>. This skin has no parameters, and was created to enable you to embed RichFaces components into existing projects with their own predefined styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does my reRender fail when using hide/show components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Rerendering fails when RichFaces tries to update a component that is defined as hidden or rendered. When <literal>rendered=\"false\"</literal>, the component is not added to the DOM tree, so it cannot be updated (as per the limitations described in the AJAX Processing chapter)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The correct way to rerender a hidden or rendered component is to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Wrap the component that is to be hidden or rendered on AJAX in a wrapper component such as <literal><a4j:outputPanel></literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Set the <varname>reRender</varname> attribute on the wrapper component instead of on the component itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Fpr example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This ensures that the wrapper component presents in the DOM tree, which means that its contents can be updated dynamically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why am I seeing a <exceptionname>ResourceNotRegistered</exceptionname> Exception?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces registers its resources (for example, scripts and images) after an application is accessed, and then accesses these via a generated URL. During application development, when an application is constantly updated on the server, RichFaces may re-register its resources after every server restart, while the browser may attempt to access resources via a cached URL."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve this problem by updating the browser cache: press <keycap>CTRL</keycap>+<keycap>F5</keycap>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I reRender only a particular row(s) of a table?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>ajaxKeys</literal> attribute defines Strings that are updated after an AJAX request, and lets you update several child components separately without updating the whole page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable row selection in a scrollableDataTable using <literal>one and multi-selection rows mode</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable row selection in <literal>one and multi-selection rows mode</literal>, you must use the <varname>selection</varname> attribute. In the example code that follows, when a user submits the form, the current collection of objects selected by the user is placed in the object's property. Upon completion, the <literal><rich:modalPanel></literal> will be rendered with the selected data."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, you can create a managed bean like the one below. The <literal>takeSelection()</literal> method fills the <literal>selectedCars</literal> Array with data retrieved from the <varname>selection</varname>. The <literal>getSelectedCars()</literal> method returns <literal>selectedCars</literal> Array, which is then used to populate select rows of the <literal><rich:dataTable></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I select several rows in a <literal>scrollableDataTable</literal> and drag-and-drop them into a <literal>dataTable</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, to enable row selection, see the previous section on <xref linkend=\"RowSelectionInScrollableDataTable\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable the drag-and-drop function on a <literal>dataTable</literal>, use the <literal><rich:dragSupport></literal> and <literal><rich:dropSupport></literal> components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous example is also available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/scrollableDataTable.jsf\">RichFaces LiveDemo</ulink> site. Only one method is added where the dropped collection is stored:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of the <rich:simpleTogglePanel>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>opened</varname> attribute responsible for storing panel state, and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:simpleTogglePanel></literal> icon appears and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered between page views."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, create a managed bean like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of <rich:panelMenuGroup>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>expanded</varname> attribute and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:panelMenuGroup></literal> expands and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered across page views."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I highlight the rows of a dataTable on the mouseover event?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <literal>onRowMouseOver</literal> and <literal>onRowMouseOut</literal> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable selecting the row of a <literal><rich:dataTable></literal> when I click on it, even if I click within the bounds of an <literal><h:inputText></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following JavaScript function to enable row selection when you click on the row:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can then use <literal><a4j:support></literal> with <varname>event</varname> and <varname>onsubmit</varname> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I rerender table cells with <a4j:support>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To rerender table cells with <literal><a4j:support></literal>, set exact ID values for each component to be updated, and point this <varname>id</varname> to the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The value of the <varname>reRender</varname> attribute belonging to the <literal> <a4j:support></literal> tag defines the sections of the page that will be updated. In the previous example code, the only update made is to the <literal><h:outputText></literal> component in the footer, because its <literal>id</literal> value matches the value of the <varname>reRender</varname> attribute. You can update multiple elements on a page by listing their IDs as the value of the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I create dynamic columns?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create dynamic columns by using the <literal><rich:column></literal> with the <varname>rendered</varname> attribute. Set the value of the <varname>rendered</varname> attribute to match the ID of the dynamic cell, as in the following example code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you could create a managed bean, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use RichFaces with Trinidad?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of a basic <filename>web.xml</filename> file that integrates RichFaces with Trinidad."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why do I see a JavaScript conflict?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Richfaces 3.1.3 uses version 1.6.0 of the <filename> prototype.js</filename> instead of version 1.5.1, which has been used in earlier versions. The source of the conflict is that two versions of the prototype script are included. The first is included as a dependency of the toggle panel components, and the second is included explicitly as a link."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces 3.1.3 is bundled with the same scripts included in Prototype 1.6.0 and Scriptaculous 1.8.0:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Using Prototype with RichFaces components can be problematic because issues that were fixed in version 1.6.0 were not always patched in version 1.5.1. When version 1.5.1 is used, some RichFaces components will not work as expected."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with the Seam Framework?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To use the <literal><rich:fileUpload></literal> component with the Seam Framework, define initialization parameters for the Seam Filter in your <filename>web.xml</filename> file. The Seam Framework will then automatically set the component up for the AJAX4JSF filter at start-up time."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of defining initialization parameters:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with MyFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The order in which filters are defined and mapped in <filename>web.xml</filename> is important to integrating the <literal><rich:fileUpload></literal> component with MyFaces. The code sample that follows shows the correct order in which to define your filters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To ensure that this sequence wors correctly, map the extension filter on your Faces Servlet, not to <filename>*.jsf</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable optional object selection in <rich:suggestionbox>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:suggestionBox></literal> component provides features such as object selection. To store the selected items as objects to be accessed, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the <varname>usingSuggestObjects</varname> attribute to the <literal><rich:suggestionBox></literal> component, and define it as <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <varname>onobjectchange</varname> event attribute to store the currently-selected objects."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All of the selected objects are stored in the <literal>suggestion.SelectedItems</literal> Array. Each Array element contains <literal>text</literal> and <literal>object</literal> properties, so you can iterate this Array, retrieve objects that are not <literal>null</literal>, and retrieve the required property."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for ViewExpiredException?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This exception appears after your session has timed out. Because RichFaces 3.1 is intended for use with JavaServer Faces 1.1, <exceptionname>ViewExpiredException</exceptionname>s will not generate automatically when RichFaces is used with JavaServer Faces 1.2. To work around this limitation, add the following to your <filename>web.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for Request Errors and Session Expiration?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To redefine the standard handlers that are responsible for processing different exceptional situations, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add custom <literal>onError</literal> and <literal>onExpire</literal> handlers, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more detailed description of this process, see <xref linkend=\"RequestErrorsAndSessionExpirationHandling\" /> in the Developer Guide."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Custom <literal>onError</literal> and <literal>onExpire</literal> handlers will not work under MyFaces, because MyFaces handles exceptions with an internally-generated debug page. To prevent this behavior, use the following code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I add a cookie in an AJAX response?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The bean described below adds a cookie to an AJAX response:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you can define the cookie to be included as shown in the following example. After the <literal>test</literal> cookie is set, the value of that cookie will appear on a page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is new in AJAX4JSF 3.2.x?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces 3.2.x releases have some new features:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><a4j:portlet</literal> component has been <emphasis>deprecated</emphasis>, since JSR-301 defines a similar function for <literal>UIViewRoot</literal> components;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><rich:ajaxValidator></literal>, <literal><rich:beanValidator></literal> and <literal><rich:graphValidator></literal> validators have been added to provide different validation types."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I launch the RichFaces sample on the JBoss server?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To launch the RichFaces sample application on the JBoss server, add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass a Boolean value in the <rich:componentControl> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code shows you how to avoid requiring a Boolean value:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use <code>'block'</code> instead of <code>' '</code> to avoid <literal>invalid style</literal> CSS errors."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/Getting_Started.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/Getting_Started.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,159 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Started with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This chapter tells you how to plug RichFaces components into a JSF application. The instructions are based on a simple <emphasis>JSF with RichFaces</emphasis> creation process, from downloading the required libraries to running the application in a browser. These instructions do not depend on the integrated development environment that is in use."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Simple JSF application with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> — the simple application — is similar to a typical <emphasis>hello world</emphasis> application, with one exception: the world of RichFaces will say \"Hello!\" to the user first."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a standard JSF 1.2 project named <literal>Greeter</literal>. Include all required libraries, and continue with the instructions that follow."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Adding RichFaces libraries into the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "From the <filename>RichFaces</filename> folder where you unzipped the RichFaces binary files, open the <filename>lib</filename>. This folder contains three <filename>*.jar</filename> files with API, UI, and implementation libraries. Copy these JARs from <filename>lib</filename> to the <filename>WEB-INF/lib</filename> directory of your <application>Greeter</application> JSF application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A JSF application with RichFaces assumes that the following JARs are available in the project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-beanutils-1.7.0.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-collections-3.2.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-digester-1.8.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-logging-1.0.4.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jhighlight-1.0.jar</filename>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering RichFaces in <filename>web.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "After you add the RichFaces libraries to the project, you must register them in the project <filename>web.xml</filename> file. Add the following to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For more information about RichFaces skins, read <xref linkend=\"Skinnability\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, your <filename>web.xml</filename> should look like this:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Managed bean"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <application>RichFaces Greeter</application> application needs a managed bean. In the project's <filename>JavaSource</filename> directory, create a new managed bean named <literal>user</literal> in the <literal>demo</literal> package. Place the following code in <filename>user</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering the bean in <filename>faces-cofig.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To register the <literal>user</literal> bean, add the following to the <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Greeter index.jsp"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> has only one JSP page. Create <filename>index.jsp</filename> in the root of <literal>WEB CONTENT</literal> folder and add the following to the JSP file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The application uses three RichFaces components: <emphasis role=\"bold\"><property><rich:panel></property></emphasis> is used as visual container for information; <emphasis role=\"bold\"><property><a4j:commandButton></property></emphasis> with built-in AJAX support lets a greeting be rendered dynamically after a response returns; and <emphasis role=\"bold\"><property><a4j:form></property></emphasis> helps the button to perform the action."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces tag library should be declared on each JSP page. For XHTML pages, add the following lines to declare your tag libraries:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Now, run the application on the server by pointing your browser to the <filename>index.jsp</filename> page: <literal>http://localhost:8080/Greeter/index.jsf</literal>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "\"RichFaces Greeter\" application"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Relevant Resources Links"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"https://www.redhat.com/apps/store/developers/jboss_developer_studio.html\">JBoss Developer Studio</ulink> includes tight integration with the RichFaces component framework. <!-- The following links might be useful for those who already use this IDE and RichFaces to develop applications, and for those who wish to improve their development process. -->"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/IDE_Support.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/IDE_Support.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/IDE_Support.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Integrated Development Environment Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is supported by both <ulink url=\"http://www.redhat.com/developers/rhds/index.html\">JBoss Developer Studio 1.0.0 GA</ulink> and <ulink url=\"http://www.jboss.org/tools/index.html\">Jboss Tools</ulink>. JBoss Developer Studio is a fully packaged Integrated Development Environment (IDE) that provides full support for Java Server Faces, RichFaces, Facelets, Struts and other Web technologies. It seamlessly combines visual and source-oriented development approaches. You can add JBoss Developer Studio capabilities to any JSF project by adding the appropriate libraries and modifying configuration files as required."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/Introduction.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/Introduction.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/Introduction.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,79 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is an open source framework that adds AJAX capability into existing JSF applications without resorting to JavaScript."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces leverages aspects of the JavaServer Faces (JSF) framework, including lifecycle, validation, conversion facilities, and management of static and dynamic resources. RichFaces components with built-in AJAX support and a highly customizable look-and-feel can be easily incorporated into JSF applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces allows you to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Experience the benefits of JSF while working with AJAX. RichFaces is fully integrated into the JSF lifecycle. Where other frameworks only allow access to the managed bean facility, RichFaces lets you access the action and value change listeners, and invokes server-side validators and converters during the AJAX request-response cycle."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add AJAX capabilities to existing JSF applications. The RichFaces framework provides two component libraries (Core AJAX and UI). The Core library adds AJAX functionality to existing pages, so you need not write any JavaScript or replace existing components with new AJAX components manually. RichFaces enables page-wide rather than component-wide AJAX support, giving you the opportunity to define events on the page. <!-- An event invokes an AJAX request and areas of the page which become synchronized with the JSF Component Tree after changing the data on the server by AJAX request in accordance with events fired on the client. -->"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily create different views with a variety of components, available out-of-the-box. The RichFaces UI library contains components for adding rich user interface (UI) features to JSF applications, providing you with a broad variety of AJAX-enabled components with extensive skins support. RichFaces components are designed to integrate seamlessly with other third-party component libraries, so you have more options when you develop applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Write your own rich components with built-in AJAX support. The Component Development Kit (CDK) is constantly being expanded. It includes both code generation and templating facilities and a simple JSP-like (JavaServer Pages) syntax, letting you create first-class rich components with built-in AJAX functionality."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Package resources with application Java classes. RichFaces provides advanced support for managing different resource types, including images, JavaScript code, and CSS stylesheets. The resource framework makes it easier to include these resources in JAR files with your custom component code."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily generate binary resources. The resource framework can generate images, sounds, Excel spreadsheets, etc. in real time, so you can, for example, create images with the Java Graphics 2D library and other similar resources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customize the look and feel of your user interface with skins-based technology. RichFaces lets you easily define and manage different color schemes and other user interface parameters by using named <emphasis>skin parameters</emphasis>. This means you can access UI parameters from JSP and Java code to adjust your UI in real time. RichFaces includes a number of predefined skins to kick-start your application's development, but it is easy to create your own custom skins."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Simultaneously create and test your components, actions, listeners, and pages. RichFaces will soon include an automated testing facility to generate test cases for your component as you develop it. The testing framework tests not only the components, but also any other server-side or client-side functionality, including JavaScript code — and it will do so <emphasis>without</emphasis> deploying the test application into the Servlet container."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces UI components can be implemented immediately, right out of the box. This saves development time and gives you immediate access to RichFaces web application development features, so experience with RichFaces is fast and easy to obtain."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/Links_to_Resources.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/Links_to_Resources.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/Links_to_Resources.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,74 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Links to information resources"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Links"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/portal/jbossrichfaces/\">JBoss RichFaces</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss Forum"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://jboss.com/index.html?module=bb&op=main&c=27\">JBoss Forums</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Wiki"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/wiki/RichFaces\">RichFaces Wiki</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Blog"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "<ulink url=\"http://jroller.com/page/a4j\">RichFaces Blog</ulink>"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/Revision_History.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/Revision_History.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/Revision_History.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: member
+#, no-c-format
+msgid "JIRA corrections."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/RichFaces_Developer_Guide.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/RichFaces_Developer_Guide.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/RichFaces_Developer_Guide.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/Settings.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/Settings.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/Settings.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,334 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Settings for different environments"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces includes support for all tags (components) included in the JavaServer Faces (JSF) specification. To add RichFaces capabilities to an existing JSF project, place the RichFaces libraries into the <filename>lib</filename> directory of the project, and add filter mapping. The behavior of the existing project does not change when you add RichFaces."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Application Descriptor Parameters"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not require that any parameters be defined in your <filename>web.xml</filename>, but the RichFaces parameters listed below will help you during the development process and increase the flexibility of your RichFaces applications."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.SKIN"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The name of a skin that is used in an application. Can be a literal string with a skin name or the EL expression (<literal>#{...}</literal>) associated with a String property (skin name) of a property of a <literal>org.richfaces.framework.skin</literal> type. In the latter case, that instance is used as the current skin."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadScriptStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces script files are loaded to the application. Possible values are <literal>ALL</literal>, <literal>DEFAULT</literal> and <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadStyleStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces style files are loaded into the application. Possible values are: <literal>ALL</literal>, <literal>DEFAULT</literal>, or <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.LOGFILE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "none"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The URL of an application or a container log file (if applicable). If this parameter is set, content from the given URL is shown on a Debug page in the <literal>iframe</literal> window."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.VIEW_HANDLERS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of <literal>ViewHandler</literal> instances for inserting in a view handler chain. These handlers are inserted before the RichFaces viewhandlers, in the order they are listed. In a Facelets application, you would declare <literal>com.sun.facelets.FaceletViewHandler</literal> here instead of in the <filename>faces-config.xml</filename> file."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.CONTROL_COMPONENTS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of special <emphasis>control case</emphasis> components, such as the messages bundle loader or an alias bean component. These handlers are provided via a reflection from the static field <literal>COMPONENT_TYPE</literal>. Encoding methods for these components are always called while rendering AJAX responses, even if a component has not been updated."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_RESOURCE_DATA"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "false"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "For generated resources (such as encrypt generation data), this is encoded in the resource URL. For example, the URL of an image generated by the <classname>mediaOutput</classname> component contains the name of a generation method. Since malicious code can exploit this to create a request for any JSF bean or attribute, this parameter should be set to <literal>true</literal> in critical applications. (This fix works with Java Runtime Environment 1.4.)"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_PASSWORD"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "random"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A password used to encrypt resource data. If this is not set, a random password is used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.COMPRESS_SCRIPT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "true"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "When defined, does not allow the frameword to reformat JavaScript files. This means that the debug feature cannot be used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URLs of all generated resources. This is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.GLOBAL_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/g"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URI of all global resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SESSION_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/s"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be used to track the sessions of generated resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.DEFAULT_EXPIRE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "86400"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the period (in seconds) for which resources are cached when they are streamed back to the browser."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SERIALIZE_SERVER_STATE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "If set to <literal>true</literal>, the component state (not the tree) will be serialized before it is stored in the session. This can be useful in applications with view state that is sensitive to model changes. Alternatively, use <literal>com.sun.faces.serializeServerState</literal> and <literal> org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</literal> parameters in their respective environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>org.richfaces.SKIN</literal> is used in the same way as <literal>org.ajax4jsf.SKIN</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "org.ajax4jsf.Filter Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "log4j-init-file"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "-"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A path (relative to the web application's context) to the <filename>log4j.xml</filename> configuration file. This can be used to set up per-application custom logging."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "enable-cache"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Enables caching of framework-generated resources (JavaScript, CSS, images, etc.). However, your cached resources will not be used when attempting to debug custom JavaScript or Styles."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "forcenotrf"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Forces all JSF pages to be parsed by a HTML syntax check filter. If set to <literal>false</literal>, only AJAX responses will be parsed and converted to well-formed XML. Setting this to <literal>false</literal> can improve performance, but may also cause unexpected information to be rendered during AJAX updates."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Sun JSF RI"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces works with JavaServer Faces 1.2_13 without needing to modify additional settings."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Facelets Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces has high-level support for Facelets, regardless of the version used. However, some JSF frameworks (including Faces) require that their own <literal>ViewHandler</literal> be listed first in the <literal>ViewHandler</literal> chain. RichFaces also requires that its <literal>AjaxViewHandler</literal> be listed first, but because it is installed first, no settings will need to be altered. Where multiple frameworks are used without RichFaces, you can use the <literal>VIEW_HANDLERS</literal> parameter to define the order in which the <literal>ViewHandler</literal>s are used. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This declares that while <literal>Facelets</literal> will officially be first, <literal>AjaxViewHandler</literal> will briefly be ahead of it to perform some small, important task."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this case, you need not define <literal>FaceletViewHandler</literal> in <filename>WEB-INF/faces-config.xml</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JBoss Seam Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is compatible with <application>JBoss Seam</application> and Facelets when run within JBoss Enterprise Application Server. No additional JARs are required. All you need to do is package the RichFaces library with your application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For <application>Seam 1.2</application>, your <filename>web.xml</filename> must be as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>Seam 2.x</application> supports RichFaces Filter, so your <filename>web.xml</filename> must look like this:"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/es-ES/Technical_Requirements.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/es-ES/Technical_Requirements.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/es-ES/Technical_Requirements.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,179 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Technical Requirements"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces</application> was developed with an open architecture to ensure that it was compatible with the widest possible variety of environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This is what you need to start working with <application>RichFaces 3.3.1</application>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JavaServer Faces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java Application Server <emphasis>or</emphasis> Servlet Container"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Browser (on client side)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Java Versions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JDK 1.5 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported JavaServer Faces Implementations and Frameworks"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun JSF-RI - 1.2_12"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "MyFaces 1.2.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Facelets 1.1.1 - 1.2"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Seam 1.2. - 2.1.0"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Servers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Apache Tomcat 5.5 - 6.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "BEA WebLogic 9.1 - 10.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Resin 3.1"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Jetty 6.1.x"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun Application Server 9 (J2EE 1.5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "GlassFish (J2EE 5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JBoss 4.2.x - 5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Websphere 7.0. and higher"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Geronimo 2.0 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Browsers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6.0 - 8.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Firefox 2.0 - 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera 8.5 - 9.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Google Chrome"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This list is composed from user reports of compatibility. We assume that this list is incomplete, so the absence of your environment from the list does not necessarily mean that it is incompatible with RichFaces."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "We appreciate your feedback about compatible platforms and browsers that are not listed here. This helps us keep the list up-to-date."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/Architecture_Overview.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/Architecture_Overview.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/Architecture_Overview.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,1829 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Basic concepts of the RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces Framework is implemented as a component library that adds AJAX capabilities into existing pages. This means that you do not need to write any JavaScript code or replace existing components with new AJAX widgets. RichFaces enables page-wide AJAX support instead of the traditional component-wide support, so you can define areas of the page that will reflect changes made by AJAX events on the client."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram following shows the process in full:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Processing flow"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you use JSF tags to define sections of a JSF page that you wish to update with the results of an AJAX request. It also provides you with several options for sending AJAX requests to the server. You do not need to write any JavaScript or <literal>XMLHTTPRequest</literal> objects by hand — everything is done automatically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Architecture Overview"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following figure lists several important elements of the RichFaces Framework."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Core AJAX component structure"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Filter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To make the most of RichFaces, you should register a <literal>Filter</literal> in your application's <filename>web.xml</filename>. The <literal>Filter</literal> recognizes multiple request types. The sequence diagram in Figure 5.3 shows the differences in processing between a <emphasis>regular</emphasis> JSF request and an AJAX request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request processing sequence diagram"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In either case, the required static or dynamic resource information that your application requests is registered in the <literal>ResourceBuilder</literal> class."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When a resource request is issued, the RichFaces filter checks the <literal>Resource Cache</literal> for this resource. If it is present, the resource is returned to the client. Otherwise, the filter searches for the resource among those registered in the <literal>ResourceBuilder</literal>. If the resource is registered, the RichFaces filter requests that the <literal>ResourceBuilder</literal> creates (delivers) the resource."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram that follows illustrates the process of requesting a resource."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Resource request sequence diagram"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Action Components"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "AJAX Action components are used to send AJAX requests from the client side. There are a number of AJAX Action components, including <literal><a4j:commandButton></literal>, <literal><a4j:commandLink></literal>, <literal><a4j:poll></literal>, and <literal><a4j:support></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Containers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>AjaxContainer</literal> is an interface that defines an area on your JSF page that should be decoded during an AJAX request. <literal>AjaxViewRoot</literal> and <literal>AjaxRegion</literal> are both implementations of this interface."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JavaScript Engine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces JavaScript Engine runs on the client side, and updates different areas of your JSF page based on information from the AJAX response. This JavaScript code operates automatically, so there is no need to use it directly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors and Session Expiration Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you redefine the standard handlers responsible for processing exceptions. We recommend defining your own JavaScript, which will be executed when exceptional situations occur."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To execute your own code on the client in the event of an error during an AJAX request, you must redefine the standard <literal>A4J.AJAX.onError</literal> method like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function accepts the following as parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>req</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a parameter string of a request that calls an error"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>status</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the number of an error returned by the server"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>message</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for the given error"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, you can create your own handler that is called when timeouts, internal server errors, etc. occur."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Session Expired Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also redefine the <literal>onExpired</literal> framework method that is called on the <literal>SessionExpiration</literal> event."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Example:</emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function can take the following parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>loc</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the URL of the current page (can be updated on demand)"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>expiredMsg</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for display in the event of <literal>SessionExpiration</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customized <literal>onExpire</literal> handlers do not work under MyFaces. MyFaces handles exceptions by internally generating a debug page. To prevent this behavior, use the following:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skinnability"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you look at any CSS (Cascading Style Sheets) file in an enterprise application, you will notice how often the same color is noted. Standard CSS cannot define a particular colour abstractly as a panel header color, the background color of an active pop-up menu item, a separator color, etc. To define common interface styles, you must copy the same value multiple times, and the more interfaces you have, the more repetition is required."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, if you want to change the palette of an application, you must change all interrelating values, or your interface can appear clumsy. If a customer wants to be able to adjust their interface's look and feel in real time, you must be able to alter several CSS files, each of which will contain the same value multiple times."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve these problems with the <emphasis>skins</emphasis> that are built into and rully implemented in RichFaces. Every named skin has <emphasis>skin parameters</emphasis> that define a palette and other attributes of the user interface. By changing a few skin parameters, you can alter the appearance of dozens of components simultaneously, without interfering with interface consistency."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinnability</literal> feature cannot completely replace standard CSS, and does not eliminate its usage. Instead, it is a high-level extension of standard CSS that can be used in combination with regular CSS declarations. You can also refer to skin parameters in CSS through the JSF Expression Language. This lets you completely synchronize the appearance of all elements in your pages."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Using Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces <emphasis>skinnability</emphasis> is designed for use alongside:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "skin parameters defined in the RichFaces framework,"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "predefined CSS classes for components, and"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "user style classes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A component's color scheme can be applied to its elements using any of three style classes:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A default style class inserted into the framework"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This contains stle parameters that are linked to some constants from a skin. It is defined for every component and specifies a default level of representation. You can modify an application interface by changing the values of the skin parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A style class of skin extension"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This class name is defined for every component element, and inserted into the framework to let you define a class with the same name in your CSS files. This lets you easily extend the appearance of all components that use this class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "User style class"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use one of the <literal>styleClass</literal> parameters to define your own class for component elements. As a result, the appearance of one particular component is changed according to a CSS style parameter specified in the class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Example"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following is an example of a simple <emphasis>panel</emphasis> component:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This code generates a panel component on a page, which consists of two elements: a wrapper <literal><div></literal> element and a <literal><div></literal> element for the panel body with the specified style properties. The wrapper <literal><div></literal> element will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>dr-pnl</literal> is a CSS class that is specified in the framework via skin parameters:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>background-color</varname> is defined with <literal>generalBackgroundColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>border-color</varname> is defined with <literal>panelBorderColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change all colors for all panels on all pages by changing these skin parameter values. However, if you specify a <literal><rich:panel></literal> class on the page, its parameters are also acquired by all panels on this page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Developers can also change the style properties for panel. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous definition could add some style properties from <literal>customClass</literal> to one particular panel. As a result, we will get three styles:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skin Parameters Tables in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces provides eight predefined skin parameters (skins) at the simplest level of common customization:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "plain"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "emeraldTown"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "blueSky"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "wine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "japanCherry"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ruby"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "classic"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "deepMarine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To apply a skin, you must specify a skin name in the <varname>org.richfaces.SKIN</varname> context parameter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following table shows the values for each parameter in the <literal>blueSky</literal> skin:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Colors"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Parameter name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#BED6F8"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerGradientColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#F2F7FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#000000"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerWeightFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bold"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FFFFFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "11px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Arial, Verdana, sans-serif"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "additionalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#ECF4FE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowOpacity"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "panelBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "subBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C6DEFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabDisabledTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#8DB7F3"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "trimColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#D6E6FB"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FAE6B0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E5973E"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "selectControlColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E79A00"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0078D0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0090FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "visitedLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Fonts"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableFooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#cccccc"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableSubfooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#f1f1f1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C0C0C0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>plain</literal> skin was added in version 3.0.2. It has no parameters, and is important when embedding RichFaces components into existing projects with their own styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Creating and Using Your Own Skin File"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To create your own skin file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a file. In it, define skin constants to be used by style classes (see <xref linkend=\"SkinParametersTablesInRichFaces\" />). The name of the skin file should follow this format: <literal><name>.skin.properties</literal>. (For examples of this file, see the RichFaces predefined skin parameters: <literal>blueSky</literal>, <literal>classic</literal>, <literal>deepMarine</literal>, etc. These files are located in the <filename>richfaces-impl-xxxxx.jar</filename> archive in the <filename>/META-INF/skins</filename> folder."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the skin definition <literal><contex-param></literal> to the <filename>web.xml</filename> of your application, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place your <literal><name>.skin.properties</literal> file in either your <filename>/META-INF/skins</filename> or <filename>/WEB-INF/classes</filename> directory."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Built-in Skinnability in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you incorporate skins into your user interface (UI) design. This framework lets you use named skin parameters in your properties files to control skin appearance consistently across a set of components. You can see examples of predefined skins at: <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">http://livedemo.exadel.com/richfaces-demo/ </ulink>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Skins let you define a style in which to render standard JSF components and custom JSF components built with RichFaces. You can experiment with skins by following these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a custom render kit and register it in the <filename>faces-config.xml</filename> like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, create and register custom renderers for the component based on the look-and-feel predefined variables:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, place a properties file with skin parameters into the class path root. There are two requirements for the properties file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The file must be named <filename><replaceable>skinName</replaceable>.skin.properties</filename>. In this case, we would call it <literal>newskin.skin.properties</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The first line in this file should be <literal>render.kit=<replaceable>render-kit-id</replaceable></literal>. In this case, we would use <literal>render.kit=NEW_SKIN</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "More information about creating custom renderers can be found at: <ulink url=\"http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html\">http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Changing skin in runtime"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change skins during runtime by defining the following EL-expression in your <filename>web.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinBean</literal> code looks like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also set the <varname>skin</varname> property's initial value in the configuration file. To set <literal>classic</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also change the properties of the default skin. To do so, edit the properties of the default skin. The following shows you example page code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The above code will generate the following list of options:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Controls Skinning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This feature is designed to unify the look and feel of standard HTML elements and RichFaces components. Skinning can be applied to all controls on a page based on element names and attribute types (where applicable). This feature also provides a set of CSS styles that let skins be applied by assigning <literal>rich-*</literal> classes to particular elements, or to a container of elements that nests controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard Controls Skinning provides two levels of skinning: <emphasis>Basic</emphasis> and <emphasis>Extended</emphasis>. The level used depends on the browser type detected. If the browser type cannot be detected, <literal>Extended</literal> is used. However, if you want to explicitly specify the level to be applied, add a <varname></varname> context parameter to your <filename>web.xml</filename> and set the value to either <literal>basic</literal> or <literal>extended</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Basic</emphasis> level provides customization for only basic style properties. Basic skinning is applied to the following browsers:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in BackCompat mode (see <ulink url=\"http://msdn2.microsoft.com/en-us/library/ms533687(VS.85).aspx\">document.compatMode property in MSDN</ulink>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Extended</emphasis> level introduces a broader number of style properties on top of basic skinning, and is applied to browsers with rich visual styling control capabilities. The following browsers support Extended skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Mozilla Firefox"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in Standards-compliant mode (CSS1Compat mode)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following elements can be modified with skins:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>input</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>select</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>textarea</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>keygen</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>isindex</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>legend</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>fieldset</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>hr</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>a</literal> (together with the <literal>a:hover</literal>, <literal>a:visited</literal> pseudo-elements)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two ways to initialize skinning for standard HTML controls:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. This method implies that skinning style properties are applied per-element and attribute type (where applicable). No additional steps are required. See the <xref linkend=\"BasicLevel\" /> and <xref linkend=\"ExtendedLevel\" /> tables for elements to which skinning can be applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. When enabled, you are provided with a set of predefined CSS classes to apply skins to your HTML components."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enabling <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> provides you style classes that can be applied to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "basic elements nested within elements with a <emphasis>rich-container</emphasis> class. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements with a class name that corresponds to one of the basic element names or types are mapped with the <literal>rich-<elementName>[-<elementType>]</literal> scheme, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements are given classes depending upon their <literal>link</literal> type and pseudo-class name, for example, <literal>rich-link</literal>, <literal>rich-link-hover</literal>, <literal>rich-link-visited</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The predefined rich CSS classes provided can be used as classes for both basic and complex HTML elements."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code snippet shows several elements as an example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more thorough look at standard component skinning, we recommend exploring the CSS files located in the <filename>ui/core/src/main/resources/org/richfaces/</filename> directory of the RichFaces SVN repository."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex and legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "CSS Properties"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-size"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-family"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for hr"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:hover"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColorgeneralLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Elements Skin Bindings for .rich-input, .rich-select, .rich-textarea, .rich-keygen, .rich-isindex, .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-fieldset"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-hr"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-width"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-style"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "solid"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:hover"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin parameters/Value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "inset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-color"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "no-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-position"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px 1px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-edit"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "editBackgroundColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-error"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "warningBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding-left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "7px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button, .rich-button-disabled, .rich-button-over"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "2px 10px 2px 10px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "text-align"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "cursor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "pointer"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "repeat-x"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "top left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button-press"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bottom left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-container fieldset, .rich-fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "10px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-weight"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-form"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "0px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "margin"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Extended level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-image"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for button[type=button], button[type=reset], button[type=submit], input[type=reset], input[type=submit], input[type=button]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button[disabled], .rich-container *|button[disabled], .rich-button-disabled"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonDisabledBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for .rich-button-disabled, .rich-container button[type=\"button\"][disabled], .rich-button-button-disabled, .rich-container button[type=\"reset\"][disabled], .rich-button-reset-disabled, .rich-container button[type=\"submit\"][disabled], .rich-button-submit-disabled, .rich-container input[type=\"reset\"][disabled], .rich-input-reset-disabled, .rich-container input[type=\"submit\"][disabled], .rich-input-submit-disabled, .rich-container input[type=\"button\"][disabled], .rich-input-button-disabled"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *button[type=\"button\"][disabled], button[type=\"reset\"][disabled], button[type=\"submit\"][disabled], input[type=\"reset\"][disabled], input[type=\"submit\"][disabled], input[type=\"button\"][disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.InputBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for textarea[type=textarea], input[type=text], input[type=password], select"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea[disabled], .rich-container *|textarea[disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "textarea[type=\"textarea\"][disabled], input[type=\"text\"][disabled], input[type=\"password\"][disabled]"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The basic skinning level can fail if the <literal>ajaxPortlet</literal> is configured as follows:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Client-side Script for Extended Skinning Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Extended skinning of standard HTML controls is applied automatically: the browser type is detected, and if a browser does not fully support extended skinning, only basic skinning is applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are some problems with standard HTML controls in certain browsers (Opera and Safari) that may cause problems if you wish to skin your RichFaces components and standard HTML controls manually."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable skinnability, set the <varname>org.richfaces.LoadStyleStrategy</varname> parameter to <literal>NONE</literal> in your <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You should also include the style sheets that apply skins to RichFaces components and standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To work around the problem of extended skinning in Opera and Safari, the <filename>skinning.js</filename> client script is added to the RichFaces library. This detects the browser type and enables extended skinning only for browsers that fully support it."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Activate the script by inserting the following JavaScript into your page:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When no script-loading strategy is used and extended skinning is enabled, a warning message appears in the console."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also specify the <varname>media</varname> attribute in the <literal>link</literal> tag. This adds the <filename>extended_both.xcss</filename> style sheet to <literal>rich-extended-skinning</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include your style sheets to the page when automatic skinnability is disabled, add the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Base64 encoder now uses <literal>!</literal> instead of <literal>.</literal>, so remember to use the <literal>a4j/versionXXX</literal> resources prefix instead of <literal>a4j_versionXXX</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "XCSS File Format"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Cross-site Cascading Style Sheet (XCSS) files are the core of RichFaces component skinnability. XCSS is XML-formatted CSS that extends the skinning process. RichFaces parses the XCSS file containing all look and feel parameters of a particular component and compiles the information into a standard CSS file that can be recognized by a web browser."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The XCSS file contains CSS properties and skin parameter mappings. Mapping a CSS selector to a skin parameter can be done with <literal>< u:selector ></literal> and <literal>< u:style></literal> XML tags, which define the mapping structure, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "During processing, this code will be parsed and assembled into a standard CSS format, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>name</varname> attribute of <literal><u:selector></literal> defines the CSS selector, while the <varname>name</varname> attribute of the <literal><u:style></literal> tag defines the skin constant that is mapped to a CSS property. You can also use the <varname>value</varname> attribute of the <literal><u:style></literal> tag to assign a value to a CSS property."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "CSS selectors with identical skin properties can be included in a comma-separated list:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Plug-n-Skin</emphasis> lets you easily create, customize, and plug in a custom skin to your project. You can create skins based on the parameters of predefined RichFaces skins. Plug-n-Skin also lets you unify the appearance of rich controls with standard HTML elements. This section contains step-by-step instructions for creating your own skin with Plug-n-Skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, use Maven to create a template for your new skin. (You can find more information about configuring Maven for RichFaces in the <!-- #modify add info? --><ulink url=\"http://wiki.jboss.org/wiki/HowToConfigureMavenForRichFaces\">JBoss wiki article</ulink>. These Maven instructions can be copied and pasted into the command line interface to execute them."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Primary keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>archetypeVersion</varname> — indicates the RichFaces version; for example, <literal>3.3.1.GA</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>artifactId</varname> — the artifact ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>groupId</varname> — the group ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>version</varname> — the version of the project you create. By default, this is set to <literal>1.0.-SNAPSHOT</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This operation creates a directory named after your <literal>ARTIFACT-ID</literal>. The directory contains a template of the Maven project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following steps will guide you though creating of the skin itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Run the following command from the root directory of the Maven project. (This directory will contain your <filename>pom.xml</filename> file.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>name</varname> — defines the name of the new skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>package</varname> — the base package of the skin. By default, the project's <literal>groupId</literal> is used."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Additional optional keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — defines the name of the base skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>createExt</varname> — if set to <literal>true</literal>, extended CSS classes are added. For more information, please, see <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once these operations are complete, the following files and folders should have been created:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImage.java</filename> — the base class used to store images. Location: <filename>\\src\\main\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImageTest.java</filename> — a test version of a class that stores images. Location: <filename>\\src\\test\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>XCSS files</filename> — XCSS files define the new look of RichFaces components affected by the new skin. Location: \"\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.properties</filename> — a file that contains the new skin's properties. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following properties are used to configure the <filename>SKIN-NAME.properties</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — the name of the skin to be used as a basis for your own skin. The look of the skin you define will be affected by the new style properties."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>generalStyleSheet</varname> — a path to the style sheet (<filename>SKIN-NAME.xcss</filename>) that imports your component's style sheets to be modified by the new skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>extendedStyleSheet</varname> — the path to a style sheet that is used to unify the appearance of RichFaces components and standard HTML controls. For additional information, read <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>gradientType</varname> — a predefined property to set the type of gradient applied to the new skin. Possible values are <literal>glass</literal>, <literal>plastic</literal>, <literal>plain</literal>. More information on gradient implementation you can find further in this chapter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.xcss</filename> — an XCSS file that imports the component's XCSS files to be modified by the new skin. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>XCSS files</literal> — creates the XCSS files that determine styles for standard controls (<filename>extended_classes.xcss</filename> and <filename>extended.xcss</filename>), if the <varname>createExt</varname> key is set to <literal>true</literal>. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-ext.xcss</filename> — creates the <filename>SKIN-NAME-ext.xcss</filename> file that imports defining styles for standard controls if <varname>createExt</varname> is set to <literal>true</literal>. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-resources.xml</filename> — contains descriptions of all files listed previously. Location: <filename>src\\main\\config\\resources</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now start editing the XCSS files located in <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>. Assign new style properties to your selectors (listed in the XCSS files) in either of the following ways:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard CSS coding approach (that is, add CSS properties to the selectors). Remember that the selectors must be within <literal><f:verbatim> </f:verbatim></literal> tags. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "XCSS coding approach (the usual method of creating XCSS files in RichFaces). XCSS tags must be placed <emphasis>outside</emphasis> <literal><f:verbatim> </f:verbatim></literal> tags."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once you have performed these steps and edited the XCSS files, build the new skin and plug it into the project. To build the skin, execute the following command from the root directory of your skin project (the directory that contains your <filename>pom.xml</filename> file):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Plug-n-skin feature also has a number of predefined gradients. The following code can be used to apply a gradient:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>background-image</varname> CSS property is defined with <literal><f:resource f:key=\"org.richfaces.renderkit.html.CustomizeableGradient\"></literal>, which sets the gradient. The gradient type can be specified in the <filename>SKIN-NAME.properties</filename> with the <varname>gradientType</varname> property, which can be set to <literal>glass</literal>, <literal>plastic</literal>, or <literal>plain</literal>. The gradient can then be adjusted with the <varname>baseColor</varname>, <varname>gradientColor</varname>, <varname>gradientHeight</varname>, <varname>valign</varname> attributes, as seen in the previous code snippet."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now use your newly-created skin in your project by adding your new skin parameters to the <filename>web.xml</filename> file, and placing the JAR file containing your skin (located in the <filename>target</filename> directory of your skin project) in the <filename>\\WebContent\\WEB-INF\\lib\\</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Details of Usage"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This section covers some practical aspects of Plug-n-Skin implementation. We assume that you have read the section of the guide describing the Plug-n-Skin prototype creation process."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, we must create a new skin (as described in the previous section). The following creates a template of the new skin project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now browse the <filename>P-n-S</filename> directory to view the files and folders created."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use Maven to add all required files to the skin project, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As mentioned in the previous section, <!-- #modify '-D' typo? --><literal>-DbaseSkin</literal> defines the RichFaces built-in skin to use as a base, and <literal>-DcreateExt=true</literal>, which determines that the new skin will include XCSS files that unify the appearance of the rich components and the standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once your resources have been created, you can begin refining the newly-created skin. Begin by editing the rich components' XCSS files."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example of the Plug-n-Skin feature, we will edit some <literal><rich:calendar></literal> style attributes and some basic HTML controls. We will show you how to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor the background of the current day in the <literal><rich:calendar></literal>;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor a standard HTML submit button;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To edit <literal><rich:properties></literal>'s style properties, you must open the <filename>calendar.xcss</filename> file, located in <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the <filename>calendar.xcss</filename> file, find the <literal>.rich-calendar-today</literal> selector and amend it as follows:<literal>background-color: #075ad1;</literal>. This will change the background color of the current day."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next we will change the font style of a standard HTML <emphasis>submit</emphasis> button. Open the <filename>extended.xcss</filename> file from the <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename> directory and insert <literal>font-weight: bold;</literal> between the curly braces of these selectors, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The desired changes have now been made, and you can proceed to building the new <literal>PlugnSkinDemo</literal> skin and importing it into the project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Build the skin by executing <command>mvn clean install</command> from the <filename>P-n-S</filename> directory. This creates a <filename>target</filename> directory containing a JAR file with a newly-compiled skin. In our case, the file is named <filename>P-n-S-1.0.-SNAPSHOT.jar</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, import the new <literal>PlugnSkinDemo</literal> skin into your project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Copy the <filename>P-n-S-1.0.-SNAPSHOT.jar</filename> file to the <filename>\\WebContent\\WEB-INF\\lib\\</filename> directory."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the name of the new skin to the <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember, standard controls skinning must be enabled in <filename>web.xml</filename>. Add the following to enable standard controls skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The results of each alteration to the skin are shown in the figures that follow:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin feature in action."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "State Manager API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JSF has an advanced navigation mechanism that lets you define <emphasis>navigation</emphasis> from view to view. In a web application, navigation occurs when a user changes from one page to another by clicking on a button, a hyperlink, or another command component. There is no switch mechanism between some logical states of the same view. For example, in <emphasis>Login/Register dialog</emphasis>, an existing user signs in with his user name and password, but if a new user attempts to register, an additional field (<literal>Confirm</literal>) is displayed, and button labels and methods are changed when the user clicks the <guilabel>To register</guilabel> link:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Login Dialog"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Register Dialog"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>RichFaces State API</emphasis> lets you easily define a set of states for pages, and properties for these states."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>States</varname> class interfaces with a <property>map</property>, where the <methodname>keySet</methodname> defines the State name and the <methodname>entrySet</methodname> is a <varname>State</varname> <property>map</property>. The <varname>State</varname> <property>map</property> defines the properties, method bindings, or constant state variables of a key or object, where these values may change depending on the active State."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces State API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One of the most convenient features of the RichFaces State API is the ability to navigate between <varname>State</varname>s. The API implements changes in <varname>State</varname> through standard JSF navigation. When the action component returns an outcome, the JSF navigation handler (extended through the RichFaces State API) checks whether the outcome is registered as a <emphasis><varname>State</varname> change outcome</emphasis>. If <literal>true</literal>, the corresponding <varname>State</varname> is activated. If <literal>false</literal>, standard navigation handling is called."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Implement the RichFaces State API like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register the State Navigation Handler and the EL Resolver in your <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register an additional application factory in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register two managed beans in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One bean (<literal>config</literal>) defines and stores <varname>State</varname> as seen in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second bean, with the <literal>org.richfaces.ui.model.States</literal> type (<literal>state</literal>), contains the managed property <property>states</property>, which is bound to the first <literal>config</literal> bean."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use <property>state</property> bindings on the page, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To see complete example of the Login/Register dialog, see the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/stateAPI.jsf?c=stateAPI\">RichFaces Live Demo</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Identifying User Roles"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces also lets you check whether the logged-in user belongs to a certain <property>user role</property> with the <literal>rich:isUserInRole(Object)</literal> function. This function takes a String or a comma-delineated list of Strings, a Collection, etc. as arguments and returns a Boolean value."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example, imagine that you need to render some controls only for administrators. To do so, create an administrator role (<literal>admin</literal>) in your <filename>web.xml</filename> file. Then implement authorization that assigns the <literal>admin</literal> role to the user that has logged in as an administrator. Once this has been done, you can use the <literal>rich:isUserInRole(Object)</literal> function with the <varname>rendered</varname> attribute of any component. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Here, only a logged-in user with an <literal>admin</literal> role can see the text editor, which will not be rendered for users with other roles."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/Author_Group.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/Author_Group.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/Author_Group.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/Book_Info.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/Book_Info.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/Book_Info.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Developer Guide"
+msgstr ""
+
+#. Tag: subtitle
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/FAQ.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/FAQ.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/FAQ.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,989 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "FAQ"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find additional information on RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most important links for RichFaces can be found <ulink url=\"http://jboss.com/index.html?module=bb&op=viewtopic&t=104575\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where are the binary/source distributions for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Distributions are available from the <ulink url=\"http://labs.jboss.com/jbossrichfaces/downloads/\">JBoss RichFaces Download area</ulink>. The source distribution is found in the <filename>richfaces-ui-3.3.0-src.zip</filename> file. The binary distribution is in the <filename>richfaces-ui-3.3.0-bin.zip</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I manually build a RichFaces snapshot?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This <ulink url=\"http://labs.jboss.com/wiki/HowToBuildRichFacesSnapshotManually\"> wiki article</ulink> takes you through the process."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I configure Maven for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, download and install Maven. (Follow the instructions at <ulink url=\"http://maven.apache.org/download.html\">http://maven.apache.org/download.html</ulink>.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Open the <filename><Maven-Root>/conf/settings.xml</filename> file and add the following to the <literal><profile></literal> section:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following to the <literal><activeProfiles></literal> section:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is the structure of RichFaces SVN repository?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can see the structure in the RichFaces Repository Structure Overview in <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">this Wiki article</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I build <literal>richfaces-samples</literal> applications?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "he <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">RichFaces Repository Structure Overview</ulink> describes how to build <literal>richfaces-samples</literal> applications in Eclipse."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find a demo for RichFaces components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Online demo applications that showcase RichFaces features are available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also find a nightly build (in the WAR format) <ulink url=\"http://maven.exadel.com/org/richfaces/samples/richfaces-demo/3.1.0-SNAPSHOT/\">here</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Source Code (SVN) can be found <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-demo/\">in the JBoss RichFaces SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What causes the \"Prototype.Browser() function cannot be found\" error in RichFaces 3.1.0, and how do I fix it?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Your application probably uses an older version of Prototype from Tomahawk 1.1.6. RichFaces 3.1.0 uses the latest Prototype (1.5.1.1). Upgrade your version of Prototype to solve this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does the RichFaces library contain the <literal><rich:dataTable></literal> component as well as the <literal><h:dataTable></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dataTable></literal> component lets you use skins to change the look and feel of your data tables. You can see an example of the difference between these components at the <ulink url=\"http://livedemo.exadel.com/richfaces-art-datatable/\">RichFaces dataTable LiveDemo page</ulink>, or see the source code in the <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-art-datatable/\">SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I organize wizards with the <literal><rich:modalPanel></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place the <literal><a4j:include></literal> tag inside the <literal><rich:modalPanel></literal> and perform navigation inside it, as in the following example below:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I stop <literal>modalPanel</literal> closing when validation fails?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two methods available to fix this problem. The first is simply to remove the <literal>windowclose()</literal> method from the <literal>modalPanel</literal>, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that when an error presents, the panel will simply do nothing rather than closing the window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second method assumes that you use Facelets. Add the following to your <filename>default.xhtml</filename> template:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This invisible form will be refreshed on every postback, and contains a hidden field that determines the maximum severity in the message queue. If you add the following function to your JavaScript:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method reads the value of the hidden field to determine whether the last postback to the server generated any errors. This means that the <literal><a4j:commandLink></literal> or <literal><a4j:commandButton></literal> that submits your form will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method lets you easily adjust the behaviour of any JavaScript code depending on whether an error is present. See the <ulink url=\"http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4061517\">JBoss RichFaces forum</ulink> post for more information and variations on this method."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "When I use <literal>suggestionbox</literal> inside the <literal>modalPanel</literal>, the suggestion list sits behind the <literal>modalPanel</literal> and I cannot see it. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You are using an old version of RichFaces. Upgrade to the latest version to fix this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Does RichFaces work with Facelets?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes. Full Facelets support is one of RichFaces' primary features. The main <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\"> demo</ulink> is a Facelets-based application."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I create a dynamic menu with the <literal><rich:dropDownMenu></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:dropDownMenu></literal> is a standard JSF component, so creating a menu dynamically from the JavaScript code is the same as for any other JSF component."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I customize the look of a <literal>datascroller</literal> (the forward/back buttons) and replace them with images?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can. The <literal>datascroller</literal> component provides two controller groups for switching:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Page numbers</emphasis> so that you can switch to a particular page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Fast-switching</emphasis> controls: <literal>first</literal>, <literal>last</literal>, <literal>next</literal>, <literal>previous</literal>, <literal>fastforward</literal> and <literal>fastrewind</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create fast-switching controls by adding a <literal>facet</literal> component with the corresponding name:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also create disabled states with facets There are also facets used to create the disabled states: <literal>first_disabled</literal>, <literal>last_disabled</literal>, <literal>next_disabled</literal>, <literal>previous_disabled</literal>, <literal>fastforward_disabled</literal>, <literal>fastrewind_disabled</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I place simple links inside a menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include a link to an external URL, use the following approach:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see a demonstration of the <literal><rich:dropDownMenu></literal> component at the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/dropDownMenu.jsf\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal>dropDownMenu</literal> as a context menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dropDownMenu></literal> is not designed for use as a <literal>contextMenu</literal>. A <literal><rich:contextMenu></literal> component is planned for development, but is not scheduled for any currently planned version."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass my own parameters during a <literal>modalPanel</literal> opening or closing?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass your parameters during modalPanel opening or closing like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass any of your own parameters, except for the standard <literal>modalPanel</literal> parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I add a simple link to the tree node?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following simple code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Is it possible to place tabs upright in the <literal>tabPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, it is not. Try using the <literal>togglePanel</literal> instead; toggle controls can be placed anywhere in the layout."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use a <literal>commandButton</literal> within the <literal>modalPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two important rules to follow when using <literal>modalPanel</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if <literal>modalPanel</literal> has form elements (input or command elements), it must have its own form."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if the <literal>modalPanel</literal> contains a form, it must not be included in a higher-level form."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I define the currently selected tab?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I retrieve the current value from the <literal>inputNumberSlider</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can retrieve the value with the following approach:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How to apply skins to the standard input components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The answer could be found <ulink url=\"http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103494\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I remove the table border and styles from the <literal>datascroller</literal> and show only links?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To do this, you must redefine your rich* classes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I expand/collapse tree nodes from code?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/ExpandCollapseTreeNodes\">This Wiki article</ulink> has some useful information about expanding and collapsing tree nodes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the JavaScript API?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I load the Scriptaculous library?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To load the whole Scriptaculous library shipped with RichFaces, use the <literal><a4j:loadScript></literal> tag:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This command lets you load an integrated version of the library that includes all existing Scriptaculous files, <emphasis>except</emphasis> <filename>unittest.js</filename>. If you do not want to load the whole library, but wish to load a specific file (for example, <filename>effect.js</filename>), use the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you load the whole library, you do not need to load a particular file."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid the problem with text wrapping in <literal><rich:tab></literal> in Internet Explorer 7?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The problem lies with a tab height bug in IE7. (Tab height is correct in Firefox and in IE6.) To work around the bug, you can change the doctype declaration from:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see the <ulink url=\"http://jira.jboss.com/jira/browse/RF-1011\">JIRA Issue</ulink> for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the status of the <literal><rich:effect></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:effect></literal> has several callback methods such as <literal>beforeStart</literal> and <literal>afterFinish</literal>, which can be used to save the status. You can also see the <ulink url=\"http://wiki.github.com/madrobby/scriptaculous/core-effects\">Scriptaculous Core Effects</ulink> page for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I send an additional parameter to the server with <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This example code gives you one method:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the example, the <literal>onselect</literal> event sends the selected value to the server. You can pass additional fields of the selected object (which do not belong to the <literal>fetchvalue</literal> attribute) in the same way."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I set the border of <literal><rich:dataTable></literal> to 0px?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your CSS file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I dynamically create a <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is a working example:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What should I change on the server side?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The list of zones to be rerendered can be specified as an EL expression. The list of IDs is formed during the <literal>RENDER_RESPONSE</literal> <emphasis>beforePhase</emphasis>, so you can point the <literal>reRender</literal> to the <classname>Set</classname>, and fill it during a tracking request to form a list of areas which can be dynamically updated."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I check request conditions before sending a request?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To check the terms of sending a request on a client, add the <literal>onSubmit</literal> attribute to all components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this example, the <literal>doSomething()</literal> function is executed before the AJAX request, and if the function returns <literal>false</literal>, the request is not fired."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The behavior of our <literal>onsubmit</literal> attribute differs slightly from the standard <literal>onsubmit</literal>. Do not return <literal>true</literal> if you want to fire the request: <code><xxx><a4j:support event=\"onclick\" onsubmit=\"return true;\"></code> becomes <code><xxx onclick=\"return true;A4J.Submit(.... );\" ></code> and standard event processing is fired instead of the request. Only return <literal>false</literal> if your conditions were not completed, or set actions to be performed without any returned response if you do need to fire the request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What were the changes to the <varname>onComplete</varname> attribute after version 1.0?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To avoid conflict with other JavaScript attributes, we have changed the placement of a function during a Javascript call. Rather than inserting attribute contents (<code>oncomplete:anotherFunction(this)</code>), we make the function anonymous (<code>oncomplete:function(){anotherFunction(this);}</code>) so that you can insert a <emphasis>chain</emphasis> of statements into an attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The change also means that the <literal>this</literal> keyword will point to a parameter map instead of a control element. You can use <code>document.findElementById()</code> to retrieve references to this parameter map after a request is processed. Pages updated with AJAX will then reference a control removed from a DOM tree."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you are certain that your element will not be updated, you can add <literal>onsubmit</literal> to your <literal><a4j:support></literal> tag (or <literal>onclick</literal> to your <literal><a4j:commandLink/Button></literal> tag) to place a reference to a known variable, like so: <code><a4j:commandLink onclick=\"var myControl=this;\" oncomplete=\"anotherFunction(myControl)\"/></code>)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The onComplete syntax now follows this form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>event</literal> is a variable defining the location in which the JavaScript event that fires the request will be placed. <literal>data</literal> is a variable containing the deserialized value of the <varname>data</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use InvokeOnComponent with JSF 1.2?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not use <literal>invokeOnComponent</literal> for two reasons:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To retain compatibility with JSF 1.1 and MyFaces applications, since these are often used in corporate applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>invokeOnComponent</literal> works well when used to communicate between a Widget and a backed component, or to update the content of a rendered component. However, there are some limitations for more complicated use-cases implemented in RichFaces, such as making update decisions with application logic."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that you must update whole components (for example, an entire <literal>dataTable</literal>), but all AJAX core action components in that component will work correctly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid generating exceptions for the <literal><a4j:keepAlive></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember: the component stores beans in a serialized view. Your bean should implement <literal>java.io.Serializable</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "My form will not submit, or, my setter is not called after an AJAX request. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This can occur because of conversion or validation errors at submission time. To verify this, place the following update message inside a form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:message></literal> component has built-in AJAX support, and can be combined with the <ulink url=\"http://www.jsfone.com/blog/max_katz/2008/07/creating_jsf_phase_listener.html\">JSF Phase Tracker</ulink> to fix this issue, in some instances."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I create an <literal>a4j</literal> delayed render zone?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><a4j:support></literal> component has a <varname>requestDelay</varname> attribute, where you can define the delay period."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use IgnoreDupResponses and requestDelay?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>ignoreDupResponses</varname> ignores an AJAX request if a newer request exists. <varname>requestDelay</varname> defines the time delay on the client between compiling a request response and sending that response. You can find more information in <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use eventsQueue attribute?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>eventsQueue</literal> defines the name of the queue that will order upcoming AJAX requests. The queue makes certain that redundant requests are not sent. It is created and named by default. You can find more information in the section on <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use multiple <literal><a4j:status></literal> components on one page?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes, you can. You can find out more from the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/status.jsf?c=status\">JBoss RichFaces Online Demos</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal><a4j:region></literal> component inside the <literal><a4j:repeat></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, you cannot. The <literal><a4j:region></literal> component cannot work inside iteration components such as <literal><h:dataTable></literal> and <literal><a4j:repeat></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I disable skinnability?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You cannot disable skinnability, but you can use a special skin: <literal>plain</literal>. This skin has no parameters, and was created to enable you to embed RichFaces components into existing projects with their own predefined styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does my reRender fail when using hide/show components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Rerendering fails when RichFaces tries to update a component that is defined as hidden or rendered. When <literal>rendered=\"false\"</literal>, the component is not added to the DOM tree, so it cannot be updated (as per the limitations described in the AJAX Processing chapter)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The correct way to rerender a hidden or rendered component is to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Wrap the component that is to be hidden or rendered on AJAX in a wrapper component such as <literal><a4j:outputPanel></literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Set the <varname>reRender</varname> attribute on the wrapper component instead of on the component itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Fpr example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This ensures that the wrapper component presents in the DOM tree, which means that its contents can be updated dynamically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why am I seeing a <exceptionname>ResourceNotRegistered</exceptionname> Exception?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces registers its resources (for example, scripts and images) after an application is accessed, and then accesses these via a generated URL. During application development, when an application is constantly updated on the server, RichFaces may re-register its resources after every server restart, while the browser may attempt to access resources via a cached URL."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve this problem by updating the browser cache: press <keycap>CTRL</keycap>+<keycap>F5</keycap>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I reRender only a particular row(s) of a table?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>ajaxKeys</literal> attribute defines Strings that are updated after an AJAX request, and lets you update several child components separately without updating the whole page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable row selection in a scrollableDataTable using <literal>one and multi-selection rows mode</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable row selection in <literal>one and multi-selection rows mode</literal>, you must use the <varname>selection</varname> attribute. In the example code that follows, when a user submits the form, the current collection of objects selected by the user is placed in the object's property. Upon completion, the <literal><rich:modalPanel></literal> will be rendered with the selected data."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, you can create a managed bean like the one below. The <literal>takeSelection()</literal> method fills the <literal>selectedCars</literal> Array with data retrieved from the <varname>selection</varname>. The <literal>getSelectedCars()</literal> method returns <literal>selectedCars</literal> Array, which is then used to populate select rows of the <literal><rich:dataTable></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I select several rows in a <literal>scrollableDataTable</literal> and drag-and-drop them into a <literal>dataTable</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, to enable row selection, see the previous section on <xref linkend=\"RowSelectionInScrollableDataTable\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable the drag-and-drop function on a <literal>dataTable</literal>, use the <literal><rich:dragSupport></literal> and <literal><rich:dropSupport></literal> components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous example is also available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/scrollableDataTable.jsf\">RichFaces LiveDemo</ulink> site. Only one method is added where the dropped collection is stored:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of the <rich:simpleTogglePanel>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>opened</varname> attribute responsible for storing panel state, and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:simpleTogglePanel></literal> icon appears and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered between page views."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, create a managed bean like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of <rich:panelMenuGroup>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>expanded</varname> attribute and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:panelMenuGroup></literal> expands and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered across page views."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I highlight the rows of a dataTable on the mouseover event?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <literal>onRowMouseOver</literal> and <literal>onRowMouseOut</literal> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable selecting the row of a <literal><rich:dataTable></literal> when I click on it, even if I click within the bounds of an <literal><h:inputText></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following JavaScript function to enable row selection when you click on the row:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can then use <literal><a4j:support></literal> with <varname>event</varname> and <varname>onsubmit</varname> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I rerender table cells with <a4j:support>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To rerender table cells with <literal><a4j:support></literal>, set exact ID values for each component to be updated, and point this <varname>id</varname> to the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The value of the <varname>reRender</varname> attribute belonging to the <literal> <a4j:support></literal> tag defines the sections of the page that will be updated. In the previous example code, the only update made is to the <literal><h:outputText></literal> component in the footer, because its <literal>id</literal> value matches the value of the <varname>reRender</varname> attribute. You can update multiple elements on a page by listing their IDs as the value of the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I create dynamic columns?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create dynamic columns by using the <literal><rich:column></literal> with the <varname>rendered</varname> attribute. Set the value of the <varname>rendered</varname> attribute to match the ID of the dynamic cell, as in the following example code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you could create a managed bean, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use RichFaces with Trinidad?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of a basic <filename>web.xml</filename> file that integrates RichFaces with Trinidad."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why do I see a JavaScript conflict?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Richfaces 3.1.3 uses version 1.6.0 of the <filename> prototype.js</filename> instead of version 1.5.1, which has been used in earlier versions. The source of the conflict is that two versions of the prototype script are included. The first is included as a dependency of the toggle panel components, and the second is included explicitly as a link."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces 3.1.3 is bundled with the same scripts included in Prototype 1.6.0 and Scriptaculous 1.8.0:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Using Prototype with RichFaces components can be problematic because issues that were fixed in version 1.6.0 were not always patched in version 1.5.1. When version 1.5.1 is used, some RichFaces components will not work as expected."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with the Seam Framework?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To use the <literal><rich:fileUpload></literal> component with the Seam Framework, define initialization parameters for the Seam Filter in your <filename>web.xml</filename> file. The Seam Framework will then automatically set the component up for the AJAX4JSF filter at start-up time."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of defining initialization parameters:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with MyFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The order in which filters are defined and mapped in <filename>web.xml</filename> is important to integrating the <literal><rich:fileUpload></literal> component with MyFaces. The code sample that follows shows the correct order in which to define your filters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To ensure that this sequence wors correctly, map the extension filter on your Faces Servlet, not to <filename>*.jsf</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable optional object selection in <rich:suggestionbox>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:suggestionBox></literal> component provides features such as object selection. To store the selected items as objects to be accessed, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the <varname>usingSuggestObjects</varname> attribute to the <literal><rich:suggestionBox></literal> component, and define it as <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <varname>onobjectchange</varname> event attribute to store the currently-selected objects."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All of the selected objects are stored in the <literal>suggestion.SelectedItems</literal> Array. Each Array element contains <literal>text</literal> and <literal>object</literal> properties, so you can iterate this Array, retrieve objects that are not <literal>null</literal>, and retrieve the required property."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for ViewExpiredException?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This exception appears after your session has timed out. Because RichFaces 3.1 is intended for use with JavaServer Faces 1.1, <exceptionname>ViewExpiredException</exceptionname>s will not generate automatically when RichFaces is used with JavaServer Faces 1.2. To work around this limitation, add the following to your <filename>web.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for Request Errors and Session Expiration?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To redefine the standard handlers that are responsible for processing different exceptional situations, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add custom <literal>onError</literal> and <literal>onExpire</literal> handlers, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more detailed description of this process, see <xref linkend=\"RequestErrorsAndSessionExpirationHandling\" /> in the Developer Guide."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Custom <literal>onError</literal> and <literal>onExpire</literal> handlers will not work under MyFaces, because MyFaces handles exceptions with an internally-generated debug page. To prevent this behavior, use the following code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I add a cookie in an AJAX response?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The bean described below adds a cookie to an AJAX response:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you can define the cookie to be included as shown in the following example. After the <literal>test</literal> cookie is set, the value of that cookie will appear on a page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is new in AJAX4JSF 3.2.x?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces 3.2.x releases have some new features:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><a4j:portlet</literal> component has been <emphasis>deprecated</emphasis>, since JSR-301 defines a similar function for <literal>UIViewRoot</literal> components;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><rich:ajaxValidator></literal>, <literal><rich:beanValidator></literal> and <literal><rich:graphValidator></literal> validators have been added to provide different validation types."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I launch the RichFaces sample on the JBoss server?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To launch the RichFaces sample application on the JBoss server, add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass a Boolean value in the <rich:componentControl> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code shows you how to avoid requiring a Boolean value:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use <code>'block'</code> instead of <code>' '</code> to avoid <literal>invalid style</literal> CSS errors."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/Getting_Started.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/Getting_Started.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,159 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Started with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This chapter tells you how to plug RichFaces components into a JSF application. The instructions are based on a simple <emphasis>JSF with RichFaces</emphasis> creation process, from downloading the required libraries to running the application in a browser. These instructions do not depend on the integrated development environment that is in use."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Simple JSF application with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> — the simple application — is similar to a typical <emphasis>hello world</emphasis> application, with one exception: the world of RichFaces will say \"Hello!\" to the user first."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a standard JSF 1.2 project named <literal>Greeter</literal>. Include all required libraries, and continue with the instructions that follow."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Adding RichFaces libraries into the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "From the <filename>RichFaces</filename> folder where you unzipped the RichFaces binary files, open the <filename>lib</filename>. This folder contains three <filename>*.jar</filename> files with API, UI, and implementation libraries. Copy these JARs from <filename>lib</filename> to the <filename>WEB-INF/lib</filename> directory of your <application>Greeter</application> JSF application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A JSF application with RichFaces assumes that the following JARs are available in the project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-beanutils-1.7.0.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-collections-3.2.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-digester-1.8.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-logging-1.0.4.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jhighlight-1.0.jar</filename>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering RichFaces in <filename>web.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "After you add the RichFaces libraries to the project, you must register them in the project <filename>web.xml</filename> file. Add the following to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For more information about RichFaces skins, read <xref linkend=\"Skinnability\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, your <filename>web.xml</filename> should look like this:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Managed bean"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <application>RichFaces Greeter</application> application needs a managed bean. In the project's <filename>JavaSource</filename> directory, create a new managed bean named <literal>user</literal> in the <literal>demo</literal> package. Place the following code in <filename>user</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering the bean in <filename>faces-cofig.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To register the <literal>user</literal> bean, add the following to the <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Greeter index.jsp"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> has only one JSP page. Create <filename>index.jsp</filename> in the root of <literal>WEB CONTENT</literal> folder and add the following to the JSP file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The application uses three RichFaces components: <emphasis role=\"bold\"><property><rich:panel></property></emphasis> is used as visual container for information; <emphasis role=\"bold\"><property><a4j:commandButton></property></emphasis> with built-in AJAX support lets a greeting be rendered dynamically after a response returns; and <emphasis role=\"bold\"><property><a4j:form></property></emphasis> helps the button to perform the action."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces tag library should be declared on each JSP page. For XHTML pages, add the following lines to declare your tag libraries:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Now, run the application on the server by pointing your browser to the <filename>index.jsp</filename> page: <literal>http://localhost:8080/Greeter/index.jsf</literal>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "\"RichFaces Greeter\" application"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Relevant Resources Links"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"https://www.redhat.com/apps/store/developers/jboss_developer_studio.html\">JBoss Developer Studio</ulink> includes tight integration with the RichFaces component framework. <!-- The following links might be useful for those who already use this IDE and RichFaces to develop applications, and for those who wish to improve their development process. -->"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/IDE_Support.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/IDE_Support.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/IDE_Support.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Integrated Development Environment Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is supported by both <ulink url=\"http://www.redhat.com/developers/rhds/index.html\">JBoss Developer Studio 1.0.0 GA</ulink> and <ulink url=\"http://www.jboss.org/tools/index.html\">Jboss Tools</ulink>. JBoss Developer Studio is a fully packaged Integrated Development Environment (IDE) that provides full support for Java Server Faces, RichFaces, Facelets, Struts and other Web technologies. It seamlessly combines visual and source-oriented development approaches. You can add JBoss Developer Studio capabilities to any JSF project by adding the appropriate libraries and modifying configuration files as required."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/Introduction.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/Introduction.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/Introduction.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,79 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is an open source framework that adds AJAX capability into existing JSF applications without resorting to JavaScript."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces leverages aspects of the JavaServer Faces (JSF) framework, including lifecycle, validation, conversion facilities, and management of static and dynamic resources. RichFaces components with built-in AJAX support and a highly customizable look-and-feel can be easily incorporated into JSF applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces allows you to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Experience the benefits of JSF while working with AJAX. RichFaces is fully integrated into the JSF lifecycle. Where other frameworks only allow access to the managed bean facility, RichFaces lets you access the action and value change listeners, and invokes server-side validators and converters during the AJAX request-response cycle."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add AJAX capabilities to existing JSF applications. The RichFaces framework provides two component libraries (Core AJAX and UI). The Core library adds AJAX functionality to existing pages, so you need not write any JavaScript or replace existing components with new AJAX components manually. RichFaces enables page-wide rather than component-wide AJAX support, giving you the opportunity to define events on the page. <!-- An event invokes an AJAX request and areas of the page which become synchronized with the JSF Component Tree after changing the data on the server by AJAX request in accordance with events fired on the client. -->"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily create different views with a variety of components, available out-of-the-box. The RichFaces UI library contains components for adding rich user interface (UI) features to JSF applications, providing you with a broad variety of AJAX-enabled components with extensive skins support. RichFaces components are designed to integrate seamlessly with other third-party component libraries, so you have more options when you develop applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Write your own rich components with built-in AJAX support. The Component Development Kit (CDK) is constantly being expanded. It includes both code generation and templating facilities and a simple JSP-like (JavaServer Pages) syntax, letting you create first-class rich components with built-in AJAX functionality."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Package resources with application Java classes. RichFaces provides advanced support for managing different resource types, including images, JavaScript code, and CSS stylesheets. The resource framework makes it easier to include these resources in JAR files with your custom component code."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily generate binary resources. The resource framework can generate images, sounds, Excel spreadsheets, etc. in real time, so you can, for example, create images with the Java Graphics 2D library and other similar resources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customize the look and feel of your user interface with skins-based technology. RichFaces lets you easily define and manage different color schemes and other user interface parameters by using named <emphasis>skin parameters</emphasis>. This means you can access UI parameters from JSP and Java code to adjust your UI in real time. RichFaces includes a number of predefined skins to kick-start your application's development, but it is easy to create your own custom skins."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Simultaneously create and test your components, actions, listeners, and pages. RichFaces will soon include an automated testing facility to generate test cases for your component as you develop it. The testing framework tests not only the components, but also any other server-side or client-side functionality, including JavaScript code — and it will do so <emphasis>without</emphasis> deploying the test application into the Servlet container."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces UI components can be implemented immediately, right out of the box. This saves development time and gives you immediate access to RichFaces web application development features, so experience with RichFaces is fast and easy to obtain."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/Links_to_Resources.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/Links_to_Resources.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/Links_to_Resources.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,74 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Links to information resources"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Links"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/portal/jbossrichfaces/\">JBoss RichFaces</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss Forum"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://jboss.com/index.html?module=bb&op=main&c=27\">JBoss Forums</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Wiki"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/wiki/RichFaces\">RichFaces Wiki</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Blog"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "<ulink url=\"http://jroller.com/page/a4j\">RichFaces Blog</ulink>"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/Revision_History.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/Revision_History.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/Revision_History.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: member
+#, no-c-format
+msgid "JIRA corrections."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/RichFaces_Developer_Guide.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/RichFaces_Developer_Guide.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/RichFaces_Developer_Guide.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/Settings.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/Settings.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/Settings.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,334 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Settings for different environments"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces includes support for all tags (components) included in the JavaServer Faces (JSF) specification. To add RichFaces capabilities to an existing JSF project, place the RichFaces libraries into the <filename>lib</filename> directory of the project, and add filter mapping. The behavior of the existing project does not change when you add RichFaces."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Application Descriptor Parameters"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not require that any parameters be defined in your <filename>web.xml</filename>, but the RichFaces parameters listed below will help you during the development process and increase the flexibility of your RichFaces applications."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.SKIN"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The name of a skin that is used in an application. Can be a literal string with a skin name or the EL expression (<literal>#{...}</literal>) associated with a String property (skin name) of a property of a <literal>org.richfaces.framework.skin</literal> type. In the latter case, that instance is used as the current skin."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadScriptStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces script files are loaded to the application. Possible values are <literal>ALL</literal>, <literal>DEFAULT</literal> and <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadStyleStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces style files are loaded into the application. Possible values are: <literal>ALL</literal>, <literal>DEFAULT</literal>, or <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.LOGFILE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "none"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The URL of an application or a container log file (if applicable). If this parameter is set, content from the given URL is shown on a Debug page in the <literal>iframe</literal> window."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.VIEW_HANDLERS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of <literal>ViewHandler</literal> instances for inserting in a view handler chain. These handlers are inserted before the RichFaces viewhandlers, in the order they are listed. In a Facelets application, you would declare <literal>com.sun.facelets.FaceletViewHandler</literal> here instead of in the <filename>faces-config.xml</filename> file."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.CONTROL_COMPONENTS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of special <emphasis>control case</emphasis> components, such as the messages bundle loader or an alias bean component. These handlers are provided via a reflection from the static field <literal>COMPONENT_TYPE</literal>. Encoding methods for these components are always called while rendering AJAX responses, even if a component has not been updated."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_RESOURCE_DATA"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "false"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "For generated resources (such as encrypt generation data), this is encoded in the resource URL. For example, the URL of an image generated by the <classname>mediaOutput</classname> component contains the name of a generation method. Since malicious code can exploit this to create a request for any JSF bean or attribute, this parameter should be set to <literal>true</literal> in critical applications. (This fix works with Java Runtime Environment 1.4.)"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_PASSWORD"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "random"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A password used to encrypt resource data. If this is not set, a random password is used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.COMPRESS_SCRIPT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "true"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "When defined, does not allow the frameword to reformat JavaScript files. This means that the debug feature cannot be used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URLs of all generated resources. This is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.GLOBAL_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/g"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URI of all global resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SESSION_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/s"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be used to track the sessions of generated resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.DEFAULT_EXPIRE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "86400"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the period (in seconds) for which resources are cached when they are streamed back to the browser."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SERIALIZE_SERVER_STATE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "If set to <literal>true</literal>, the component state (not the tree) will be serialized before it is stored in the session. This can be useful in applications with view state that is sensitive to model changes. Alternatively, use <literal>com.sun.faces.serializeServerState</literal> and <literal> org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</literal> parameters in their respective environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>org.richfaces.SKIN</literal> is used in the same way as <literal>org.ajax4jsf.SKIN</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "org.ajax4jsf.Filter Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "log4j-init-file"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "-"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A path (relative to the web application's context) to the <filename>log4j.xml</filename> configuration file. This can be used to set up per-application custom logging."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "enable-cache"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Enables caching of framework-generated resources (JavaScript, CSS, images, etc.). However, your cached resources will not be used when attempting to debug custom JavaScript or Styles."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "forcenotrf"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Forces all JSF pages to be parsed by a HTML syntax check filter. If set to <literal>false</literal>, only AJAX responses will be parsed and converted to well-formed XML. Setting this to <literal>false</literal> can improve performance, but may also cause unexpected information to be rendered during AJAX updates."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Sun JSF RI"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces works with JavaServer Faces 1.2_13 without needing to modify additional settings."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Facelets Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces has high-level support for Facelets, regardless of the version used. However, some JSF frameworks (including Faces) require that their own <literal>ViewHandler</literal> be listed first in the <literal>ViewHandler</literal> chain. RichFaces also requires that its <literal>AjaxViewHandler</literal> be listed first, but because it is installed first, no settings will need to be altered. Where multiple frameworks are used without RichFaces, you can use the <literal>VIEW_HANDLERS</literal> parameter to define the order in which the <literal>ViewHandler</literal>s are used. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This declares that while <literal>Facelets</literal> will officially be first, <literal>AjaxViewHandler</literal> will briefly be ahead of it to perform some small, important task."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this case, you need not define <literal>FaceletViewHandler</literal> in <filename>WEB-INF/faces-config.xml</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JBoss Seam Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is compatible with <application>JBoss Seam</application> and Facelets when run within JBoss Enterprise Application Server. No additional JARs are required. All you need to do is package the RichFaces library with your application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For <application>Seam 1.2</application>, your <filename>web.xml</filename> must be as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>Seam 2.x</application> supports RichFaces Filter, so your <filename>web.xml</filename> must look like this:"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/fr-FR/Technical_Requirements.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/fr-FR/Technical_Requirements.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/fr-FR/Technical_Requirements.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,179 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Technical Requirements"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces</application> was developed with an open architecture to ensure that it was compatible with the widest possible variety of environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This is what you need to start working with <application>RichFaces 3.3.1</application>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JavaServer Faces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java Application Server <emphasis>or</emphasis> Servlet Container"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Browser (on client side)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Java Versions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JDK 1.5 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported JavaServer Faces Implementations and Frameworks"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun JSF-RI - 1.2_12"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "MyFaces 1.2.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Facelets 1.1.1 - 1.2"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Seam 1.2. - 2.1.0"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Servers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Apache Tomcat 5.5 - 6.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "BEA WebLogic 9.1 - 10.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Resin 3.1"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Jetty 6.1.x"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun Application Server 9 (J2EE 1.5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "GlassFish (J2EE 5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JBoss 4.2.x - 5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Websphere 7.0. and higher"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Geronimo 2.0 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Browsers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6.0 - 8.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Firefox 2.0 - 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera 8.5 - 9.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Google Chrome"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This list is composed from user reports of compatibility. We assume that this list is incomplete, so the absence of your environment from the list does not necessarily mean that it is incompatible with RichFaces."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "We appreciate your feedback about compatible platforms and browsers that are not listed here. This helps us keep the list up-to-date."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/Architecture_Overview.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/Architecture_Overview.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/Architecture_Overview.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,1829 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Basic concepts of the RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces Framework is implemented as a component library that adds AJAX capabilities into existing pages. This means that you do not need to write any JavaScript code or replace existing components with new AJAX widgets. RichFaces enables page-wide AJAX support instead of the traditional component-wide support, so you can define areas of the page that will reflect changes made by AJAX events on the client."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram following shows the process in full:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Processing flow"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you use JSF tags to define sections of a JSF page that you wish to update with the results of an AJAX request. It also provides you with several options for sending AJAX requests to the server. You do not need to write any JavaScript or <literal>XMLHTTPRequest</literal> objects by hand — everything is done automatically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Architecture Overview"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following figure lists several important elements of the RichFaces Framework."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Core AJAX component structure"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Filter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To make the most of RichFaces, you should register a <literal>Filter</literal> in your application's <filename>web.xml</filename>. The <literal>Filter</literal> recognizes multiple request types. The sequence diagram in Figure 5.3 shows the differences in processing between a <emphasis>regular</emphasis> JSF request and an AJAX request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request processing sequence diagram"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In either case, the required static or dynamic resource information that your application requests is registered in the <literal>ResourceBuilder</literal> class."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When a resource request is issued, the RichFaces filter checks the <literal>Resource Cache</literal> for this resource. If it is present, the resource is returned to the client. Otherwise, the filter searches for the resource among those registered in the <literal>ResourceBuilder</literal>. If the resource is registered, the RichFaces filter requests that the <literal>ResourceBuilder</literal> creates (delivers) the resource."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram that follows illustrates the process of requesting a resource."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Resource request sequence diagram"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Action Components"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "AJAX Action components are used to send AJAX requests from the client side. There are a number of AJAX Action components, including <literal><a4j:commandButton></literal>, <literal><a4j:commandLink></literal>, <literal><a4j:poll></literal>, and <literal><a4j:support></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Containers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>AjaxContainer</literal> is an interface that defines an area on your JSF page that should be decoded during an AJAX request. <literal>AjaxViewRoot</literal> and <literal>AjaxRegion</literal> are both implementations of this interface."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JavaScript Engine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces JavaScript Engine runs on the client side, and updates different areas of your JSF page based on information from the AJAX response. This JavaScript code operates automatically, so there is no need to use it directly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors and Session Expiration Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you redefine the standard handlers responsible for processing exceptions. We recommend defining your own JavaScript, which will be executed when exceptional situations occur."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To execute your own code on the client in the event of an error during an AJAX request, you must redefine the standard <literal>A4J.AJAX.onError</literal> method like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function accepts the following as parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>req</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a parameter string of a request that calls an error"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>status</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the number of an error returned by the server"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>message</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for the given error"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, you can create your own handler that is called when timeouts, internal server errors, etc. occur."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Session Expired Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also redefine the <literal>onExpired</literal> framework method that is called on the <literal>SessionExpiration</literal> event."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Example:</emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function can take the following parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>loc</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the URL of the current page (can be updated on demand)"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>expiredMsg</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for display in the event of <literal>SessionExpiration</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customized <literal>onExpire</literal> handlers do not work under MyFaces. MyFaces handles exceptions by internally generating a debug page. To prevent this behavior, use the following:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skinnability"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you look at any CSS (Cascading Style Sheets) file in an enterprise application, you will notice how often the same color is noted. Standard CSS cannot define a particular colour abstractly as a panel header color, the background color of an active pop-up menu item, a separator color, etc. To define common interface styles, you must copy the same value multiple times, and the more interfaces you have, the more repetition is required."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, if you want to change the palette of an application, you must change all interrelating values, or your interface can appear clumsy. If a customer wants to be able to adjust their interface's look and feel in real time, you must be able to alter several CSS files, each of which will contain the same value multiple times."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve these problems with the <emphasis>skins</emphasis> that are built into and rully implemented in RichFaces. Every named skin has <emphasis>skin parameters</emphasis> that define a palette and other attributes of the user interface. By changing a few skin parameters, you can alter the appearance of dozens of components simultaneously, without interfering with interface consistency."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinnability</literal> feature cannot completely replace standard CSS, and does not eliminate its usage. Instead, it is a high-level extension of standard CSS that can be used in combination with regular CSS declarations. You can also refer to skin parameters in CSS through the JSF Expression Language. This lets you completely synchronize the appearance of all elements in your pages."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Using Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces <emphasis>skinnability</emphasis> is designed for use alongside:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "skin parameters defined in the RichFaces framework,"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "predefined CSS classes for components, and"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "user style classes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A component's color scheme can be applied to its elements using any of three style classes:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A default style class inserted into the framework"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This contains stle parameters that are linked to some constants from a skin. It is defined for every component and specifies a default level of representation. You can modify an application interface by changing the values of the skin parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A style class of skin extension"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This class name is defined for every component element, and inserted into the framework to let you define a class with the same name in your CSS files. This lets you easily extend the appearance of all components that use this class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "User style class"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use one of the <literal>styleClass</literal> parameters to define your own class for component elements. As a result, the appearance of one particular component is changed according to a CSS style parameter specified in the class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Example"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following is an example of a simple <emphasis>panel</emphasis> component:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This code generates a panel component on a page, which consists of two elements: a wrapper <literal><div></literal> element and a <literal><div></literal> element for the panel body with the specified style properties. The wrapper <literal><div></literal> element will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>dr-pnl</literal> is a CSS class that is specified in the framework via skin parameters:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>background-color</varname> is defined with <literal>generalBackgroundColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>border-color</varname> is defined with <literal>panelBorderColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change all colors for all panels on all pages by changing these skin parameter values. However, if you specify a <literal><rich:panel></literal> class on the page, its parameters are also acquired by all panels on this page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Developers can also change the style properties for panel. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous definition could add some style properties from <literal>customClass</literal> to one particular panel. As a result, we will get three styles:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skin Parameters Tables in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces provides eight predefined skin parameters (skins) at the simplest level of common customization:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "plain"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "emeraldTown"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "blueSky"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "wine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "japanCherry"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ruby"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "classic"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "deepMarine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To apply a skin, you must specify a skin name in the <varname>org.richfaces.SKIN</varname> context parameter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following table shows the values for each parameter in the <literal>blueSky</literal> skin:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Colors"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Parameter name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#BED6F8"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerGradientColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#F2F7FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#000000"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerWeightFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bold"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FFFFFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "11px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Arial, Verdana, sans-serif"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "additionalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#ECF4FE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowOpacity"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "panelBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "subBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C6DEFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabDisabledTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#8DB7F3"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "trimColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#D6E6FB"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FAE6B0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E5973E"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "selectControlColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E79A00"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0078D0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0090FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "visitedLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Fonts"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableFooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#cccccc"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableSubfooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#f1f1f1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C0C0C0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>plain</literal> skin was added in version 3.0.2. It has no parameters, and is important when embedding RichFaces components into existing projects with their own styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Creating and Using Your Own Skin File"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To create your own skin file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a file. In it, define skin constants to be used by style classes (see <xref linkend=\"SkinParametersTablesInRichFaces\" />). The name of the skin file should follow this format: <literal><name>.skin.properties</literal>. (For examples of this file, see the RichFaces predefined skin parameters: <literal>blueSky</literal>, <literal>classic</literal>, <literal>deepMarine</literal>, etc. These files are located in the <filename>richfaces-impl-xxxxx.jar</filename> archive in the <filename>/META-INF/skins</filename> folder."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the skin definition <literal><contex-param></literal> to the <filename>web.xml</filename> of your application, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place your <literal><name>.skin.properties</literal> file in either your <filename>/META-INF/skins</filename> or <filename>/WEB-INF/classes</filename> directory."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Built-in Skinnability in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you incorporate skins into your user interface (UI) design. This framework lets you use named skin parameters in your properties files to control skin appearance consistently across a set of components. You can see examples of predefined skins at: <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">http://livedemo.exadel.com/richfaces-demo/ </ulink>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Skins let you define a style in which to render standard JSF components and custom JSF components built with RichFaces. You can experiment with skins by following these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a custom render kit and register it in the <filename>faces-config.xml</filename> like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, create and register custom renderers for the component based on the look-and-feel predefined variables:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, place a properties file with skin parameters into the class path root. There are two requirements for the properties file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The file must be named <filename><replaceable>skinName</replaceable>.skin.properties</filename>. In this case, we would call it <literal>newskin.skin.properties</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The first line in this file should be <literal>render.kit=<replaceable>render-kit-id</replaceable></literal>. In this case, we would use <literal>render.kit=NEW_SKIN</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "More information about creating custom renderers can be found at: <ulink url=\"http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html\">http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Changing skin in runtime"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change skins during runtime by defining the following EL-expression in your <filename>web.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinBean</literal> code looks like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also set the <varname>skin</varname> property's initial value in the configuration file. To set <literal>classic</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also change the properties of the default skin. To do so, edit the properties of the default skin. The following shows you example page code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The above code will generate the following list of options:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Controls Skinning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This feature is designed to unify the look and feel of standard HTML elements and RichFaces components. Skinning can be applied to all controls on a page based on element names and attribute types (where applicable). This feature also provides a set of CSS styles that let skins be applied by assigning <literal>rich-*</literal> classes to particular elements, or to a container of elements that nests controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard Controls Skinning provides two levels of skinning: <emphasis>Basic</emphasis> and <emphasis>Extended</emphasis>. The level used depends on the browser type detected. If the browser type cannot be detected, <literal>Extended</literal> is used. However, if you want to explicitly specify the level to be applied, add a <varname></varname> context parameter to your <filename>web.xml</filename> and set the value to either <literal>basic</literal> or <literal>extended</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Basic</emphasis> level provides customization for only basic style properties. Basic skinning is applied to the following browsers:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in BackCompat mode (see <ulink url=\"http://msdn2.microsoft.com/en-us/library/ms533687(VS.85).aspx\">document.compatMode property in MSDN</ulink>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Extended</emphasis> level introduces a broader number of style properties on top of basic skinning, and is applied to browsers with rich visual styling control capabilities. The following browsers support Extended skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Mozilla Firefox"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in Standards-compliant mode (CSS1Compat mode)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following elements can be modified with skins:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>input</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>select</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>textarea</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>keygen</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>isindex</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>legend</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>fieldset</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>hr</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>a</literal> (together with the <literal>a:hover</literal>, <literal>a:visited</literal> pseudo-elements)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two ways to initialize skinning for standard HTML controls:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. This method implies that skinning style properties are applied per-element and attribute type (where applicable). No additional steps are required. See the <xref linkend=\"BasicLevel\" /> and <xref linkend=\"ExtendedLevel\" /> tables for elements to which skinning can be applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. When enabled, you are provided with a set of predefined CSS classes to apply skins to your HTML components."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enabling <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> provides you style classes that can be applied to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "basic elements nested within elements with a <emphasis>rich-container</emphasis> class. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements with a class name that corresponds to one of the basic element names or types are mapped with the <literal>rich-<elementName>[-<elementType>]</literal> scheme, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements are given classes depending upon their <literal>link</literal> type and pseudo-class name, for example, <literal>rich-link</literal>, <literal>rich-link-hover</literal>, <literal>rich-link-visited</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The predefined rich CSS classes provided can be used as classes for both basic and complex HTML elements."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code snippet shows several elements as an example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more thorough look at standard component skinning, we recommend exploring the CSS files located in the <filename>ui/core/src/main/resources/org/richfaces/</filename> directory of the RichFaces SVN repository."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex and legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "CSS Properties"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-size"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-family"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for hr"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:hover"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColorgeneralLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Elements Skin Bindings for .rich-input, .rich-select, .rich-textarea, .rich-keygen, .rich-isindex, .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-fieldset"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-hr"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-width"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-style"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "solid"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:hover"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin parameters/Value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "inset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-color"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "no-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-position"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px 1px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-edit"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "editBackgroundColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-error"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "warningBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding-left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "7px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button, .rich-button-disabled, .rich-button-over"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "2px 10px 2px 10px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "text-align"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "cursor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "pointer"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "repeat-x"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "top left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button-press"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bottom left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-container fieldset, .rich-fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "10px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-weight"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-form"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "0px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "margin"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Extended level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-image"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for button[type=button], button[type=reset], button[type=submit], input[type=reset], input[type=submit], input[type=button]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button[disabled], .rich-container *|button[disabled], .rich-button-disabled"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonDisabledBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for .rich-button-disabled, .rich-container button[type=\"button\"][disabled], .rich-button-button-disabled, .rich-container button[type=\"reset\"][disabled], .rich-button-reset-disabled, .rich-container button[type=\"submit\"][disabled], .rich-button-submit-disabled, .rich-container input[type=\"reset\"][disabled], .rich-input-reset-disabled, .rich-container input[type=\"submit\"][disabled], .rich-input-submit-disabled, .rich-container input[type=\"button\"][disabled], .rich-input-button-disabled"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *button[type=\"button\"][disabled], button[type=\"reset\"][disabled], button[type=\"submit\"][disabled], input[type=\"reset\"][disabled], input[type=\"submit\"][disabled], input[type=\"button\"][disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.InputBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for textarea[type=textarea], input[type=text], input[type=password], select"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea[disabled], .rich-container *|textarea[disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "textarea[type=\"textarea\"][disabled], input[type=\"text\"][disabled], input[type=\"password\"][disabled]"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The basic skinning level can fail if the <literal>ajaxPortlet</literal> is configured as follows:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Client-side Script for Extended Skinning Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Extended skinning of standard HTML controls is applied automatically: the browser type is detected, and if a browser does not fully support extended skinning, only basic skinning is applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are some problems with standard HTML controls in certain browsers (Opera and Safari) that may cause problems if you wish to skin your RichFaces components and standard HTML controls manually."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable skinnability, set the <varname>org.richfaces.LoadStyleStrategy</varname> parameter to <literal>NONE</literal> in your <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You should also include the style sheets that apply skins to RichFaces components and standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To work around the problem of extended skinning in Opera and Safari, the <filename>skinning.js</filename> client script is added to the RichFaces library. This detects the browser type and enables extended skinning only for browsers that fully support it."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Activate the script by inserting the following JavaScript into your page:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When no script-loading strategy is used and extended skinning is enabled, a warning message appears in the console."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also specify the <varname>media</varname> attribute in the <literal>link</literal> tag. This adds the <filename>extended_both.xcss</filename> style sheet to <literal>rich-extended-skinning</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include your style sheets to the page when automatic skinnability is disabled, add the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Base64 encoder now uses <literal>!</literal> instead of <literal>.</literal>, so remember to use the <literal>a4j/versionXXX</literal> resources prefix instead of <literal>a4j_versionXXX</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "XCSS File Format"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Cross-site Cascading Style Sheet (XCSS) files are the core of RichFaces component skinnability. XCSS is XML-formatted CSS that extends the skinning process. RichFaces parses the XCSS file containing all look and feel parameters of a particular component and compiles the information into a standard CSS file that can be recognized by a web browser."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The XCSS file contains CSS properties and skin parameter mappings. Mapping a CSS selector to a skin parameter can be done with <literal>< u:selector ></literal> and <literal>< u:style></literal> XML tags, which define the mapping structure, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "During processing, this code will be parsed and assembled into a standard CSS format, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>name</varname> attribute of <literal><u:selector></literal> defines the CSS selector, while the <varname>name</varname> attribute of the <literal><u:style></literal> tag defines the skin constant that is mapped to a CSS property. You can also use the <varname>value</varname> attribute of the <literal><u:style></literal> tag to assign a value to a CSS property."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "CSS selectors with identical skin properties can be included in a comma-separated list:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Plug-n-Skin</emphasis> lets you easily create, customize, and plug in a custom skin to your project. You can create skins based on the parameters of predefined RichFaces skins. Plug-n-Skin also lets you unify the appearance of rich controls with standard HTML elements. This section contains step-by-step instructions for creating your own skin with Plug-n-Skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, use Maven to create a template for your new skin. (You can find more information about configuring Maven for RichFaces in the <!-- #modify add info? --><ulink url=\"http://wiki.jboss.org/wiki/HowToConfigureMavenForRichFaces\">JBoss wiki article</ulink>. These Maven instructions can be copied and pasted into the command line interface to execute them."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Primary keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>archetypeVersion</varname> — indicates the RichFaces version; for example, <literal>3.3.1.GA</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>artifactId</varname> — the artifact ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>groupId</varname> — the group ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>version</varname> — the version of the project you create. By default, this is set to <literal>1.0.-SNAPSHOT</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This operation creates a directory named after your <literal>ARTIFACT-ID</literal>. The directory contains a template of the Maven project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following steps will guide you though creating of the skin itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Run the following command from the root directory of the Maven project. (This directory will contain your <filename>pom.xml</filename> file.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>name</varname> — defines the name of the new skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>package</varname> — the base package of the skin. By default, the project's <literal>groupId</literal> is used."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Additional optional keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — defines the name of the base skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>createExt</varname> — if set to <literal>true</literal>, extended CSS classes are added. For more information, please, see <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once these operations are complete, the following files and folders should have been created:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImage.java</filename> — the base class used to store images. Location: <filename>\\src\\main\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImageTest.java</filename> — a test version of a class that stores images. Location: <filename>\\src\\test\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>XCSS files</filename> — XCSS files define the new look of RichFaces components affected by the new skin. Location: \"\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.properties</filename> — a file that contains the new skin's properties. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following properties are used to configure the <filename>SKIN-NAME.properties</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — the name of the skin to be used as a basis for your own skin. The look of the skin you define will be affected by the new style properties."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>generalStyleSheet</varname> — a path to the style sheet (<filename>SKIN-NAME.xcss</filename>) that imports your component's style sheets to be modified by the new skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>extendedStyleSheet</varname> — the path to a style sheet that is used to unify the appearance of RichFaces components and standard HTML controls. For additional information, read <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>gradientType</varname> — a predefined property to set the type of gradient applied to the new skin. Possible values are <literal>glass</literal>, <literal>plastic</literal>, <literal>plain</literal>. More information on gradient implementation you can find further in this chapter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.xcss</filename> — an XCSS file that imports the component's XCSS files to be modified by the new skin. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>XCSS files</literal> — creates the XCSS files that determine styles for standard controls (<filename>extended_classes.xcss</filename> and <filename>extended.xcss</filename>), if the <varname>createExt</varname> key is set to <literal>true</literal>. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-ext.xcss</filename> — creates the <filename>SKIN-NAME-ext.xcss</filename> file that imports defining styles for standard controls if <varname>createExt</varname> is set to <literal>true</literal>. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-resources.xml</filename> — contains descriptions of all files listed previously. Location: <filename>src\\main\\config\\resources</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now start editing the XCSS files located in <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>. Assign new style properties to your selectors (listed in the XCSS files) in either of the following ways:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard CSS coding approach (that is, add CSS properties to the selectors). Remember that the selectors must be within <literal><f:verbatim> </f:verbatim></literal> tags. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "XCSS coding approach (the usual method of creating XCSS files in RichFaces). XCSS tags must be placed <emphasis>outside</emphasis> <literal><f:verbatim> </f:verbatim></literal> tags."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once you have performed these steps and edited the XCSS files, build the new skin and plug it into the project. To build the skin, execute the following command from the root directory of your skin project (the directory that contains your <filename>pom.xml</filename> file):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Plug-n-skin feature also has a number of predefined gradients. The following code can be used to apply a gradient:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>background-image</varname> CSS property is defined with <literal><f:resource f:key=\"org.richfaces.renderkit.html.CustomizeableGradient\"></literal>, which sets the gradient. The gradient type can be specified in the <filename>SKIN-NAME.properties</filename> with the <varname>gradientType</varname> property, which can be set to <literal>glass</literal>, <literal>plastic</literal>, or <literal>plain</literal>. The gradient can then be adjusted with the <varname>baseColor</varname>, <varname>gradientColor</varname>, <varname>gradientHeight</varname>, <varname>valign</varname> attributes, as seen in the previous code snippet."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now use your newly-created skin in your project by adding your new skin parameters to the <filename>web.xml</filename> file, and placing the JAR file containing your skin (located in the <filename>target</filename> directory of your skin project) in the <filename>\\WebContent\\WEB-INF\\lib\\</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Details of Usage"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This section covers some practical aspects of Plug-n-Skin implementation. We assume that you have read the section of the guide describing the Plug-n-Skin prototype creation process."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, we must create a new skin (as described in the previous section). The following creates a template of the new skin project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now browse the <filename>P-n-S</filename> directory to view the files and folders created."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use Maven to add all required files to the skin project, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As mentioned in the previous section, <!-- #modify '-D' typo? --><literal>-DbaseSkin</literal> defines the RichFaces built-in skin to use as a base, and <literal>-DcreateExt=true</literal>, which determines that the new skin will include XCSS files that unify the appearance of the rich components and the standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once your resources have been created, you can begin refining the newly-created skin. Begin by editing the rich components' XCSS files."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example of the Plug-n-Skin feature, we will edit some <literal><rich:calendar></literal> style attributes and some basic HTML controls. We will show you how to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor the background of the current day in the <literal><rich:calendar></literal>;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor a standard HTML submit button;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To edit <literal><rich:properties></literal>'s style properties, you must open the <filename>calendar.xcss</filename> file, located in <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the <filename>calendar.xcss</filename> file, find the <literal>.rich-calendar-today</literal> selector and amend it as follows:<literal>background-color: #075ad1;</literal>. This will change the background color of the current day."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next we will change the font style of a standard HTML <emphasis>submit</emphasis> button. Open the <filename>extended.xcss</filename> file from the <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename> directory and insert <literal>font-weight: bold;</literal> between the curly braces of these selectors, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The desired changes have now been made, and you can proceed to building the new <literal>PlugnSkinDemo</literal> skin and importing it into the project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Build the skin by executing <command>mvn clean install</command> from the <filename>P-n-S</filename> directory. This creates a <filename>target</filename> directory containing a JAR file with a newly-compiled skin. In our case, the file is named <filename>P-n-S-1.0.-SNAPSHOT.jar</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, import the new <literal>PlugnSkinDemo</literal> skin into your project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Copy the <filename>P-n-S-1.0.-SNAPSHOT.jar</filename> file to the <filename>\\WebContent\\WEB-INF\\lib\\</filename> directory."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the name of the new skin to the <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember, standard controls skinning must be enabled in <filename>web.xml</filename>. Add the following to enable standard controls skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The results of each alteration to the skin are shown in the figures that follow:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin feature in action."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "State Manager API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JSF has an advanced navigation mechanism that lets you define <emphasis>navigation</emphasis> from view to view. In a web application, navigation occurs when a user changes from one page to another by clicking on a button, a hyperlink, or another command component. There is no switch mechanism between some logical states of the same view. For example, in <emphasis>Login/Register dialog</emphasis>, an existing user signs in with his user name and password, but if a new user attempts to register, an additional field (<literal>Confirm</literal>) is displayed, and button labels and methods are changed when the user clicks the <guilabel>To register</guilabel> link:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Login Dialog"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Register Dialog"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>RichFaces State API</emphasis> lets you easily define a set of states for pages, and properties for these states."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>States</varname> class interfaces with a <property>map</property>, where the <methodname>keySet</methodname> defines the State name and the <methodname>entrySet</methodname> is a <varname>State</varname> <property>map</property>. The <varname>State</varname> <property>map</property> defines the properties, method bindings, or constant state variables of a key or object, where these values may change depending on the active State."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces State API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One of the most convenient features of the RichFaces State API is the ability to navigate between <varname>State</varname>s. The API implements changes in <varname>State</varname> through standard JSF navigation. When the action component returns an outcome, the JSF navigation handler (extended through the RichFaces State API) checks whether the outcome is registered as a <emphasis><varname>State</varname> change outcome</emphasis>. If <literal>true</literal>, the corresponding <varname>State</varname> is activated. If <literal>false</literal>, standard navigation handling is called."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Implement the RichFaces State API like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register the State Navigation Handler and the EL Resolver in your <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register an additional application factory in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register two managed beans in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One bean (<literal>config</literal>) defines and stores <varname>State</varname> as seen in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second bean, with the <literal>org.richfaces.ui.model.States</literal> type (<literal>state</literal>), contains the managed property <property>states</property>, which is bound to the first <literal>config</literal> bean."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use <property>state</property> bindings on the page, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To see complete example of the Login/Register dialog, see the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/stateAPI.jsf?c=stateAPI\">RichFaces Live Demo</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Identifying User Roles"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces also lets you check whether the logged-in user belongs to a certain <property>user role</property> with the <literal>rich:isUserInRole(Object)</literal> function. This function takes a String or a comma-delineated list of Strings, a Collection, etc. as arguments and returns a Boolean value."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example, imagine that you need to render some controls only for administrators. To do so, create an administrator role (<literal>admin</literal>) in your <filename>web.xml</filename> file. Then implement authorization that assigns the <literal>admin</literal> role to the user that has logged in as an administrator. Once this has been done, you can use the <literal>rich:isUserInRole(Object)</literal> function with the <varname>rendered</varname> attribute of any component. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Here, only a logged-in user with an <literal>admin</literal> role can see the text editor, which will not be rendered for users with other roles."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/Author_Group.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/Author_Group.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/Author_Group.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/Book_Info.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/Book_Info.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/Book_Info.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Developer Guide"
+msgstr ""
+
+#. Tag: subtitle
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/FAQ.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/FAQ.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/FAQ.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,989 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "FAQ"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find additional information on RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most important links for RichFaces can be found <ulink url=\"http://jboss.com/index.html?module=bb&op=viewtopic&t=104575\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where are the binary/source distributions for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Distributions are available from the <ulink url=\"http://labs.jboss.com/jbossrichfaces/downloads/\">JBoss RichFaces Download area</ulink>. The source distribution is found in the <filename>richfaces-ui-3.3.0-src.zip</filename> file. The binary distribution is in the <filename>richfaces-ui-3.3.0-bin.zip</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I manually build a RichFaces snapshot?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This <ulink url=\"http://labs.jboss.com/wiki/HowToBuildRichFacesSnapshotManually\"> wiki article</ulink> takes you through the process."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I configure Maven for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, download and install Maven. (Follow the instructions at <ulink url=\"http://maven.apache.org/download.html\">http://maven.apache.org/download.html</ulink>.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Open the <filename><Maven-Root>/conf/settings.xml</filename> file and add the following to the <literal><profile></literal> section:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following to the <literal><activeProfiles></literal> section:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is the structure of RichFaces SVN repository?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can see the structure in the RichFaces Repository Structure Overview in <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">this Wiki article</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I build <literal>richfaces-samples</literal> applications?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "he <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">RichFaces Repository Structure Overview</ulink> describes how to build <literal>richfaces-samples</literal> applications in Eclipse."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find a demo for RichFaces components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Online demo applications that showcase RichFaces features are available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also find a nightly build (in the WAR format) <ulink url=\"http://maven.exadel.com/org/richfaces/samples/richfaces-demo/3.1.0-SNAPSHOT/\">here</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Source Code (SVN) can be found <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-demo/\">in the JBoss RichFaces SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What causes the \"Prototype.Browser() function cannot be found\" error in RichFaces 3.1.0, and how do I fix it?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Your application probably uses an older version of Prototype from Tomahawk 1.1.6. RichFaces 3.1.0 uses the latest Prototype (1.5.1.1). Upgrade your version of Prototype to solve this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does the RichFaces library contain the <literal><rich:dataTable></literal> component as well as the <literal><h:dataTable></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dataTable></literal> component lets you use skins to change the look and feel of your data tables. You can see an example of the difference between these components at the <ulink url=\"http://livedemo.exadel.com/richfaces-art-datatable/\">RichFaces dataTable LiveDemo page</ulink>, or see the source code in the <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-art-datatable/\">SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I organize wizards with the <literal><rich:modalPanel></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place the <literal><a4j:include></literal> tag inside the <literal><rich:modalPanel></literal> and perform navigation inside it, as in the following example below:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I stop <literal>modalPanel</literal> closing when validation fails?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two methods available to fix this problem. The first is simply to remove the <literal>windowclose()</literal> method from the <literal>modalPanel</literal>, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that when an error presents, the panel will simply do nothing rather than closing the window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second method assumes that you use Facelets. Add the following to your <filename>default.xhtml</filename> template:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This invisible form will be refreshed on every postback, and contains a hidden field that determines the maximum severity in the message queue. If you add the following function to your JavaScript:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method reads the value of the hidden field to determine whether the last postback to the server generated any errors. This means that the <literal><a4j:commandLink></literal> or <literal><a4j:commandButton></literal> that submits your form will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method lets you easily adjust the behaviour of any JavaScript code depending on whether an error is present. See the <ulink url=\"http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4061517\">JBoss RichFaces forum</ulink> post for more information and variations on this method."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "When I use <literal>suggestionbox</literal> inside the <literal>modalPanel</literal>, the suggestion list sits behind the <literal>modalPanel</literal> and I cannot see it. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You are using an old version of RichFaces. Upgrade to the latest version to fix this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Does RichFaces work with Facelets?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes. Full Facelets support is one of RichFaces' primary features. The main <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\"> demo</ulink> is a Facelets-based application."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I create a dynamic menu with the <literal><rich:dropDownMenu></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:dropDownMenu></literal> is a standard JSF component, so creating a menu dynamically from the JavaScript code is the same as for any other JSF component."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I customize the look of a <literal>datascroller</literal> (the forward/back buttons) and replace them with images?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can. The <literal>datascroller</literal> component provides two controller groups for switching:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Page numbers</emphasis> so that you can switch to a particular page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Fast-switching</emphasis> controls: <literal>first</literal>, <literal>last</literal>, <literal>next</literal>, <literal>previous</literal>, <literal>fastforward</literal> and <literal>fastrewind</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create fast-switching controls by adding a <literal>facet</literal> component with the corresponding name:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also create disabled states with facets There are also facets used to create the disabled states: <literal>first_disabled</literal>, <literal>last_disabled</literal>, <literal>next_disabled</literal>, <literal>previous_disabled</literal>, <literal>fastforward_disabled</literal>, <literal>fastrewind_disabled</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I place simple links inside a menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include a link to an external URL, use the following approach:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see a demonstration of the <literal><rich:dropDownMenu></literal> component at the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/dropDownMenu.jsf\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal>dropDownMenu</literal> as a context menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dropDownMenu></literal> is not designed for use as a <literal>contextMenu</literal>. A <literal><rich:contextMenu></literal> component is planned for development, but is not scheduled for any currently planned version."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass my own parameters during a <literal>modalPanel</literal> opening or closing?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass your parameters during modalPanel opening or closing like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass any of your own parameters, except for the standard <literal>modalPanel</literal> parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I add a simple link to the tree node?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following simple code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Is it possible to place tabs upright in the <literal>tabPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, it is not. Try using the <literal>togglePanel</literal> instead; toggle controls can be placed anywhere in the layout."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use a <literal>commandButton</literal> within the <literal>modalPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two important rules to follow when using <literal>modalPanel</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if <literal>modalPanel</literal> has form elements (input or command elements), it must have its own form."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if the <literal>modalPanel</literal> contains a form, it must not be included in a higher-level form."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I define the currently selected tab?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I retrieve the current value from the <literal>inputNumberSlider</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can retrieve the value with the following approach:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How to apply skins to the standard input components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The answer could be found <ulink url=\"http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103494\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I remove the table border and styles from the <literal>datascroller</literal> and show only links?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To do this, you must redefine your rich* classes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I expand/collapse tree nodes from code?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/ExpandCollapseTreeNodes\">This Wiki article</ulink> has some useful information about expanding and collapsing tree nodes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the JavaScript API?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I load the Scriptaculous library?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To load the whole Scriptaculous library shipped with RichFaces, use the <literal><a4j:loadScript></literal> tag:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This command lets you load an integrated version of the library that includes all existing Scriptaculous files, <emphasis>except</emphasis> <filename>unittest.js</filename>. If you do not want to load the whole library, but wish to load a specific file (for example, <filename>effect.js</filename>), use the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you load the whole library, you do not need to load a particular file."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid the problem with text wrapping in <literal><rich:tab></literal> in Internet Explorer 7?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The problem lies with a tab height bug in IE7. (Tab height is correct in Firefox and in IE6.) To work around the bug, you can change the doctype declaration from:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see the <ulink url=\"http://jira.jboss.com/jira/browse/RF-1011\">JIRA Issue</ulink> for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the status of the <literal><rich:effect></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:effect></literal> has several callback methods such as <literal>beforeStart</literal> and <literal>afterFinish</literal>, which can be used to save the status. You can also see the <ulink url=\"http://wiki.github.com/madrobby/scriptaculous/core-effects\">Scriptaculous Core Effects</ulink> page for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I send an additional parameter to the server with <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This example code gives you one method:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the example, the <literal>onselect</literal> event sends the selected value to the server. You can pass additional fields of the selected object (which do not belong to the <literal>fetchvalue</literal> attribute) in the same way."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I set the border of <literal><rich:dataTable></literal> to 0px?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your CSS file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I dynamically create a <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is a working example:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What should I change on the server side?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The list of zones to be rerendered can be specified as an EL expression. The list of IDs is formed during the <literal>RENDER_RESPONSE</literal> <emphasis>beforePhase</emphasis>, so you can point the <literal>reRender</literal> to the <classname>Set</classname>, and fill it during a tracking request to form a list of areas which can be dynamically updated."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I check request conditions before sending a request?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To check the terms of sending a request on a client, add the <literal>onSubmit</literal> attribute to all components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this example, the <literal>doSomething()</literal> function is executed before the AJAX request, and if the function returns <literal>false</literal>, the request is not fired."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The behavior of our <literal>onsubmit</literal> attribute differs slightly from the standard <literal>onsubmit</literal>. Do not return <literal>true</literal> if you want to fire the request: <code><xxx><a4j:support event=\"onclick\" onsubmit=\"return true;\"></code> becomes <code><xxx onclick=\"return true;A4J.Submit(.... );\" ></code> and standard event processing is fired instead of the request. Only return <literal>false</literal> if your conditions were not completed, or set actions to be performed without any returned response if you do need to fire the request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What were the changes to the <varname>onComplete</varname> attribute after version 1.0?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To avoid conflict with other JavaScript attributes, we have changed the placement of a function during a Javascript call. Rather than inserting attribute contents (<code>oncomplete:anotherFunction(this)</code>), we make the function anonymous (<code>oncomplete:function(){anotherFunction(this);}</code>) so that you can insert a <emphasis>chain</emphasis> of statements into an attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The change also means that the <literal>this</literal> keyword will point to a parameter map instead of a control element. You can use <code>document.findElementById()</code> to retrieve references to this parameter map after a request is processed. Pages updated with AJAX will then reference a control removed from a DOM tree."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you are certain that your element will not be updated, you can add <literal>onsubmit</literal> to your <literal><a4j:support></literal> tag (or <literal>onclick</literal> to your <literal><a4j:commandLink/Button></literal> tag) to place a reference to a known variable, like so: <code><a4j:commandLink onclick=\"var myControl=this;\" oncomplete=\"anotherFunction(myControl)\"/></code>)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The onComplete syntax now follows this form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>event</literal> is a variable defining the location in which the JavaScript event that fires the request will be placed. <literal>data</literal> is a variable containing the deserialized value of the <varname>data</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use InvokeOnComponent with JSF 1.2?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not use <literal>invokeOnComponent</literal> for two reasons:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To retain compatibility with JSF 1.1 and MyFaces applications, since these are often used in corporate applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>invokeOnComponent</literal> works well when used to communicate between a Widget and a backed component, or to update the content of a rendered component. However, there are some limitations for more complicated use-cases implemented in RichFaces, such as making update decisions with application logic."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that you must update whole components (for example, an entire <literal>dataTable</literal>), but all AJAX core action components in that component will work correctly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid generating exceptions for the <literal><a4j:keepAlive></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember: the component stores beans in a serialized view. Your bean should implement <literal>java.io.Serializable</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "My form will not submit, or, my setter is not called after an AJAX request. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This can occur because of conversion or validation errors at submission time. To verify this, place the following update message inside a form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:message></literal> component has built-in AJAX support, and can be combined with the <ulink url=\"http://www.jsfone.com/blog/max_katz/2008/07/creating_jsf_phase_listener.html\">JSF Phase Tracker</ulink> to fix this issue, in some instances."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I create an <literal>a4j</literal> delayed render zone?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><a4j:support></literal> component has a <varname>requestDelay</varname> attribute, where you can define the delay period."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use IgnoreDupResponses and requestDelay?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>ignoreDupResponses</varname> ignores an AJAX request if a newer request exists. <varname>requestDelay</varname> defines the time delay on the client between compiling a request response and sending that response. You can find more information in <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use eventsQueue attribute?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>eventsQueue</literal> defines the name of the queue that will order upcoming AJAX requests. The queue makes certain that redundant requests are not sent. It is created and named by default. You can find more information in the section on <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use multiple <literal><a4j:status></literal> components on one page?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes, you can. You can find out more from the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/status.jsf?c=status\">JBoss RichFaces Online Demos</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal><a4j:region></literal> component inside the <literal><a4j:repeat></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, you cannot. The <literal><a4j:region></literal> component cannot work inside iteration components such as <literal><h:dataTable></literal> and <literal><a4j:repeat></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I disable skinnability?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You cannot disable skinnability, but you can use a special skin: <literal>plain</literal>. This skin has no parameters, and was created to enable you to embed RichFaces components into existing projects with their own predefined styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does my reRender fail when using hide/show components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Rerendering fails when RichFaces tries to update a component that is defined as hidden or rendered. When <literal>rendered=\"false\"</literal>, the component is not added to the DOM tree, so it cannot be updated (as per the limitations described in the AJAX Processing chapter)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The correct way to rerender a hidden or rendered component is to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Wrap the component that is to be hidden or rendered on AJAX in a wrapper component such as <literal><a4j:outputPanel></literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Set the <varname>reRender</varname> attribute on the wrapper component instead of on the component itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Fpr example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This ensures that the wrapper component presents in the DOM tree, which means that its contents can be updated dynamically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why am I seeing a <exceptionname>ResourceNotRegistered</exceptionname> Exception?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces registers its resources (for example, scripts and images) after an application is accessed, and then accesses these via a generated URL. During application development, when an application is constantly updated on the server, RichFaces may re-register its resources after every server restart, while the browser may attempt to access resources via a cached URL."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve this problem by updating the browser cache: press <keycap>CTRL</keycap>+<keycap>F5</keycap>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I reRender only a particular row(s) of a table?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>ajaxKeys</literal> attribute defines Strings that are updated after an AJAX request, and lets you update several child components separately without updating the whole page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable row selection in a scrollableDataTable using <literal>one and multi-selection rows mode</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable row selection in <literal>one and multi-selection rows mode</literal>, you must use the <varname>selection</varname> attribute. In the example code that follows, when a user submits the form, the current collection of objects selected by the user is placed in the object's property. Upon completion, the <literal><rich:modalPanel></literal> will be rendered with the selected data."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, you can create a managed bean like the one below. The <literal>takeSelection()</literal> method fills the <literal>selectedCars</literal> Array with data retrieved from the <varname>selection</varname>. The <literal>getSelectedCars()</literal> method returns <literal>selectedCars</literal> Array, which is then used to populate select rows of the <literal><rich:dataTable></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I select several rows in a <literal>scrollableDataTable</literal> and drag-and-drop them into a <literal>dataTable</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, to enable row selection, see the previous section on <xref linkend=\"RowSelectionInScrollableDataTable\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable the drag-and-drop function on a <literal>dataTable</literal>, use the <literal><rich:dragSupport></literal> and <literal><rich:dropSupport></literal> components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous example is also available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/scrollableDataTable.jsf\">RichFaces LiveDemo</ulink> site. Only one method is added where the dropped collection is stored:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of the <rich:simpleTogglePanel>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>opened</varname> attribute responsible for storing panel state, and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:simpleTogglePanel></literal> icon appears and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered between page views."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, create a managed bean like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of <rich:panelMenuGroup>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>expanded</varname> attribute and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:panelMenuGroup></literal> expands and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered across page views."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I highlight the rows of a dataTable on the mouseover event?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <literal>onRowMouseOver</literal> and <literal>onRowMouseOut</literal> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable selecting the row of a <literal><rich:dataTable></literal> when I click on it, even if I click within the bounds of an <literal><h:inputText></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following JavaScript function to enable row selection when you click on the row:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can then use <literal><a4j:support></literal> with <varname>event</varname> and <varname>onsubmit</varname> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I rerender table cells with <a4j:support>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To rerender table cells with <literal><a4j:support></literal>, set exact ID values for each component to be updated, and point this <varname>id</varname> to the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The value of the <varname>reRender</varname> attribute belonging to the <literal> <a4j:support></literal> tag defines the sections of the page that will be updated. In the previous example code, the only update made is to the <literal><h:outputText></literal> component in the footer, because its <literal>id</literal> value matches the value of the <varname>reRender</varname> attribute. You can update multiple elements on a page by listing their IDs as the value of the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I create dynamic columns?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create dynamic columns by using the <literal><rich:column></literal> with the <varname>rendered</varname> attribute. Set the value of the <varname>rendered</varname> attribute to match the ID of the dynamic cell, as in the following example code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you could create a managed bean, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use RichFaces with Trinidad?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of a basic <filename>web.xml</filename> file that integrates RichFaces with Trinidad."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why do I see a JavaScript conflict?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Richfaces 3.1.3 uses version 1.6.0 of the <filename> prototype.js</filename> instead of version 1.5.1, which has been used in earlier versions. The source of the conflict is that two versions of the prototype script are included. The first is included as a dependency of the toggle panel components, and the second is included explicitly as a link."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces 3.1.3 is bundled with the same scripts included in Prototype 1.6.0 and Scriptaculous 1.8.0:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Using Prototype with RichFaces components can be problematic because issues that were fixed in version 1.6.0 were not always patched in version 1.5.1. When version 1.5.1 is used, some RichFaces components will not work as expected."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with the Seam Framework?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To use the <literal><rich:fileUpload></literal> component with the Seam Framework, define initialization parameters for the Seam Filter in your <filename>web.xml</filename> file. The Seam Framework will then automatically set the component up for the AJAX4JSF filter at start-up time."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of defining initialization parameters:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with MyFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The order in which filters are defined and mapped in <filename>web.xml</filename> is important to integrating the <literal><rich:fileUpload></literal> component with MyFaces. The code sample that follows shows the correct order in which to define your filters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To ensure that this sequence wors correctly, map the extension filter on your Faces Servlet, not to <filename>*.jsf</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable optional object selection in <rich:suggestionbox>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:suggestionBox></literal> component provides features such as object selection. To store the selected items as objects to be accessed, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the <varname>usingSuggestObjects</varname> attribute to the <literal><rich:suggestionBox></literal> component, and define it as <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <varname>onobjectchange</varname> event attribute to store the currently-selected objects."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All of the selected objects are stored in the <literal>suggestion.SelectedItems</literal> Array. Each Array element contains <literal>text</literal> and <literal>object</literal> properties, so you can iterate this Array, retrieve objects that are not <literal>null</literal>, and retrieve the required property."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for ViewExpiredException?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This exception appears after your session has timed out. Because RichFaces 3.1 is intended for use with JavaServer Faces 1.1, <exceptionname>ViewExpiredException</exceptionname>s will not generate automatically when RichFaces is used with JavaServer Faces 1.2. To work around this limitation, add the following to your <filename>web.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for Request Errors and Session Expiration?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To redefine the standard handlers that are responsible for processing different exceptional situations, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add custom <literal>onError</literal> and <literal>onExpire</literal> handlers, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more detailed description of this process, see <xref linkend=\"RequestErrorsAndSessionExpirationHandling\" /> in the Developer Guide."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Custom <literal>onError</literal> and <literal>onExpire</literal> handlers will not work under MyFaces, because MyFaces handles exceptions with an internally-generated debug page. To prevent this behavior, use the following code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I add a cookie in an AJAX response?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The bean described below adds a cookie to an AJAX response:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you can define the cookie to be included as shown in the following example. After the <literal>test</literal> cookie is set, the value of that cookie will appear on a page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is new in AJAX4JSF 3.2.x?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces 3.2.x releases have some new features:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><a4j:portlet</literal> component has been <emphasis>deprecated</emphasis>, since JSR-301 defines a similar function for <literal>UIViewRoot</literal> components;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><rich:ajaxValidator></literal>, <literal><rich:beanValidator></literal> and <literal><rich:graphValidator></literal> validators have been added to provide different validation types."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I launch the RichFaces sample on the JBoss server?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To launch the RichFaces sample application on the JBoss server, add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass a Boolean value in the <rich:componentControl> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code shows you how to avoid requiring a Boolean value:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use <code>'block'</code> instead of <code>' '</code> to avoid <literal>invalid style</literal> CSS errors."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/Getting_Started.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/Getting_Started.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,159 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Started with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This chapter tells you how to plug RichFaces components into a JSF application. The instructions are based on a simple <emphasis>JSF with RichFaces</emphasis> creation process, from downloading the required libraries to running the application in a browser. These instructions do not depend on the integrated development environment that is in use."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Simple JSF application with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> — the simple application — is similar to a typical <emphasis>hello world</emphasis> application, with one exception: the world of RichFaces will say \"Hello!\" to the user first."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a standard JSF 1.2 project named <literal>Greeter</literal>. Include all required libraries, and continue with the instructions that follow."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Adding RichFaces libraries into the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "From the <filename>RichFaces</filename> folder where you unzipped the RichFaces binary files, open the <filename>lib</filename>. This folder contains three <filename>*.jar</filename> files with API, UI, and implementation libraries. Copy these JARs from <filename>lib</filename> to the <filename>WEB-INF/lib</filename> directory of your <application>Greeter</application> JSF application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A JSF application with RichFaces assumes that the following JARs are available in the project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-beanutils-1.7.0.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-collections-3.2.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-digester-1.8.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-logging-1.0.4.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jhighlight-1.0.jar</filename>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering RichFaces in <filename>web.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "After you add the RichFaces libraries to the project, you must register them in the project <filename>web.xml</filename> file. Add the following to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For more information about RichFaces skins, read <xref linkend=\"Skinnability\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, your <filename>web.xml</filename> should look like this:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Managed bean"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <application>RichFaces Greeter</application> application needs a managed bean. In the project's <filename>JavaSource</filename> directory, create a new managed bean named <literal>user</literal> in the <literal>demo</literal> package. Place the following code in <filename>user</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering the bean in <filename>faces-cofig.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To register the <literal>user</literal> bean, add the following to the <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Greeter index.jsp"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> has only one JSP page. Create <filename>index.jsp</filename> in the root of <literal>WEB CONTENT</literal> folder and add the following to the JSP file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The application uses three RichFaces components: <emphasis role=\"bold\"><property><rich:panel></property></emphasis> is used as visual container for information; <emphasis role=\"bold\"><property><a4j:commandButton></property></emphasis> with built-in AJAX support lets a greeting be rendered dynamically after a response returns; and <emphasis role=\"bold\"><property><a4j:form></property></emphasis> helps the button to perform the action."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces tag library should be declared on each JSP page. For XHTML pages, add the following lines to declare your tag libraries:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Now, run the application on the server by pointing your browser to the <filename>index.jsp</filename> page: <literal>http://localhost:8080/Greeter/index.jsf</literal>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "\"RichFaces Greeter\" application"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Relevant Resources Links"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"https://www.redhat.com/apps/store/developers/jboss_developer_studio.html\">JBoss Developer Studio</ulink> includes tight integration with the RichFaces component framework. <!-- The following links might be useful for those who already use this IDE and RichFaces to develop applications, and for those who wish to improve their development process. -->"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/IDE_Support.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/IDE_Support.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/IDE_Support.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Integrated Development Environment Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is supported by both <ulink url=\"http://www.redhat.com/developers/rhds/index.html\">JBoss Developer Studio 1.0.0 GA</ulink> and <ulink url=\"http://www.jboss.org/tools/index.html\">Jboss Tools</ulink>. JBoss Developer Studio is a fully packaged Integrated Development Environment (IDE) that provides full support for Java Server Faces, RichFaces, Facelets, Struts and other Web technologies. It seamlessly combines visual and source-oriented development approaches. You can add JBoss Developer Studio capabilities to any JSF project by adding the appropriate libraries and modifying configuration files as required."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/Introduction.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/Introduction.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/Introduction.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,79 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is an open source framework that adds AJAX capability into existing JSF applications without resorting to JavaScript."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces leverages aspects of the JavaServer Faces (JSF) framework, including lifecycle, validation, conversion facilities, and management of static and dynamic resources. RichFaces components with built-in AJAX support and a highly customizable look-and-feel can be easily incorporated into JSF applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces allows you to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Experience the benefits of JSF while working with AJAX. RichFaces is fully integrated into the JSF lifecycle. Where other frameworks only allow access to the managed bean facility, RichFaces lets you access the action and value change listeners, and invokes server-side validators and converters during the AJAX request-response cycle."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add AJAX capabilities to existing JSF applications. The RichFaces framework provides two component libraries (Core AJAX and UI). The Core library adds AJAX functionality to existing pages, so you need not write any JavaScript or replace existing components with new AJAX components manually. RichFaces enables page-wide rather than component-wide AJAX support, giving you the opportunity to define events on the page. <!-- An event invokes an AJAX request and areas of the page which become synchronized with the JSF Component Tree after changing the data on the server by AJAX request in accordance with events fired on the client. -->"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily create different views with a variety of components, available out-of-the-box. The RichFaces UI library contains components for adding rich user interface (UI) features to JSF applications, providing you with a broad variety of AJAX-enabled components with extensive skins support. RichFaces components are designed to integrate seamlessly with other third-party component libraries, so you have more options when you develop applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Write your own rich components with built-in AJAX support. The Component Development Kit (CDK) is constantly being expanded. It includes both code generation and templating facilities and a simple JSP-like (JavaServer Pages) syntax, letting you create first-class rich components with built-in AJAX functionality."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Package resources with application Java classes. RichFaces provides advanced support for managing different resource types, including images, JavaScript code, and CSS stylesheets. The resource framework makes it easier to include these resources in JAR files with your custom component code."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily generate binary resources. The resource framework can generate images, sounds, Excel spreadsheets, etc. in real time, so you can, for example, create images with the Java Graphics 2D library and other similar resources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customize the look and feel of your user interface with skins-based technology. RichFaces lets you easily define and manage different color schemes and other user interface parameters by using named <emphasis>skin parameters</emphasis>. This means you can access UI parameters from JSP and Java code to adjust your UI in real time. RichFaces includes a number of predefined skins to kick-start your application's development, but it is easy to create your own custom skins."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Simultaneously create and test your components, actions, listeners, and pages. RichFaces will soon include an automated testing facility to generate test cases for your component as you develop it. The testing framework tests not only the components, but also any other server-side or client-side functionality, including JavaScript code — and it will do so <emphasis>without</emphasis> deploying the test application into the Servlet container."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces UI components can be implemented immediately, right out of the box. This saves development time and gives you immediate access to RichFaces web application development features, so experience with RichFaces is fast and easy to obtain."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/Links_to_Resources.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/Links_to_Resources.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/Links_to_Resources.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,74 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Links to information resources"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Links"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/portal/jbossrichfaces/\">JBoss RichFaces</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss Forum"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://jboss.com/index.html?module=bb&op=main&c=27\">JBoss Forums</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Wiki"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/wiki/RichFaces\">RichFaces Wiki</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Blog"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "<ulink url=\"http://jroller.com/page/a4j\">RichFaces Blog</ulink>"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/Revision_History.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/Revision_History.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/Revision_History.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: member
+#, no-c-format
+msgid "JIRA corrections."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/RichFaces_Developer_Guide.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/RichFaces_Developer_Guide.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/RichFaces_Developer_Guide.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/Settings.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/Settings.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/Settings.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,334 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Settings for different environments"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces includes support for all tags (components) included in the JavaServer Faces (JSF) specification. To add RichFaces capabilities to an existing JSF project, place the RichFaces libraries into the <filename>lib</filename> directory of the project, and add filter mapping. The behavior of the existing project does not change when you add RichFaces."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Application Descriptor Parameters"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not require that any parameters be defined in your <filename>web.xml</filename>, but the RichFaces parameters listed below will help you during the development process and increase the flexibility of your RichFaces applications."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.SKIN"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The name of a skin that is used in an application. Can be a literal string with a skin name or the EL expression (<literal>#{...}</literal>) associated with a String property (skin name) of a property of a <literal>org.richfaces.framework.skin</literal> type. In the latter case, that instance is used as the current skin."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadScriptStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces script files are loaded to the application. Possible values are <literal>ALL</literal>, <literal>DEFAULT</literal> and <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadStyleStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces style files are loaded into the application. Possible values are: <literal>ALL</literal>, <literal>DEFAULT</literal>, or <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.LOGFILE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "none"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The URL of an application or a container log file (if applicable). If this parameter is set, content from the given URL is shown on a Debug page in the <literal>iframe</literal> window."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.VIEW_HANDLERS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of <literal>ViewHandler</literal> instances for inserting in a view handler chain. These handlers are inserted before the RichFaces viewhandlers, in the order they are listed. In a Facelets application, you would declare <literal>com.sun.facelets.FaceletViewHandler</literal> here instead of in the <filename>faces-config.xml</filename> file."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.CONTROL_COMPONENTS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of special <emphasis>control case</emphasis> components, such as the messages bundle loader or an alias bean component. These handlers are provided via a reflection from the static field <literal>COMPONENT_TYPE</literal>. Encoding methods for these components are always called while rendering AJAX responses, even if a component has not been updated."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_RESOURCE_DATA"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "false"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "For generated resources (such as encrypt generation data), this is encoded in the resource URL. For example, the URL of an image generated by the <classname>mediaOutput</classname> component contains the name of a generation method. Since malicious code can exploit this to create a request for any JSF bean or attribute, this parameter should be set to <literal>true</literal> in critical applications. (This fix works with Java Runtime Environment 1.4.)"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_PASSWORD"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "random"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A password used to encrypt resource data. If this is not set, a random password is used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.COMPRESS_SCRIPT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "true"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "When defined, does not allow the frameword to reformat JavaScript files. This means that the debug feature cannot be used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URLs of all generated resources. This is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.GLOBAL_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/g"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URI of all global resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SESSION_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/s"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be used to track the sessions of generated resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.DEFAULT_EXPIRE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "86400"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the period (in seconds) for which resources are cached when they are streamed back to the browser."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SERIALIZE_SERVER_STATE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "If set to <literal>true</literal>, the component state (not the tree) will be serialized before it is stored in the session. This can be useful in applications with view state that is sensitive to model changes. Alternatively, use <literal>com.sun.faces.serializeServerState</literal> and <literal> org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</literal> parameters in their respective environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>org.richfaces.SKIN</literal> is used in the same way as <literal>org.ajax4jsf.SKIN</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "org.ajax4jsf.Filter Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "log4j-init-file"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "-"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A path (relative to the web application's context) to the <filename>log4j.xml</filename> configuration file. This can be used to set up per-application custom logging."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "enable-cache"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Enables caching of framework-generated resources (JavaScript, CSS, images, etc.). However, your cached resources will not be used when attempting to debug custom JavaScript or Styles."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "forcenotrf"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Forces all JSF pages to be parsed by a HTML syntax check filter. If set to <literal>false</literal>, only AJAX responses will be parsed and converted to well-formed XML. Setting this to <literal>false</literal> can improve performance, but may also cause unexpected information to be rendered during AJAX updates."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Sun JSF RI"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces works with JavaServer Faces 1.2_13 without needing to modify additional settings."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Facelets Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces has high-level support for Facelets, regardless of the version used. However, some JSF frameworks (including Faces) require that their own <literal>ViewHandler</literal> be listed first in the <literal>ViewHandler</literal> chain. RichFaces also requires that its <literal>AjaxViewHandler</literal> be listed first, but because it is installed first, no settings will need to be altered. Where multiple frameworks are used without RichFaces, you can use the <literal>VIEW_HANDLERS</literal> parameter to define the order in which the <literal>ViewHandler</literal>s are used. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This declares that while <literal>Facelets</literal> will officially be first, <literal>AjaxViewHandler</literal> will briefly be ahead of it to perform some small, important task."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this case, you need not define <literal>FaceletViewHandler</literal> in <filename>WEB-INF/faces-config.xml</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JBoss Seam Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is compatible with <application>JBoss Seam</application> and Facelets when run within JBoss Enterprise Application Server. No additional JARs are required. All you need to do is package the RichFaces library with your application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For <application>Seam 1.2</application>, your <filename>web.xml</filename> must be as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>Seam 2.x</application> supports RichFaces Filter, so your <filename>web.xml</filename> must look like this:"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/ja-JP/Technical_Requirements.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/ja-JP/Technical_Requirements.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/ja-JP/Technical_Requirements.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,179 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Technical Requirements"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces</application> was developed with an open architecture to ensure that it was compatible with the widest possible variety of environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This is what you need to start working with <application>RichFaces 3.3.1</application>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JavaServer Faces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java Application Server <emphasis>or</emphasis> Servlet Container"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Browser (on client side)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Java Versions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JDK 1.5 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported JavaServer Faces Implementations and Frameworks"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun JSF-RI - 1.2_12"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "MyFaces 1.2.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Facelets 1.1.1 - 1.2"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Seam 1.2. - 2.1.0"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Servers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Apache Tomcat 5.5 - 6.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "BEA WebLogic 9.1 - 10.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Resin 3.1"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Jetty 6.1.x"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun Application Server 9 (J2EE 1.5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "GlassFish (J2EE 5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JBoss 4.2.x - 5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Websphere 7.0. and higher"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Geronimo 2.0 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Browsers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6.0 - 8.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Firefox 2.0 - 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera 8.5 - 9.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Google Chrome"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This list is composed from user reports of compatibility. We assume that this list is incomplete, so the absence of your environment from the list does not necessarily mean that it is incompatible with RichFaces."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "We appreciate your feedback about compatible platforms and browsers that are not listed here. This helps us keep the list up-to-date."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/Architecture_Overview.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/Architecture_Overview.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/Architecture_Overview.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,1829 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Basic concepts of the RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces Framework is implemented as a component library that adds AJAX capabilities into existing pages. This means that you do not need to write any JavaScript code or replace existing components with new AJAX widgets. RichFaces enables page-wide AJAX support instead of the traditional component-wide support, so you can define areas of the page that will reflect changes made by AJAX events on the client."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram following shows the process in full:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Processing flow"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you use JSF tags to define sections of a JSF page that you wish to update with the results of an AJAX request. It also provides you with several options for sending AJAX requests to the server. You do not need to write any JavaScript or <literal>XMLHTTPRequest</literal> objects by hand — everything is done automatically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Architecture Overview"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following figure lists several important elements of the RichFaces Framework."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Core AJAX component structure"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Filter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To make the most of RichFaces, you should register a <literal>Filter</literal> in your application's <filename>web.xml</filename>. The <literal>Filter</literal> recognizes multiple request types. The sequence diagram in Figure 5.3 shows the differences in processing between a <emphasis>regular</emphasis> JSF request and an AJAX request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request processing sequence diagram"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In either case, the required static or dynamic resource information that your application requests is registered in the <literal>ResourceBuilder</literal> class."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When a resource request is issued, the RichFaces filter checks the <literal>Resource Cache</literal> for this resource. If it is present, the resource is returned to the client. Otherwise, the filter searches for the resource among those registered in the <literal>ResourceBuilder</literal>. If the resource is registered, the RichFaces filter requests that the <literal>ResourceBuilder</literal> creates (delivers) the resource."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram that follows illustrates the process of requesting a resource."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Resource request sequence diagram"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Action Components"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "AJAX Action components are used to send AJAX requests from the client side. There are a number of AJAX Action components, including <literal><a4j:commandButton></literal>, <literal><a4j:commandLink></literal>, <literal><a4j:poll></literal>, and <literal><a4j:support></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Containers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>AjaxContainer</literal> is an interface that defines an area on your JSF page that should be decoded during an AJAX request. <literal>AjaxViewRoot</literal> and <literal>AjaxRegion</literal> are both implementations of this interface."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JavaScript Engine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces JavaScript Engine runs on the client side, and updates different areas of your JSF page based on information from the AJAX response. This JavaScript code operates automatically, so there is no need to use it directly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors and Session Expiration Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you redefine the standard handlers responsible for processing exceptions. We recommend defining your own JavaScript, which will be executed when exceptional situations occur."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To execute your own code on the client in the event of an error during an AJAX request, you must redefine the standard <literal>A4J.AJAX.onError</literal> method like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function accepts the following as parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>req</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a parameter string of a request that calls an error"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>status</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the number of an error returned by the server"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>message</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for the given error"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, you can create your own handler that is called when timeouts, internal server errors, etc. occur."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Session Expired Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also redefine the <literal>onExpired</literal> framework method that is called on the <literal>SessionExpiration</literal> event."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Example:</emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function can take the following parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>loc</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the URL of the current page (can be updated on demand)"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>expiredMsg</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for display in the event of <literal>SessionExpiration</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customized <literal>onExpire</literal> handlers do not work under MyFaces. MyFaces handles exceptions by internally generating a debug page. To prevent this behavior, use the following:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skinnability"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you look at any CSS (Cascading Style Sheets) file in an enterprise application, you will notice how often the same color is noted. Standard CSS cannot define a particular colour abstractly as a panel header color, the background color of an active pop-up menu item, a separator color, etc. To define common interface styles, you must copy the same value multiple times, and the more interfaces you have, the more repetition is required."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, if you want to change the palette of an application, you must change all interrelating values, or your interface can appear clumsy. If a customer wants to be able to adjust their interface's look and feel in real time, you must be able to alter several CSS files, each of which will contain the same value multiple times."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve these problems with the <emphasis>skins</emphasis> that are built into and rully implemented in RichFaces. Every named skin has <emphasis>skin parameters</emphasis> that define a palette and other attributes of the user interface. By changing a few skin parameters, you can alter the appearance of dozens of components simultaneously, without interfering with interface consistency."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinnability</literal> feature cannot completely replace standard CSS, and does not eliminate its usage. Instead, it is a high-level extension of standard CSS that can be used in combination with regular CSS declarations. You can also refer to skin parameters in CSS through the JSF Expression Language. This lets you completely synchronize the appearance of all elements in your pages."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Using Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces <emphasis>skinnability</emphasis> is designed for use alongside:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "skin parameters defined in the RichFaces framework,"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "predefined CSS classes for components, and"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "user style classes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A component's color scheme can be applied to its elements using any of three style classes:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A default style class inserted into the framework"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This contains stle parameters that are linked to some constants from a skin. It is defined for every component and specifies a default level of representation. You can modify an application interface by changing the values of the skin parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A style class of skin extension"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This class name is defined for every component element, and inserted into the framework to let you define a class with the same name in your CSS files. This lets you easily extend the appearance of all components that use this class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "User style class"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use one of the <literal>styleClass</literal> parameters to define your own class for component elements. As a result, the appearance of one particular component is changed according to a CSS style parameter specified in the class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Example"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following is an example of a simple <emphasis>panel</emphasis> component:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This code generates a panel component on a page, which consists of two elements: a wrapper <literal><div></literal> element and a <literal><div></literal> element for the panel body with the specified style properties. The wrapper <literal><div></literal> element will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>dr-pnl</literal> is a CSS class that is specified in the framework via skin parameters:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>background-color</varname> is defined with <literal>generalBackgroundColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>border-color</varname> is defined with <literal>panelBorderColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change all colors for all panels on all pages by changing these skin parameter values. However, if you specify a <literal><rich:panel></literal> class on the page, its parameters are also acquired by all panels on this page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Developers can also change the style properties for panel. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous definition could add some style properties from <literal>customClass</literal> to one particular panel. As a result, we will get three styles:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skin Parameters Tables in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces provides eight predefined skin parameters (skins) at the simplest level of common customization:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "plain"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "emeraldTown"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "blueSky"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "wine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "japanCherry"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ruby"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "classic"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "deepMarine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To apply a skin, you must specify a skin name in the <varname>org.richfaces.SKIN</varname> context parameter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following table shows the values for each parameter in the <literal>blueSky</literal> skin:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Colors"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Parameter name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#BED6F8"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerGradientColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#F2F7FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#000000"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerWeightFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bold"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FFFFFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "11px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Arial, Verdana, sans-serif"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "additionalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#ECF4FE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowOpacity"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "panelBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "subBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C6DEFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabDisabledTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#8DB7F3"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "trimColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#D6E6FB"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FAE6B0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E5973E"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "selectControlColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E79A00"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0078D0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0090FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "visitedLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Fonts"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableFooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#cccccc"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableSubfooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#f1f1f1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C0C0C0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>plain</literal> skin was added in version 3.0.2. It has no parameters, and is important when embedding RichFaces components into existing projects with their own styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Creating and Using Your Own Skin File"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To create your own skin file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a file. In it, define skin constants to be used by style classes (see <xref linkend=\"SkinParametersTablesInRichFaces\" />). The name of the skin file should follow this format: <literal><name>.skin.properties</literal>. (For examples of this file, see the RichFaces predefined skin parameters: <literal>blueSky</literal>, <literal>classic</literal>, <literal>deepMarine</literal>, etc. These files are located in the <filename>richfaces-impl-xxxxx.jar</filename> archive in the <filename>/META-INF/skins</filename> folder."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the skin definition <literal><contex-param></literal> to the <filename>web.xml</filename> of your application, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place your <literal><name>.skin.properties</literal> file in either your <filename>/META-INF/skins</filename> or <filename>/WEB-INF/classes</filename> directory."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Built-in Skinnability in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you incorporate skins into your user interface (UI) design. This framework lets you use named skin parameters in your properties files to control skin appearance consistently across a set of components. You can see examples of predefined skins at: <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">http://livedemo.exadel.com/richfaces-demo/ </ulink>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Skins let you define a style in which to render standard JSF components and custom JSF components built with RichFaces. You can experiment with skins by following these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a custom render kit and register it in the <filename>faces-config.xml</filename> like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, create and register custom renderers for the component based on the look-and-feel predefined variables:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, place a properties file with skin parameters into the class path root. There are two requirements for the properties file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The file must be named <filename><replaceable>skinName</replaceable>.skin.properties</filename>. In this case, we would call it <literal>newskin.skin.properties</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The first line in this file should be <literal>render.kit=<replaceable>render-kit-id</replaceable></literal>. In this case, we would use <literal>render.kit=NEW_SKIN</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "More information about creating custom renderers can be found at: <ulink url=\"http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html\">http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Changing skin in runtime"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change skins during runtime by defining the following EL-expression in your <filename>web.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinBean</literal> code looks like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also set the <varname>skin</varname> property's initial value in the configuration file. To set <literal>classic</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also change the properties of the default skin. To do so, edit the properties of the default skin. The following shows you example page code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The above code will generate the following list of options:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Controls Skinning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This feature is designed to unify the look and feel of standard HTML elements and RichFaces components. Skinning can be applied to all controls on a page based on element names and attribute types (where applicable). This feature also provides a set of CSS styles that let skins be applied by assigning <literal>rich-*</literal> classes to particular elements, or to a container of elements that nests controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard Controls Skinning provides two levels of skinning: <emphasis>Basic</emphasis> and <emphasis>Extended</emphasis>. The level used depends on the browser type detected. If the browser type cannot be detected, <literal>Extended</literal> is used. However, if you want to explicitly specify the level to be applied, add a <varname></varname> context parameter to your <filename>web.xml</filename> and set the value to either <literal>basic</literal> or <literal>extended</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Basic</emphasis> level provides customization for only basic style properties. Basic skinning is applied to the following browsers:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in BackCompat mode (see <ulink url=\"http://msdn2.microsoft.com/en-us/library/ms533687(VS.85).aspx\">document.compatMode property in MSDN</ulink>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Extended</emphasis> level introduces a broader number of style properties on top of basic skinning, and is applied to browsers with rich visual styling control capabilities. The following browsers support Extended skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Mozilla Firefox"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in Standards-compliant mode (CSS1Compat mode)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following elements can be modified with skins:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>input</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>select</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>textarea</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>keygen</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>isindex</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>legend</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>fieldset</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>hr</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>a</literal> (together with the <literal>a:hover</literal>, <literal>a:visited</literal> pseudo-elements)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two ways to initialize skinning for standard HTML controls:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. This method implies that skinning style properties are applied per-element and attribute type (where applicable). No additional steps are required. See the <xref linkend=\"BasicLevel\" /> and <xref linkend=\"ExtendedLevel\" /> tables for elements to which skinning can be applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. When enabled, you are provided with a set of predefined CSS classes to apply skins to your HTML components."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enabling <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> provides you style classes that can be applied to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "basic elements nested within elements with a <emphasis>rich-container</emphasis> class. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements with a class name that corresponds to one of the basic element names or types are mapped with the <literal>rich-<elementName>[-<elementType>]</literal> scheme, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements are given classes depending upon their <literal>link</literal> type and pseudo-class name, for example, <literal>rich-link</literal>, <literal>rich-link-hover</literal>, <literal>rich-link-visited</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The predefined rich CSS classes provided can be used as classes for both basic and complex HTML elements."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code snippet shows several elements as an example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more thorough look at standard component skinning, we recommend exploring the CSS files located in the <filename>ui/core/src/main/resources/org/richfaces/</filename> directory of the RichFaces SVN repository."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex and legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "CSS Properties"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-size"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-family"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for hr"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:hover"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColorgeneralLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Elements Skin Bindings for .rich-input, .rich-select, .rich-textarea, .rich-keygen, .rich-isindex, .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-fieldset"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-hr"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-width"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-style"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "solid"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:hover"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin parameters/Value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "inset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-color"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "no-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-position"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px 1px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-edit"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "editBackgroundColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-error"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "warningBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding-left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "7px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button, .rich-button-disabled, .rich-button-over"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "2px 10px 2px 10px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "text-align"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "cursor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "pointer"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "repeat-x"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "top left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button-press"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bottom left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-container fieldset, .rich-fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "10px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-weight"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-form"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "0px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "margin"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Extended level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-image"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for button[type=button], button[type=reset], button[type=submit], input[type=reset], input[type=submit], input[type=button]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button[disabled], .rich-container *|button[disabled], .rich-button-disabled"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonDisabledBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for .rich-button-disabled, .rich-container button[type=\"button\"][disabled], .rich-button-button-disabled, .rich-container button[type=\"reset\"][disabled], .rich-button-reset-disabled, .rich-container button[type=\"submit\"][disabled], .rich-button-submit-disabled, .rich-container input[type=\"reset\"][disabled], .rich-input-reset-disabled, .rich-container input[type=\"submit\"][disabled], .rich-input-submit-disabled, .rich-container input[type=\"button\"][disabled], .rich-input-button-disabled"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *button[type=\"button\"][disabled], button[type=\"reset\"][disabled], button[type=\"submit\"][disabled], input[type=\"reset\"][disabled], input[type=\"submit\"][disabled], input[type=\"button\"][disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.InputBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for textarea[type=textarea], input[type=text], input[type=password], select"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea[disabled], .rich-container *|textarea[disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "textarea[type=\"textarea\"][disabled], input[type=\"text\"][disabled], input[type=\"password\"][disabled]"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The basic skinning level can fail if the <literal>ajaxPortlet</literal> is configured as follows:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Client-side Script for Extended Skinning Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Extended skinning of standard HTML controls is applied automatically: the browser type is detected, and if a browser does not fully support extended skinning, only basic skinning is applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are some problems with standard HTML controls in certain browsers (Opera and Safari) that may cause problems if you wish to skin your RichFaces components and standard HTML controls manually."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable skinnability, set the <varname>org.richfaces.LoadStyleStrategy</varname> parameter to <literal>NONE</literal> in your <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You should also include the style sheets that apply skins to RichFaces components and standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To work around the problem of extended skinning in Opera and Safari, the <filename>skinning.js</filename> client script is added to the RichFaces library. This detects the browser type and enables extended skinning only for browsers that fully support it."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Activate the script by inserting the following JavaScript into your page:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When no script-loading strategy is used and extended skinning is enabled, a warning message appears in the console."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also specify the <varname>media</varname> attribute in the <literal>link</literal> tag. This adds the <filename>extended_both.xcss</filename> style sheet to <literal>rich-extended-skinning</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include your style sheets to the page when automatic skinnability is disabled, add the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Base64 encoder now uses <literal>!</literal> instead of <literal>.</literal>, so remember to use the <literal>a4j/versionXXX</literal> resources prefix instead of <literal>a4j_versionXXX</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "XCSS File Format"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Cross-site Cascading Style Sheet (XCSS) files are the core of RichFaces component skinnability. XCSS is XML-formatted CSS that extends the skinning process. RichFaces parses the XCSS file containing all look and feel parameters of a particular component and compiles the information into a standard CSS file that can be recognized by a web browser."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The XCSS file contains CSS properties and skin parameter mappings. Mapping a CSS selector to a skin parameter can be done with <literal>< u:selector ></literal> and <literal>< u:style></literal> XML tags, which define the mapping structure, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "During processing, this code will be parsed and assembled into a standard CSS format, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>name</varname> attribute of <literal><u:selector></literal> defines the CSS selector, while the <varname>name</varname> attribute of the <literal><u:style></literal> tag defines the skin constant that is mapped to a CSS property. You can also use the <varname>value</varname> attribute of the <literal><u:style></literal> tag to assign a value to a CSS property."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "CSS selectors with identical skin properties can be included in a comma-separated list:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Plug-n-Skin</emphasis> lets you easily create, customize, and plug in a custom skin to your project. You can create skins based on the parameters of predefined RichFaces skins. Plug-n-Skin also lets you unify the appearance of rich controls with standard HTML elements. This section contains step-by-step instructions for creating your own skin with Plug-n-Skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, use Maven to create a template for your new skin. (You can find more information about configuring Maven for RichFaces in the <!-- #modify add info? --><ulink url=\"http://wiki.jboss.org/wiki/HowToConfigureMavenForRichFaces\">JBoss wiki article</ulink>. These Maven instructions can be copied and pasted into the command line interface to execute them."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Primary keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>archetypeVersion</varname> — indicates the RichFaces version; for example, <literal>3.3.1.GA</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>artifactId</varname> — the artifact ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>groupId</varname> — the group ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>version</varname> — the version of the project you create. By default, this is set to <literal>1.0.-SNAPSHOT</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This operation creates a directory named after your <literal>ARTIFACT-ID</literal>. The directory contains a template of the Maven project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following steps will guide you though creating of the skin itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Run the following command from the root directory of the Maven project. (This directory will contain your <filename>pom.xml</filename> file.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>name</varname> — defines the name of the new skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>package</varname> — the base package of the skin. By default, the project's <literal>groupId</literal> is used."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Additional optional keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — defines the name of the base skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>createExt</varname> — if set to <literal>true</literal>, extended CSS classes are added. For more information, please, see <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once these operations are complete, the following files and folders should have been created:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImage.java</filename> — the base class used to store images. Location: <filename>\\src\\main\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImageTest.java</filename> — a test version of a class that stores images. Location: <filename>\\src\\test\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>XCSS files</filename> — XCSS files define the new look of RichFaces components affected by the new skin. Location: \"\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.properties</filename> — a file that contains the new skin's properties. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following properties are used to configure the <filename>SKIN-NAME.properties</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — the name of the skin to be used as a basis for your own skin. The look of the skin you define will be affected by the new style properties."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>generalStyleSheet</varname> — a path to the style sheet (<filename>SKIN-NAME.xcss</filename>) that imports your component's style sheets to be modified by the new skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>extendedStyleSheet</varname> — the path to a style sheet that is used to unify the appearance of RichFaces components and standard HTML controls. For additional information, read <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>gradientType</varname> — a predefined property to set the type of gradient applied to the new skin. Possible values are <literal>glass</literal>, <literal>plastic</literal>, <literal>plain</literal>. More information on gradient implementation you can find further in this chapter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.xcss</filename> — an XCSS file that imports the component's XCSS files to be modified by the new skin. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>XCSS files</literal> — creates the XCSS files that determine styles for standard controls (<filename>extended_classes.xcss</filename> and <filename>extended.xcss</filename>), if the <varname>createExt</varname> key is set to <literal>true</literal>. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-ext.xcss</filename> — creates the <filename>SKIN-NAME-ext.xcss</filename> file that imports defining styles for standard controls if <varname>createExt</varname> is set to <literal>true</literal>. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-resources.xml</filename> — contains descriptions of all files listed previously. Location: <filename>src\\main\\config\\resources</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now start editing the XCSS files located in <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>. Assign new style properties to your selectors (listed in the XCSS files) in either of the following ways:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard CSS coding approach (that is, add CSS properties to the selectors). Remember that the selectors must be within <literal><f:verbatim> </f:verbatim></literal> tags. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "XCSS coding approach (the usual method of creating XCSS files in RichFaces). XCSS tags must be placed <emphasis>outside</emphasis> <literal><f:verbatim> </f:verbatim></literal> tags."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once you have performed these steps and edited the XCSS files, build the new skin and plug it into the project. To build the skin, execute the following command from the root directory of your skin project (the directory that contains your <filename>pom.xml</filename> file):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Plug-n-skin feature also has a number of predefined gradients. The following code can be used to apply a gradient:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>background-image</varname> CSS property is defined with <literal><f:resource f:key=\"org.richfaces.renderkit.html.CustomizeableGradient\"></literal>, which sets the gradient. The gradient type can be specified in the <filename>SKIN-NAME.properties</filename> with the <varname>gradientType</varname> property, which can be set to <literal>glass</literal>, <literal>plastic</literal>, or <literal>plain</literal>. The gradient can then be adjusted with the <varname>baseColor</varname>, <varname>gradientColor</varname>, <varname>gradientHeight</varname>, <varname>valign</varname> attributes, as seen in the previous code snippet."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now use your newly-created skin in your project by adding your new skin parameters to the <filename>web.xml</filename> file, and placing the JAR file containing your skin (located in the <filename>target</filename> directory of your skin project) in the <filename>\\WebContent\\WEB-INF\\lib\\</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Details of Usage"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This section covers some practical aspects of Plug-n-Skin implementation. We assume that you have read the section of the guide describing the Plug-n-Skin prototype creation process."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, we must create a new skin (as described in the previous section). The following creates a template of the new skin project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now browse the <filename>P-n-S</filename> directory to view the files and folders created."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use Maven to add all required files to the skin project, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As mentioned in the previous section, <!-- #modify '-D' typo? --><literal>-DbaseSkin</literal> defines the RichFaces built-in skin to use as a base, and <literal>-DcreateExt=true</literal>, which determines that the new skin will include XCSS files that unify the appearance of the rich components and the standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once your resources have been created, you can begin refining the newly-created skin. Begin by editing the rich components' XCSS files."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example of the Plug-n-Skin feature, we will edit some <literal><rich:calendar></literal> style attributes and some basic HTML controls. We will show you how to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor the background of the current day in the <literal><rich:calendar></literal>;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor a standard HTML submit button;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To edit <literal><rich:properties></literal>'s style properties, you must open the <filename>calendar.xcss</filename> file, located in <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the <filename>calendar.xcss</filename> file, find the <literal>.rich-calendar-today</literal> selector and amend it as follows:<literal>background-color: #075ad1;</literal>. This will change the background color of the current day."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next we will change the font style of a standard HTML <emphasis>submit</emphasis> button. Open the <filename>extended.xcss</filename> file from the <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename> directory and insert <literal>font-weight: bold;</literal> between the curly braces of these selectors, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The desired changes have now been made, and you can proceed to building the new <literal>PlugnSkinDemo</literal> skin and importing it into the project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Build the skin by executing <command>mvn clean install</command> from the <filename>P-n-S</filename> directory. This creates a <filename>target</filename> directory containing a JAR file with a newly-compiled skin. In our case, the file is named <filename>P-n-S-1.0.-SNAPSHOT.jar</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, import the new <literal>PlugnSkinDemo</literal> skin into your project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Copy the <filename>P-n-S-1.0.-SNAPSHOT.jar</filename> file to the <filename>\\WebContent\\WEB-INF\\lib\\</filename> directory."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the name of the new skin to the <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember, standard controls skinning must be enabled in <filename>web.xml</filename>. Add the following to enable standard controls skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The results of each alteration to the skin are shown in the figures that follow:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin feature in action."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "State Manager API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JSF has an advanced navigation mechanism that lets you define <emphasis>navigation</emphasis> from view to view. In a web application, navigation occurs when a user changes from one page to another by clicking on a button, a hyperlink, or another command component. There is no switch mechanism between some logical states of the same view. For example, in <emphasis>Login/Register dialog</emphasis>, an existing user signs in with his user name and password, but if a new user attempts to register, an additional field (<literal>Confirm</literal>) is displayed, and button labels and methods are changed when the user clicks the <guilabel>To register</guilabel> link:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Login Dialog"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Register Dialog"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>RichFaces State API</emphasis> lets you easily define a set of states for pages, and properties for these states."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>States</varname> class interfaces with a <property>map</property>, where the <methodname>keySet</methodname> defines the State name and the <methodname>entrySet</methodname> is a <varname>State</varname> <property>map</property>. The <varname>State</varname> <property>map</property> defines the properties, method bindings, or constant state variables of a key or object, where these values may change depending on the active State."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces State API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One of the most convenient features of the RichFaces State API is the ability to navigate between <varname>State</varname>s. The API implements changes in <varname>State</varname> through standard JSF navigation. When the action component returns an outcome, the JSF navigation handler (extended through the RichFaces State API) checks whether the outcome is registered as a <emphasis><varname>State</varname> change outcome</emphasis>. If <literal>true</literal>, the corresponding <varname>State</varname> is activated. If <literal>false</literal>, standard navigation handling is called."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Implement the RichFaces State API like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register the State Navigation Handler and the EL Resolver in your <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register an additional application factory in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register two managed beans in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One bean (<literal>config</literal>) defines and stores <varname>State</varname> as seen in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second bean, with the <literal>org.richfaces.ui.model.States</literal> type (<literal>state</literal>), contains the managed property <property>states</property>, which is bound to the first <literal>config</literal> bean."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use <property>state</property> bindings on the page, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To see complete example of the Login/Register dialog, see the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/stateAPI.jsf?c=stateAPI\">RichFaces Live Demo</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Identifying User Roles"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces also lets you check whether the logged-in user belongs to a certain <property>user role</property> with the <literal>rich:isUserInRole(Object)</literal> function. This function takes a String or a comma-delineated list of Strings, a Collection, etc. as arguments and returns a Boolean value."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example, imagine that you need to render some controls only for administrators. To do so, create an administrator role (<literal>admin</literal>) in your <filename>web.xml</filename> file. Then implement authorization that assigns the <literal>admin</literal> role to the user that has logged in as an administrator. Once this has been done, you can use the <literal>rich:isUserInRole(Object)</literal> function with the <varname>rendered</varname> attribute of any component. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Here, only a logged-in user with an <literal>admin</literal> role can see the text editor, which will not be rendered for users with other roles."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/Author_Group.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/Author_Group.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/Author_Group.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/Book_Info.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/Book_Info.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/Book_Info.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Developer Guide"
+msgstr ""
+
+#. Tag: subtitle
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/FAQ.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/FAQ.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/FAQ.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,989 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "FAQ"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find additional information on RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most important links for RichFaces can be found <ulink url=\"http://jboss.com/index.html?module=bb&op=viewtopic&t=104575\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where are the binary/source distributions for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Distributions are available from the <ulink url=\"http://labs.jboss.com/jbossrichfaces/downloads/\">JBoss RichFaces Download area</ulink>. The source distribution is found in the <filename>richfaces-ui-3.3.0-src.zip</filename> file. The binary distribution is in the <filename>richfaces-ui-3.3.0-bin.zip</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I manually build a RichFaces snapshot?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This <ulink url=\"http://labs.jboss.com/wiki/HowToBuildRichFacesSnapshotManually\"> wiki article</ulink> takes you through the process."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I configure Maven for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, download and install Maven. (Follow the instructions at <ulink url=\"http://maven.apache.org/download.html\">http://maven.apache.org/download.html</ulink>.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Open the <filename><Maven-Root>/conf/settings.xml</filename> file and add the following to the <literal><profile></literal> section:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following to the <literal><activeProfiles></literal> section:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is the structure of RichFaces SVN repository?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can see the structure in the RichFaces Repository Structure Overview in <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">this Wiki article</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I build <literal>richfaces-samples</literal> applications?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "he <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">RichFaces Repository Structure Overview</ulink> describes how to build <literal>richfaces-samples</literal> applications in Eclipse."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find a demo for RichFaces components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Online demo applications that showcase RichFaces features are available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also find a nightly build (in the WAR format) <ulink url=\"http://maven.exadel.com/org/richfaces/samples/richfaces-demo/3.1.0-SNAPSHOT/\">here</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Source Code (SVN) can be found <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-demo/\">in the JBoss RichFaces SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What causes the \"Prototype.Browser() function cannot be found\" error in RichFaces 3.1.0, and how do I fix it?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Your application probably uses an older version of Prototype from Tomahawk 1.1.6. RichFaces 3.1.0 uses the latest Prototype (1.5.1.1). Upgrade your version of Prototype to solve this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does the RichFaces library contain the <literal><rich:dataTable></literal> component as well as the <literal><h:dataTable></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dataTable></literal> component lets you use skins to change the look and feel of your data tables. You can see an example of the difference between these components at the <ulink url=\"http://livedemo.exadel.com/richfaces-art-datatable/\">RichFaces dataTable LiveDemo page</ulink>, or see the source code in the <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-art-datatable/\">SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I organize wizards with the <literal><rich:modalPanel></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place the <literal><a4j:include></literal> tag inside the <literal><rich:modalPanel></literal> and perform navigation inside it, as in the following example below:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I stop <literal>modalPanel</literal> closing when validation fails?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two methods available to fix this problem. The first is simply to remove the <literal>windowclose()</literal> method from the <literal>modalPanel</literal>, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that when an error presents, the panel will simply do nothing rather than closing the window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second method assumes that you use Facelets. Add the following to your <filename>default.xhtml</filename> template:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This invisible form will be refreshed on every postback, and contains a hidden field that determines the maximum severity in the message queue. If you add the following function to your JavaScript:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method reads the value of the hidden field to determine whether the last postback to the server generated any errors. This means that the <literal><a4j:commandLink></literal> or <literal><a4j:commandButton></literal> that submits your form will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method lets you easily adjust the behaviour of any JavaScript code depending on whether an error is present. See the <ulink url=\"http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4061517\">JBoss RichFaces forum</ulink> post for more information and variations on this method."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "When I use <literal>suggestionbox</literal> inside the <literal>modalPanel</literal>, the suggestion list sits behind the <literal>modalPanel</literal> and I cannot see it. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You are using an old version of RichFaces. Upgrade to the latest version to fix this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Does RichFaces work with Facelets?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes. Full Facelets support is one of RichFaces' primary features. The main <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\"> demo</ulink> is a Facelets-based application."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I create a dynamic menu with the <literal><rich:dropDownMenu></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:dropDownMenu></literal> is a standard JSF component, so creating a menu dynamically from the JavaScript code is the same as for any other JSF component."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I customize the look of a <literal>datascroller</literal> (the forward/back buttons) and replace them with images?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can. The <literal>datascroller</literal> component provides two controller groups for switching:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Page numbers</emphasis> so that you can switch to a particular page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Fast-switching</emphasis> controls: <literal>first</literal>, <literal>last</literal>, <literal>next</literal>, <literal>previous</literal>, <literal>fastforward</literal> and <literal>fastrewind</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create fast-switching controls by adding a <literal>facet</literal> component with the corresponding name:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also create disabled states with facets There are also facets used to create the disabled states: <literal>first_disabled</literal>, <literal>last_disabled</literal>, <literal>next_disabled</literal>, <literal>previous_disabled</literal>, <literal>fastforward_disabled</literal>, <literal>fastrewind_disabled</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I place simple links inside a menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include a link to an external URL, use the following approach:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see a demonstration of the <literal><rich:dropDownMenu></literal> component at the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/dropDownMenu.jsf\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal>dropDownMenu</literal> as a context menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dropDownMenu></literal> is not designed for use as a <literal>contextMenu</literal>. A <literal><rich:contextMenu></literal> component is planned for development, but is not scheduled for any currently planned version."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass my own parameters during a <literal>modalPanel</literal> opening or closing?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass your parameters during modalPanel opening or closing like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass any of your own parameters, except for the standard <literal>modalPanel</literal> parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I add a simple link to the tree node?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following simple code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Is it possible to place tabs upright in the <literal>tabPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, it is not. Try using the <literal>togglePanel</literal> instead; toggle controls can be placed anywhere in the layout."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use a <literal>commandButton</literal> within the <literal>modalPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two important rules to follow when using <literal>modalPanel</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if <literal>modalPanel</literal> has form elements (input or command elements), it must have its own form."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if the <literal>modalPanel</literal> contains a form, it must not be included in a higher-level form."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I define the currently selected tab?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I retrieve the current value from the <literal>inputNumberSlider</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can retrieve the value with the following approach:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How to apply skins to the standard input components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The answer could be found <ulink url=\"http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103494\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I remove the table border and styles from the <literal>datascroller</literal> and show only links?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To do this, you must redefine your rich* classes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I expand/collapse tree nodes from code?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/ExpandCollapseTreeNodes\">This Wiki article</ulink> has some useful information about expanding and collapsing tree nodes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the JavaScript API?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I load the Scriptaculous library?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To load the whole Scriptaculous library shipped with RichFaces, use the <literal><a4j:loadScript></literal> tag:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This command lets you load an integrated version of the library that includes all existing Scriptaculous files, <emphasis>except</emphasis> <filename>unittest.js</filename>. If you do not want to load the whole library, but wish to load a specific file (for example, <filename>effect.js</filename>), use the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you load the whole library, you do not need to load a particular file."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid the problem with text wrapping in <literal><rich:tab></literal> in Internet Explorer 7?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The problem lies with a tab height bug in IE7. (Tab height is correct in Firefox and in IE6.) To work around the bug, you can change the doctype declaration from:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see the <ulink url=\"http://jira.jboss.com/jira/browse/RF-1011\">JIRA Issue</ulink> for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the status of the <literal><rich:effect></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:effect></literal> has several callback methods such as <literal>beforeStart</literal> and <literal>afterFinish</literal>, which can be used to save the status. You can also see the <ulink url=\"http://wiki.github.com/madrobby/scriptaculous/core-effects\">Scriptaculous Core Effects</ulink> page for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I send an additional parameter to the server with <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This example code gives you one method:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the example, the <literal>onselect</literal> event sends the selected value to the server. You can pass additional fields of the selected object (which do not belong to the <literal>fetchvalue</literal> attribute) in the same way."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I set the border of <literal><rich:dataTable></literal> to 0px?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your CSS file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I dynamically create a <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is a working example:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What should I change on the server side?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The list of zones to be rerendered can be specified as an EL expression. The list of IDs is formed during the <literal>RENDER_RESPONSE</literal> <emphasis>beforePhase</emphasis>, so you can point the <literal>reRender</literal> to the <classname>Set</classname>, and fill it during a tracking request to form a list of areas which can be dynamically updated."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I check request conditions before sending a request?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To check the terms of sending a request on a client, add the <literal>onSubmit</literal> attribute to all components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this example, the <literal>doSomething()</literal> function is executed before the AJAX request, and if the function returns <literal>false</literal>, the request is not fired."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The behavior of our <literal>onsubmit</literal> attribute differs slightly from the standard <literal>onsubmit</literal>. Do not return <literal>true</literal> if you want to fire the request: <code><xxx><a4j:support event=\"onclick\" onsubmit=\"return true;\"></code> becomes <code><xxx onclick=\"return true;A4J.Submit(.... );\" ></code> and standard event processing is fired instead of the request. Only return <literal>false</literal> if your conditions were not completed, or set actions to be performed without any returned response if you do need to fire the request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What were the changes to the <varname>onComplete</varname> attribute after version 1.0?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To avoid conflict with other JavaScript attributes, we have changed the placement of a function during a Javascript call. Rather than inserting attribute contents (<code>oncomplete:anotherFunction(this)</code>), we make the function anonymous (<code>oncomplete:function(){anotherFunction(this);}</code>) so that you can insert a <emphasis>chain</emphasis> of statements into an attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The change also means that the <literal>this</literal> keyword will point to a parameter map instead of a control element. You can use <code>document.findElementById()</code> to retrieve references to this parameter map after a request is processed. Pages updated with AJAX will then reference a control removed from a DOM tree."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you are certain that your element will not be updated, you can add <literal>onsubmit</literal> to your <literal><a4j:support></literal> tag (or <literal>onclick</literal> to your <literal><a4j:commandLink/Button></literal> tag) to place a reference to a known variable, like so: <code><a4j:commandLink onclick=\"var myControl=this;\" oncomplete=\"anotherFunction(myControl)\"/></code>)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The onComplete syntax now follows this form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>event</literal> is a variable defining the location in which the JavaScript event that fires the request will be placed. <literal>data</literal> is a variable containing the deserialized value of the <varname>data</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use InvokeOnComponent with JSF 1.2?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not use <literal>invokeOnComponent</literal> for two reasons:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To retain compatibility with JSF 1.1 and MyFaces applications, since these are often used in corporate applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>invokeOnComponent</literal> works well when used to communicate between a Widget and a backed component, or to update the content of a rendered component. However, there are some limitations for more complicated use-cases implemented in RichFaces, such as making update decisions with application logic."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that you must update whole components (for example, an entire <literal>dataTable</literal>), but all AJAX core action components in that component will work correctly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid generating exceptions for the <literal><a4j:keepAlive></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember: the component stores beans in a serialized view. Your bean should implement <literal>java.io.Serializable</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "My form will not submit, or, my setter is not called after an AJAX request. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This can occur because of conversion or validation errors at submission time. To verify this, place the following update message inside a form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:message></literal> component has built-in AJAX support, and can be combined with the <ulink url=\"http://www.jsfone.com/blog/max_katz/2008/07/creating_jsf_phase_listener.html\">JSF Phase Tracker</ulink> to fix this issue, in some instances."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I create an <literal>a4j</literal> delayed render zone?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><a4j:support></literal> component has a <varname>requestDelay</varname> attribute, where you can define the delay period."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use IgnoreDupResponses and requestDelay?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>ignoreDupResponses</varname> ignores an AJAX request if a newer request exists. <varname>requestDelay</varname> defines the time delay on the client between compiling a request response and sending that response. You can find more information in <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use eventsQueue attribute?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>eventsQueue</literal> defines the name of the queue that will order upcoming AJAX requests. The queue makes certain that redundant requests are not sent. It is created and named by default. You can find more information in the section on <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use multiple <literal><a4j:status></literal> components on one page?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes, you can. You can find out more from the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/status.jsf?c=status\">JBoss RichFaces Online Demos</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal><a4j:region></literal> component inside the <literal><a4j:repeat></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, you cannot. The <literal><a4j:region></literal> component cannot work inside iteration components such as <literal><h:dataTable></literal> and <literal><a4j:repeat></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I disable skinnability?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You cannot disable skinnability, but you can use a special skin: <literal>plain</literal>. This skin has no parameters, and was created to enable you to embed RichFaces components into existing projects with their own predefined styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does my reRender fail when using hide/show components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Rerendering fails when RichFaces tries to update a component that is defined as hidden or rendered. When <literal>rendered=\"false\"</literal>, the component is not added to the DOM tree, so it cannot be updated (as per the limitations described in the AJAX Processing chapter)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The correct way to rerender a hidden or rendered component is to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Wrap the component that is to be hidden or rendered on AJAX in a wrapper component such as <literal><a4j:outputPanel></literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Set the <varname>reRender</varname> attribute on the wrapper component instead of on the component itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Fpr example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This ensures that the wrapper component presents in the DOM tree, which means that its contents can be updated dynamically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why am I seeing a <exceptionname>ResourceNotRegistered</exceptionname> Exception?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces registers its resources (for example, scripts and images) after an application is accessed, and then accesses these via a generated URL. During application development, when an application is constantly updated on the server, RichFaces may re-register its resources after every server restart, while the browser may attempt to access resources via a cached URL."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve this problem by updating the browser cache: press <keycap>CTRL</keycap>+<keycap>F5</keycap>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I reRender only a particular row(s) of a table?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>ajaxKeys</literal> attribute defines Strings that are updated after an AJAX request, and lets you update several child components separately without updating the whole page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable row selection in a scrollableDataTable using <literal>one and multi-selection rows mode</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable row selection in <literal>one and multi-selection rows mode</literal>, you must use the <varname>selection</varname> attribute. In the example code that follows, when a user submits the form, the current collection of objects selected by the user is placed in the object's property. Upon completion, the <literal><rich:modalPanel></literal> will be rendered with the selected data."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, you can create a managed bean like the one below. The <literal>takeSelection()</literal> method fills the <literal>selectedCars</literal> Array with data retrieved from the <varname>selection</varname>. The <literal>getSelectedCars()</literal> method returns <literal>selectedCars</literal> Array, which is then used to populate select rows of the <literal><rich:dataTable></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I select several rows in a <literal>scrollableDataTable</literal> and drag-and-drop them into a <literal>dataTable</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, to enable row selection, see the previous section on <xref linkend=\"RowSelectionInScrollableDataTable\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable the drag-and-drop function on a <literal>dataTable</literal>, use the <literal><rich:dragSupport></literal> and <literal><rich:dropSupport></literal> components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous example is also available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/scrollableDataTable.jsf\">RichFaces LiveDemo</ulink> site. Only one method is added where the dropped collection is stored:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of the <rich:simpleTogglePanel>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>opened</varname> attribute responsible for storing panel state, and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:simpleTogglePanel></literal> icon appears and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered between page views."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, create a managed bean like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of <rich:panelMenuGroup>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>expanded</varname> attribute and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:panelMenuGroup></literal> expands and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered across page views."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I highlight the rows of a dataTable on the mouseover event?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <literal>onRowMouseOver</literal> and <literal>onRowMouseOut</literal> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable selecting the row of a <literal><rich:dataTable></literal> when I click on it, even if I click within the bounds of an <literal><h:inputText></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following JavaScript function to enable row selection when you click on the row:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can then use <literal><a4j:support></literal> with <varname>event</varname> and <varname>onsubmit</varname> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I rerender table cells with <a4j:support>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To rerender table cells with <literal><a4j:support></literal>, set exact ID values for each component to be updated, and point this <varname>id</varname> to the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The value of the <varname>reRender</varname> attribute belonging to the <literal> <a4j:support></literal> tag defines the sections of the page that will be updated. In the previous example code, the only update made is to the <literal><h:outputText></literal> component in the footer, because its <literal>id</literal> value matches the value of the <varname>reRender</varname> attribute. You can update multiple elements on a page by listing their IDs as the value of the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I create dynamic columns?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create dynamic columns by using the <literal><rich:column></literal> with the <varname>rendered</varname> attribute. Set the value of the <varname>rendered</varname> attribute to match the ID of the dynamic cell, as in the following example code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you could create a managed bean, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use RichFaces with Trinidad?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of a basic <filename>web.xml</filename> file that integrates RichFaces with Trinidad."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why do I see a JavaScript conflict?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Richfaces 3.1.3 uses version 1.6.0 of the <filename> prototype.js</filename> instead of version 1.5.1, which has been used in earlier versions. The source of the conflict is that two versions of the prototype script are included. The first is included as a dependency of the toggle panel components, and the second is included explicitly as a link."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces 3.1.3 is bundled with the same scripts included in Prototype 1.6.0 and Scriptaculous 1.8.0:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Using Prototype with RichFaces components can be problematic because issues that were fixed in version 1.6.0 were not always patched in version 1.5.1. When version 1.5.1 is used, some RichFaces components will not work as expected."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with the Seam Framework?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To use the <literal><rich:fileUpload></literal> component with the Seam Framework, define initialization parameters for the Seam Filter in your <filename>web.xml</filename> file. The Seam Framework will then automatically set the component up for the AJAX4JSF filter at start-up time."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of defining initialization parameters:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with MyFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The order in which filters are defined and mapped in <filename>web.xml</filename> is important to integrating the <literal><rich:fileUpload></literal> component with MyFaces. The code sample that follows shows the correct order in which to define your filters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To ensure that this sequence wors correctly, map the extension filter on your Faces Servlet, not to <filename>*.jsf</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable optional object selection in <rich:suggestionbox>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:suggestionBox></literal> component provides features such as object selection. To store the selected items as objects to be accessed, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the <varname>usingSuggestObjects</varname> attribute to the <literal><rich:suggestionBox></literal> component, and define it as <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <varname>onobjectchange</varname> event attribute to store the currently-selected objects."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All of the selected objects are stored in the <literal>suggestion.SelectedItems</literal> Array. Each Array element contains <literal>text</literal> and <literal>object</literal> properties, so you can iterate this Array, retrieve objects that are not <literal>null</literal>, and retrieve the required property."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for ViewExpiredException?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This exception appears after your session has timed out. Because RichFaces 3.1 is intended for use with JavaServer Faces 1.1, <exceptionname>ViewExpiredException</exceptionname>s will not generate automatically when RichFaces is used with JavaServer Faces 1.2. To work around this limitation, add the following to your <filename>web.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for Request Errors and Session Expiration?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To redefine the standard handlers that are responsible for processing different exceptional situations, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add custom <literal>onError</literal> and <literal>onExpire</literal> handlers, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more detailed description of this process, see <xref linkend=\"RequestErrorsAndSessionExpirationHandling\" /> in the Developer Guide."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Custom <literal>onError</literal> and <literal>onExpire</literal> handlers will not work under MyFaces, because MyFaces handles exceptions with an internally-generated debug page. To prevent this behavior, use the following code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I add a cookie in an AJAX response?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The bean described below adds a cookie to an AJAX response:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you can define the cookie to be included as shown in the following example. After the <literal>test</literal> cookie is set, the value of that cookie will appear on a page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is new in AJAX4JSF 3.2.x?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces 3.2.x releases have some new features:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><a4j:portlet</literal> component has been <emphasis>deprecated</emphasis>, since JSR-301 defines a similar function for <literal>UIViewRoot</literal> components;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><rich:ajaxValidator></literal>, <literal><rich:beanValidator></literal> and <literal><rich:graphValidator></literal> validators have been added to provide different validation types."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I launch the RichFaces sample on the JBoss server?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To launch the RichFaces sample application on the JBoss server, add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass a Boolean value in the <rich:componentControl> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code shows you how to avoid requiring a Boolean value:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use <code>'block'</code> instead of <code>' '</code> to avoid <literal>invalid style</literal> CSS errors."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/Getting_Started.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/Getting_Started.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,159 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Started with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This chapter tells you how to plug RichFaces components into a JSF application. The instructions are based on a simple <emphasis>JSF with RichFaces</emphasis> creation process, from downloading the required libraries to running the application in a browser. These instructions do not depend on the integrated development environment that is in use."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Simple JSF application with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> — the simple application — is similar to a typical <emphasis>hello world</emphasis> application, with one exception: the world of RichFaces will say \"Hello!\" to the user first."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a standard JSF 1.2 project named <literal>Greeter</literal>. Include all required libraries, and continue with the instructions that follow."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Adding RichFaces libraries into the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "From the <filename>RichFaces</filename> folder where you unzipped the RichFaces binary files, open the <filename>lib</filename>. This folder contains three <filename>*.jar</filename> files with API, UI, and implementation libraries. Copy these JARs from <filename>lib</filename> to the <filename>WEB-INF/lib</filename> directory of your <application>Greeter</application> JSF application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A JSF application with RichFaces assumes that the following JARs are available in the project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-beanutils-1.7.0.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-collections-3.2.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-digester-1.8.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-logging-1.0.4.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jhighlight-1.0.jar</filename>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering RichFaces in <filename>web.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "After you add the RichFaces libraries to the project, you must register them in the project <filename>web.xml</filename> file. Add the following to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For more information about RichFaces skins, read <xref linkend=\"Skinnability\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, your <filename>web.xml</filename> should look like this:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Managed bean"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <application>RichFaces Greeter</application> application needs a managed bean. In the project's <filename>JavaSource</filename> directory, create a new managed bean named <literal>user</literal> in the <literal>demo</literal> package. Place the following code in <filename>user</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering the bean in <filename>faces-cofig.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To register the <literal>user</literal> bean, add the following to the <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Greeter index.jsp"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> has only one JSP page. Create <filename>index.jsp</filename> in the root of <literal>WEB CONTENT</literal> folder and add the following to the JSP file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The application uses three RichFaces components: <emphasis role=\"bold\"><property><rich:panel></property></emphasis> is used as visual container for information; <emphasis role=\"bold\"><property><a4j:commandButton></property></emphasis> with built-in AJAX support lets a greeting be rendered dynamically after a response returns; and <emphasis role=\"bold\"><property><a4j:form></property></emphasis> helps the button to perform the action."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces tag library should be declared on each JSP page. For XHTML pages, add the following lines to declare your tag libraries:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Now, run the application on the server by pointing your browser to the <filename>index.jsp</filename> page: <literal>http://localhost:8080/Greeter/index.jsf</literal>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "\"RichFaces Greeter\" application"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Relevant Resources Links"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"https://www.redhat.com/apps/store/developers/jboss_developer_studio.html\">JBoss Developer Studio</ulink> includes tight integration with the RichFaces component framework. <!-- The following links might be useful for those who already use this IDE and RichFaces to develop applications, and for those who wish to improve their development process. -->"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/IDE_Support.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/IDE_Support.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/IDE_Support.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Integrated Development Environment Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is supported by both <ulink url=\"http://www.redhat.com/developers/rhds/index.html\">JBoss Developer Studio 1.0.0 GA</ulink> and <ulink url=\"http://www.jboss.org/tools/index.html\">Jboss Tools</ulink>. JBoss Developer Studio is a fully packaged Integrated Development Environment (IDE) that provides full support for Java Server Faces, RichFaces, Facelets, Struts and other Web technologies. It seamlessly combines visual and source-oriented development approaches. You can add JBoss Developer Studio capabilities to any JSF project by adding the appropriate libraries and modifying configuration files as required."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/Introduction.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/Introduction.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/Introduction.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,79 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is an open source framework that adds AJAX capability into existing JSF applications without resorting to JavaScript."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces leverages aspects of the JavaServer Faces (JSF) framework, including lifecycle, validation, conversion facilities, and management of static and dynamic resources. RichFaces components with built-in AJAX support and a highly customizable look-and-feel can be easily incorporated into JSF applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces allows you to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Experience the benefits of JSF while working with AJAX. RichFaces is fully integrated into the JSF lifecycle. Where other frameworks only allow access to the managed bean facility, RichFaces lets you access the action and value change listeners, and invokes server-side validators and converters during the AJAX request-response cycle."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add AJAX capabilities to existing JSF applications. The RichFaces framework provides two component libraries (Core AJAX and UI). The Core library adds AJAX functionality to existing pages, so you need not write any JavaScript or replace existing components with new AJAX components manually. RichFaces enables page-wide rather than component-wide AJAX support, giving you the opportunity to define events on the page. <!-- An event invokes an AJAX request and areas of the page which become synchronized with the JSF Component Tree after changing the data on the server by AJAX request in accordance with events fired on the client. -->"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily create different views with a variety of components, available out-of-the-box. The RichFaces UI library contains components for adding rich user interface (UI) features to JSF applications, providing you with a broad variety of AJAX-enabled components with extensive skins support. RichFaces components are designed to integrate seamlessly with other third-party component libraries, so you have more options when you develop applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Write your own rich components with built-in AJAX support. The Component Development Kit (CDK) is constantly being expanded. It includes both code generation and templating facilities and a simple JSP-like (JavaServer Pages) syntax, letting you create first-class rich components with built-in AJAX functionality."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Package resources with application Java classes. RichFaces provides advanced support for managing different resource types, including images, JavaScript code, and CSS stylesheets. The resource framework makes it easier to include these resources in JAR files with your custom component code."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily generate binary resources. The resource framework can generate images, sounds, Excel spreadsheets, etc. in real time, so you can, for example, create images with the Java Graphics 2D library and other similar resources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customize the look and feel of your user interface with skins-based technology. RichFaces lets you easily define and manage different color schemes and other user interface parameters by using named <emphasis>skin parameters</emphasis>. This means you can access UI parameters from JSP and Java code to adjust your UI in real time. RichFaces includes a number of predefined skins to kick-start your application's development, but it is easy to create your own custom skins."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Simultaneously create and test your components, actions, listeners, and pages. RichFaces will soon include an automated testing facility to generate test cases for your component as you develop it. The testing framework tests not only the components, but also any other server-side or client-side functionality, including JavaScript code — and it will do so <emphasis>without</emphasis> deploying the test application into the Servlet container."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces UI components can be implemented immediately, right out of the box. This saves development time and gives you immediate access to RichFaces web application development features, so experience with RichFaces is fast and easy to obtain."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/Links_to_Resources.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/Links_to_Resources.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/Links_to_Resources.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,74 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Links to information resources"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Links"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/portal/jbossrichfaces/\">JBoss RichFaces</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss Forum"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://jboss.com/index.html?module=bb&op=main&c=27\">JBoss Forums</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Wiki"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/wiki/RichFaces\">RichFaces Wiki</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Blog"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "<ulink url=\"http://jroller.com/page/a4j\">RichFaces Blog</ulink>"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/Revision_History.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/Revision_History.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/Revision_History.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: member
+#, no-c-format
+msgid "JIRA corrections."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/RichFaces_Developer_Guide.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/RichFaces_Developer_Guide.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/RichFaces_Developer_Guide.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/Settings.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/Settings.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/Settings.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,334 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Settings for different environments"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces includes support for all tags (components) included in the JavaServer Faces (JSF) specification. To add RichFaces capabilities to an existing JSF project, place the RichFaces libraries into the <filename>lib</filename> directory of the project, and add filter mapping. The behavior of the existing project does not change when you add RichFaces."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Application Descriptor Parameters"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not require that any parameters be defined in your <filename>web.xml</filename>, but the RichFaces parameters listed below will help you during the development process and increase the flexibility of your RichFaces applications."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.SKIN"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The name of a skin that is used in an application. Can be a literal string with a skin name or the EL expression (<literal>#{...}</literal>) associated with a String property (skin name) of a property of a <literal>org.richfaces.framework.skin</literal> type. In the latter case, that instance is used as the current skin."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadScriptStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces script files are loaded to the application. Possible values are <literal>ALL</literal>, <literal>DEFAULT</literal> and <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadStyleStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces style files are loaded into the application. Possible values are: <literal>ALL</literal>, <literal>DEFAULT</literal>, or <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.LOGFILE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "none"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The URL of an application or a container log file (if applicable). If this parameter is set, content from the given URL is shown on a Debug page in the <literal>iframe</literal> window."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.VIEW_HANDLERS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of <literal>ViewHandler</literal> instances for inserting in a view handler chain. These handlers are inserted before the RichFaces viewhandlers, in the order they are listed. In a Facelets application, you would declare <literal>com.sun.facelets.FaceletViewHandler</literal> here instead of in the <filename>faces-config.xml</filename> file."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.CONTROL_COMPONENTS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of special <emphasis>control case</emphasis> components, such as the messages bundle loader or an alias bean component. These handlers are provided via a reflection from the static field <literal>COMPONENT_TYPE</literal>. Encoding methods for these components are always called while rendering AJAX responses, even if a component has not been updated."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_RESOURCE_DATA"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "false"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "For generated resources (such as encrypt generation data), this is encoded in the resource URL. For example, the URL of an image generated by the <classname>mediaOutput</classname> component contains the name of a generation method. Since malicious code can exploit this to create a request for any JSF bean or attribute, this parameter should be set to <literal>true</literal> in critical applications. (This fix works with Java Runtime Environment 1.4.)"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_PASSWORD"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "random"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A password used to encrypt resource data. If this is not set, a random password is used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.COMPRESS_SCRIPT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "true"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "When defined, does not allow the frameword to reformat JavaScript files. This means that the debug feature cannot be used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URLs of all generated resources. This is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.GLOBAL_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/g"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URI of all global resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SESSION_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/s"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be used to track the sessions of generated resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.DEFAULT_EXPIRE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "86400"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the period (in seconds) for which resources are cached when they are streamed back to the browser."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SERIALIZE_SERVER_STATE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "If set to <literal>true</literal>, the component state (not the tree) will be serialized before it is stored in the session. This can be useful in applications with view state that is sensitive to model changes. Alternatively, use <literal>com.sun.faces.serializeServerState</literal> and <literal> org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</literal> parameters in their respective environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>org.richfaces.SKIN</literal> is used in the same way as <literal>org.ajax4jsf.SKIN</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "org.ajax4jsf.Filter Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "log4j-init-file"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "-"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A path (relative to the web application's context) to the <filename>log4j.xml</filename> configuration file. This can be used to set up per-application custom logging."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "enable-cache"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Enables caching of framework-generated resources (JavaScript, CSS, images, etc.). However, your cached resources will not be used when attempting to debug custom JavaScript or Styles."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "forcenotrf"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Forces all JSF pages to be parsed by a HTML syntax check filter. If set to <literal>false</literal>, only AJAX responses will be parsed and converted to well-formed XML. Setting this to <literal>false</literal> can improve performance, but may also cause unexpected information to be rendered during AJAX updates."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Sun JSF RI"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces works with JavaServer Faces 1.2_13 without needing to modify additional settings."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Facelets Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces has high-level support for Facelets, regardless of the version used. However, some JSF frameworks (including Faces) require that their own <literal>ViewHandler</literal> be listed first in the <literal>ViewHandler</literal> chain. RichFaces also requires that its <literal>AjaxViewHandler</literal> be listed first, but because it is installed first, no settings will need to be altered. Where multiple frameworks are used without RichFaces, you can use the <literal>VIEW_HANDLERS</literal> parameter to define the order in which the <literal>ViewHandler</literal>s are used. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This declares that while <literal>Facelets</literal> will officially be first, <literal>AjaxViewHandler</literal> will briefly be ahead of it to perform some small, important task."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this case, you need not define <literal>FaceletViewHandler</literal> in <filename>WEB-INF/faces-config.xml</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JBoss Seam Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is compatible with <application>JBoss Seam</application> and Facelets when run within JBoss Enterprise Application Server. No additional JARs are required. All you need to do is package the RichFaces library with your application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For <application>Seam 1.2</application>, your <filename>web.xml</filename> must be as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>Seam 2.x</application> supports RichFaces Filter, so your <filename>web.xml</filename> must look like this:"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/pt-BR/Technical_Requirements.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/pt-BR/Technical_Requirements.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/pt-BR/Technical_Requirements.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,179 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Technical Requirements"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces</application> was developed with an open architecture to ensure that it was compatible with the widest possible variety of environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This is what you need to start working with <application>RichFaces 3.3.1</application>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JavaServer Faces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java Application Server <emphasis>or</emphasis> Servlet Container"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Browser (on client side)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Java Versions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JDK 1.5 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported JavaServer Faces Implementations and Frameworks"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun JSF-RI - 1.2_12"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "MyFaces 1.2.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Facelets 1.1.1 - 1.2"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Seam 1.2. - 2.1.0"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Servers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Apache Tomcat 5.5 - 6.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "BEA WebLogic 9.1 - 10.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Resin 3.1"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Jetty 6.1.x"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun Application Server 9 (J2EE 1.5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "GlassFish (J2EE 5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JBoss 4.2.x - 5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Websphere 7.0. and higher"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Geronimo 2.0 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Browsers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6.0 - 8.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Firefox 2.0 - 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera 8.5 - 9.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Google Chrome"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This list is composed from user reports of compatibility. We assume that this list is incomplete, so the absence of your environment from the list does not necessarily mean that it is incompatible with RichFaces."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "We appreciate your feedback about compatible platforms and browsers that are not listed here. This helps us keep the list up-to-date."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/Architecture_Overview.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/Architecture_Overview.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/Architecture_Overview.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,1829 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Basic concepts of the RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces Framework is implemented as a component library that adds AJAX capabilities into existing pages. This means that you do not need to write any JavaScript code or replace existing components with new AJAX widgets. RichFaces enables page-wide AJAX support instead of the traditional component-wide support, so you can define areas of the page that will reflect changes made by AJAX events on the client."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram following shows the process in full:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Processing flow"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you use JSF tags to define sections of a JSF page that you wish to update with the results of an AJAX request. It also provides you with several options for sending AJAX requests to the server. You do not need to write any JavaScript or <literal>XMLHTTPRequest</literal> objects by hand — everything is done automatically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Architecture Overview"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following figure lists several important elements of the RichFaces Framework."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Core AJAX component structure"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Filter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To make the most of RichFaces, you should register a <literal>Filter</literal> in your application's <filename>web.xml</filename>. The <literal>Filter</literal> recognizes multiple request types. The sequence diagram in Figure 5.3 shows the differences in processing between a <emphasis>regular</emphasis> JSF request and an AJAX request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request processing sequence diagram"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In either case, the required static or dynamic resource information that your application requests is registered in the <literal>ResourceBuilder</literal> class."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When a resource request is issued, the RichFaces filter checks the <literal>Resource Cache</literal> for this resource. If it is present, the resource is returned to the client. Otherwise, the filter searches for the resource among those registered in the <literal>ResourceBuilder</literal>. If the resource is registered, the RichFaces filter requests that the <literal>ResourceBuilder</literal> creates (delivers) the resource."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The diagram that follows illustrates the process of requesting a resource."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Resource request sequence diagram"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Action Components"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "AJAX Action components are used to send AJAX requests from the client side. There are a number of AJAX Action components, including <literal><a4j:commandButton></literal>, <literal><a4j:commandLink></literal>, <literal><a4j:poll></literal>, and <literal><a4j:support></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "AJAX Containers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>AjaxContainer</literal> is an interface that defines an area on your JSF page that should be decoded during an AJAX request. <literal>AjaxViewRoot</literal> and <literal>AjaxRegion</literal> are both implementations of this interface."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JavaScript Engine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces JavaScript Engine runs on the client side, and updates different areas of your JSF page based on information from the AJAX response. This JavaScript code operates automatically, so there is no need to use it directly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors and Session Expiration Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you redefine the standard handlers responsible for processing exceptions. We recommend defining your own JavaScript, which will be executed when exceptional situations occur."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Request Errors Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To execute your own code on the client in the event of an error during an AJAX request, you must redefine the standard <literal>A4J.AJAX.onError</literal> method like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function accepts the following as parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>req</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a parameter string of a request that calls an error"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>status</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the number of an error returned by the server"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>message</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for the given error"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, you can create your own handler that is called when timeouts, internal server errors, etc. occur."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Session Expired Handling"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also redefine the <literal>onExpired</literal> framework method that is called on the <literal>SessionExpiration</literal> event."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Example:</emphasis>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This function can take the following parameters:"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>loc</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the URL of the current page (can be updated on demand)"
+msgstr ""
+
+#. Tag: term
+#, no-c-format
+msgid "<literal>expiredMsg</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a default message for display in the event of <literal>SessionExpiration</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customized <literal>onExpire</literal> handlers do not work under MyFaces. MyFaces handles exceptions by internally generating a debug page. To prevent this behavior, use the following:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skinnability"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you look at any CSS (Cascading Style Sheets) file in an enterprise application, you will notice how often the same color is noted. Standard CSS cannot define a particular colour abstractly as a panel header color, the background color of an active pop-up menu item, a separator color, etc. To define common interface styles, you must copy the same value multiple times, and the more interfaces you have, the more repetition is required."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Therefore, if you want to change the palette of an application, you must change all interrelating values, or your interface can appear clumsy. If a customer wants to be able to adjust their interface's look and feel in real time, you must be able to alter several CSS files, each of which will contain the same value multiple times."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve these problems with the <emphasis>skins</emphasis> that are built into and rully implemented in RichFaces. Every named skin has <emphasis>skin parameters</emphasis> that define a palette and other attributes of the user interface. By changing a few skin parameters, you can alter the appearance of dozens of components simultaneously, without interfering with interface consistency."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinnability</literal> feature cannot completely replace standard CSS, and does not eliminate its usage. Instead, it is a high-level extension of standard CSS that can be used in combination with regular CSS declarations. You can also refer to skin parameters in CSS through the JSF Expression Language. This lets you completely synchronize the appearance of all elements in your pages."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Using Skinnability"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces <emphasis>skinnability</emphasis> is designed for use alongside:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "skin parameters defined in the RichFaces framework,"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "predefined CSS classes for components, and"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "user style classes."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A component's color scheme can be applied to its elements using any of three style classes:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A default style class inserted into the framework"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This contains stle parameters that are linked to some constants from a skin. It is defined for every component and specifies a default level of representation. You can modify an application interface by changing the values of the skin parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "A style class of skin extension"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This class name is defined for every component element, and inserted into the framework to let you define a class with the same name in your CSS files. This lets you easily extend the appearance of all components that use this class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "User style class"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use one of the <literal>styleClass</literal> parameters to define your own class for component elements. As a result, the appearance of one particular component is changed according to a CSS style parameter specified in the class."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Example"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following is an example of a simple <emphasis>panel</emphasis> component:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This code generates a panel component on a page, which consists of two elements: a wrapper <literal><div></literal> element and a <literal><div></literal> element for the panel body with the specified style properties. The wrapper <literal><div></literal> element will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>dr-pnl</literal> is a CSS class that is specified in the framework via skin parameters:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>background-color</varname> is defined with <literal>generalBackgroundColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>border-color</varname> is defined with <literal>panelBorderColor</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change all colors for all panels on all pages by changing these skin parameter values. However, if you specify a <literal><rich:panel></literal> class on the page, its parameters are also acquired by all panels on this page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Developers can also change the style properties for panel. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous definition could add some style properties from <literal>customClass</literal> to one particular panel. As a result, we will get three styles:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Skin Parameters Tables in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces provides eight predefined skin parameters (skins) at the simplest level of common customization:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "plain"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "emeraldTown"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "blueSky"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "wine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "japanCherry"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ruby"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "classic"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "deepMarine"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To apply a skin, you must specify a skin name in the <varname>org.richfaces.SKIN</varname> context parameter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following table shows the values for each parameter in the <literal>blueSky</literal> skin:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Colors"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Parameter name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#BED6F8"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerGradientColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#F2F7FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#000000"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerWeightFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bold"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FFFFFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "11px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Arial, Verdana, sans-serif"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "controlBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "additionalBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#ECF4FE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "shadowOpacity"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "panelBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "subBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C6DEFF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabDisabledTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#8DB7F3"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "trimColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#D6E6FB"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#FAE6B0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tipBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E5973E"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "selectControlColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#E79A00"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "generalLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0078D0"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#0090FF"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "visitedLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Fonts"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tabFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonSizeFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "buttonFamilyFont"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableFooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#cccccc"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableSubfooterBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#f1f1f1"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "tableBorderColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "#C0C0C0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>plain</literal> skin was added in version 3.0.2. It has no parameters, and is important when embedding RichFaces components into existing projects with their own styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Creating and Using Your Own Skin File"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To create your own skin file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a file. In it, define skin constants to be used by style classes (see <xref linkend=\"SkinParametersTablesInRichFaces\" />). The name of the skin file should follow this format: <literal><name>.skin.properties</literal>. (For examples of this file, see the RichFaces predefined skin parameters: <literal>blueSky</literal>, <literal>classic</literal>, <literal>deepMarine</literal>, etc. These files are located in the <filename>richfaces-impl-xxxxx.jar</filename> archive in the <filename>/META-INF/skins</filename> folder."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the skin definition <literal><contex-param></literal> to the <filename>web.xml</filename> of your application, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place your <literal><name>.skin.properties</literal> file in either your <filename>/META-INF/skins</filename> or <filename>/WEB-INF/classes</filename> directory."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Built-in Skinnability in RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces lets you incorporate skins into your user interface (UI) design. This framework lets you use named skin parameters in your properties files to control skin appearance consistently across a set of components. You can see examples of predefined skins at: <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">http://livedemo.exadel.com/richfaces-demo/ </ulink>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Skins let you define a style in which to render standard JSF components and custom JSF components built with RichFaces. You can experiment with skins by following these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a custom render kit and register it in the <filename>faces-config.xml</filename> like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, create and register custom renderers for the component based on the look-and-feel predefined variables:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, place a properties file with skin parameters into the class path root. There are two requirements for the properties file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The file must be named <filename><replaceable>skinName</replaceable>.skin.properties</filename>. In this case, we would call it <literal>newskin.skin.properties</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The first line in this file should be <literal>render.kit=<replaceable>render-kit-id</replaceable></literal>. In this case, we would use <literal>render.kit=NEW_SKIN</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "More information about creating custom renderers can be found at: <ulink url=\"http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html\">http://java.sun.com/javaee/javaserverfaces/reference/docs/index.html</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Changing skin in runtime"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can change skins during runtime by defining the following EL-expression in your <filename>web.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>skinBean</literal> code looks like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also set the <varname>skin</varname> property's initial value in the configuration file. To set <literal>classic</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also change the properties of the default skin. To do so, edit the properties of the default skin. The following shows you example page code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The above code will generate the following list of options:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Controls Skinning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This feature is designed to unify the look and feel of standard HTML elements and RichFaces components. Skinning can be applied to all controls on a page based on element names and attribute types (where applicable). This feature also provides a set of CSS styles that let skins be applied by assigning <literal>rich-*</literal> classes to particular elements, or to a container of elements that nests controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard Controls Skinning provides two levels of skinning: <emphasis>Basic</emphasis> and <emphasis>Extended</emphasis>. The level used depends on the browser type detected. If the browser type cannot be detected, <literal>Extended</literal> is used. However, if you want to explicitly specify the level to be applied, add a <varname></varname> context parameter to your <filename>web.xml</filename> and set the value to either <literal>basic</literal> or <literal>extended</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Basic</emphasis> level provides customization for only basic style properties. Basic skinning is applied to the following browsers:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in BackCompat mode (see <ulink url=\"http://msdn2.microsoft.com/en-us/library/ms533687(VS.85).aspx\">document.compatMode property in MSDN</ulink>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <emphasis>Extended</emphasis> level introduces a broader number of style properties on top of basic skinning, and is applied to browsers with rich visual styling control capabilities. The following browsers support Extended skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Mozilla Firefox"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 7 in Standards-compliant mode (CSS1Compat mode)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following elements can be modified with skins:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>input</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>select</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>textarea</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>keygen</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>isindex</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>legend</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>fieldset</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>hr</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>a</literal> (together with the <literal>a:hover</literal>, <literal>a:visited</literal> pseudo-elements)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two ways to initialize skinning for standard HTML controls:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. This method implies that skinning style properties are applied per-element and attribute type (where applicable). No additional steps are required. See the <xref linkend=\"BasicLevel\" /> and <xref linkend=\"ExtendedLevel\" /> tables for elements to which skinning can be applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "add the <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> parameter to <filename>web.xml</filename>. <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> takes <literal>enable</literal> and <literal>disable</literal> as parameters. When enabled, you are provided with a set of predefined CSS classes to apply skins to your HTML components."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enabling <varname>org.richfaces.CONTROL_SKINNING_CLASSES</varname> provides you style classes that can be applied to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "basic elements nested within elements with a <emphasis>rich-container</emphasis> class. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements with a class name that corresponds to one of the basic element names or types are mapped with the <literal>rich-<elementName>[-<elementType>]</literal> scheme, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Elements are given classes depending upon their <literal>link</literal> type and pseudo-class name, for example, <literal>rich-link</literal>, <literal>rich-link-hover</literal>, <literal>rich-link-visited</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The predefined rich CSS classes provided can be used as classes for both basic and complex HTML elements."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code snippet shows several elements as an example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more thorough look at standard component skinning, we recommend exploring the CSS files located in the <filename>ui/core/src/main/resources/org/richfaces/</filename> directory of the RichFaces SVN repository."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard Level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex and legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "CSS Properties"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-size"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-family"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-color"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for hr"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:hover"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "hoverLinkColorgeneralLinkColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for a:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Elements Skin Bindings for .rich-input, .rich-select, .rich-textarea, .rich-keygen, .rich-isindex, .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-fieldset"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-hr"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-width"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "border-style"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "solid"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:hover"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-link:visited"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Skin parameters/Value"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "inset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-color"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "no-repeat"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-position"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "1px 1px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-edit"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "editBackgroundColor"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-field-error"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "warningBackgroundColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding-left"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "7px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button, .rich-button-disabled, .rich-button-over"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "padding"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "2px 10px 2px 10px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "text-align"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "center"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "cursor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "pointer"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "repeat-x"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "top left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-button-press"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "bottom left"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-container fieldset, .rich-fieldset"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "10px"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-legend"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "font-weight"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Rich Element Skin Bindings for .rich-form"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "0px"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "margin"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Extended level"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "headerTextColor"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "background-image"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for button[type=button], button[type=reset], button[type=submit], input[type=reset], input[type=submit], input[type=button]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|button[disabled], .rich-container *|button[disabled], .rich-button-disabled"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.ButtonDisabledBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for .rich-button-disabled, .rich-container button[type=\"button\"][disabled], .rich-button-button-disabled, .rich-container button[type=\"reset\"][disabled], .rich-button-reset-disabled, .rich-container button[type=\"submit\"][disabled], .rich-button-submit-disabled, .rich-container input[type=\"reset\"][disabled], .rich-input-reset-disabled, .rich-container input[type=\"submit\"][disabled], .rich-input-submit-disabled, .rich-container input[type=\"button\"][disabled], .rich-input-button-disabled"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *button[type=\"button\"][disabled], button[type=\"reset\"][disabled], button[type=\"submit\"][disabled], input[type=\"reset\"][disabled], input[type=\"submit\"][disabled], input[type=\"button\"][disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.renderkit.html.images.InputBackgroundImage"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for textarea[type=textarea], input[type=text], input[type=password], select"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "HTML Element Skin Bindings for *|textarea[disabled], .rich-container *|textarea[disabled]"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "textarea[type=\"textarea\"][disabled], input[type=\"text\"][disabled], input[type=\"password\"][disabled]"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The basic skinning level can fail if the <literal>ajaxPortlet</literal> is configured as follows:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Client-side Script for Extended Skinning Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Extended skinning of standard HTML controls is applied automatically: the browser type is detected, and if a browser does not fully support extended skinning, only basic skinning is applied."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are some problems with standard HTML controls in certain browsers (Opera and Safari) that may cause problems if you wish to skin your RichFaces components and standard HTML controls manually."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable skinnability, set the <varname>org.richfaces.LoadStyleStrategy</varname> parameter to <literal>NONE</literal> in your <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You should also include the style sheets that apply skins to RichFaces components and standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To work around the problem of extended skinning in Opera and Safari, the <filename>skinning.js</filename> client script is added to the RichFaces library. This detects the browser type and enables extended skinning only for browsers that fully support it."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Activate the script by inserting the following JavaScript into your page:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When no script-loading strategy is used and extended skinning is enabled, a warning message appears in the console."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You must also specify the <varname>media</varname> attribute in the <literal>link</literal> tag. This adds the <filename>extended_both.xcss</filename> style sheet to <literal>rich-extended-skinning</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include your style sheets to the page when automatic skinnability is disabled, add the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Base64 encoder now uses <literal>!</literal> instead of <literal>.</literal>, so remember to use the <literal>a4j/versionXXX</literal> resources prefix instead of <literal>a4j_versionXXX</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "XCSS File Format"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Cross-site Cascading Style Sheet (XCSS) files are the core of RichFaces component skinnability. XCSS is XML-formatted CSS that extends the skinning process. RichFaces parses the XCSS file containing all look and feel parameters of a particular component and compiles the information into a standard CSS file that can be recognized by a web browser."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The XCSS file contains CSS properties and skin parameter mappings. Mapping a CSS selector to a skin parameter can be done with <literal>< u:selector ></literal> and <literal>< u:style></literal> XML tags, which define the mapping structure, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "During processing, this code will be parsed and assembled into a standard CSS format, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>name</varname> attribute of <literal><u:selector></literal> defines the CSS selector, while the <varname>name</varname> attribute of the <literal><u:style></literal> tag defines the skin constant that is mapped to a CSS property. You can also use the <varname>value</varname> attribute of the <literal><u:style></literal> tag to assign a value to a CSS property."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "CSS selectors with identical skin properties can be included in a comma-separated list:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Plug-n-Skin</emphasis> lets you easily create, customize, and plug in a custom skin to your project. You can create skins based on the parameters of predefined RichFaces skins. Plug-n-Skin also lets you unify the appearance of rich controls with standard HTML elements. This section contains step-by-step instructions for creating your own skin with Plug-n-Skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, use Maven to create a template for your new skin. (You can find more information about configuring Maven for RichFaces in the <!-- #modify add info? --><ulink url=\"http://wiki.jboss.org/wiki/HowToConfigureMavenForRichFaces\">JBoss wiki article</ulink>. These Maven instructions can be copied and pasted into the command line interface to execute them."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Primary keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>archetypeVersion</varname> — indicates the RichFaces version; for example, <literal>3.3.1.GA</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>artifactId</varname> — the artifact ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>groupId</varname> — the group ID of the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>version</varname> — the version of the project you create. By default, this is set to <literal>1.0.-SNAPSHOT</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This operation creates a directory named after your <literal>ARTIFACT-ID</literal>. The directory contains a template of the Maven project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following steps will guide you though creating of the skin itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Run the following command from the root directory of the Maven project. (This directory will contain your <filename>pom.xml</filename> file.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>name</varname> — defines the name of the new skin"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>package</varname> — the base package of the skin. By default, the project's <literal>groupId</literal> is used."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Additional optional keys for the command:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — defines the name of the base skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>createExt</varname> — if set to <literal>true</literal>, extended CSS classes are added. For more information, please, see <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once these operations are complete, the following files and folders should have been created:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImage.java</filename> — the base class used to store images. Location: <filename>\\src\\main\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>BaseImageTest.java</filename> — a test version of a class that stores images. Location: <filename>\\src\\test\\java\\SKIN-PACKAGE\\SKIN-NAME\\images\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>XCSS files</filename> — XCSS files define the new look of RichFaces components affected by the new skin. Location: \"\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.properties</filename> — a file that contains the new skin's properties. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following properties are used to configure the <filename>SKIN-NAME.properties</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>baseSkin</varname> — the name of the skin to be used as a basis for your own skin. The look of the skin you define will be affected by the new style properties."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>generalStyleSheet</varname> — a path to the style sheet (<filename>SKIN-NAME.xcss</filename>) that imports your component's style sheets to be modified by the new skin."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>extendedStyleSheet</varname> — the path to a style sheet that is used to unify the appearance of RichFaces components and standard HTML controls. For additional information, read <xref linkend=\"StControlsSkinning\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>gradientType</varname> — a predefined property to set the type of gradient applied to the new skin. Possible values are <literal>glass</literal>, <literal>plastic</literal>, <literal>plain</literal>. More information on gradient implementation you can find further in this chapter."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME.xcss</filename> — an XCSS file that imports the component's XCSS files to be modified by the new skin. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>XCSS files</literal> — creates the XCSS files that determine styles for standard controls (<filename>extended_classes.xcss</filename> and <filename>extended.xcss</filename>), if the <varname>createExt</varname> key is set to <literal>true</literal>. Location: <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-ext.xcss</filename> — creates the <filename>SKIN-NAME-ext.xcss</filename> file that imports defining styles for standard controls if <varname>createExt</varname> is set to <literal>true</literal>. Location: <filename>src\\main\\resources\\META-INF\\skins</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>SKIN-NAME-resources.xml</filename> — contains descriptions of all files listed previously. Location: <filename>src\\main\\config\\resources</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now start editing the XCSS files located in <filename>\\src\\main\\resources\\SKIN-PACKAGE\\SKIN-NAME\\css\\</filename>. Assign new style properties to your selectors (listed in the XCSS files) in either of the following ways:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Standard CSS coding approach (that is, add CSS properties to the selectors). Remember that the selectors must be within <literal><f:verbatim> </f:verbatim></literal> tags. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "XCSS coding approach (the usual method of creating XCSS files in RichFaces). XCSS tags must be placed <emphasis>outside</emphasis> <literal><f:verbatim> </f:verbatim></literal> tags."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once you have performed these steps and edited the XCSS files, build the new skin and plug it into the project. To build the skin, execute the following command from the root directory of your skin project (the directory that contains your <filename>pom.xml</filename> file):"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Plug-n-skin feature also has a number of predefined gradients. The following code can be used to apply a gradient:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>background-image</varname> CSS property is defined with <literal><f:resource f:key=\"org.richfaces.renderkit.html.CustomizeableGradient\"></literal>, which sets the gradient. The gradient type can be specified in the <filename>SKIN-NAME.properties</filename> with the <varname>gradientType</varname> property, which can be set to <literal>glass</literal>, <literal>plastic</literal>, or <literal>plain</literal>. The gradient can then be adjusted with the <varname>baseColor</varname>, <varname>gradientColor</varname>, <varname>gradientHeight</varname>, <varname>valign</varname> attributes, as seen in the previous code snippet."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now use your newly-created skin in your project by adding your new skin parameters to the <filename>web.xml</filename> file, and placing the JAR file containing your skin (located in the <filename>target</filename> directory of your skin project) in the <filename>\\WebContent\\WEB-INF\\lib\\</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Details of Usage"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This section covers some practical aspects of Plug-n-Skin implementation. We assume that you have read the section of the guide describing the Plug-n-Skin prototype creation process."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, we must create a new skin (as described in the previous section). The following creates a template of the new skin project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can now browse the <filename>P-n-S</filename> directory to view the files and folders created."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use Maven to add all required files to the skin project, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As mentioned in the previous section, <!-- #modify '-D' typo? --><literal>-DbaseSkin</literal> defines the RichFaces built-in skin to use as a base, and <literal>-DcreateExt=true</literal>, which determines that the new skin will include XCSS files that unify the appearance of the rich components and the standard HTML controls."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Once your resources have been created, you can begin refining the newly-created skin. Begin by editing the rich components' XCSS files."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example of the Plug-n-Skin feature, we will edit some <literal><rich:calendar></literal> style attributes and some basic HTML controls. We will show you how to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor the background of the current day in the <literal><rich:calendar></literal>;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Recolor a standard HTML submit button;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To edit <literal><rich:properties></literal>'s style properties, you must open the <filename>calendar.xcss</filename> file, located in <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the <filename>calendar.xcss</filename> file, find the <literal>.rich-calendar-today</literal> selector and amend it as follows:<literal>background-color: #075ad1;</literal>. This will change the background color of the current day."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next we will change the font style of a standard HTML <emphasis>submit</emphasis> button. Open the <filename>extended.xcss</filename> file from the <filename>P-n-S\\src\\main\\resources\\skinpackage\\plugnskindemo\\css\\</filename> directory and insert <literal>font-weight: bold;</literal> between the curly braces of these selectors, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The desired changes have now been made, and you can proceed to building the new <literal>PlugnSkinDemo</literal> skin and importing it into the project."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Build the skin by executing <command>mvn clean install</command> from the <filename>P-n-S</filename> directory. This creates a <filename>target</filename> directory containing a JAR file with a newly-compiled skin. In our case, the file is named <filename>P-n-S-1.0.-SNAPSHOT.jar</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, import the new <literal>PlugnSkinDemo</literal> skin into your project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Copy the <filename>P-n-S-1.0.-SNAPSHOT.jar</filename> file to the <filename>\\WebContent\\WEB-INF\\lib\\</filename> directory."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the name of the new skin to the <filename>web.xml</filename> file, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember, standard controls skinning must be enabled in <filename>web.xml</filename>. Add the following to enable standard controls skinning:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The results of each alteration to the skin are shown in the figures that follow:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Plug-n-Skin feature in action."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "State Manager API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JSF has an advanced navigation mechanism that lets you define <emphasis>navigation</emphasis> from view to view. In a web application, navigation occurs when a user changes from one page to another by clicking on a button, a hyperlink, or another command component. There is no switch mechanism between some logical states of the same view. For example, in <emphasis>Login/Register dialog</emphasis>, an existing user signs in with his user name and password, but if a new user attempts to register, an additional field (<literal>Confirm</literal>) is displayed, and button labels and methods are changed when the user clicks the <guilabel>To register</guilabel> link:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Login Dialog"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Register Dialog"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>RichFaces State API</emphasis> lets you easily define a set of states for pages, and properties for these states."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>States</varname> class interfaces with a <property>map</property>, where the <methodname>keySet</methodname> defines the State name and the <methodname>entrySet</methodname> is a <varname>State</varname> <property>map</property>. The <varname>State</varname> <property>map</property> defines the properties, method bindings, or constant state variables of a key or object, where these values may change depending on the active State."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces State API"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One of the most convenient features of the RichFaces State API is the ability to navigate between <varname>State</varname>s. The API implements changes in <varname>State</varname> through standard JSF navigation. When the action component returns an outcome, the JSF navigation handler (extended through the RichFaces State API) checks whether the outcome is registered as a <emphasis><varname>State</varname> change outcome</emphasis>. If <literal>true</literal>, the corresponding <varname>State</varname> is activated. If <literal>false</literal>, standard navigation handling is called."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Implement the RichFaces State API like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register the State Navigation Handler and the EL Resolver in your <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register an additional application factory in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Register two managed beans in the <filename>faces-config.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One bean (<literal>config</literal>) defines and stores <varname>State</varname> as seen in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second bean, with the <literal>org.richfaces.ui.model.States</literal> type (<literal>state</literal>), contains the managed property <property>states</property>, which is bound to the first <literal>config</literal> bean."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Next, use <property>state</property> bindings on the page, as in the following example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To see complete example of the Login/Register dialog, see the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/stateAPI.jsf?c=stateAPI\">RichFaces Live Demo</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Identifying User Roles"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces also lets you check whether the logged-in user belongs to a certain <property>user role</property> with the <literal>rich:isUserInRole(Object)</literal> function. This function takes a String or a comma-delineated list of Strings, a Collection, etc. as arguments and returns a Boolean value."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As an example, imagine that you need to render some controls only for administrators. To do so, create an administrator role (<literal>admin</literal>) in your <filename>web.xml</filename> file. Then implement authorization that assigns the <literal>admin</literal> role to the user that has logged in as an administrator. Once this has been done, you can use the <literal>rich:isUserInRole(Object)</literal> function with the <varname>rendered</varname> attribute of any component. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Here, only a logged-in user with an <literal>admin</literal> role can see the text editor, which will not be rendered for users with other roles."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/Author_Group.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/Author_Group.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/Author_Group.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/Book_Info.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/Book_Info.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/Book_Info.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Developer Guide"
+msgstr ""
+
+#. Tag: subtitle
+#, no-c-format
+msgid "for Use with JBoss Enterprise Application Platform"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/FAQ.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/FAQ.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/FAQ.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,989 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "FAQ"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find additional information on RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Most important links for RichFaces can be found <ulink url=\"http://jboss.com/index.html?module=bb&op=viewtopic&t=104575\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where are the binary/source distributions for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Distributions are available from the <ulink url=\"http://labs.jboss.com/jbossrichfaces/downloads/\">JBoss RichFaces Download area</ulink>. The source distribution is found in the <filename>richfaces-ui-3.3.0-src.zip</filename> file. The binary distribution is in the <filename>richfaces-ui-3.3.0-bin.zip</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I manually build a RichFaces snapshot?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This <ulink url=\"http://labs.jboss.com/wiki/HowToBuildRichFacesSnapshotManually\"> wiki article</ulink> takes you through the process."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I configure Maven for RichFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, download and install Maven. (Follow the instructions at <ulink url=\"http://maven.apache.org/download.html\">http://maven.apache.org/download.html</ulink>.)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Open the <filename><Maven-Root>/conf/settings.xml</filename> file and add the following to the <literal><profile></literal> section:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following to the <literal><activeProfiles></literal> section:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is the structure of RichFaces SVN repository?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can see the structure in the RichFaces Repository Structure Overview in <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">this Wiki article</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I build <literal>richfaces-samples</literal> applications?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "he <ulink url=\"http://labs.jboss.com/wiki/RichFacesRepositoryStructureOverview\">RichFaces Repository Structure Overview</ulink> describes how to build <literal>richfaces-samples</literal> applications in Eclipse."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Where can I find a demo for RichFaces components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Online demo applications that showcase RichFaces features are available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also find a nightly build (in the WAR format) <ulink url=\"http://maven.exadel.com/org/richfaces/samples/richfaces-demo/3.1.0-SNAPSHOT/\">here</ulink>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Source Code (SVN) can be found <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-demo/\">in the JBoss RichFaces SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What causes the \"Prototype.Browser() function cannot be found\" error in RichFaces 3.1.0, and how do I fix it?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Your application probably uses an older version of Prototype from Tomahawk 1.1.6. RichFaces 3.1.0 uses the latest Prototype (1.5.1.1). Upgrade your version of Prototype to solve this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does the RichFaces library contain the <literal><rich:dataTable></literal> component as well as the <literal><h:dataTable></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dataTable></literal> component lets you use skins to change the look and feel of your data tables. You can see an example of the difference between these components at the <ulink url=\"http://livedemo.exadel.com/richfaces-art-datatable/\">RichFaces dataTable LiveDemo page</ulink>, or see the source code in the <ulink url=\"http://anonsvn.jboss.org/repos/richfaces/trunk/samples/richfaces-art-datatable/\">SVN repository</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I organize wizards with the <literal><rich:modalPanel></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Place the <literal><a4j:include></literal> tag inside the <literal><rich:modalPanel></literal> and perform navigation inside it, as in the following example below:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I stop <literal>modalPanel</literal> closing when validation fails?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two methods available to fix this problem. The first is simply to remove the <literal>windowclose()</literal> method from the <literal>modalPanel</literal>, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that when an error presents, the panel will simply do nothing rather than closing the window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The second method assumes that you use Facelets. Add the following to your <filename>default.xhtml</filename> template:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This invisible form will be refreshed on every postback, and contains a hidden field that determines the maximum severity in the message queue. If you add the following function to your JavaScript:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method reads the value of the hidden field to determine whether the last postback to the server generated any errors. This means that the <literal><a4j:commandLink></literal> or <literal><a4j:commandButton></literal> that submits your form will look like this:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This method lets you easily adjust the behaviour of any JavaScript code depending on whether an error is present. See the <ulink url=\"http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4061517\">JBoss RichFaces forum</ulink> post for more information and variations on this method."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "When I use <literal>suggestionbox</literal> inside the <literal>modalPanel</literal>, the suggestion list sits behind the <literal>modalPanel</literal> and I cannot see it. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You are using an old version of RichFaces. Upgrade to the latest version to fix this problem."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Does RichFaces work with Facelets?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes. Full Facelets support is one of RichFaces' primary features. The main <ulink url=\"http://livedemo.exadel.com/richfaces-demo/\"> demo</ulink> is a Facelets-based application."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I create a dynamic menu with the <literal><rich:dropDownMenu></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:dropDownMenu></literal> is a standard JSF component, so creating a menu dynamically from the JavaScript code is the same as for any other JSF component."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I customize the look of a <literal>datascroller</literal> (the forward/back buttons) and replace them with images?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can. The <literal>datascroller</literal> component provides two controller groups for switching:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Page numbers</emphasis> so that you can switch to a particular page."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>Fast-switching</emphasis> controls: <literal>first</literal>, <literal>last</literal>, <literal>next</literal>, <literal>previous</literal>, <literal>fastforward</literal> and <literal>fastrewind</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create fast-switching controls by adding a <literal>facet</literal> component with the corresponding name:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also create disabled states with facets There are also facets used to create the disabled states: <literal>first_disabled</literal>, <literal>last_disabled</literal>, <literal>next_disabled</literal>, <literal>previous_disabled</literal>, <literal>fastforward_disabled</literal>, <literal>fastrewind_disabled</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I place simple links inside a menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To include a link to an external URL, use the following approach:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see a demonstration of the <literal><rich:dropDownMenu></literal> component at the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/dropDownMenu.jsf\">RichFaces LiveDemo page</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal>dropDownMenu</literal> as a context menu?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:dropDownMenu></literal> is not designed for use as a <literal>contextMenu</literal>. A <literal><rich:contextMenu></literal> component is planned for development, but is not scheduled for any currently planned version."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass my own parameters during a <literal>modalPanel</literal> opening or closing?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass your parameters during modalPanel opening or closing like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can pass any of your own parameters, except for the standard <literal>modalPanel</literal> parameters."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I add a simple link to the tree node?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following simple code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Is it possible to place tabs upright in the <literal>tabPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, it is not. Try using the <literal>togglePanel</literal> instead; toggle controls can be placed anywhere in the layout."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use a <literal>commandButton</literal> within the <literal>modalPanel</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are two important rules to follow when using <literal>modalPanel</literal>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if <literal>modalPanel</literal> has form elements (input or command elements), it must have its own form."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "if the <literal>modalPanel</literal> contains a form, it must not be included in a higher-level form."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I define the currently selected tab?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I retrieve the current value from the <literal>inputNumberSlider</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can retrieve the value with the following approach:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How to apply skins to the standard input components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The answer could be found <ulink url=\"http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103494\">here</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I remove the table border and styles from the <literal>datascroller</literal> and show only links?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To do this, you must redefine your rich* classes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I expand/collapse tree nodes from code?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://www.jboss.org/community/wiki/ExpandCollapseTreeNodes\">This Wiki article</ulink> has some useful information about expanding and collapsing tree nodes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the JavaScript API?"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I load the Scriptaculous library?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To load the whole Scriptaculous library shipped with RichFaces, use the <literal><a4j:loadScript></literal> tag:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This command lets you load an integrated version of the library that includes all existing Scriptaculous files, <emphasis>except</emphasis> <filename>unittest.js</filename>. If you do not want to load the whole library, but wish to load a specific file (for example, <filename>effect.js</filename>), use the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you load the whole library, you do not need to load a particular file."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid the problem with text wrapping in <literal><rich:tab></literal> in Internet Explorer 7?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The problem lies with a tab height bug in IE7. (Tab height is correct in Firefox and in IE6.) To work around the bug, you can change the doctype declaration from:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can also see the <ulink url=\"http://jira.jboss.com/jira/browse/RF-1011\">JIRA Issue</ulink> for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the status of the <literal><rich:effect></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal><rich:effect></literal> has several callback methods such as <literal>beforeStart</literal> and <literal>afterFinish</literal>, which can be used to save the status. You can also see the <ulink url=\"http://wiki.github.com/madrobby/scriptaculous/core-effects\">Scriptaculous Core Effects</ulink> page for further information."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I send an additional parameter to the server with <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This example code gives you one method:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the example, the <literal>onselect</literal> event sends the selected value to the server. You can pass additional fields of the selected object (which do not belong to the <literal>fetchvalue</literal> attribute) in the same way."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I set the border of <literal><rich:dataTable></literal> to 0px?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your CSS file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I dynamically create a <literal><rich:suggestionbox></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is a working example:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What should I change on the server side?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The list of zones to be rerendered can be specified as an EL expression. The list of IDs is formed during the <literal>RENDER_RESPONSE</literal> <emphasis>beforePhase</emphasis>, so you can point the <literal>reRender</literal> to the <classname>Set</classname>, and fill it during a tracking request to form a list of areas which can be dynamically updated."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I check request conditions before sending a request?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To check the terms of sending a request on a client, add the <literal>onSubmit</literal> attribute to all components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this example, the <literal>doSomething()</literal> function is executed before the AJAX request, and if the function returns <literal>false</literal>, the request is not fired."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The behavior of our <literal>onsubmit</literal> attribute differs slightly from the standard <literal>onsubmit</literal>. Do not return <literal>true</literal> if you want to fire the request: <code><xxx><a4j:support event=\"onclick\" onsubmit=\"return true;\"></code> becomes <code><xxx onclick=\"return true;A4J.Submit(.... );\" ></code> and standard event processing is fired instead of the request. Only return <literal>false</literal> if your conditions were not completed, or set actions to be performed without any returned response if you do need to fire the request."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What were the changes to the <varname>onComplete</varname> attribute after version 1.0?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To avoid conflict with other JavaScript attributes, we have changed the placement of a function during a Javascript call. Rather than inserting attribute contents (<code>oncomplete:anotherFunction(this)</code>), we make the function anonymous (<code>oncomplete:function(){anotherFunction(this);}</code>) so that you can insert a <emphasis>chain</emphasis> of statements into an attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The change also means that the <literal>this</literal> keyword will point to a parameter map instead of a control element. You can use <code>document.findElementById()</code> to retrieve references to this parameter map after a request is processed. Pages updated with AJAX will then reference a control removed from a DOM tree."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you are certain that your element will not be updated, you can add <literal>onsubmit</literal> to your <literal><a4j:support></literal> tag (or <literal>onclick</literal> to your <literal><a4j:commandLink/Button></literal> tag) to place a reference to a known variable, like so: <code><a4j:commandLink onclick=\"var myControl=this;\" oncomplete=\"anotherFunction(myControl)\"/></code>)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The onComplete syntax now follows this form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>event</literal> is a variable defining the location in which the JavaScript event that fires the request will be placed. <literal>data</literal> is a variable containing the deserialized value of the <varname>data</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use InvokeOnComponent with JSF 1.2?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not use <literal>invokeOnComponent</literal> for two reasons:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To retain compatibility with JSF 1.1 and MyFaces applications, since these are often used in corporate applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>invokeOnComponent</literal> works well when used to communicate between a Widget and a backed component, or to update the content of a rendered component. However, there are some limitations for more complicated use-cases implemented in RichFaces, such as making update decisions with application logic."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This means that you must update whole components (for example, an entire <literal>dataTable</literal>), but all AJAX core action components in that component will work correctly."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I avoid generating exceptions for the <literal><a4j:keepAlive></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Remember: the component stores beans in a serialized view. Your bean should implement <literal>java.io.Serializable</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "My form will not submit, or, my setter is not called after an AJAX request. What's wrong?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This can occur because of conversion or validation errors at submission time. To verify this, place the following update message inside a form:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:message></literal> component has built-in AJAX support, and can be combined with the <ulink url=\"http://www.jsfone.com/blog/max_katz/2008/07/creating_jsf_phase_listener.html\">JSF Phase Tracker</ulink> to fix this issue, in some instances."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I create an <literal>a4j</literal> delayed render zone?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><a4j:support></literal> component has a <varname>requestDelay</varname> attribute, where you can define the delay period."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use IgnoreDupResponses and requestDelay?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>ignoreDupResponses</varname> ignores an AJAX request if a newer request exists. <varname>requestDelay</varname> defines the time delay on the client between compiling a request response and sending that response. You can find more information in <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use eventsQueue attribute?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>eventsQueue</literal> defines the name of the queue that will order upcoming AJAX requests. The queue makes certain that redundant requests are not sent. It is created and named by default. You can find more information in the section on <xref linkend=\"QueueandTrafficFloodProtection\" />."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use multiple <literal><a4j:status></literal> components on one page?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Yes, you can. You can find out more from the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/status.jsf?c=status\">JBoss RichFaces Online Demos</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Can I use the <literal><a4j:region></literal> component inside the <literal><a4j:repeat></literal> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "No, you cannot. The <literal><a4j:region></literal> component cannot work inside iteration components such as <literal><h:dataTable></literal> and <literal><a4j:repeat></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I disable skinnability?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You cannot disable skinnability, but you can use a special skin: <literal>plain</literal>. This skin has no parameters, and was created to enable you to embed RichFaces components into existing projects with their own predefined styles."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why does my reRender fail when using hide/show components?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Rerendering fails when RichFaces tries to update a component that is defined as hidden or rendered. When <literal>rendered=\"false\"</literal>, the component is not added to the DOM tree, so it cannot be updated (as per the limitations described in the AJAX Processing chapter)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The correct way to rerender a hidden or rendered component is to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Wrap the component that is to be hidden or rendered on AJAX in a wrapper component such as <literal><a4j:outputPanel></literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Set the <varname>reRender</varname> attribute on the wrapper component instead of on the component itself."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Fpr example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This ensures that the wrapper component presents in the DOM tree, which means that its contents can be updated dynamically."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why am I seeing a <exceptionname>ResourceNotRegistered</exceptionname> Exception?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces registers its resources (for example, scripts and images) after an application is accessed, and then accesses these via a generated URL. During application development, when an application is constantly updated on the server, RichFaces may re-register its resources after every server restart, while the browser may attempt to access resources via a cached URL."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can solve this problem by updating the browser cache: press <keycap>CTRL</keycap>+<keycap>F5</keycap>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I reRender only a particular row(s) of a table?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>ajaxKeys</literal> attribute defines Strings that are updated after an AJAX request, and lets you update several child components separately without updating the whole page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable row selection in a scrollableDataTable using <literal>one and multi-selection rows mode</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable row selection in <literal>one and multi-selection rows mode</literal>, you must use the <varname>selection</varname> attribute. In the example code that follows, when a user submits the form, the current collection of objects selected by the user is placed in the object's property. Upon completion, the <literal><rich:modalPanel></literal> will be rendered with the selected data."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, you can create a managed bean like the one below. The <literal>takeSelection()</literal> method fills the <literal>selectedCars</literal> Array with data retrieved from the <varname>selection</varname>. The <literal>getSelectedCars()</literal> method returns <literal>selectedCars</literal> Array, which is then used to populate select rows of the <literal><rich:dataTable></literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I select several rows in a <literal>scrollableDataTable</literal> and drag-and-drop them into a <literal>dataTable</literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "First, to enable row selection, see the previous section on <xref linkend=\"RowSelectionInScrollableDataTable\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To enable the drag-and-drop function on a <literal>dataTable</literal>, use the <literal><rich:dragSupport></literal> and <literal><rich:dropSupport></literal> components, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The previous example is also available on the <ulink url=\"http://livedemo.exadel.com/richfaces-demo/richfaces/scrollableDataTable.jsf\">RichFaces LiveDemo</ulink> site. Only one method is added where the dropped collection is stored:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of the <rich:simpleTogglePanel>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>opened</varname> attribute responsible for storing panel state, and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:simpleTogglePanel></literal> icon appears and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered between page views."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To build this application, create a managed bean like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I save the state of <rich:panelMenuGroup>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can use the <varname>expanded</varname> attribute and an <literal><a4j:support></literal> tag bound to <varname>onexpand</varname> and <varname>oncollapse</varname> events."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In the following example, when you click on the toggle icon, the <literal><rich:panelMenuGroup></literal> expands and the current state is displayed in the <literal><rich:modalPanel></literal>. This state is remembered across page views."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I highlight the rows of a dataTable on the mouseover event?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <literal>onRowMouseOver</literal> and <literal>onRowMouseOut</literal> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I enable selecting the row of a <literal><rich:dataTable></literal> when I click on it, even if I click within the bounds of an <literal><h:inputText></literal>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the following JavaScript function to enable row selection when you click on the row:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can then use <literal><a4j:support></literal> with <varname>event</varname> and <varname>onsubmit</varname> attributes, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I rerender table cells with <a4j:support>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To rerender table cells with <literal><a4j:support></literal>, set exact ID values for each component to be updated, and point this <varname>id</varname> to the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The value of the <varname>reRender</varname> attribute belonging to the <literal> <a4j:support></literal> tag defines the sections of the page that will be updated. In the previous example code, the only update made is to the <literal><h:outputText></literal> component in the footer, because its <literal>id</literal> value matches the value of the <varname>reRender</varname> attribute. You can update multiple elements on a page by listing their IDs as the value of the <varname>reRender</varname> attribute."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I create dynamic columns?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can create dynamic columns by using the <literal><rich:column></literal> with the <varname>rendered</varname> attribute. Set the value of the <varname>rendered</varname> attribute to match the ID of the dynamic cell, as in the following example code:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you could create a managed bean, like so:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I use RichFaces with Trinidad?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of a basic <filename>web.xml</filename> file that integrates RichFaces with Trinidad."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Why do I see a JavaScript conflict?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Richfaces 3.1.3 uses version 1.6.0 of the <filename> prototype.js</filename> instead of version 1.5.1, which has been used in earlier versions. The source of the conflict is that two versions of the prototype script are included. The first is included as a dependency of the toggle panel components, and the second is included explicitly as a link."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces 3.1.3 is bundled with the same scripts included in Prototype 1.6.0 and Scriptaculous 1.8.0:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Using Prototype with RichFaces components can be problematic because issues that were fixed in version 1.6.0 were not always patched in version 1.5.1. When version 1.5.1 is used, some RichFaces components will not work as expected."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with the Seam Framework?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To use the <literal><rich:fileUpload></literal> component with the Seam Framework, define initialization parameters for the Seam Filter in your <filename>web.xml</filename> file. The Seam Framework will then automatically set the component up for the AJAX4JSF filter at start-up time."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code is an example of defining initialization parameters:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I use the <rich:fileUpload> component with MyFaces?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The order in which filters are defined and mapped in <filename>web.xml</filename> is important to integrating the <literal><rich:fileUpload></literal> component with MyFaces. The code sample that follows shows the correct order in which to define your filters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To ensure that this sequence wors correctly, map the extension filter on your Faces Servlet, not to <filename>*.jsf</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable optional object selection in <rich:suggestionbox>?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal><rich:suggestionBox></literal> component provides features such as object selection. To store the selected items as objects to be accessed, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the <varname>usingSuggestObjects</varname> attribute to the <literal><rich:suggestionBox></literal> component, and define it as <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use the <varname>onobjectchange</varname> event attribute to store the currently-selected objects."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All of the selected objects are stored in the <literal>suggestion.SelectedItems</literal> Array. Each Array element contains <literal>text</literal> and <literal>object</literal> properties, so you can iterate this Array, retrieve objects that are not <literal>null</literal>, and retrieve the required property."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for ViewExpiredException?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This exception appears after your session has timed out. Because RichFaces 3.1 is intended for use with JavaServer Faces 1.1, <exceptionname>ViewExpiredException</exceptionname>s will not generate automatically when RichFaces is used with JavaServer Faces 1.2. To work around this limitation, add the following to your <filename>web.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I enable handling for Request Errors and Session Expiration?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To redefine the standard handlers that are responsible for processing different exceptional situations, follow these steps:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add custom <literal>onError</literal> and <literal>onExpire</literal> handlers, like so:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For a more detailed description of this process, see <xref linkend=\"RequestErrorsAndSessionExpirationHandling\" /> in the Developer Guide."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Custom <literal>onError</literal> and <literal>onExpire</literal> handlers will not work under MyFaces, because MyFaces handles exceptions with an internally-generated debug page. To prevent this behavior, use the following code:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How can I add a cookie in an AJAX response?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The bean described below adds a cookie to an AJAX response:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, you can define the cookie to be included as shown in the following example. After the <literal>test</literal> cookie is set, the value of that cookie will appear on a page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What is new in AJAX4JSF 3.2.x?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces 3.2.x releases have some new features:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><a4j:portlet</literal> component has been <emphasis>deprecated</emphasis>, since JSR-301 defines a similar function for <literal>UIViewRoot</literal> components;"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the <literal><rich:ajaxValidator></literal>, <literal><rich:beanValidator></literal> and <literal><rich:graphValidator></literal> validators have been added to provide different validation types."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I launch the RichFaces sample on the JBoss server?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To launch the RichFaces sample application on the JBoss server, add the following code to your <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "How do I pass a Boolean value in the <rich:componentControl> component?"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following code shows you how to avoid requiring a Boolean value:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Use <code>'block'</code> instead of <code>' '</code> to avoid <literal>invalid style</literal> CSS errors."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/Getting_Started.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/Getting_Started.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/Getting_Started.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,159 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Getting Started with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This chapter tells you how to plug RichFaces components into a JSF application. The instructions are based on a simple <emphasis>JSF with RichFaces</emphasis> creation process, from downloading the required libraries to running the application in a browser. These instructions do not depend on the integrated development environment that is in use."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Simple JSF application with RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> — the simple application — is similar to a typical <emphasis>hello world</emphasis> application, with one exception: the world of RichFaces will say \"Hello!\" to the user first."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Create a standard JSF 1.2 project named <literal>Greeter</literal>. Include all required libraries, and continue with the instructions that follow."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Adding RichFaces libraries into the project"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "From the <filename>RichFaces</filename> folder where you unzipped the RichFaces binary files, open the <filename>lib</filename>. This folder contains three <filename>*.jar</filename> files with API, UI, and implementation libraries. Copy these JARs from <filename>lib</filename> to the <filename>WEB-INF/lib</filename> directory of your <application>Greeter</application> JSF application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A JSF application with RichFaces assumes that the following JARs are available in the project:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-beanutils-1.7.0.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-collections-3.2.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-digester-1.8.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>commons-logging-1.0.4.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jhighlight-1.0.jar</filename>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering RichFaces in <filename>web.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "After you add the RichFaces libraries to the project, you must register them in the project <filename>web.xml</filename> file. Add the following to <filename>web.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For more information about RichFaces skins, read <xref linkend=\"Skinnability\" />."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Finally, your <filename>web.xml</filename> should look like this:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Managed bean"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <application>RichFaces Greeter</application> application needs a managed bean. In the project's <filename>JavaSource</filename> directory, create a new managed bean named <literal>user</literal> in the <literal>demo</literal> package. Place the following code in <filename>user</filename>:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Registering the bean in <filename>faces-cofig.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To register the <literal>user</literal> bean, add the following to the <filename>faces-config.xml</filename> file:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RichFaces Greeter index.jsp"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces Greeter</application> has only one JSP page. Create <filename>index.jsp</filename> in the root of <literal>WEB CONTENT</literal> folder and add the following to the JSP file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The application uses three RichFaces components: <emphasis role=\"bold\"><property><rich:panel></property></emphasis> is used as visual container for information; <emphasis role=\"bold\"><property><a4j:commandButton></property></emphasis> with built-in AJAX support lets a greeting be rendered dynamically after a response returns; and <emphasis role=\"bold\"><property><a4j:form></property></emphasis> helps the button to perform the action."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The RichFaces tag library should be declared on each JSP page. For XHTML pages, add the following lines to declare your tag libraries:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Now, run the application on the server by pointing your browser to the <filename>index.jsp</filename> page: <literal>http://localhost:8080/Greeter/index.jsf</literal>"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "\"RichFaces Greeter\" application"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Relevant Resources Links"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"https://www.redhat.com/apps/store/developers/jboss_developer_studio.html\">JBoss Developer Studio</ulink> includes tight integration with the RichFaces component framework. <!-- The following links might be useful for those who already use this IDE and RichFaces to develop applications, and for those who wish to improve their development process. -->"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/IDE_Support.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/IDE_Support.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/IDE_Support.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Integrated Development Environment Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is supported by both <ulink url=\"http://www.redhat.com/developers/rhds/index.html\">JBoss Developer Studio 1.0.0 GA</ulink> and <ulink url=\"http://www.jboss.org/tools/index.html\">Jboss Tools</ulink>. JBoss Developer Studio is a fully packaged Integrated Development Environment (IDE) that provides full support for Java Server Faces, RichFaces, Facelets, Struts and other Web technologies. It seamlessly combines visual and source-oriented development approaches. You can add JBoss Developer Studio capabilities to any JSF project by adding the appropriate libraries and modifying configuration files as required."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/Introduction.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/Introduction.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/Introduction.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,79 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Introduction"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is an open source framework that adds AJAX capability into existing JSF applications without resorting to JavaScript."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces leverages aspects of the JavaServer Faces (JSF) framework, including lifecycle, validation, conversion facilities, and management of static and dynamic resources. RichFaces components with built-in AJAX support and a highly customizable look-and-feel can be easily incorporated into JSF applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces allows you to:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Experience the benefits of JSF while working with AJAX. RichFaces is fully integrated into the JSF lifecycle. Where other frameworks only allow access to the managed bean facility, RichFaces lets you access the action and value change listeners, and invokes server-side validators and converters during the AJAX request-response cycle."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Add AJAX capabilities to existing JSF applications. The RichFaces framework provides two component libraries (Core AJAX and UI). The Core library adds AJAX functionality to existing pages, so you need not write any JavaScript or replace existing components with new AJAX components manually. RichFaces enables page-wide rather than component-wide AJAX support, giving you the opportunity to define events on the page. <!-- An event invokes an AJAX request and areas of the page which become synchronized with the JSF Component Tree after changing the data on the server by AJAX request in accordance with events fired on the client. -->"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily create different views with a variety of components, available out-of-the-box. The RichFaces UI library contains components for adding rich user interface (UI) features to JSF applications, providing you with a broad variety of AJAX-enabled components with extensive skins support. RichFaces components are designed to integrate seamlessly with other third-party component libraries, so you have more options when you develop applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Write your own rich components with built-in AJAX support. The Component Development Kit (CDK) is constantly being expanded. It includes both code generation and templating facilities and a simple JSP-like (JavaServer Pages) syntax, letting you create first-class rich components with built-in AJAX functionality."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Package resources with application Java classes. RichFaces provides advanced support for managing different resource types, including images, JavaScript code, and CSS stylesheets. The resource framework makes it easier to include these resources in JAR files with your custom component code."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Quickly and easily generate binary resources. The resource framework can generate images, sounds, Excel spreadsheets, etc. in real time, so you can, for example, create images with the Java Graphics 2D library and other similar resources."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Customize the look and feel of your user interface with skins-based technology. RichFaces lets you easily define and manage different color schemes and other user interface parameters by using named <emphasis>skin parameters</emphasis>. This means you can access UI parameters from JSP and Java code to adjust your UI in real time. RichFaces includes a number of predefined skins to kick-start your application's development, but it is easy to create your own custom skins."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Simultaneously create and test your components, actions, listeners, and pages. RichFaces will soon include an automated testing facility to generate test cases for your component as you develop it. The testing framework tests not only the components, but also any other server-side or client-side functionality, including JavaScript code — and it will do so <emphasis>without</emphasis> deploying the test application into the Servlet container."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces UI components can be implemented immediately, right out of the box. This saves development time and gives you immediate access to RichFaces web application development features, so experience with RichFaces is fast and easy to obtain."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/Links_to_Resources.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/Links_to_Resources.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/Links_to_Resources.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,74 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Links to information resources"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Resources"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Links"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss RichFaces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/portal/jbossrichfaces/\">JBoss RichFaces</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "JBoss Forum"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://jboss.com/index.html?module=bb&op=main&c=27\">JBoss Forums</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Wiki"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://labs.jboss.com/wiki/RichFaces\">RichFaces Wiki</ulink>"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "RichFaces Blog"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "<ulink url=\"http://jroller.com/page/a4j\">RichFaces Blog</ulink>"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/Revision_History.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/Revision_History.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/Revision_History.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,24 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: member
+#, no-c-format
+msgid "JIRA corrections."
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/RichFaces_Developer_Guide.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/RichFaces_Developer_Guide.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/RichFaces_Developer_Guide.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,14 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/Settings.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/Settings.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/Settings.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,334 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Settings for different environments"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces includes support for all tags (components) included in the JavaServer Faces (JSF) specification. To add RichFaces capabilities to an existing JSF project, place the RichFaces libraries into the <filename>lib</filename> directory of the project, and add filter mapping. The behavior of the existing project does not change when you add RichFaces."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web Application Descriptor Parameters"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces does not require that any parameters be defined in your <filename>web.xml</filename>, but the RichFaces parameters listed below will help you during the development process and increase the flexibility of your RichFaces applications."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Name"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Default"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Description"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.SKIN"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "DEFAULT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The name of a skin that is used in an application. Can be a literal string with a skin name or the EL expression (<literal>#{...}</literal>) associated with a String property (skin name) of a property of a <literal>org.richfaces.framework.skin</literal> type. In the latter case, that instance is used as the current skin."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadScriptStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces script files are loaded to the application. Possible values are <literal>ALL</literal>, <literal>DEFAULT</literal> and <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.richfaces.LoadStyleStrategy"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines how the RichFaces style files are loaded into the application. Possible values are: <literal>ALL</literal>, <literal>DEFAULT</literal>, or <literal>NONE</literal>."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.LOGFILE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "none"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "The URL of an application or a container log file (if applicable). If this parameter is set, content from the given URL is shown on a Debug page in the <literal>iframe</literal> window."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.VIEW_HANDLERS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of <literal>ViewHandler</literal> instances for inserting in a view handler chain. These handlers are inserted before the RichFaces viewhandlers, in the order they are listed. In a Facelets application, you would declare <literal>com.sun.facelets.FaceletViewHandler</literal> here instead of in the <filename>faces-config.xml</filename> file."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.CONTROL_COMPONENTS"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A comma-separated list of special <emphasis>control case</emphasis> components, such as the messages bundle loader or an alias bean component. These handlers are provided via a reflection from the static field <literal>COMPONENT_TYPE</literal>. Encoding methods for these components are always called while rendering AJAX responses, even if a component has not been updated."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_RESOURCE_DATA"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "false"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "For generated resources (such as encrypt generation data), this is encoded in the resource URL. For example, the URL of an image generated by the <classname>mediaOutput</classname> component contains the name of a generation method. Since malicious code can exploit this to create a request for any JSF bean or attribute, this parameter should be set to <literal>true</literal> in critical applications. (This fix works with Java Runtime Environment 1.4.)"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.ENCRYPT_PASSWORD"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "random"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A password used to encrypt resource data. If this is not set, a random password is used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.COMPRESS_SCRIPT"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "true"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "When defined, does not allow the frameword to reformat JavaScript files. This means that the debug feature cannot be used."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URLs of all generated resources. This is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.GLOBAL_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/g"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be added to the URI of all global resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SESSION_RESOURCE_URI_PREFIX"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "a4j/s"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the prefix to be used to track the sessions of generated resources. This prefix is designed to handle RichFaces generated resource requests."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.DEFAULT_EXPIRE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "86400"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Defines the period (in seconds) for which resources are cached when they are streamed back to the browser."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "org.ajax4jsf.SERIALIZE_SERVER_STATE"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "If set to <literal>true</literal>, the component state (not the tree) will be serialized before it is stored in the session. This can be useful in applications with view state that is sensitive to model changes. Alternatively, use <literal>com.sun.faces.serializeServerState</literal> and <literal> org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</literal> parameters in their respective environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>org.richfaces.SKIN</literal> is used in the same way as <literal>org.ajax4jsf.SKIN</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "org.ajax4jsf.Filter Initialization Parameters"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "log4j-init-file"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "-"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "A path (relative to the web application's context) to the <filename>log4j.xml</filename> configuration file. This can be used to set up per-application custom logging."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "enable-cache"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Enables caching of framework-generated resources (JavaScript, CSS, images, etc.). However, your cached resources will not be used when attempting to debug custom JavaScript or Styles."
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "forcenotrf"
+msgstr ""
+
+#. Tag: entry
+#, no-c-format
+msgid "Forces all JSF pages to be parsed by a HTML syntax check filter. If set to <literal>false</literal>, only AJAX responses will be parsed and converted to well-formed XML. Setting this to <literal>false</literal> can improve performance, but may also cause unexpected information to be rendered during AJAX updates."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Sun JSF RI"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces works with JavaServer Faces 1.2_13 without needing to modify additional settings."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Facelets Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces has high-level support for Facelets, regardless of the version used. However, some JSF frameworks (including Faces) require that their own <literal>ViewHandler</literal> be listed first in the <literal>ViewHandler</literal> chain. RichFaces also requires that its <literal>AjaxViewHandler</literal> be listed first, but because it is installed first, no settings will need to be altered. Where multiple frameworks are used without RichFaces, you can use the <literal>VIEW_HANDLERS</literal> parameter to define the order in which the <literal>ViewHandler</literal>s are used. For example:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This declares that while <literal>Facelets</literal> will officially be first, <literal>AjaxViewHandler</literal> will briefly be ahead of it to perform some small, important task."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "In this case, you need not define <literal>FaceletViewHandler</literal> in <filename>WEB-INF/faces-config.xml</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JBoss Seam Support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces is compatible with <application>JBoss Seam</application> and Facelets when run within JBoss Enterprise Application Server. No additional JARs are required. All you need to do is package the RichFaces library with your application."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For <application>Seam 1.2</application>, your <filename>web.xml</filename> must be as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>Seam 2.x</application> supports RichFaces Filter, so your <filename>web.xml</filename> must look like this:"
+msgstr ""
+
Added: projects/docs/enterprise/5.0/RichFaces/zh-CN/Technical_Requirements.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/zh-CN/Technical_Requirements.po (rev 0)
+++ projects/docs/enterprise/5.0/RichFaces/zh-CN/Technical_Requirements.po 2009-12-10 05:41:45 UTC (rev 97668)
@@ -0,0 +1,179 @@
+#
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"PO-Revision-Date: 2009-12-10T05:38:02\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Technical Requirements"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<application>RichFaces</application> was developed with an open architecture to ensure that it was compatible with the widest possible variety of environments."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This is what you need to start working with <application>RichFaces 3.3.1</application>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JavaServer Faces"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java Application Server <emphasis>or</emphasis> Servlet Container"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Browser (on client side)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RichFaces Framework"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Java Versions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JDK 1.5 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported JavaServer Faces Implementations and Frameworks"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun JSF-RI - 1.2_12"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "MyFaces 1.2.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Facelets 1.1.1 - 1.2"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Seam 1.2. - 2.1.0"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Servers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Apache Tomcat 5.5 - 6.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "BEA WebLogic 9.1 - 10.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Resin 3.1"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Jetty 6.1.x"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Sun Application Server 9 (J2EE 1.5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "GlassFish (J2EE 5)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JBoss 4.2.x - 5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Websphere 7.0. and higher"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Geronimo 2.0 and higher"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Supported Browsers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Internet Explorer 6.0 - 8.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Firefox 2.0 - 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Opera 8.5 - 9.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Safari 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Google Chrome"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This list is composed from user reports of compatibility. We assume that this list is incomplete, so the absence of your environment from the list does not necessarily mean that it is incompatible with RichFaces."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "We appreciate your feedback about compatible platforms and browsers that are not listed here. This helps us keep the list up-to-date."
+msgstr ""
+
More information about the jboss-cvs-commits
mailing list