website view i18n.php @ rev 1090

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