[haiku-commits] r36744 - in haiku/branches/releases/r1alpha2/docs/welcome: . de en es fr ...

From: humdingerb@xxxxxxxxxxxxxx
To: haiku-commits@xxxxxxxxxxxxx
Date: Sat, 8 May 2010 17:00:22 +0200 (CEST)
Author: humdinger
Date: 2010-05-08 17:00:22 +0200 (Sat, 08 May 2010)
New Revision: 36744
Changeset: http://dev.haiku-os.org/changeset/36744/haiku

Added:
   haiku/branches/releases/r1alpha2/docs/welcome/images/flags/jp.png
   haiku/branches/releases/r1alpha2/docs/welcome/jp/bugreports.html
   haiku/branches/releases/r1alpha2/docs/welcome/jp/wifi.html
   haiku/branches/releases/r1alpha2/docs/welcome/welcome_jp.html
Removed:
   haiku/branches/releases/r1alpha2/docs/welcome/it/
   haiku/branches/releases/r1alpha2/docs/welcome/sv_SE/
Modified:
   haiku/branches/releases/r1alpha2/docs/welcome/de/bugreports.html
   haiku/branches/releases/r1alpha2/docs/welcome/de/wifi.html
   haiku/branches/releases/r1alpha2/docs/welcome/en/bugreports.html
   haiku/branches/releases/r1alpha2/docs/welcome/en/wifi.html
   haiku/branches/releases/r1alpha2/docs/welcome/es/bugreports.html
   haiku/branches/releases/r1alpha2/docs/welcome/es/wifi.html
   haiku/branches/releases/r1alpha2/docs/welcome/fr/bugreports.html
   haiku/branches/releases/r1alpha2/docs/welcome/fr/wifi.html
   haiku/branches/releases/r1alpha2/docs/welcome/ru/bugreports.html
   haiku/branches/releases/r1alpha2/docs/welcome/ru/wifi.html
   haiku/branches/releases/r1alpha2/docs/welcome/uk/bugreports.html
   haiku/branches/releases/r1alpha2/docs/welcome/uk/wifi.html
   haiku/branches/releases/r1alpha2/docs/welcome/welcome_de.html
   haiku/branches/releases/r1alpha2/docs/welcome/welcome_en.html
   haiku/branches/releases/r1alpha2/docs/welcome/welcome_es.html
   haiku/branches/releases/r1alpha2/docs/welcome/welcome_fr.html
   haiku/branches/releases/r1alpha2/docs/welcome/welcome_ru.html
   haiku/branches/releases/r1alpha2/docs/welcome/welcome_uk.html
Log:
This is our welcome package  and all the translat
ions for alpha2. Thanks very much everyone\!

Modified: haiku/branches/releases/r1alpha2/docs/welcome/de/bugreports.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/de/bugreports.html    
2010-05-08 14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/de/bugreports.html    
2010-05-08 15:00:22 UTC (rev 36744)
@@ -32,6 +32,7 @@
 <li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" 
/>Français</a></li>
 <li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
 <li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
 </ul>

Modified: haiku/branches/releases/r1alpha2/docs/welcome/de/wifi.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/de/wifi.html  2010-05-08 
14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/de/wifi.html  2010-05-08 
15:00:22 UTC (rev 36744)
@@ -23,7 +23,7 @@
 <body>
 
 <div id="banner">
-<div><span>User guide</span></div>
+<div><span>User Guide</span></div>
 </div>
 
 <div class="nav">
@@ -33,6 +33,7 @@
 <li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" 
/>Français</a></li>
 <li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
 <li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
 </ul>
@@ -94,21 +95,21 @@
 <h3><a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
 <a name="wep" rel="nofollow" id="wep">WEP Verschlüsselung</a></h3>
 <p>WEP Verschlüsselung ist durch das Kommandozeilen-Programm <span 
class="cli">setwep</span> verfügbar. Es ist ein Provisorium, um sich in ein 
nicht oder per WEP verschlüsseltes Netzwerk einzuklinken. <span 
class="cli">setwep</span> funktioniert mit 64- und 128-bit WEP und unterstützt 
Passwörter als Text und Hex-Werte (siehe <a href="#wep-notes" 
rel="nofollow">WEP Info</a> weiter unten).</p>
-<p>Der Gebrauch ist: <span class="cli">setwep Geräte_Pfad [ssid] [key]</span>. 
Nachfolgend einige Beispiele.</p>
-<p>In diesen Beispielen gehen wir von einer Netzwerkkarte 
"/dev/net/iprowifi3945/0" und einem Funknetzwerk mit dem Namen "haikuwifi" 
aus.</p>
+<p>Der Gebrauch ist: <span class="cli">setwep Geräte_Pfad [ssid] 
[key]</span>.</p>
+<p>In nachfolgenden Beispielen gehen wir von einer Netzwerkkarte 
"/dev/net/iprowifi3945/0" und einem Funknetzwerk mit dem Namen "haikuwifi" 
aus.</p>
 <h4>Beispiel 1: Verbindung mit einer 64-bit WEP Verschlüsselung und einem 
Hex-Passwort</h4>
 <pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
 </pre><h4>Beispiel 2: Verbindung mit einem unverschlüsselten Funknetzwerk</h4>
 <pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi
 </pre><div class="box-info">
 <li>Den Pfad zu seinem Gerät findet man unter Preferences -&gt; Network.</li>
-<li>Um sich bei jedem Hochfahren mit dem Netzwerk unter dieser SSID zu 
verbinden, schreibt man den setwep Befehl ins 
home/config/boot/UserBootscript.</li>
+<li>Um sich bei jedem Hochfahren mit dem Netzwerk unter dieser SSID zu 
verbinden, schreibt man den <tt>setwep</tt> Befehl ins 
<tt>home/config/boot/UserBootscript</tt>.</li>
 </div>
 <p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP 
Info</strong></a></p>
 <ul>
 <li>64-bit WEP benutzt ein 40-bit Passwort, das sind 5 Buchstaben oder 10 
Hex-Werte</li>
 <li>128-bit WEP benutzt ein 104-bit Passwort, das sind 13 Buchstaben oder 26 
Hex-Werte</li>
-<li>Hex-Werte sind die Zahlen 0-9 und Buchstaben A bis F (mit einem 
vorangestellten '0x')</li>
+<li>Hex-Werte sind die Zahlen 0-9 und Buchstaben A bis F (in <tt>setwep</tt> 
mit einem vorangestellten '0x')</li>
 </ul>
 <h3><a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
 <a name="wpa" rel="nofollow" id="wpa">WPA Verschlüsselung</a></h3>

Modified: haiku/branches/releases/r1alpha2/docs/welcome/en/bugreports.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/en/bugreports.html    
2010-05-08 14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/en/bugreports.html    
2010-05-08 15:00:22 UTC (rev 36744)
@@ -31,6 +31,7 @@
 <li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
 <li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
 <li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 </ul>
 <span>

Modified: haiku/branches/releases/r1alpha2/docs/welcome/en/wifi.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/en/wifi.html  2010-05-08 
14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/en/wifi.html  2010-05-08 
15:00:22 UTC (rev 36744)
@@ -32,6 +32,7 @@
 <li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
 <li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
 <li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 </ul>
 
@@ -96,23 +97,23 @@
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
 <a name="wep" rel="nofollow" id="wep">WEP encryption</a></h3>
-<p>WEP encryption is available through a command-line application <span 
class="cli">setwep</span>. It is a temporary means for joining an unencrypted 
or WEP encrypted wifi network. <span class="cli">setwep</span> works with 64- 
and 128-bit WEP and supports both text keys as well as hex digit keys (see <a 
href="#wep-notes" rel="nofollow">WEP notes</a> below)
+<p>WEP encryption is available through a command-line application <span 
class="cli">setwep</span>. It is a temporary means for joining an unencrypted 
or WEP encrypted wifi network. <span class="cli">setwep</span> works with 64- 
and 128-bit WEP and supports both text keys as well as hex digit keys (see <a 
href="#wep-notes" rel="nofollow">WEP notes</a> below).
 </p>
-<p>The usage is: <span class="cli">setwep device_path [ssid] [key]</span>. 
Below are some examples. </p>
-<p>In this example, let us assume your wifi network card is 
"/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".</p>
+<p>The usage is: <span class="cli">setwep device_path [ssid] [key]</span></p>
+<p>Below are two examples. Let us assume your wifi network card is 
"/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".</p>
 <h4>Example 1: Connect with 64-bit WEP encryption using a hex digit key</h4>
 <pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
 </pre><h4>Example 2: Connect to an unencrypted wireless network</h4>
 <pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi
 </pre><div class="box-info">
