Update userguide and welcome documentation with the latest additions and translations from i18n.haiku-os.org.

docs/welcome/de/bugreports.html

@@ -41,6 +41,8 @@
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
@@ -81,7 +83,7 @@ Nach dieser Überprüfung sollte man so genau wie möglich den Fehler beschreibe
 <ul>
 	<li><p>Der Fehler sollte mit einer aktuellen Version von Haiku zu reproduzierbar sein. Zum Testen gibt es installierbare <a href="http://haiku-files.org/">Images</a>.</p></li>
 	<li><p>Wie wurde Haiku verwendet (auf echter Hardware oder virtualisiert unter VMWare, QEMU oder ähnlichem)?</p></li>
-	<li><p>Welche Versionsnummer aus dem <acronym title="Subversion, unser Source Code Management System">SVN</acronym> wurde verwendet? Die Version ist auch unter <span class="menu">About Haiku...</span> im Deskbar Menü zu finden. Wie genau Haiku kompiliert wurde (gcc2, gcc4, gcc2hybrid, gcc4hybrid), ist ebenfalls von Interesse. Die runterladbaren Images sind entsprechend benannt; Leute, die sich ihr Haiku selber zusammenbauen, sollten wissen wie sie das gemacht haben.</p></li>
+	<li><p>Welche Versionsnummer aus dem <acronym title="Subversion, unser Source Code Management System">SVN</acronym> wurde verwendet? Die Version ist auch unter <span class="menu">Über Haiku...</span> im Deskbar Menü zu finden. Wie genau Haiku kompiliert wurde (gcc2, gcc4, gcc2hybrid, gcc4hybrid), ist ebenfalls von Interesse. Die runterladbaren Images sind entsprechend benannt; Leute, die sich ihr Haiku selber zusammenbauen, sollten wissen wie sie das gemacht haben.</p></li>
 	<li><p>Der Fehler sollte so präzise wie möglich beschrieben werden. Welches Verhalten wurde erwartet und was wurde statt dessen beobachtet?</p></li>
 	<li><p>Wann tritt der Fehler auf? Nur mit einer Schritt-für-Schritt Anleitung können die Entwickler den Bug nachstellen und beheben.</p></li>
 	<li><p>An den Fehlerbericht sollten so viele Informationen wie möglich angehängt werden. Handelt es sich um einen Bug in der grafischen Oberfläche oder einer der Anwendungen, ist ein Bildschirmfoto mittels der <span class="key">DRUCK</span> Taste hilfreich.</p></li>
@@ -106,7 +108,7 @@ Außer dass alles etwas unansehnlicher und unbequemer ist, gilt eigentlich das g
 <li><p>Das System fährt nicht mehr richtig hoch. Unter Umständen führt es spontan einen Neustart durch oder bleibt an einer Stelle stecken, vielleicht bei einem bestimmten Symbol des Boot Bildschirms. In letzterem Falle sollte man auch mal ein <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> versuchen.</p></li>
 <li><p>Das ganze System oder eine bestimmte Hardwarekomponente funktioniert nicht richtig. Es könnte beispielsweise nur sehr langsam laufen, Fehler könnten auftreten oder etwas funktioniert überhaupt nicht. Verweigert eine Hardwarekomponente die Arbeit komplett, sollte man natürlich erst mal checken, ob Haiku sie momentan überhaupt treibermäßig unterstützt, indem man zum Beispiel auf der Mainlingliste oder im Forum nachfragt.</p></li>
 </ul>
