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