-<li>To find out what your device_path is, have a look in Preferences -&gt; 
Network.</li>
-<li>To make your wifi device connect to a given SSID at each boot, add the 
setwep command to your home/config/boot/UserBootscript.</li>
+<li>To find out what your device_path is, have a look in Preferences -&gt; 
Network</li>
+<li>To make your wifi device connect to a given SSID at each boot, add the 
<tt>setwep</tt> command to your <tt>home/config/boot/UserBootscript</tt></li>
 </div>
 <p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP 
notes</strong></a></p>
 <ul>
 <li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex 
digits</li>
 <li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex 
digits</li>
-<li>hexadecimal digits = characters 0-9 and A through F (prepended with 
'0x')</li>
+<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" 
in <tt>setwep</tt>)</li>
 </ul>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
@@ -121,8 +122,8 @@
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
 <a name="install_script" rel="nofollow" 
id="install_script">install-wifi-firmwares.sh</a></h3>
-<p>To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, 
Broadcom 43xx &amp; Marvell 88W8335, you'll need to run</p>
-<pre class="terminal">~&gt; install-wifi-firmwares.sh
+<p>To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, 
Broadcom 43xx &amp; Marvell 88W8335, you need to run</p>
+<pre class="terminal">install-wifi-firmwares.sh
 </pre>
 <p>The Intel ipw2100 and ipw22xx will install without an internet connection, 
as the licensing terms allow Haiku to distribute the original firmware 
archives. However, they do require acknowledgment by the end-user prior to 
their installation. The Broadcom 43xx and Marvell 88W8335 will require an 
active internet connection, as the files containing their respective firmwares 
cannot be distributed with Haiku.</p>
 <p>People building their own Haiku image can modify their <span 
class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and 
general updates on the wifi topic are found at the <a 
href="http://www.haiku-os.org/guides/wifi";>online version of this 
document</a>.</p>

Modified: haiku/branches/releases/r1alpha2/docs/welcome/es/bugreports.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/es/bugreports.html    
2010-05-08 14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/es/bugreports.html    
2010-05-08 15:00:22 UTC (rev 36744)
@@ -22,7 +22,7 @@
 <body>
 
 <div id="banner">
-<div><span>User guide</span></div>
+<div><span>Guía del usuario</span></div>
 </div>
 
 <div class="nav">
@@ -32,6 +32,7 @@
 <li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" 
/>Français</a></li>
 <li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
 <li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
+<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
 </ul>

Modified: haiku/branches/releases/r1alpha2/docs/welcome/es/wifi.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/es/wifi.html  2010-05-08 
14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/es/wifi.html  2010-05-08 
15:00:22 UTC (rev 36744)
@@ -10,6 +10,8 @@
  * Authors:
 *              Matt Madia who wrote http://www.haiku-os.org/guides/wifi 
  *             Humdinger <humdingerb@xxxxxxxxx>
+ * Translators:
+ *             miguel~1.mx
  *
 -->
        <meta http-equiv="content-type" content="text/html; charset=utf-8" />
@@ -21,7 +23,7 @@
 <body>
 
 <div id="banner">
-<div><span>User guide</span></div>
+<div><span>Guía del usuario</span></div>
 </div>
 
 <div class="nav">
@@ -31,6 +33,7 @@
 <li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" 
/>Français</a></li>
 <li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
 <li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
+<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
 </ul>
@@ -43,90 +46,83 @@
 <div id="content">
 <div>
 
-<h2>Wifi in Haiku</h2>
-<h3>
-<a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
-<a name="hardware" rel="nofollow" id="hardware">Expected supported 
hardware</a></h3>
-<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, 
ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, 
PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
-This includes:
+<h2>Wifi en Haiku</h2>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
+<a name="hardware" rel="nofollow" id="hardware">Hardware que se espera 
funcione</a></h3>
+<p>Todos los controladores wlan de FreeBSD 8 deberían trabajar. Cualquier 
tarjeta basada PCMCIA, CardBus, ExpressCard, USB o ISA no funcionará. 
Únicamente las PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X se espera 
que trabajen.<br />
+Esto incluye a:
 </p>
 <ul>
-<li><p><i>aironetwifi</i> supporting at least<br />
-Cisco Aironet 350 Series<br />
-Aironet PCI4500<br />
-Aironet PCI4800<br />
+<li><p><i>aironetwifi</i> soportando al menos:<br />
+Aironet PCI4500 y<br />
+Aironet PCI4800.<br />
 </p></li>
-<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no 
AR9285 chips)</p></li>
-<li><p><i>broadcom43xx</i> supporting<br />
-BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
+<li><p><i>atheroswifi</i> soportando casi todos los chipsets de afuera (aunque 
no los chips AR9285).</p></li>
+<li><p><i>broadcom43xx</i> soportando<br />
+BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 y BCM4318.
 </p></li>
-<li><p><i>iprowifi2100</i> supporting the 2100 chips</p></li>
-<li><p><i>iprowifi2200</i> supporting<br />
-2200BG<br />
-2225BG<br />
-2915ABG
+<li><p><i>iprowifi2100</i> soportando los chips 2100.</p></li>
+<li><p><i>iprowifi2200</i> soportando:<br />
+2200BG,<br />
+2225BG y<br />
+2915ABG.
 </p></li>
-<li><p><i>iprowifi3945</i> supporting the 3945 chips</p></li>
-<li><p><i>iprowifi4965</i> supporting the 4965 chips</p></li>
-<li><p><i>marvell88w8335</i> supporting<br />
-Marvell Libertas 88W8310<br />
-Marvell Libertas 88W8335
+<li><p><i>iprowifi3945</i> soportando los chips 3945.</p></li>
+<li><p><i>iprowifi4965</i> soportando los chips 4965.</p></li>
+<li><p><i>marvell88w8335</i> soportando:<br />
+Marvell Libertas 88W8310 y<br />
+Marvell Libertas 88W8335.
 </p></li>
-<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
-<li><p><i>ralinkwifi</i> supporting<br />
-RT2560<br />
-RT2561S<br />
-RT2561<br />
-RT2661
+<li><p><i>marvell88w8363</i> soportando los chips 88W8363.</p></li>
+<li><p><i>ralinkwifi</i> soportando:<br />
+RT2560,<br />
+RT2561S,<br />
+RT2561 y <br />
+RT2661.
 </p></li>
-<li><p><i>wavelanwifi</i> supporting at least<br />
-3Com Airconnect<br />
-GLPRISM2 WaveLAN<br />
-Intersil Prism3<br />
-Intersil Prism2.5<br />
-Linksys WDT11<br />
-Netgear MA301<br />
-PRISM2STA WaveLAN<br />
-Siemens SpeedStream<br />
-SMC 2602W<br />
-Us Robotics 2415<br />
-Addtron AWA-100 PCI
+<li><p><i>wavelanwifi</i> soportando al menos:<br />
+3Com Airconnect,<br />
+GLPRISM2 WaveLAN,<br />
+Intersil Prism3,<br />
+Intersil Prism2.5,<br />
+Linksys WDT11,<br />
+Netgear MA301,<br />
+PRISM2STA WaveLAN,<br />
+Siemens SpeedStream,<br />
+SMC 2602W,<br />
+Us Robotics 2415 y<br />
+Addtron AWA-100 PCI.
 </p></li>
 </ul>
