User: jpmcc Date: 2009-12-29 00:00:41+0000 Modified: native-lang/www/planet/atom.xml native-lang/www/planet/index.html native-lang/www/planet/opml.xml native-lang/www/planet/rss10.xml native-lang/www/planet/rss20.xml
Log: Planet run at Tue Dec 29 01:00:32 CET 2009 File Changes: Directory: /native-lang/www/planet/ =================================== File [changed]: atom.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/atom.xml?r1=1.2546&r2=1.2547 Delta lines: +72 -8 -------------------- --- atom.xml 2009-12-28 18:02:09+0000 1.2546 +++ atom.xml 2009-12-29 00:00:38+0000 1.2547 @@ -5,9 +5,73 @@ <link rel="self" href="http://native-lang.openoffice.org/planet/atom.xml"/> <link href="http://native-lang.openoffice.org/planet/"/> <id>http://native-lang.openoffice.org/planet/atom.xml</id> - <updated>2009-12-28T18:02:07+00:00</updated> + <updated>2009-12-29T00:00:36+00:00</updated> <generator uri="http://www.planetplanet.org/";>Planet/2.0 +http://www.planetplanet.org</generator> + <entry xml:lang="fr"> + <title type="html">Nouveau format pour les fichiers de configuration OOo</title> + <link href="http://sophiegautier.com/blog/index.php/2009/12/28/137-nouveau-format-pour-les-fichiers-de-configuration-ooo"/> + <id>tag:sophiegautier.com,2009-12-28:/blog/137</id> + <updated>2009-12-28T17:45:14+00:00</updated> + <content type="html"><p>L'équipe qui travaille sur les performances de OOo s'est attaquée à modifier la façon dont les fichiers de configurations de OOo sont pris en charge. Pour ceux qui sont habitués à les manipuler, il s'agit des fichiers .xcs et .xcu. +<br /> +Un nouveau format de fichier a été créé, le format .xcd qui reprend pratiquement le xml des autres formats. Au lieu d'avoir maintenant des tas de fichiers dans tous les coins, il n'en reste plus que quelques uns qui concatènent les précédents. Cela permet d'économiser de l'espace disque et d'éviter la multiplication des appels.<br /> +<br /> +Ainsi, si vous aviez l'habitude de modifier l'installation en modifiant les fichiers .xcu, il faudra passer par une extension pour continuer de réaliser ces modifications, les extensions contenant toujours ce type de configuration. De la même façon, l'ancienne configuration utilisateur est migré vers le nouveau format au premier démarrage de OOo. +<br /> +Pour plus d'informations à ce sujet, vous pouvez consulter la page <a href="http://wiki.services.openoffice.org/wiki/Performance/Configuration" hreflang="en">wiki du projet performance</a>.</p></content> + <author> + <name>sophi</name> + <uri>http://sophiegautier.com/blog/index.php/</uri> + </author> + <source> + <title type="html">Sgauti at OOo</title> + <subtitle type="html">Histoires OpenOfficiennes et autres...</subtitle> + <link rel="self" href="http://sophiegautier.com/blog/atom.php"/> + <id>tag:sophiegautier.com,2009:/blog/index.php/</id> + <updated>2009-12-29T00:00:34+00:00</updated> + </source> + </entry> + + <entry xml:lang="fr"> + <title type="html" xml:lang="en">QA on l10n build - small reminder :-)</title> + <link href="http://sophiegautier.com/blog/index.php/2009/12/28/136-qa-on-l10n-build-small-reminder-"/> + <id>tag:sophiegautier.com,2009-12-28:/blog/136</id> + <updated>2009-12-28T14:08:24+00:00</updated> + <content type="html" xml:lang="en"><p>here is a reminder for all of you who want to test l10n builds.</p> + +<ul> +<li>Builds to test appear in QATrack and NL project leads are notified by e-mail and RSS. If you wish to test a build which has not appeared on QATrack yet, send a request to the [email protected] mailing list.</li> +<li>The lead of the NL project registers users (testers) in the TCM and assigns them various test scenarios. (At least the "Release Sanity" scenario should be assigned once per platform).</li> +<li>The testers make the tests, and enter the results in the TCM.</li> +<li>The lead enters the status of the testing to the QATrack</li> +<li>After the tests have been done, you update the status page and file an issue in IssueZilla, stating that the build is ready for distribution. Use this link as template.</li> +<li>Then you update your project page to announce the availability of your localized builds :)</li> +</ul> + +<p>Note: for all builds (RC1, RC2...., RCN) the tests are the same in TCM. Simply update the status of bugs in the current release.</p> + + +<p>In case full TCM tests are not possible because of lack of time or testers, you can follow the easier path with <a href="http://wiki.services.openoffice.org/wiki/Sanity_Check_Of_L10n_Builds" hreflang="en">Sanity Check Of L10n Builds</a>. You can skip then all TCM-related steps. Remember, though: the more tests, the less bugs in the software. But don't forget to file an issue stating that the build is available and the link to the build.</p> + + +<p>All the links and indications are available <a href="http://wiki.services.openoffice.org/wiki/NLC/localizedQA" hreflang="en">on the wiki page</a></p> + + +<p>As usual, don't hesitate to ask on the l10n list if you have any question.</p></content> + <author> + <name>sophi</name> + <uri>http://sophiegautier.com/blog/index.php/</uri> + </author> + <source> + <title type="html">Sgauti at OOo</title> + <subtitle type="html">Histoires OpenOfficiennes et autres...</subtitle> + <link rel="self" href="http://sophiegautier.com/blog/atom.php"/> + <id>tag:sophiegautier.com,2009:/blog/index.php/</id> + <updated>2009-12-29T00:00:34+00:00</updated> + </source> + </entry> + <entry xml:lang="utf-8"> <title type="html">2010 Year of Tiger</title> <link href="http://openoffice.exblog.jp/9514993/"/> @@ -61,7 +125,7 @@ <subtitle type="html">Histoires OpenOfficiennes et autres...</subtitle> <link rel="self" href="http://sophiegautier.com/blog/atom.php"/> <id>tag:sophiegautier.com,2009:/blog/index.php/</id> - <updated>2009-12-27T18:00:35+00:00</updated> + <updated>2009-12-29T00:00:34+00:00</updated> </source> </entry> @@ -106,7 +170,7 @@ <subtitle type="html">Histoires OpenOfficiennes et autres...</subtitle> <link rel="self" href="http://sophiegautier.com/blog/atom.php"/> <id>tag:sophiegautier.com,2009:/blog/index.php/</id> - <updated>2009-12-27T18:00:35+00:00</updated> + <updated>2009-12-29T00:00:34+00:00</updated> </source> </entry> @@ -127,7 +191,7 @@ <subtitle type="html">Histoires OpenOfficiennes et autres...</subtitle> <link rel="self" href="http://sophiegautier.com/blog/atom.php"/> <id>tag:sophiegautier.com,2009:/blog/index.php/</id> - <updated>2009-12-27T18:00:35+00:00</updated> + <updated>2009-12-29T00:00:34+00:00</updated> </source> </entry> @@ -177,7 +241,7 @@ <subtitle type="html">Histoires OpenOfficiennes et autres...</subtitle> <link rel="self" href="http://sophiegautier.com/blog/atom.php"/> <id>tag:sophiegautier.com,2009:/blog/index.php/</id> - <updated>2009-12-27T18:00:35+00:00</updated> + <updated>2009-12-29T00:00:34+00:00</updated> </source> </entry> @@ -196,7 +260,7 @@ <subtitle type="html">Histoires OpenOfficiennes et autres...</subtitle> <link rel="self" href="http://sophiegautier.com/blog/atom.php"/> <id>tag:sophiegautier.com,2009:/blog/index.php/</id> - <updated>2009-12-27T18:00:35+00:00</updated> + <updated>2009-12-29T00:00:34+00:00</updated> </source> </entry> @@ -219,7 +283,7 @@ <subtitle type="html">Histoires OpenOfficiennes et autres...</subtitle> <link rel="self" href="http://sophiegautier.com/blog/atom.php"/> <id>tag:sophiegautier.com,2009:/blog/index.php/</id> - <updated>2009-12-27T18:00:35+00:00</updated> + <updated>2009-12-29T00:00:34+00:00</updated> </source> </entry> @@ -260,7 +324,7 @@ <subtitle type="html">Histoires OpenOfficiennes et autres...</subtitle> <link rel="self" href="http://sophiegautier.com/blog/atom.php"/> <id>tag:sophiegautier.com,2009:/blog/index.php/</id> - <updated>2009-12-27T18:00:35+00:00</updated> + <updated>2009-12-29T00:00:34+00:00</updated> </source> </entry> File [changed]: index.html Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/index.html?r1=1.2546&r2=1.2547 Delta lines: +56 -1 -------------------- --- index.html 2009-12-28 18:02:09+0000 1.2546 +++ index.html 2009-12-29 00:00:38+0000 1.2547 @@ -29,8 +29,63 @@ <a href="rss20.xml"><img src="rss2.gif" alt="Link to RSS 2 feed" /></a> </div> -<p><em>Bloggings on native language topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: December 28, 2009 06:02 PM CET</em></p> +<p><em>Bloggings on native language topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: December 29, 2009 12:00 AM CET</em></p> +<h2>December 28, 2009</h2> +<h3> +<a href="http://sophiegautier.com/blog/index.php/"; title="Sgauti at OOo"> +Sophie Gautier</a> : +<a href="http://sophiegautier.com/blog/index.php/2009/12/28/137-nouveau-format-pour-les-fichiers-de-configuration-ooo";> +Nouveau format pour les fichiers de configuration OOo</a> +</h3> +<p> +<p>L'équipe qui travaille sur les performances de OOo s'est attaquée à modifier la façon dont les fichiers de configurations de OOo sont pris en charge. Pour ceux qui sont habitués à les manipuler, il s'agit des fichiers .xcs et .xcu. +<br /> +Un nouveau format de fichier a été créé, le format .xcd qui reprend pratiquement le xml des autres formats. Au lieu d'avoir maintenant des tas de fichiers dans tous les coins, il n'en reste plus que quelques uns qui concatènent les précédents. Cela permet d'économiser de l'espace disque et d'éviter la multiplication des appels.<br /> +<br /> +Ainsi, si vous aviez l'habitude de modifier l'installation en modifiant les fichiers .xcu, il faudra passer par une extension pour continuer de réaliser ces modifications, les extensions contenant toujours ce type de configuration. De la même façon, l'ancienne configuration utilisateur est migré vers le nouveau format au premier démarrage de OOo. +<br /> +Pour plus d'informations à ce sujet, vous pouvez consulter la page <a href="http://wiki.services.openoffice.org/wiki/Performance/Configuration"; hreflang="en">wiki du projet performance</a>.</p></p> +<p> +<em><a href="http://sophiegautier.com/blog/index.php/2009/12/28/137-nouveau-format-pour-les-fichiers-de-configuration-ooo";>by sophi at December 28, 2009 05:45 PM CET</a></em> +</p> +<br /> +<hr /> +<br /> +<h3> +<a href="http://sophiegautier.com/blog/index.php/"; title="Sgauti at OOo"> +Sophie Gautier</a> : +<a href="http://sophiegautier.com/blog/index.php/2009/12/28/136-qa-on-l10n-build-small-reminder-";> +QA on l10n build - small reminder :-)</a> +</h3> +<p> +<p>here is a reminder for all of you who want to test l10n builds.</p> + +<ul> +<li>Builds to test appear in QATrack and NL project leads are notified by e-mail and RSS. If you wish to test a build which has not appeared on QATrack yet, send a request to the [email protected] mailing list.</li> +<li>The lead of the NL project registers users (testers) in the TCM and assigns them various test scenarios. (At least the "Release Sanity" scenario should be assigned once per platform).</li> +<li>The testers make the tests, and enter the results in the TCM.</li> +<li>The lead enters the status of the testing to the QATrack</li> +<li>After the tests have been done, you update the status page and file an issue in IssueZilla, stating that the build is ready for distribution. Use this link as template.</li> +<li>Then you update your project page to announce the availability of your localized builds :)</li> +</ul> + +<p>Note: for all builds (RC1, RC2...., RCN) the tests are the same in TCM. Simply update the status of bugs in the current release.</p> + + +<p>In case full TCM tests are not possible because of lack of time or testers, you can follow the easier path with <a href="http://wiki.services.openoffice.org/wiki/Sanity_Check_Of_L10n_Builds"; hreflang="en">Sanity Check Of L10n Builds</a>. You can skip then all TCM-related steps. Remember, though: the more tests, the less bugs in the software. But don't forget to file an issue stating that the build is available and the link to the build.</p> + + +<p>All the links and indications are available <a href="http://wiki.services.openoffice.org/wiki/NLC/localizedQA"; hreflang="en">on the wiki page</a></p> + + +<p>As usual, don't hesitate to ask on the l10n list if you have any question.</p></p> +<p> +<em><a href="http://sophiegautier.com/blog/index.php/2009/12/28/136-qa-on-l10n-build-small-reminder-";>by sophi at December 28, 2009 02:08 PM CET</a></em> +</p> +<br /> +<hr /> +<br /> <h2>December 27, 2009</h2> <h3> <a href="http://openoffice.exblog.jp"; title="Hirano, Kazunari"> File [changed]: opml.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/opml.xml?r1=1.2545&r2=1.2546 Delta lines: +1 -1 ------------------- --- opml.xml 2009-12-28 18:02:09+0000 1.2545 +++ opml.xml 2009-12-29 00:00:39+0000 1.2546 @@ -2,7 +2,7 @@ <opml version="1.1"> <head> <title>Native Language Confederation Planet</title> - <dateModified>Mon, 28 Dec 2009 18:02:07 +0000</dateModified> + <dateModified>Tue, 29 Dec 2009 00:00:37 +0000</dateModified> <ownerName>Native Language Confederation</ownerName> <ownerEmail>[email protected]</ownerEmail> </head> File [changed]: rss10.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/rss10.xml?r1=1.390&r2=1.391 Delta lines: +42 -0 -------------------- --- rss10.xml 2009-12-27 12:00:39+0000 1.390 +++ rss10.xml 2009-12-29 00:00:39+0000 1.391 @@ -13,6 +13,8 @@ <items> <rdf:Seq> + <rdf:li rdf:resource="tag:sophiegautier.com,2009-12-28:/blog/137" /> + <rdf:li rdf:resource="tag:sophiegautier.com,2009-12-28:/blog/136" /> <rdf:li rdf:resource="http://openoffice.exblog.jp/9514993/"; /> <rdf:li rdf:resource="http://rss.exblog.jp/rss/exblog/openoffice/80d9067cf6e8b075de8095aeab1dad53"; /> <rdf:li rdf:resource="tag:sophiegautier.com,2009-12-24:/blog/135" /> @@ -28,6 +30,46 @@ </items> </channel> +<item rdf:about="tag:sophiegautier.com,2009-12-28:/blog/137"> + <title>Sophie Gautier: Nouveau format pour les fichiers de configuration OOo</title> + <link>http://sophiegautier.com/blog/index.php/2009/12/28/137-nouveau-format-pour-les-fichiers-de-configuration-ooo</link> + <content:encoded><p>L'équipe qui travaille sur les performances de OOo s'est attaquée à modifier la façon dont les fichiers de configurations de OOo sont pris en charge. Pour ceux qui sont habitués à les manipuler, il s'agit des fichiers .xcs et .xcu. +<br /> +Un nouveau format de fichier a été créé, le format .xcd qui reprend pratiquement le xml des autres formats. Au lieu d'avoir maintenant des tas de fichiers dans tous les coins, il n'en reste plus que quelques uns qui concatènent les précédents. Cela permet d'économiser de l'espace disque et d'éviter la multiplication des appels.<br /> +<br /> +Ainsi, si vous aviez l'habitude de modifier l'installation en modifiant les fichiers .xcu, il faudra passer par une extension pour continuer de réaliser ces modifications, les extensions contenant toujours ce type de configuration. De la même façon, l'ancienne configuration utilisateur est migré vers le nouveau format au premier démarrage de OOo. +<br /> +Pour plus d'informations à ce sujet, vous pouvez consulter la page <a href="http://wiki.services.openoffice.org/wiki/Performance/Configuration" hreflang="en">wiki du projet performance</a>.</p></content:encoded> + <dc:date>2009-12-28T17:45:14+00:00</dc:date> + <dc:creator>sophi</dc:creator> +</item> +<item rdf:about="tag:sophiegautier.com,2009-12-28:/blog/136"> + <title>Sophie Gautier: QA on l10n build - small reminder :-)</title> + <link>http://sophiegautier.com/blog/index.php/2009/12/28/136-qa-on-l10n-build-small-reminder-</link> + <content:encoded><p>here is a reminder for all of you who want to test l10n builds.</p> + +<ul> +<li>Builds to test appear in QATrack and NL project leads are notified by e-mail and RSS. If you wish to test a build which has not appeared on QATrack yet, send a request to the [email protected] mailing list.</li> +<li>The lead of the NL project registers users (testers) in the TCM and assigns them various test scenarios. (At least the "Release Sanity" scenario should be assigned once per platform).</li> +<li>The testers make the tests, and enter the results in the TCM.</li> +<li>The lead enters the status of the testing to the QATrack</li> +<li>After the tests have been done, you update the status page and file an issue in IssueZilla, stating that the build is ready for distribution. Use this link as template.</li> +<li>Then you update your project page to announce the availability of your localized builds :)</li> +</ul> + +<p>Note: for all builds (RC1, RC2...., RCN) the tests are the same in TCM. Simply update the status of bugs in the current release.</p> + + +<p>In case full TCM tests are not possible because of lack of time or testers, you can follow the easier path with <a href="http://wiki.services.openoffice.org/wiki/Sanity_Check_Of_L10n_Builds" hreflang="en">Sanity Check Of L10n Builds</a>. You can skip then all TCM-related steps. Remember, though: the more tests, the less bugs in the software. But don't forget to file an issue stating that the build is available and the link to the build.</p> + + +<p>All the links and indications are available <a href="http://wiki.services.openoffice.org/wiki/NLC/localizedQA" hreflang="en">on the wiki page</a></p> + + +<p>As usual, don't hesitate to ask on the l10n list if you have any question.</p></content:encoded> + <dc:date>2009-12-28T14:08:24+00:00</dc:date> + <dc:creator>sophi</dc:creator> +</item> <item rdf:about="http://openoffice.exblog.jp/9514993/";> <title>Kazunari Hirano: 2010 Year of Tiger</title> <link>http://openoffice.exblog.jp/9514993/</link> File [changed]: rss20.xml Url: http://native-lang.openoffice.org/source/browse/native-lang/www/planet/rss20.xml?r1=1.391&r2=1.392 Delta lines: +40 -0 -------------------- --- rss20.xml 2009-12-27 12:00:39+0000 1.391 +++ rss20.xml 2009-12-29 00:00:39+0000 1.392 @@ -8,6 +8,46 @@ <description>Native Language Confederation Planet - http://native-lang.openoffice.org/planet/</description> <item> + <title>Sophie Gautier: Nouveau format pour les fichiers de configuration OOo</title> + <guid>tag:sophiegautier.com,2009-12-28:/blog/137</guid> + <link>http://sophiegautier.com/blog/index.php/2009/12/28/137-nouveau-format-pour-les-fichiers-de-configuration-ooo</link> + <description><p>L'équipe qui travaille sur les performances de OOo s'est attaquée à modifier la façon dont les fichiers de configurations de OOo sont pris en charge. Pour ceux qui sont habitués à les manipuler, il s'agit des fichiers .xcs et .xcu. +<br /> +Un nouveau format de fichier a été créé, le format .xcd qui reprend pratiquement le xml des autres formats. Au lieu d'avoir maintenant des tas de fichiers dans tous les coins, il n'en reste plus que quelques uns qui concatènent les précédents. Cela permet d'économiser de l'espace disque et d'éviter la multiplication des appels.<br /> +<br /> +Ainsi, si vous aviez l'habitude de modifier l'installation en modifiant les fichiers .xcu, il faudra passer par une extension pour continuer de réaliser ces modifications, les extensions contenant toujours ce type de configuration. De la même façon, l'ancienne configuration utilisateur est migré vers le nouveau format au premier démarrage de OOo. +<br /> +Pour plus d'informations à ce sujet, vous pouvez consulter la page <a href="http://wiki.services.openoffice.org/wiki/Performance/Configuration" hreflang="en">wiki du projet performance</a>.</p></description> + <pubDate>Mon, 28 Dec 2009 17:45:14 +0000</pubDate> +</item> +<item> + <title>Sophie Gautier: QA on l10n build - small reminder :-)</title> + <guid>tag:sophiegautier.com,2009-12-28:/blog/136</guid> + <link>http://sophiegautier.com/blog/index.php/2009/12/28/136-qa-on-l10n-build-small-reminder-</link> + <description><p>here is a reminder for all of you who want to test l10n builds.</p> + +<ul> +<li>Builds to test appear in QATrack and NL project leads are notified by e-mail and RSS. If you wish to test a build which has not appeared on QATrack yet, send a request to the [email protected] mailing list.</li> +<li>The lead of the NL project registers users (testers) in the TCM and assigns them various test scenarios. (At least the "Release Sanity" scenario should be assigned once per platform).</li> +<li>The testers make the tests, and enter the results in the TCM.</li> +<li>The lead enters the status of the testing to the QATrack</li> +<li>After the tests have been done, you update the status page and file an issue in IssueZilla, stating that the build is ready for distribution. Use this link as template.</li> +<li>Then you update your project page to announce the availability of your localized builds :)</li> +</ul> + +<p>Note: for all builds (RC1, RC2...., RCN) the tests are the same in TCM. Simply update the status of bugs in the current release.</p> + + +<p>In case full TCM tests are not possible because of lack of time or testers, you can follow the easier path with <a href="http://wiki.services.openoffice.org/wiki/Sanity_Check_Of_L10n_Builds" hreflang="en">Sanity Check Of L10n Builds</a>. You can skip then all TCM-related steps. Remember, though: the more tests, the less bugs in the software. But don't forget to file an issue stating that the build is available and the link to the build.</p> + + +<p>All the links and indications are available <a href="http://wiki.services.openoffice.org/wiki/NLC/localizedQA" hreflang="en">on the wiki page</a></p> + + +<p>As usual, don't hesitate to ask on the l10n list if you have any question.</p></description> + <pubDate>Mon, 28 Dec 2009 14:08:24 +0000</pubDate> +</item> +<item> <title>Kazunari Hirano: 2010 Year of Tiger</title> <guid>http://openoffice.exblog.jp/9514993/</guid> <link>http://openoffice.exblog.jp/9514993/</link> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