-<p>Während nur der letzte Punkt explizit auf eine Hardware-Ursache eingeht, können auch alle anderen Symptome auf Fehler in einem Hardware Treiber hindeuten. Hat man einen Verdacht welche Hardware oder entsprechender Treiber mit dem Problem zu tun haben könnte, sollte man prüfen ob das Entfernen oder Deaktivieren von Hardware oder Treiber Abhilfe schafft. Wenn man das Problem beispielsweise beim WLAN vermutet, könnte diese Funktion vielleicht im BIOS ausgeschaltet werden. Wenn nicht, kann man auch den entsprechenden Treiber aus dem System entfernen (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
+<p>Während nur der letzte Punkt explizit auf eine Hardware-Ursache eingeht, können auch alle anderen Symptome auf Fehler in einem Hardware Treiber hindeuten. Hat man einen Verdacht welche Hardware oder entsprechender Treiber mit dem Problem zu tun haben könnte, sollte man prüfen ob das Entfernen oder Deaktivieren von Hardware oder Treiber Abhilfe schafft. Wenn man das Problem beispielsweise beim WLAN vermutet, könnte diese Funktion vielleicht im BIOS ausgeschaltet werden. Wenn nicht, kann man auch den entsprechenden Treiber aus dem System entfernen (in <span class="path"><acronym title="/boot/system/add-ons/kernel/drivers/bin">/boot/System/add-ons/kernel/drivers/bin</acronym></span>).</p>
 
 <h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
@@ -125,7 +127,7 @@ Im KDL kann es passieren, dass die Tastatur nicht mehr funktioniert. PS/2 Tastat
 <h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="syslog" name="syslog">Syslog</a></h3>
 <p><b>Dies ist die beste Methode Informationen über ein nicht-bootendes System zu gewinnen.</b><br />
-Das Syslog (kurz für System Log) enthält wertvolle Infos was im System abläuft, einschließlich der Ausgaben einer KDL Sitzung. Man sollte es immer an einen Trac Ticket hängen wenn es etwas mit dem Kernel zu tun haben könnte. Das Syslog befindet sich in der Datei <span class="path">/boot/common/var/log/syslog</span>. Um in eine Datei schreiben zu können, braucht man ein funktionierendes System. Tritt ein Problem im Kernel auf (insbesondere bei spontanen Neustarts und nicht-fortsetzbaren KDL Sitzungen), kann es daher passieren dass es die letzten Ausgaben nicht mehr ins Syslog schaffen.</p>
+Das Syslog (kurz für System Log) enthält wertvolle Infos was im System abläuft, einschließlich der Ausgaben einer KDL Sitzung. Man sollte es immer an einen Trac Ticket hängen wenn es etwas mit dem Kernel zu tun haben könnte. Das Syslog befindet sich in der Datei <span class="path"><acronym title="/boot/common/var/log/syslog">/boot/Allgemein/var/log/syslog</acronym></span>. Um in eine Datei schreiben zu können, braucht man ein funktionierendes System. Tritt ein Problem im Kernel auf (insbesondere bei spontanen Neustarts und nicht-fortsetzbaren KDL Sitzungen), kann es daher passieren dass es die letzten Ausgaben nicht mehr ins Syslog schaffen.</p>
 <p>Durch die Option <span class="menu">Enable debug syslog</span> im <span class="menu">Debug menu</span> des Bootloaders wird das Syslog im Speicher etwas langlebiger. Das ist standardmäßig aktiviert. "Etwas langlebiger" bedeutet, dass es einen Reset überlebt und direkt danach noch im Bootloader verfübar ist. Bootet man allerdings ein Betriebssystem (zumindest bei Haiku, wahrscheinlich aber bei allen), werden diese Informationen zerstört. Man muss beim Neustart also unbedingt das Bootloader Menü mittels gedrückter <span class="key">SHIFT</span> Taste aufrufen.<br />
 Dort sollte man im <span class="menu">Debug menu</span> jetzt die Einträge <span class="menu">Display syslog from previous session</span> und <span class="menu">Save syslog from previous session</span> sehen. Ersterer zeigt das Syslog direkt auf dem Bildschirm an, mit letzterem lässt es sich speichern. Momentan geht das nur auf FAT32 formatierten Medien. Möchte man dafür einen USB-Stick benutzen, den man allerdings erst zu spät reingesteckt hat und der deswegen nicht erkannt wurde, kann man den Rechner nochmals resetten und das Bootloader Menü erneut aufrufen. Es gilt aber immer noch: Bootet man ausversehen ein Betriebssystem, sind die Syslog Daten weg.</p>
 

docs/welcome/de/wifi.html

@@ -40,6 +40,8 @@
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 
@@ -118,7 +120,7 @@ Addtron AWA-100 PCI</p></li>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a name="auto-connect" rel="nofollow" id="auto-connect">Automatische Verbindung zu einem Funknetzwerk</a></h3>
-<p>Nach dem Hochfahren kann man sich auch automatisch mit einem durch seine SSID benannten Netzwerk verbinden. Dazu müssen Funknetzwerke und die entsprechenden Passwörter in der Datei <tt>/boot/common/settings/network/wireless_networks</tt> in folgendem Format abgelegt werden:</p>
+<p>Nach dem Hochfahren kann man sich auch automatisch mit einem durch seine SSID benannten Netzwerk verbinden. Dazu müssen Funknetzwerke und die entsprechenden Passwörter in der Datei <tt><acronym title="/boot/common/settings/network/wireless_networks">/boot/Allgemein/settings/network/wireless_networks</acronym></tt> in folgendem Format abgelegt werden:</p>
 <pre>network wifitopia {
    password DasPasswort
 }</pre>

docs/welcome/en/bugreports.html

@@ -38,6 +38,8 @@
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 </ul>
 <span>
     <a href="../welcome_en.html" class="uplink">Welcome</a>

docs/welcome/en/wifi.html

@@ -38,6 +38,8 @@
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 </ul>
 
 <span>

docs/welcome/es/bugreports.html

@@ -39,6 +39,8 @@
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/es/wifi.html

@@ -39,6 +39,8 @@
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 

docs/welcome/fi/bugreports.html

@@ -0,0 +1,171 @@
+<?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-2010, Haiku. All rights reserved.
+ * Distributed under the terms of the MIT License.
+ *
+ * Authors:
+ * 		Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
+ *		http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
+ *		Humdinger <[email protected]>
+ *
+-->
+	<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/fi.png" alt="" /> Suomi</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="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</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="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</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="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
+<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
+<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
+</ul>
+<span>
+    <a href="../welcome_fi.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>
+
+<table class="index" id="index" summary="index">
+<tr class="heading"><td>Reporting bugs</td></tr>
+<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
+                <a href="#report">Creating a bug report</a><br />
+                <a href="#app">Application bugs</a><br />
+                  <a href="#server">Server bugs</a><br />
+                  <a href="#kernel">Kernel bugs</a><br />
+                  <a href="#kdl">Kernel Debugging Land - KDL</a><br />
+                  <a href="#syslog">Syslog</a><br />
+                  <a href="#onscreen">On screen debug output</a><br />
+                  <a href="#hardware">Hardware/Driver bugs</a><br />
+                  <a href="#next">What's next?</a></td></tr>
+</table>
+
+<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><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="account" name="accout">Getting a Trac account</a></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><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="report" name="report">Creating a bug report</a></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>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  <a href="http://haiku-files.org/">available</a>.</p></li>
+	<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 <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</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 take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
+</ul>
+	
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="app" name="app">Application bugs</a></h2>
+<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
+
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="server" name="server">Server bugs</a></h2>
+<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
+Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
+
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="kernel" name="kernel">Kernel bugs</a></h2>
+<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
+<ul>
+<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
+<li><p>The system reboots spontaneously.</p></li>
+<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <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). Wait at least a minute to see, if anything happens.</p></li>
+<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
+<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
+</ul>
+<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
+
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
+<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
+Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
+<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
+<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
+<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
+<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
+<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
+</table>
+<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
+<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
+
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="syslog" name="syslog">Syslog</a></h3>
+<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
+The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/common/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
+<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
+In the boot loader's <span class="menu">Debug menu</span> you should now find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.</p>
+
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="onscreen" name="onscreen">On screen debug output</a></h3>
+<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
+This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
+Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
+One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/fi/bootloader.html">Boot Loader</a>.</p>
+
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
+<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
+
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
+<tr><td>- <span class="cli">listdev</span></td><td> </td><td>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>.</td></tr>
+<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
+<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>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.</td></tr>
+<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
+<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
+<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
+</table>
+
+<p>The first four commands are entered 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>
+
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="next" name="next">What's next?</a></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_fi.html" class="uplink">Welcome</a>
+</span></div>
+</div>
+
+</body>
+</html>