-<h3>
-<a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
-<a name="wep" rel="nofollow" id="wep">WEP encryption</a></h3>
-<p>WEP encryption is available through a command-line application <span 
class="cli">setwep</span>. It is a temporary means for joining an unencrypted 
or WEP encrypted wifi network. <span class="cli">setwep</span> works with 64- 
and 128-bit WEP and supports both text keys as well as hex digit keys (see <a 
href="#wep-notes" rel="nofollow">WEP notes</a> below)
-</p>
-<p>The usage is: <span class="cli">setwep device_path [ssid] [key]</span>. 
Below are some examples. </p>
-<p>In this example, let us assume your wifi network card is 
"/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".</p>
-<h4>Example 1: Connect with 64-bit WEP encryption using a hex digit key</h4>
-<pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
-</pre><h4>Example 2: Connect to an unencrypted wireless network</h4>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
+<a name="wep" rel="nofollow" id="wep">Encripción WEP</a></h3>
+<p>Está disponible la encripción WEP mediante una aplicación de comando de 
línea <span class="cli">setwep</span>. Es una manera temporal para unirse a una 
red Wifi sin encriptar o con encripción WEP. <span class="cli">setwep</span> 
trabaja con WEP 64- y 128-bit y soporta tanto claves de texto 
+WEP como claves de dígito hexadecimal (vea las (see <a href="#wep-notes" 
rel="nofollow">notas WEP</a> debajo).</p>
+<p>La forma de uso es: <span class="cli">setwep device_path [ssid] 
[key]</span></p>
+<p>Debajo hay dos ejemplos. Asumamos que la tarjeta Wifi en su sistema está en 
"/dev/net/iprowifi3945/0" y la red inalámbrica se llama "haikuwifi".</p>
+<h4>Ejemplo 1: Conectarse con encripción WEP 64-bit usando una clave de 
dígitos hexadecimales</h4>
+<pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi 
0x3456789abc</pre><h4>Ejemplo 2: Conectarse a una red inalámbrica sin 
encripción</h4>
 <pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi
-</pre><div class="box-info">
-<li>To find out what your device_path is, have a look in Preferences -&gt; 
Network.</li>
-<li>To make your wifi device connect to a given SSID at each boot, add the 
setwep command to your home/config/boot/UserBootscript.</li>
+</pre><div class="box-info"><li>Para averiguar qué device_path tiene su 
dispositivo, dé un vistazo en Preferencias -&gt; Red</li>
+<li>Para hacer que su dispositivo Wifi se conecte a un SSID dado en cada 
inicio del sistema, agregue el comando <tt>setwep</tt> command a su 
<tt>home/config/boot/UserBootscript</tt></li>
 </div>
-<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP 
notes</strong></a></p>
+<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Notas 
WEP</strong></a></p>
 <ul>
-<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex 
digits</li>
-<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex 
digits</li>
-<li>hexadecimal digits = characters 0-9 and A through F (prepended with 
'0x')</li>
+<li>El WEP de 64-bit usa una clave de 40-bit, lo cual significa 5 caracteres 
de texto o 10 dígitos hexadecimales.</li>
+<li>El WEP de 128-bit usa una clave de 104-bit, lo cual significa 13 
caracteres de texto o 16 dígitos hexadecimales.</li>
+<li>Dígitos hexadecimales = caracteres del 0 al 9 y de la A a la F 
(antepuestos con "0x" en <tt>setwep</tt>).</li>
 </ul>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
+<a name="wpa" rel="nofollow" id="wpa">Encripción WPA</a></h3>
+<p>Al momento no hay encripción WPA disponible en Haiku. Sin embargo hay algo 
de <a target="_blank" class="ext" href="http://alexbl.net/%7Ealexbl/haiku-wpa/"; 
rel="nofollow">código preliminar y sin terminar pra implementar WPA</a><span 
class="ext"></span> disponible. Algunas tareas para mejorar esto es conectarse 
en el build del proceso del wpa_supplicant build y luego arreglar los problemas 
de compilación y los problemas en tiempo de ejecución.</p>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
-<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
-<p>At the moment there is no WPA encryption available in Haiku. However, there 
is some <a target="_blank" class="ext" 
href="http://alexbl.net/%7Ealexbl/haiku-wpa/"; rel="nofollow">preliminary and 
unfinished code for implementing WPA</a><span class="ext"></span> available. 
Some tasks for improving this is to plug it into the wpa_supplicant build 
process and then fixing compile &amp; runtime issues.</p>
-<h3>
-<a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
 <a name="install_script" rel="nofollow" 
id="install_script">install-wifi-firmwares.sh</a></h3>
-<p>To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, 
Broadcom 43xx &amp; Marvell 88W8335, you'll need to run</p>
-<pre class="terminal">~&gt; install-wifi-firmwares.sh
-</pre>
-<p>The Intel ipw2100 and ipw22xx will install without an internet connection, 
as the licensing terms allow Haiku to distribute the original firmware 
archives. However, they do require acknowledgment by the end-user prior to 
their installation. The Broadcom 43xx and Marvell 88W8335 will require an 
active internet connection, as the files containing their respective firmwares 
cannot be distributed with Haiku.</p>
-<p>People building their own Haiku image can modify their <span 
class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and 
general updates on the wifi topic are found at the <a 
href="http://www.haiku-os.org/guides/wifi";>online version of this 
document</a>.</p>
-<p>If you have to download the firmware, but don't have a working internet 
connection under Haiku, the online version offers a <a 
href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt"; 
rel="nofollow">shell script</a>, which will create a zip file for you to 
extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by 
install-wifi-firmwares.sh.</p>
+<p>Para instalar el firmware para las Intel ipw2100, Intel ipw2200/2225/2915, 
Broadcom 43xx y Marvell 88W8335, se necesita correr</p>
+<pre class="terminal">install-wifi-firmwares.sh</pre>
+<p>Las tarjetas Intel ipw2100 y ipw22xx se instalarán sin conexión a Internet, 
pues los términos de la licencia permiten a Haiku distribuir los archivos de 
firmware originales. No obstante, requieren cierto acuerdo por el usuario final 
previo a la instalación. Las tarjetas Broadcom 43xx y Marvell 88W8335 
requerirán una conexión a Internet activa, pues los archivos que contienen los 
respectivos firmwares no pueden redistribuirse con Haiku.</p>
+<p>La gente que hace su propio build de la imagen de Haiku puede modificar su 
<span class="cli">build/jam/UserBuildConfig</span> en conformidad. Los detalles 
para ello y actualizaciones generales del tema de Wifi se encuentran en la <a 
href="http://www.haiku-os.org/guides/wifi";>versión en línea de este 
documento</a>.</p>
+<p>Si tiene que descargar el firmware, pero no tiene una conexión a Internet 
funcionando bajo Haiku, la versión en línea de este documento ofrece un <a 
href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt"; 
rel="nofollow">script de shell</a>, el cual creará un archivo zip para que se 
extraiga en la carpeta <tt>/boot</tt> de Haiku. Después de ello tendrá todos 
los archivos necesarios por install-wifi-firmwares.sh.</p>
 </div>
 </div>
 

Modified: haiku/branches/releases/r1alpha2/docs/welcome/fr/bugreports.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/fr/bugreports.html    
2010-05-08 14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/fr/bugreports.html    
2010-05-08 15:00:22 UTC (rev 36744)
@@ -33,6 +33,7 @@
 <li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
 <li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
 <li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
 </ul>
@@ -54,12 +55,12 @@
 Lors de la création d’un nouveau compte, pensez à <b>indiquer votre adresse 
e-mail</b> afin d’obtenir les privilèges basiques de gestions des tickets. 
N’oubliez pas de <b>Vérifier votre dossier de pourriel</b> après, car les 
e-mails de vérifications s’y retrouvent souvent.</p>
 
 <h2>Créer un rapport de bogue</h2>
-<p>Avant de rapporter un bogue, veuillez <a 
href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority";>vérifier</a>qu’il
 n’est pas déjà répertorié. Vous pouvez aussi utiliser la <a 
href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on";>fonction
 de recherche</a> pour cela.<br />
-Après vous être assurer que votre bogue est unique, obtenez des informations 
précises sur votre environnement :</p>
+<p>Avant de rapporter un bogue, veuillez <a 
href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority";>vérifier</a>
 qu’il n’est pas déjà répertorié. Vous pouvez aussi utiliser la <a 
href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on";>fonction
 de recherche</a> pour cela.<br />
+Après vous être assuré que votre bogue est unique, obtenez des informations 
précises sur votre environnement :</p>
 <ul>
        <li><p>Indiquez comment vous testez Haiku (sur machine réelle, dans 
VMware, dans Qemu…)</p></li>
        <li><p>Indiquez quelle révision <acronym title="Subversion, le système 
de gestion de code source que nous utilisons">SVN</acronym> de Haiku vous 
utilisez. Vous pouvez trouver des informations à ce sujet dans le menu 
« <i>About This System…</i> » de la Deskbar.</p></li>
-       <li><p>Décrire le problème que vous rencontrez. Essayez d'être aussi 
précis que possible : décrivez le comportement réel, et celui que vous 
attendiez.</p></li>
+       <li><p>Décrivez le problème que vous rencontrez. soyez aussi précis que 
possible : décrivez le comportement réel, et celui que vous attendiez.</p></li>
        <li><p>Décrivez les actions que vous avez effectuées avant de faire 
ressortir le bogue. Cela permettra aux développeurs de le reproduire.</p></li>
        <li><p>Attachez au rapport le plus d’informations possibles. Si le 
bogue concerne l’interface graphique ou une application, essayez de faire une 
capture d’écran (la touche <span class="key">IMPR ÉCRAN</span> créera une image 
<acronym title="Portable Network Graphics image format">PNG</acronym> dans le 
dossier <span class="path">/boot/home/</span>).</p></li>
 </ul>
@@ -90,7 +91,7 @@
 
 <h2>Et après ?</h2>
 <p>Une fois le bogue rapporté, un développeur le consultera et essayera de le 
cataloguer. Retenez que tous les développeurs sont des volontaires; un long 
délai avant réponse peut s’écouler après le rapport de bogue. L’ajout de 
nouvelles informations une fois celles-ci disponibles peut généralement 
permettre à un bogue d’être analysé plus rapidement. Néanmoins, n’essayez pas 
de « faire remonter » un bogue en ajoutant des commentaires non pertinents.</p>
-<p>N’oubliez pas, le rapport d’un bogue ne se limite pas à sa soumission. Une 
fois cette tâche faite, vous ferez partie du processus de développement de 
Haiku. Les développeurs pourront vous poser des question pour essayer de 
résoudre votre bogue. Merci de rester disponible pour y répondre. Considérez 
votre travail « terminé » quand le bogue sera marqué comme étant « corrigé 
».</p>
+<p>N’oubliez pas, le rapport d’un bogue ne se limite pas à sa soumission. Une 
fois cette tâche faite, vous ferez partie du processus de développement de 
Haiku. Les développeurs pourront vous poser des question pour essayer de 
résoudre votre bogue. Merci de rester disponible pour y répondre. Vous pourrez 
considérer votre travail « terminé » quand le bogue sera marqué comme étant « 
corrigé ».</p>
 
 </div>
 </div>

Modified: haiku/branches/releases/r1alpha2/docs/welcome/fr/wifi.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/fr/wifi.html  2010-05-08 
14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/fr/wifi.html  2010-05-08 
15:00:22 UTC (rev 36744)
@@ -10,6 +10,9 @@
  * Authors:
 *              Matt Madia who wrote http://www.haiku-os.org/guides/wifi 
  *             Humdinger <humdingerb@xxxxxxxxx>
+ * Translators:
+ *             Loïc
+ *             Vincent Duvert
  *
 -->
        <meta http-equiv="content-type" content="text/html; charset=utf-8" />
@@ -21,7 +24,7 @@
 <body>
 
 <div id="banner">
-<div><span>User guide</span></div>
+<div><span>Guide de l’utilisateur</span></div>
 </div>
 
 <div class="nav">
@@ -31,6 +34,7 @@
 <li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
 <li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
 <li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
 </ul>
@@ -43,43 +47,47 @@
 <div id="content">
 <div>
 
-<h2>Wifi in Haiku</h2>
+<h2>Le Wifi dans Haiku</h2>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
-<a name="hardware" rel="nofollow" id="hardware">Expected supported 
hardware</a></h3>
-<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, 
ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, 
PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
-This includes:
-</p>
+<a name="hardware" rel="nofollow" id="hardware">Matériel théoriquement 
supporté</a></h3>
+<p>Tous les pilotes de réseau sans fil de FreeBSD 8 devraient fonctionner. En 
revanche, les périphériques PCMCIA, CardBus, ExpressCard, USB, ou ISA ne sont 
pas supportés. Seules les cartes PCI, MiniPCI, PCI-Express, minipci-Express et 
PCI-X sont censées fonctionner.<br />
+Cela inclut :</p>
 <ul>
-<li><p><i>aironetwifi</i> supporting at least<br />
+<li><p>Le module <i>aironetwifi</i>, qui supporte au minimum les cartes :<br />
 Cisco Aironet 350 Series<br />
 Aironet PCI4500<br />
 Aironet PCI4800<br />
 </p></li>
-<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no 
AR9285 chips)</p></li>
-<li><p><i>broadcom43xx</i> supporting<br />
-BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
-</p></li>
-<li><p><i>iprowifi2100</i> supporting the 2100 chips</p></li>
-<li><p><i>iprowifi2200</i> supporting<br />
+<li><p>Le module <i>atheroswifi</i>, qui supporte la plupart des puces Atheros 
(à l'exception de la puce AR9285)</p></li>
+<li><p>Le module <i>broadcom43xx</i> qui supporte les cartes :<br />
+BCM4301<br />
+BCM4306<br />
+BCM4307<br />
+BCM4309<br />
+BCM4311<br />
+BCM4312<br />
+BCM4318</p></li>
+<li><p>Le module <i>iprowifi2100</i> qui supporte les puces Intel Pro Wifi 
2100</p></li>
+<li><p>Module <i>iprowifi2200</i> qui supporte les cartes :<br />
 2200BG<br />
 2225BG<br />
 2915ABG
 </p></li>
-<li><p><i>iprowifi3945</i> supporting the 3945 chips</p></li>
-<li><p><i>iprowifi4965</i> supporting the 4965 chips</p></li>
-<li><p><i>marvell88w8335</i> supporting<br />
+<li><p>Module <i>iprowifi3945</i> qui supporte les puces 3945 d’Intel</p></li>
+<li><p>Module <i>iprowifi4965</i> qui supporte les puces 4965 d’Intel</p></li>
+<li><p>Module <i>marvell88w8335</i> qui supporte les cartes :<br />
 Marvell Libertas 88W8310<br />
 Marvell Libertas 88W8335
 </p></li>
-<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
-<li><p><i>ralinkwifi</i> supporting<br />
+<li><p>Module <i>marvell88w8363</i> qui supporte les puces Marvell 
88W8363</p></li>
+<li><p>Le module <i>ralinkwifi</i> qui supporte les cartes :<br />
 RT2560<br />
 RT2561S<br />
 RT2561<br />
 RT2661
 </p></li>
-<li><p><i>wavelanwifi</i> supporting at least<br />
+<li><p>Le module <i>wavelanwifi</i> qui supporte au moins les cartes suivantes 
:<br />
 3Com Airconnect<br />
 GLPRISM2 WaveLAN<br />
 Intersil Prism3<br />
@@ -95,38 +103,39 @@
 </ul>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
-<a name="wep" rel="nofollow" id="wep">WEP encryption</a></h3>
-<p>WEP encryption is available through a command-line application <span 
class="cli">setwep</span>. It is a temporary means for joining an unencrypted 
or WEP encrypted wifi network. <span class="cli">setwep</span> works with 64- 
and 128-bit WEP and supports both text keys as well as hex digit keys (see <a 
href="#wep-notes" rel="nofollow">WEP notes</a> below)
-</p>
-<p>The usage is: <span class="cli">setwep device_path [ssid] [key]</span>. 
Below are some examples. </p>
-<p>In this example, let us assume your wifi network card is 
"/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".</p>
-<h4>Example 1: Connect with 64-bit WEP encryption using a hex digit key</h4>
+<a name="wep" rel="nofollow" id="wep">Sécurisation WEP</a></h3>
+<p>Le protocole de sécurité WEP est disponible au travers de l'application en 
ligne de commande <span class="cli">setwep</span>. 
+Il s’agit une solution temporaire pour accéder à un réseau Wifi non protégé ou 
en codage WEP. <span class="cli">setwep</span> 
+supporte les clés WEP 64 et 128 bits, indiquées sous forme hexadécimale ou 
texte. (voir les <a href="#wep-notes" rel="nofollow">remarques concernant le 
WEP</a> ci-dessous).</p>
+<p>L'usage est le suivant : <span class="cli">setwep chemin_de_périphérique 
[ssid] [clé]</span> ([ssid] est le nom du réseau à rejoindre)</p>
+<p>Voici deux exemples pour lesquels nous supposerons que votre carte réseau 
wifi est «/dev/net/iprowifi3945/0» et que le réseau sans fil est nommé 
«haikuwifi».</p>
+<h4>Exemple 1 : Se connecter avec un cryptage WEP 64 bits et une clé numérique 
hexadécimale</h4>
 <pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
-</pre><h4>Example 2: Connect to an unencrypted wireless network</h4>
+</pre><h4>Exemple 2 : Se connecter à un réseau sans fil non protégé</h4>
 <pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi
 </pre><div class="box-info">
-<li>To find out what your device_path is, have a look in Preferences -&gt; 
Network.</li>
-<li>To make your wifi device connect to a given SSID at each boot, add the 
setwep command to your home/config/boot/UserBootscript.</li>
-</div>
-<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP 
notes</strong></a></p>
+<li>Pour connaître le chemin_du_périphérique, regardez dans les préférences 
réseau (Preferences -&gt; Network)</li>
+<li>Pour connecter votre adaptateur Wifi à un réseau de SSID donné à chaque 
démarrage, ajoutez la commande <tt>setwep</tt> a votre script 
<tt>home/config/boot/UserBootscript</tt></li></div>
+<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Remarques 
concernant le WEP</strong></a></p>
 <ul>
-<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex 
digits</li>
-<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex 
digits</li>
-<li>hexadecimal digits = characters 0-9 and A through F (prepended with 
'0x')</li>
+<li>Le WEP « 64 bits » utilise une clé de 40 bits, c’est à dire 5 caractères 
alphanumériques ou 10 chiffres hexadécimaux.</li>
+<li>Le WEP « 128 bits » utilise une clé de 104 bits, c’est à dire 13 
caractères alphanumériques ou 26 chiffres hexadécimaux.</li>
+<li>Un chiffre hexadécimal est un chiffre de 0 à 9 ou une lettre de 0 à F. Un 
nombre hexadécimal doit être précédé de « 0x » lorsqu’il est utilisé dans 
<tt>setwep</tt>.</li>
 </ul>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
-<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
-<p>At the moment there is no WPA encryption available in Haiku. However, there 
is some <a target="_blank" class="ext" 
href="http://alexbl.net/%7Ealexbl/haiku-wpa/"; rel="nofollow">preliminary and 
unfinished code for implementing WPA</a><span class="ext"></span> available. 
Some tasks for improving this is to plug it into the wpa_supplicant build 
process and then fixing compile &amp; runtime issues.</p>
+<a name="wpa" rel="nofollow" id="wpa">Le cryptage WPA</a></h3>
+<p>Pour le moment, le codage WPA n'est pas disponible dans Haiku. Cependant, 
il existe une ébauche de <a target="_blank" class="ext" 
href="http://alexbl.net/%7Ealexbl/haiku-wpa/"; rel="nofollow">code pour la mise 
en œuvre de cette sécurité</a><span class="ext"></span>.
+Il reste notamment à intégrer le processus de construction du gestionnaire 
wpa_supplicant et à corriger des problèmes de compilation et d’exécution.</p>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
 <a name="install_script" rel="nofollow" 
id="install_script">install-wifi-firmwares.sh</a></h3>
-<p>To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, 
Broadcom 43xx &amp; Marvell 88W8335, you'll need to run</p>
-<pre class="terminal">~&gt; install-wifi-firmwares.sh
+<p>Pour installer le micro-logiciel des cartes Intel ipw2100, Intel 
ipw2200/2225/2915, Broadcom 43xx et Marvell 88W8335 vous devez exécuter la 
commande</p>
+<pre class="terminal">install-wifi-firmwares.sh
 </pre>
-<p>The Intel ipw2100 and ipw22xx will install without an internet connection, 
as the licensing terms allow Haiku to distribute the original firmware 
archives. However, they do require acknowledgment by the end-user prior to 
their installation. The Broadcom 43xx and Marvell 88W8335 will require an 
active internet connection, as the files containing their respective firmwares 
cannot be distributed with Haiku.</p>
-<p>People building their own Haiku image can modify their <span 
class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and 
general updates on the wifi topic are found at the <a 
href="http://www.haiku-os.org/guides/wifi";>online version of this 
document</a>.</p>
-<p>If you have to download the firmware, but don't have a working internet 
connection under Haiku, the online version offers a <a 
href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt"; 
rel="nofollow">shell script</a>, which will create a zip file for you to 
extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by 
install-wifi-firmwares.sh.</p>
+<p>Les pilotes Intel ipw2100 et ipw22xx pourront être installés sans qu’une 
connexion Internet soit présente, car la distribution, dans Haiku, des fichiers 
contenant les micro-logiciels originaux est autorisée par leur licence. En 
revanche, vous devrez accepter les termes de cette licence avant 
l’installation. Les pilotes Broadcom 43xx et Marvell 88W8335 nécessiteront une 
connexion Internet pour s’installer, car les fichiers contenant leurs 
micro-logiciels respectifs ne peuvent être redistribués avec Haiku.</p>
+<p>Si vous compilez vous-même Haiku, vous pouvez modifier votre fichier <span 
class="cli">build/jam/UserBuildConfig</span> afin de pouvoir utiliser cet 
outil. Vous pourrez trouver plus de détails sur le Wifi dans Haiku sur la <a 
href="http://www.haiku-os.org/guides/wifi";>version en ligne de ce document</a> 
(en anglais).</p>
+<p>Si il vous faut télécharger le micro-logiciel mais que vous n'avez pas de 
connexion internet qui fonctionne sous Haiku, la version en ligne vous propose 
aussi un <a 
href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt"; 
rel="nofollow">script de commande</a>, qui crée un fichier zip à extraire dans 
le dossier <tt>/boot</tt> de Haiku. Après cela, vous aurez tous les fichiers 
nécessaires pour install-wifi-firmwares.sh.</p>
 </div>
 </div>
 

Added: haiku/branches/releases/r1alpha2/docs/welcome/images/flags/jp.png
===================================================================
(Binary files differ)


Property changes on: 
haiku/branches/releases/r1alpha2/docs/welcome/images/flags/jp.png
___________________________________________________________________
Added: svn:mime-type
   + application/octet-stream

Added: haiku/branches/releases/r1alpha2/docs/welcome/jp/bugreports.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/jp/bugreports.html            
                (rev 0)
+++ haiku/branches/releases/r1alpha2/docs/welcome/jp/bugreports.html    
2010-05-08 15:00:22 UTC (rev 36744)
@@ -0,0 +1,104 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<html xmlns="http://www.w3.org/1999/xhtml"; lang="en-US" xml:lang="en-US"> 
+<head>
+<!-- 
+ *
+ * Copyright 2008-2009, Haiku. All rights reserved.
+ * Distributed under the terms of the MIT License.
+ *
+ * Authors:
+ *             Niels Reedijk and Matt Madia who wrote 
http://dev.haiku-os.org/wiki 
+ *             Humdinger <humdingerb@xxxxxxxxx>
+ *
+-->
+       <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+       <meta name="robots" content="all" />
+       <title>Reporting bugs</title>
+       <link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
+</head>
+<body>
+
+<div id="banner">
+<div><span>User guide</span></div>
+</div>
+
+<div class="nav">
+<div class="inner">
+<ul class="lang-menu">
+<li class="now"><img src="../images/flags/jp.png" alt="" /> 日本語</li>
+<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" 
/>Français</a></li>
+<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
+<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
+<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
+<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
+</ul>
+<span>
+    <a href="../welcome_jp.html" class="uplink">Welcome</a>
+</span></div>
+</div>
+
+<div id="content">
+<div>
+<div class="box-info">The translation of this page isn't yet complete. Until 
it is, unfinished parts use the English original.</div>
+
+<h1>Reporting bugs</h1>
+
+<p>Since our developers are unable to test every hardware combination, nor 
every different way of interacting with the operating system, we are relying on 
users to give us some input on how things work at their end. Since Haiku is 
still quite young, it's very likely that you will encounter bugs. We thank you 
for taking the time to report these. Together we can improve Haiku, bit by 
bit.</p>
+<p>To keep our bugtracker effective, it's essential to abide by the <a 
href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette";>Bug Tracker 
Etiquette</a>.</p>
+
+<h2>Getting a Trac account</h2>
+<p>To file a ticket, you need to have an account at <a 
href="http://dev.haiku-os.org/register"; title="Register at Haiku's 
Bugtracker">Haiku's Bugtracker</a>.<br />
+When creating a new account, be certain to <b>provide your email address</b> 
as it is necessary to obtain basic ticket modification privileges. Be sure to 
<b>check your spam folder</b> shortly afterwards, as the all important 
verification mail often ends up there.</p>
+
+<h2>Creating a bug report</h2>
+<p>Before reporting a bug, please <a 
href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority";>make
 sure</a> that it does not yet exist. You can also use the <a 
href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on";>search</a>
 function for this.<br />
+After you have established that it's a unique bug, make your information as 
accurate as possible:</p>
+<ul>
+       <li><p>Include basic information such as how you are testing Haiku (on 
real hardware, on VMWare, on QEMU, etc.).</p></li>
+       <li><p>Mention which revision from <acronym title="Subversion, the 
source code management system we use">SVN</acronym> you are running. You can 
find this information in '<i>About This System...</i>' from the Deskbar 
menu.</p></li>
+       <li><p>Describe the problem you are experiencing. Try to be as accurate 
as you can: describe the actual behavior, and the behavior you 
expected.</p></li>
+       <li><p>Describe what steps you need to perform in order to expose the 
bug. This will help developers reproduce the bug.</p></li>
+       <li><p>Attach as much information as you have. If it is a GUI bug, or a 
bug in one of the applications, try to make a screen shot (the <span 
class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics 
image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
+</ul>
+       
+<h3>Software Bugs</h3>
+<p>When an application crashed, you should invoke the debugger from the alert 
that pops up. Entering <span class="cli">bt</span> into the launched debug 
Terminal, you create a "backtrace" that you should copy into your bug 
report.</p>
+
+<h3>Hardware Bugs</h3>
+<p>When dealing with a hardware/driver related bug, you should attach the 
following information:</p>
+<ul>
+<li><span class="cli">listdev</span> - a detailed listing of your hardware, 
including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> 
and <span class="cli">lspci</span>.</li>
+<li><span class="cli">listusb -v</span> - assuming its a USB related issue, 
similar to <span class="cli">lsusb</span>.</li>
+<li><span class="cli">open /var/log/syslog</span> - the primary system log 
used by Haiku, akin to on screen debugging during boot. With the <span 
class="cli">open</span> command you can crop down the relevant part of the 
syslog in a text editor.</li>
+<li><span class="cli">listimage | grep drivers/</span> - lists all used 
drivers.</li>
+<li><span class="cli">ints</span> - only available within <i>Kernel Debugging 
Land</i> (see below). Shows interrupt usage. There shouldn't be too many that 
are shared by different devices.</li>
+</ul>
+<p>You enter these commands into Terminal. Add a <span class="cli"> &gt; 
output.txt</span> after a command, and it's piped into a text file called 
"output.txt" that you can attach to your bug report or email.</p>
+
+<h3>Kernel Debugging Land - KDL</h3>
+<p>When some very low level system component crashed, you may end up in the 
kernel debugger. It can also be entered deliberately with <span 
class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> 
(<span class="key">SysReq</span> being <span class="key">PRINT</span> on most 
keyboards).</p>
+<ul>
+<li><span class="cli">co</span> - will exit KDL and continue normal system 
operation, if possible.</li>
+<li><span class="cli">int</span> - will show interrupt usage (as described 
above).</li>
+<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly 
the crash happened.</li>
+</ul>
+
+<h2>What's next?</h2>
+<p>After the bug has been reported, a developer will look at your bug and try 
to classify it. Remember, we are all volunteers, and as such, sometimes a bug 
report might go unanswered for a while. Adding new information when it becomes 
available usually helps getting a bug picked up quicker, but do not try to 
'bump' the bug up by adding
+non-descriptive comments.</p>
+<p>Remember, reporting a bug is not something you spend a little time on and 
then you are done. If you reported a bug, then you are part of the Haiku 
development process. Developers might come up with questions while they are 
trying to fix your bug. Please stay around to answer these. Consider your 
participation 'done' when the bug is marked
+as 'fixed'.</p>
+
+</div>
+</div>
+
+<div class="nav">
+<div class="inner"><span>
+    <a href="../welcome_jp.html" class="uplink">Welcome</a>
+</span></div>
+</div>
+
+</body>
+</html>

Added: haiku/branches/releases/r1alpha2/docs/welcome/jp/wifi.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/jp/wifi.html                  
        (rev 0)
+++ haiku/branches/releases/r1alpha2/docs/welcome/jp/wifi.html  2010-05-08 
15:00:22 UTC (rev 36744)
@@ -0,0 +1,142 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<html xmlns="http://www.w3.org/1999/xhtml"; lang="en" xml:lang="en">
+<head>
+<!-- 
+ *
+ * Copyright 2010, Haiku. All rights reserved.
+ * Distributed under the terms of the MIT License.
+ *
+ * Authors:
+*              Matt Madia who wrote http://www.haiku-os.org/guides/wifi 
+ *             Humdinger <humdingerb@xxxxxxxxx>
+ *
+-->
+       <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+       <meta http-equiv="Content-Style-Type" content="text/css" />
+       <meta name="robots" content="all" />
+       <title>Wifi</title>
+       <link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
+</head>
+<body>
+
+<div id="banner">
+<div><span>User guide</span></div>
+</div>
+
+<div class="nav">
+<div class="inner">
+<ul class="lang-menu">
+<li class="now"><img src="../images/flags/jp.png" alt="" /> 日本語</li>
+<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" 
/>Français</a></li>
+<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
+<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" 
/>Русский</a></li>
+<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
+<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
+</ul>
+
+<span>
+   <a href="../welcome_jp.html" class="uplink">Welcome</a>
+</span></div>
+</div>
+
+<div id="content">
+<div>
+<div class="box-info">The translation of this page isn't yet complete. Until 
it is, unfinished parts use the English original.</div>
+
+<h2>Wifi in Haiku</h2>
+<h3>
+<a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
+<a name="hardware" rel="nofollow" id="hardware">Expected supported 
hardware</a></h3>
+<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, 
ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, 
PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
+This includes:
+</p>
+<ul>
+<li><p><i>aironetwifi</i> supporting at least<br />
+Cisco Aironet 350 Series<br />
+Aironet PCI4500<br />
+Aironet PCI4800<br />
+</p></li>
+<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no 
AR9285 chips)</p></li>
+<li><p><i>broadcom43xx</i> supporting<br />
+BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
+</p></li>
+<li><p><i>iprowifi2100</i> supporting the 2100 chips</p></li>
+<li><p><i>iprowifi2200</i> supporting<br />
+2200BG<br />
+2225BG<br />
+2915ABG
+</p></li>
+<li><p><i>iprowifi3945</i> supporting the 3945 chips</p></li>
+<li><p><i>iprowifi4965</i> supporting the 4965 chips</p></li>
+<li><p><i>marvell88w8335</i> supporting<br />
+Marvell Libertas 88W8310<br />
+Marvell Libertas 88W8335
+</p></li>
+<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
+<li><p><i>ralinkwifi</i> supporting<br />
+RT2560<br />
+RT2561S<br />
+RT2561<br />
+RT2661
+</p></li>
+<li><p><i>wavelanwifi</i> supporting at least<br />
+3Com Airconnect<br />
+GLPRISM2 WaveLAN<br />
+Intersil Prism3<br />
+Intersil Prism2.5<br />
+Linksys WDT11<br />
+Netgear MA301<br />
+PRISM2STA WaveLAN<br />
+Siemens SpeedStream<br />
+SMC 2602W<br />
+Us Robotics 2415<br />
+Addtron AWA-100 PCI
+</p></li>
+</ul>
+<h3>
+<a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
+<a name="wep" rel="nofollow" id="wep">WEP encryption</a></h3>
+<p>WEP encryption is available through a command-line application <span 
class="cli">setwep</span>. It is a temporary means for joining an unencrypted 
or WEP encrypted wifi network. <span class="cli">setwep</span> works with 64- 
and 128-bit WEP and supports both text keys as well as hex digit keys (see <a 
href="#wep-notes" rel="nofollow">WEP notes</a> below).
+</p>
+<p>The usage is: <span class="cli">setwep device_path [ssid] [key]</span></p>
+<p>Below are two examples. Let us assume your wifi network card is 
"/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".</p>
+<h4>Example 1: Connect with 64-bit WEP encryption using a hex digit key</h4>
+<pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
+</pre><h4>Example 2: Connect to an unencrypted wireless network</h4>
+<pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi
+</pre><div class="box-info">
+<li>To find out what your device_path is, have a look in Preferences -&gt; 
Network</li>
+<li>To make your wifi device connect to a given SSID at each boot, add the 
<tt>setwep</tt> command to your <tt>home/config/boot/UserBootscript</tt></li>
+</div>
+<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP 
notes</strong></a></p>
+<ul>
+<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex 
digits</li>
+<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex 
digits</li>
+<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" 
in <tt>setwep</tt>)</li>
+</ul>
+<h3>
+<a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
+<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
+<p>At the moment there is no WPA encryption available in Haiku. However, there 
is some <a target="_blank" class="ext" 
href="http://alexbl.net/%7Ealexbl/haiku-wpa/"; rel="nofollow">preliminary and 
unfinished code for implementing WPA</a><span class="ext"></span> available. 
Some tasks for improving this is to plug it into the wpa_supplicant build 
process and then fixing compile &amp; runtime issues.</p>
+<h3>
+<a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
+<a name="install_script" rel="nofollow" 
id="install_script">install-wifi-firmwares.sh</a></h3>
+<p>To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, 
Broadcom 43xx &amp; Marvell 88W8335, you need to run</p>
+<pre class="terminal">install-wifi-firmwares.sh
+</pre>
+<p>The Intel ipw2100 and ipw22xx will install without an internet connection, 
as the licensing terms allow Haiku to distribute the original firmware 
archives. However, they do require acknowledgment by the end-user prior to 
their installation. The Broadcom 43xx and Marvell 88W8335 will require an 
active internet connection, as the files containing their respective firmwares 
cannot be distributed with Haiku.</p>
+<p>People building their own Haiku image can modify their <span 
class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and 
general updates on the wifi topic are found at the <a 
href="http://www.haiku-os.org/guides/wifi";>online version of this 
document</a>.</p>
+<p>If you have to download the firmware, but don't have a working internet 
connection under Haiku, the online version offers a <a 
href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt"; 
rel="nofollow">shell script</a>, which will create a zip file for you to 
extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by 
install-wifi-firmwares.sh.</p>
+</div>
+</div>
+
+<div class="nav">
+<div class="inner"><span>
+   <a href="../welcome_jp.html" class="uplink">Welcome</a>
+</span></div>
+</div>
+
+</body>
+</html>

