From fedora-docs-commits at redhat.com Wed Jun 10 15:29:45 2015 Content-Type: multipart/mixed; boundary="===============7006473139095136905==" MIME-Version: 1.0 From: fedora-docs-commits at redhat.com To: docs-commits at lists.fedoraproject.org Subject: translation-quick-start-guide translation-quick-start-en.xml, NONE, 1.1 Date: Wed, 18 Jan 2006 01:43:47 -0500 Message-ID: <200601180643.k0I6hl00023005@cvs-int.fedora.redhat.com> --===============7006473139095136905== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: mospina Update of /cvs/docs/translation-quick-start-guide In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22988 Added Files: translation-quick-start-en.xml = Log Message: trans-quick --- NEW FILE translation-quick-start-en.xml --- %FEDORA-ENTITIES-EN; ]> =
Translation Quick Start Guide 2005 &FORMAL-RHI; Manuel Ospina Ospina Manuel &LEGALNOTICE;
Introduction This guide intends to be a fast, simple step by step set of instruction= s to start contributing with the translation of Fedora Project's software and documents. Those interested in getting a better understanding of the translation process involved can see the Translation guide or refer to = the manual of the specific translation tool.
Accounts and subscriptions To participate in the Fedora Project as a translator you need an accoun= t. You can apply for an account at http://i18n.redhat.com/cgi-bin/i18n-signup/. You need to provid= e a username (login), an e-mail address, a target language -most likely your native language-, and the public part of your ssh key. = If you do not have a ssh key yet, you can generate one using the follow= ing steps: 1. Type in a comand line: ssh-keygen -t dsa Accept the default location (~/.ssh/id_dsa) and enter a passphrase. Note Do not forget this passphrase as you will need it to access to the CVS repository. 2. Copy the key to the appropiate file: cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys 3. Change permissions to your key and .ssh directory: chmod 755 ~/.ssh chmod 644 ~/.ssh/authorized_keys Next, copy and paste the ssh key in the space provided in order to complete= the account application. There are also two lists where you can discuss translation issues. fedora-trans-list is a general list to discuss problems that affect all languages; the second is the language-specific list (ex. fedora-trans-es for Spanish language) to discuss issues that affect only the individual communi= ty of translators. It is also useful to subscribe to fedora-doc-list to be inform= ed of issues concerning the general documentation.
Translating software The translatable part of a software package is available in one or more po = files. Fedora Project stores these files in a CVS repository under the directory /transla= te. Once your account has been approved, you can download this directory typing= the following instructions in a command line: export CVS_RSH=3Dssh export CVSROOT=3D:ext:[username]@i18.redhat.com:/usr/local/CVS cvs -z9 co translate/ All the modules and po files will be downloaded to your machine following t= he same hierarchy of the repository. Each directory contains a pot file (ex. anaconda.pot) and the po files for each language (af.po, de.po, es.po, etc). You can check the status of the translations at http://i18n.redhat.com/c= gi-bin/i18n-status. Choose your language in the dropdown menu or check the overall status. You can click on each package to view the maintainer and th= e 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 wor= king on that module. Afterwards, press [take] in the status page. The module will be assigned to you. When asked for a password, enter the one you have received via e-mail after applying for the account. = You can now start translating: 1. Go to the directory of the package you have taken. cd ~/translate/[package_name] 2. Update the files with the command: cvs up 3. Translate the po file of your language in a po editor like KBabel, gtranslator, etc. For example, to open the po file for Spanish in kbabel, t= ype: kbabel es.po 4. When you finish your work, commit your changes back to the repository: cvs commit -m 'comments' [lang].po 5. As a last step, release the module in the status page clicking on the [release] link so other people can work on it. If you want to proofread your translation as part of the software, follow t= hese steps: 1. Go to the directory of the package you want to proofread: cd ~/translate/[package_name] 2. Convert the .po file in .mo file with msgfmt: msgfmt [lang].po 3. Overwrite the existing .mo file in /usr/share/locale/[lang]/LC_MESSAGES/= . Firstly, make sure to back up the existing file: cp /usr/share/locale/[lang]/LC_MESSAGES/[package_name].mo [package= _name].mo-backup mv [package_name].mo /usr/share/locale/[lang]/LC_MESSAGES/ 4. Proofread the package with the translated strings as part of the applica= tion: LANG=3D[lang] rpm -qi [package_name] The application related to the translated package will run with the transla= ted strings.
Translating documentation The Fedora documentation is also stored in a CVS repository under the direc= tory /docs. The process to download the documentation is similar to the one used to downloa= d po files: export CVSROOT=3D:ext:[username]@cvs.fedora.redhat.com:/cvs/docs cvs co docs This will download all the current documents in the directory. If you want = to download only the document you are interested to translate, list the current documents in the repository and then check out the directory containing the document you want: cvs co -c cvs co example-tutorial The documents are written in xml format (docBook to be precise) and named u= sing the specific-language locale: example-tutorial-en.xml. If you are planning = to translate directly from the original xml file, you should create the docume= nt for your language; for instance: = cp example-tutorial-en.xml example-tutorial-es.xml Afterwards you can work on the new copy. You can also convert the xml files into po files and work with a po editor like KBabel o gtranslator. To do so, follow these steps: 1. In a terminal, go to the directory of the document you want to translate: cd ~/docs/example-tutorial 2. Extract the translatable strings with xml2pot: xml2pot example-tutorial-en.xml > [lang].po 3. Now you can translate the file using the same application used to transl= ate software: kbabel [lang].po 4. Once you finish, it is necessary to convert the translated .po file to .= xml file in the target language with po2xml: po2xml example-tutorial-en.xml [lang].po > example-tutorial-[lang]= .xml As the filter (xml2po) does not include entities in the .po file, you have = to change the language of the document from English: <article id=3D"example-tutorial" lang=3D"en"> to your language: <article id=3D"example-tutorial" lang=3D"es"> When the translated file is ready, add it to the repository: cvs add example-tutorial-[lang].xml cvs commit -m 'any comment' example-tutorial-[lang].xml As a final step, you may have to change the Makefile so the document can be built in HTML and PDF formats. Note: Please advise fedora-doc-list and fedora-trans-[locale] that you are modify= ing the Makefile. You should tell your community that you are working on the translation of this document before you start translating to avoid that different people work on the same file. = 1. In the text editor of your preference, open the Makefile. vi Makefile 2. Add the locale of the new translation after the other languages as in the following example: LANGUAGES =3D en de [lang] 3. Include also the following lines: DOCTITLE-[lang] =3D [name of tutorial] XMLEXTRAFILES-[lang]=3D 4. Commit the Makefile cvs commit -m 'any comment' Makefile Then, you can build the document in your machine by typing: make
--===============7006473139095136905==--