docs/welcome/fi/wifi.html

@@ -0,0 +1,159 @@
+<?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-2011, 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@gmail.com>
+ *
+-->
+	<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/fi.png" alt="" /> Suomi</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="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</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="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</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="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
+<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
+<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
+</ul>
+
+<span>
+   <a href="../welcome_fi.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>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
+<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
+2200BG<br />
+2225BG<br />
+2915ABG
+</p></li>
+<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
+<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 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>ralink2860 supporting Ralink RT2860</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="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
+<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
+<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
+<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
+<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
+<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
+<h4>Listing wireless networks:</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
+<h4>Joining unsecured wireless network:</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
+<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
+<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
+<h4>Leaving a wireless network:</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
+<h3>
+<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
+<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
+<pre>network wifitopia {
+   password mypassword
+}</pre>
+<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
+<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>ifconfig</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><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></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 iprowifi2200/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 iprowifi22xx 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_fi.html" class="uplink">Welcome</a>
+</span></div>
+</div>
+
+</body>
+</html>

docs/welcome/fr/bugreports.html

@@ -40,6 +40,8 @@
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/fr/wifi.html

@@ -40,6 +40,8 @@
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 

docs/welcome/it/bugreports.html

@@ -37,6 +37,8 @@
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/it/wifi.html

@@ -39,6 +39,8 @@
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 
@@ -68,14 +70,14 @@ Aironet PCI4800<br />
 <li><p><i>broadcom43xx</i>, supporta i chipset<br />
 BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 e BCM4318
 </p></li>