Modified: haiku/branches/releases/r1alpha2/docs/welcome/ru/bugreports.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/ru/bugreports.html    
2010-05-08 14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/ru/bugreports.html    
2010-05-08 15:00:22 UTC (rev 36744)
@@ -12,6 +12,7 @@
  *             Humdinger <humdingerb@xxxxxxxxx>
  * Translators:
  *             Michael Smirnov
+ *             Diver
  *
 -->
        <meta http-equiv="content-type" content="text/html; charset=utf-8" />
@@ -32,6 +33,7 @@
 <li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" 
/>Français</a></li>
 <li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
 <li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
 </ul>
@@ -67,11 +69,11 @@
 <p>Когда приложение аварийно завершилось, вы должны использовать автоматически 
открывающийся отладчик. Введя в окне терминала с дебагером <span 
class="cli">bt</span>, вы создаёте "трассировку", которую необходимо 
скопировать в ваш багрепорт.</p>
 
 <h3>Аппаратные ошибки</h3>
-<p>Если вы столкнулись с ошибкой работы аппаратных средств и/или их драйвера, 
то вы должны приложить следующую информацию:</p>
+<p>Если вы столкнулись с ошибкой работы оборудования и/или драйвера, то вы 
должны приложить следующую информацию:</p>
 <ul>
 <li><span class="cli">listdev</span> - подробный список оборудования, 
