GNOME.org
 

gnomeweb-wml r6157 - in trunk/www.gnome.org/projects/epiphany: . development

Author: diegoe
Date: Thu Jun  5 05:22:51 2008
New Revision: 6157
URL: http://svn.gnome.org/viewvc/gnomeweb-wml?rev=6157&view=rev

Log:
Removed old plan-*.html files and updated translations.html to reflect the use
of SVN and not CVS.


Removed:
   trunk/www.gnome.org/projects/epiphany/development/plan-12.html
   trunk/www.gnome.org/projects/epiphany/development/plan-14.html
Modified:
   trunk/www.gnome.org/projects/epiphany/   (props changed)
   trunk/www.gnome.org/projects/epiphany/development/bugreports.html
   trunk/www.gnome.org/projects/epiphany/development/index.html
   trunk/www.gnome.org/projects/epiphany/development/translations.html

Modified: trunk/www.gnome.org/projects/epiphany/development/bugreports.html
==============================================================================
--- trunk/www.gnome.org/projects/epiphany/development/bugreports.html	(original)
+++ trunk/www.gnome.org/projects/epiphany/development/bugreports.html	Thu Jun  5 05:22:51 2008
@@ -84,9 +84,7 @@
 
           <li><a href="translations.html">Translations</a></li>
 
-          <li><a href="plan-12.html">Epiphany 1.2 Plan</a></li>
-
-          <li><a href="plan-14.html">Epiphany 1.4 Plan</a></li>
+          <li><a href="http://live.gnome.org/Epiphany";>Epiphany Wiki</a></li>
         </ul>
       </li>
 

Modified: trunk/www.gnome.org/projects/epiphany/development/index.html
==============================================================================
--- trunk/www.gnome.org/projects/epiphany/development/index.html	(original)
+++ trunk/www.gnome.org/projects/epiphany/development/index.html	Thu Jun  5 05:22:51 2008
@@ -27,7 +27,7 @@
 
     <p>You can submit patches on the <a href="http://mail.gnome.org/mailman/listinfo/epiphany-list/";>Epiphany mailing list</a> or in <a href="http://bugzilla.gnome.org/";>bugzilla</a>. In the latter case remember to add the PATCH keyword to the bug, to bring it to the mantainer attention.</p>
 
-    <h2>The Future of Epiphany: 1.6 and beyond</h2>
+    <h2>The Future of Epiphany</h2>
     <p>Planning for the next Epiphany releases takes place in the <a href="http://live.gnome.org/Epiphany";>Epiphany Wiki</a>.</p>
   </div>
 
@@ -52,10 +52,6 @@
 
           <li><a href="http://live.gnome.org/Epiphany";>Epiphany Wiki</a></li>
 
-          <li><a href="plan-12.html">Epiphany 1.2 Plan</a></li>
-
-          <li><a href="plan-14.html">Epiphany 1.4 Plan</a></li>
-
         </ul>
       </li>
 

Modified: trunk/www.gnome.org/projects/epiphany/development/translations.html
==============================================================================
--- trunk/www.gnome.org/projects/epiphany/development/translations.html	(original)
+++ trunk/www.gnome.org/projects/epiphany/development/translations.html	Thu Jun  5 05:22:51 2008
@@ -25,7 +25,7 @@
 
     <p>To help us with Epiphany translations, we'd <em>really</em> like you to join the GTP and join your respective language team first. Joining is easy, what it takes is more or less just subscribing to some mailing lists. More on that below.</p>
 
-    <p>There's a lot of reasons why we want you to do this. First of all, you will not be required to translate anything - it's all up to you, even if you join the GTP. Second, we'd really hate if there later was discovered that someone had done duplicate work - there might already be someone working on a Epiphany translation for your language, but there's no way to know until you have contacted your language team and asked if someone is already working on a translation. In most cases that's probably not the case, but asking first might save a lot of trouble later. Third, your translation team has people that probably have translated a lot of applications into your language before, and they can usually help you with any translation question (technical or linguistic) that you might have. Fourth, every translation team usually has at least one person with access to the GNOME CVS repository (where Epiphany development takes place), and he/she can commit your finished translatio
 n directly into this CVS repository.</p>
