web/html/docs/translation-quick-start-guide/en_US generated-index.php, 1.9, 1.10 index.php, 1.13, 1.14 legalnotice-opl.php, 1.7, 1.8 rv-revhistory.php, 1.13, 1.14 sn_accounts.php, 1.13, 1.14 sn_translating_docs.php, 1.13, 1.14 sn_translating_software.php, 1.13, 1.14

Karsten Wade kwade at fedoraproject.org
Fri Feb 6 01:58:33 UTC 2009


Author: kwade

Update of /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv25067/en_US

Modified Files:
	generated-index.php index.php legalnotice-opl.php 
	rv-revhistory.php sn_accounts.php sn_translating_docs.php 
	sn_translating_software.php 
Log Message:
updating to latest version from upstream; resolves bugs such as bug#483176


Index: generated-index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/generated-index.php,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- generated-index.php	15 Aug 2008 05:17:46 -0000	1.9
+++ generated-index.php	6 Feb 2009 01:58:02 -0000	1.10
@@ -3,11 +3,11 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Index</title>
 <link rel="stylesheet" href="fedora.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
-<link rel="start" href="index.php" title="Translation Quick Start Guide">
+<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="home" href="index.php" title="Translation Quick Start Guide">
 <link rel="up" href="index.php" title="Translation Quick Start Guide">
 <link rel="prev" href="sn_translating_docs.php" title="4. Translating Documentation">
-<link rel="copyright" href="ln-legalnotice-opl.php" title="Legal Notice">
+<link rel="copyright" href="legalnotice-opl.php" title="Legal Notice">
 </head>
 <?
 


Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/index.php,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- index.php	15 Aug 2008 05:17:46 -0000	1.13
+++ index.php	6 Feb 2009 01:58:02 -0000	1.14
@@ -3,10 +3,10 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Translation Quick Start Guide</title>
 <link rel="stylesheet" href="fedora.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
-<link rel="start" href="index.php" title="Translation Quick Start Guide">
+<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="home" href="index.php" title="Translation Quick Start Guide">
 <link rel="next" href="sn_accounts.php" title="2. Accounts and Subscriptions">
-<link rel="copyright" href="ln-legalnotice-opl.php" title="Legal Notice">
+<link rel="copyright" href="legalnotice-opl.php" title="Legal Notice">
 </head>
 <?
 
@@ -56,33 +56,21 @@
 <span class="firstname">Dimitris</span> <span class="surname">Glezos</span>
 </h3>
 </div>
-</div></div>
-<div><div class="othercredit"><h3 class="othercredit">
-<span class="firstname">Hugo</span> <span class="surname">Cisneiros</span>
-</h3></div></div>
-<div><div class="othercredit"><h3 class="othercredit">
-<span class="firstname">Francesco</span> <span class="surname">Tombolini</span>
-</h3></div></div>
-<div><div class="othercredit"><h3 class="othercredit">
-<span class="firstname">Andrew</span> <span class="surname">Martynov</span>
-</h3></div></div>
-<div><div class="othercredit"><h3 class="othercredit">
-<span class="firstname">José</span> <span class="surname">Pires</span>
-</h3></div></div>
-<div><div class="othercredit"><h3 class="othercredit">
-<span class="firstname">Bart</span> <span class="surname">Courveur</span>
-</h3></div></div>
-<div><div class="othercredit"><h3 class="othercredit">
-<span class="firstname">Damien</span> <span class="surname">Durand</span>
-</h3></div></div>
-<div><div class="othercredit"><h3 class="othercredit">
-<span class="firstname">Guillermo</span> <span class="surname">Gomez</span>
-</h3></div></div>
-<div><div class="othercredit"><h3 class="othercredit">
+<div class="editor">
+<h4 class="editedby">Edited by</h4>
+<h3 class="editor">
 <span class="firstname">Diego</span> <span class="othername">Búrigo</span> <span class="surname">Zacarão</span>
-</h3></div></div>
-<div><p class="releaseinfo">Version 0.5 (2008-04-18)</p></div>
-<div><p class="copyright">Copyright © 2005, 2006, 2007 Red Hat, Inc. and others</p></div>
+</h3>
+</div>
+<div class="editor">
+<h4 class="editedby">Edited by</h4>
+<h3 class="editor">
+<span class="firstname">Piotr</span> <span class="surname">DrÄ…g</span>
+</h3>
+</div>
+</div></div>
+<div><p class="releaseinfo">Version 0.5.2 (2009-01-09)</p></div>
+<div><p class="copyright">Copyright © 2005, 2006, 2007, 2008, 2009 Red Hat, Inc. and others</p></div>
 <div><a href="legalnotice-opl.php">Legal Notice</a></div>
 <div><a href="rv-revhistory.php">Revision History</a></div>
 </div>
@@ -97,42 +85,39 @@
 <dt><span class="section"><a href="sn_accounts.php#sn-gpg-key">2.3. Making a GPG Key</a></span></dt>
 <dt><span class="section"><a href="sn_accounts.php#sn-apply-account">2.4. Applying for an Account</a></span></dt>
 <dt><span class="section"><a href="sn_accounts.php#sn-sign-cla">2.5. Signing the CLA</a></span></dt>
-<dt><span class="section"><a href="sn_accounts.php#sn-join-cvsl10n">2.6. Joining the <code class="systemitem">cvsl10n</code> Group</a></span></dt>
+<dt><span class="section"><a href="sn_accounts.php#sn-join-cvsl10n">2.6. Joining the cvsl10n Group</a></span></dt>
 <dt><span class="section"><a href="sn_accounts.php#sn-test-access">2.7. Testing Your Access</a></span></dt>
-<dt><span class="section"><a href="sn_accounts.php#sn-create-wikiacct">2.8. Creating a Wiki Account</a></span></dt>
-<dt><span class="section"><a href="sn_accounts.php#sn-intro-yourself">2.9. Introducing Yourself</a></span></dt>
-<dt><span class="section"><a href="sn_accounts.php#sn-bugzilla-account">2.10. Create a Bugzilla account</a></span></dt>
-<dt><span class="section"><a href="sn_accounts.php#sn-check-list">2.11. Checklist</a></span></dt>
+<dt><span class="section"><a href="sn_accounts.php#sn-intro-yourself">2.8. Introducing Yourself</a></span></dt>
+<dt><span class="section"><a href="sn_accounts.php#sn-bugzilla-account">2.9. Create a Bugzilla account</a></span></dt>
+<dt><span class="section"><a href="sn_accounts.php#sn-check-list">2.10. Checklist</a></span></dt>
 </dl></dd>
 <dt><span class="section"><a href="sn_translating_software.php">3. Translating Software</a></span></dt>
 <dd><dl>
 <dt><span class="section"><a href="sn_translating_software.php#sn-file-structure">3.1. File Structure</a></span></dt>
 <dt><span class="section"><a href="sn_translating_software.php#sn-obtain-translate-modules">3.2. Obtaining and Translating Modules</a></span></dt>
 <dt><span class="section"><a href="sn_translating_software.php#sn-commit-modules">3.3. Committing Modules</a></span></dt>
-<dt><span class="section"><a href="sn_translating_software.php#sn-add-new-file">3.4. Adding New .po file</a></span></dt>
+<dt><span class="section"><a href="sn_translating_software.php#sn-add-new-file">3.4. Adding New .po File</a></span></dt>
 <dt><span class="section"><a href="sn_translating_software.php#sn-proofreading">3.5. Proofreading</a></span></dt>
 </dl></dd>
 <dt><span class="section"><a href="sn_translating_docs.php">4. Translating Documentation</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="sn_translating_docs.php#sn-get-started">4.1. Getting Started</a></span></dt>
-<dt><span class="section"><a href="sn_translating_docs.php#sn-creating-common">4.2. Creating Common Files</a></span></dt>
+<dt><span class="section"><a href="sn_translating_docs.php#sn-creating-common">4.1. Creating Common Files</a></span></dt>
+<dt><span class="section"><a href="sn_translating_docs.php#sn-what-to-translate">4.2. What to Translate</a></span></dt>
 <dt><span class="section"><a href="sn_translating_docs.php#sn-translating-with-apps">4.3. Using Translation Applications</a></span></dt>
-<dt><span class="section"><a href="sn_translating_docs.php#sn-what-to-translate">4.4. What to Translate</a></span></dt>
 </dl></dd>
 <dt><span class="index"><a href="generated-index.php">Index</a></span></dt>
 </dl></div>
 <div class="section" lang="en-US">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both" id="sn-intro">1. Introduction</h2></div></div></div>
 <p>
-      This guide is a fast, simple, step-by-step set of instructions for
-      translating Fedora Project software and documents.  If you are interested in
-      better understanding the translation process involved, refer to
-      the Translation guide or the manual of the specific translation
-      tool.
-    </p>
+    This guide is a fast, simple, step-by-step set of instructions for
+    translating Fedora Project software and documents. If you are interested in
+    better understanding the translation process involved, refer to the
+    Translation guide or the manual of the specific translation tool.
+  </p>
 <p>
-	    More information can be found in FAQ, <a class="ulink" href="http://fedoraproject.org/wiki/L10N/FAQ" target="_top">http://fedoraproject.org/wiki/L10N/FAQ</a>.
-    </p>
+    More information can be found in FAQ, <a class="ulink" href="http://fedoraproject.org/wiki/L10N/FAQ" target="_top">http://fedoraproject.org/wiki/L10N/FAQ</a>.
+  </p>
 </div>
 </div>
 <div class="navfooter">


Index: legalnotice-opl.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/legalnotice-opl.php,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- legalnotice-opl.php	15 Aug 2008 05:17:46 -0000	1.7
+++ legalnotice-opl.php	6 Feb 2009 01:58:02 -0000	1.8
@@ -3,7 +3,7 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Legal Notice</title>
 <link rel="stylesheet" href="fedora.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
 </head>
 <?
 