-<li><p><i>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
-<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
+<li><p><i>iprowifi2100</i>, supporta i chip Intel Pro Wireless 2100</p></li>
+<li><p><i>iprowifi2200</i>, supporta i chip Intel Pro Wireless<br />
 2200BG<br />
 2225BG<br />
 2915ABG
 </p></li>
-<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
-<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 4965 chips</p></li>
+<li><p><i>iprowifi3945</i>, supporta i chip Intel Pro Wireless 3945</p></li>
+<li><p><i>iprowifi4965</i>, supporta i chip Intel Pro Wireless 4965</p></li>
 <li><p><i>marvell88w8335</i>, supporta<br />
 Marvell Libertas 88W8310<br />
 Marvell Libertas 88W8335
@@ -87,7 +89,7 @@ RT2561S<br />
 RT2561<br />
 RT2661
 </p></li>
-<li><p>ralink2860 supporting Ralink RT2860</p></li>
+<li><p>ralink2860, supporta i chip Ralink RT2860</p></li>
 <li><p><i>wavelanwifi</i>, supporta almeno<br />
 3Com Airconnect<br />
 GLPRISM2 WaveLAN<br />
@@ -103,13 +105,13 @@ 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="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
+<a name="connect" rel="nofollow" id="connect">Connettersi a un network wireless</a></h3>
 <p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
 <p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
 <pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
 <p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
 <p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
-<h4>Listing wireless networks:</h4>
+<h4>Mostrare una lista dei network wireless:</h4>
 <pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
 <h4>Joining unsecured wireless network:</h4>
 <pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
@@ -121,13 +123,13 @@ Addtron AWA-100 PCI
 <pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
+<a name="auto-connect" rel="nofollow" id="auto-connect">Connettersi automaticamente a un network wireless</a></h3>
 <p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
 <pre>network wifitopia {
    password mypassword
 }</pre>
 <p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
-<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>Note sul 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>
@@ -140,7 +142,7 @@ Addtron AWA-100 PCI
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="indice" /></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 iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, you need to run</p>
+<p>Per installare il firmware per le schede ipw2100, Intel iprowifi2200/2225/2915, Broadcom 43xx &amp; Marvell 88W8335, dovete far partire lo script</p>
 <pre class="terminal">install-wifi-firmwares.sh
 </pre>
 <p>The Intel ipw2100 and iprowifi22xx 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>

docs/welcome/jp/bugreports.html

@@ -40,6 +40,8 @@
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/jp/wifi.html

@@ -41,6 +41,8 @@
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 

docs/welcome/pt_PT/bugreports.html

@@ -37,6 +37,8 @@
 <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="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/pt_PT/wifi.html

@@ -37,6 +37,8 @@
 <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="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 

docs/welcome/ru/bugreports.html

@@ -41,6 +41,8 @@
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
@@ -135,10 +137,10 @@ In the boot loader's <span class="menu">Debug menu</span> you should now find th
 
 <h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="onscreen" name="onscreen">Вывод отладочной информации на экран</a></h3>
-<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
-This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
-Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
-One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/ru/bootloader.html">Boot Loader</a>.</p>
+<p><b>Функция вывода отладочной информации на экран полезна для отладки только специфичных проблем, она также имеет известные проблемы с таймингами. Используйте ее только если это очень необходимо.</b><br />
+Ее использование имеет смысл только когда Haiku не загружается на вашем компьютереи функция <span class="menu">Debug syslog option</span> по какой-то причине не работает. Перед появлением загрузочного экрана зажмите  <span class="key">SHIFT</span> для входа в меню загрузчика. Выберите <span class="menu">Select safe mode options</span>. Почти в самом низу будет опция, <span class="menu">[ ] Enable on screen debug output</span>. (Имейте в виду, что можно включить остальные опции, чтобы Haiku загрузилась. Если Haiku будет загружаться только при включении одной или более опций, не забудьте указать какие именно.)<br />
+И наконец выбарите <span class="menu">Return to main menu</span>, а затем then <span class="menu">Continue booting</span>.<br />
+Одна страница текста или более появятся на экране, только последние несколько строк нужно включать в ваш багрепорт. Дополнительная информация имеется в статье <a href="../../../userguide/ru/bootloader.html">Загрузчик</a>.</p>
 
 <h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="hardware" name="hardware">Аппаратные ошибки/Ошибки в драйверах</a></h2>

docs/welcome/ru/wifi.html

@@ -40,6 +40,8 @@
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 

docs/welcome/sk/bugreports.html

@@ -0,0 +1,171 @@
+<?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-2010, Haiku. All rights reserved.
+ * Distributed under the terms of the MIT License.
+ *
+ * Authors:
+ * 		Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
+ *		http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
+ *		Humdinger <humdingerb@gmail.com>
+ *
+-->
+	<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/sk.png" alt="" /> Slovenčina</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="../it/bugreports.html"><img src="../images/flags/it.png" alt="" />Italiano</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="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</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="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
+<li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
+</ul>
+<span>
+    <a href="../welcome_sk.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>
+
+<table class="index" id="index" summary="index">
+<tr class="heading"><td>Reporting bugs</td></tr>
+<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
+                <a href="#report">Creating a bug report</a><br />
+                <a href="#app">Application bugs</a><br />
+                  <a href="#server">Server bugs</a><br />
+                  <a href="#kernel">Kernel bugs</a><br />
+                  <a href="#kdl">Kernel Debugging Land - KDL</a><br />
+                  <a href="#syslog">Syslog</a><br />
+                  <a href="#onscreen">On screen debug output</a><br />
+                  <a href="#hardware">Hardware/Driver bugs</a><br />
+                  <a href="#next">What's next?</a></td></tr>
+</table>
+
+<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><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="account" name="accout">Getting a Trac account</a></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><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="report" name="report">Creating a bug report</a></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>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  <a href="http://haiku-files.org/">available</a>.</p></li>
+	<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 <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</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 take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
+</ul>
+	
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="app" name="app">Application bugs</a></h2>
+<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
+
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="server" name="server">Server bugs</a></h2>
+<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
+Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
+
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="kernel" name="kernel">Kernel bugs</a></h2>
+<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
+<ul>
+<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
+<li><p>The system reboots spontaneously.</p></li>
+<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <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). Wait at least a minute to see, if anything happens.</p></li>
+<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
+<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
+</ul>
+<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
+
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
+<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
+Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
+<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
+<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
+<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
+<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
+<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
+</table>
+<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
+<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
+
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="syslog" name="syslog">Syslog</a></h3>
+<p><b>This is the preferred method for gaining information from a non-booting system.</b><br />
+The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file <span class="path">/boot/common/var/log/syslog</span>. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).</p>
+<p>The option <span class="menu">Enable debug syslog</span> in the boot loader's <span class="menu">Debug menu</span> makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down <span class="key">SHIFT</span> while booting.<br />
+In the boot loader's <span class="menu">Debug menu</span> you should now find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.</p>
+
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="onscreen" name="onscreen">On screen debug output</a></h3>
+<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
+This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
+Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
+One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/sk/bootloader.html">Boot Loader</a>.</p>
+
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
+<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
+
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
+<tr><td>- <span class="cli">listdev</span></td><td> </td><td>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>.</td></tr>
+<tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</td></tr>
+<tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>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.</td></tr>
+<tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Lists all used drivers.</td></tr>
+<tr><td>- <span class="cli">ints</span></td><td> </td><td>Only available within <i>Kernel Debugging Land</i> (see above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</td></tr>
+<tr><td colspan="3">- On screen debug output (a safe mode boot time option).</td></tr>
+</table>
+
+<p>The first four commands are entered 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>
+
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="next" name="next">What's next?</a></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_sk.html" class="uplink">Welcome</a>
+</span></div>
+</div>
+
+</body>
+</html>

docs/welcome/sk/wifi.html

@@ -0,0 +1,159 @@
+<?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-2011, 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@gmail.com>
+ *
+-->
+	<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/sk.png" alt="" /> Slovenčina</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="../it/wifi.html"><img src="../images/flags/it.png" alt="" />Italiano</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="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svenska</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="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
+<li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
+</ul>
+
+<span>
+   <a href="../welcome_sk.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>ipw2100</i> supporting Intel Pro Wireless 2100 chips</p></li>
+<li><p><i>iprowifi2200</i> supporting Intel Pro Wireless<br />
+2200BG<br />
+2225BG<br />
+2915ABG
+</p></li>
+<li><p><i>iprowifi3945</i> supporting Intel Pro Wireless 3945 chips</p></li>
+<li><p><i>iprowifi4965</i> supporting Intel Pro Wireless 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>ralink2860 supporting Ralink RT2860</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="connect" rel="nofollow" id="connect">Connecting to a wireless network</a></h3>
+<p>Besides of course unencrypted networks, Haiku has preliminary support for accessing wireless networks via <a href="#wep-notes" rel="nofollow">WEP encryption keys</a>. WEP is an early encryption method, although not the most secure.</p>
+<p>You can list available networks, join and leave them with the command <span class="cli">ifconfig</span> from Terminal:</p>
+<pre class="terminal">ifconfig [wifi_device_path] [list|join|leave] (key)</pre>
+<p>You can find your <tt>wifi_device_path</tt> in the <span class="app">Network</span> preferences applet, or by executing <span class="cli">ifconfig -a</span>.</p>
+<p>Below are a few examples of connecting to a wireless network named <i>wifitopia</i>. For these examples we are assuming your wifi network card is <tt>/dev/net/iprowifi3945/0</tt>.</p>
+<h4>Listing wireless networks:</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 list</pre>
+<h4>Joining unsecured wireless network:</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia</pre>
+<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (ascii password)</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia mypassword</pre>
+<h4>Joining <a href="#wep-notes">WEP secured</a> wireless network: (64-bit hex password)</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 join wifitopia 0x4010FABEEF</pre>
+<h4>Leaving a wireless network:</h4>
+<pre class="terminal">ifconfig /dev/net/iprowifi3945/0 leave wifitopia</pre>
+<h3>
+<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
+<a name="auto-connect" rel="nofollow" id="auto-connect">Automatically connecting to a wireless network</a></h3>
+<p>To make your system connect to a given SSID at each boot automatically, you can specify your wireless networks and passwords in <tt>/boot/common/settings/network/wireless_networks</tt> with the following format:</p>
+<pre>network wifitopia {
+   password mypassword
+}</pre>
+<p>If you don't create this configuration file, the system will connect to the first unencrypted network it finds.</p>
+<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>ifconfig</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><p>At the moment there is no WPA encryption available in Haiku, though there have been <a target="blank" href="http://haiku-os.org/blog/axeld/2010-10-13_wpa_encryption_progress">some efforts</a> bringing it significantly closer.</p></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 iprowifi2200/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 iprowifi22xx 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_sk.html" class="uplink">Welcome</a>
+</span></div>
+</div>
+
+</body>
+</html>

docs/welcome/sv_SE/bugreports.html

@@ -39,6 +39,8 @@
 <li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/sv_SE/wifi.html

@@ -39,6 +39,8 @@
 <li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 

docs/welcome/uk/bugreports.html

@@ -37,6 +37,8 @@
 <li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
 <li><a href="../zh_CN/bugreports.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/uk/wifi.html

@@ -37,6 +37,8 @@
 <li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
 <li><a href="../zh_CN/wifi.html"><img src="../images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 

docs/welcome/welcome_de.html

@@ -40,6 +40,8 @@
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
@@ -78,7 +80,7 @@
 <h2>
 <a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="software" name="software">Software installieren</a></h2>
-<p>Da Haiku sowohl binärkompatibel als auch code-kompatibel mit dem BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku (für manche Programme muss das Optional Package "beoscompatibility" installiert werden, siehe unten).  Nach dem Herunterladen eines Programm-Pakets muss es lediglich nach <span class="path">/boot/apps/</span> entpackt (ein Doppelklick öffnet den <span class="app">Expander</span>) und von dort gestartet werden.</p>
+<p>Da Haiku sowohl binärkompatibel als auch code-kompatibel mit dem BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku (für manche Programme muss das Optional Package "beoscompatibility" installiert werden, siehe unten).  Nach dem Herunterladen eines Programm-Pakets muss es lediglich nach <span class="path"><acronym title="/boot/apps/">/boot/Anwendungen</acronym></span> entpackt (ein Doppelklick öffnet den <span class="app"><acronym title="Expander">Entpacker</acronym></span>) und von dort gestartet werden.</p>
 
 <p>Große Software-Verzeichnisse sind:</p>
 <ul>

docs/welcome/welcome_en.html

@@ -37,6 +37,8 @@
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 </ul>
 <span>
  

docs/welcome/welcome_es.html

@@ -39,6 +39,8 @@
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/welcome_fi.html

@@ -0,0 +1,134 @@
+<?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-2010, Haiku. All rights reserved.
+ * Distributed under the terms of the MIT License.
+ *
+ * Authors:
+ *		Humdinger <humdingerb@gmail.com>
+ *		Stephan Aßmus <superstippi@gmx.de> 
+ *
+-->
+	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+	<meta name="robots" content="all" />
+	<title>Welcome to Haiku!</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/fi.png" alt="" /> Suomi</li>
+<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
+<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
+<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
+<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
+<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
+<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
+<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
+<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
+<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
+<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
+<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
+</ul>
+<span>
+ 
+</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>
+<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
+<p>Thank you very much for checking out Haiku! This is our third public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
+<p>We have been working hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
+<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
+
+<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
+<ul>
+	<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
+	<li><a href="fi/bugreports.html">Tips for a helpful bug report</a></li>
+</ul>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="system" name="system">Getting to know the system</a></h2>
+<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
+<ul>
+	<li><a href="../userguide/fi/contents.html">Haiku User Guide</a></li>
+	<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
+</ul>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="software" name="software">Installing more software</a></h2>
+<p>Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
+
+<p>Popular software repositories are:</p>
+<ul>
+	<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
+	<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
+	<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
+	<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - hosts native BeOS and Haiku open source software projects</li>
+</ul>
+
+<p>There are also so-called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. Instead, a utility script is provided, <tt>installoptionalpackage</tt>. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.<br />
+You'll have to run a command in Terminal: <tt>installoptionalpackage -h</tt> explains its usage.</p>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="software" name="wifi">Wifi in Haiku</a></h2>
+<p>Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our <a href="fi/wifi.html">Wifi</a> page (also <a href="http://www.haiku-os.org/guides/wifi">online</a>).</p> 
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="api" name="api">Getting to know the API</a></h2>
+<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.</p>
+
+<p>There are additional resources that should help you getting started:</p>
+<ul>
+	<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
+	<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Browser</a></li>
+	<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
+	<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
+</ul>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="contact" name="contact">Getting in contact</a></h2>
+<p>Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
+<ul>
+	<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
+	<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
+	<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
+	<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
+	<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
+	<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
+</ul>
+
+</div>
+</div>
+
+<div class="nav">
+<div class="inner"><span>
+ 
+</span></div>
+</div>
+
+</body>
+</html>

docs/welcome/welcome_fr.html

@@ -40,6 +40,8 @@
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/welcome_it.html

@@ -38,6 +38,8 @@
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
@@ -47,11 +49,11 @@
 
 <div id="content">
 <div>
-<div class="box-info">La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.</div>
 
 <h2>
 <a id="welcome" name="welcome">Benvenuto in Haiku!</a></h2>
-<p>Thank you very much for checking out Haiku! This is our third public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
+<p>Grazie per aver deciso di provare Haiku! Questa è la nostra terza release al pubblico. Speriamo di attrarre nuovi sviluppatori al nostro progetto e dare agli utenti futuri una possibilità di provare Haiku. Ci rendiamo conto che quest'<i>alpha release</i> non è ancora completamente all'altezza degli obiettivi che ci siamo fissati e non offre tutte le funzionalità e un'esperienza piacevole e bilanciata per l'utente finale pianificate per la versione R1 definitiva. Comunque, speriamo che questa release ti faccia scoprire il grande potenziale di Haiku e ti faccia condividere il nostro entusiasmo.
+</p>
 
 <h2>
 <a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>

docs/welcome/welcome_jp.html

@@ -40,6 +40,8 @@
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/welcome_pt_PT.html

@@ -36,6 +36,8 @@
 <li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/welcome_ru.html

@@ -41,6 +41,8 @@
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/welcome_sk.html

@@ -0,0 +1,134 @@
+<?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-2010, Haiku. All rights reserved.
+ * Distributed under the terms of the MIT License.
+ *
+ * Authors:
+ *		Humdinger <humdingerb@gmail.com>
+ *		Stephan Aßmus <superstippi@gmx.de> 
+ *
+-->
+	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+	<meta name="robots" content="all" />
+	<title>Welcome to Haiku!</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/sk.png" alt="" /> Slovenčina</li>
+<li><a href="welcome_fr.html"><img src="images/flags/fr.png" alt="" />Français</a></li>
+<li><a href="welcome_de.html"><img src="images/flags/de.png" alt="" />Deutsch</a></li>
+<li><a href="welcome_it.html"><img src="images/flags/it.png" alt="" />Italiano</a></li>
+<li><a href="welcome_ru.html"><img src="images/flags/ru.png" alt="" />Русский</a></li>
+<li><a href="welcome_es.html"><img src="images/flags/es.png" alt="" />Español</a></li>
+<li><a href="welcome_sv_SE.html"><img src="images/flags/sv_SE.png" alt="" />Svenska</a></li>
+<li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
+<li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
+<li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
+<li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
+</ul>
+<span>
+ 
+</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>
+<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
+<p>Thank you very much for checking out Haiku! This is our third public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
+<p>We have been working hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
+<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
+
+<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
+<ul>
+	<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
+	<li><a href="sk/bugreports.html">Tips for a helpful bug report</a></li>
+</ul>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="system" name="system">Getting to know the system</a></h2>
+<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
+<ul>
+	<li><a href="../userguide/sk/contents.html">Haiku User Guide</a></li>
+	<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
+</ul>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="software" name="software">Installing more software</a></h2>
+<p>Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
+
+<p>Popular software repositories are:</p>
+<ul>
+	<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
+	<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
+	<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - maintains patches for ported software</li>
+	<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - hosts native BeOS and Haiku open source software projects</li>
+</ul>
+
+<p>There are also so-called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. Instead, a utility script is provided, <tt>installoptionalpackage</tt>. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.<br />
+You'll have to run a command in Terminal: <tt>installoptionalpackage -h</tt> explains its usage.</p>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="software" name="wifi">Wifi in Haiku</a></h2>
+<p>Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our <a href="sk/wifi.html">Wifi</a> page (also <a href="http://www.haiku-os.org/guides/wifi">online</a>).</p> 
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="api" name="api">Getting to know the API</a></h2>
+<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.</p>
+
+<p>There are additional resources that should help you getting started:</p>
+<ul>
+	<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
+	<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Browser</a></li>
+	<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
+	<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
+</ul>
+
+<h2>
+<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
+<a id="contact" name="contact">Getting in contact</a></h2>
+<p>Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
+<ul>
+	<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
+	<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
+	<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
+	<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
+	<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
+	<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
+</ul>
+
+</div>
+</div>
+
+<div class="nav">
+<div class="inner"><span>
+ 
+</span></div>
+</div>
+
+</body>
+</html>

docs/welcome/welcome_sv_SE.html

@@ -38,6 +38,8 @@
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/welcome_uk.html

@@ -38,6 +38,8 @@
 <li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
 <li><a href="welcome_zh_CN.html"><img src="images/flags/zh_CN.png" alt="" /> 中文 ［中文］</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
@@ -47,17 +49,16 @@
 
 <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>
 <a id="welcome" name="welcome">Вітаємо в Haiku!</a></h2>
-<p>Thank you very much for checking out Haiku! This is our third public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
+<p>Дякуємо за інтерес, який Ви проявляєте до Haiku! Це наш третій публічний реліз, ми маємо надію привернути увагу нових розробників і дати можливість майбутнім користувачам побачити Haiku в дії. Зрозуміло, що цей <i>альфа реліз</i> далеко не повністю відповідає цілям, які поставлені і не надає всіх функцій, які ми збирались надати кінцевому користувачеві, запланувавши їх для фінальної версії  R1. Однак, ми маємо надію, що він дозволить Вам помітити значний потенціал Haiku і Ви знайдете хвильку для її вивчення.</p>
 
 <h2>
 <a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="bugreport" name="bugreport">Остерігайтесь помилок</a></h2>
 <p>Ми провели значну роботу по виявленню і усуненню помилок ("багів") , однак це лише альфа-реліз і в ньому можлива присутність деякої кількості невиявлених помилок.</p>
-<div class="box-warning">Ми не рекомендуємо використовувати альфа версії у якості основної операційної системи. В наші дані з великою ймовірністю можуть бути   внесені небажані зміни, вони можуть бути спотворені або навіть знищені .</div>
+<div class="box-warning">Ми не рекомендуємо використовувати альфа версій у якості основної опереаційної системи. У Ваші дані з великою ймовірністю можуть бути внесені небажані зміни, вони можуть бути спотворені або навіть знищені.</div>
 
 <p>Одна з основних причин випуску альфа-версії є бажання привернути більше користувачів для тестування і виявлення помилок, а також отримання від них пропозицій для подальшого покращення Haiku. Прохання залишати звіти про найдені помилки і пропозиції з покращення ОС  в нашій системі відслідкування помилок (bug tracker) , але тільки після попереднього пошуку, для уникнення появи дублікатів.</p>
 <ul>

docs/welcome/welcome_zh_CN.html

@@ -38,6 +38,8 @@
 <li><a href="welcome_jp.html"><img src="images/flags/jp.png" alt="" />日本語</a></li>
 <li><a href="welcome_uk.html"><img src="images/flags/uk.png" alt="" />Українська</a></li>
 <li><a href="welcome_pt_PT.html"><img src="images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="welcome_fi.html"><img src="images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="welcome_sk.html"><img src="images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="welcome_en.html"><img src="images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/zh_CN/bugreports.html

@@ -40,6 +40,8 @@
 <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="../pt_PT/bugreports.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/bugreports.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/bugreports.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>

docs/welcome/zh_CN/wifi.html

@@ -40,6 +40,8 @@
 <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="../pt_PT/wifi.html"><img src="../images/flags/pt_PT.png" alt="" />Português</a></li>
+<li><a href="../fi/wifi.html"><img src="../images/flags/fi.png" alt="" />Suomi</a></li>
+<li><a href="../sk/wifi.html"><img src="../images/flags/sk.png" alt="" />Slovenčina</a></li>
 <li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>