включающий ID поставщиков и отдельных устройств, схожа с командами Linux <span 
class="cli">lshw</span> и <span class="cli">lspci</span>.</li>
 <li><span class="cli">listusb -v</span> - при ошибке, связанной с USB, 
аналогична команде <span class="cli">lsusb</span>.</li>
-<li><span class="cli">open /var/log/syslog</span> - основной системный лог 
используемый Haiku, сродни выводимой на экран отладочной информации при 
загрузке в соответствующем режиме. С командой <span class="cli">open</span> 
можно вырезать нужную часть лога в текстовом редакторе.</li>
+<li><span class="cli">open /var/log/syslog</span> - основной системный лог, 
используемый Haiku, сродни выводимой на экран отладочной информации при 
загрузке в соответствующем режиме. С командой <span class="cli">open</span> 
можно вырезать нужную часть лога в текстовом редакторе.</li>
 <li><span class="cli">listimage | grep drivers/</span> - список всех 
задействованных драйверов.</li>
 <li><span class="cli">ints</span> - доступна только в режиме <i>Царства 
отладки ядра (Kernel Debugging Land - KDL)</i> (см. ниже), отображает 
используемые прерывания. Не должно быть слишком много устройств, использующих 
одно прерывание.</li>
 </ul>
@@ -86,8 +88,8 @@
 </ul>
 
 <h2>Что дальше?</h2>