@@ -24,7 +24,7 @@
 <a name="opl.terms"></a><ol type="I">
 <li>
 <a name="opl.require"></a><h2>
-<a name="id561758"></a>REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED
+<a name="id2660829"></a>REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED
 	VERSIONS</h2>
 <p>
 	Open Publication works may be reproduced and distributed in
@@ -58,7 +58,7 @@
 </li>
 <li>
 <a name="opl.copyright"></a><h2>
-<a name="id561796"></a>COPYRIGHT</h2>
+<a name="id2655732"></a>COPYRIGHT</h2>
 <p>
 	The copyright to each Open Publication is owned by its author(s)
 	or designee.
@@ -66,7 +66,7 @@
 </li>
 <li>
 <a name="opl.scope"></a><h2>
-<a name="id561605"></a>SCOPE OF LICENSE</h2>
+<a name="id2641695"></a>SCOPE OF LICENSE</h2>
 <p>
 	The following license terms apply to all Open Publication works,
 	unless otherwise explicitly stated in the document.
@@ -94,7 +94,7 @@
 </li>
 <li>
 <a name="opl.modified.works"></a><h2>
-<a name="id561637"></a>REQUIREMENTS ON MODIFIED WORKS</h2>
+<a name="id2647155"></a>REQUIREMENTS ON MODIFIED WORKS</h2>
 <p>
 	All modified versions of documents covered by this license,
 	including translations, anthologies, compilations and partial
@@ -126,7 +126,7 @@
 </li>
 <li>
 <a name="opl.good-practice"></a><h2>
-<a name="id563799"></a>GOOD-PRACTICE RECOMMENDATIONS</h2>
+<a name="id2659934"></a>GOOD-PRACTICE RECOMMENDATIONS</h2>
 <p>
 	In addition to the requirements of this license, it is requested
 	from and strongly recommended of redistributors that:
@@ -155,7 +155,7 @@
 </li>
 <li>
 <a name="opl.options"></a><h2>
-<a name="id561957"></a>LICENSE OPTIONS</h2>
+<a name="id2651295"></a>LICENSE OPTIONS</h2>
 <p>
 	The author(s) and/or publisher of an Open Publication-licensed
 	document may elect certain options by appending language to the


Index: rv-revhistory.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/rv-revhistory.php,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- rv-revhistory.php	15 Aug 2008 05:17:46 -0000	1.13
+++ rv-revhistory.php	6 Feb 2009 01:58:02 -0000	1.14
@@ -3,7 +3,7 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>Revision History</title>
 <link rel="stylesheet" href="fedora.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
+<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
 </head>
 <?
 
@@ -17,6 +17,26 @@
 <div class="revhistory"><table border="1" width="100%" summary="Revision history">
 <tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr>
 <tr>
+<td align="left">Revision 0.5.2</td>
+<td align="left">2009-01-09</td>
+<td align="left">NM</td>
+</tr>
+<tr><td align="left" colspan="3">
+        <p>
+          Bug #479346 fixed
+        </p>
+      </td></tr>
+<tr>
+<td align="left">Revision 0.5.1</td>
+<td align="left">2008-08-31</td>
+<td align="left">PD</td>
+</tr>
+<tr><td align="left" colspan="3">
+        <p>
+          General bug fixes
+        </p>
+      </td></tr>
+<tr>
 <td align="left">Revision 0.5</td>
 <td align="left">2008-04-18</td>
 <td align="left">NM</td>
@@ -25,7 +45,7 @@
         <p>
           Updated Accounts and Subscriptions chapter to conform the
           current FAS2. Some minor changes made to other chapters along
-          with bugs filed.
+          with bugs filed
         </p>
       </td></tr>
 <tr>
@@ -35,7 +55,7 @@
 </tr>
 <tr><td align="left" colspan="3">
         <p>
-          Replaced the links in the section 3.2.
+          Replaced the links in the section 3.2
         </p>
       </td></tr>
 <tr>
@@ -86,7 +106,7 @@
 <tr><td align="left" colspan="3">
         <p>
           Modified and updated all chapters to reflect latest
-          information including usage of transifex, moved repository
+          information including usage of Transifex, moved repository
           etc.
         </p>
       </td></tr>
@@ -220,7 +240,7 @@
 </tr>
 <tr><td align="left" colspan="3">
         <p>
-          Fix doc translation procedure to include other common files
+          Fix docs translation procedure to include other common files
           translations
         </p>
       </td></tr>
@@ -303,7 +323,7 @@
 </tr>
 <tr><td align="left" colspan="3">
         <p>
-          First round of editing.
+          First round of editing
         </p>
       </td></tr>
 <tr>


Index: sn_accounts.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/sn_accounts.php,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- sn_accounts.php	15 Aug 2008 05:17:46 -0000	1.13
+++ sn_accounts.php	6 Feb 2009 01:58:02 -0000	1.14
@@ -3,12 +3,12 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>2. Accounts and Subscriptions</title>
 <link rel="stylesheet" href="fedora.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
-<link rel="start" href="index.php" title="Translation Quick Start Guide">
+<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="home" href="index.php" title="Translation Quick Start Guide">
 <link rel="up" href="index.php" title="Translation Quick Start Guide">
 <link rel="prev" href="index.php" title="Translation Quick Start Guide">
 <link rel="next" href="sn_translating_software.php" title="3. Translating Software">
-<link rel="copyright" href="ln-legalnotice-opl.php" title="Legal Notice">
+<link rel="copyright" href="legalnotice-opl.php" title="Legal Notice">
 </head>
 <?
 
@@ -37,7 +37,7 @@
 <div class="titlepage"><div><div><h2 class="title" style="clear: both" id="sn_accounts">2. Accounts and Subscriptions</h2></div></div></div>
 <p>
     To become a Fedora Translator, you must sign up for accounts and
-    subscriptions as described in this chapter.  If you have questions,
+    subscriptions as described in this chapter. If you have questions,
     post them on the fedora-trans-list, or ask for help via Internet
     Relay Chat, or <acronym class="acronym">IRC</acronym>, at <code class="systemitem">irc.freenode.org</code> on channel
     <code class="systemitem">#fedora-l10n</code>.
@@ -46,61 +46,62 @@
 <div class="titlepage"><div><div><h3 class="title" id="signup-ml">2.1. Subscribing to the Mailing List</h3></div></div></div>
 <div class="procedure"><ol type="1">
 <li><p>
-	  Visit <a class="ulink" href="https://listman.redhat.com/mailman/listinfo/fedora-trans-list/" target="_top">https://listman.redhat.com/mailman/listinfo/fedora-trans-list/</a> 
-	  and subscribe to the main translation mailing list.
-	</p></li>
-<li><p>
-	  Wait for the confirmation email which contains a link to
-	  confirm your subscription. Click the link to confirm your
-	  subscription.
-	</p></li>
-<li><p>
-	  Check <a class="ulink" href="http://fedoraproject.org/wiki/L10N/Teams/" target="_top">http://fedoraproject.org/wiki/L10N/Teams/</a>
-	  to see if there is a special mailing list for your language.
-	  If so, subscribe to that list too.
-	</p></li>
+          Visit <a class="ulink" href="https://listman.redhat.com/mailman/listinfo/fedora-trans-list" target="_top">https://listman.redhat.com/mailman/listinfo/fedora-trans-list</a>
+          and subscribe to the main translation mailing list.
+        </p></li>
+<li><p>
+          Wait for the confirmation email which contains a link to
+          confirm your subscription. Click the link to confirm your
+          subscription.
+        </p></li>
+<li><p>
+          Check <a class="ulink" href="http://translate.fedoraproject.org/teams" target="_top">http://translate.fedoraproject.org/teams</a>
+          to see if there is a special mailing list for your language.
+          If so, subscribe to that list too.
+        </p></li>
 </ol></div>
 </div>
 <div class="section" lang="en-US">
 <div class="titlepage"><div><div><h3 class="title" id="sn-ssh-key">2.2. Making a SSH Key</h3></div></div></div>
 <p>
       If you already have an existing SSH key, you can use it for Fedora
-      work.  In that case, proceed to <a class="xref" href="sn_accounts.php#st-change-permissions" title="Step 2">Step 2</a> in the following procedure. If
+      work. In that case, proceed to <a class="xref" href="sn_accounts.php#st-change-permissions" title="Step 2">Step 2</a> in the following procedure. If
       you do not have a SSH key yet, start with the first step below:
     </p>
 <div class="procedure"><ol type="1">
 <li>
 <p>
-	  Enter the following command:
-	</p>
+          Enter the following command:
+        </p>
 <pre class="screen"><code class="command">ssh-keygen -t rsa</code></pre>
 <p>
-	  Accept the default location
-	  (<code class="filename">~/.ssh/id_rsa</code>) and enter a passphrase.
-	</p>
+          Accept the default location
+          (<code class="filename">~/.ssh/id_rsa</code>) and enter a passphrase.
+        </p>
 <div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Caution: Remember Your Passphrase">
 <tr>
 <td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="./stylesheet-images/caution.png"></td>
 <th align="left">Remember Your Passphrase</th>
 </tr>
 <tr><td align="left" valign="top"><p>
-	    You must have your passphrase to access to the CVS
-	    repository.  It cannot be recovered if you forget it.
-	  </p></td></tr>
+            You must have your passphrase to access to the CVS
+            repository. It cannot be recovered if you forget it.
+          </p></td></tr>
 </table></div>
 </li>
 <li>
 <a name="st-change-permissions"></a><p>
