[jboss-cvs] JBossAS SVN: r104511 - projects/docs/enterprise/5.0/RichFaces/de-DE.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu May 6 02:08:39 EDT 2010
Author: xhuang at jboss.com
Date: 2010-05-06 02:08:38 -0400 (Thu, 06 May 2010)
New Revision: 104511
Modified:
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/Getting_Started.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Introduction.po
projects/docs/enterprise/5.0/RichFaces/de-DE/Revision_History.po
Log:
update po
Modified: projects/docs/enterprise/5.0/RichFaces/de-DE/Architecture_Overview.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Architecture_Overview.po 2010-05-06 06:03:45 UTC (rev 104510)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Architecture_Overview.po 2010-05-06 06:08:38 UTC (rev 104511)
@@ -1,10 +1,10 @@
-#
+#
# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"POT-Creation-Date: 2010-05-06T06:01:37\n"
"PO-Revision-Date: 2009-12-10T05:38:02\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -24,7 +24,13 @@
#. 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."
+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
@@ -39,7 +45,12 @@
#. 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."
+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
@@ -49,7 +60,9 @@
#. Tag: para
#, no-c-format
-msgid "The following figure lists several important elements of the RichFaces Framework."
+msgid ""
+"The following figure lists several important elements of the RichFaces "
+"Framework."
msgstr ""
#. Tag: title
@@ -64,7 +77,12 @@
#. 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."
+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
@@ -74,17 +92,27 @@
#. 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."
+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."
+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."
+msgid ""
+"The diagram that follows illustrates the process of requesting a resource."
msgstr ""
#. Tag: title
@@ -99,7 +127,12 @@
#. 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>."
+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
@@ -109,7 +142,11 @@
#. 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."
+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
@@ -119,7 +156,11 @@
#. 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."
+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
@@ -129,7 +170,10 @@
#. 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."
+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
@@ -144,7 +188,10 @@
#. 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:"
+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
@@ -184,7 +231,9 @@
#. Tag: para
#, no-c-format
-msgid "Therefore, you can create your own handler that is called when timeouts, internal server errors, etc. occur."
+msgid ""
+"Therefore, you can create your own handler that is called when timeouts, "
+"internal server errors, etc. occur."
msgstr ""
#. Tag: title
@@ -194,7 +243,9 @@
#. 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."
+msgid ""
+"You can also redefine the <literal>onExpired</literal> framework method that "
+"is called on the <literal>SessionExpiration</literal> event."
msgstr ""
#. Tag: para
@@ -224,12 +275,17 @@
#. Tag: para
#, no-c-format
-msgid "a default message for display in the event of <literal>SessionExpiration</literal>."
+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:"
+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
@@ -244,22 +300,45 @@
#. 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."
+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."
+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."
+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."
+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
@@ -269,7 +348,8 @@
#. Tag: para
#, no-c-format
-msgid "RichFaces <emphasis>skinnability</emphasis> is designed for use alongside:"
+msgid ""
+"RichFaces <emphasis>skinnability</emphasis> is designed for use alongside:"
msgstr ""
#. Tag: para
@@ -289,7 +369,9 @@
#. Tag: para
#, no-c-format
-msgid "A component's color scheme can be applied to its elements using any of three style classes:"
+msgid ""
+"A component's color scheme can be applied to its elements using any of three "
+"style classes:"
msgstr ""
#. Tag: title
@@ -299,7 +381,11 @@
#. 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."
+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
@@ -309,7 +395,11 @@
#. 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."
+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
@@ -319,7 +409,11 @@
#. 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."
+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
@@ -329,32 +423,48 @@
#. Tag: para
#, no-c-format
-msgid "The following is an example of a simple <emphasis>panel</emphasis> component:"
+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:"
+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:"
+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>"
+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>"
+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."
+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
@@ -364,7 +474,10 @@
#. 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:"
+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
@@ -374,7 +487,9 @@
#. Tag: para
#, no-c-format
-msgid "RichFaces provides eight predefined skin parameters (skins) at the simplest level of common customization:"
+msgid ""
+"RichFaces provides eight predefined skin parameters (skins) at the simplest "
+"level of common customization:"
msgstr ""
#. Tag: para
@@ -424,12 +539,16 @@
#. 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."
+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:"
+msgid ""
+"The following table shows the values for each parameter in the "
+"<literal>blueSky</literal> skin:"
msgstr ""
#. Tag: title
@@ -724,7 +843,10 @@
#. 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."
+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
@@ -739,17 +861,30 @@
#. 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."
+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:"
+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."
+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
@@ -759,42 +894,66 @@
#. 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>"
+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:"
+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:"
+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:"
+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:"
+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>."
+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>."
+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>."
+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
@@ -804,7 +963,9 @@
#. Tag: para
#, no-c-format
-msgid "You can change skins during runtime by defining the following EL-expression in your <filename>web.xml</filename>."
+msgid ""
+"You can change skins during runtime by defining the following EL-expression "
+"in your <filename>web.xml</filename>."
msgstr ""
#. Tag: para
@@ -814,12 +975,16 @@
#. 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>:"
+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:"
+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
@@ -834,17 +999,32 @@
#. 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."
+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>."
+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:"
+msgid ""
+"The <emphasis>Basic</emphasis> level provides customization for only basic "
+"style properties. Basic skinning is applied to the following browsers:"
msgstr ""
#. Tag: para
@@ -854,7 +1034,10 @@
#. 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>)"
+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
@@ -869,7 +1052,11 @@
#. 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:"
+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
@@ -929,7 +1116,9 @@
#. Tag: para
#, no-c-format
-msgid "<literal>a</literal> (together with the <literal>a:hover</literal>, <literal>a:visited</literal> pseudo-elements)"
+msgid ""
+"<literal>a</literal> (together with the <literal>a:hover</literal>, "
+"<literal>a:visited</literal> pseudo-elements)"
msgstr ""
#. Tag: para
@@ -939,37 +1128,61 @@
#. 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."
+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."
+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:"
+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:"
+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:"
+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>"
+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."
+msgid ""
+"The predefined rich CSS classes provided can be used as classes for both "
+"basic and complex HTML elements."
msgstr ""
#. Tag: para
@@ -979,7 +1192,10 @@
#. 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."
+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
@@ -989,7 +1205,9 @@
#. Tag: title
#, no-c-format
-msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex and legend"
+msgid ""
+"HTML Element Skin Bindings for input, select, textarea, button, keygen, "
+"isindex and legend"
msgstr ""
#. Tag: entry
@@ -1054,7 +1272,9 @@
#. Tag: title
#, no-c-format
-msgid "Rich Elements Skin Bindings for .rich-input, .rich-select, .rich-textarea, .rich-keygen, .rich-isindex, .rich-link"
+msgid ""
+"Rich Elements Skin Bindings for .rich-input, .rich-select, .rich-textarea, ."
+"rich-keygen, .rich-isindex, .rich-link"
msgstr ""
#. Tag: title
@@ -1179,7 +1399,9 @@
#. Tag: title
#, no-c-format
-msgid "Rich Element Skin Bindings for .rich-button, .rich-button-disabled, .rich-button-over"
+msgid ""
+"Rich Element Skin Bindings for .rich-button, .rich-button-disabled, .rich-"
+"button-over"
msgstr ""
#. Tag: entry
@@ -1274,7 +1496,9 @@
#. Tag: title
#, no-c-format
-msgid "HTML Element Skin Bindings for input, select, textarea, button, keygen, isindex"
+msgid ""
+"HTML Element Skin Bindings for input, select, textarea, button, keygen, "
+"isindex"
msgstr ""
#. Tag: title
@@ -1299,12 +1523,17 @@
#. 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]"
+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"
+msgid ""
+"HTML Element Skin Bindings for *|button[disabled], .rich-container *|button"
+"[disabled], .rich-button-disabled"
msgstr ""
#. Tag: entry
@@ -1314,12 +1543,24 @@
#. 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"
+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]"
+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
@@ -1334,22 +1575,30 @@
#. Tag: title
#, no-c-format
-msgid "HTML Element Skin Bindings for textarea[type=textarea], input[type=text], input[type=password], select"
+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]"
+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]"
+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:"
+msgid ""
+"The basic skinning level can fail if the <literal>ajaxPortlet</literal> is "
+"configured as follows:"
msgstr ""
#. Tag: title
@@ -1359,52 +1608,78 @@
#. 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."
+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."
+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:"
+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."
+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."
+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:"
+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."
+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>."
+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:"
+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>."
+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
@@ -1414,27 +1689,46 @@
#. 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."
+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:"
+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:"
+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."
+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:"
+msgid ""
+"CSS selectors with identical skin properties can be included in a comma-"
+"separated list:"
msgstr ""
#. Tag: title
@@ -1444,12 +1738,23 @@
#. 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."
+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."
+msgid ""
+"First, use Maven to create a template for your new skin. (You can find more "
+"information about configuring Maven for RichFaces in the <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
@@ -1459,7 +1764,9 @@
#. Tag: para
#, no-c-format
-msgid "<varname>archetypeVersion</varname> — indicates the RichFaces version; for example, <literal>3.3.1.GA</literal>"
+msgid ""
+"<varname>archetypeVersion</varname> — indicates the RichFaces version; for "
+"example, <literal>3.3.1.GA</literal>"
msgstr ""
#. Tag: para
@@ -1474,12 +1781,16 @@
#. 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>"
+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."
+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
@@ -1489,7 +1800,9 @@
#. 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.)"
+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
@@ -1499,7 +1812,9 @@
#. 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."
+msgid ""
+"<varname>package</varname> — the base package of the skin. By default, the "
+"project's <literal>groupId</literal> is used."
msgstr ""
#. Tag: para
@@ -1514,112 +1829,191 @@
#. 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\" />."
+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:"
+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>"
+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>"
+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\\\""
+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>"
+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:"
+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."
+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."
+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\" />."
+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."
+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>"
+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>"
+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>."
+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>."
+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:"
+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:"
+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."
+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):"
+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:"
+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."
+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>."
+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
@@ -1629,17 +2023,24 @@
#. 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."
+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:"
+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."
+msgid ""
+"You can now browse the <filename>P-n-S</filename> directory to view the "
+"files and folders created."
msgstr ""
#. Tag: para
@@ -1649,22 +2050,33 @@
#. 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."
+msgid ""
+"As mentioned in the previous section, <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."
+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:"
+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>;"
+msgid ""
+"Recolor the background of the current day in the <literal><rich:"
+"calendar></literal>;"
msgstr ""
#. Tag: para
@@ -1674,52 +2086,80 @@
#. 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>."
+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."
+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:"
+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."
+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>."
+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:"
+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."
+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:"
+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:"
+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:"
+msgid ""
+"The results of each alteration to the skin are shown in the figures that "
+"follow:"
msgstr ""
#. Tag: title
@@ -1734,7 +2174,17 @@
#. 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:"
+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
@@ -1749,12 +2199,21 @@
#. 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."
+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."
+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
@@ -1764,7 +2223,16 @@
#. 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."
+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
@@ -1774,37 +2242,53 @@
#. Tag: para
#, no-c-format
-msgid "Register the State Navigation Handler and the EL Resolver in your <filename>faces-config.xml</filename> file:"
+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>:"
+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>:"
+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:"
+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."
+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:"
+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>."
+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
@@ -1814,16 +2298,29 @@
#. 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."
+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:"
+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."
+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 ""
-
Modified: projects/docs/enterprise/5.0/RichFaces/de-DE/Author_Group.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Author_Group.po 2010-05-06 06:03:45 UTC (rev 104510)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Author_Group.po 2010-05-06 06:08:38 UTC (rev 104511)
@@ -1,10 +1,10 @@
-#
+#
# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"POT-Creation-Date: 2010-05-06T06:01:38\n"
"PO-Revision-Date: 2009-12-10T05:38:02\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -12,3 +12,7 @@
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+#. Tag: firstname
+#, no-c-format
+msgid "Red Hat Documentation Group"
+msgstr ""
Modified: projects/docs/enterprise/5.0/RichFaces/de-DE/Getting_Started.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Getting_Started.po 2010-05-06 06:03:45 UTC (rev 104510)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Getting_Started.po 2010-05-06 06:08:38 UTC (rev 104511)
@@ -1,10 +1,10 @@
-#
+#
# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"POT-Creation-Date: 2010-05-06T06:01:38\n"
"PO-Revision-Date: 2009-12-10T05:38:02\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -19,7 +19,12 @@
#. 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."
+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
@@ -29,12 +34,17 @@
#. 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."
+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."
+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
@@ -44,12 +54,20 @@
#. 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."
+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:"
+msgid ""
+"A JSF application with RichFaces assumes that the following JARs are "
+"available in the project:"
msgstr ""
#. Tag: para
@@ -84,12 +102,17 @@
#. 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>:"
+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\" />."
+msgid ""
+"For more information about RichFaces skins, read <xref linkend=\"Skinnability"
+"\" />."
msgstr ""
#. Tag: para
@@ -104,7 +127,11 @@
#. 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>:"
+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
@@ -114,7 +141,9 @@
#. Tag: para
#, no-c-format
-msgid "To register the <literal>user</literal> bean, add the following to the <filename>faces-config.xml</filename> file:"
+msgid ""
+"To register the <literal>user</literal> bean, add the following to the "
+"<filename>faces-config.xml</filename> file:"
msgstr ""
#. Tag: title
@@ -124,22 +153,37 @@
#. 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:"
+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."
+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:"
+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>"
+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
@@ -154,6 +198,8 @@
#. 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. -->"
+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."
msgstr ""
-
Modified: projects/docs/enterprise/5.0/RichFaces/de-DE/Introduction.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Introduction.po 2010-05-06 06:03:45 UTC (rev 104510)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Introduction.po 2010-05-06 06:08:38 UTC (rev 104511)
@@ -1,10 +1,10 @@
-#
+#
# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"POT-Creation-Date: 2010-05-06T06:01:38\n"
"PO-Revision-Date: 2009-12-10T05:38:02\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -19,12 +19,19 @@
#. Tag: para
#, no-c-format
-msgid "RichFaces is an open source framework that adds AJAX capability into existing JSF applications without resorting to JavaScript."
+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."
+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
@@ -34,46 +41,94 @@
#. 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."
+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. -->"
+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."
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."
+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."
+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."
+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."
+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."
+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."
+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."
+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 ""
-
Modified: projects/docs/enterprise/5.0/RichFaces/de-DE/Revision_History.po
===================================================================
--- projects/docs/enterprise/5.0/RichFaces/de-DE/Revision_History.po 2010-05-06 06:03:45 UTC (rev 104510)
+++ projects/docs/enterprise/5.0/RichFaces/de-DE/Revision_History.po 2010-05-06 06:08:38 UTC (rev 104511)
@@ -1,10 +1,10 @@
-#
+#
# AUTHOR <EMAIL at ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2009-12-10T05:38:02\n"
+"POT-Creation-Date: 2010-05-06T06:01:39\n"
"PO-Revision-Date: 2009-12-10T05:38:02\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
@@ -17,8 +17,17 @@
msgid "Revision History"
msgstr ""
+#. Tag: firstname
+#, no-c-format
+msgid "Laura"
+msgstr ""
+
+#. Tag: surname
+#, no-c-format
+msgid "Bailey"
+msgstr ""
+
#. Tag: member
#, no-c-format
msgid "JIRA corrections."
msgstr ""
-
More information about the jboss-cvs-commits
mailing list