-<p>После того как багрепорт отправлен, разработчик рассмотрит вашу ошибку и 
попытаться классифицировать ее. Помните, что мы все добровольцы, и  иногда 
багрепорт может оставаться без ответа некоторое время. Добавление новой 
информации об ошибке помогает исправить её быстрее, но не пытайтесь увеличить 
её значимость, добавляя не относящиеся к делу комментарии.</p>
-<p>Помните, что отправка багрепорта, на который вы потратили некоторое время - 
это ещё полдела, и желательно чтобы вы следили за его состоянием. Только в этом 
случае вы внесёте ощутимую часть в процесс развития Haiku. У разработчиков 
могут возникнуть вопросы, относящиеся к багу во время его исправления, 
пожалуйста, не игнорируйте их, постаравшись как можно подробней ответить. 
Считайте свое участие законченным, только когда ошибка пиобритёт статус 
"исправлено (fixed)".</p>
+<p>После того как багрепорт отправлен, разработчик рассмотрит вашу ошибку и 
попытаться классифицировать ее. Помните, что мы все добровольцы, и  иногда 
багрепорт может оставаться без ответа некоторое время. Добавление новой 
информации к этой ошибке помогает исправить её быстрее, но не пытайтесь 
увеличить её значимость, добавляя не относящиеся к делу комментарии.</p>
+<p>Помните, что отправка багрепорта, на который вы потратили некоторое время - 
это ещё полдела, и желательно чтобы вы следили за его состоянием. Только в этом 
случае вы внесёте ощутимую часть в процесс развития Haiku. У разработчиков 
могут возникнуть вопросы, относящиеся к багу во время его исправления, 
пожалуйста, не игнорируйте их, постаравшись как можно подробней ответить. 
Считайте свое участие законченным, только когда ошибка приобретёт статус 
"исправлено (fixed)".</p>
 
 </div>
 </div>

