Editing Debian
From Proxecto Trasno
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.
The system administrator who locked it offered this explanation: Esta wiki está temporalmente en modo de só lectura
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | '''Debian GNU/Linux''', organizada a través do '''Proxecto Debian''', é unha distribución de Software Libre moi empregada e desenvolvida a través da colaboración de voluntarios de todo o mundo. Dende os seus comezos, o sistema GNU/Linux, baséase no Kernel de Linux, con moitas tarefas básicas do sistema operativo realizadas co software do Proxecto GNU. Debian é coñecida polo seu seguimento da filosofía de Unix e do Software Libre e pola abundancia de opcións —a versión actual inclúe sobre quince mil paquetes de software para once arquitectura]s de computador. Debian GNU/Linux é a base de moitas outras distribucións como Knoppix, Ubuntu Linux, a galega Triquel, ou a desenvolvida pola Asociación Galega de Usuarios de Linux (AGNIX). | + | == Distribución Debian == |
| + | |||
| + | == Debian GNU/Linux == | ||
| + | '''Debian GNU/Linux''', organizada a través do '''Proxecto Debian''', é unha distribución de Software Libre moi empregada e desenvolvida a través da colaboración de voluntarios de todo o mundo. Dende os seus comezos, o sistema GNU/Linux, baséase no Kernel de Linux, con moitas tarefas básicas do sistema operativo realizadas co software do Proxecto GNU. Debian é coñecida polo seu seguimento da filosofía de Unix e do Software Libre e pola abundancia de opcións —a versión actual inclúe sobre quince mil paquetes de software para once arquitectura]]s de computador. Debian GNU/Linux é a base de moitas outras distribucións como Knoppix, Ubuntu Linux, a galega Triquel, ou a desenvolvida pola Asociación Galega de Usuarios de Linux (AGNIX). | ||
== Grupo de traballo == | == Grupo de traballo == | ||
| Line 14: | Line 17: | ||
== Como colaborar == | == Como colaborar == | ||
| − | Para colaborar na tradución de Debian avisa nas [mailto:proxecto@trasno.net listas do proxecto trasno] ou escríbelle ao | + | Para colaborar na tradución de Debian avisa nas [mailto: proxecto@trasno.net listas do proxecto trasno] ou escríbelle ao coordinador. |
| Line 26: | Line 29: | ||
The Debian installer system (d-i, for short) is made up of several components. Some of these components were written especially for the Debian installer; others, however, are standalone applications which are used during the installation of Debian. The translations of many of these components are managed separately; however, an effort is being made to keep track of them, providing a single dashboard where a translator can see the status of the d-i translations, get files to translate, instructions for submitting the translations, etc. This dashboard resides at http://d-i.alioth.debian.org/l10n-stats/. | The Debian installer system (d-i, for short) is made up of several components. Some of these components were written especially for the Debian installer; others, however, are standalone applications which are used during the installation of Debian. The translations of many of these components are managed separately; however, an effort is being made to keep track of them, providing a single dashboard where a translator can see the status of the d-i translations, get files to translate, instructions for submitting the translations, etc. This dashboard resides at http://d-i.alioth.debian.org/l10n-stats/. | ||
| − | There is [http://d-i.alioth.debian.org/doc/i18n/|a translation guide] for d-i, explaining what components are in each level, how to retrieve the files to translate or update, and how to submit the translated files. I’m giving here a short summary in this post. | + | There is [[http://d-i.alioth.debian.org/doc/i18n/|a translation guide]] for d-i, explaining what components are in each level, how to retrieve the files to translate or update, and how to submit the translated files. I’m giving here a short summary in this post. |
For translation purposes, d-i is divided in five levels. Level 1 contains the strings everyone sees when installing Debian — the following levels contain components whose translation is less user-visible. Therefore, when translating d-i you should prioritize level 1 translations, then level 2 translations and so on. However, this doesn’t mean that they are any less important; you should try to always keep them up to date! | For translation purposes, d-i is divided in five levels. Level 1 contains the strings everyone sees when installing Debian — the following levels contain components whose translation is less user-visible. Therefore, when translating d-i you should prioritize level 1 translations, then level 2 translations and so on. However, this doesn’t mean that they are any less important; you should try to always keep them up to date! | ||
| − | You can see the status of every language in each level by going to the [http://d-i.alioth.debian.org/l10n-stats/|l10n-stats page]. If you click on a language you can see a text file with a more detailed report on the translations for that level and language. You can also opt in to receive emails every morning when the status in a level for your language changes — you’ll have to ask Christian Perrier to subscribe you to the websec-txt notifications for your language. | + | You can see the status of every language in each level by going to the [[http://d-i.alioth.debian.org/l10n-stats/|l10n-stats page]]. If you click on a language you can see a text file with a more detailed report on the translations for that level and language. You can also opt in to receive emails every morning when the status in a level for your language changes — you’ll have to ask Christian Perrier to subscribe you to the websec-txt notifications for your language. |
Level 1 translations are maintained on Alioth, so you should get an Alioth account and request to be added to the d-i project as translator. Then, you’ll be able to download and upload the translations using Subversion. There are lots of programs and packages that comprise level 1; however, to make translation easier and more efficient, the translations are consolidated in only 5 files (called sublevels). In this way, if the same string appears several times in several programs, you only need to translate it once. It’s 5 files instead of a single one so that it’s easier to distribute work, assign priorities, etc. | Level 1 translations are maintained on Alioth, so you should get an Alioth account and request to be added to the d-i project as translator. Then, you’ll be able to download and upload the translations using Subversion. There are lots of programs and packages that comprise level 1; however, to make translation easier and more efficient, the translations are consolidated in only 5 files (called sublevels). In this way, if the same string appears several times in several programs, you only need to translate it once. It’s 5 files instead of a single one so that it’s easier to distribute work, assign priorities, etc. | ||
| Line 42: | Line 45: | ||
When you work actively, the web page whose URL you need to know is http://www.debian.org/intl/l10n/po-debconf/. There you have links to all languages for which there are translations. Click on yours, and you’ll see a page listing the state of every source package’s debconf template translations for your language. First, you see the partially-translated packages, then the fully translated packages, and finally a list of packages which are not translated to your language. For each package in the first two sections you can download the .POT and .PO files; the names of the packages in the last section just link to a big webpage from which you can download every package’s .POT file. | When you work actively, the web page whose URL you need to know is http://www.debian.org/intl/l10n/po-debconf/. There you have links to all languages for which there are translations. Click on yours, and you’ll see a page listing the state of every source package’s debconf template translations for your language. First, you see the partially-translated packages, then the fully translated packages, and finally a list of packages which are not translated to your language. For each package in the first two sections you can download the .POT and .PO files; the names of the packages in the last section just link to a big webpage from which you can download every package’s .POT file. | ||
| − | In the top part of the page you have links to other useful pages. An interesting one is the [http://www.debian.org/intl/l10n/po-debconf/rank|ranking] page, which lists all the languages in order of completeness. | + | In the top part of the page you have links to other useful pages. An interesting one is the [[http://www.debian.org/intl/l10n/po-debconf/rank|ranking]] page, which lists all the languages in order of completeness. |
| − | For working reactively, you need to subscribe to the [http://lists.debian.org/debian-i18n/|debian-i18n mailing list], because when there is a call for updates or for translations it is always sent to that mailing list. Also, if there already is a translation for your language, another email will be sent to the translation group’s mailing list, as well as to the file’s latest translator. | + | For working reactively, you need to subscribe to the [[http://lists.debian.org/debian-i18n/|debian-i18n mailing list]], because when there is a call for updates or for translations it is always sent to that mailing list. Also, if there already is a translation for your language, another email will be sent to the translation group’s mailing list, as well as to the file’s latest translator. |
Calls for translations include information on the deadline and the package maintainer’s preferred methods for submitting the translation. There may also be some notes from the package maintainer. Finally, the .POT file is attached to the call for translations sent to debian-i18n, while the old .PO file is attached to the call for translations sent to the group and the latest translator. | Calls for translations include information on the deadline and the package maintainer’s preferred methods for submitting the translation. There may also be some notes from the package maintainer. Finally, the .POT file is attached to the call for translations sent to debian-i18n, while the old .PO file is attached to the call for translations sent to the group and the latest translator. | ||
| Line 63: | Line 66: | ||
This is what I do to start a new translation for a package called “example": | This is what I do to start a new translation for a package called “example": | ||
| − | + | - Extract the attached templates.pot file into $HOME/pos/example_templates.pot. | |
| − | + | - Bootstrap the translation with my compendium, using this command:<code bash>$ ./bootstrap-po example_templates.pot > gl.po</code>The script is smart enough to know that a file called example_templates.pot is a templates file for a package called example. However, I can specify a different package name as its second argument:<code bash>$ ./bootstrap-po nonsensicalfilename.pot example > gl.po</code> | |
| − | + | - The generated gl.po file is UTF-8 encoded. However, I use xemacs to translate, which cannot read that, so I encode it into iso-8859-1:<code bash>$ msgconv -t iso-8859-1 gl.po -o gll.po</code> | |
| − | + | - Edit the file. | |
| − | + | - Encode the edited file into utf-8:<code bash>$ msgconv -t utf-8 gll.po -o gl.po</code> | |
| − | + | - Add the translations to my compendium:<code bash>$ ./add-total-po</code>(My compendium is the total.po.txt file, hence the name.) | |
| − | + | - Optional: edit the compendium to remove obsolete strings or strings which may be ambiguous so I don’t want them in the compendium. | |
| − | + | - Send the translated file to the package maintainer using the BTS:<code bash>$ ./send-po example</code> | |
| − | + | - Record and push the changes to the compendium:<code bash>$ darcs record -a | |
| + | $ darcs push -a</code> | ||
This is how I update an existing, outdated translation: | This is how I update an existing, outdated translation: | ||
| − | + | - Extract the file into $HOME/pos/gl.po. | |
| − | + | - Most likely, it’s UTF-8 encoded. Encode it into iso-8859-1:<code bash>$ msgconv -t iso-8859-1 gl.po -o gll.po</code> | |
| − | + | - Edit the file, fix only the fuzzy translations. | |
| − | + | - Encode it back into UTF-8:<code bash>$ msgconv -t utf-8 gll.po -o gl.po</code> | |
| − | + | - Update the translation using the existing translated strings and the compendium:<code bash>$ ./refresh-po gl.po | msgconv -t iso-8859-1 -o gll.po</code> | |
| − | + | - Open the file. Hopefully you’ll have new fuzzy translations. Edit the translation and complete it, or do some strings then refresh again and edit and refresh again until the file is completed. If the file contains lots of similar sentences you can just translate a couple of them, refresh, and the other ones will then be all fuzzy. Magic! | |
| − | + | - When I’m done, encode into UTF-8, update the compendium, send to maintainer, submit changes to compendium. | |
=== Reviewing Galician debconf template translations === | === Reviewing Galician debconf template translations === | ||
| Line 96: | Line 100: | ||
== Estatísticas == | == Estatísticas == | ||
A información do estado das traducións pódese atopar aquí: | A información do estado das traducións pódese atopar aquí: | ||
| − | * [http://d-i.debian.org/l10n-stats/|Estado das traducións do instalador] | + | * [[http://d-i.debian.org/l10n-stats/|Estado das traducións do instalador]] |
| − | * [http://www.debian.org/international/l10n/po-debconf/gl|Estado das traducións das pantallas de configuración dos paquetes] | + | * [[http://www.debian.org/international/l10n/po-debconf/gl|Estado das traducións das pantallas de configuración dos paquetes]] |
