web/html/participate/translation-faq index.php,1.1.1.1,1.2

[Sarah Wang (sarahs)]

Author: sarahs

Update of /cvs/fedora/web/html/participate/translation-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22695

Modified Files:
	index.php 
Log Message:
add more faqs contributed by the community


Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/participate/translation-faq/index.php,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- index.php	30 Mar 2005 17:47:24 -0000	1.1.1.1
+++ index.php	31 Aug 2005 01:55:33 -0000	1.2
@@ -53,6 +53,29 @@
 <p>
 File a bug against Anaconda giving the keyboard and timezone defaults for the locale. Also specify the font required for it.
 </p>
+<h3> Q: How do I test translated .po files? </h3>
+<p>
+<ol>
+<li> Close all instances of the programs that use the .po file </li>
+<li> Go to the directory that contains the file and then run :
+<pre>	$ msgfmt your_locale.po -o package_name.mo 
+</pre> </li>
+<li> Make a backup copy of the file
+/usr/share/locale/your_locale/LC_MESSAGES/package_name.mo </li>
+<li> Copy the new file in the catalog directory:
+<pre>
+$	cp package_name.mo /usr/share/locale/your_locale/LC_MESSAGES/.
+</pre> </li>
+<li> Run the program and your translation will be there. </li>
+</ol>
+<h3> Q: Will the newest po file automatically be included in the next distribuited rpm package? </h3>
+<p>
+The answer is "yes" if the newest po file is commited to cvs before the final build of the rpm package. However, this is not an automated process at this stage. The best way to ensure your translation is included in the release is to adhere the translation freeze date, as outlined on Fedora <a href="http://fedora.redhat.com/participate/schedule/">schedule</a> page.
+</p>
+<h3> Q: What should I do if my translations is not included in the distributed rpm package? </h3>
+<p>
+File a bug report against that package on <a href="http://bugzilla.redhat.com/">bugzilla</a>, providing detailed information such as your locale, the version of the po file etc.
+</p>
 <hr>
 
 <h2> CVS FAQ </h2>
@@ -67,6 +90,15 @@
 <p>
 You need to generate another set of ssh keys and email <a href="i18n at redhat.com">i18n at redhat.com</a> with your login name and the new public key to get your account information updated.
 </p>
+<h3> Q: I have a working account, How do I ceckout the files from cvs server? </h3>
+<p>
+Open a terminal and issue following commands:
+<pre>
+$ export CVS_RSH=ssh
+$ export CVSROOT=<your_login>:ext:@i18n.redhat.com:/usr/local/CVS
+$ cvs -z9 co translate
+</pre>
+</p>
 <h3> Q: What is the CVSROOT to check out the translation files? </h3>
 <p>
 CVSROOT=:ext:<your_login>@i18n.redhat.com:/usr/local/CVS
@@ -79,6 +111,19 @@
 <p>
 You need to first make sure that your cvs account has been approved. If you have an active cvs account but still get "permission denied" error, email <a href="mailto:i18n at redhat.com">i18n at redhat.com</a> with your current ssh key file (~/.ssh/id_dsa.pub) as attachment.
 </p>
+<h3> Q: I have done the initial checkout from the cvs server. What should I do if I want the latest version? </h3>
+<p>
+Open a terminal, change to your "translate" directory, issue the following command:
+<pre>
+$ cvs -f -q update -d -P '.' 
+</pre>
+</p>
+<h3> Q: How do I send my modified .po files to server? </h3>
+<p>
+Open a terminal, change to the directory containing the po file, issue the following command:
+<pre>
+$ cvs -f commit -l -m ''some message you want to record in the log'
+</pre> </p>
 <h3> Q: Can I add files to cvs? </h3>
 <p>
 No. If you need to add new po files to any package, send your completed translation to <a href="mailto: i18n at redhat.com">i18n.redhat.com</a> for cvs addition.