website rev 838
Edit i18n
| author | Paul Issott <paul@slitaz.org> |
|---|---|
| date | Sat Apr 30 21:27:24 2011 +0100 (2011-04-30) |
| parents | 22362cd19489 |
| children | 1cfd203ce733 |
| files | i18n.php |
line diff
1.1 --- a/i18n.php Sat Apr 30 21:14:41 2011 +0100 1.2 +++ b/i18n.php Sat Apr 30 21:27:24 2011 +0100 1.3 @@ -2,7 +2,7 @@ 1.4 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 1.5 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> 1.6 <head> 1.7 - <title>SliTaz - Internationalisation</title> 1.8 + <title>SliTaz - Internationalization</title> 1.9 <meta http-equiv="content-type" content="text/html; charset=utf-8" /> 1.10 <meta name="description" content="SliTaz GNU/Linux LiveCD operating system" /> 1.11 <meta name="keywords" lang="en" content="Système, libre, gnu, linux, logiciels opensource, livecd" /> 1.12 @@ -99,34 +99,34 @@ 1.13 </p> 1.14 1.15 <a name="howto"></a> 1.16 -<h2>Howto participate</h2> 1.17 +<h2>How to participate</h2> 1.18 1.19 <p> 1.20 - From fixing typo to translating a full xHTML page we always translation 1.21 - and proofreading to accomplish. Website often move and get update and 1.22 - SliTaz home made tools such TazPanel got new strings depending the new 1.23 - functions we add to it. By the time we have now many way to let you contact 1.24 - us and get involve in the project. 1.25 + From fixing typos to translating a full xHTML page there's always editing 1.26 + and proofreading to be done. Websites often move and get updated and 1.27 + SliTaz home made tools such as TazPanel acquire new strings depending on the new 1.28 + functions added to it. Over time we have developed a few ways to let you contact 1.29 + us and get involved in the project. 1.30 </p> 1.31 <p> 1.32 - For sending translation work or request a new language you can join the 1.33 - SliTaz <a href="en/mailing-list.html">Mailing List</a> and/or the 1.34 + For sending translations or requesting a new language you can join the 1.35 + SliTaz <a href="en/mailing-list.html">Mailing List</a> and/or join the 1.36 community <a href="http://scn.slitaz.org/groups/i18n/">group on SCN</a> 1.37 and post to the <a href="http://scn.slitaz.org/groups/i18n/forum/">forum</a> 1.38 - witch let you attache files. 1.39 + which lets you attach files. 1.40 </p> 1.41 1.42 <h3>Website translation</h3> 1.43 1.44 <p> 1.45 - Here is an howto translate SliTaz website in a new language. First you need 1.46 - the original website page in English. You have 2 way to get a full copy 1.47 - of the website, use Mercurial and clone the repository or download the 1.48 - latest archive in tar.bz2 format. Using Mercurial let you after update your 1.49 + Here is a howto for translating a SliTaz website into a new language. First 1.50 + you need the original website page in English. You have 2 ways to get a full 1.51 + copy of the website: use Mercurial and clone the repository or download the 1.52 + latest archive in tar.bz2 format. Using Mercurial lets you update your 1.53 local copy in one command and downloading directly from the repository 1.54 - let you get just a page if you want. So it'a matter of choice, but if you 1.55 + allows you to get the page you want. So it's matter of choice, but if you 1.56 want to manage a language and push changes yourself, you will have to use 1.57 - Mercurial, here is <a href="en/devel/forge.php">more info on Hg</a>. 1.58 + Mercurial, here is some <a href="en/devel/forge.php">more info on Hg</a>. 1.59 </p> 1.60 <p> 1.61 Clone the website or get the latest archive: 1.62 @@ -138,41 +138,41 @@ 1.63 </pre> 1.64 1.65 <p> 1.66 - Now that you have a full copy of the website you can fix typo or start a new 1.67 - translation. The reference is English, so always copy and english page to 1.68 - your native language and naturraly keep the website structure intact. When 1.69 - you happy with with your work you can sent it the the community like 1.70 - explained before. 1.71 + Now that you have a full copy of the website you can fix typos or start a new 1.72 + translation. The reference is English, so always copy an English page to 1.73 + your native language and naturally keep the website structure intact. When 1.74 + you're happy with your work you can send it to the community as 1.75 + explained beforehand. 1.76 </p> 1.77 <p> 1.78 - If you a bit afraid about sending a mail to more than 300 people on the list 1.79 - or be exposed on the forum, you can send a private message to one the i18n 1.80 - group member on SCN but he might not have time to anser. Keep in mind we are 1.81 - a friendly community and ther is no stupid questions. 1.82 + If you're a bit afraid about sending a mail to more than 300 people on the list 1.83 + or becoming exposed on the forum, you can send a private message to one of the i18n 1.84 + group members on SCN, but he/she might not have time to answer. Keep in mind we are 1.85 + a friendly community and there aren't any stupid questions. 1.86 </p> 1.87 1.88 <h3>System translation</h3> 1.89 1.90 <p> 1.91 - Like said above, the goal is to provide full language support, not only 1.92 - with the website or forum, but the system itsef. Everything can be translate 1.93 - from menu items to SHell script and GUI boxes. For this we use a standard 1.94 + Like said before, the goal is to provide full language support, not only 1.95 + with the website or forum, but with the system itself. Everything can be translated 1.96 + from menu items to SHell scripts and GUI boxes. For this we use standard 1.97 gettext POT files. 1.98 </p> 1.99 <p> 1.100 - Each translation of a sub-project have is own file named with the language 1.101 + Each translation of a sub-project has its own file named with a language 1.102 prefix, example: pt.po or fr.po. This PO file can be translated with a nice 1.103 - graphical editor like POedit on SliTaz. That means you dont need to have 1.104 - programming or goog Linux skills to help or maintain a translation. 1.105 + graphical editor like POedit on SliTaz. That means you don't need to have 1.106 + programming or Linux skills to help or maintain a translation. 1.107 </p> 1.108 <p> 1.109 - If a PO file for language doesn't exist yet you can create it yourself or 1.110 - ask a contributors to do it and commit the new file to Hg. For each project 1.111 - you will find a README file with translation instruction to use msginit 1.112 - and other gettext tools. If you want to update or complet a translation 1.113 + If a PO file for a language doesn't exist you can create one yourself or 1.114 + ask a contributor to do it for you and commit the new file to Hg. For each project 1.115 + you will find a README file with translation instructions to use msginit 1.116 + and other gettext tools. If you want to update or complete a translation 1.117 PO file, you can download it from here or from Hg and then send it to 1.118 - the list, the forum or SCN as usual. Note that some project are in the 1.119 - same repository such as tazpkg-notify who is part of tazpkg. 1.120 + the list, the forum or SCN as usual. Note that some projects are contained in the 1.121 + same repository such as tazpkg-notify which is part of tazpkg. 1.122 </p> 1.123 1.124 <style type="text/css"> 1.125 @@ -186,9 +186,9 @@ 1.126 </style> 1.127 1.128 <!-- 1.129 - Here we dont link to old gtkdialog box POT file since they will be 1.130 - removed. We ma have link to menu files or some explaination about 1.131 - menu translation. 1.132 + Here we don't link to old gtkdialog box POT files since they will be 1.133 + removed. We may have links to menu files or some explaination about 1.134 + menu translations. 1.135 --> 1.136 1.137 <table>