Author: essaidetest Date: 2009-10-18 12:47:04 -0400 (Sun, 18 Oct 2009) New Revision: 11604 Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Hsearch.po branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po Log: Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Hsearch.po =================================================================== --- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Hsearch.po 2009-10-18 09:24:03 UTC (rev 11603) +++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/Hsearch.po 2009-10-18 16:47:04 UTC (rev 11604) @@ -6,8 +6,8 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2009-06-11 18:45+0000\n" -"PO-Revision-Date: 2008-04-04 01:24+0000\n" -"Last-Translator: Automatically generated\n" +"PO-Revision-Date: 2009-10-18 18:46+0100\n" +"Last-Translator: P.J <essaidetest(a)yahoo.fr&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -17,69 +17,49 @@ #: Hsearch.xml:5 #, no-c-format msgid "Hibernate Search" -msgstr "" +msgstr "Hibernate Search" #. Tag: title #: Hsearch.xml:8 #, no-c-format msgid "Introduction" -msgstr "" +msgstr "Introduction" #. Tag: para #: Hsearch.xml:10 #, no-c-format -msgid "" -"Full text search engines like Apache Lucene™ are a very powerful technology " -"that bring full text and efficient queries to applications. Hibernate " -"Search, which uses Apache Lucene under the covers, indexes your domain model " -"with the addition of a few annotations, takes care of the database / index " -"synchronization and returns regular managed objects that are matched by full " -"text queries. Keep in mind, thought, that there are mismatches that arise " -"when dealing with an object domain model over a text index (keeping the " -"index up to date, mismatch between the index structure and the domain model, " -"and querying mismatch). But the benefits of speed and efficiency far " -"outweigh these limitations." -msgstr "" +msgid "Full text search engines like Apache Lucene™ are a very powerful technology that bring full text and efficient queries to applications. Hibernate Search, which uses Apache Lucene under the covers, indexes your domain model with the addition of a few annotations, takes care of the database / index synchronization and returns regular managed objects that are matched by full text queries. Keep in mind, thought, that there are mismatches that arise when dealing with an object domain model over a text index (keeping the index up to date, mismatch between the index structure and the domain model, and querying mismatch). But the benefits of speed and efficiency far outweigh these limitations." +msgstr "Les moteurs de recherches plein texte comme Apache Lucene™ sont une technologie très puissante qui apporte la recherche plain texte et l'efficacité des requêtes dans les applications. Hibernate Search qui utilise Apache Lucene soujacent indexe votre modèle du domaine avec quelques annotations additionnelles, prends garde à la synchronisation base de données / indexes et retourne des objets opérationnels qui correspondent aux requêtes de recherche plain texte. Gardez à l'esprit qu'il peut avoir des erreurs qui apparaisssent avec un modèle de domaine objet par dessus un index de textes (conserver l'index à jours, erreur entre la structure de l'index et le modèle du domaine, et erreurs dans les requêtes). Mais les avantages de la vitesse et de l'efficacité va au delà de ces limitations." #. Tag: para #: Hsearch.xml:21 #, no-c-format -msgid "" -"Hibernate Search has been designed to integrate nicely and as naturally as " -"possible with JPA and Hibernate. As a natural extension, JBoss Seam provides " -"an Hibernate Search integration." -msgstr "" +msgid "Hibernate Search has been designed to integrate nicely and as naturally as possible with JPA and Hibernate. As a natural extension, JBoss Seam provides an Hibernate Search integration." +msgstr "Hibernate Search a été conçu pour s'intégrer facilement et naturellement que possible avec JPA et Hibernate. Comme une extension naturelle, JBoss Seam fourni une intégration avec Hibernate Search." #. Tag: para #: Hsearch.xml:25 #, no-c-format -msgid "" -"Please refer to the <ulink url=\"http://www.hibernate.org/hib_docs/search/" -"reference/en/html_single/\">Hibernate Search documentation</ulink> for " -"information specific to the Hibernate Search project." -msgstr "" +msgid "Please refer to the <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_sin... Search documentation</ulink> for information specific to the Hibernate Search project." +msgstr "Merci de vous référer à <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_sin... Search documentation</ulink> pour plus d'information spécifique sur le projet Hibernate Search." #. Tag: title #: Hsearch.xml:33 #, no-c-format msgid "Configuration" -msgstr "" +msgstr "La configuration" #. Tag: para #: Hsearch.xml:35 #, no-c-format -msgid "" -"Hibernate Search is configured either in the <filename>META-INF/persistence." -"xml</filename> or <filename>hibernate.cfg.xml</filename> file." -msgstr "" +msgid "Hibernate Search is configured either in the <filename>META-INF/persistence.xml</filename> or <filename>hibernate.cfg.xml</filename> file." +msgstr "Hibernate Search est configuré aussi bien dans le fichier <filename>META-INF/persistence.xml</filename> que dans le fichier <filename>hibernate.cfg.xml</filename>." #. Tag: para #: Hsearch.xml:39 #, no-c-format -msgid "" -"Hibernate Search configuration has sensible defaults for most configuration " -"parameters. Here is a minimal persistence unit configuration to get started." -msgstr "" +msgid "Hibernate Search configuration has sensible defaults for most configuration parameters. Here is a minimal persistence unit configuration to get started." +msgstr "La configuration d'Hibernate Search configuration est par défaut judicieuse pour la plus part des paramètre de configuration. Ici n configuration d'une unité de persistance minimale pour démarrer." #. Tag: programlisting #: Hsearch.xml:43 @@ -98,15 +78,24 @@ " </properties>\n" "</persistence-unit>]]>" msgstr "" +"<![CDATA[<persistence-unit name=\"sample\">\n" +" <jta-data-source>java:/DefaultDS</jta-data-source>\n" +" <properties>\n" +" [...]\n" +" <!-- use a file system based index -->\n" +" <property name=\"hibernate.search.default.directory_provider\" \n" +" value=\"org.hibernate.search.store.FSDirectoryProvider\"/>\n" +" <!-- directory where the indexes will be stored -->\n" +" <property name=\"hibernate.search.default.indexBase\" \n" +" value=\"/Users/prod/apps/dvdstore/dvdindexes\"/>\n" +" </properties>\n" +"</persistence-unit>]]>" #. Tag: para #: Hsearch.xml:45 #, no-c-format -msgid "" -"If you plan to target Hibernate Annotations or EntityManager 3.2.x (embedded " -"into JBoss AS 4.2.x and later), you also need to configure the appropriate " -"event listeners." -msgstr "" +msgid "If you plan to target Hibernate Annotations or EntityManager 3.2.x (embedded into JBoss AS 4.2.x and later), you also need to configure the appropriate event listeners." +msgstr "Si vous plannifier de cibler Hibernate Annotations ou EntityManager 3.2.x (embarqué dans JBoss AS 4.2.x et suppérieur), vous allez avoir besoin de configurer les écouteurs d'évènement appropriés." #. Tag: programlisting #: Hsearch.xml:49 @@ -124,97 +113,95 @@ " value=\"/Users/prod/apps/dvdstore/dvdindexes\"/>\n" "\n" " <property name=\"hibernate.ejb.event.post-insert\" \n" -" value=\"org.hibernate.search.event.FullTextIndexEventListener" -"\"/>\n" +" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n" " <property name=\"hibernate.ejb.event.post-update\" \n" -" value=\"org.hibernate.search.event.FullTextIndexEventListener" -"\"/>\n" +" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n" " <property name=\"hibernate.ejb.event.post-delete\" \n" -" value=\"org.hibernate.search.event.FullTextIndexEventListener" -"\"/>\n" +" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n" " \n" " </properties>\n" "</persistence-unit>]]>" msgstr "" +"<![CDATA[<persistence-unit name=\"sample\">\n" +" <jta-data-source>java:/DefaultDS</jta-data-source>\n" +" <properties>\n" +" [...]\n" +" <!-- use a file system based index -->\n" +" <property name=\"hibernate.search.default.directory_provider\" \n" +" value=\"org.hibernate.search.store.FSDirectoryProvider\"/>\n" +" <!-- directory where the indexes will be stored -->\n" +" <property name=\"hibernate.search.default.indexBase\" \n" +" value=\"/Users/prod/apps/dvdstore/dvdindexes\"/>\n" +"\n" +" <property name=\"hibernate.ejb.event.post-insert\" \n" +" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n" +" <property name=\"hibernate.ejb.event.post-update\" \n" +" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n" +" <property name=\"hibernate.ejb.event.post-delete\" \n" +" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n" +" \n" +" </properties>\n" +"</persistence-unit>]]>" #. Tag: para #: Hsearch.xml:52 #, no-c-format -msgid "" -"It is not longer necessary the register the event listeners if Hibernate " -"Annotations or EntityManager 3.3.x are used. When using Hibernate Search 3.1." -"x more eventlisteners are needed, but these are registered automatically by " -"Hibernate Annotations; refer to the Hibernate Search reference for " -"configuring it without EntityManager and Annotations." -msgstr "" +msgid "It is not longer necessary the register the event listeners if Hibernate Annotations or EntityManager 3.3.x are used. When using Hibernate Search 3.1.x more eventlisteners are needed, but these are registered automatically by Hibernate Annotations; refer to the Hibernate Search reference for configuring it without EntityManager and Annotations." +msgstr "Il n'est plus nécéssaire d'enregistrer les écouteurs d'évènements si Hibernate Annotations ou EntityManager 3.3.x sont utilisés. Quand on utilise Hibernate Search 3.1.x quelques écouteurs d'évènements sont nécéssaire, mais ils sont automatiquement enregistrés par Hibernate Annotations; référeez vous au guide d'Hibernate Search pour sa configuration sans EntityManager et les Annotations." #. Tag: para #: Hsearch.xml:60 #, no-c-format -msgid "" -"In addition to the configuration file, the following jars have to be " -"deployed:" -msgstr "" +msgid "In addition to the configuration file, the following jars have to be deployed:" +msgstr "En plus du fichier de configuration, les jars suivants doivent être déployés:" #. Tag: para #: Hsearch.xml:65 #, no-c-format msgid "hibernate-search.jar" -msgstr "" +msgstr "hibernate-search.jar" #. Tag: para #: Hsearch.xml:69 #, no-c-format msgid "hibernate-commons-annotations.jar" -msgstr "" +msgstr "hibernate-commons-annotations.jar" #. Tag: para #: Hsearch.xml:73 #, no-c-format msgid "lucene-core.jar" -msgstr "" +msgstr "lucene-core.jar" #. Tag: para #: Hsearch.xml:78 #, no-c-format -msgid "" -"If you deploy those in a EAR, don't forget to update <filename>application." -"xml</filename>" -msgstr "" +msgid "If you deploy those in a EAR, don't forget to update <filename>application.xml</filename>" +msgstr "Si vous déployez ceux là dans un EAR, n'oubliez pas de mettre à jours <filename>application.xml</filename>" #. Tag: title #: Hsearch.xml:84 #, no-c-format msgid "Usage" -msgstr "" +msgstr "Utilisation" #. Tag: para #: Hsearch.xml:86 #, no-c-format -msgid "" -"Hibernate Search uses annotations to map entities to a Lucene index, check " -"the <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/" -"html_single/\">reference documentation</ulink> for more informations." -msgstr "" +msgid "Hibernate Search uses annotations to map entities to a Lucene index, check the <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_sin... documentation</ulink> for more informations." +msgstr "Hibernate Search utlise les annotations pour faire correspondre les entités à l'index de Lucene, vérifiez <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_sin... documentation de référence </ulink> pour plus d'informations." #. Tag: para #: Hsearch.xml:91 #, no-c-format -msgid "" -"Hibernate Search is fully integrated with the API and semantic of JPA / " -"Hibernate. Switching from a HQL or Criteria based query requires just a few " -"lines of code. The main API the application interacts with is the " -"<classname>FullTextSession</classname> API (subclass of Hibernate's " -"<classname>Session</classname>)." -msgstr "" +msgid "Hibernate Search is fully integrated with the API and semantic of JPA / Hibernate. Switching from a HQL or Criteria based query requires just a few lines of code. The main API the application interacts with is the <classname>FullTextSession</classname> API (subclass of Hibernate's <classname>Session</classname>)." +msgstr "Hibernate Search est pleinement intégré avec les API et la sémentique JPA / Hibernate. Le basculement des requêtes HQL ou Criteria nécéssite juste quelques lignes de codes. L'API principale à intéragir avec est l'API <classname>FullTextSession</classname> (sousclasse de <classname>Session</classname> d'Hibernate )." #. Tag: para #: Hsearch.xml:97 #, no-c-format -msgid "" -"When Hibernate Search is present, JBoss Seam injects a " -"<classname>FullTextSession</classname>." -msgstr "" +msgid "When Hibernate Search is present, JBoss Seam injects a <classname>FullTextSession</classname>." +msgstr "Quand Hibernate Search est présent, JBoss Seam injecte un <classname>FullTextSession</classname>." #. Tag: programlisting #: Hsearch.xml:100 @@ -228,8 +215,7 @@ "\n" " public void search(String searchString) {\n" " org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n" -" org.hibernate.Query query session.createFullTextQuery(luceneQuery, " -"Product.class);\n" +" org.hibernate.Query query session.createFullTextQuery(luceneQuery, Product.class);\n" " searchResults = query\n" " .setMaxResults(pageSize + 1)\n" " .setFirstResult(pageSize * currentPage)\n" @@ -238,21 +224,34 @@ " [...]\n" "}]]>" msgstr "" +"<![CDATA[@Stateful\n" +"@Name(\"search\")\n" +"public class FullTextSearchAction implements FullTextSearch, Serializable {\n" +"\n" +" @In FullTextSession session;\n" +"\n" +" public void search(String searchString) {\n" +" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n" +" org.hibernate.Query query session.createFullTextQuery(luceneQuery, Product.class);\n" +" searchResults = query\n" +" .setMaxResults(pageSize + 1)\n" +" .setFirstResult(pageSize * currentPage)\n" +" .list();\n" +" }\n" +" [...]\n" +"}]]>" #. Tag: para #: Hsearch.xml:103 #, no-c-format -msgid "" -"<classname>FullTextSession</classname> extends <classname>org.hibernate." -"Session</classname> so that it can be used as a regular Hibernate Session" -msgstr "" +msgid "<classname>FullTextSession</classname> extends <classname>org.hibernate.Session</classname> so that it can be used as a regular Hibernate Session" +msgstr "<classname>FullTextSession</classname> étend <classname>org.hibernate.Session</classname> ainsi il peut être utilisé avec une Hibernate Session habituelle" #. Tag: para #: Hsearch.xml:108 #, no-c-format -msgid "" -"If the Java Persistence API is used, a smoother integration is proposed." -msgstr "" +msgid "If the Java Persistence API is used, a smoother integration is proposed." +msgstr "Si l'API de Persistence de Java est utilisée, une intégration en douceur est proposée." #. Tag: programlisting #: Hsearch.xml:111 @@ -266,8 +265,7 @@ "\n" " public void search(String searchString) {\n" " org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n" -" javax.persistence.Query query = em.createFullTextQuery(luceneQuery, " -"Product.class);\n" +" javax.persistence.Query query = em.createFullTextQuery(luceneQuery, Product.class);\n" " searchResults = query\n" " .setMaxResults(pageSize + 1)\n" " .setFirstResult(pageSize * currentPage)\n" @@ -276,30 +274,34 @@ " [...]\n" "}]]>" msgstr "" +"<![CDATA[@Stateful\n" +"@Name(\"search\")\n" +"public class FullTextSearchAction implements FullTextSearch, Serializable {\n" +" \n" +" @In FullTextEntityManager em;\n" +"\n" +" public void search(String searchString) {\n" +" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n" +" javax.persistence.Query query = em.createFullTextQuery(luceneQuery, Product.class);\n" +" searchResults = query\n" +" .setMaxResults(pageSize + 1)\n" +" .setFirstResult(pageSize * currentPage)\n" +" .getResultList();\n" +" }\n" +" [...]\n" +"}]]>" #. Tag: para #: Hsearch.xml:113 #, no-c-format -msgid "" -"When Hibernate Search is present, a <classname>FulltextEntityManager</" -"classname> is injected. <classname>FullTextEntityManager</classname> extends " -"<classname>EntityManager</classname> with search specific methods, the same " -"way <classname>FullTextSession</classname> extends <classname>Session</" -"classname>." -msgstr "" +msgid "When Hibernate Search is present, a <classname>FulltextEntityManager</classname> is injected. <classname>FullTextEntityManager</classname> extends <classname>EntityManager</classname> with search specific methods, the same way <classname>FullTextSession</classname> extends <classname>Session</classname>." +msgstr "Quand Hibernate Search est présent, un <classname>FulltextEntityManager</classname> est injecté. <classname>FullTextEntityManager</classname> étends <classname>EntityManager</classname> avec des méthodes de recherche spécifique, de la même façon que <classname>FullTextSession</classname> étends <classname>Session</classname>." #. Tag: para #: Hsearch.xml:120 #, no-c-format -msgid "" -"When an EJB 3.0 Session or Message Driven Bean injection is used (i.e. via " -"the @PersistenceContext annotation), it is not possible to replace the " -"<classname>EntityManager</classname> interface by the " -"<classname>FullTextEntityManager</classname> interface in the declaration " -"statement. However, the implementation injected will be a " -"<classname>FullTextEntityManager</classname> implementation: downcasting is " -"then possible." -msgstr "" +msgid "When an EJB 3.0 Session or Message Driven Bean injection is used (i.e. via the @PersistenceContext annotation), it is not possible to replace the <classname>EntityManager</classname> interface by the <classname>FullTextEntityManager</classname> interface in the declaration statement. However, the implementation injected will be a <classname>FullTextEntityManager</classname> implementation: downcasting is then possible." +msgstr "Quand une Session EJB3.0 ou une injection de Message Driven Bean est utilisé (par exemple via l'annotation @PersistenceContext), il ets possible de remplacer l'interface de <classname>EntityManager</classname> par l'interface de <classname>FullTextEntityManager</classname> dans la partie déclaration. Cependant, l'implémentation injectée sera une implémentation de <classname>FullTextEntityManager</classname>: la conversion est ensuite possible." #. Tag: programlisting #: Hsearch.xml:128 @@ -314,8 +316,7 @@ " public void search(String searchString) {\n" " org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n" " FullTextEntityManager ftEm = (FullTextEntityManager) em;\n" -" javax.persistence.Query query = ftEm.createFullTextQuery(luceneQuery, " -"Product.class);\n" +" javax.persistence.Query query = ftEm.createFullTextQuery(luceneQuery, Product.class);\n" " searchResults = query\n" " .setMaxResults(pageSize + 1)\n" " .setFirstResult(pageSize * currentPage)\n" @@ -324,19 +325,33 @@ " [...]\n" "}]]>" msgstr "" +"<![CDATA[@Stateful\n" +"@Name(\"search\")\n" +"public class FullTextSearchAction implements FullTextSearch, Serializable {\n" +" \n" +" @PersistenceContext EntityManager em;\n" +"\n" +" public void search(String searchString) {\n" +" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n" +" FullTextEntityManager ftEm = (FullTextEntityManager) em;\n" +" javax.persistence.Query query = ftEm.createFullTextQuery(luceneQuery, Product.class);\n" +" searchResults = query\n" +" .setMaxResults(pageSize + 1)\n" +" .setFirstResult(pageSize * currentPage)\n" +" .getResultList();\n" +" }\n" +" [...]\n" +"}]]>" #. Tag: para #: Hsearch.xml:133 #, no-c-format -msgid "" -"For people accustomed to Hibernate Search out of Seam, note that using " -"<methodname>Search.getFullTextSession</methodname> is not necessary." -msgstr "" +msgid "For people accustomed to Hibernate Search out of Seam, note that using <methodname>Search.getFullTextSession</methodname> is not necessary." +msgstr "Pour les personnes abituées à Hibernate Search sans Seam, notez que l'utilisation de <methodname>Search.getFullTextSession</methodname> n'est pas nécéssaire." #. Tag: para #: Hsearch.xml:138 #, no-c-format -msgid "" -"Check the DVDStore or the blog examples of the JBoss Seam distribution for a " -"concrete use of Hibernate Search." -msgstr "" +msgid "Check the DVDStore or the blog examples of the JBoss Seam distribution for a concrete use of Hibernate Search." +msgstr "Voyez le DVDStore dans les exemples de blog de la distribution de JBoss Seam pour une utilisation concrète de Hibernate Search." + Modified: branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po =================================================================== --- branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po 2009-10-18 09:24:03 UTC (rev 11603) +++ branches/community/Seam_2_2/doc/Seam_Reference_Guide/fr-FR/I18n.po 2009-10-18 16:47:04 UTC (rev 11604) @@ -6,8 +6,8 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2009-06-25 15:02+0000\n" -"PO-Revision-Date: 2008-04-04 01:24+0000\n" -"Last-Translator: Automatically generated\n" +"PO-Revision-Date: 2009-10-18 18:46+0100\n" +"Last-Translator: P.J <essaidetest(a)yahoo.fr&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -17,173 +17,120 @@ #: I18n.xml:5 #, no-c-format msgid "Internationalization, localization and themes" -msgstr "" +msgstr "Internationnalisation, les langues locales et les thèmes" #. Tag: para #: I18n.xml:7 #, no-c-format -msgid "" -"Seam makes it easy to build internationalized applications. First, let's " -"walk through all the stages needed to internationalize and localize your " -"app. Then we'll take a look at the components Seam bundles." -msgstr "" +msgid "Seam makes it easy to build internationalized applications. First, let's walk through all the stages needed to internationalize and localize your app. Then we'll take a look at the components Seam bundles." +msgstr "Seam rend facile la construction d'applications internationnalisées? En premier, regardons toutes les étapes nécéssaires pour internationnaliser et rendre avec une langue locale votre application. Ensuite nous allons regarde les composants livrés dans Seam." #. Tag: title #: I18n.xml:14 #, no-c-format msgid "Internationalizing your app" -msgstr "" +msgstr "Internationnalisation de votre application." #. Tag: para #: I18n.xml:16 #, no-c-format -msgid "" -"A JEE application consists of many components and all of them must be " -"configured properly for your application to be localized." -msgstr "" +msgid "A JEE application consists of many components and all of them must be configured properly for your application to be localized." +msgstr "Une application JEE consisten en plusieurs composants et tous doivent être configurés de manière appropriés pour que votre application soit traduisible." #. Tag: para #: I18n.xml:21 #, no-c-format -msgid "" -"Starting at the bottom, the first step is to ensure that your database " -"server and client is using the correct character encoding for your locale. " -"Normally you'll want to use UTF-8. How to do this is outside the scope of " -"this tutorial." -msgstr "" +msgid "Starting at the bottom, the first step is to ensure that your database server and client is using the correct character encoding for your locale. Normally you'll want to use UTF-8. How to do this is outside the scope of this tutorial." +msgstr "En partant du bas, la première étape est de s'assrer que le serveur de base de données et le client utilise le bon encodage de caractères pour votre langue. Normallement, vous devriez vouloir utiliser UTF-8. Comment faire cela est hors de porté de ce tutorial." #. Tag: title #: I18n.xml:29 #, no-c-format msgid "Application server configuration" -msgstr "" +msgstr "La configuration du serveur d'application" #. Tag: para #: I18n.xml:31 #, no-c-format -msgid "" -"To ensure that the application server receives the request parameters in the " -"correct encoding from client requests you have to configure the tomcat " -"connector. If you use Tomcat or JBoss AS, add the <literal>URIEncoding=\"UTF-" -"8\"</literal> attribute to the connector configuration. For JBoss AS 4.2 " -"change <literal>${JBOSS_HOME}/server/(default)/deploy/jboss-web.deployer/" -"server.xml</literal>:" -msgstr "" +msgid "To ensure that the application server receives the request parameters in the correct encoding from client requests you have to configure the tomcat connector. If you use Tomcat or JBoss AS, add the <literal>URIEncoding=\"UTF-8\"</literal> attribute to the connector configuration. For JBoss AS 4.2 change <literal>${JBOSS_HOME}/server/(default)/deploy/jboss-web.deployer/server.xml</literal>:" +msgstr "Pour s'assurer que le serveur d'application reçoit les paramètres dans l'encodage correct depuis les requêtes client, vous devez configurer le connecteur de tomcat. Si vous utilisez Tomcat ou JBoss AS, ajoutez l'attribut <literal>URIEncoding=\"UTF-8\"</literal> à la configuration du connecteur. Pour JBoss AS 4.2, modifiez <literal>${JBOSS_HOME}/server/(default)/deploy/jboss-web.deployer/server.xml</literal>:" #. Tag: programlisting #: I18n.xml:40 #, no-c-format msgid "&lt;Connector port=\"8080\" URIEncoding=\"UTF-8\"/&gt;" -msgstr "" +msgstr "&lt;Connector port=\"8080\" URIEncoding=\"UTF-8\"/&gt;" #. Tag: para #: I18n.xml:42 #, no-c-format -msgid "" -"There is alternative which is probably better. You can tell JBoss AS that " -"the encoding for the request parameters will be taken from the request:" -msgstr "" +msgid "There is alternative which is probably better. You can tell JBoss AS that the encoding for the request parameters will be taken from the request:" +msgstr "Il ya une alternative qui est probablement meilleure. Vous pouvez dire à JBoss AS que l'encodage des paramètres des requeêtes sera prit depuis la requête:" #. Tag: programlisting #: I18n.xml:48 #, no-c-format msgid "&lt;Connector port=\"8080\" useBodyEncodingForURI=\"true\"/&gt;" -msgstr "" +msgstr "&lt;Connector port=\"8080\" useBodyEncodingForURI=\"true\"/&gt;" #. Tag: title #: I18n.xml:52 #, no-c-format msgid "Translated application strings" -msgstr "" +msgstr "Les chaines de caractères de l'application traduites" #. Tag: para #: I18n.xml:54 #, no-c-format -msgid "" -"You'll also need localized strings for all the <emphasis>messages</emphasis> " -"in your application (for example field labels on your views). First you need " -"to ensure that your resource bundle is encoded using the desired character " -"encoding. By default ASCII is used. Although ASCII is enough for many " -"languages, it doesn't provide characters for all languages." -msgstr "" +msgid "You'll also need localized strings for all the <emphasis>messages</emphasis> in your application (for example field labels on your views). First you need to ensure that your resource bundle is encoded using the desired character encoding. By default ASCII is used. Although ASCII is enough for many languages, it doesn't provide characters for all languages." +msgstr "Vous allez avoir besoin des chaines de caractères traduites pour tous les <emphasis>messages</emphasis> de votre applicatin (par exemple les labels des champsd e vos vues). En premier, vous alleza avoir besoin de vous assurer que vos fiches de ressources sont encodés avec l'encodage désiré. Par défaut, l'ASCII est utilisé. Mais l'ASCII n'est pas suffisant pour beaucoups de langues, il ne fourni pas toutes les lettres de tous les langages." #. Tag: para #: I18n.xml:63 #, no-c-format -msgid "" -"Resource bundles must be created in ASCII, or use Unicode escape codes to " -"represent Unicode characters. Since you don't compile a property file to " -"byte code, there is no way to tell the JVM which character set to use. So " -"you must use either ASCII characters or escape characters not in the ASCII " -"character set. You can represent a Unicode character in any Java file using " -"\\uXXXX, where XXXX is the hexidecimal representation of the character." -msgstr "" +msgid "Resource bundles must be created in ASCII, or use Unicode escape codes to represent Unicode characters. Since you don't compile a property file to byte code, there is no way to tell the JVM which character set to use. So you must use either ASCII characters or escape characters not in the ASCII character set. You can represent a Unicode character in any Java file using \\uXXXX, where XXXX is the hexidecimal representation of the character." +msgstr "Les fichiers de ressource doivent être créés en ASCII ou utiliser le code déspécialisé Unicode pour représenter les lettres Unicode. Sinon vous ne pourez pas compiler le fichier de propriété dans le byte-code, il n'y a pas de moyen pour indiquer à la JVM quel groupe de caractères utiliser. Donc vous devez utiliser soit les caractères ASCII soi des caractères déspécialisés qui ne sont pas dans le groupe des caractères de l'ASCII. Vous pouvez représenter un caractère Unicode dans le fichier en Java en utilisant \\uXXX, où XXX est la représentation hexadécimale de ce caractère." #. Tag: para #: I18n.xml:73 #, no-c-format -msgid "" -"You can write your translation of labels (<xref linkend=\"labels\"/>) to " -"your messages resource bundle in the native encoding and then convert the " -"content of the file into the escaped format through the tool " -"<literal>native2ascii</literal> provided in the JDK. This tool will convert " -"a file written in your native encoding to one that represents non-ASCII " -"characters as Unicode escape sequences." +msgid "You can write your translation of labels (<xref linkend=\"labels\"/>) to your messages resource bundle in the native encoding and then convert the content of the file into the escaped format through the tool <literal>native2ascii</literal> provided in the JDK. This tool will convert a file written in your native encoding to one that represents non-ASCII characters as Unicode escape sequences." msgstr "" #. Tag: para #: I18n.xml:83 #, no-c-format -msgid "" -"Usage of this tool is described <ulink url=\"http://java.sun.com/j2se/1.5.0/" -"docs/tooldocs/index.html#intl\">here for Java 5</ulink> or <ulink url=" -"\"http://java.sun.com/javase/6/docs/technotes/tools/#intl\">here for Java 6</" -"ulink>. For example, to convert a file from UTF-8:" -msgstr "" +msgid "Usage of this tool is described <ulink url=\"http://java.sun.com/j2se/1.5.0/docs/tooldocs/index.html#intl\&... for Java 5</ulink> or <ulink url=\"http://java.sun.com/javase/6/docs/technotes/tools/#intl\"... for Java 6</ulink>. For example, to convert a file from UTF-8:" +msgstr "L'utilisation de cet outil est décrit dans <ulink url=\"http://java.sun.com/j2se/1.5.0/docs/tooldocs/index.html#intl\&... pour Java 5</ulink> ou <ulink url=\"http://java.sun.com/javase/6/docs/technotes/tools/#intl\"... pour Java 6</ulink>. Par exemple, pour convertir un fichier depuis UTF-8:" #. Tag: programlisting #: I18n.xml:91 #, no-c-format -msgid "" -"<prompt>$ native2ascii -encoding UTF-8 messages_cs.properties &gt; " -"messages_cs_escaped.properties</prompt>" -msgstr "" +msgid "<prompt>$ native2ascii -encoding UTF-8 messages_cs.properties &gt; messages_cs_escaped.properties</prompt>" +msgstr "<prompt>$ native2ascii -encoding UTF-8 messages_cs.properties &gt; messages_cs_escaped.properties</prompt>" #. Tag: title #: I18n.xml:96 #, no-c-format msgid "Other encoding settings" -msgstr "" +msgstr "D'autres réglages pour l'encodage" #. Tag: para #: I18n.xml:98 #, no-c-format -msgid "" -"We need to make sure that the view displays your localized data and messages " -"using the correct character set and also any data submitted uses the correct " -"encoding." +msgid "We need to make sure that the view displays your localized data and messages using the correct character set and also any data submitted uses the correct encoding." msgstr "" #. Tag: para #: I18n.xml:104 #, no-c-format -msgid "" -"To set the display character encoding, you need to use the <literal>&lt;f:" -"view locale=\"cs_CZ\"/&gt;</literal> tag (here we tell JSF to use the Czech " -"locale). You may want to change the encoding of the xml document itself if " -"you want to embed localized strings in the xml. To do this alter the " -"encoding attribute in xml declaration <literal>&lt;?xml version=\"1.0\" " -"encoding=\"UTF-8\"?&gt;</literal> as required." +msgid "To set the display character encoding, you need to use the <literal>&lt;f:view locale=\"cs_CZ\"/&gt;</literal> tag (here we tell JSF to use the Czech locale). You may want to change the encoding of the xml document itself if you want to embed localized strings in the xml. To do this alter the encoding attribute in xml declaration <literal>&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;</literal> as required." msgstr "" #. Tag: para #: I18n.xml:114 #, no-c-format -msgid "" -"Also JSF/Facelets should submit any requests using the specified character " -"encoding, but to make sure any requests that don't specify an encoding you " -"can force the request encoding using a servlet filter. Configure this in " -"<literal>components.xml</literal>:" +msgid "Also JSF/Facelets should submit any requests using the specified character encoding, but to make sure any requests that don't specify an encoding you can force the request encoding using a servlet filter. Configure this in <literal>components.xml</literal>:" msgstr "" #. Tag: programlisting @@ -194,67 +141,50 @@ " override-client=\"true\" \n" " url-pattern=\"*.seam\" />]]>" msgstr "" +"<![CDATA[<web:character-encoding-filter encoding=\"UTF-8\" \n" +" override-client=\"true\" \n" +" url-pattern=\"*.seam\" />]]>" #. Tag: title #: I18n.xml:126 #, no-c-format msgid "Locales" -msgstr "" +msgstr "Les locales" #. Tag: para #: I18n.xml:128 #, no-c-format -msgid "" -"Each user login session has an associated instance of <literal>java.util." -"Locale</literal> (available to the application as a component named " -"<literal>locale</literal>). Under normal circumstances, you won't need to do " -"any special configuration to set the locale. Seam just delegates to JSF to " -"determine the active locale:" +msgid "Each user login session has an associated instance of <literal>java.util.Locale</literal> (available to the application as a component named <literal>locale</literal>). Under normal circumstances, you won't need to do any special configuration to set the locale. Seam just delegates to JSF to determine the active locale:" msgstr "" #. Tag: para #: I18n.xml:136 #, no-c-format -msgid "" -"If there is a locale associated with the HTTP request (the browser locale), " -"and that locale is in the list of supported locales from <literal>faces-" -"config.xml</literal>, use that locale for the rest of the session." +msgid "If there is a locale associated with the HTTP request (the browser locale), and that locale is in the list of supported locales from <literal>faces-config.xml</literal>, use that locale for the rest of the session." msgstr "" #. Tag: para #: I18n.xml:143 #, no-c-format -msgid "" -"Otherwise, if a default locale was specified in the <literal>faces-config." -"xml</literal>, use that locale for the rest of the session." +msgid "Otherwise, if a default locale was specified in the <literal>faces-config.xml</literal>, use that locale for the rest of the session." msgstr "" #. Tag: para #: I18n.xml:149 #, no-c-format msgid "Otherwise, use the default locale of the server." -msgstr "" +msgstr "Sinon, utilise la locale par défaut du serveur." #. Tag: para #: I18n.xml:153 #, no-c-format -msgid "" -"It is <emphasis>possible</emphasis> to set the locale manually via the Seam " -"configuration properties <literal> org.jboss.seam.international." -"localeSelector.language</literal>, <literal> org.jboss.seam.international." -"localeSelector.country</literal> and <literal> org.jboss.seam.international." -"localeSelector.variant</literal>, but we can't think of any good reason to " -"ever do this." +msgid "It is <emphasis>possible</emphasis> to set the locale manually via the Seam configuration properties <literal> org.jboss.seam.international.localeSelector.language</literal>, <literal> org.jboss.seam.international.localeSelector.country</literal> and <literal> org.jboss.seam.international.localeSelector.variant</literal>, but we can't think of any good reason to ever do this." msgstr "" #. Tag: para #: I18n.xml:160 #, no-c-format -msgid "" -"It is, however, useful to allow the user to set the locale manually via the " -"application user interface. Seam provides built-in functionality for " -"overriding the locale determined by the algorithm above. All you have to do " -"is add the following fragment to a form in your JSP or Facelets page:" +msgid "It is, however, useful to allow the user to set the locale manually via the application user interface. Seam provides built-in functionality for overriding the locale determined by the algorithm above. All you have to do is add the following fragment to a form in your JSP or Facelets page:" msgstr "" #. Tag: programlisting @@ -273,9 +203,7 @@ #. Tag: para #: I18n.xml:168 #, no-c-format -msgid "" -"Or, if you want a list of all supported locales from <literal> faces-config." -"xml</literal>, just use:" +msgid "Or, if you want a list of all supported locales from <literal> faces-config.xml</literal>, just use:" msgstr "" #. Tag: programlisting @@ -292,116 +220,79 @@ #. Tag: para #: I18n.xml:173 #, no-c-format -msgid "" -"When the user selects an item from the drop-down, then clicks the command " -"button, the Seam and JSF locales will be overridden for the rest of the " -"session." +msgid "When the user selects an item from the drop-down, then clicks the command button, the Seam and JSF locales will be overridden for the rest of the session." msgstr "" #. Tag: para #: I18n.xml:177 #, no-c-format -msgid "" -"The brings us to the question of where the supported locales are defined. " -"Typically, you provide a list of locales for which you have matching " -"resource bundles in the <literal>&lt;locale-config&gt;</literal> element of " -"the JSF configuration file (/META-INF/faces-config.xml). However, you have " -"learned to appreciate that Seam's component configuration mechanism is more " -"powerful than what is provided in Java EE. For that reason, you can " -"configure the supported locales, and the default locale of the server, using " -"the built-in component named <literal>org.jboss.seam.international." -"localeConfig</literal>. To use it, you first declare an XML namespace for " -"Seam's international package in the Seam component descriptor. You then " -"define the default locale and supported locales as follows:" +msgid "The brings us to the question of where the supported locales are defined. Typically, you provide a list of locales for which you have matching resource bundles in the <literal>&lt;locale-config&gt;</literal> element of the JSF configuration file (/META-INF/faces-config.xml). However, you have learned to appreciate that Seam's component configuration mechanism is more powerful than what is provided in Java EE. For that reason, you can configure the supported locales, and the default locale of the server, using the built-in component named <literal>org.jboss.seam.international.localeConfig</literal>. To use it, you first declare an XML namespace for Seam's international package in the Seam component descriptor. You then define the default locale and supported locales as follows:" msgstr "" #. Tag: programlisting #: I18n.xml:190 #, no-c-format -msgid "" -"&lt;international:locale-config default-locale=\"fr_CA\" supported-locales=" -"\"en fr_CA fr_FR\"/&gt;" +msgid "&lt;international:locale-config default-locale=\"fr_CA\" supported-locales=\"en fr_CA fr_FR\"/&gt;" msgstr "" #. Tag: para #: I18n.xml:192 #, no-c-format -msgid "" -"Naturally, if you pronounce that you support a locale, you better provide a " -"resource bundle to match it! Up next, you'll learn how to define the " -"language-specific labels." +msgid "Naturally, if you pronounce that you support a locale, you better provide a resource bundle to match it! Up next, you'll learn how to define the language-specific labels." msgstr "" #. Tag: title #: I18n.xml:198 #, no-c-format msgid "Labels" -msgstr "" +msgstr "Les labels" #. Tag: para #: I18n.xml:200 #, no-c-format -msgid "" -"JSF supports internationalization of user interface labels and descriptive " -"text via the use of <literal>&lt;f:loadBundle /&gt;</literal>. You can use " -"this approach in Seam applications. Alternatively, you can take advantage of " -"the Seam <literal> messages</literal> component to display templated labels " -"with embedded EL expressions." +msgid "JSF supports internationalization of user interface labels and descriptive text via the use of <literal>&lt;f:loadBundle /&gt;</literal>. You can use this approach in Seam applications. Alternatively, you can take advantage of the Seam <literal> messages</literal> component to display templated labels with embedded EL expressions." msgstr "" #. Tag: title #: I18n.xml:207 #, no-c-format msgid "Defining labels" -msgstr "" +msgstr "La définition des labels" #. Tag: para #: I18n.xml:209 #, no-c-format -msgid "" -"Seam provides a <literal>java.util.ResourceBundle</literal> (available to " -"the application as a <literal> org.jboss.seam.core.resourceBundle</" -"literal>). You'll need to make your internationalized labels available via " -"this special resource bundle. By default, the resource bundle used by Seam " -"is named <literal>messages</literal> and so you'll need to define your " -"labels in files named <literal> messages.properties</literal>, <literal> " -"messages_en.properties</literal>, <literal> messages_en_AU.properties</" -"literal>, etc. These files usually belong in the <literal>WEB-INF/classes</" -"literal> directory." +msgid "Seam provides a <literal>java.util.ResourceBundle</literal> (available to the application as a <literal> org.jboss.seam.core.resourceBundle</literal>). You'll need to make your internationalized labels available via this special resource bundle. By default, the resource bundle used by Seam is named <literal>messages</literal> and so you'll need to define your labels in files named <literal> messages.properties</literal>, <literal> messages_en.properties</literal>, <literal> messages_en_AU.properties</literal>, etc. These files usually belong in the <literal>WEB-INF/classes</literal> directory." msgstr "" #. Tag: para #: I18n.xml:220 #, no-c-format msgid "So, in <literal>messages_en.properties</literal>:" -msgstr "" +msgstr "Ainsi, dans <literal>messages_en.properties</literal>:" #. Tag: programlisting #: I18n.xml:222 #, no-c-format msgid "Hello=Hello" -msgstr "" +msgstr "Hello=Hello" #. Tag: para #: I18n.xml:224 #, no-c-format msgid "And in <literal>messages_en_AU.properties</literal>:" -msgstr "" +msgstr "Et dans <literal>messages_en_AU.properties</literal>:" #. Tag: programlisting #: I18n.xml:226 #, no-c-format msgid "Hello=G'day" -msgstr "" +msgstr "Hello=G'day" #. Tag: para #: I18n.xml:228 #, no-c-format -msgid "" -"You can select a different name for the resource bundle by setting the Seam " -"configuration property named <literal> org.jboss.seam.core.resourceLoader." -"bundleNames</literal>. You can even specify a list of resource bundle names " -"to be searched (depth first) for messages." +msgid "You can select a different name for the resource bundle by setting the Seam configuration property named <literal> org.jboss.seam.core.resourceLoader.bundleNames</literal>. You can even specify a list of resource bundle names to be searched (depth first) for messages." msgstr "" #. Tag: programlisting @@ -419,69 +310,56 @@ #. Tag: para #: I18n.xml:236 #, no-c-format -msgid "" -"If you want to define a message just for a particular page, you can specify " -"it in a resource bundle with the same name as the JSF view id, with the " -"leading <literal>/</literal> and trailing file extension removed. So we " -"could put our message in <literal> welcome/hello_en.properties</literal> if " -"we only needed to display the message on <literal> /welcome/hello.jsp</" -"literal>." +msgid "If you want to define a message just for a particular page, you can specify it in a resource bundle with the same name as the JSF view id, with the leading <literal>/</literal> and trailing file extension removed. So we could put our message in <literal> welcome/hello_en.properties</literal> if we only needed to display the message on <literal> /welcome/hello.jsp</literal>." msgstr "" #. Tag: para #: I18n.xml:243 #, no-c-format -msgid "" -"You can even specify an explicit bundle name in <literal> pages.xml</" -"literal>:" +msgid "You can even specify an explicit bundle name in <literal> pages.xml</literal>:" msgstr "" #. Tag: programlisting #: I18n.xml:246 #, no-c-format msgid "&lt;page view-id=\"/welcome/hello.jsp\" bundle=\"HelloMessages\"/&gt;" -msgstr "" +msgstr "&lt;page view-id=\"/welcome/hello.jsp\" bundle=\"HelloMessages\"/&gt;" #. Tag: para #: I18n.xml:248 #, no-c-format -msgid "" -"Then we could use messages defined in <literal> HelloMessages.properties</" -"literal> on <literal> /welcome/hello.jsp</literal>." +msgid "Then we could use messages defined in <literal> HelloMessages.properties</literal> on <literal> /welcome/hello.jsp</literal>." msgstr "" #. Tag: title #: I18n.xml:254 #, no-c-format msgid "Displaying labels" -msgstr "" +msgstr "L'affichage des labels" #. Tag: para #: I18n.xml:256 #, no-c-format -msgid "" -"If you define your labels using the Seam resource bundle, you'll be able to " -"use them without having to type <literal> &lt;f:loadBundle ... /&gt;</" -"literal> on every page. Instead, you can simply type:" +msgid "If you define your labels using the Seam resource bundle, you'll be able to use them without having to type <literal> &lt;f:loadBundle ... /&gt;</literal> on every page. Instead, you can simply type:" msgstr "" #. Tag: programlisting #: I18n.xml:260 #, no-c-format msgid "&lt;h:outputText value=\"#{messages['Hello']}\"/&gt;" -msgstr "" +msgstr "&lt;h:outputText value=\"#{messages['Hello']}\"/&gt;" #. Tag: para #: I18n.xml:262 #, no-c-format msgid "<para>or:</para>" -msgstr "" +msgstr "<para>ou:</para>" #. Tag: programlisting #: I18n.xml:264 #, no-c-format msgid "&lt;h:outputText value=\"#{messages.Hello}\"/&gt;" -msgstr "" +msgstr "&lt;h:outputText value=\"#{messages.Hello}\"/&gt;" #. Tag: para #: I18n.xml:266 @@ -493,45 +371,42 @@ #: I18n.xml:269 #, no-c-format msgid "Hello=Hello, #{user.firstName} #{user.lastName}" -msgstr "" +msgstr "Hello=Hello, #{user.firstName} #{user.lastName}" #. Tag: programlisting #: I18n.xml:271 #, no-c-format msgid "Hello=G'day, #{user.firstName}" -msgstr "" +msgstr "Hello=G'day, #{user.firstName}" #. Tag: para #: I18n.xml:273 #, no-c-format msgid "You can even use the messages in your code:" -msgstr "" +msgstr "Vous pouvez même utiliser les messages dans votre code:" #. Tag: programlisting #: I18n.xml:275 #, no-c-format msgid "@In private Map&lt;String, String&gt; messages;" -msgstr "" +msgstr "@In private Map&lt;String, String&gt; messages;" #. Tag: programlisting #: I18n.xml:277 #, no-c-format msgid "@In(\"#{messages['Hello']}\") private String helloMessage;" -msgstr "" +msgstr "@In(\"#{messages['Hello']}\") private String helloMessage;" #. Tag: title #: I18n.xml:281 #, no-c-format msgid "Faces messages" -msgstr "" +msgstr "Les messages Faces" #. Tag: para #: I18n.xml:283 #, no-c-format -msgid "" -"The <literal>facesMessages</literal> component is a super-convenient way to " -"display success or failure messages to the user. The functionality we just " -"described also works for faces messages:" +msgid "The <literal>facesMessages</literal> component is a super-convenient way to display success or failure messages to the user. The functionality we just described also works for faces messages:" msgstr "" #. Tag: programlisting @@ -548,75 +423,63 @@ " }\n" "}" msgstr "" +"@Name(\"hello\")\n" +"@Stateless\n" +"public class HelloBean implements Hello {\n" +" @In FacesMessages facesMessages;\n" +" \n" +" public String sayIt() {\n" +" facesMessages.addFromResourceBundle(\"Hello\");\n" +" }\n" +"}" #. Tag: para #: I18n.xml:290 #, no-c-format -msgid "" -"This will display <literal>Hello, Gavin King</literal> or <literal>G'day, " -"Gavin</literal>, depending upon the user's locale." -msgstr "" +msgid "This will display <literal>Hello, Gavin King</literal> or <literal>G'day, Gavin</literal>, depending upon the user's locale." +msgstr "Cela va afficher <literal>Hello, Gavin King</literal> ou <literal>G'day, Gavin</literal>, selon la locale de l'utilisateur." #. Tag: title #: I18n.xml:297 #, no-c-format msgid "Timezones" -msgstr "" +msgstr "Les fuseaux horaires" #. Tag: para #: I18n.xml:299 #, no-c-format -msgid "" -"There is also a session-scoped instance of <literal> java.util.Timezone</" -"literal>, named <literal> org.jboss.seam.international.timezone</literal>, " -"and a Seam component for changing the timezone named <literal> org.jboss." -"seam.international.timezoneSelector</literal>. By default, the timezone is " -"the default timezone of the server. Unfortunately, the JSF specification " -"says that all dates and times should be assumed to be UTC, and displayed as " -"UTC, unless a timezone is explicitly specified using <literal> &lt;f:" -"convertDateTime&gt;</literal>. This is an extremely inconvenient default " -"behavior." +msgid "There is also a session-scoped instance of <literal> java.util.Timezone</literal>, named <literal> org.jboss.seam.international.timezone</literal>, and a Seam component for changing the timezone named <literal> org.jboss.seam.international.timezoneSelector</literal>. By default, the timezone is the default timezone of the server. Unfortunately, the JSF specification says that all dates and times should be assumed to be UTC, and displayed as UTC, unless a timezone is explicitly specified using <literal> &lt;f:convertDateTime&gt;</literal>. This is an extremely inconvenient default behavior." msgstr "" #. Tag: para #: I18n.xml:310 #, no-c-format -msgid "" -"Seam overrides this behavior, and defaults all dates and times to the Seam " -"timezone. In addition, Seam provides the <literal> &lt;s:convertDateTime&gt;" -"</literal> tag which always performs conversions in the Seam timezone." +msgid "Seam overrides this behavior, and defaults all dates and times to the Seam timezone. In addition, Seam provides the <literal> &lt;s:convertDateTime&gt;</literal> tag which always performs conversions in the Seam timezone." msgstr "" #. Tag: para #: I18n.xml:315 #, no-c-format -msgid "" -"Seam also provides a default date converter to convert a string value to a " -"date. This saves you from having to specify a converter on input fields that " -"are simply capturing a date. The pattern is selected according the the " -"user's locale and the time zone is selected as described above." +msgid "Seam also provides a default date converter to convert a string value to a date. This saves you from having to specify a converter on input fields that are simply capturing a date. The pattern is selected according the the user's locale and the time zone is selected as described above." msgstr "" #. Tag: title #: I18n.xml:322 #, no-c-format msgid "Themes" -msgstr "" +msgstr "Les thèmes" #. Tag: para #: I18n.xml:324 #, no-c-format -msgid "" -"Seam applications are also very easily skinnable. The theme API is very " -"similar to the localization API, but of course these two concerns are " -"orthogonal, and some applications support both localization and themes." +msgid "Seam applications are also very easily skinnable. The theme API is very similar to the localization API, but of course these two concerns are orthogonal, and some applications support both localization and themes." msgstr "" #. Tag: para #: I18n.xml:329 #, no-c-format msgid "First, configure the set of supported themes:" -msgstr "" +msgstr "En permier, configurez le groupe de thème disponibles:" #. Tag: programlisting #: I18n.xml:331 @@ -635,16 +498,12 @@ #: I18n.xml:333 #, no-c-format msgid "Note that the first theme listed is the default theme." -msgstr "" +msgstr "Notez que le premier thème listé est le thème par défaut." #. Tag: para #: I18n.xml:335 #, no-c-format -msgid "" -"Themes are defined in a properties file with the same name as the theme. For " -"example, the <literal>default</literal> theme is defined as a set of entries " -"in <literal> default.properties</literal>. For example, <literal> default." -"properties</literal> might define:" +msgid "Themes are defined in a properties file with the same name as the theme. For example, the <literal>default</literal> theme is defined as a set of entries in <literal> default.properties</literal>. For example, <literal> default.properties</literal> might define:" msgstr "" #. Tag: programlisting @@ -654,30 +513,26 @@ "css ../screen.css\n" "template /template.xhtml" msgstr "" +"css ../screen.css\n" +"template /template.xhtml" #. Tag: para #: I18n.xml:342 #, no-c-format -msgid "" -"Usually the entries in a theme resource bundle will be paths to CSS styles " -"or images and names of facelets templates (unlike localization resource " -"bundles which are usually text)." +msgid "Usually the entries in a theme resource bundle will be paths to CSS styles or images and names of facelets templates (unlike localization resource bundles which are usually text)." msgstr "" #. Tag: para #: I18n.xml:346 #, no-c-format -msgid "" -"Now we can use these entries in our JSP or facelets pages. For example, to " -"theme the stylesheet in a facelets page:" +msgid "Now we can use these entries in our JSP or facelets pages. For example, to theme the stylesheet in a facelets page:" msgstr "" #. Tag: programlisting #: I18n.xml:349 #, no-c-format -msgid "" -"&lt;link href=\"#{theme.css}\" rel=\"stylesheet\" type=\"text/css\" /&gt;" -msgstr "" +msgid "&lt;link href=\"#{theme.css}\" rel=\"stylesheet\" type=\"text/css\" /&gt;" +msgstr "&lt;link href=\"#{theme.css}\" rel=\"stylesheet\" type=\"text/css\" /&gt;" #. Tag: para #: I18n.xml:351 @@ -689,17 +544,16 @@ #: I18n.xml:353 #, no-c-format msgid "" -"&lt;link href=\"#{facesContext.externalContext.requestContextPath}#{theme." -"css}\" \n" +"&lt;link href=\"#{facesContext.externalContext.requestContextPath}#{theme.css}\" \n" " rel=\"stylesheet\" type=\"text/css\" /&gt;" msgstr "" +"&lt;link href=\"#{facesContext.externalContext.requestContextPath}#{theme.css}\" \n" +" rel=\"stylesheet\" type=\"text/css\" /&gt;" #. Tag: para #: I18n.xml:355 #, no-c-format -msgid "" -"Most powerfully, facelets lets us theme the template used by a <literal>&lt;" -"ui:composition&gt;</literal>:" +msgid "Most powerfully, facelets lets us theme the template used by a <literal>&lt;ui:composition&gt;</literal>:" msgstr "" #. Tag: programlisting @@ -712,13 +566,16 @@ " xmlns:f=\"http://java.sun.com/jsf/core\"\n" " template=\"#{theme.template}\"&gt;" msgstr "" +"&lt;ui:composition xmlns=\"http://www.w3.org/1999/xhtml\"\n" +" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n" +" xmlns:h=\"http://java.sun.com/jsf/html\"\n" +" xmlns:f=\"http://java.sun.com/jsf/core\"\n" +" template=\"#{theme.template}\"&gt;" #. Tag: para #: I18n.xml:360 #, no-c-format -msgid "" -"Just like the locale selector, there is a built-in theme selector to allow " -"the user to freely switch themes:" +msgid "Just like the locale selector, there is a built-in theme selector to allow the user to freely switch themes:" msgstr "" #. Tag: programlisting @@ -728,9 +585,12 @@ "&lt;h:selectOneMenu value=\"#{themeSelector.theme}\"&gt;\n" " &lt;f:selectItems value=\"#{themeSelector.themes}\"/&gt;\n" "&lt;/h:selectOneMenu&gt;\n" -"&lt;h:commandButton action=\"#{themeSelector.select}\" value=\"Select Theme" -"\"/&gt;" +"&lt;h:commandButton action=\"#{themeSelector.select}\" value=\"Select Theme\"/&gt;" msgstr "" +"&lt;h:selectOneMenu value=\"#{themeSelector.theme}\"&gt;\n" +" &lt;f:selectItems value=\"#{themeSelector.themes}\"/&gt;\n" +"&lt;/h:selectOneMenu&gt;\n" +"&lt;h:commandButton action=\"#{themeSelector.select}\" value=\"Select Theme\"/&gt;" #. Tag: title #: I18n.xml:367 @@ -741,11 +601,7 @@ #. Tag: para #: I18n.xml:369 #, no-c-format -msgid "" -"The locale selector, theme selector and timezone selector all support " -"persistence of locale and theme preference to a cookie. Simply set the " -"<literal>cookie-enabled</literal> property in <literal>components.xml</" -"literal>:" +msgid "The locale selector, theme selector and timezone selector all support persistence of locale and theme preference to a cookie. Simply set the <literal>cookie-enabled</literal> property in <literal>components.xml</literal>:" msgstr "" #. Tag: programlisting @@ -762,3 +618,13 @@ "\n" "&lt;international:locale-selector cookie-enabled=\"true\"/&gt;" msgstr "" +"&lt;theme:theme-selector cookie-enabled=\"true\"&gt;\n" +" &lt;theme:available-themes&gt;\n" +" &lt;value&gt;default&lt;/value&gt;\n" +" &lt;value&gt;accessible&lt;/value&gt;\n" +" &lt;value&gt;printable&lt;/value&gt;\n" +" &lt;/theme:available-themes&gt;\n" +"&lt;/theme:theme-selector&gt;\n" +"\n" +"&lt;international:locale-selector cookie-enabled=\"true\"/&gt;" +