website view i18n.php @ rev 1212
en/news: up all page
| author | Christophe Lincoln <pankso@slitaz.org> |
|---|---|
| date | Fri May 02 16:55:22 2014 +0200 (2014-05-02) |
| parents | 3d26c92b1820 |
| children | e9715dc517ed |
line source
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4 <head>
5 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
6 <title>Internationalization | SliTaz</title>
7 <meta name="description" content="SliTaz GNU/Linux languages" />
8 <meta name="keywords" lang="en" content="SliTaz POT, gettext, translation" />
9 <meta name="author" content="Christophe Lincoln"/>
10 <?php include("lib/html/meta-link.html"); ?>
11 <style type="text/css">
12 table {
13 width: 100%;
14 border: 1px solid #ddd;
15 padding: 10px;
16 border-radius: 4px;
17 border-spacing: 0 2px;
18 }
19 .thead { font-weight: bold; text-align: center; }
20 .thead td { border-bottom: 1pt dotted #ccc; }
21 td.proj a, td.pot a, td.po a, td.docs a, td.desk a { text-decoration: none; }
22 td.po, td.docs, td.desk { padding: 0; border-bottom: 1pt dotted #ccc; }
23 td.po a, td.docs a, td.desk a { padding: 0.4em; border-radius: 0.5em; }
24 td.proj, td.pot, td.po a, td.docs a, td.desk a {
25 display: table-cell;
26 border: 1pt solid #aaa;
27 text-align: center;
28 }
29 td.proj { background-color: #FFDCC7; border-radius: 1em 0 0 1em; }
30 td.pot { background-color: #C7FFE4; border-radius: 0 1em 1em 0; border-left: none; }
31 td.po a { background-color: #FFF5C7; }
32 td.docs a { background-color: #FFC7FD; }
33 td.desk a { background-color: #FEFFC7; }
34 hr { border-top: none; border-bottom: 1pt solid #aaa; color: #aaa; margin: 0; height: 1pt}
35 </style>
36 </head>
37 <body>
39 <?php include("lib/html/header.html"); ?>
41 <!-- Block -->
42 <div id="block">
43 <!-- Navigation -->
44 <div id="block_nav" style="text-align: center; padding: 4px;">
45 <?php include("lib/random-image.php"); ?>
46 </div>
47 <!-- Information/image -->
48 <div id="block_info">
49 <h4>About i18n</h4>
50 <p>
51 The main goal of SliTaz is to provide full support for a given
52 language, including the website, official Wiki documentation,
53 a dedicated forum and all SliTaz related projects such as the
54 LiveCD GUI builder.
55 </p>
56 <p>
57 <img src="images/users.png" alt="*" />
58 <a href="http://scn.slitaz.org/groups/i18n/">Join us on SCN</a>
59 </p>
60 </div>
61 </div>
63 <!-- Content -->
64 <div id="content">
66 <h2>Internationalization</h2>
68 <p>
69 Translation is a community effort and everyone can help. You're
70 welcome to join the team! You can find more pot files on
71 <a href="http://hg.slitaz.org/">Hg</a>, just pick one up,
72 translate it and send it to the mailing list or upload it onto the
73 SliTaz Community Network aka <a href="http://scn.slitaz.org/">SCN</a>.
74 </p>
76 <p>
77 SliTaz project Website is available in the following languages:
78 </p>
80 <div class="box">
81 <?php include "lib/lang.php" ?>
82 </div>
84 <h2>Information</h2>
86 <p>
87 The website and documentation has been translated and is kept
88 up-to-date by several contributors. For now, the actively maintained
89 languages are Bosnian, English, French, Italian, Portuguese, Russian, Spanish and Chinese.
90 German is on the stove, but more help is needed. Most of the
91 communication is done through the
92 <a href="en/mailing-list.php">Mailing List</a> and the
93 <a href="http://scn.slitaz.org/groups/i18n/">i18n group</a> on SCN.
94 </p>
96 <p>
97 Some additional languages can be installed through the Package
98 Manager, but we are not able to provide support and documentation.
99 SliTaz is a community based project, everyone can help out and is
100 more than welcome to join us.
101 </p>
103 <h2 id="howto">How to participate</h2>
105 <p>
106 From fixing typos to translating a full xHTML page there's always editing
107 and proofreading to be done. Websites often move and get updated and
108 SliTaz home made tools such as TazPanel acquire new strings depending on the new
109 functions added to it. Over time we have developed a few ways to let you contact
110 us and get involved in the project.
111 </p>
112 <p>
113 For sending translations or requesting a new language you can join the
114 SliTaz <a href="en/mailing-list.php">Mailing List</a> and/or join the
115 community <a href="http://scn.slitaz.org/groups/i18n/">group on SCN</a>
116 and post to the <a href="http://scn.slitaz.org/groups/i18n/forum/">forum</a>
117 which lets you attach files.
118 </p>
120 <h3>Website translation</h3>
122 <p>
123 Here is a howto for translating a SliTaz website into a new language. First
124 you need the original website page in English. You have 2 ways to get a full
125 copy of the website: use Mercurial and clone the repository or download the
126 latest archive in tar.bz2 format. Using Mercurial lets you update your
127 local copy in one command and downloading directly from the repository
128 allows you to get the page you want. So it's matter of choice, but if you
129 want to manage a language and push changes yourself you will have to use
130 Mercurial; here is some <a href="en/devel/forge.php">more info on Hg</a>.
131 </p>
132 <p>
133 Clone the website or get the latest archive:
134 </p>
136 <pre>
137 $ hg clone http://hg.slitaz.org/website
138 $ wget <a href="http://hg.slitaz.org/website/archive/tip.tar.bz2">http://hg.slitaz.org/website/archive/tip.tar.bz2</a>
139 </pre>
141 <p>
142 Now that you have a full copy of the website you can fix typos or start a new
143 translation. The reference is English, so always copy an English page to
144 your native language and naturally keep the website structure intact. When
145 you're happy with your work you can send it to the community as
146 explained beforehand.
147 </p>
148 <p>
149 If you're a bit afraid about sending a mail to more than 300 people on the list
150 or becoming exposed on the forum you can send a private message to one of the i18n
151 group members on SCN (but they might not have time to answer). Keep in mind we are
152 a friendly community and there aren't any stupid questions.
153 </p>
155 <h3>System translation</h3>
157 <p>
158 Like said before, the goal is to provide full language support; not only
159 with the website or forum, but with the system itself. Everything can be translated
160 from menu items to SHell scripts and GUI boxes. For this we use standard
161 gettext POT files.
162 </p>
163 <p>
164 Each translation of a sub-project has its own file named with a language
165 prefix, example: pt_BR.po or fr.po. This PO file can be translated with a nice
166 graphical editor like POedit on SliTaz. That means you don't need to have
167 programming or Linux skills to help or maintain a translation.
168 </p>
169 <p>
170 If a PO file for a language doesn't exist you can create one yourself or
171 ask a contributor to do it for you and commit the new file to Hg. For each
172 project you will find a README file with translation instructions to use
173 msginit and other gettext tools. If you want to update or complete a
174 translation PO file you can download it from here or from Hg and then
175 send it to the list, the forum or SCN as usual. Note that some projects
176 are contained in the same repository such as tazpkg-notify which is part
177 of tazpkg.
178 </p>
180 <!--
181 Here we don't link to old gtkdialog box POT files since they will be
182 removed. We may have links to menu files or some explaination about
183 menu translations.
184 -->
186 <?php require_once("lib/i18n-info.php"); ?>
187 <?php get_info(); ?>
189 <!-- End of content -->
190 </div>
192 <?php include("lib/html/footer.html"); ?>
194 </body>
195 </html>