Author: pfrields
Update of /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32513
Modified Files:
generated-index.php index.php rv-revhistory.php
sn_accounts.php sn_translating_docs.php
sn_translating_software.php
Log Message:
Publish TQSG 0.3.9 en_US
Index: generated-index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/generated-index.php,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- generated-index.php 4 Sep 2007 23:52:58 -0000 1.2
+++ generated-index.php 14 Nov 2007 23:02:48 -0000 1.3
@@ -7,7 +7,7 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Index</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn_translating_docs.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="index" id="generated-index"><div class="titlepage"><div><div><h2 class="title"><a name="generated-index"></a>Index</h2></div></div></div><div class="index"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn_translating_docs.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">4. Translating Documentation </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Index</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn_translating_docs.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="index" id="generated-index"><div class="titlepage"><div><div><h2 class="title">Index</h2></div></div></div><div class="index"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn_translating_docs.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">4. Translating Documentation </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div>
<?
$template->displayFooter('$Date$');
Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/index.php,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.php 4 Sep 2007 23:52:58 -0000 1.6
+++ index.php 14 Nov 2007 23:02:48 -0000 1.7
@@ -7,7 +7,7 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Translation Quick Start Guide</th></tr><tr><td width="20%" align="left">Â </td><th width="60%" align="center">Â </th><td width="20%" align="right">Â <a accesskey="n" href="sn_accounts.php">Next</a></td></tr></table><hr></div><div class="article" lang="en-US" id="translation-quick-start"><div class="titlepage"><div><div><h1 class="title"><a name="translation-quick-start"></a>Translation Quick Start Guide</h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Manuel</span> <span class="surname">Ospina</span></h3></div><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Paul</span> <span class="othername">W.</span> <span class="surname">Frields</span></h3></div><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Noriko</span> <span cla!
ss="surname">Mizumoto</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">Dimitris</span> <span class="surname">Glezos</span></h3></div></div><div><div class="othercredit"><h3 class="othercredit"><span clas!
s="firstname">Damien</span> <span class="surname">Durand</span!
></h3>
iv></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"><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.3.8.1 (2007-09-04)</p></div><div><p class="copyright">Copyright © 2005, 2006, 2007 Red Hat, Inc. and others</p></div><div><a href="ln-legalnotice-opl.php">Legal Notice</a></div><div><a href="rv-revhistory.php">Revision History</a></div></div><hr></div><div class="toc"><dl><dt><span class="section"><a href="index.php#sn-intro">1. Introduction</a></span></dt><dt><span class="section"><a href="sn_accounts.php">2. Accounts and Subscriptions</a></span></dt><dd><dl><dt><span class="section"><a href="sn_accounts.php#sn-ssh-key">2.1. Making a SSH Key</a></span></dt><dt><span class="section"><a href="sn_accounts.!
php#sn-accounts-trans">2.2. Accounts for Software Translation</a></span></dt><dt><span class="section"><a href="sn_accounts.php#sn-accounts-docs">2.3. Accounts for Documentation</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-translating-strings">3.1. Translating Strings</a></span></dt><dt><span class="section"><a href="sn_translating_software.php#sn-proofreading">3.2. 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-downloading-docs">4.1. Downloading Documentation</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-tra!
nslating-with-apps">4.3. Using Translation Applications</a></s!
pan></
</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"><a name="sn-intro"></a>1. Introduction</h2></div></div></div><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Translation Quick Start Guide</th></tr><tr><td width="20%" align="left">Â </td><th width="60%" align="center">Â </th><td width="20%" align="right">Â <a accesskey="n" href="sn_accounts.php">Next</a></td></tr></table><hr></div><div class="article" lang="en-US" id="translation-quick-start"><div class="titlepage"><div><div><h2 class="title">Translation Quick Start Guide</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Manuel</span> <span class="surname">Ospina</span></h3></div><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Paul</span> <span class="othername">W.</span> <span class="surname">Frields</span></h3></div><div class="editor"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Noriko</span> <span class="surname">Mizumoto</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">Dimitris</span> <span class="surname">Glezos</span></h3></div></div><div><div class="othercredit"><h3 class="othercredit"><span class="firstname">Damien</span> <span clas!
s="surname">Durand</span></h3></div></div><div><div class="oth!
ercred
><h3 class="othercredit"><span class="firstname">Guillermo</span> <span class="surname">Gomez</span></h3></div></div><div><div class="othercredit"><h3 class="othercredit"><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.3.9 (2007-11-14)</p></div><div><p class="copyright">Copyright © 2005, 2006, 2007 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><hr></div><div class="toc"><dl><dt><span class="section"><a href="index.php#sn-intro">1. Introduction</a></span></dt><dt><span class="section"><a href="sn_accounts.php">2. Accounts and Subscriptions</a></span></dt><dd><dl><dt><span class="section"><a href="sn_accounts.php#signup-ml">2.1. Subscribing to the Mailing List</a></span></dt><dt><span class="section"><a href="sn_accounts.php#sn-ssh-key">2.2. Making a!
SSH Key</a></span></dt><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-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></dl></dd><dt><spa!
n clas
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-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_transla!
ting_docs.php#sn-creating-common">4.2. Creating Common Files</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
Index: rv-revhistory.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/rv-revhistory.php,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- rv-revhistory.php 4 Sep 2007 23:52:58 -0000 1.6
+++ rv-revhistory.php 14 Nov 2007 23:02:48 -0000 1.7
@@ -7,97 +7,107 @@
?>
-<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.3.8.1</td><td align="left">2007-09-04</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+<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.3.9</td><td align="left">2007-11-14</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
+ <p>
+ Editing for style, grammar, and clarity
+ </p>
+ </td></tr><tr><td align="left">Revision 0.3.8.2</td><td align="left">2007-09-28</td><td align="left">NM</td></tr><tr><td align="left" colspan="3">
+ <p>
+ Modified and updated all chapters to reflect latest
+ information including usage of transifex, moved repository
+ etc.
+ </p>
+ </td></tr><tr><td align="left">Revision 0.3.8.1</td><td align="left">2007-09-04</td><td align="left">DZ</td></tr><tr><td align="left" colspan="3">
<p>
Add information on using an existing SSH key
</p>
- </td></tr><tr><td align="left">Revision 0.3.8</td><td align="left">2007-08-23</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.8</td><td align="left">2007-08-23</td><td align="left">NM</td></tr><tr><td align="left" colspan="3">
<p>
Brokeup main file into multiple files based on chapters
</p>
- </td></tr><tr><td align="left">Revision 0.3.7.5</td><td align="left">2007-07-29</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.7.5</td><td align="left">2007-07-29</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Add information about LINGUAS and remove unnecessary
admonitions
</p>
- </td></tr><tr><td align="left">Revision 0.3.7.4</td><td align="left">2007-07-28</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.7.4</td><td align="left">2007-07-28</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Add information on branch modules and testing changes
</p>
- </td></tr><tr><td align="left">Revision 0.3.7.3</td><td align="left">2007-07-06</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.7.3</td><td align="left">2007-07-06</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Make admonition against manual POT changes
</p>
- </td></tr><tr><td align="left">Revision 0.3.7.2</td><td align="left">2007-05-29</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.7.2</td><td align="left">2007-05-29</td><td align="left">MO</td></tr><tr><td align="left" colspan="3">
<p>
Fix CVS group membership details; shorten copyright holders
list
</p>
- </td></tr><tr><td align="left">Revision 0.3.7.1</td><td align="left">2007-04-03</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.7.1</td><td align="left">2007-04-03</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Generate new POT and PO keeping general entities
</p>
- </td></tr><tr><td align="left">Revision 0.3.7</td><td align="left">2006-10-14</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.7</td><td align="left">2006-10-14</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Fix erroneous URL (#209900)
</p>
- </td></tr><tr><td align="left">Revision 0.3.6</td><td align="left">2006-09-20</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.6</td><td align="left">2006-09-20</td><td align="left">MO</td></tr><tr><td align="left" colspan="3">
<p>
Bug fixes (#198726, #204266, #205167)
</p>
- </td></tr><tr><td align="left">Revision 0.3.5</td><td align="left">2006-08-14</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.5</td><td align="left">2006-08-14</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Editorial pass, revising procedure to match proper ordering
</p>
- </td></tr><tr><td align="left">Revision 0.3.4</td><td align="left">2006-08-10</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.4</td><td align="left">2006-08-10</td><td align="left">MO</td></tr><tr><td align="left" colspan="3">
<p>
Additional information about joining the Docs Project and GPG.
</p>
- </td></tr><tr><td align="left">Revision 0.3.3</td><td align="left">2006-08-06</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.3</td><td align="left">2006-08-06</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Remove step for translating rpm-info since this is now part of
document POT
</p>
- </td></tr><tr><td align="left">Revision 0.3.2</td><td align="left">2006-07-03</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.2</td><td align="left">2006-07-03</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Fix doc translation procedure to include other common files
translations
</p>
- </td></tr><tr><td align="left">Revision 0.3.1</td><td align="left">2006-05-28</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3.1</td><td align="left">2006-05-28</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Add information on common entities and admonition for disabled
locales
</p>
- </td></tr><tr><td align="left">Revision 0.3</td><td align="left">2006-05-27</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.3</td><td align="left">2006-05-27</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Fix procedural guide and include document-specific entities
</p>
- </td></tr><tr><td align="left">Revision 0.2.2.2</td><td align="left">2006-02-13</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.2.2.2</td><td align="left">2006-02-13</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Move to DocBook XML 4.4 and use XInclude
</p>
- </td></tr><tr><td align="left">Revision 0.2.2.1</td><td align="left">2006-02-02</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.2.2.1</td><td align="left">2006-02-02</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Fix spelling (#179717)
</p>
- </td></tr><tr><td align="left">Revision 0.2.2</td><td align="left">2006-02-01</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.2.2</td><td align="left">2006-02-01</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Add entity for bug reporting
</p>
- </td></tr><tr><td align="left">Revision 0.2.1</td><td align="left">2006-01-30</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.2.1</td><td align="left">2006-01-30</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Fix hostname error
</p>
- </td></tr><tr><td align="left">Revision 0.2</td><td align="left">2006-01-25</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.2</td><td align="left">2006-01-25</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
Additional style editing, division of procedures into more
readable sections
</p>
- </td></tr><tr><td align="left">Revision 0.1</td><td align="left">Fri Jan 20 2006</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.1</td><td align="left">Fri Jan 20 2006</td><td align="left">PWF</td></tr><tr><td align="left" colspan="3">
<p>
First round of editing.
</p>
- </td></tr><tr><td align="left">Revision 0.0.1</td><td align="left">Wed Jan 18 2006</td><td align="left"></td></tr><tr><td align="left" colspan="3">
+ </td></tr><tr><td align="left">Revision 0.0.1</td><td align="left">Wed Jan 18 2006</td><td align="left">MO</td></tr><tr><td align="left" colspan="3">
<p>
First draft
</p>
Index: sn_accounts.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/translation-quick-start-guide/en_US/sn_accounts.php,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- sn_accounts.php 4 Sep 2007 23:52:58 -0000 1.6
+++ sn_accounts.php 14 Nov 2007 23:02:48 -0000 1.7
@@ -7,102 +7,158 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2. Accounts and Subscriptions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn_translating_software.php">Next</a></td></tr></table><hr></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn_accounts"></a>2. Accounts and Subscriptions</h2></div></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-ssh-key"></a>2.1. Making a SSH Key</h3></div></div></div><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2. Accounts and Subscriptions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn_translating_software.php">Next</a></td></tr></table><hr></div><div class="section" lang="en-US"><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,
+ 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>.
+ </p><div class="section" lang="en-US"><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></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 href="sn_accounts.php#st-change-permissions" title="???TITLE???">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><pre class="screen">
-<code class="command">ssh-keygen -t dsa</code>
-</pre><p>
- Accept the default location
- (<code class="filename">~/.ssh/id_dsa</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></table></div></li><li><a name="st-change-permissions"></a><p>
- Change permissions to your key and <code class="filename">.ssh</code>
- directory:
- </p><pre class="screen">
-<code class="command">chmod 700 ~/.ssh</code>
-<code class="command">chmod 600 ~/.ssh/id_dsa</code>
-<code class="command">chmod 644 ~/.ssh/id_dsa.pub</code>
-</pre></li><li><p>
- Copy and paste the SSH key in the space provided in order to
- complete the account application.
- </p></li></ol></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-accounts-trans"></a>2.2. Accounts for Software Translation</h3></div></div></div><p>
- To participate in the Fedora Project as a translator you need an account.
- You can apply for an account at <a href="http://i18n.redhat.com/cgi-bin/i18n-signup/"; target="_top">http://i18n.redhat.com/cgi-bin/i18n-signup/</a>. You need
- to provide a user name, an email address, a target language
- â?? most likely your native language â?? and the public
- part of your SSH key.
- </p><p>
- There are also two lists where you can discuss translation
- issues. The first is <em class="firstterm">fedora-trans-list</em>, a
- general list to discuss problems that affect all languages.
- Refer to <a href="http://www.redhat.com/archives/fedora-trans-list"; target="_top">http://www.redhat.com/archives/fedora-trans-list</a> for
- more information. The second is the language-specific list,
- such as <em class="firstterm">fedora-trans-es</em> for Spanish
- translators, to discuss issues that affect only the individual
- community of translators.
- </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-accounts-docs"></a>2.3. Accounts for Documentation</h3></div></div></div><p>
- Follow this procedure to start working directly with the Fedora Documentation Project
- to translate documentation.
- </p><div class="procedure"><ol type="1"><li><p>
- The Fedora Documentation Project encourages all participants to sign e-mails with a
- GPG key. To create a key, use the following command:
- </p><pre class="screen">
-<code class="command">gpg --gen-key</code>
-</pre><p>
- A series of prompts guides you through the process. Press
- <span><strong class="keycap">Enter</strong></span> to select the default values.
- </p><p>
- You must export your public key so other people can verify
- your signature. Use this command to export your key to a
- public server:
- </p><pre class="screen">
-<code class="command">gpg --keyserver pgp.mit.edu --send-keys GPGKEYID</code>
-</pre></li><li><p>
- Request a membership on the Fedora Documentation Project mailing list. To do that,
- fill out the form at <a href="http://www.redhat.com/mailman/listinfo/fedora-docs-list/"; target="_top">http://www.redhat.com/mailman/listinfo/fedora-docs-list/</a>.
- </p></li><li><p>
- You should post a self-introduction to the Fedora Documentation Project mailing
- list. For details, refer to <a href="http://fedoraproject.org/wiki/DocsProject/SelfIntroduction"; target="_top">http://fedoraproject.org/wiki/DocsProject/SelfIntroduction</a>.
- </p></li><li><p>
- You also need to sign up for a Fedora account. Visit <a href="https://admin.fedoraproject.org/accounts/"; target="_top">https://admin.fedoraproject.org/accounts/</a> and
- select the link <span><strong class="guilabel">Apply for a new
- account</strong></span>. After filling out this form, you have
- a basic account.
- </p><p>
- You must complete the Contributors License Agreement
- (<acronym class="acronym">CLA</acronym>), refer to <a href="http://fedoraproject.org/wiki/Infrastructure/AccountSystem/CLAHowTo"; target="_top">http://fedoraproject.org/wiki/Infrastructure/AccountSystem/CLAHowTo</a> for instructions.
- </p></li><li><p>
- Once you have successfully completed the CLA, return to the
- account system and select <span><strong class="guilabel">Edit Your
- Account</strong></span>. Enter the password you received by
- email and select <span><strong class="guilabel">Add new membership</strong></span> at
- the bottom of the page. In the field
- <span><strong class="guilabel">Groupname</strong></span>, enter
- <strong class="userinput"><code>cvsl10n</code></strong> and select
- <span><strong class="guilabel">Add</strong></span>. This action requests access
- to the CVS repository where the documentation is stored.
- </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: CVS Access is Not Automatic"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td><th align="left">CVS Access is Not Automatic</th></tr><tr><td align="left" valign="top"><p>
- When you fill out this form, you are not automatically
- granted write access to the CVS repository. You may need
- sponsorship from one of the Fedora Documentation Project managers to get this
- access.
- </p></td></tr></table></div></li><li><p>
- The next step is to create a wiki account. Fill out the form
- at <a href="http://fedoraproject.org/wiki/UserPreferences"; target="_top">http://fedoraproject.org/wiki/UserPreferences</a>,
- and select <span><strong class="guilabel">Create Profile</strong></span>.
- </p></li><li><p>
- Contact any person with edit access and ask to be added to
- the Wiki edit account in <a href="http://fedoraproject.org/wiki/EditGroup"; target="_top">http://fedoraproject.org/wiki/EditGroup</a>. You can
- do this on IRC or by posting on the
- <code class="systemitem">fedora-docs-list</code> mailing list you
- joined in a previous step.
- </p></li></ol></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn_translating_software.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Translation Quick Start Guide </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 3. Translating Software</td></tr></table></div>
+ </p><div class="procedure"><ol type="1"><li><p>
+ Enter the following command:
+ </p><pre class="screen"><code class="command">ssh-keygen -t dsa</code></pre><p>
+ Accept the default location
+ (<code class="filename">~/.ssh/id_dsa</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></table></div></li><li><a name="st-change-permissions"></a><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_dsa
+chmod 644 ~/.ssh/id_dsa.pub</code></pre></li><li><p>
+ Copy and paste the SSH key in the space provided in order to
+ complete the account application.
+ </p></li></ol></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-gpg-key">2.3. Making a GPG Key</h3></div></div></div><div class="procedure"><ol type="1"><li><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><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><th align="left">Choosing a Good Password</th></tr><tr><td align="left" valign="top"><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></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><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><pre class="screen"><code class="command">gpg --keyserver pgp.mit.edu --send-keys <em class="replaceable"><code>GPGKEYID</code></em></code></pre></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>Apply for a new account</strong></span>.
+ </p></li><li><p>
+ Fill in the form and choose a password for your Fedora account.
+ Enter information for your GPG key ID and SSH key in the form.
+ In the <span class="guilabel"><strong>Comments</strong></span> field, write the
+ languages you plan to work on.
+ </p></li></ol></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-sign-cla">2.5. Signing the CLA</h3></div></div></div><p>
+ You must complete the Contributors License Agreement, or
+ <acronym class="acronym">CLA</acronym>.
+ </p><div class="procedure"><ol type="1"><li><p>Visit <a class="ulink" href="https://admin.fedoraproject.org/accounts/send-cla.cgi"; target="_top">https://admin.fedoraproject.org/accounts/send-cla.cgi</a>.
+ Authenticate using your username and password from the previous
+ process.
+ </p></li><li><p>Wait for receipt of an email with an attachment. The
+ attachment is an agreement you can sign and return. Save the
+ attachment to your Desktop.
+ </p></li><li><p>Double-click the file on your Desktop to open it with an
+ editor. Add the phrase "I agree" and your full name.
+ </p></li><li><p>
+ Digitally sign the text file using your GPG key with the
+ following command, providing your password when prompted:
+ </p><pre class="screen"><code class="command"> gpg -a --sign fedora-icla-{username}.txt </code></pre><p>There is now a new file on your Desktop that ends with
+ <code class="filename">.asc</code>. This file is the
+ signed version of the CLA.
+ </p></li><li><p>
+ Open your email client again and reply to the CLA email.
+ Attach the signed file which ends with <code class="filename">.asc</code>, and send the email.
+ </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>
+ Visit <a class="ulink" href="https://admin.fedora.redhat.com/accounts/userbox.cgi?_edit=1"; target="_top">https://admin.fedora.redhat.com/accounts/userbox.cgi?_edit=1</a>.
+ Select <span class="guilabel"><strong>Add new membership</strong></span> at the bottom
+ of the page. In the field <span class="guilabel"><strong>Groupname</strong></span>,
+ enter <strong class="userinput"><code>cvsl10n</code></strong> and select
+ <span class="guilabel"><strong>Add</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.
+ </p></li></ol></div><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Caution"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="./stylesheet-images/caution.png"></td><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.
+ </p></td></tr></table></div><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td><th align="left">Important</th></tr><tr><td align="left" valign="top"><p>
+ Some of the Fedora modules are still hosted on the <code class="systemitem">i18n.redhat.com</code> system,
+ which is not enabled to work with the
+ <code class="systemitem">cvsl10n</code> group. To translate modules
+ hosted there, please visit <a class="ulink" href="http://i18n.redhat.com/cgi-bin/i18n-signup"; target="_top">http://i18n.redhat.com/cgi-bin/i18n-signup</a>. This
+ warning may be deprecated soon.
+ </p></td></tr></table></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-test-access">2.7. Testing Your Access</h3></div></div></div><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><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><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></li></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="procedure"><ol type="1"><li><p>
+ Visit <a class="ulink" href="http://fedoraproject.org/wiki/UserPreferences/"; target="_top">http://fedoraproject.org/wiki/UserPreferences/</a>. For
+ your username, choose a name like 'FirstnameLastname' and
+ select <span class="guilabel"><strong>Create Profile</strong></span>.
+ </p></li><li><p>
+ A current wiki user can now 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>
+ 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"><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></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><p>
+ 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><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><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><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><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></ul></div><p>
+ Sit back and enjoy your achievement. You are now a fully
+ recognized member of the Fedora community, capable of digitally
+ signing documents and emails, submitting contributions to our CVS,
+ publishing content on the wiki, submitting bugs, following the
+ discussions of our groups and joining other Fedora teams.
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn_translating_software.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Translation Quick Start Guide </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 3. Translating Software</td></tr></table></div>
<?
$template->displayFooter('$Date$');
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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- sn_translating_docs.php 4 Sep 2007 23:52:58 -0000 1.6
+++ sn_translating_docs.php 14 Nov 2007 23:02:48 -0000 1.7
@@ -7,145 +7,135 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4. Translating Documentation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn_translating_software.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="generated-index.php">Next</a></td></tr></table><hr></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn_translating_docs"></a>4. Translating Documentation</h2></div></div></div><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></ul></div><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4. Translating Documentation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn_translating_software.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="generated-index.php">Next</a></td></tr></table><hr></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></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>
+ and <span class="package">make</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'</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:
+ </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">su -c 'yum install gnome-doc-utils xmlto make'</code>
-</pre><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-downloading-docs"></a>4.1. Downloading Documentation</h3></div></div></div><p>
- The Fedora documentation is also stored in a CVS repository
- under the directory <code class="filename">docs/</code>. The process to
- download the documentation is similar to the one used to
- download <code class="filename">.po</code> files. To list the available
- modules, run the following commands:
- </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 example-tutorial docs-common</code>
-</pre><p>Modules that are created for each release of Fedora are
- separated into <em class="firstterm">branches</em>. The branch
- shows the release of Fedora for which that document was
- created. The <code class="filename">release-notes-F-7</code> module, for
- example, contains the branch of the <em class="citetitle">Release
- Notes</em> created for Fedora 7.</p><p>
- The documents are written in DocBook XML format. Each is stored
- in a directory named for the specific-language locale, such as
- <code class="filename">en_US/example-tutorial.xml</code>. The
- translation <code class="filename">.po</code> files are
- stored in the <code class="filename">po/</code>
- directory.
- </p></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-creating-common"></a>4.2. Creating Common Files</h3></div></div></div><p>
+ <code class="command">cvs co release-notes/</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><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><p>
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>.
- </p><div class="procedure"><ol type="1"><li><p>
+ </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></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><li><p>
Once you have created common entities for your locale and
- committed the results to CVS, create a locale file for the
- legal notice:
- </p><pre class="screen">
-<code class="command">cd docs-common/common/</code>
+ 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"><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></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></table></div></li><li><p>
- Then commit that file to CVS also:
- </p><pre class="screen">
-<code class="command">cvs add legalnotice-opl-<em class="replaceable"><code>pt_BR</code></em>.xml</code>
-<code class="command">cvs ci -m 'Added legal notice for <em class="replaceable"><code>pt_BR</code></em>' legalnotice-opl-<em class="replaceable"><code>pt_BR</code></em>.xml</code>
-</pre></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>
+ </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>
+ </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"><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></tr><tr><td align="left" valign="top"><p>
+<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"><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></tr><tr><td align="left" valign="top"><p>
If you do not create these common entities, building your
document may fail.
- </p></td></tr></table></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-translating-with-apps"></a>4.3. Using Translation Applications</h3></div></div></div><p>
+ </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
+ 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
+ used to create new <code class="filename">.po</code>
+ 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><pre class="screen">
-<code class="command">mkdir po</code>
+ </p><pre class="screen"><code class="command">mkdir po</code>
<code class="command">cvs add po/</code>
<code class="command">make pot</code>
-</pre><p>
+</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></table></div><p>
To work with a <code class="filename">.po</code> editor
- like <span><strong class="application">KBabel</strong></span> or
- <span><strong class="application">gtranslator</strong></span>, follow these
- steps:
- </p><div class="procedure"><ol type="1"><li><p>
+ like <span class="application"><strong>KBabel</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></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><pre class="screen">
-<code class="command">cd ~/docs/example-tutorial</code>
-</pre></li><li><p>To add your locale, you must locate and change the
+ </p><pre class="screen"><code class="command">cd ~/docs/example-tutorial</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>In the <code class="filename">po/LINGUAS</code>, add your
- translation language code to the list. <span class="emphasis"><em>Keep the
- list in alphabetical order.</em></span></p></li><li><p>
+ 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. <span class="emphasis"><em>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><pre class="screen">
-<code class="command">make po/<em class="replaceable"><code>pt_BR</code></em>.po</code>
-</pre></li><li><p>
- Now you can translate the file using 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></li><li><p>
- Test your translation using the HTML build tools:
- </p><pre class="screen">
-<code class="command">make html-<em class="replaceable"><code>pt_BR</code></em></code>
-</pre><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></table></div></li><li><p>
- When you have finished your translation, commit the
- <code class="filename">.po</code> file. 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>'Message about commit'</code></em> po/<em class="replaceable"><code>pt_BR</code></em>.po</code>
-</pre><p>
- <span class="emphasis"><em>Do not commit the <code class="filename">Makefile</code>
- until your translation is finished.</em></span> To do so,
- run this command:
- </p><pre class="screen">
-<code class="command">cvs ci -m 'Translation to <em class="replaceable"><code>pt_BR</code></em> finished' Makefile</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 href="https://bugzilla.redhat.com"; target="_top">https://bugzilla.redhat.com</a> to file a bug
- against the document.</p></td></tr></table></div></li></ol></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn_translating_software.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="generated-index.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3. Translating Software </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> Index</td></tr></table></div>
+ </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></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><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.</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></table></div></li><li><p class="title"><b>Commit Work</b></p><p>
+ When you have finished your translation, commit the <code class="filename">.po</code> file. 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><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn_translating_software.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="generated-index.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3. Translating Software </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> Index</td></tr></table></div>
<?
$template->displayFooter('$Date$');
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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- sn_translating_software.php 4 Sep 2007 23:52:58 -0000 1.6
+++ sn_translating_software.php 14 Nov 2007 23:02:48 -0000 1.7
@@ -7,115 +7,143 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3. Translating Software</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn_accounts.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn_translating_docs.php">Next</a></td></tr></table><hr></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn_translating_software"></a>3. Translating Software</h2></div></div></div><p>
- The translatable part of a software package is available in one or
- more <code class="filename">po</code> files. The Fedora Project stores these files in
- a CVS repository under the directory
- <code class="filename">translate/</code>. Once your account has been
- approved, download this directory typing the following
- instructions in a command line:
- </p><pre class="screen">
-<code class="command">export CVS_RSH=ssh</code>
-<code class="command">export CVSROOT=:ext:<em class="replaceable"><code>username</code></em>@i18n.redhat.com:/usr/local/CVS</code>
-<code class="command">cvs -z9 co translate/</code>
-</pre><p>
- These commands download all the modules and
- <code class="filename">.po</code> files to your machine following the same
- hierarchy of the repository. Each directory contains a
- <code class="filename">.pot</code> file, such as
- <code class="filename">anaconda.pot</code>, and the
- <code class="filename">.po</code> files for each language, such as
- <code class="filename">zh_CN.po</code>, <code class="filename">de.po</code>, and so
- forth.
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3. Translating Software</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn_accounts.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn_translating_docs.php">Next</a></td></tr></table><hr></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h2 class="title" style="clear: both" id="sn_translating_software">3. Translating Software</h2></div></div></div><p>
+ The translatable part of a software package is available in one or
+ 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 the
+ <code class="systemitem">i18n.redhat.com</code>
+ server. The <code class="systemitem">i18n.redhat.com</code> system is not
+ enabled to work with the <code class="systemitem">cvsl10n</code> group. To
+ sign up for an account on <code class="systemitem">i18n.redhat.com</code>, please visit
+ <a class="ulink" href="http://i18n.redhat.com/cgi-bin/i18n-signup/"; target="_top">http://i18n.redhat.com/cgi-bin/i18n-signup/</a>. This
+ warning will probably be deprecated soon.
+ </p><p>
+ This chapter explains how to translate the modules hosted on
+ <code class="systemitem">fedoraproject.org</code>.
+ Translators work on two interfaces, one for obtaining modules and
+ another for committing modules. Before you start, you must first
+ prepare the directories which hold your <code class="filename">po</code> files.
+ </p><div class="section" lang="en-US"><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://publictest5.fedora.redhat.com/submit/module/"; target="_top">https://publictest5.fedora.redhat.com/submit/module/</a>.
</p><p>
- You can check the status of the translations at <a href="http://i18n.redhat.com/cgi-bin/i18n-status"; target="_top">http://i18n.redhat.com/cgi-bin/i18n-status</a>. Choose your
- language in the dropdown menu or check the overall status. Select
- a package to view the maintainer and the name of the last
- translator of this module. If you want to translate a module,
- contact your language-specific list and let your community know
- you are working on that module. Afterwards, select
- <code class="literal">take</code> in the status page. The module is then
- assigned to you. At the password prompt, enter the one you
- received via e-mail when you applied for your account.
- </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Requesting a Language Status Page"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Requesting a Language Status Page</th></tr><tr><td align="left" valign="top"><p>
- If your language is not in the list of available languages,
- select <span><strong class="guilabel">Other</strong></span> and click <span><strong class="guibutton">Show
- Status</strong></span>. On the next page, select your language and
- press <span><strong class="guibutton">Continue</strong></span> to show your interest.
- Send an email to <code class="email"><<a href="mailto:fedora-trans-list@xxxxxxxxxx";>fedora-trans-list@xxxxxxxxxx</a>></code> to
- express your interest in translating for the selected language
- in Fedora.
- </p></td></tr></table></div><p>
- You can now start translating.
- </p><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-translating-strings"></a>3.1. Translating Strings</h3></div></div></div><div class="procedure"><ol type="1"><li><p>
- Change directory to the location of the package you have
- taken.
- </p><pre class="screen">
-<code class="command">cd ~/translate/<em class="replaceable"><code>package_name</code></em></code>
-</pre></li><li><p>
- Update the files with the following command:
- </p><pre class="screen">
-<code class="command">cvs up</code>
-</pre></li><li><p>
- Before you start translating, make sure the <code class="filename">.po</code> file reflects the latest
- <code class="filename">.pot</code>. Run the
- following command to synchronize your <code class="filename">.po</code> file:
- </p><pre class="screen">
-<code class="command">msgmerge <em class="replaceable"><code>lang</code></em>.po <em class="replaceable"><code>package_name</code></em>.pot > <em class="replaceable"><code>tmp</code></em>.po</code>
-</pre></li><li><p>Check the integrity of the new file:</p><pre class="screen">
-<code class="command">msgfmt -cvo /dev/null <em class="replaceable"><code>tmp</code></em>.po</code>
-</pre></li><li><p>
- If no error message appears, run the following command to
- overwrite the
- <code class="filename"><em class="replaceable"><code>lang</code></em>.po</code> with
- <code class="filename"><em class="replaceable"><code>tmp</code></em>.po</code>:
- </p><pre class="screen">
-<code class="command">mv <em class="replaceable"><code>tmp</code></em>.po <em class="replaceable"><code>lang</code></em>.po</code>
-</pre></li><li><p>
- Translate the <code class="filename">.po</code>
- file of your language in a <code class="filename">.po</code> editor such as
- <span><strong class="application">KBabel</strong></span> or
- <span><strong class="application">gtranslator</strong></span>. For example, to open
- the <code class="filename">.po</code> file for
- Spanish in <span><strong class="application">KBabel</strong></span>, type:
- </p><pre class="screen">
-<code class="command">kbabel es.po</code>
-</pre></li><li><p>
- When you finish your work, commit your changes back to the
- repository:
- </p><pre class="screen">
-<code class="command">cvs commit -m '<em class="replaceable"><code>comments</code></em>' <em class="replaceable"><code>lang</code></em>.po</code>
-</pre></li><li><p>
- Click the <code class="literal">Release</code> link on the status page
- to release the module so other people can work on it.
- </p></li></ol></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title"><a name="sn-proofreading"></a>3.2. Proofreading</h3></div></div></div><p>
- If you want to proofread your translation as part of the
- software, follow these steps:
- </p><div class="procedure"><ol type="1"><li><p>
- Go to the directory of the package you want to proofread:
- </p><pre class="screen">
-<code class="command">cd ~/translate/<em class="replaceable"><code>package_name</code></em></code>
-</pre></li><li><p>
- Convert the <code class="filename">.po</code> file in
- <code class="filename">.mo</code> file with <code class="command">msgfmt</code>:
- </p><pre class="screen">
-<code class="command">msgfmt <em class="replaceable"><code>lang</code></em>.po</code>
-</pre></li><li><p>
- 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>.
- First, back up the existing file:
- </p><pre class="screen">
-<code class="command">cp /usr/share/locale/<em class="replaceable"><code>lang</code></em>/LC_MESSAGES/<em class="replaceable"><code>package_name</code></em>.mo <em class="replaceable"><code>package_name</code></em>.mo-backup</code>
-<code class="command">mv <em class="replaceable"><code>package_name</code></em>.mo /usr/share/locale/<em class="replaceable"><code>lang</code></em>/LC_MESSAGES/</code>
-</pre></li><li><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>lang</code></em> rpm -qi <em class="replaceable"><code>package_name</code></em></code>
-</pre></li></ol></div><p>
- The application related to the translated package runs with
- the translated strings.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn_accounts.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn_translating_docs.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2. Accounts and Subscriptions </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 4. Translating Documentation</td></tr></table></div>
+ 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
+ download the <code class="systemitem">comps</code> module for
+ translation, make the following directories:
+ </p><pre class="screen"><code class="command">mkdir -p ~/myproject/comps/</code></pre><p>
+ To work on another module later, make a directory with the module
+ name under the parent directory such as <code class="filename">myproject</code>.
+ </p></div><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.
+ </p><div class="procedure"><ol type="1"><li><p>
+ Visit <a class="ulink" href="http://translate.fedoraproject.org/module/"; target="_top">http://translate.fedoraproject.org/module/</a> and
+ select a target module. The interface will redirect you to a
+ page for that module, such as <a class="ulink" href="http://translate.fedoraproject.org/module/comps/"; target="_top">http://translate.fedoraproject.org/module/comps/</a>.
+ </p></li><li><p>
+ Scroll down the page to find the table of all <code class="filename">po</code> files
+ available. The <code class="filename">pot</code> file
+ appears at the top of the listing. Use the green download
+ icon next to each language to download the 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><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>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><li><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><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td><th align="left">Important</th></tr><tr><td align="left" valign="top"><p>
+ If any error message appears, correct it before commit.
+ </p></td></tr></table></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-commit-modules">3.3. Committing Modules</h3></div></div></div><p>
+ Once you finish translation work, commit the file using a separate
+ interface called <span class="application"><strong>Transifex</strong></span>. You can
+ find detailed information about this web tool at <a class="ulink" href="https://publictest5.fedora.redhat.com/submit/"; target="_top">https://publictest5.fedora.redhat.com/submit/</a>.
+ </p><div class="procedure"><ol type="1"><li><p>
+ Visit <a class="ulink" href="https://publictest5.fedora.redhat.com/submit/"; target="_top">https://publictest5.fedora.redhat.com/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></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
+ Translation 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><p>
+ If there is no <code class="filename">po</code> file for
+ your language, add it.
+ </p><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><pre class="screen"><code class="command">cp ~/myproject/comps/comps.HEAD.pot ja.po
+kbabel 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 committing 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><pre class="screen"><strong class="userinput"><code>po/ja.po</code></strong></pre></li></ol></div></div><div class="section" lang="en-US"><div class="titlepage"><div><div><h3 class="title" id="sn-proofreading">3.5. Proofreading</h3></div></div></div><p>
+ To proofread your translation as part of the software, follow
+ these steps:
+ </p><div class="procedure"><ol type="1"><li><p>
+ Change directory to the package you want to proofread:
+ </p><pre class="screen"><code class="command">cd ~/myproject/<em class="replaceable"><code>package_name</code></em></code></pre></li><li><p>
+ Convert the <code class="filename">.po</code> file to
+ a <code class="filename">.mo</code> file with
+ <code class="command">msgfmt</code>:
+ </p><pre class="screen"><code class="command">msgfmt <em class="replaceable"><code>lang</code></em>.po</code></pre></li><li><p>
+ 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>.
+ First, back up the existing file:
+ </p><pre class="screen"><code class="command">cp /usr/share/locale/<em class="replaceable"><code>lang</code></em>/LC_MESSAGES/<em class="replaceable"><code>package_name</code></em>.mo <em class="replaceable"><code>package_name</code></em>.mo-backup</code>
+<code class="command">mv <em class="replaceable"><code>package_name</code></em>.mo /usr/share/locale/<em class="replaceable"><code>lang</code></em>/LC_MESSAGES/</code></pre></li><li><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>lang</code></em> <em class="replaceable"><code>package_command</code></em></code></pre></li></ol></div><p>
+ The application related to the translated package runs with the
+ translated strings.
+ </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn_accounts.php">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="sn_translating_docs.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2. Accounts and Subscriptions </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 4. Translating Documentation</td></tr></table></div>
<?
$template->displayFooter('$Date$');
--
Fedora-websites-list mailing list
Fedora-websites-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-websites-list