-	  Change permissions to your key and <code class="filename">.ssh</code>
-	  directory:
-	</p>
+          Change permissions to your key and <code class="filename">.ssh</code>
+          directory:
+        </p>
 <pre class="screen"><code class="command">chmod 700 ~/.ssh
 chmod 600 ~/.ssh/id_rsa
 chmod 644 ~/.ssh/id_rsa.pub</code></pre>
 </li>
 <li><p>
-		This public key (~/.ssh/id_rsa.pub) will be used for your Fedora account creation described  in <a class="xref" href="sn_accounts.php#sn-apply-account" title="2.4. Applying for an Account">Section 2.4, “Applying for an Account”</a>. 
-	</p></li>
+          This public key (~/.ssh/id_rsa.pub) will be used for your
+          Fedora account creation described in <a class="xref" href="sn_accounts.php#sn-apply-account" title="2.4. Applying for an Account">Section 2.4, “Applying for an Account”</a>.
+        </p></li>
 </ol></div>
 </div>
 <div class="section" lang="en-US">
@@ -108,14 +109,14 @@
 <div class="procedure"><ol type="1">
 <li>
 <p>
-	  Generate a key by typing in a command line:
-	</p>
+          Generate a key by typing in a command line:
+        </p>
 <pre class="screen"><code class="command">gpg --gen-key</code></pre>
 <p>
-	  A series of prompts guides you through the process. The
-	  default values suffice in almost all cases. Remember to choose
-	  a good password.
-	</p>
+          A series of prompts guides you through the process. The
+          default values suffice in almost all cases. Remember to choose
+          a good password.
+        </p>
 <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Choosing a Good Password">
 <tr>
 <td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td>
@@ -125,62 +126,80 @@
 <p>A good password:</p>
 <div class="itemizedlist"><ul type="disc">
 <li><p>consists of uppercase and lowercase letters,
-		numbers, punctuation, and other characters</p></li>
-<li><p>does not include any words or names, with or without
-		substitutions</p></li>
-<li><p>is not the same as any other password used for other
-		systems</p></li>
+                numbers, punctuation, and other characters</p></li>
+<li><p>does not include any words or names, with or
+                without substitutions</p></li>
+<li><p>is not the same as any other password used for
+                other systems</p></li>
 </ul></div>
 </td></tr>
 </table></div>
 </li>
 <li><p>
-	  In the resulting text, find your key ID in the statement that
-	  resembles "pub  1024D/1B2AFA1C". Your key ID is the 8
-	  character "word" after the slash (<code class="literal">/</code>).  In
-	  the previous example, the GPG Key ID is
-	  <code class="literal">1B2AFA1C</code>.  Write down your key ID.
-	</p></li>
+          In the resulting text, find your key ID in the statement that
+          resembles 'pub 1024D/1B2AFA1C'. Your key ID is the 8
+          character 'word' after the slash (<code class="literal">/</code>). In
+          the previous example, the GPG Key ID is
+          <code class="literal">1B2AFA1C</code>. Write down your key ID.
+        </p></li>
 <li>
 <p>
-	  Export your public key to a public server so that others can
-	  find it with the following command, substituting your key ID:
-	</p>
+          Export your public key to a public server so that others can
+          find it with the following command, substituting your key ID:
+        </p>
 <pre class="screen"><code class="command">gpg --keyserver subkeys.pgp.net --send-keys <em class="replaceable"><code>GPGKEYID</code></em></code></pre>
 </li>
 <li><p>
-		This GPG key ID will be used for your Fedora account creation described in <a class="xref" href="sn_accounts.php#sn-apply-account" title="2.4. Applying for an Account">Section 2.4, “Applying for an Account”</a>.
-  	</p></li>
+          This GPG key ID will be used for your Fedora account creation
+          described in <a class="xref" href="sn_accounts.php#sn-apply-account" title="2.4. Applying for an Account">Section 2.4, “Applying for an Account”</a>.
+        </p></li>
 </ol></div>
 </div>
 <div class="section" lang="en-US">
 <div class="titlepage"><div><div><h3 class="title" id="sn-apply-account">2.4. Applying for an Account</h3></div></div></div>
 <div class="procedure"><ol type="1">
 <li><p>
-	  To sign up for a Fedora account, first visit <a class="ulink" href="https://admin.fedoraproject.org/accounts/" target="_top">https://admin.fedoraproject.org/accounts/</a> and select
-	  <span class="guilabel"><strong>New Account</strong></span>. 
-	</p></li>
+          To sign up for a Fedora account, first visit <a class="ulink" href="https://admin.fedoraproject.org/accounts" target="_top">https://admin.fedoraproject.org/accounts</a> and select
+          <span class="guilabel"><strong>New Account</strong></span>.
+        </p></li>
 <li><p>
-	  Fill in <span class="guilabel"><strong>Username</strong></span>, <span class="guilabel"><strong>Full Name</strong></span> and <span class="guilabel"><strong>Email</strong></span>, and click <span class="guibutton"><strong>Sign up!</strong></span>. Your password will be emailed to you.
-	</p></li>
+          Fill in <span class="guilabel"><strong>Username</strong></span>,
+          <span class="guilabel"><strong>Full Name</strong></span> and <span class="guilabel"><strong>Email</strong></span>,
+          and click <span class="guibutton"><strong>Sign up!</strong></span>. Your password will
+          be emailed to you.
+        </p></li>
 <li><p>
-		Go back to <a class="ulink" href="https://admin.fedoraproject.org/accounts/" target="_top">https://admin.fedoraproject.org/accounts/</a> and log in with your password. The welcome page will be displayed, and it reminds you that CLA is not completed and that an SSH key is not submitted.
-	</p></li>
+          Go back to <a class="ulink" href="https://admin.fedoraproject.org/accounts" target="_top">https://admin.fedoraproject.org/accounts</a> and log in
+          with your password. The welcome page will be displayed, and it
+          reminds you that CLA is not completed and that an SSH key is
+          not submitted.
+        </p></li>
 <li><p>
-		To submit public SSH key and GPG key ID, click <span class="guilabel"><strong>My Account</strong></span> or go to <a class="ulink" href="https://admin.fedoraproject.org/accounts/user/edit" target="_top"> https://admin.fedoraproject.org/accounts/user/edit</a>. 
+          To submit public SSH key and GPG key ID, click <span class="guilabel"><strong>My
+          Account</strong></span> or go to <a class="ulink" href="https://admin.fedoraproject.org/accounts/user/edit" target="_top">https://admin.fedoraproject.org/accounts/user/edit</a>.
         </p></li>
 <li><p>
-	  In the Edit Account (user_name) page, enter your GPG key ID in <span class="guilabel"><strong>GPG Key ID:</strong></span> field. For pubic SSH key, click <span class="guilabel"><strong>Browse...</strong></span> button located next to <span class="guilabel"><strong>Public SSH Key:</strong></span> field and specify your public SSH key.
-  	</p></li>
+          In the Edit Account (user_name) page, enter your GPG key ID in
+          <span class="guilabel"><strong>GPG Key ID:</strong></span> field. For the public SSH
+          key, click <span class="guilabel"><strong>Browse...</strong></span> button located next
+          to <span class="guilabel"><strong>Public SSH Key:</strong></span> field and specify your
+          public SSH key.
+        </p></li>
 <li><p>
-	  <span class="guilabel"><strong>Telephone Number</strong></span> and <span class="guilabel"><strong>Postal Address</strong></span> fields are also required to fill in for signing the CLA. These information is NOT accessible by others except admin groups. Please refer to Fedora Privacy Policy at  <a class="ulink" href="http://fedoraproject.org/wiki/Legal/PrivacyPolicy" target="_top"> http://fedoraproject.org/wiki/Legal/PrivacyPolicy</a>.
-  	</p></li>
+          <span class="guilabel"><strong>Telephone Number</strong></span> and <span class="guilabel"><strong>Postal
+          Address</strong></span> fields are also required to fill in for
+          signing the CLA. These information is NOT accessible by others
+          except admin groups. Please refer to Fedora Privacy Policy at
+          <a class="ulink" href="http://fedoraproject.org/wiki/Legal/PrivacyPolicy" target="_top">http://fedoraproject.org/wiki/Legal/PrivacyPolicy</a>.
+        </p></li>
 <li><p>
-	  Other fields will be displayed by any other member by visitng the user's view page.
-	</p></li>
+          Other fields will be displayed by any other member by visiting
+          the user's view page.
+        </p></li>
 <li><p>
-	  Now click <span class="guilabel"><strong>Save!</strong></span> located at the bottom of this page to save your information.
-	</p></li>
+          Now click <span class="guilabel"><strong>Save!</strong></span> located at the bottom of
+          this page to save your information.
+        </p></li>
 </ol></div>
 </div>
 <div class="section" lang="en-US">
@@ -190,34 +209,54 @@
       <acronym class="acronym">CLA</acronym>.
     </p>
 <div class="procedure"><ol type="1">
-<li><p>Visit <a class="ulink" href="https://admin.fedoraproject.org/accounts/" target="_top">https://admin.fedoraproject.org/accounts/</a> and login your account using your username and password obtained from the previous process.
-	</p></li>
 <li><p>
-	  In the Welcome page, click <span class="guilabel"><strong>complete the CLA</strong></span> or go to <a class="ulink" href="https://admin.fedoraproject.org/accounts/user/edit" target="_top"> https://admin.fedoraproject.org/accounts/user/edit</a>.
-	</p></li>
+          Visit <a class="ulink" href="https://admin.fedoraproject.org/accounts" target="_top">https://admin.fedoraproject.org/accounts</a>
+          and login your account using your user name and password
+          obtained from the previous process.
+        </p></li>
+<li><p>
+          In the Welcome page, click <span class="guilabel"><strong>complete the
+          CLA</strong></span> or go to <a class="ulink" href="https://admin.fedoraproject.org/accounts/user/edit" target="_top">https://admin.fedoraproject.org/accounts/user/edit</a>.
+        </p></li>
 <li><p>
-	  If the information of telephone number and postal address have not been provided yet, the Edit Account (user_name) page will be appeared. Otherwise Fedora Contributor License Agreement page will be displayed. Read through the agreement carefully and click <span class="guibutton"><strong>I agree</strong></span> if you are happy to do so. 
-	</p></li>
+          If the information of telephone number and postal address have
+          not been provided yet, the Edit Account (user_name) page will
+          be appeared. Otherwise Fedora Contributor License Agreement
+          page will be displayed. Read through the agreement carefully
+          and click <span class="guibutton"><strong>I agree</strong></span> if you are happy to
+          do so.
+        </p></li>
 <li><p>
-	  The user-view page is appeared and shows the <span class="guilabel"><strong>CLA:</strong></span> field as <span class="guilabel"><strong>CLA Done</strong></span>.
-	</p></li>
+          The user-view page is appeared and shows the
+          <span class="guilabel"><strong>CLA:</strong></span> field as
+          <span class="guilabel"><strong>CLA Done</strong></span>.
+        </p></li>
 </ol></div>
 </div>
 <div class="section" lang="en-US">
 <div class="titlepage"><div><div><h3 class="title" id="sn-join-cvsl10n">2.6. Joining the <code class="systemitem">cvsl10n</code> Group</h3></div></div></div>
 <div class="procedure"><ol type="1">
 <li><p>
-	  In the user-view page, click <span class="guilabel"><strong>Apply For a new Group</strong></span> located in the left side bar. If you like to do this step sometime later, your user-view page can be reached at <a class="ulink" href="https://admin.fedoraproject.org/accounts/user/view/user_name" target="_top">https://admin.fedoraproject.org/accounts/user/view/user_name</a>.
-	 </p></li>
+          In the user-view page, click <span class="guilabel"><strong>Apply for a New
+          Group</strong></span> located in the left side bar. If you like to
+          do this step sometime later, your user-view page can be
+          reached at <a class="ulink" href="https://admin.fedoraproject.org/accounts/user/view/user_name" target="_top">https://admin.fedoraproject.org/accounts/user/view/user_name</a>.
+        </p></li>
 <li><p>
-	  Click <span class="guilabel"><strong>C</strong></span> of the alphabet, it returns the list of the groups starting with 'c'.
-	</p></li>
+          Click <span class="guilabel"><strong>C</strong></span> of the alphabet, it returns the
+          list of the groups starting with 'c'.
+        </p></li>
 <li><p>
-	  Find the group name <span class="guilabel"><strong>cvsl10n</strong></span> in the list and click <span class="guilabel"><strong>Apply</strong></span>. 
-	</p></li>
+          Find the group name <span class="guilabel"><strong>cvsl10n</strong></span> in the list
+          and click <span class="guilabel"><strong>Apply</strong></span>.
+        </p></li>
 <li><p>
-	  An administrator is notified of your application, and offers to sponsor you. This may take between an hour and a few days. The membership notification will be emailed to you once sponsored. 
-	</p></li>
+          All administrators are notified of your application.
+          Introduce yourself by following <a class="xref" href="sn_accounts.php#sn-intro-yourself" title="2.8. Introducing Yourself">Section 2.8, “Introducing Yourself”</a>. Then your language
+          administrator offers to sponsor you. This may take between an
+          hour and a few days. The membership notification will be
+          emailed to you once sponsored.
+        </p></li>
 </ol></div>
 <div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Caution">
 <tr>
@@ -225,11 +264,11 @@
 <th align="left">Caution</th>
 </tr>
 <tr><td align="left" valign="top"><p>
-	The rest of the steps help you test your access and grant you
-	privileges to all the Fedora infrastructure you might need in
-	the near future. Language maintainers and people starting new
-	languages should follow them. Although they are optional for
-	translations, everyone is encouraged to follow them.
+        The rest of the steps help you test your access and grant you
+        privileges to all the Fedora infrastructure you might need in the
+        near future. Language maintainers and people starting new
+        languages should follow them. Although they are optional for
+        translations, everyone is encouraged to follow them.
       </p></td></tr>
 </table></div>
 </div>
@@ -238,16 +277,17 @@
 <div class="procedure"><ol type="1">
 <li>
 <p>
-	  Install the <span class="package">cvs</span> package, if it is not
-	  already installed, with the following command:
-	</p>
+          Install the <span class="package">cvs</span> package, if it is not
+          already installed, with the following command:
+        </p>
 <pre class="screen"><code class="command">su -c 'yum install cvs'</code></pre>
 </li>
 <li>
 <p>
-	  Checkout some PO files with the following command, substituting your
-	  username and providing your SSH key passphrase when prompted:
-	</p>
+          Checkout some PO files with the following command,
+          substituting your user name and providing your SSH key
+          passphrase when prompted:
+        </p>
 <pre class="screen"><code class="command">export CVSROOT=:ext:<em class="replaceable"><code>username</code></em>@cvs.fedoraproject.org:/cvs/l10n
 cvs co web
 ls web/flpweb/po</code></pre>
@@ -255,66 +295,49 @@
 </ol></div>
 </div>
 <div class="section" lang="en-US">
-<div class="titlepage"><div><div><h3 class="title" id="sn-create-wikiacct">2.8. Creating a Wiki Account</h3></div></div></div>
+<div class="titlepage"><div><div><h3 class="title" id="sn-intro-yourself">2.8. Introducing Yourself</h3></div></div></div>
 <div class="procedure"><ol type="1">
 <li><p>
-	  A current wiki user can give you Edit access on the wiki. Contact someone from the Edit Group at <a class="ulink" href="http://fedoraproject.org/wiki/EditGroup/" target="_top">http://fedoraproject.org/wiki/EditGroup/</a>, or add your name to the EditGroupQueue at <a class="ulink" href="http://fedoraproject.org/wiki/EditGroupQueue/" target="_top">http://fedoraproject.org/wiki/EditGroupQueue/</a>, and someone will add you shortly.
-	</p></li>
-<li><p>
-	  Once added, Visit <a class="ulink" href="http://fedoraproject.org/wiki/UserPreferences/" target="_top">http://fedoraproject.org/wiki/UserPreferences/</a> and create a profile page. For your username, choose a name like 'FirstnameLastname' and select <span class="guilabel"><strong>Create Profile</strong></span>.
-	</p></li>
-<li><p>
-	  If you are starting a new language, or want to become the
-	  maintainer of one, add your information on the L10N/Teams page
-	  at <a class="ulink" href="http://fedoraproject.org/wiki/L10N/Teams/" target="_top">http://fedoraproject.org/wiki/L10N/Teams/</a>.
-	</p></li>
-</ol></div>
-</div>
-<div class="section" lang="en-US">
-<div class="titlepage"><div><div><h3 class="title" id="sn-intro-yourself">2.9. Introducing Yourself</h3></div></div></div>
-<div class="procedure"><ol type="1">
+          Create a personal page at <a class="ulink" href="http://fedoraproject.org/wiki/User:Username" target="_top">http://fedoraproject.org/wiki/User:Username</a>. This is
+          very useful for Fedora contributors to get to know and contact
+          each other.
+        </p></li>
 <li><p>
-	  Once you have edit access on the wiki, create a personal
-	  page.  
-	  at a URL like this: <a class="ulink" href="http://fedoraproject.org/wiki/FirstnameLastname/" target="_top">http://fedoraproject.org/wiki/FirstnameLastname/</a>.
-	  This is very useful for Fedora contributors to get to know and
-	  contact each other.
-	</p></li>
-<li><p>
-	  Post a short self introduction <a class="ulink" href="http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction/" target="_top">http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction/</a> 
-	  to the <code class="systemitem">fedora-trans-list</code> mailing list
-	  and to the list of your local team.
-	</p></li>
+          Post a short self introduction <a class="ulink" href="http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction" target="_top">http://fedoraproject.org/wiki/L10N/Join/SelfIntroduction</a>
+          to the <code class="systemitem">fedora-trans-list</code> mailing list
+          and to the list of your local team. Please remember to include
+          your FAS username and your language. With this information,
+          sponsor can identify you for 'cvsl10n' group joining approval.
+        </p></li>
 </ol></div>
 </div>
 <div class="section" lang="en-US">
-<div class="titlepage"><div><div><h3 class="title" id="sn-bugzilla-account">2.10. Create a Bugzilla account</h3></div></div></div>
+<div class="titlepage"><div><div><h3 class="title" id="sn-bugzilla-account">2.9. Create a Bugzilla account</h3></div></div></div>
 <p>
-      Visit <a class="ulink" href="https://bugzilla.redhat.com/bugzilla/createaccount.cgi/" target="_top">https://bugzilla.redhat.com/bugzilla/createaccount.cgi/</a>
+      Visit <a class="ulink" href="https://bugzilla.redhat.com/bugzilla/createaccount.cgi" target="_top">https://bugzilla.redhat.com/bugzilla/createaccount.cgi</a>
       to create a Bugzilla account.
     </p>
 </div>
 <div class="section" lang="en-US">
-<div class="titlepage"><div><div><h3 class="title" id="sn-check-list">2.11. Checklist</h3></div></div></div>
+<div class="titlepage"><div><div><h3 class="title" id="sn-check-list">2.10. Checklist</h3></div></div></div>
 <p>
       You should now have the following:
     </p>
 <div class="itemizedlist"><ul type="disc">
 <li><p>Subscription to fedora-trans-list mailing list
-	  and your locale-specific mailing list, if there is
-	  one</p></li>
+        and your locale-specific mailing list, if there is
+        one</p></li>
 <li><p>A SSH key</p></li>
 <li><p>A GPG key</p></li>
 <li><p>A Fedora account</p></li>
 <li><p>Membership in the <code class="systemitem">cvsl10n</code>
-	  group</p></li>
-<li><p>A wiki account</p></li>
+      group</p></li>
 <li><p>Your language and translation team appear on
-	  <a class="ulink" href="http://fedoraproject.org/wiki/L10N/Teams/" target="_top">http://fedoraproject.org/wiki/L10N/Teams/</a></p></li>
+        <a class="ulink" href="http://translate.fedoraproject.org/teams" target="_top">http://translate.fedoraproject.org/teams</a></p></li>
 <li><p>A Bugzilla account</p></li>
 <li><p>A personal homepage on the wiki</p></li>
 <li><p>A self-introduction sent to the mailing
-	  list</p></li>
+      list</p></li>
 </ul></div>
 <p>
       Sit back and enjoy your achievement. You are now a fully


Index: sn_translating_docs.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/sn_translating_docs.php,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- sn_translating_docs.php	15 Aug 2008 05:17:46 -0000	1.13
+++ sn_translating_docs.php	6 Feb 2009 01:58:02 -0000	1.14
@@ -3,12 +3,12 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>4. Translating Documentation</title>
 <link rel="stylesheet" href="fedora.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
-<link rel="start" href="index.php" title="Translation Quick Start Guide">
+<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="home" href="index.php" title="Translation Quick Start Guide">
 <link rel="up" href="index.php" title="Translation Quick Start Guide">
 <link rel="prev" href="sn_translating_software.php" title="3. Translating Software">
 <link rel="next" href="generated-index.php" title="Index">
-<link rel="copyright" href="ln-legalnotice-opl.php" title="Legal Notice">
+<link rel="copyright" href="legalnotice-opl.php" title="Legal Notice">
 </head>
 <?
 
@@ -35,304 +35,250 @@
 </div>
 <div class="section" lang="en-US">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both" id="sn_translating_docs">4. Translating Documentation</h2></div></div></div>
-<p>
-    To translate Fedora documentation, become a member of the
-    <code class="systemitem">cvsl10n</code> group.  For more information on
-    account and subscriptions, refer to <a class="xref" href="sn_accounts.php" title="2. Accounts and Subscriptions">Section 2, “Accounts and Subscriptions”</a>.
-    </p>
-<p>
-	    To translate documentation, you need a Fedora 5 or later system with the following packages installed:
-    </p>
-<div class="itemizedlist"><ul type="disc">
-<li><p><span class="package">gnome-doc-utils</span></p></li>
-<li><p><span class="package">xmlto</span></p></li>
-<li><p><span class="package">make</span></p></li>
-<li><p><span class="package">w3m</span></p></li>
-</ul></div>
-<p>The <span class="package">gnome-doc-utils</span> package provides the
-    <code class="command">xml2po</code> command, and does not require you to
-    install the GNOME desktop environment.  The <span class="package">xmlto</span>, <span class="package">make</span> and <span class="package">w3m</span> packages contain tools necessary for
-    testing document builds and translations.</p>
-<p>
-      To install these packages, use the following command:
-    </p>
-<pre class="screen"><code class="command">su -c 'yum install gnome-doc-utils xmlto make w3m'</code></pre>
-<div class="section" lang="en-US">
-<div class="titlepage"><div><div><h3 class="title" id="sn-get-started">4.1. Getting Started</h3></div></div></div>
-<p>
-      The Fedora documentation is stored in a CVS repository under the
-      directory <code class="filename">docs/</code>.  To list the available
-      modules, run the following commands (where <em class="replaceable"><code>username</code></em> is replaced with your Fedora account username):
-    </p>
-<pre class="screen"><code class="command">export CVSROOT=:ext:<em class="replaceable"><code>username</code></em>@cvs.fedoraproject.org:/cvs/docs</code>
-<code class="command">cvs co -c</code></pre>
-<p>
-      To download a module to translate, list the current modules in the
-      repository and then check out that module.  You must also check
-      out the <code class="filename">docs-common</code> module to work with some
-      modules.
-    </p>
-<pre class="screen"><code class="command">cvs co release-notes docs-common</code></pre>
-<p>
-      Some modules are <em class="firstterm">release specific</em>, meaning
-      that they have a <em class="firstterm">branch</em>, or subdirectory,
-      for each release of Fedora:
-    </p>
-<pre class="screen"><strong class="userinput"><code>ls release-notes/</code></strong>
-<code class="computeroutput">CVS  F-7  FC-5  FC-6  FC3  FC4  devel</code></pre>
-<p>
-      The <code class="filename">devel/</code> branch is used
-      for the <span class="emphasis"><em>upcoming</em></span> release of Fedora. Often
-      translators work on this branch, and port changes back to previous
-      branches as required.
-    </p>
-<div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: How to get the smallest check out">
+<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Some Fedora Documentation Has Moved">
 <tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td>
-<th align="left">How to get the smallest check out</th>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td>
+<th align="left">
+<a name="nt-docs_moved_to_git"></a>Some Fedora Documentation Has Moved</th>
 </tr>
-<tr><td align="left" valign="top">
-<p>
-	Another method is to use a module alias.  Using the alias
-	<code class="filename">release-notes-<em class="replaceable"><code>version</code></em></code> 
-	checks out just the <em class="replaceable"><code>version</code></em>
-	specified. This method brings the versioned subdirectory and the
-	<code class="filename">docs-common</code> module into one directory,
-	<code class="filename">release-notes-<em class="replaceable"><code>version</code></em></code>. 
-	For example, to get just the <code class="filename">-devel</code>
-	version, use this command:
-      </p>
-<pre class="screen"><code class="command">cvs co release-notes-devel</code></pre>
-<p>
-	Everything needed to build the document is now in the directory
-	<code class="filename">release-notes-devel/</code>:
-      </p>
-<pre class="screen"><code class="command">ls release-notes-devel</code>
-<code class="command">CVS  docs-common  release-notes</code></pre>
-</td></tr>
+<tr><td align="left" valign="top"><p>
+      Current Fedora Documentation material is now maintained in the
+      Fedora Hosted system as <code class="command">git</code> repositories.
+      This includes the latest versions of the common documentation
+      build tools. You do not need to install <code class="command">git</code>
+      to translate these materials. Instead, use Transifex, as
+      described in previous sections, to translate these documentation
+      materials.
+    </p></td></tr>
 </table></div>
-</div>
 <div class="section" lang="en-US">
-<div class="titlepage"><div><div><h3 class="title" id="sn-creating-common">4.2. Creating Common Files</h3></div></div></div>
+<div class="titlepage"><div><div><h3 class="title" id="sn-creating-common">4.1. Creating Common Files</h3></div></div></div>
 <p>
-	Only if you are creating the first-ever translation for a locale, you
-	must first translate some common files used in all documents for
-	your locale.  The common files are located in <code class="filename">docs-common/common/</code>.
+        If you are creating the first-ever translation for a locale, you
+        must first translate some common files used in all documents for
+        your locale. The common files are located in the Fedora Hosted
+        repository for the <span class="package">fedora-doc-utils</span>
+        package.
       </p>
 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Example Locale is pt_BR">
 <tr>
 <td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td>
-<th align="left">Example Locale is <em class="replaceable"><code>pt_BR</code></em>
-</th>
+<th align="left">Example Locale is pt_BR</th>
 </tr>
-<tr><td align="left" valign="top"><p>The following examples use the locale code
-	<em class="replaceable"><code>pt_BR</code></em>.  Substitute your locale code
-      in these commands as necessary.</p></td></tr>
+<tr><td align="left" valign="top"><p>
+          The following examples use the locale code
+          <em class="replaceable"><code>pt_BR</code></em>. Substitute your locale code in
+          these commands as necessary.
+        </p></td></tr>
 </table></div>
 <div class="procedure"><ol type="1">
 <li><p>
-	    Read the <code class="filename">README.txt</code> file in the
-	    <code class="filename">docs-common/common/entities</code> and
-	    follow the directions to create new entities.
-	  </p></li>
+          Visit Transifex at <a class="ulink" href="http://translate.fedoraproject.org" target="_top">http://translate.fedoraproject.org</a>, and translate
+          the module <span class="guilabel"><strong>Docs :: Common entities</strong></span>, using
+          the same procedure shown in <a class="xref" href="sn_translating_software.php" title="3. Translating Software">Section 3, “Translating Software”</a>.
+        </p></li>
+<li><p>
+          Visit the <span class="package">fedora-doc-utils</span> hosted project
+          at <a class="ulink" href="https://fedorahosted.org/fedora-doc-utils" target="_top">https://fedorahosted.org/fedora-doc-utils</a>.
+          Select the <span class="guilabel"><strong>Login</strong></span> link and use your
+          Fedora Account System login and password to login.
+        </p></li>
 <li>
 <p>
-	    Once you have created common entities for your locale and
-	    committed the results to CVS, create locale files for the
-	    legal notices:
-	  </p>
-<pre class="screen"><code class="command">cd docs-common/common/</code>
-<code class="command">cp legalnotice-opl-en_US.xml legalnotice-opl-<em class="replaceable"><code>pt_BR</code></em>.xml</code>
-<code class="command">cp legalnotice-relnotes-en_US.xml legalnotice-relnotes-<em class="replaceable"><code>pt_BR</code></em>.xml</code>	
-</pre>
-<div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Do Not Translate Legal Notice">
+          Select the <span class="guilabel"><strong>New ticket</strong></span> link to file a
+          new ticket. Use the following information to fill in the
+          ticket:
+        </p>
+<div class="itemizedlist"><ul type="disc">
+<li><p>
+              Summary: New language support request:
+              <em class="replaceable"><code>pt_BR</code></em>
+            </p></li>
+<li><p>
+              Priority: minor
+            </p></li>
+<li><p>
+              Component: language support
+            </p></li>
+</ul></div>
+<p>
+          You may leave the details blank or fill in information as
+          desired.
+        </p>
+<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Attach Files if Necessary">
 <tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td>
-<th align="left">Do Not Translate Legal Notice</th>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td>
+<th align="left">Attach Files if Necessary</th>
 </tr>
 <tr><td align="left" valign="top"><p>
-	      To ensure it is legally equivalent in all locales, do not
-	      translate the OPL.
-	    </p></td></tr>
+            If you have any problems submitting PO files using
+            Transifex, you can attach them to the Trac ticket.
+          </p></td></tr>
 </table></div>
 </li>
-<li>
-<p>
-	    Then commit those file to CVS also:
-	  </p>
-<pre class="screen"><code class="command">cvs add legalnotice-*-<em class="replaceable"><code>pt_BR</code></em>.xml</code>
-<code class="command">cvs ci -m 'Added legal notices for <em class="replaceable"><code>pt_BR</code></em>' legalnotice-*-<em class="replaceable"><code>pt_BR</code></em>.xml</code></pre>
-</li>
-<li>
-<p>
-	    Next, build the draft watermark for your locale in the
-	    <code class="filename">docs-common/images/</code>
-	    folder:
-	  </p>
-<pre class="screen"><code class="command">cd docs-common/images/</code>
-<code class="command">cp watermark-en_US.svg watermark-<em class="replaceable"><code>pt_BR</code></em>.svg</code></pre>
-<p>
-	    Translate the <code class="sgmltag-element">text</code>
-	    elements in the SVG.  Then add your locale's SVG file to the
-	    <code class="filename">Makefile</code>, produce the PNG and commit
-	    the results:
-	  </p>
-<pre class="screen"><code class="command">make watermark-<em class="replaceable"><code>pt_BR</code></em>.png</code>
-<code class="command">cvs add watermark-<em class="replaceable"><code>pt_BR</code></em>*</code>
-<code class="command">cvs ci -m 'Added <em class="replaceable"><code>pt_BR</code></em> images' Makefile watermark-<em class="replaceable"><code>pt_BR</code></em>*</code></pre>
-</li>
 </ol></div>
-<div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Build Errors">
+</div>
+<div class="section" lang="en-US">
+<div class="titlepage"><div><div><h3 class="title" id="sn-what-to-translate">4.2. What to Translate</h3></div></div></div>
+<p>
+      The most important documentation for each release of Fedora
+      are the following:
+    </p>
+<div class="itemizedlist"><ul type="disc">
+<li><p><span class="guilabel"><strong>Docs :: Common entities</strong></span></p></li>
+<li><p><span class="guilabel"><strong>Docs :: Release Notes</strong></span></p></li>
+<li><p><span class="guilabel"><strong>Docs :: Installation Guide</strong></span></p></li>
+<li><p><span class="guilabel"><strong>Docs :: About Fedora</strong></span></p></li>
+<li><p><span class="guilabel"><strong>Docs :: Readme</strong></span></p></li>
+<li><p><span class="guilabel"><strong>Docs :: Readme Burning ISOs</strong></span></p></li>
+<li><p><span class="guilabel"><strong>Docs :: Readme Live Image</strong></span></p></li>
+</ul></div>
+</div>
+<div class="section" lang="en-US">
+<div class="titlepage"><div><div><h3 class="title" id="sn-translating-with-apps">4.3. Using Translation Applications</h3></div></div></div>
+<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: For Advanced Users">
 <tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td>
-<th align="left">Build Errors</th>
+<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td>
+<th align="left">For Advanced Users</th>
 </tr>
 <tr><td align="left" valign="top"><p>
-	    If you do not create these common entities, building your
-	    document may fail.
-	  </p></td></tr>
+        Most casual translators do not need to read this section, and
+        should use Transifex instead. Translators who are used to
+        command-line tools can refer to this section for guidance.
+      </p></td></tr>
 </table></div>
-</div>
-<div class="section" lang="en-US">
-<div class="titlepage"><div><div><h3 class="title" id="sn-translating-with-apps">4.3. Using Translation Applications</h3></div></div></div>
-<p>The <code class="filename">po/</code> directory
+<p>
+      The <code class="filename">po/</code> directory
       contains the <code class="filename">.po</code> files used
-      to translate content.  It also contains a <code class="filename">.pot</code> file, or PO template, which is
+      to translate content. It also contains a <code class="filename">.pot</code> file, or PO template, which is
       used to create new <code class="filename">.po</code>
-      files when necessary.</p>
+      files when necessary.
+    </p>
 <p>
-	If the <code class="filename">po/</code> directory does
-	not exist, you can create it and the translation template file
-	with the following commands:
-      </p>
+      If the <code class="filename">po/</code> directory does
+      not exist, you can create it and the translation template file
+      with the following commands:
+    </p>
 <pre class="screen"><code class="command">mkdir po</code>
 <code class="command">cvs add po/</code>
-<code class="command">make pot</code>
-</pre>
+<code class="command">make pot</code></pre>
 <div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Caution: Do Not Make Manual POT Changes">
 <tr>
 <td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="./stylesheet-images/caution.png"></td>
 <th align="left">Do Not Make Manual POT Changes</th>
 </tr>
-<tr><td align="left" valign="top"><p>Authors and editors generate the POT file from the source
-	XML files, which overwrite any manual changes to a POT file.  If
-	you find a problem in the original messages of a POT file, visit
-	Bugzilla at <a class="ulink" href="https://bugzilla.redhat.com" target="_top">https://bugzilla.redhat.com</a> to file a bug against the document.</p></td></tr>
+<tr><td align="left" valign="top"><p>
+        Authors and editors generate the POT file from the source XML
+        files, which overwrite any manual changes to a POT file. If you
+        find a problem in the original messages of a POT file, visit
+        Bugzilla at <a class="ulink" href="https://bugzilla.redhat.com" target="_top">https://bugzilla.redhat.com</a> to file a bug against the document.
+      </p></td></tr>
 </table></div>
 <p>
-	To work with a <code class="filename">.po</code> editor
-	like <span class="application"><strong>KBabel</strong></span> or
-	<span class="application"><strong>gtranslator</strong></span>, follow these
-	steps.
-      </p>
+      To work with a <code class="filename">.po</code> editor
+      like <span class="application"><strong>Lokalize</strong></span> or
+      <span class="application"><strong>gtranslator</strong></span>, follow these
+      steps.
+    </p>
 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Example Locale is pt_BR">
 <tr>
 <td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td>
-<th align="left">Example Locale is <em class="replaceable"><code>pt_BR</code></em>
-</th>
+<th align="left">Example Locale is pt_BR</th>
 </tr>
-<tr><td align="left" valign="top"><p>The following examples use the locale code
-	<em class="replaceable"><code>pt_BR</code></em>.  Substitute your locale code
-      in these commands as necessary.</p></td></tr>
+<tr><td align="left" valign="top"><p>
+        The following examples use the locale code
+        <em class="replaceable"><code>pt_BR</code></em>. Substitute your locale code in
+        these commands as necessary.
+      </p></td></tr>
 </table></div>
 <div class="procedure"><ol type="1">
 <li>
 <p class="title"><b>Change Directory</b></p>
 <p>
-	    In a terminal, go to the directory of the document you want
-	    to translate:
-	  </p>
+          In a terminal, go to the directory of the document you want to
+          translate:
+        </p>
 <pre class="screen"><code class="command">cd ~/docs/translation-quick-start-guide/</code></pre>
 </li>
 <li>
 <p class="title"><b>Add Locale to List</b></p>
-<p>To add your locale, you must locate and change the
-	    appropriate locale list.  Some documents are using the
-	    <code class="filename">po/LINGUAS</code> file, as standardized in the
-	    GNOME project, to track locales.  Some documents have not
-	    been updated to this standard yet.  If you find the module
-	    you are translating has not been updated, notify the Fedora Documentation Project
-	    or file a bug using Bugzilla.</p>
-<p>Add your translation language code to the list in the
-	  <code class="filename">po/LINGUAS</code> file using your preferred editor. For example,
-  	  </p>
+<p>
+          To add your locale, you must locate and change the
+          appropriate locale list. Some documents are using the
+          <code class="filename">po/LINGUAS</code> file, as standardized in the
+          GNOME project, to track locales. Some documents have not
+          been updated to this standard yet. If you find the module
+          you are translating has not been updated, notify the Fedora Documentation Project
+          or file a bug using Bugzilla.
+        </p>
+<p>
+          Add your translation language code to the list in the
+          <code class="filename">po/LINGUAS</code> file using your preferred
+          editor. For example,
+        </p>
 <pre class="screen"><code class="command">vi po/LINGUAS</code></pre>
 <p>
-	    Press 'a' to modify and add your language code. Once added, save it and exit the editor.
-    	  </p>
-<p><span class="emphasis"><em>Please remember to keep the list in alphabetical order.</em></span> 
-	  </p>
+          Press 'a' to modify and add your language code. Once added, save it and exit the editor.
+        </p>
+<p>
+          <span class="emphasis"><em>Please remember to keep the list in alphabetical
+          order.</em></span>
+        </p>
 </li>
 <li>
 <p class="title"><b>Create PO File</b></p>
 <p>
-	    Make a new <code class="filename">.po</code> file
-	    for your locale:
-	  </p>
+          Make a new <code class="filename">.po</code> file
+          for your locale:
+        </p>
 <pre class="screen"><code class="command">make po/<em class="replaceable"><code>pt_BR</code></em>.po</code></pre>
 </li>
 <li>
 <p class="title"><b>Translate Strings</b></p>
 <p>
-	  To translate the file, use the same application used to
-	  translate software:
-	  </p>
-<pre class="screen"><code class="command">kbabel po/<em class="replaceable"><code>pt_BR</code></em>.po</code></pre>
+          To translate the file, use the same application used to
+          translate software:
+        </p>
+<pre class="screen"><code class="command">lokalize po/<em class="replaceable"><code>pt_BR</code></em>.po</code></pre>
 </li>
 <li>
 <p class="title"><b>Check Integrity</b></p>
 <p>
-	  Before committing your changes, check the integrity of the XML
-	  with the following command.  This ensures a sane build for all
-	  users.
-     </p>
+          Before committing your changes, check the integrity of the
+          XML with the following command. This ensures a sane build
+          for all users.
+        </p>
 <pre class="screen"><code class="command">make html-<em class="replaceable"><code>pt_BR</code></em></code></pre>
-<p>You can read the resulting HTML files with a Web
-	  browser. If no HTML is created, the error message(s) can be found in the output. Please resolve them before commit.</p>
+<p>
+          You can read the resulting HTML files with a Web browser. If
+          no HTML is created, the error message(s) can be found in the
+          output. Please resolve them before commit.
+        </p>
 <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Always Test Your Translation">
 <tr>
 <td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td>
 <th align="left">Always Test Your Translation</th>
 </tr>
 <tr><td align="left" valign="top"><p>
-	    Do not go to the next step or commit changes until you test
-	    your work in this step. Erroneous changes can break
-	    documents for other users, editors, and automated
-	    applications.</p></td></tr>
+            Do not go to the next step or commit changes until you
+            test your work in this step. Erroneous changes can break
+            documents for other users, editors, and automated
+            applications.
+          </p></td></tr>
 </table></div>
 </li>
 <li>
 <p class="title"><b>Commit Work</b></p>
 <p>
-		Before commit your <code class="filename">.po</code> file, always make sure that the html has been generated successfully. You may note the percent complete or some other useful message at commit time.
-	  </p>
+          Before commit your <code class="filename">.po</code>
+          file, always make sure that the html has been generated
+          successfully. You may note the percent complete or some other
+          useful message at commit time.
+        </p>
 <pre class="screen"><code class="command">cvs ci -m <em class="replaceable"><code>'Translating... 400/10/126'</code></em> po/<em class="replaceable"><code>pt_BR</code></em>.po</code></pre>
 </li>
 </ol></div>
 </div>
-<div class="section" lang="en-US">
-<div class="titlepage"><div><div><h3 class="title" id="sn-what-to-translate">4.4. What to Translate</h3></div></div></div>
-<p>
-      The most important docs modules/directories for each release are
-      the following:
-    </p>
-<div class="itemizedlist"><ul type="disc">
-<li><p><code class="filename">docs-common/common/entities</code></p></li>
-<li><p><code class="filename">release-notes/devel</code></p></li>
-<li><p><code class="filename">homepage/devel</code></p></li>
-<li><p><code class="filename">install-guide/devel</code></p></li>
-<li><p><code class="filename">about-fedora/devel</code></p></li>
-<li><p><code class="filename">readme/devel</code></p></li>
-<li><p><code class="filename">readme-burning-isos/devel</code></p></li>
-<li><p><code class="filename">readme-live-image/devel</code></p></li>
-</ul></div>
-<p>
-      To see all documents available in the documentation repository,
-      run:
-    </p>
-<pre class="screen"><code class="command">export CVSROOT=:ext:<em class="replaceable"><code>username</code></em>@cvs.fedoraproject.org:/cvs/docs</code>
-<code class="command">cvs co -c</code></pre>
-</div>
 </div>
 <div class="navfooter">
 <hr>


Index: sn_translating_software.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/sn_translating_software.php,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- sn_translating_software.php	15 Aug 2008 05:17:46 -0000	1.13
+++ sn_translating_software.php	6 Feb 2009 01:58:02 -0000	1.14
@@ -3,12 +3,12 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>3. Translating Software</title>
 <link rel="stylesheet" href="fedora.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
-<link rel="start" href="index.php" title="Translation Quick Start Guide">
+<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<link rel="home" href="index.php" title="Translation Quick Start Guide">
 <link rel="up" href="index.php" title="Translation Quick Start Guide">
 <link rel="prev" href="sn_accounts.php" title="2. Accounts and Subscriptions">
 <link rel="next" href="sn_translating_docs.php" title="4. Translating Documentation">
-<link rel="copyright" href="ln-legalnotice-opl.php" title="Legal Notice">
+<link rel="copyright" href="legalnotice-opl.php" title="Legal Notice">
 </head>
 <?
 
@@ -40,7 +40,7 @@
     more <code class="filename">po</code> files. These files
     may be maintained in any of a number of version control systems
     (VCSs) depending on the project, such as CVS, Subversion, Mercurial,
-    and git.  They may be hosted on either <code class="systemitem">fedoraproject.org</code> or other
+    and git. They may be hosted on either <code class="systemitem">fedoraproject.org</code> or other
     systems.
   </p>
 <p>
@@ -54,14 +54,14 @@
 <div class="titlepage"><div><div><h3 class="title" id="sn-file-structure">3.1. File Structure</h3></div></div></div>
 <p>
       To find which modules are translatable, visit the Module List at
-      <a class="ulink" href="https://translate.fedoraproject.org/submit/module/" target="_top">https://translate.fedoraproject.org/submit/module/</a>. 
+      <a class="ulink" href="https://translate.fedoraproject.org/submit/module" target="_top">https://translate.fedoraproject.org/submit/module</a>.
     </p>
 <p>
       Before you download any files, prepare the structure holding those
       files. The described structure below is an example, and your
-      structure can be formed differently.  For example, if you want to
+      structure can be formed differently. For example, if you want to
       download the <code class="systemitem">comps</code> module for
-      translation, make the following directories: 
+      translation, make the following directories:
     </p>
 <pre class="screen"><code class="command">mkdir -p ~/myproject/comps/</code></pre>
 <p>
@@ -72,38 +72,46 @@
 <div class="section" lang="en-US">
 <div class="titlepage"><div><div><h3 class="title" id="sn-obtain-translate-modules">3.2. Obtaining and Translating Modules</h3></div></div></div>
 <p>
-	    Now that you have prepared a directory structure, you can download a file to translate. You may need to communicate with other translators in your language team to avoid confliction. If you are not sure, please contact your language coordinator.
+      Now that you have prepared a directory structure, you can download
+      a file to translate. You may need to communicate with other
+      translators in your language team to avoid confliction. If you are
+      not sure, please contact your language coordinator.
     </p>
 <div class="procedure"><ol type="1">
 <li><p>
-		Visit your language page such as <a class="ulink" href="http://translate.fedoraproject.org/languages/ja/" target="_top">http://translate.fedoraproject.org/languages/ja/</a>, and select a target release. The interface will redirect you to a page for that release, such as <a class="ulink" href="http://translate.fedoraproject.org/languages/ja/fedora-9" target="_top">http://translate.fedoraproject.org/languages/ja/fedora-9</a>.
-	</p></li>
+          Visit your language page such as <a class="ulink" href="http://translate.fedoraproject.org/languages/ja" target="_top">http://translate.fedoraproject.org/languages/ja</a>, and
+          select a target release. The interface will redirect you to a
+          page for that release, such as <a class="ulink" href="http://translate.fedoraproject.org/languages/ja/fedora-10" target="_top">http://translate.fedoraproject.org/languages/ja/fedora-10</a>.
+        </p></li>
 <li><p>
-	 Scroll down the page to find the table of all modules available for that release. Use the green download icon next to each module to download the po file to the directory you created in the previous section. 
-	</p></li>
+          Scroll down the page to find the table of all modules
+          available for that release. Use the green download icon next
+          to each module to download the po file to the directory you
+          created in the previous section.
+        </p></li>
 <li>
 <p>
-	  Since the file name to commit follows the name convention of
-	  <code class="filename">lang.po</code>, change the name of the
-	  downloaded file.  The following example uses the Japanese
-	  locale for the <code class="filename">po</code> file:
-	</p>
+          Since the file name to commit follows the name convention of
+          <code class="filename">lang.po</code>, change the name of the
+          downloaded file. The following example uses the Japanese
+          locale for the <code class="filename">po</code> file:
+        </p>
 <pre class="screen"><strong class="userinput"><code>ls ~/myproject/comps/</code></strong>
 <code class="computeroutput">comps.HEAD.ja.po</code>
-<strong class="userinput"><code>mv ~/myproject/comps/comps.HEAD.ja.po ja.po</code></strong> 
+<strong class="userinput"><code>mv ~/myproject/comps/comps.HEAD.ja.po ja.po</code></strong>
 <strong class="userinput"><code>ls ~/myproject/comps/</code></strong>
 <code class="computeroutput">ja.po</code></pre>
 </li>
 <li><p>
-	  Now the file is ready for translation. Translate the <code class="filename">po</code> file for your language in a
-	  <code class="filename">po</code> editor such as
-	  <span class="application"><strong>KBabel</strong></span> or
-	  <span class="application"><strong>gtranslator</strong></span>.
-	</p></li>
+          Now the file is ready for translation. Translate the <code class="filename">po</code> file for your language in a
+          <code class="filename">po</code> editor such as
+          <span class="application"><strong>Lokalize</strong></span> or
+          <span class="application"><strong>gtranslator</strong></span>.
+        </p></li>
 <li>
 <p>
-	  Check the integrity of your file before you commit it.
-	</p>
+          Check the integrity of your file before you commit it.
+        </p>
 <pre class="screen"><code class="command">msgfmt -cvo /dev/null ja.po</code></pre>
 </li>
 </ol></div>
@@ -113,7 +121,7 @@
 <th align="left">Important</th>
 </tr>
 <tr><td align="left" valign="top"><p>
-	If any error message appears, correct it before commit.
+        If any error message appears, correct it before commit.
       </p></td></tr>
 </table></div>
 </div>
@@ -126,55 +134,57 @@
     </p>
 <div class="procedure"><ol type="1">
 <li><p>
-	  Visit <a class="ulink" href="https://translate.fedoraproject.org/submit" target="_top">https://translate.fedoraproject.org/submit</a> and
-	  click the link <span class="guilabel"><strong>Jump to Modules!</strong></span> to go to
-	  the <span class="guilabel"><strong>Modules and repositories</strong></span> page.  This
-	  page displays all modules to which you can commit changes.
-	  Find the module to commit from the list and select it to visit
-	  the <span class="guilabel"><strong>Submit</strong></span> page for that module.
-	</p></li>
+          Visit <a class="ulink" href="https://translate.fedoraproject.org/submit" target="_top">https://translate.fedoraproject.org/submit</a> and click
+          the link <span class="guilabel"><strong>Jump to Modules!</strong></span> to go to the
+          <span class="guilabel"><strong>Modules and repositories</strong></span> page. This page
+          displays all modules to which you can commit changes. Find the
+          module to commit from the list and select it to visit the
+          <span class="guilabel"><strong>Submit</strong></span> page for that module.
+        </p></li>
 <li>
 <p class="title"><b>Login</b></p>
 <p>
-	  At the bottom of the <span class="guilabel"><strong>Submit</strong></span> page, select
-	  <span class="guilabel"><strong>Authenticate as a translator</strong></span> to visit the
-	  <span class="guilabel"><strong>Login</strong></span> page. Authenticate with your Fedora
-	  Account System username and password.  Upon successful login,
-	  the <span class="guilabel"><strong>Submit</strong></span> page appears.
-	</p>
+          At the bottom of the <span class="guilabel"><strong>Submit</strong></span> page, select
+          <span class="guilabel"><strong>Authenticate as a translator</strong></span> to visit the
+          <span class="guilabel"><strong>Login</strong></span> page. Authenticate with your Fedora
+          Account System username and password. Upon successful login,
+          the <span class="guilabel"><strong>Submit</strong></span> page appears.
+        </p>
 </li>
 <li>
 <p class="title"><b>Submit</b></p>
 <p>
-	  In the section labeled <span class="guilabel"><strong>Local file</strong></span>, click
-	  the browse button to locate your translated file. 
-	</p>
-<p>
-	  In the section labeled <span class="guilabel"><strong>Destination file</strong></span>,
-	  click the dropdown menu labeled <span class="guilabel"><strong>Overwrite an
-	    existing file:</strong></span> to select your language.
-	</p>
-<p>
-	  In the section labeled <span class="guilabel"><strong>Commit message</strong></span>,
-	  enter a comment to describe your work.
-	</p>
-<p>
-	  Select the <span class="guibutton"><strong>Preview</strong></span> button to proceed to
-	  the <span class="guilabel"><strong>Preview submission</strong></span> page. Check the
-	  <span class="guilabel"><strong>Differences</strong></span> section to verify your
-	  changes and select the <span class="guibutton"><strong>Submit</strong></span> button.
-	</p>
-<p>
-	  The <span class="guilabel"><strong>Submit</strong></span> page appears and displays the
-	  message <span class="guilabel"><strong>Your submission was committed
-	    successfully</strong></span>. If you receive an error or some
-	  other success message, please post it to the Fedora Localization Project mailing list so it can be addressed.
-	</p>
+          In the section labeled <span class="guilabel"><strong>Local file</strong></span>, click
+          the browse button to locate your translated file.
+          
+        </p>
+<p>
+          In the section labeled <span class="guilabel"><strong>Destination file</strong></span>,
+          click the dropdown menu labeled <span class="guilabel"><strong>Overwrite an
+          existing file:</strong></span> to select your language.
+        </p>
+<p>
+          In the section labeled <span class="guilabel"><strong>Commit message</strong></span>,
+          enter a comment to describe your work.
+        </p>
+<p>
+          Select the <span class="guibutton"><strong>Preview</strong></span> button to proceed to
+          the <span class="guilabel"><strong>Preview submission</strong></span> page. Check the
+          <span class="guilabel"><strong>Differences</strong></span> section to verify your
+          changes and select the <span class="guibutton"><strong>Submit</strong></span> button.
+        </p>
+<p>
+          The <span class="guilabel"><strong>Submit</strong></span> page appears and displays the
+          message <span class="guilabel"><strong>Your submission was committed
+          successfully</strong></span>. If you receive an error or some
+          other success message, please post it to the Fedora
+          Localization Project mailing list so it can be addressed.
+        </p>
 </li>
 </ol></div>
 </div>
 <div class="section" lang="en-US">
-<div class="titlepage"><div><div><h3 class="title" id="sn-add-new-file">3.4. Adding New .po file</h3></div></div></div>
+<div class="titlepage"><div><div><h3 class="title" id="sn-add-new-file">3.4. Adding New .po File</h3></div></div></div>
 <p>
       If there is no <code class="filename">po</code> file for
       your language, add it.
@@ -182,25 +192,25 @@
 <div class="procedure"><ol type="1">
 <li>
 <p>
-	  Download the <code class="filename">pot</code> file
-	  and copy it as your own language's <code class="filename">po</code> file.
-	</p>
+          Download the <code class="filename">pot</code> file
+          and copy it as your own language's <code class="filename">po</code> file.
+        </p>
 <pre class="screen"><code class="command">cp ~/myproject/comps/comps.HEAD.pot ja.po
-kbabel ja.po
+lokalize ja.po
 msgfmt -cvo /dev/null ja.po</code></pre>
 </li>
 <li><p>
-	  Once you finish the translation, follow the same steps for
-	  verifying and then commit your translation described in
-	  previous section. 
-	</p></li>
+          Once you finish the translation, follow the same steps for
+          verifying and then commit your translation described in
+          previous section.
+        </p></li>
 <li>
 <p>
-	  In the section labeled <span class="guilabel"><strong>Destination file</strong></span>,
-	  type your new filename in the field marked <span class="guilabel"><strong>Type the
-	    name for a new one:</strong></span>, replacing the filename with
-	  your locale:
-	</p>
+          In the section labeled <span class="guilabel"><strong>Destination file</strong></span>,
+          type your new filename in the field marked <span class="guilabel"><strong>Type the
+          name for a new one:</strong></span>, replacing the filename with
+          your locale:
+        </p>
 <pre class="screen"><strong class="userinput"><code>po/ja.po</code></strong></pre>
 </li>
 </ol></div>
@@ -214,41 +224,43 @@
 <div class="procedure"><ol type="1">
 <li>
 <p>
-	  Change directory to the package you want to proofread. For example,
-	</p>
+          Change directory to the package you want to proofread. For
+          example,
+        </p>
 <pre class="screen"><code class="command">cd ~/myproject/<em class="replaceable"><code>system-config-printer/</code></em></code></pre>
 </li>
 <li>
 <p>
-	  Convert the <code class="filename">.po</code> file to
-	  a <code class="filename">.mo</code> file using <code class="command">msgfmt</code> with <code class="option">-o</code> option:
-	</p>
+          Convert the <code class="filename">.po</code> file to
+          a <code class="filename">.mo</code> file using
+          <code class="command">msgfmt</code> with <code class="option">-o</code> option:
+        </p>
 <pre class="screen"><code class="command">msgfmt -o system-config-printer.mo <em class="replaceable"><code>ja</code></em>.po</code></pre>
 </li>
 <li>
 <p>
-	  As a root user, overwrite the existing <code class="filename">.mo</code> file in
-	  <code class="filename">/usr/share/locale/<em class="replaceable"><code>lang</code></em>/LC_MESSAGES/</code>.
-  	</p>
+          As a root user, overwrite the existing <code class="filename">.mo</code> file in
+          <code class="filename">/usr/share/locale/<em class="replaceable"><code>lang</code></em>/LC_MESSAGES/</code>.
+        </p>
 <p>
-	  First, back up the existing file:
-	</p>
+          First, back up the existing file:
+        </p>
 <pre class="screen"><code class="command">su -</code></pre>
 <pre class="screen"><code class="command">cp /usr/share/locale/<em class="replaceable"><code>ja</code></em>/LC_MESSAGES/<em class="replaceable"><code>system-config-printer</code></em>.mo <em class="replaceable"><code>system-config-printer</code></em>.mo-backup</code></pre>
 <p>
-	  Now move the file converted for proofreading.
-	</p>
+          Now move the file converted for proofreading.
+        </p>
 <pre class="screen"><code class="command">mv <em class="replaceable"><code>system-config-printer</code></em>.mo /usr/share/locale/<em class="replaceable"><code>ja</code></em>/LC_MESSAGES/</code></pre>
 <p>
-	  Exit root user.
-	</p>
+          Exit root user.
+        </p>
 <pre class="screen"><code class="command">exit</code></pre>
 </li>
 <li>
 <p>
-	  Proofread the package with the translated strings as part of
-	  the application:
-	</p>
+          Proofread the package with the translated strings as part of
+          the application:
+        </p>
 <pre class="screen"><code class="command">LANG=<em class="replaceable"><code>ja_JP.UTF-8</code></em> <em class="replaceable"><code>system-config-printer</code></em></code></pre>
 </li>
 </ol></div>




More information about the Fedora-docs-commits mailing list