+    <p>There's a lot of reasons why we want you to do this. First of all, you will not be required to translate anything - it's all up to you, even if you join the GTP. Second, we'd really hate if there later was discovered that someone had done duplicate work - there might already be someone working on a Epiphany translation for your language, but there's no way to know until you have contacted your language team and asked if someone is already working on a translation. In most cases that's probably not the case, but asking first might save a lot of trouble later. Third, your translation team has people that probably have translated a lot of applications into your language before, and they can usually help you with any translation question (technical or linguistic) that you might have. Fourth, every translation team usually has at least one person with access to the GNOME SVN repository (where Epiphany development takes place), and he/she can commit your finished translatio
 n directly into this SVN repository.</p>
 
     <p>Instructions on how to join the GTP are on the GTP web site, mentioned above. To join the GTP itself, you should (as mentioned on the GTP page) subscribe to the gnome-i18n gnome org mailing list. This can be done by going to:</p>
 
@@ -39,23 +39,23 @@
 
     <p>&gt;From now on I will assume that you have done the above, and joined the GTP and the team for your language. Now we come to the part on how to actually translate. You need at least one important software package installed on your system to be able to translate: "gettext". Please make sure that you have this package installed before you begin.</p>
 
-    <p>To be able to start a new translation you need the application's untranslated messages, which is stored in a so called pot file (suffix .pot). The pot file for Epiphany can either be fetched from the web or generated from Epiphany source code taken from CVS.</p>
+    <p>To be able to start a new translation you need the application's untranslated messages, which is stored in a so called pot file (suffix .pot). The pot file for Epiphany can either be fetched from the web or generated from Epiphany source code taken from SVN.</p>
 
     <h3>Fetching the pot file from the translation status pages</h3>
 
     <p>The easiest way to get the pot file is to fetch the pot file from the web. You'll find it on the GNOME translation status pages, located at:</p>
 
-    <p><a href="http://developer.gnome.org/projects/gtp/status/";>http://developer.gnome.org/projects/gtp/status/</a></p>
+    <p><a href="http://l10n.gnome.org/";>http://l10n.gnome.org/</a></p>
 
     <p>If you browse these pages you should find a reference to Epiphany and be able to download a pot file for it.</p>
 
-    <h3>Generating the pot file from Epiphany source code in CVS</h3>
+    <h3>Generating the pot file from Epiphany source code in SVN</h3>
 
-    <p>Another way of getting the pot file is by using anonymous GNOME CVS access. If you do intend to get the pot file this way you need to make sure that you have the software "intltool" installed on your computer. It should always be the latest available version; if it isn't, please upgrade before you begin.</p>
+    <p>Another way of getting the pot file is by using anonymous GNOME SVN access. If you do intend to get the pot file this way you need to make sure that you have the software "intltool" installed on your computer. It should always be the latest available version; if it isn't, please upgrade before you begin.</p>
 
-    <p>When you use CVS you need to checkout the "EpiphanyMODULE" module and go to the "po" directory of the module. Instructions on how to use anonymous GNOME CVS access are at:</p>
+    <p>When you use SVN you need to checkout the "EpiphanyMODULE" module and go to the "po" directory of the module. Instructions on how to use anonymous GNOME SVN access are at:</p>
 
-    <p><a href="http://developer.gnome.org/tools/cvs.html";>http://developer.gnome.org/tools/cvs.html</a></p>
+    <p><a href="http://developer.gnome.org/tools/svn.html";>http://developer.gnome.org/tools/svn.html</a></p>
 
     <p>When you have checked out the module, go to the "po" directory inside it and run:</p>
     <pre>
@@ -84,7 +84,7 @@
  msgfmt -cv xy.po
 </pre>
 
-    <p>If there is any error, please go back and correct it before continuing. When all errors are gone, send the translation to a person in your language team that has GNOME CVS access, and ask him/her to please commit it. If you send the file by mail, it's usually a good idea to first compress the file with "gzip", since otherwise some mail software may do bad things and not preserve the encoding.</p>
+    <p>If there is any error, please go back and correct it before continuing. When all errors are gone, send the translation to a person in your language team that has GNOME SVN access, and ask him/her to please commit it. If you send the file by mail, it's usually a good idea to first compress the file with "gzip", since otherwise some mail software may do bad things and not preserve the encoding.</p>
 
     <p>That's it. If you have any questions regarding the PO format, gettext or translations, please ask your language team. If the question is specific to Epiphany (such as the messages themselves or Epiphany code), ask Epiphany developers.</p>
 
@@ -111,9 +111,7 @@
 
           <li>Translations</li>
 
-          <li><a href="plan-12.html">Epiphany 1.2 Plan</a></li>
-
-          <li><a href="plan-14.html">Epiphany 1.4 Plan</a></li>
+          <li><a href="http://live.gnome.org/Epiphany";>Epiphany Wiki</a></li>
         </ul>
       </li>
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]