Modified: haiku/branches/releases/r1alpha2/docs/welcome/ru/wifi.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/ru/wifi.html  2010-05-08 
14:58:32 UTC (rev 36743)
+++ haiku/branches/releases/r1alpha2/docs/welcome/ru/wifi.html  2010-05-08 
15:00:22 UTC (rev 36744)
@@ -10,18 +10,20 @@
  * Authors:
 *              Matt Madia who wrote http://www.haiku-os.org/guides/wifi 
  *             Humdinger <humdingerb@xxxxxxxxx>
+ * Translators:
+ *             Diver
  *
 -->
        <meta http-equiv="content-type" content="text/html; charset=utf-8" />
        <meta http-equiv="Content-Style-Type" content="text/css" />
        <meta name="robots" content="all" />
-       <title>Wifi</title>
+       <title>Беспроводная сеть Wifi</title>
        <link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
 </head>
 <body>
 
 <div id="banner">
-<div><span>User guide</span></div>
+<div><span>Руководство пользователя</span></div>
 </div>
 
 <div class="nav">
@@ -31,6 +33,7 @@
 <li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" 
/>Français</a></li>
 <li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" 
/>Deutsch</a></li>
 <li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" 
/>Español</a></li>
+<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" 
/>日本語</a></li>
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" 
/>Українська</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" 
/>English</a></li>
 </ul>
@@ -43,43 +46,44 @@
 <div id="content">
 <div>
 
-<h2>Wifi in Haiku</h2>
+<h2>Беспроводная сеть Wifi в Haiku</h2>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
-<a name="hardware" rel="nofollow" id="hardware">Expected supported 
hardware</a></h3>
-<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, 
ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, 
PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
-This includes:
+<a name="hardware" rel="nofollow" id="hardware">Поддерживаемое 
оборудование:</a></h3>
+<p>Должны работать все wlan драйвера, поддерживаемые FreeBSD 8. <br />
+Не поддерживаются все PCMCIA, CardBus, ExpressCard, USB и ISA карты. <br 
/>Поддерживаются только PCI, miniPCI, PCI-Express, miniPci-Express и PCI-X.<br 
/>
+
 </p>
 <ul>
-<li><p><i>aironetwifi</i> supporting at least<br />
+<li><p><i>aironetwifi</i> поддерживает как минимум:<br />
 Cisco Aironet 350 Series<br />
 Aironet PCI4500<br />
 Aironet PCI4800<br />
 </p></li>
-<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no 
AR9285 chips)</p></li>
-<li><p><i>broadcom43xx</i> supporting<br />
+<li><p><i>atheroswifi</i> поддерживает почти все существующие чипсеты (кроме 
чипов AR9285)</p></li>
+<li><p><i>broadcom43xx</i> поддерживает:<br />
 BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
 </p></li>
-<li><p><i>iprowifi2100</i> supporting the 2100 chips</p></li>
-<li><p><i>iprowifi2200</i> supporting<br />
+<li><p><i>iprowifi2100</i> поддерживает 2100 чипсет</p></li>
+<li><p><i>iprowifi2200</i> поддерживает:<br />
 2200BG<br />
 2225BG<br />
 2915ABG
 </p></li>
-<li><p><i>iprowifi3945</i> supporting the 3945 chips</p></li>
-<li><p><i>iprowifi4965</i> supporting the 4965 chips</p></li>
-<li><p><i>marvell88w8335</i> supporting<br />
+<li><p><i>iprowifi3945</i> поддерживает 3945 чипсет</p></li>
+<li><p><i>iprowifi4965</i> поддерживает 4965 чипсет</p></li>
+<li><p><i>marvell88w8335</i> поддерживает:<br />
 Marvell Libertas 88W8310<br />
 Marvell Libertas 88W8335
 </p></li>
-<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
-<li><p><i>ralinkwifi</i> supporting<br />
+<li><p><i>marvell88w8363</i> поддерживает 88W8363 чипсет</p></li>
+<li><p><i>ralinkwifi</i> поддерживает:<br />
 RT2560<br />
 RT2561S<br />
 RT2561<br />
 RT2661
 </p></li>
-<li><p><i>wavelanwifi</i> supporting at least<br />
+<li><p><i>wavelanwifi</i> поддерживает как минимум:<br />
 3Com Airconnect<br />
 GLPRISM2 WaveLAN<br />
 Intersil Prism3<br />
@@ -95,38 +99,38 @@
 </ul>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
-<a name="wep" rel="nofollow" id="wep">WEP encryption</a></h3>
-<p>WEP encryption is available through a command-line application <span 
class="cli">setwep</span>. It is a temporary means for joining an unencrypted 
or WEP encrypted wifi network. <span class="cli">setwep</span> works with 64- 
and 128-bit WEP and supports both text keys as well as hex digit keys (see <a 
href="#wep-notes" rel="nofollow">WEP notes</a> below)
+<a name="wep" rel="nofollow" id="wep">WEP шифрование</a></h3>
+<p>WEP шифрование доступно через консольное приложение <span 
class="cli">setwep</span>. Это временный способ для подключения к незащищенным 
сетям или к сетям, использующим WEP шифрование. Приложение <span 
class="cli">setwep</span> работает с 64- и 128-битным WEP шифрованием и 
поддерживает как текстовые ключи, так и шестнадцатеричные ключи (смотрите <a 
href="#wep-notes" rel="nofollow">примечание про WEP</a> ниже).
 </p>
-<p>The usage is: <span class="cli">setwep device_path [ssid] [key]</span>. 
Below are some examples. </p>
-<p>In this example, let us assume your wifi network card is 
"/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".</p>
-<h4>Example 1: Connect with 64-bit WEP encryption using a hex digit key</h4>
+<p>Использование: <span class="cli">setwep device_path [ssid] [key]</span></p>
+<p>Ниже приведены два примера. Допустим, Ваша wifi сетевая карта это 
"/dev/net/iprowifi3945/0", а беспроводная сеть называется "haikuwifi".</p>
+<h4>Пример 1: Подключение с 64-битным WEP шифрованием, используя 
шестнадцатеричный ключ</h4>
 <pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
-</pre><h4>Example 2: Connect to an unencrypted wireless network</h4>
+</pre><h4>Пример 2: Подключение к незашифрованной беспроводной сети</h4>
 <pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi
 </pre><div class="box-info">
-<li>To find out what your device_path is, have a look in Preferences -&gt; 
Network.</li>
-<li>To make your wifi device connect to a given SSID at each boot, add the 
setwep command to your home/config/boot/UserBootscript.</li>
+<li>Чтобы узнать какой у Вас device_path is, посмотрите в Preferences -&gt; 
Network</li>
+<li>Если вы хотите, чтобы Ваше wifi устройство подключалось к данной SSID 
после каждой загрузке, добавьте команду <tt>setwep</tt> в Ваш 
<tt>home/config/boot/UserBootscript</tt></li>
 </div>
-<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP 
notes</strong></a></p>
+<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>Примечания про 
WEP</strong></a></p>
 <ul>
-<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex 
digits</li>
-<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex 
digits</li>
-<li>hexadecimal digits = characters 0-9 and A through F (prepended with 
'0x')</li>
+<li>64-битное WEP использует 40-битный ключ, что эквивалентно 5 буквам или 10 
цифрам</li>
+<li>128-битное WEP использует 104-битный ключ, что эквивалентно 13 буквам или 
26 цифрам</li>
+<li>шестнадцатеричная система = цифры  0-9 и буквы от A до F (начинающиеся с 
"0x" в <tt>setwep</tt>)</li>
 </ul>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
-<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
-<p>At the moment there is no WPA encryption available in Haiku. However, there 
is some <a target="_blank" class="ext" 
href="http://alexbl.net/%7Ealexbl/haiku-wpa/"; rel="nofollow">preliminary and 
unfinished code for implementing WPA</a><span class="ext"></span> available. 
Some tasks for improving this is to plug it into the wpa_supplicant build 
process and then fixing compile &amp; runtime issues.</p>
+<a name="wpa" rel="nofollow" id="wpa">WPA шифрование</a></h3>
+<p>В настоящий момент WPA шифрование не поддерживается в Haiku. Однако 
существует экспериментальный незавершенный код, реализующий поддержку <a 
target="_blank" class="ext" href="http://alexbl.net/%7Ealexbl/haiku-wpa/"; 
rel="nofollow">WPA</a><span class="ext"></span>. Этот код потребуется внедрить 
в процесс сборки wpa_supplicant, а затем ликвидировать  ошибки при компиляции и 
возможные проблемы при работе.</p>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" 
alt="index" /></a>
 <a name="install_script" rel="nofollow" 
id="install_script">install-wifi-firmwares.sh</a></h3>
-<p>To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, 
Broadcom 43xx &amp; Marvell 88W8335, you'll need to run</p>
+<p>Для установки микропрограмм для Intel ipw2100, Intel ipw2200/2225/2915, 
Broadcom 43xx и Marvell 88W8335 нужно запустить:</p>
 <pre class="terminal">~&gt; install-wifi-firmwares.sh
 </pre>
-<p>The Intel ipw2100 and ipw22xx will install without an internet connection, 
as the licensing terms allow Haiku to distribute the original firmware 
archives. However, they do require acknowledgment by the end-user prior to 
their installation. The Broadcom 43xx and Marvell 88W8335 will require an 
active internet connection, as the files containing their respective firmwares 
cannot be distributed with Haiku.</p>
-<p>People building their own Haiku image can modify their <span 
class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and 
general updates on the wifi topic are found at the <a 
href="http://www.haiku-os.org/guides/wifi";>online version of this 
document</a>.</p>
-<p>If you have to download the firmware, but don't have a working internet 
connection under Haiku, the online version offers a <a 
href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt"; 
rel="nofollow">shell script</a>, which will create a zip file for you to 
extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by 
install-wifi-firmwares.sh.</p>
+<p>Intel ipw2100 и ipw22xx установятся без Интернет-соединения, так как 
лицензионные условия позволяют Haiku распространять архивы с микропрограммой 
(firmware). Однако они требуют ознакомления конечного пользователя с условиями 
лицензии перед их установкой. Broadcom 43xx и Marvell 88W8335 требуют 
работающего Интернет-соединения, так как файлы, содержащие их микропрограммы 
(firmwares), не могут распространяться с Haiku.</p>
+<p>Те, кто самостоятельно собирают  собственные образы Haiku, могут 
соответственным образом изменить свой <span 
class="cli">build/jam/UserBuildConfig</span>. Описание этого процесса, а также 
обновление информации по поддержке wifi можно найти в <a 
href="http://www.haiku-os.org/guides/wifi";>онлайн-версии</a> этого 
документа.</p>
+<p>Если вы скачали микропрограмму (firmware), но не имеете работающего 
Интернет-соединения в Haiku, то онлайн-версия предлагает <a 
href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt"; 
rel="nofollow">скрипт</a>, который создаст для Вас zip файл, который нужно 
будет извлечь в директорию <tt>/boot</tt>. После этого у Вас будут все файлы, 
необходимые для запуска install-wifi-firmwares.sh.</p>
 </div>
 </div>
 

Modified: haiku/branches/releases/r1alpha2/docs/welcome/uk/bugreports.html
===================================================================
--- haiku/branches/releases/r1alpha2/docs/welcome/uk/bugreports.html    
2010-05-08 14:58:32 UTC (rev 36743)

[... truncated: 571 lines follow ...]
[haiku-commits] r36744 - in haiku/branches/releases/r1alpha2/docs/welcome: . de en es fr ...

Other related posts:
