Update of user guide and welcome page and their translations.

git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@38032 a95241bf-73f2-0310-859d-f6bbb57e9c96
2010-08-11 17:56:45 +00:00
parent 5091a866ec
commit 834e58f9b7
91 changed files with 1541 additions and 837 deletions
@@ -70,7 +70,7 @@ Das jeweils aktivierte, durch ein X markierte der beiden kann mit <span class="k
 <table summary="options" border="0" cellpadding="2" cellspacing="0">
 <tr><td><span class="menu">Save Image</span></td><td><span class="key">ALT</span> <span class="key">S</span></td><td> </td><td>Die aktuelle Darstellung wird als "Resource"-Datei gespeichert.</td></tr>
 <tr><td><span class="menu">Copy Image</span></td><td><span class="key">ALT</span> <span class="key">C</span></td><td> </td><td>Die aktuelle Darstellung wird in die Ablage kopiert.</td></tr>
-<tr><td><span class="menu">Hide/Show Info</span></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Die Informationen im Programmfenster oben und unten werden ein/ausgeblendet.</td></tr>
+<tr><td><span class="menu">Hide/Show Info</span></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Die Informationen im Programmfenster oben und unten werden ein/ausgeblendet.</td></tr>
 <tr><td><span class="menu">Add a Crosshair</span></td><td><span class="key">ALT</span> <span class="key">H</span></td><td> </td><td>Fügt ein von maximal zwei blauen Fadenkreuzen hinzu.</td></tr>
 <tr><td><span class="menu">Remove a Crosshair</span></td><td><span class="key">ALT</span> <span class="key">SHIFT</span> <span class="key">H</span></td><td> </td><td>Entfernt das zuletzt hinzugefügte blaue Fadenkreuz.</td></tr>
 <tr><td><span class="menu">Hide/Show Grid</span></td><td><span class="key">ALT</span> <span class="key">G</span></td><td> </td><td>Hier kann das angezeigte Gitternetz ein/ausgeschaltet werden.</td></tr>
@@ -49,40 +49,38 @@
 <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><img src="../../images/apps-images/textsearch-icon_64.png" alt="textsearch-icon_64.png" width="64" height="64" />TextSearch</h2>
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
-<tr><td>Deskbar:</td><td style="width:15px;"></td><td><i>No entry, normally launched via Tracker Add-on</i></td></tr>
+<tr><td>Deskbar:</td><td style="width:15px;"></td><td><i>Kein Eintrag; wird normalerweise über das Tracker Add-on gestartet.</i></td></tr>
 <tr><td>Ort:</td><td></td><td><span class="path">/boot/system/apps/TextSearch</span></td></tr>
 <tr><td>Einstellungen:</td><td></td><td><span class="path">~/config/settings/TextSearch</span></td></tr>
 </table>
 <p><br /></p>
-<p>TextSearch looks for a string in text files. Typically it is invoked from <a href="../tracker-add-ons.html">Tracker's Add-on</a> context menu on the selection of files or folders you want to search.</p>
+<p>TextSearch sucht nach Zeichenfolgen in Textdateien. Normalerweise wählt man dazu die Dateien oder Ordner aus, die durchsucht werden sollen und wählt TextSearch aus Trackers <a href="../tracker-add-ons.html">Add-on</a> Kontextmenü.</p>
 <img src="../images/apps-images/textsearch.png" alt="textsearch.png" />
-<p>You enter a search string in the text box on top and hit <span class="key">RETURN</span> or click <span class="button">Search</span> to start. If <span class="menu">Show lines</span> is checked, the hits are automatically expanded to show the lines of the file containing the search string.</p>
+<p>Im Textfeld oben wird der Suchbegriff eingegeben und die Suche per <span class="key">RETURN</span> oder Klick auf <span class="button">Search</span> gestartet. Ist die <span class="menu">Show lines</span> Option aktiviert, werden die Suchergebnisse automatisch aufgeklappt und zeigen dann die Zeilennummern der Fundstellen in den Dateien, die den Suchbegriff enthalten.</p>
-<p>Only a few words on some of the otherwise self-explaining menu items:</p>
+<p>Nur ein paar kurze Erläuterungen zu den ansonsten sich selbst erklärenden Menüpunkten:</p>
 <table summary="menus" border="0" cellpadding="2" cellspacing="0">
-<tr><td colspan="5"><h3>File menu</h3></td></tr>
+<tr><td colspan="5"><h3>File Menü</h3></td></tr>
-<tr><td class="onelinetop"><span class="menu">New window</span></td><td></td><td><span class="key">ALT</span> <span class="key">N</span></td><td> </td><td>Opens a new window where you can enter another string and search through the same files/folders.
+<tr><td class="onelinetop"><span class="menu">New window</span></td><td></td><td><span class="key">ALT</span> <span class="key">N</span></td><td> </td><td>Öffnet ein neues Fenster, um dieselben Dateien/Ordner nach einem neuen Begriff zu durchsuchen.</td></tr>
-</td></tr>
+<tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Zum Ändern der Dateien oder Ordner, die durchsucht werden sollen.</td></tr>
-<tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
+<tr><td colspan="5"><h3>Action Menü</h3></td></tr>
-<tr><td colspan="5"><h3>Action menu</h3></td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Entfernt alle Suchergebnisse aus der Liste, die nicht  ausgewählt sind.</td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Öffnet die ausgewählten Dateien mit ihrer bevorzugten Anwendung (wie bei einem Doppelklick). Falls es sich um einen Texteditor handelt, der das unterstützt (wie Pe), lässt sich auch genau zu der Zeile der Fundstelle springen.</td></tr>
-<tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
+<tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Öffnet die Speicherorte der gerade ausgewählten Dateien im Tracker.</td></tr>
-<tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Kopiert die momentane Auswahl in die Ablage.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td colspan="5"><h3>Settings Menü</h3></td></tr>
-<tr><td colspan="5"><h3>Settings menu</h3></td></tr>
+<tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>Nützlich wenn man sich in einer Unix-Umgebung bewegt, in der Verwaltungsdateien oft in "<tt>.Ordner</tt>" versteckt werden. Sourcecode Versionierungssysteme wie SVN und CVS sind Beispiele für Anwendungen, die das so machen und auch unter Haiku weit verbreitet sind.</td></tr>
-<tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch benutzt das Konsolenprogramm <span class="cli">grep</span>. Dazu müssen spezielle Zeichen wie <tt>'"*\$?!</tt> und Leerzeichen mit einem <tt>\</tt> "escaped" werden. Deaktiviert man diese Option, heißt das, dass man das von Hand machen muss, im Gegenzug erhält man allerdings die mächtigen Möglichkeiten von <a href="http://de.wikipedia.org/wiki/Regul%C3%A4re_Ausdr%C3%BCcke" class="external free" title="Reguläre Ausdrücke" rel="nofollow">Regulären Ausdrücken</a>.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch ist momentan nur zur Suche von Begriffen in reinen Textdateien sinnvoll zu gebrauchen. Deaktiviert man diese Option, werden alle Arten von Dateien durchsucht.</td></tr>
-<tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
+<tr><td colspan="5"><h3>History Menü</h3></td></tr>
-<tr><td colspan="5"><h3>History menu</h3></td></tr>
+<tr><td colspan="4"></td><td>Enthält kürzlich benutzte Suchbegriffe.</td></tr>
-<tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
+<tr><td colspan="5"><h3>Encoding Menü</h3></td></tr>
-<tr><td colspan="5"><h3>Encoding menu</h3></td></tr>
+<tr><td colspan="4"></td><td>Erlaubt bei Bedarf verschiedene Zeichencodierungen.</td></tr>
 <tr><td colspan="4"></td><td>Lets you choose different character encodings if needed.</td></tr>
 </table>
 </div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>User Guide</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,8 +41,8 @@
 <li><a href="../en/gui.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="filesystem-layout.html">Dateisystem Layout</a> 
+ «  <a href="filesystem-layout.html">Filesystem layout</a> 
-::  <a href="contents.html" class="uplink">Inhalt</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="workspaces.html">Workspaces</a>  »
 </span></div>
 </div>
@@ -113,8 +113,8 @@ Ein Rechtsklick auf ein Replikanten-Symbol öffnet ein Kontextmenü, um das <spa
 <div class="nav">
 <div class="inner"><span>
- «  <a href="filesystem-layout.html">Dateisystem Layout</a> 
+ «  <a href="filesystem-layout.html">Filesystem layout</a> 
-::  <a href="contents.html" class="uplink">Inhalt</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="workspaces.html">Workspaces</a>  »
 </span></div>
 </div>
@@ -24,7 +24,7 @@
 <body>
 <div id="banner">
-<div><span>User Guide</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -44,7 +44,7 @@
 </ul>
 <span>
 «  <a href="tracker-add-ons.html">Tracker Add-Ons</a> 
-::  <a href="contents.html" class="uplink">Inhalt</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="deskbar.html">Deskbar</a>  »
 </span></div>
 </div>
@@ -133,7 +133,7 @@ Die eingegebenen Zeichen erscheinen unten links, wo ansonsten die Anzahl der Obj
 <div class="nav">
 <div class="inner"><span>
 «  <a href="tracker-add-ons.html">Tracker Add-Ons</a> 
-::  <a href="contents.html" class="uplink">Inhalt</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="deskbar.html">Deskbar</a>  »
 </span></div>
 </div>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>User Guide</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -43,7 +43,7 @@
 </ul>
 <span>
 «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">Einstellungen</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -153,7 +153,7 @@ Im ersten Textfeld gibt man die zu prüfende Kopfzeile an. Diese Werte möglich:
 	<tr><td><span class="menu">Spam/Genuine Estimate</span></td><td> </td>
 		<td>der errechnete Wert des Spam-Filters für diese Mail; dieser Wert wird in wissenschaftlicher Schreibweise notiert, so steht zum Beispiel 1.065e-12 für 1,065/(10^12), also für "1,065 dividiert durch 10 hoch 12" - was ausgeschrieben 0,000000000001065 ergibt</td></tr>
 </table>
-<p>Das zweite Textfeld ist für das Suchmuster. Hier können "reguläre Ausdrücke" - sogenannte <a href="http://de.wikipedia.org/wiki/Regul%C3%A4rer_Ausdruck" class="external free" title="Wikipedia: Reguläre Ausdrücke" rel="nofollow">Reguläre Ausdrücke (reg_ex)</a> - verwendet werden. Damit erreicht man zwar eine sehr hohe Flexibilität bei den Suchmustern, unglücklicherweise sind reguläre Ausdrücke aber nicht leicht anzuwenden. Ein wenig Einarbeitung ist es aber wert und einfache reg_ex sind auch nicht <i>zu</i> schwer.</p>
+<p>Das zweite Textfeld ist für das Suchmuster. Hier können "reguläre Ausdrücke" - sogenannte <a href="http://de.wikipedia.org/wiki/Regul%C3%A4rer_Ausdruck" class="external free" title="Wikipedia: Reguläre Ausdrücke" rel="nofollow">Reguläre Ausdrücke</a> - verwendet werden. Damit erreicht man zwar eine sehr hohe Flexibilität bei den Suchmustern, unglücklicherweise sind reguläre Ausdrücke aber nicht leicht anzuwenden. Ein wenig Einarbeitung ist es aber wert und einfache reg_ex sind auch nicht <i>zu</i> schwer.</p>
 <p>Über das Menü darunter lässt sich eine Aktion ausführen, wenn das Suchmuster erkannt wurde. So kann der Status der Mail verändert, oder die Mail an sich verschoben oder direkt gelöscht werden.</p>
 <h3>
@@ -182,7 +182,7 @@ Wenn man seine Netzwerkverbindung über eine Wählverbindung aufbaut, ist es rat
 <div class="nav">
 <div class="inner"><span>
 «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">Einstellungen</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>User Guide</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -43,7 +43,7 @@
 </ul>
 <span>
 «  <a href="index.html">Index</a> 
-::  <a href="contents.html" class="uplink">Inhalt</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
@@ -124,13 +124,13 @@ So lässt sich die Trefferzahl sehr gut einschränken.</p>
 <ul>
 <li><p>Die Suchformel lässt sich in eine E-Mail oder Forumbeitrag kopieren oder im IRC erwähnen, damit sie von anderen benutzt oder verbessert werden kann.</p></li>
 <li><p>Mit dieser Methode lassen sich Queries entspannt im <span class="menu">Attribute</span> Modus konstruieren. Anschließend wechselt man in den  <span class="menu">Formula</span> Modus, um die Formel der so erstellten Query im Terminal oder einem Skript zu nutzen.</p></li>
-<li><p>Eine Query lässt sich so fein anpassen, indem man zusätzliche Klammern setzt, in bestimmten Abschnitten auf Groß- und Kleinschreibung achtet oder einige logische Verknüpfungen verneint durch Ändern von "<tt>==</tt>" zu "<tt>!=</tt>" für ein NOT AND. Dazu benötigt man nur ein gewisses Basiswissen über <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">Reguläre  Ausdrücke</a> und ein klein wenig Programmier-Kenntnisse.</p></li>
+<li><p>Eine Query lässt sich so fein anpassen, indem man zusätzliche Klammern setzt, in bestimmten Abschnitten auf Groß- und Kleinschreibung achtet oder einige logische Verknüpfungen verneint durch Ändern von "<tt>==</tt>" zu "<tt>!=</tt>" für ein NOT AND. Dazu benötigt man nur ein gewisses Basiswissen über <a href="http://de.wikipedia.org/wiki/Regul%C3%A4re_Ausdr%C3%BCcke" class="external free" title="Wikipedia: Reguläre Ausdrücke">Reguläre Ausdrücke</a> und ein klein wenig Programmier-Kenntnisse.</p></li>
 </ul>
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="result-window" name="result-window">Das Ergebnisfenster</a></h2>
-<p>Hat man die Suche gestartet, wird das FInd-Fenster durch ein Ergebnisfenster ersetzt. Hier ein Beispiel einer Suche nach "server":</p>
+<p>Hat man die Suche gestartet, wird das Find-Fenster durch ein Ergebnisfenster ersetzt. Hier ein Beispiel einer Suche nach "server":</p>
 <img src="images/queries-images/result-window.png" alt="result-window.png" />
 <p>Außer ihrem grauen Hintergrund, unterscheidet Ergebnisfenster nichts von jedem anderen Trackerfenster. Einige Dinge gehören erwähnt:</p>
 <ul>
@@ -154,7 +154,7 @@ Mit dem Menüpunkt <span class="menu">Save Query as Template</span> (siehe (1) i
 <div class="nav">
 <div class="inner"><span>
 «  <a href="index.html">Index</a> 
-::  <a href="contents.html" class="uplink">Inhalt</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>User Guide</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -43,7 +43,7 @@
 </ul>
 <span>
 «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">Inhalt</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -126,7 +126,7 @@ Dieses "type-ahead" filtern wird in den <a href="#tracker-preferences.html">Trac
 <ul>
 <li><p><b>Resize Window</b> (<span class="key">ALT</span> <span class="key">Y</span>) - Ändert die Fenstergröße auf einen sinnvollen Wert.</p></li>
 <li><p><b>Clean Up</b> (<span class="key">ALT</span> <span class="key">K</span>) - Die Icons werden an einem unsichtbaren Raster ausgerichtet; bei zusätzlichem Drücken von <span class="key">SHIFT</span> ändert sich der Menüpunkt zu <span class="menu">Clean Up All</span> und die Icons werden zusätzlich noch alphabetisch sortiert.</p></li>
-<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Wählt Dateien anhand einer <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">Regular Expression</a> aus.</p></li>
+<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Wählt Dateien anhand einer <a href="http://de.wikipedia.org/wiki/Regul%C3%A4re_Ausdr%C3%BCcke" class="external free" title="Wikipedia: Regulärer Ausdruck">Regulärer Ausdruck</a> aus.</p></li>
 <li><p><b>Close</b> (<span class="key">ALT</span> <span class="key">W</span>) - Schließt das Tracker-Fenster; bei zusätzlichem Drücken von <span class="key">SHIFT</span>  ändert sich der Menüpunkt zu <span class="menu">Close All</span> und alle Tracker-Fenster in allen Workspaces werden geschlossen.</p></li>
 <li><p><b>Close All in Workspace</b> (<span class="key">ALT</span> <span class="key">Q</span>) - Schließt alle Tracker-Fenster im akutellen Workspace; hilfreich, wenn man die Taste <span class="key">OPT</span> nicht drückte, als man durch die Verzeichnisse navigierte und nun der gesamte Arbeitsplatz voll von Tracker-Fenstern ist.</p></li>
 </ul>
@@ -197,7 +197,7 @@ Dieses "type-ahead" filtern wird in den <a href="#tracker-preferences.html">Trac
 <div class="nav">
 <div class="inner"><span>
 «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">Inhalt</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -68,13 +68,13 @@
 </td></tr>
 <tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
 <tr><td colspan="5"><h3>Action menu</h3></td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries from the list that are not currently selected.</td></tr>
 <tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
 <tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
 <tr><td colspan="5"><h3>Settings menu</h3></td></tr>
 <tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line tool <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expressions" rel="nofollow">regular expressions</a>.</td></tr>
 <tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
 <tr><td colspan="5"><h3>History menu</h3></td></tr>
 <tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
@@ -150,7 +150,7 @@ With the first text field you specify which header to check against. These are a
 	<tr><td><span class="menu">Spam/Genuine Estimate</span></td><td> </td>
 		<td>this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065.</td></tr>
 </table>
-<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
+<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
 <p>With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.</p>
 <h3>
@@ -121,7 +121,7 @@ A good way to cut down the number of search results.</p>
 <ul>
 <li><p>You could copy and paste the string into an email, forum or IRC for others to use or debug.</p></li>
 <li><p>You can use this method to construct a query in <span class="menu">Attribute</span> mode and then switch to <span class="menu">Formula</span> mode, to comfortably generate a search string to use for a query in Terminal or a script.</p></li>
-<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
+<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
 </ul>
 <h2>
@@ -123,7 +123,7 @@ This type-ahead filtering is set in the <a href="#tracker-preferences.html">Trac
 <ul>
 <li><p><b>Resize Window</b> (<span class="key">ALT</span> <span class="key">Y</span>) - Resizes the window to its ideal size.</p></li>
 <li><p><b>Clean Up</b> (<span class="key">ALT</span> <span class="key">K</span>) - Aligns all icons to an invisible grid. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Clean Up All</span> which additionally sorts all icons alphabetically.</p></li>
-<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expression</a>.</p></li>
+<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expression</a>.</p></li>
 <li><p><b>Close</b> (<span class="key">ALT</span> <span class="key">W</span>) - Closes the window. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Close All</span> which closes every Tracker window.</p></li>
 <li><p><b>Close All in Workspace</b> (<span class="key">ALT</span> <span class="key">Q</span>) - Closes every Tracker window in the current workspace. A useful shortcut if you forgot to hold the <span class="key">OPT</span> key while clicking through folders and all those still open Tracker windows clutter your workspace.</p></li>
 </ul>
@@ -71,13 +71,13 @@
 </td></tr>
 <tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
 <tr><td colspan="5"><h3>Action menu</h3></td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries from the list that are not currently selected.</td></tr>
 <tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
 <tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
 <tr><td colspan="5"><h3>Settings menu</h3></td></tr>
 <tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line tool <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expressions" rel="nofollow">regular expressions</a>.</td></tr>
 <tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
 <tr><td colspan="5"><h3>History menu</h3></td></tr>
 <tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>Guía del usuario</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,9 +42,9 @@
 <li><a href="../../en/preferences/e-mail.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="deskbar.html">Deskbar (Barra de Escritorio)</a> 
+ «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">Preferencias</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="filetypes.html">Tipos de archivo</a>  »
+::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -182,9 +182,9 @@ Si tiene una conexión de marcado, puede verificar la opción <span class="menu"
 <div class="nav">
 <div class="inner"><span>
- «  <a href="deskbar.html">Deskbar (Barra de Escritorio)</a> 
+ «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">Preferencias</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="filetypes.html">Tipos de archivo</a>  »
+::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>Guía del usuario</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,8 +42,8 @@
 </ul>
 <span>
 «  <a href="index.html">Índice</a> 
-::  <a href="contents.html" class="uplink">Contenidos</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workshop-filetypes+attributes.html">Taller</a>  »
+::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
@@ -146,8 +146,8 @@ Usando el elemento del menú <span class="menu">Save Query as Template</span> (G
 <div class="nav">
 <div class="inner"><span>
 «  <a href="index.html">Índice</a> 
-::  <a href="contents.html" class="uplink">Contenidos</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workshop-filetypes+attributes.html">Taller</a>  »
+::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>Guía del usuario</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,9 +41,9 @@
 <li><a href="../en/tracker.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="teammonitor.html">Monitor de actividad (Team Monitor)</a> 
+ «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">Contenidos</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Agregados de Tracker</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -194,9 +194,9 @@ Este filtrado de type-ahead se selecciona en las <a href="#tracker-preferences.h
 <div class="nav">
 <div class="inner"><span>
- «  <a href="teammonitor.html">Monitor de actividad (Team Monitor)</a> 
+ «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">Contenidos</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Agregados de Tracker</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -24,7 +24,7 @@
 <body>
 <div id="banner">
-<div><span>Guide de l’utilisateur</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -59,7 +59,7 @@
 <tr><td>Réglages :</td><td></td><td><span class="path">~/config/settings/DriveSetup</span></td></tr>
 </table>
 <p><br /></p>
-<p>DriveSetup est un outils pour créer, supprimer et initialiser des partitions. Pour le moment, il ne peu pas redimensionner ou déplacer une partition existante, de sorte que vous aurez besoin soit d'un volume avec un espace non partitionné (peut-être un disque USB externe ou un autre disque dur) ou modifier la configuration avec un outil comme  <a href="http://gparted.sourceforge.net/livecd.php">GParted LiveCD</a>  pour fournir l'espace pour une nouvelle partition.</p>
+<p>DriveSetup est un outils pour créer, supprimer et initialiser des partitions. Pour le moment, il ne peut pas redimensionner ou déplacer une partition existante, de sorte que vous aurez besoin soit d'un volume avec un espace non partitionné (peut-être un disque USB externe ou un autre disque dur) ou modifier la configuration avec un outil comme  <a href="http://gparted.sourceforge.net/livecd.php">GParted LiveCD</a>  pour fournir l'espace pour une nouvelle partition.</p>
 <img src="../images/apps-images/drivesetup.png" alt="drivesetup.png" />
 <p>Au sommet se trouve une représentation graphique de toutes les partitions à l'intérieur du lecteur choisi dans la liste en dessous.
 Vous pouvez avoir jusqu'à 4 partitions primaires au maximum, chacune d'entre elles pouvant contenir un certain nombre de partitions logiques.
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>Guide de l’utilisateur</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -71,12 +71,12 @@ elles peuvent aussi être déplacées avec les touches <span class="key">←</sp
 un certain nombre d'options :</p>
 <table summary="options" border="0" cellpadding="2" cellspacing="0">
 <tr><td><span class="menu">Save Image</span></td><td><span class="key">ALT</span> <span class="key">S</span></td><td> </td><td>Sauvegarde la visualisation en cours dans un fichier de ressource</td></tr>
-<tr><td><span class="menu">Copy Image</span></td><td><span class="key">ALT</span> <span class="key">C</span></td><td> </td><td>Copie la visualisation en cours dans le presse papier.</td></tr>
+<tr><td><span class="menu">Copy Image</span></td><td><span class="key">CMD</span> <span class="key">C</span></td><td> </td><td>Copie la visualisation en cours dans le presse papier.</td></tr>
-<tr><td><span class="menu">Hide/Show Info</span></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Bascule l'affichage de toutes les informations complémentaires.</td></tr>
+<tr><td><span class="menu">Hide/Show Info</span></td><td><span class="key">CMD</span> <span class="key">T</span></td><td> </td><td>Bascule l'affichage de toutes les informations complémentaires.</td></tr>
 <tr><td><span class="menu">Add a Crosshair</span></td><td><span class="key">ALT</span> <span class="key">H</span></td><td> </td><td>Ajoute une croix que vous pouvez déplacer.</td></tr>
 <tr><td><span class="menu">Remove a Crosshair</span></td><td><span class="key">ALT</span> <span class="key">MAJ</span> <span class="key">H</span></td><td> </td><td>Retire la dernière croix que vous avez ajoutée.</td></tr>
 <tr><td><span class="menu">Hide/Show Grid</span></td><td><span class="key">ALT</span> <span class="key">G</span></td><td> </td><td>Affiche la grille en surimpression.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Freeze/Unfreeze image</span></td><td><span class="key">ALT</span> <span class="key">F</span></td><td> </td><td>Arrête/reprend la mise à jour de la zone d'agrandissement.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Freeze/Unfreeze image</span></td><td><span class="key">CMD</span> <span class="key">F</span></td><td> </td><td>Arrête/reprend la mise à jour de la zone d'agrandissement.</td></tr>
 <tr><td><span class="menu">Stick Coordinates</span></td><td><span class="key">ALT</span> <span class="key">I</span></td><td> </td><td>Continue de mettre à jour la zone agrandie, mais sans suivre plus longtemps le pointeur de la souris.</td></tr>
 <tr><td><span class="menu">Make Square</span></td><td><span class="key">ALT</span> <span class="key">/</span></td><td> </td><td>Revient à un écran carré après le redimensionnement de la fenêtre.</td></tr>
 <tr><td class="onelinetop"><span class="menu">Decrease Window Size</span></td><td><span class="key">ALT</span> <span class="key">-</span></td><td> </td><td>Rétrécit la zone la zone prise en compte autour du pointeur de la souris.</td></tr>
@@ -49,40 +49,41 @@
 <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><img src="../../images/apps-images/textsearch-icon_64.png" alt="textsearch-icon_64.png" width="64" height="64" />TextSearch</h2>
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
-<tr><td>Deskbar :</td><td style="width:15px;"></td><td><i>No entry, normally launched via Tracker Add-on</i></td></tr>
+<tr><td>Deskbar :</td><td style="width:15px;"></td><td><i>Pas d'entrée, normalement vous y accédez via les Extensions du Tracker</i></td></tr>
 <tr><td>Localisation :</td><td></td><td><span class="path">/boot/system/apps/TextSearch</span></td></tr>
 <tr><td>Réglages :</td><td></td><td><span class="path">~/config/settings/TextSearch</span></td></tr>
 </table>
 <p><br /></p>
-<p>TextSearch looks for a string in text files. Typically it is invoked from <a href="../tracker-add-ons.html">Tracker's Add-on</a> context menu on the selection of files or folders you want to search.</p>
+<p>TextSearch recherche une chaîne de caractères dans des fichiers texte. En général, il est appelé à partir du menu contextuel <a href="../tracker-add-ons.html">Extensions du Tracker</a> sur la selection de fichiers ou dossiers que vous souhaitez examiner.</p>
 <img src="../images/apps-images/textsearch.png" alt="textsearch.png" />
-<p>You enter a search string in the text box on top and hit <span class="key">RETURN</span> or click <span class="button">Search</span> to start. If <span class="menu">Show lines</span> is checked, the hits are automatically expanded to show the lines of the file containing the search string.</p>
+<p>Entrez la chaîne à rechercher dans la zone de texte en haut, puis pressez <span Class="key">ENTRÉE</span> ou cliquez sur <span class="button">Search</span>(Rechercher) pour démarrer la recherche. Si <span class="menu">Show lines</span>(Afficher les lignes) est coché, les résultats sont automatiquement développés pour afficher les lignes du fichier contenant la chaîne de recherche.</p>
-<p>Only a few words on some of the otherwise self-explaining menu items:</p>
+<p>Juste quelques mots sur les éléments de menu les moins évidents :</p>
 <table summary="menus" border="0" cellpadding="2" cellspacing="0">
-<tr><td colspan="5"><h3>File menu</h3></td></tr>
+<tr><td colspan="5"><h3>Le menu Fichier (File)</h3></td></tr>
-<tr><td class="onelinetop"><span class="menu">New window</span></td><td></td><td><span class="key">ALT</span> <span class="key">N</span></td><td> </td><td>Opens a new window where you can enter another string and search through the same files/folders.
+<tr><td class="onelinetop"><span class="menu">New window</span></td><td></td><td><span class="key">CMD</span> <span class="key">N</span></td><td> </td><td>Ouvre une nouvelle fenêtre où vous pouvez entrer une autre chaîne à rechercher dans les mêmes fichiers ou dossiers.</td></tr>
-</td></tr>
+<tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">CMD</span> <span class="key">F</span></td><td></td><td>Vous permet de choisir un nouvel ensemble de fichiers et de dossiers à examiner.</td></tr>
-<tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
+<tr><td colspan="5"><h3>Le menu Action</h3></td></tr>
-<tr><td colspan="5"><h3>Action menu</h3></td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">CMD</span> <span class="key">T</span></td><td> </td><td>Supprime toutes les entrées de la liste qui ne sont pas actuellement sélectionnées.</td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">CMD</span> <span class="key">O</span></td><td></td><td>Ouvre les fichiers sélectionnés avec leurs applications préférées (comme avec un double-clic). Si c'est un éditeur de texte qui le supporte (comme Pe), vous pouvez passer à la ligne exacte où la chaîne a été trouvé.</td></tr>
-<tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
+<tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">CMD</span> <span class="key">K</span></td><td></td><td>Ouvre l'emplacement des fichiers sélectionnés dans Tracker.</td></tr>
-<tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">CMD</span> <span class="key">C</span></td><td></td><td>Copie la sélection actuelle dans le presse papier.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td colspan="5"><h3>Le menu Réglage (Settings)</h3></td></tr>
-<tr><td colspan="5"><h3>Settings menu</h3></td></tr>
+<tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>C'est utile lorsque vous travaillez dans un environnement « à la Unix », où, souvent, les fichiers d'administration sont cachés à l'intérieur de « <tt>.dossiers/</tt> ». Par exemples, les systèmes de gestion de versions de sources comme SVN et CVS, qui sont largement utilisés dans le Haiku, utilisent cela.</td></tr>
-<tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch utilise l'outil en ligne de commande <span class="cli">grep</span>. 
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+Pour ce faire, les caractères spéciaux comme <tt>'"*\$?!</tt> et espace, doivent 
-<tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
+être précédés du caractère d'échappement <tt>\</tt>.
-<tr><td colspan="5"><h3>History menu</h3></td></tr>
+Désactiver ce paramètre signifie que vous devez le faire vous-même, mais en échange, vous bénéficierez de la puissance des <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">expressions régulières</a>.</td></tr>
-<tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
+<tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch n'est actuellement utile que pour trouver des chaînes dans les fichiers de texte brut. En désactivant ce paramètre, tous les types de fichiers seront examinées.</td></tr>
-<tr><td colspan="5"><h3>Encoding menu</h3></td></tr>
+<tr><td colspan="5"><h3>Le menu Historique (History)</h3></td></tr>
-<tr><td colspan="4"></td><td>Lets you choose different character encodings if needed.</td></tr>
+<tr><td colspan="4"></td><td>Contient les chaînes recherchées récemment.</td></tr>
 <tr><td colspan="5"><h3>Le  menu Encodage (Encoding)</h3></td></tr>
 <tr><td colspan="4"></td><td>Vous permet de choisir un jeu de caractères différents, si nécessaire.</td></tr>
 </table>
 </div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>Guide de l’utilisateur</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,9 +41,9 @@
 <li><a href="../en/gui.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="filesystem-layout.html">Structure du système de fichiers</a> 
+ «  <a href="filesystem-layout.html">Filesystem layout</a> 
-::  <a href="contents.html" class="uplink">Sommaire</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workspaces.html">Espaces de travail</a>  »
+::  <a href="workspaces.html">Workspaces</a>  »
 </span></div>
 </div>
@@ -116,9 +116,9 @@ Un clic droit sur la poignée d'un Réplicant ouvrira un menu contextuel, où <s
 <div class="nav">
 <div class="inner"><span>
- «  <a href="filesystem-layout.html">Structure du système de fichiers</a> 
+ «  <a href="filesystem-layout.html">Filesystem layout</a> 
-::  <a href="contents.html" class="uplink">Sommaire</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workspaces.html">Espaces de travail</a>  »
+::  <a href="workspaces.html">Workspaces</a>  »
 </span></div>
 </div>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>Guide de l’utilisateur</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,8 +42,8 @@
 <li><a href="../en/keyboard-shortcuts.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="tracker-add-ons.html">Extensions du Tracker</a> 
+ «  <a href="tracker-add-ons.html">Tracker Add-Ons</a> 
-::  <a href="contents.html" class="uplink">Sommaire</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="deskbar.html">Deskbar</a>  »
 </span></div>
 </div>
@@ -130,8 +130,8 @@ Les lettres que vous tapez apparaîtront en bas à gauche de la fenêtre, là ou
 <div class="nav">
 <div class="inner"><span>
- «  <a href="tracker-add-ons.html">Extensions du Tracker</a> 
+ «  <a href="tracker-add-ons.html">Tracker Add-Ons</a> 
-::  <a href="contents.html" class="uplink">Sommaire</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
 ::  <a href="deskbar.html">Deskbar</a>  »
 </span></div>
 </div>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>Guide de l’utilisateur</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -43,7 +43,7 @@
 </ul>
 <span>
 «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">Préférences</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -188,7 +188,7 @@ Tous les dossiers ou requêtes placés dans ce dossier apparaîtront dans le men
 <div class="nav">
 <div class="inner"><span>
 «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">Préférences</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>Guide de l’utilisateur</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -43,8 +43,8 @@
 </ul>
 <span>
 «  <a href="index.html">Index</a> 
-::  <a href="contents.html" class="uplink">Sommaire</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workshop-filetypes+attributes.html">Atelier</a>  »
+::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
@@ -152,8 +152,8 @@ En utilisant la méthode <span class="menu">Save Query as Template</span> du men
 <div class="nav">
 <div class="inner"><span>
 «  <a href="index.html">Index</a> 
-::  <a href="contents.html" class="uplink">Sommaire</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workshop-filetypes+attributes.html">Atelier</a>  »
+::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>Guide de l’utilisateur</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -43,8 +43,8 @@
 </ul>
 <span>
 «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">Sommaire</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Extensions du Tracker</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -199,8 +199,8 @@ Si vous démarrez plusieurs tâches, un indicateur apparaît pour chacune d’en
 <div class="nav">
 <div class="inner"><span>
 «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">Sommaire</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Extensions du Tracker</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -20,7 +20,7 @@
 <body>
 <div id="banner">
-<div><span>User guide</span></div>
+<div><span>Guida dell'utente</span></div>
 </div>
 <div class="nav">
@@ -47,7 +47,7 @@
 <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>
+<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><img src="../../images/apps-images/textsearch-icon_64.png" alt="textsearch-icon_64.png" width="64" height="64" />TextSearch</h2>
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
@@ -69,13 +69,13 @@
 </td></tr>
 <tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
 <tr><td colspan="5"><h3>Action menu</h3></td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries from the list that are not currently selected.</td></tr>
 <tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
 <tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
 <tr><td colspan="5"><h3>Settings menu</h3></td></tr>
 <tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line tool <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expressions" rel="nofollow">regular expressions</a>.</td></tr>
 <tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
 <tr><td colspan="5"><h3>History menu</h3></td></tr>
 <tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
@@ -9,6 +9,8 @@
 *
 * Authors:
 *		Humdinger <[email protected]>
 * Translators:
 *		MichaelPeppers
 *
 -->
 	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
@@ -72,7 +74,7 @@
 <p>The Workspaces applet provides some additional functionality when clicking on a window while holding certain modifier keys:</p>
 <table summary="functionality-thru-modifiers" border="0" cellspacing="0" cellpadding="4">
 <tr><td><span class="key">CTRL</span></td><td style="width:15px;"></td><td>Brings the window to the front.</td></tr>
-<tr><td><span class="key">CTRL</span> <span class="key">SHIFT</span></td><td></td><td>Minimizes the window.</td></tr>
+<tr><td><span class="key">CTRL</span> <span class="key">SHIFT</span></td><td></td><td>Minimizza la finestra.</td></tr>
 <tr><td><span class="key">OPT</span></td><td></td><td>Sends the window to the back.</td></tr>
 </table>
@@ -11,6 +11,7 @@
 *		Humdinger <[email protected]>
 * Translators:
 *		Giuseppe Gargaro
 *		MichaelPeppers
 *
 -->
 	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
@@ -56,13 +57,13 @@
 <tr><td>Posizione:</td><td></td><td><span class="path">/boot/system/preferences/Appearance</span></td></tr>
 <tr><td>Impostazioni:</td><td></td><td><span class="path">~/config/settings/system/app_server/appearance</span></td></tr>
 </table>
-<p>Le preferenze Appearance permettono di cambiare alcuni aspetti visivi di Haiku .</p>
+<p>Le preferenze in Appearance permettono di cambiare alcuni aspetti visivi di Haiku .</p>
 <h2>
 <a href="#"><img src="../../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="colors" name="colors">Colors</a></h2>
+<a id="colors" name="colors">Colori</a></h2>
 <img src="../images/prefs-images/appearance-colors.png" alt="appearance-colors.png" />
-<p>In the first tab, <span class="menu">Colors</span>, you can change the colors of different parts of the user interface. The color well accepts drag&amp;drops from other programs, letting you drag colors over from e.g. <span class="app">WonderBrush</span>, <span class="app">Icon-O-Matic</span> or the <span class="app">Backgrounds</span> panel.</p>
+<p>Nella pima tab, <span class="menu">Colori</span>, puoi cambiare i colori di diverse parti dell'interfaccia utente. Il colore accetta anche drag&amp;drop da altri programmi, permettendo di prendere colori da, per esempio, <span class="app">WonderBrush</span>, <span class="app">Icon-O-Matic</span> o dal pannello di <span class="app">Backgrounds</span>.</p>
 <h2>
 <a href="#"><img src="../../images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -97,7 +98,7 @@ Antialiasing type</h3>
 <tr><td style="text-align:center; font-style:italic"><img src="../../images/prefs-images/appearance-glyph-on.png" alt="appearance-glyph-on.png" /><br />Grayscale, Hinting: on</td><td style="width:15px;"></td><td style="text-align:center; font-style:italic"><img src="../../images/prefs-images/appearance-glyph-on-subpixel.png" alt="appearance-glyph-on-subpixel.png" /><br />LCD subpixel, Hinting: on</td></tr>
 </table>
 <p><br /></p>
-<p>At the bottom of the panel are two buttons:</p>
+<p>Nel fondo del pannello ci sono due pulsanti:</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
 <tr><td><span class="button">Defaults</span></td><td> </td><td>resets everything to default values.</td></tr>
 <tr><td><span class="button">Annulla</span></td><td> </td><td>brings back the settings that were active when you started the Appearance preferences.</td></tr>
@@ -11,6 +11,7 @@
 *		Humdinger <[email protected]>
 * Translators:
 *		Andrea Bernardi
 *		MichaelPeppers
 *
 -->
 	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
@@ -74,7 +75,7 @@
 <p>Whether an icon label's actual text is black or white depends on the setting of the color picker. A dark color sets the text to white, a light color to black. So, if you assign a very bright image to the background, you should also set the color picker to a bright color in order to have icon labels readable in black. (Or use the outline option above.)<br />
 The selected color is also reflected in the <a href="../desktop-applets/workspaces.html">Workspaces applet</a>, which ignores images as backgrounds.</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="button">Annulla</span></td><td> </td><td>Ripristina le impostazioni iniziali all'appertura della preferences Backgrounds</td></tr>
+<tr><td><span class="button">Annulla</span></td><td> </td><td>Ripristina le impostazioni presenti all'apertura di Backgrounds.</td></tr>
 <tr><td><span class="button">Applica</span></td><td> </td><td>Applica i tuoi cambiamenti.</td></tr>
 </table>
@@ -49,7 +49,6 @@
 <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>
 <h1><img src="../../images/prefs-images/deskbar-icon_64.png" alt="deskbar-icon_64.png" width="64" height="64" />Deskbar</h1>
 <table summary="quickinfo" border="0" cellspacing="0" cellpadding="2">
@@ -59,7 +58,7 @@
 <span class="path">~/config/settings/Deskbar_security_code</span></td></tr>
 </table>
 <p><br /></p>
-<p>The Deskbar preference panel is also available from the Deskbar. Its settings are discussed in the topic on <a href="../deskbar.html#deskbar-prefs">Deskbar</a>.</p>
+<p>Il pannello delle preferenze del Deskbar è disponibile anche attraverso il Deskbar stesso. Le sue impostazioni sono discusse in un paragrafo apposito nella pagina del <a href="../deskbar.html#deskbar-prefs">Deskbar</a>.</p>
 </div>
 </div>
@@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a
 	<tr><td><span class="menu">Spam/Genuine Estimate</span></td><td> </td>
 		<td>this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065.</td></tr>
 </table>
-<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
+<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
 <p>With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.</p>
 <h3>
@@ -122,7 +122,7 @@ A good way to cut down the number of search results.</p>
 <ul>
 <li><p>You could copy and paste the string into an email, forum or IRC for others to use or debug.</p></li>
 <li><p>You can use this method to construct a query in <span class="menu">Attribute</span> mode and then switch to <span class="menu">Formula</span> mode, to comfortably generate a search string to use for a query in Terminal or a script.</p></li>
-<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
+<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
 </ul>
 <h2>
@@ -124,7 +124,7 @@ This type-ahead filtering is set in the <a href="#tracker-preferences.html">Trac
 <ul>
 <li><p><b>Resize Window</b> (<span class="key">ALT</span> <span class="key">Y</span>) - Resizes the window to its ideal size.</p></li>
 <li><p><b>Clean Up</b> (<span class="key">ALT</span> <span class="key">K</span>) - Aligns all icons to an invisible grid. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Clean Up All</span> which additionally sorts all icons alphabetically.</p></li>
-<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expression</a>.</p></li>
+<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expression</a>.</p></li>
 <li><p><b>Close</b> (<span class="key">ALT</span> <span class="key">W</span>) - Closes the window. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Close All</span> which closes every Tracker window.</p></li>
 <li><p><b>Close All in Workspace</b> (<span class="key">ALT</span> <span class="key">Q</span>) - Closes every Tracker window in the current workspace. A useful shortcut if you forgot to hold the <span class="key">OPT</span> key while clicking through folders and all those still open Tracker windows clutter your workspace.</p></li>
 </ul>
@@ -9,6 +9,8 @@
 *
 * Authors:
 *		Humdinger <[email protected]>
 * Translators:
 *		log-1
 *
 -->
 	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
@@ -42,25 +44,24 @@
    <!-- «  <a href="activitymonitor.html">ActivityMonitor</a> 
 ::    
 -->
-    <a href="../applications.html#list-of-bundled-apps" class="uplink">アプリケーション</a> 
+    <a href="../applications.html#list-of-bundled-apps" class="uplink">Applications</a> 
 ::  <a href="pe.html">Pe</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><img src="../../images/apps-images/bepdf-icon_64.png" alt="bepdf-icon_64.png" width="64" height="64" />BePDF</h2>
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
 <tr><td>Deskbarメニュー:</td><td style="width:15px;"></td><td><span class="menu">Applications</span></td></tr>
 <tr><td>場所:</td><td></td><td><span class="path">/boot/apps/BePDF/BePDF</span></td></tr>
-<tr><td>Documentation:</td><td></td><td><span class="path">/boot/apps/BePDF/docs/*</span></td></tr>
+<tr><td>ドキュメント:</td><td></td><td><span class="path">/boot/apps/BePDF/docs/*</span></td></tr>
 <tr><td>設定ファイル:</td><td></td><td><span class="path">/boot/common/settings/BePDF</span></td></tr>
 </table>
 <p><br /></p>
-<p>BePDF is a fast launching PDF viewer. Besides viewing, it supports annotating and user-defined bookmarking for unencrypted PDFs. It's fully localized for 20 languages at the moment with additional languages being easily added via text files.</p>
+<p>BePDFは起動が高速なPDFビューアです。PDFを表示することに加えて、暗号化されていないPDFに注釈を加える機能や、ユーザーがブックマークを定義する機能をサポートしています。現在20カ国語について完全にローカライズされています。テキスト・ファイルを編集することで、簡単に新しい言語を追加することができます。</p>
-<p>Documentation is available as <a href="file:///boot/apps/BePDF/docs/English/table_of_contents.html">HTML</a> or <a href="file:///boot/apps/BePDF/docs/English.pdf">PDF</a>. The latter will also open from the menu <span class="menu">Help | Show Help...</span>.</p>
+<p>ドキュメントは<a href="file:///boot/apps/BePDF/docs/English/table_of_contents.html">HTML</a>形式または<a href="file:///boot/apps/BePDF/docs/English.pdf">PDF</a>形式で入手することができます。PDF形式のドキュメントは、メニューの<span class="menu">Help | Show Help...</span>から開くこともできます。</p>
 </div>
 </div>
@@ -68,7 +69,7 @@
 <div class="nav">
 <div class="inner"><span>
 «  <a href="activitymonitor.html">ActivityMonitor</a> 
-::  <a href="../applications.html#list-of-bundled-apps" class="uplink">アプリケーション</a> 
+::  <a href="../applications.html#list-of-bundled-apps" class="uplink">Applications</a> 
 ::  <a href="pe.html">Pe</a>  »
 </span></div>
 </div>
@@ -40,7 +40,7 @@
 </ul>
 <span>
  «  <a href="bepdf.html">BePDF</a> 
-::  <a href="../applications.html#list-of-bundled-apps" class="uplink">アプリケーション</a> 
+::  <a href="../applications.html#list-of-bundled-apps" class="uplink">Applications</a> 
 ::  <a href="vision.html">Vision</a>  »
 </span></div>
 </div>
@@ -53,7 +53,7 @@
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
 <tr><td>Deskbarメニュー:</td><td style="width:15px;"></td><td><span class="menu">Applications</span></td></tr>
 <tr><td>場所:</td><td></td><td><span class="path">/boot/apps/Pe/Pe</span></td></tr>
-<tr><td>Documentation:</td><td></td><td><span class="path">/boot/apps/Pe/Documentation.html</span></td></tr>
+<tr><td>ドキュメント:</td><td></td><td><span class="path">/boot/apps/Pe/Documentation.html</span></td></tr>
 <tr><td>設定ファイル:</td><td></td><td><span class="path">~/config/settings/pe/*</span></td></tr>
 </table>
 <p><br /></p>
@@ -66,7 +66,7 @@
 <div class="nav">
 <div class="inner"><span>
  «  <a href="bepdf.html">BePDF</a> 
-::  <a href="../applications.html#list-of-bundled-apps" class="uplink">アプリケーション</a> 
+::  <a href="../applications.html#list-of-bundled-apps" class="uplink">Applications</a> 
 ::  <a href="vision.html">Vision</a>  »
 </span></div>
 </div>
@@ -40,7 +40,7 @@
 </ul>
 <span>
  «  <a href="terminal.html">Terminal</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">アプリケーション</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
 ::  <a href="tv.html">TV</a>  »
 </span></div>
 </div>
@@ -69,13 +69,13 @@
 </td></tr>
 <tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
 <tr><td colspan="5"><h3>Action menu</h3></td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries from the list that are not currently selected.</td></tr>
 <tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
 <tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
 <tr><td colspan="5"><h3>Settings menu</h3></td></tr>
 <tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line tool <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expressions" rel="nofollow">regular expressions</a>.</td></tr>
 <tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
 <tr><td colspan="5"><h3>History menu</h3></td></tr>
 <tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
@@ -88,7 +88,7 @@
 <div class="nav">
 <div class="inner"><span>
  «  <a href="terminal.html">Terminal</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">アプリケーション</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
 ::  <a href="tv.html">TV</a>  »
 </span></div>
 </div>
@@ -40,7 +40,7 @@
 </ul>
 <span>
  «  <a href="vision.html">Vision</a> 
-::  <a href="../applications.html#list-of-bundled-apps" class="uplink">アプリケーション</a>
+::  <a href="../applications.html#list-of-bundled-apps" class="uplink">Applications</a>
 </span></div>
 </div>
@@ -52,7 +52,7 @@
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
 <tr><td>Deskbarメニュー:</td><td style="width:15px;"></td><td><span class="menu">Applications</span></td></tr>
 <tr><td>場所:</td><td></td><td><span class="path">/boot/apps/WonderBrush/WonderBrush</span></td></tr>
-<tr><td>Documentation:</td><td></td><td><span class="path">/boot/apps/WonderBrush/Documentation {language}</span></td></tr>
+<tr><td>ドキュメント:</td><td></td><td><span class="path">/boot/apps/WonderBrush/Documentation {language}</span></td></tr>
 <tr><td>設定ファイル:</td><td></td><td><span class="path">~/config/settings/WonderBrush</span></td></tr>
 </table>
 <p><br /></p>
@@ -65,7 +65,7 @@
 <div class="nav">
 <div class="inner"><span>
 «  <a href="vision.html">Vision</a> 
-::  <a href="../applications.html#list-of-bundled-apps" class="uplink">アプリケーション</a>
+::  <a href="../applications.html#list-of-bundled-apps" class="uplink">Applications</a>
 </span></div>
 </div>
 -->
@@ -9,12 +9,14 @@
 *
 * Authors:
 *		Humdinger <humdingerb@gmail.com>
 * Translators:
 *		log-1
 *
 -->
 	<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>Bash and Scripting</title>
+	<title>Bashとスクリプト化</title>
 	<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
 </head>
 <body>
@@ -47,50 +49,49 @@
 <div id="content">
 <div>
 <div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
-<h1>Bash and Scripting</h1>
+<h1>Bashとスクリプト化</h1>
-<p>"Scripting" is the technique of automating procedures by stringing together commands and saving it all as text files, so called "scripts". Every time you run such a script, the commands are processed one after the other just like they would if you entered them into the <a href="applications/terminal.html">Terminal</a> by hand.<br />
+<p>「スクリプト化」とは、複数のコマンドを並べて書き、「スクリプト」と呼ばれるテキスト・ファイルとして保存することにより処理を自動化する方法のことです。スクリプトを走らせる度に、あたかも<a href="applications/terminal.html">Terminal</a>でそれらコマンドを1つ1つ手で打ち込んでいるようにコマンドが実行されます。<br />
-Scripts can range from simply executing a few commands in a specific order to sophisticated pieces of code that solve complex tasks.</p>
+スクリプトは、単に数個のコマンドをある特定の順番で実行するものから、複雑なタスクを処理するための高度なコードのかたまりまで、多岐にわたります。</p>
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="bash" name="bash">The Bash</a></h2>
+<a id="bash" name="bash">Bash</a></h2>
-<p>Since scripts rely naturally a lot on the shell they are interpreted by, you should first familiarize yourself with the BASH that's used by Haiku. There are many resources online as it's a widely used shell. One nice document is Johan Jansson's <a href="http://www.beforever.com/bashtut.htm" class="printurl">Introduction to bash - a tutorial for bash under BeOS</a>.</p>
+<p>そもそもスクリプトはそれを解釈するシェルに大きく依存するため、まずはHaikuで使用されているBASHに精通する必要があります。BASHは広く使用されているシェルであるため、オンライン上に資料が豊富に存在します。すばらしいドキュメントの1つに、Johan Jansson氏の<a href="http://www.beforever.com/bashtut.htm" class="printurl">Introduction to bash - a tutorial for bash under BeOS</a>があります。</p>
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="scripting-bible" name="scripting-bible">The Scripting Bible</a></h2>
+<a id="scripting-bible" name="scripting-bible">スクリプト化のための必読書</a></h2>
-<p>After you've learned a few basics about working in the shell, it's time to slowly ease yourself into the world of scripting. Again, you'll find loads of tutorials and reference material online as well as in bookstores. A very nice introduction that's practically tailor-made for Haiku is the online available <a href="http://www.birdhouse.org/beos/bible/bos/ch_scripting1.html" class="printurl">Scripting Chapter</a> (<a href="http://www.birdhouse.org/beos/bible/bos/BeOS.scripting.PDF">PDF, 900kb</a>) of Scot Hacker's BeOS Bible.</p>
+<p>シェル内で作業するためのいくつかの基礎を学んだあとは、スクリプト化の世界にゆっくりと歩み出しましょう。このときも、本屋と同じくらい豊富なチュートリアルやリファレンスをオンライン上で見つけられるでしょう。Haikuにほぼピッタリの非常にすばらしい入門編に、オンラインで入手可能なScot Hacker氏によるBeOSの必読書の<a href="http://www.birdhouse.org/beos/bible/bos/ch_scripting1.html" class="printurl">Scripting Chapter</a> (<a href="http://www.birdhouse.org/beos/bible/bos/BeOS.scripting.PDF">PDF, 900kb</a>)があります。</p>
 <h2>
-<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a><a id="user-scripts" name="user-scripts">Scripts in Haiku</a></h2>
+<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a><a id="user-scripts" name="user-scripts">Haikuにおけるスクリプト</a></h2>
-<p>In Haiku, the system makes of course also use of scripting. Booting and shutting down are typical scripting procedures. These defined sequences can be augmented by the user with certain user scripts.<br />
+<p>Haikuでは、当然のことながらシステムもまたスクリプト化機能を使用しています。起動とシャット・ダウンはスクリプト化された手続きの典型です。はじめから定義されたこれら手続きは、特定のユーザー・スクリプトを用いてユーザーが拡張することができます。<br />
-If they don't exist already, you'll have to create the needed files yourself. Otherwise simply add your commands where in the process you want them to be executed.</p>
+もしこれらユーザー・スクリプトがまだ存在しない場合は、手動でこれらファイルを作成する必要があります。ユーザー・スクリプトが存在する場合は、処理を実行したい場所に必要なコマンドを追加するだけで済みます。</p>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="userbootscript" name="userbootscript">The UserBootscript</a></h3>
+<a id="userbootscript" name="userbootscript">UserBootscript</a></h3>
-<p><span class="path">/boot/home/config/boot/UserBootscript</span> will be executed after the system has finished its boot process. For example, you could launch a number of programs that would then be automatically started on every boot up:</p>
+<p>システムの起動プロセスが完了すると、<span class="path">/boot/home/config/boot/UserBootscript</span>が実行されます。例えば次のように、システムが起動した直後に毎回いくつかのプログラムを自動起動させることができます:</p>
-<pre># Start LaunchBox
+<pre># LaunchBox を起動する
 /boot/system/apps/LaunchBox &amp;
-# Start Workspaces Applet
+# Workspaces アプレットを起動する
 /boot/system/apps/Workspaces &amp;</pre>
-<p>Remember to end a command with an "<tt>&amp;</tt>" to start it as a background process, or the script will halt until that command has finished (in this case: the launched app was closed again).</p>
+<p>コマンドをバックグラウンド・プロセスとして実行するために、コマンドの末尾は"<tt>&amp;</tt>"で終わらせることを覚えておいてください。さもなくばそのコマンドが完了するまで(この例では、起動したアプリケーションが再度閉じられるまで)スクリプトが停止してしまいます。</p>
-<p>A simple alternative to the above for launching applications at boot up is to put links to them in the <span class="path">/boot/home/config/boot/launch</span> directory. This can be done simply by right-clicking on the application you wish to have started automatically, going to <span class="menu">Create Link</span> and then <a href="tracker.html#navigating">navigating</a> to the above directory.</p>
+<p>システムの起動時にアプリケーションを起動させるための、上記とは違うシンプルな方法の1つに、それらアプリケーションへのリンクを<span class="path">/boot/home/config/boot/launch</span>ディレクトリに置くという方法があります。この方法は、自動起動させたいアプリケーションを右クリックして、<span class="menu">Create Link</span>にマウスカーソルを合わせたあと、前述のディレクトリへ<a href="tracker.html#navigating">ナビゲート</a>することで簡単に実現できます。</p>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="usershutdownscript" name="usershutdownscript">The UserShutdownScript</a></h3>
+<a id="usershutdownscript" name="usershutdownscript">UserShutdownScript</a></h3>
-<p><span class="path">/boot/home/config/boot/UserShutdownScript</span> will be executed as the first step in the shutdown process. If the script returns a non-zero exit status, the shutdown is aborted.</p>
+<p><span class="path">/boot/home/config/boot/UserShutdownScript</span>はシャットダウン・プロセスの最初のステップで実行されます。このスクリプトが0でない終了ステータスを返すと、シャットダウンは中断されます。</p>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="usershutdownfinishscript" name="usershutdownfinishscript">The UserShutdownFinishScript</a></h3>
+<a id="usershutdownfinishscript" name="usershutdownfinishscript">UserShutdownFinishScript</a></h3>
-<p><span class="path">/boot/home/config/boot/UserShutdownFinishScript</span> is executed as the last step in the shutdown process. Note, that most parts of the system have terminated by the time this script is executed.</p>
+<p><span class="path">/boot/home/config/boot/UserShutdownFinishScript</span>はシャットダウンの最終ステップで実行されます。このスクリプトが実行されるときには、システムの大部分が終了していることに注意してください。</p>
 </div>
 </div>
@@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a
 	<tr><td><span class="menu">Spam/Genuine Estimate</span></td><td> </td>
 		<td>this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065.</td></tr>
 </table>
-<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
+<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
 <p>With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.</p>
 <h3>
@@ -122,7 +122,7 @@ A good way to cut down the number of search results.</p>
 <ul>
 <li><p>You could copy and paste the string into an email, forum or IRC for others to use or debug.</p></li>
 <li><p>You can use this method to construct a query in <span class="menu">Attribute</span> mode and then switch to <span class="menu">Formula</span> mode, to comfortably generate a search string to use for a query in Terminal or a script.</p></li>
-<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
+<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
 </ul>
 <h2>
@@ -124,7 +124,7 @@ This type-ahead filtering is set in the <a href="#tracker-preferences.html">Trac
 <ul>
 <li><p><b>Resize Window</b> (<span class="key">ALT</span> <span class="key">Y</span>) - Resizes the window to its ideal size.</p></li>
 <li><p><b>Clean Up</b> (<span class="key">ALT</span> <span class="key">K</span>) - Aligns all icons to an invisible grid. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Clean Up All</span> which additionally sorts all icons alphabetically.</p></li>
-<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expression</a>.</p></li>
+<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expression</a>.</p></li>
 <li><p><b>Close</b> (<span class="key">ALT</span> <span class="key">W</span>) - Closes the window. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Close All</span> which closes every Tracker window.</p></li>
 <li><p><b>Close All in Workspace</b> (<span class="key">ALT</span> <span class="key">Q</span>) - Closes every Tracker window in the current workspace. A useful shortcut if you forgot to hold the <span class="key">OPT</span> key while clicking through folders and all those still open Tracker windows clutter your workspace.</p></li>
 </ul>
@@ -71,13 +71,13 @@
 </td></tr>
 <tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
 <tr><td colspan="5"><h3>Action menu</h3></td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries from the list that are not currently selected.</td></tr>
 <tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
 <tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
 <tr><td colspan="5"><h3>Settings menu</h3></td></tr>
 <tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line tool <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expressions" rel="nofollow">regular expressions</a>.</td></tr>
 <tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
 <tr><td colspan="5"><h3>History menu</h3></td></tr>
 <tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
@@ -9,6 +9,8 @@
 *
 * Authors:
 *		Humdinger <humdingerb@gmail.com>
 * Translators:
 *		Vasco Costa
 *
 -->
 	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
@@ -47,7 +49,6 @@
 <div id="content">
 <div>
 <div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
 <h1><img src="../../images/prefs-images/deskbar-icon_64.png" alt="deskbar-icon_64.png" width="64" height="64" />Deskbar</h1>
 <table summary="quickinfo" border="0" cellspacing="0" cellpadding="2">
@@ -57,7 +58,7 @@
 <span class="path">~/config/settings/Deskbar_security_code</span></td></tr>
 </table>
 <p><br /></p>
-<p>The Deskbar preference panel is also available from the Deskbar. Its settings are discussed in the topic on <a href="../deskbar.html#deskbar-prefs">Deskbar</a>.</p>
+<p>O painel de preferências da Deskbar também está acessível a partir da Deskbar. As definições estão documentadas no tópico <a href="../deskbar.html#deskbar-prefs">Deskbar</a>.</p>
 </div>
 </div>
@@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a
 	<tr><td><span class="menu">Spam/Genuine Estimate</span></td><td> </td>
 		<td>this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065.</td></tr>
 </table>
-<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
+<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
 <p>With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.</p>
 <h3>
@@ -122,7 +122,7 @@ A good way to cut down the number of search results.</p>
 <ul>
 <li><p>You could copy and paste the string into an email, forum or IRC for others to use or debug.</p></li>
 <li><p>You can use this method to construct a query in <span class="menu">Attribute</span> mode and then switch to <span class="menu">Formula</span> mode, to comfortably generate a search string to use for a query in Terminal or a script.</p></li>
-<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
+<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
 </ul>
 <h2>
@@ -124,7 +124,7 @@ This type-ahead filtering is set in the <a href="#tracker-preferences.html">Trac
 <ul>
 <li><p><b>Resize Window</b> (<span class="key">ALT</span> <span class="key">Y</span>) - Resizes the window to its ideal size.</p></li>
 <li><p><b>Clean Up</b> (<span class="key">ALT</span> <span class="key">K</span>) - Aligns all icons to an invisible grid. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Clean Up All</span> which additionally sorts all icons alphabetically.</p></li>
-<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expression</a>.</p></li>
+<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expression</a>.</p></li>
 <li><p><b>Close</b> (<span class="key">ALT</span> <span class="key">W</span>) - Closes the window. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Close All</span> which closes every Tracker window.</p></li>
 <li><p><b>Close All in Workspace</b> (<span class="key">ALT</span> <span class="key">Q</span>) - Closes every Tracker window in the current workspace. A useful shortcut if you forgot to hold the <span class="key">OPT</span> key while clicking through folders and all those still open Tracker windows clutter your workspace.</p></li>
 </ul>
@@ -71,13 +71,13 @@
 </td></tr>
 <tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
 <tr><td colspan="5"><h3>Action menu</h3></td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries from the list that are not currently selected.</td></tr>
 <tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
 <tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
 <tr><td colspan="5"><h3>Settings menu</h3></td></tr>
 <tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line tool <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expressions" rel="nofollow">regular expressions</a>.</td></tr>
 <tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
 <tr><td colspan="5"><h3>History menu</h3></td></tr>
 <tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>Руководство пользователя</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -43,8 +43,8 @@
 </ul>
 <span>
 «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">Настройки</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="filetypes.html">Типы файлов</a>  »
+::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -183,8 +183,8 @@
 <div class="nav">
 <div class="inner"><span>
 «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">Настройки</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="filetypes.html">Типы файлов</a>  »
+::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -24,7 +24,7 @@
 <body>
 <div id="banner">
-<div><span>Руководство пользователя</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -44,8 +44,8 @@
 </ul>
 <span>
 «  <a href="index.html">Индексация</a> 
-::  <a href="contents.html" class="uplink">Содержание</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workshop-filetypes+attributes.html">Семинар</a>  »
+::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
@@ -156,8 +156,8 @@
 <div class="nav">
 <div class="inner"><span>
 «  <a href="index.html">Индексация</a> 
-::  <a href="contents.html" class="uplink">Содержание</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workshop-filetypes+attributes.html">Семинар</a>  »
+::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
@@ -23,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>Руководство пользователя</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,9 +42,9 @@
 <li><a href="../en/tracker.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="teammonitor.html">Team Monitor - диспетчер задач</a> 
+ «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">Содержание</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Дополнения для Tracker (Tracker add-ons)</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -195,9 +195,9 @@
 <div class="nav">
 <div class="inner"><span>
- «  <a href="teammonitor.html">Team Monitor - диспетчер задач</a> 
+ «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">Содержание</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Дополнения для Tracker (Tracker add-ons)</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -72,13 +72,13 @@
 </td></tr>
 <tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
 <tr><td colspan="5"><h3>Action menu</h3></td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries from the list that are not currently selected.</td></tr>
 <tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
 <tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
 <tr><td colspan="5"><h3>Settings menu</h3></td></tr>
 <tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line tool <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expressions" rel="nofollow">regular expressions</a>.</td></tr>
 <tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
 <tr><td colspan="5"><h3>History menu</h3></td></tr>
 <tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
@@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a
 	<tr><td><span class="menu">Spam/Genuine Estimate</span></td><td> </td>
 		<td>this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065.</td></tr>
 </table>
-<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
+<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
 <p>With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.</p>
 <h3>
@@ -122,7 +122,7 @@ A good way to cut down the number of search results.</p>
 <ul>
 <li><p>You could copy and paste the string into an email, forum or IRC for others to use or debug.</p></li>
 <li><p>You can use this method to construct a query in <span class="menu">Attribute</span> mode and then switch to <span class="menu">Formula</span> mode, to comfortably generate a search string to use for a query in Terminal or a script.</p></li>
-<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
+<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
 </ul>
 <h2>
@@ -41,7 +41,7 @@
 <span>
 «  <a href="teammonitor.html">Team Monitor</a> 
 ::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Tracker-tillägg</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -124,7 +124,7 @@ This type-ahead filtering is set in the <a href="#tracker-preferences.html">Trac
 <ul>
 <li><p><b>Resize Window</b> (<span class="key">ALT</span> <span class="key">Y</span>) - Resizes the window to its ideal size.</p></li>
 <li><p><b>Clean Up</b> (<span class="key">ALT</span> <span class="key">K</span>) - Aligns all icons to an invisible grid. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Clean Up All</span> which additionally sorts all icons alphabetically.</p></li>
-<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expression</a>.</p></li>
+<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expression</a>.</p></li>
 <li><p><b>Close</b> (<span class="key">ALT</span> <span class="key">W</span>) - Closes the window. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Close All</span> which closes every Tracker window.</p></li>
 <li><p><b>Close All in Workspace</b> (<span class="key">ALT</span> <span class="key">Q</span>) - Closes every Tracker window in the current workspace. A useful shortcut if you forgot to hold the <span class="key">OPT</span> key while clicking through folders and all those still open Tracker windows clutter your workspace.</p></li>
 </ul>
@@ -193,7 +193,7 @@ This type-ahead filtering is set in the <a href="#tracker-preferences.html">Trac
 <div class="inner"><span>
 «  <a href="teammonitor.html">Team Monitor</a> 
 ::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Tracker-tillägg</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -69,13 +69,13 @@
 </td></tr>
 <tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
 <tr><td colspan="5"><h3>Action menu</h3></td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries from the list that are not currently selected.</td></tr>
 <tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
 <tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
 <tr><td colspan="5"><h3>Settings menu</h3></td></tr>
 <tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line tool <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expressions" rel="nofollow">regular expressions</a>.</td></tr>
 <tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
 <tr><td colspan="5"><h3>History menu</h3></td></tr>
 <tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
@@ -41,7 +41,7 @@
 <span>
 «  <a href="deskbar.html">Deskbar</a> 
 ::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="filetypes.html">Типи файлів (FileTypes)</a>  »
+::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a
 	<tr><td><span class="menu">Spam/Genuine Estimate</span></td><td> </td>
 		<td>this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065.</td></tr>
 </table>
-<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
+<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
 <p>With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.</p>
 <h3>
@@ -181,7 +181,7 @@ If you're on a dial-up connection, you may want to do that <span class="menu">On
 <div class="inner"><span>
 «  <a href="deskbar.html">Deskbar</a> 
 ::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="filetypes.html">Типи файлів (FileTypes)</a>  »
+::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -122,7 +122,7 @@ A good way to cut down the number of search results.</p>
 <ul>
 <li><p>You could copy and paste the string into an email, forum or IRC for others to use or debug.</p></li>
 <li><p>You can use this method to construct a query in <span class="menu">Attribute</span> mode and then switch to <span class="menu">Formula</span> mode, to comfortably generate a search string to use for a query in Terminal or a script.</p></li>
-<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
+<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
 </ul>
 <h2>
@@ -124,7 +124,7 @@ This type-ahead filtering is set in the <a href="#tracker-preferences.html">Trac
 <ul>
 <li><p><b>Resize Window</b> (<span class="key">ALT</span> <span class="key">Y</span>) - Resizes the window to its ideal size.</p></li>
 <li><p><b>Clean Up</b> (<span class="key">ALT</span> <span class="key">K</span>) - Aligns all icons to an invisible grid. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Clean Up All</span> which additionally sorts all icons alphabetically.</p></li>
-<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expression</a>.</p></li>
+<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expression</a>.</p></li>
 <li><p><b>Close</b> (<span class="key">ALT</span> <span class="key">W</span>) - Closes the window. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Close All</span> which closes every Tracker window.</p></li>
 <li><p><b>Close All in Workspace</b> (<span class="key">ALT</span> <span class="key">Q</span>) - Closes every Tracker window in the current workspace. A useful shortcut if you forgot to hold the <span class="key">OPT</span> key while clicking through folders and all those still open Tracker windows clutter your workspace.</p></li>
 </ul>
@@ -16,13 +16,13 @@
 	<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>Installer（安装器）</title>
+	<title>安装器</title>
 	<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
 </head>
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,8 +42,8 @@
 </ul>
 <span>
 «  <a href="icon-o-matic.html">Icon-O-Matic</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
-::  <a href="magnify.html">Magnify</a>  »
+::  <a href="magnify.html">放大镜</a>  »
 </span></div>
 </div>
@@ -93,8 +93,8 @@ chainloader	+1</pre></li>
 <div class="nav">
 <div class="inner"><span>
 «  <a href="icon-o-matic.html">Icon-O-Matic</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
-::  <a href="magnify.html">Magnify</a>  »
+::  <a href="magnify.html">放大镜</a>  »
 </span></div>
 </div>
@@ -9,18 +9,20 @@
 *
 * Authors:
 *		Humdinger <humdingerb@gmail.com>
 * Translators:
 *		Pengphei Han
 *
 -->
 	<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>Magnify</title>
+	<title>放大镜</title>
 	<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
 </head>
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -40,16 +42,16 @@
 </ul>
 <span>
  «  <a href="icon-o-matic.html">Icon-O-Matic</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
-::  <a href="mail.html">电子邮箱</a>  »
+::  <a href="mail.html">Mail</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
-<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</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><img src="../../images/apps-images/magnify-icon_64.png" alt="magnify-icon_64.png" width="64" height="64" />Magnify</h2>
+<h2><img src="../../images/apps-images/magnify-icon_64.png" alt="magnify-icon_64.png" width="64" height="64" />放大镜</h2>
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
 <tr><td>桌面栏：</td><td style="width:15px;"></td><td><span class="menu">应用程序</span></td></tr>
 <tr><td>位置：</td><td></td><td><span class="path">/boot/system/apps/Magnify</span></td></tr>
@@ -57,29 +59,31 @@
 </td><td></td><td><span class="path">~/config/settings/Magnify_prefs</span></td></tr>
 </table>
 <p><br /></p>
-<p>Magnify shows an enlarged version of the area around your mouse pointer.</p>
+<p>放大镜对您的鼠标指针周围区域进行了放大显示。</p>
 <img src="../images/apps-images/magnify.png" alt="magnify.png" />
-<p>At the top you'll find the size and magnification level of the area. "<i>32 x 32 @ 8 pixels/pixel</i>" means that you look at a 32x32 pixel square around your mouse pointer and every pixel is enlarged by a factor of 8.</p>
+<p>在顶部，您可以找到该区域的尺寸和放大倍数。 "<i>32 x 32 @ 8 pixels/pixel</i>" 表示，您正在查看鼠标周围 32x32 的像素面积，而且每个像素都放大了8倍。</p>
-<p>Below that is the color of the pixel that's marked by a red outline. Its color is presented as RGB and hex value.<br />
+<p>下面是一个具有红色轮廓的的像素。它的颜色以RGB和十六进制值表示。<br />
-You can move the red outline with <span class="key">←</span> / <span class="key">→</span> / <span class="key">↑</span> / <span class="key">↓</span>.</p>
+您可以使用 <span class="key">←</span> / <span class="key">→</span> / <span class="key">↑</span> / <span class="key">↓</span> 移动红色的轮廓。</p>
-<p>To measure distances and align objects, you can add up to two blue crosshairs with <span class="key">ALT</span> <span class="key">H</span>. Their X/Y coordinates toward the top left corner and, if both are added, their X/Y distance from each other, are displayed at the bottom.<br />
+<p>为了量度距离和排列的对象，您可以使用 <span class="key">ALT</span> <span class="key">H</span> 添加两个蓝色的十字丝。它们的 X/Y 坐标趋向于左上角，如果添加了两个十字丝，它们的之间的 X/Y 距离显示于窗口的底部。
-They can also be moved with <span class="key">←</span> / <span class="key">→</span> / <span class="key">↑</span> / <span class="key">↓</span>. The active crosshair is marked with an "x".</p>
+
-<p>You can move the mouse pointer pixel by pixel with <span class="key">OPT</span> <span class="key">←</span> / <span class="key">→</span> / <span class="key">↑</span> / <span class="key">↓</span>.</p>
+<br />
-<p>Clicking on the pop-up menu gives you a number of options:</p>
+十字丝也可以通过 <span class="key">←</span> / <span class="key">→</span> / <span class="key">↑</span> / <span class="key">↓</span> 进行移动，而活动的十字丝则标记为 "x" 。</p>
 <p>您可以使用 <span class="key">OPT</span> <span class="key">←</span> / <span class="key">→</span> / <span class="key">↑</span> / <span class="key">↓</span> 控制鼠标指针，使指针以像素为单位移动。</p>
 <p>点击弹出菜单将会给出下面的选项：</p>
 <table summary="options" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="menu">Save Image</span></td><td><span class="key">ALT</span> <span class="key">S</span></td><td> </td><td>Saves the current display as a resource file.</td></tr>
+<tr><td><span class="menu">Save Image</span></td><td><span class="key">ALT</span> <span class="key">S</span></td><td> </td><td>保存当前显示图像为源文件。</td></tr>
-<tr><td><span class="menu">Copy Image</span></td><td><span class="key">ALT</span> <span class="key">C</span></td><td> </td><td>Copies the current display to the clipboard.</td></tr>
+<tr><td><span class="menu">Copy Image</span></td><td><span class="key">ALT</span> <span class="key">C</span></td><td> </td><td>复制当前显示到剪贴板。</td></tr>
-<tr><td><span class="menu">Hide/Show Info</span></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Toggles the display of all the additional information.</td></tr>
+<tr><td><span class="menu">Hide/Show Info</span></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>切换显示所有的附加信息。</td></tr>
-<tr><td><span class="menu">Add a Crosshair</span></td><td><span class="key">ALT</span> <span class="key">H</span></td><td> </td><td>Adds a crosshair you can drag around. </td></tr>
+<tr><td><span class="menu">Add a Crosshair</span></td><td><span class="key">ALT</span> <span class="key">H</span></td><td> </td><td>添加可以移动的十字丝。</td></tr>
-<tr><td><span class="menu">Remove a Crosshair</span></td><td><span class="key">ALT</span> <span class="key">SHIFT</span> <span class="key">H</span></td><td> </td><td>Removes the last added crosshair.</td></tr>
+<tr><td><span class="menu">Remove a Crosshair</span></td><td><span class="key">ALT</span> <span class="key">SHIFT</span> <span class="key">H</span></td><td> </td><td>删除最近添加的十字丝。</td></tr>
-<tr><td><span class="menu">Hide/Show Grid</span></td><td><span class="key">ALT</span> <span class="key">G</span></td><td> </td><td>Toggles the overlayed grid.</td></tr>
+<tr><td><span class="menu">Hide/Show Grid</span></td><td><span class="key">ALT</span> <span class="key">G</span></td><td> </td><td>在覆盖网格之间进行切换。</td></tr>
-<tr><td class="onelinetop"><span class="menu">Freeze/Unfreeze image</span></td><td><span class="key">ALT</span> <span class="key">F</span></td><td> </td><td>Stops/continues updating the magnification area.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Freeze/Unfreeze image</span></td><td><span class="key">ALT</span> <span class="key">F</span></td><td> </td><td>停止/继续更新放大区域。</td></tr>
-<tr><td><span class="menu">Stick Coordinates</span></td><td><span class="key">ALT</span> <span class="key">I</span></td><td> </td><td>Keeps updating the magnification area, but don't follow the mouse pointer any more.</td></tr>
+<tr><td><span class="menu">Stick Coordinates</span></td><td><span class="key">ALT</span> <span class="key">I</span></td><td> </td><td>持续更新放大区域，但是不再追踪鼠标指针。</td></tr>
 <tr><td><span class="menu">Make Square</span></td><td><span class="key">ALT</span> <span class="key">/</span></td><td> </td><td>Reverts back to a square display after resizing the window.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Decrease Window Size</span></td><td><span class="key">ALT</span> <span class="key">-</span></td><td> </td><td>Shrinks the magnified area around the mouse pointer.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Decrease Window Size</span></td><td><span class="key">ALT</span> <span class="key">-</span></td><td> </td><td>缩小鼠标指针周围放大区域的面积。</td></tr>
-<tr><td><span class="menu">Increase Window Size</span></td><td><span class="key">ALT</span> <span class="key">+</span></td><td> </td><td>Enlarges the magnified area around the mouse pointer.</td></tr>
+<tr><td><span class="menu">Increase Window Size</span></td><td><span class="key">ALT</span> <span class="key">+</span></td><td> </td><td>增加鼠标指针周围放大区域的面积。</td></tr>
-<tr><td><span class="menu">Decrease Pixel Size</span></td><td><span class="key">ALT</span> <span class="key">,</span></td><td> </td><td>Lowers magnification.</td></tr>
+<tr><td><span class="menu">Decrease Pixel Size</span></td><td><span class="key">ALT</span> <span class="key">,</span></td><td> </td><td>缩小放大倍数。</td></tr>
-<tr><td><span class="menu">Increase Pixel Size</span></td><td><span class="key">ALT</span> <span class="key">.</span></td><td> </td><td>Increases magnification.</td></tr>
+<tr><td><span class="menu">Increase Pixel Size</span></td><td><span class="key">ALT</span> <span class="key">.</span></td><td> </td><td>增加放大倍数。</td></tr>
 </table>
 </div>
@@ -88,8 +92,8 @@ They can also be moved with <span class="key">←</span> / <span class="key">→
 <div class="nav">
 <div class="inner"><span>
  «  <a href="icon-o-matic.html">Icon-O-Matic</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
-::  <a href="mail.html">电子邮箱</a>  »
+::  <a href="mail.html">Mail</a>  »
 </span></div>
 </div>
@@ -9,6 +9,8 @@
 *
 * Authors:
 *		Humdinger <humdingerb@gmail.com>
 * Translators:
 *		Pengphei Han
 *
 -->
 	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
@@ -20,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -40,14 +42,13 @@
 </ul>
 <span>
  «  <a href="bepdf.html">BePDF</a> 
-::  <a href="../applications.html#list-of-bundled-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-bundled-apps" class="uplink">Applications</a> 
-::  <a href="vision.html">Vision聊天客户端</a>  »
+::  <a href="vision.html">Vision</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
 <div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
 <h2><img src="../../images/apps-images/pe-icon_64.png" alt="pe-icon_64.png" width="64" height="64" />Pe</h2>
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
@@ -58,8 +59,8 @@
 </td><td></td><td><span class="path">~/config/settings/pe/*</span></td></tr>
 </table>
 <p><br /></p>
-<p>Pe is a sophisticated editor, with its syntax highlighting targeted mainly at programmers and HTML writers. Originally created by Maarten Hekkelmann, it's been open sourced and maintained by Haiku developers. A bugtracker and more information is available at the <a href="http://pe-editor.berlios.de/">Pe project page</a>.</p>
+<p>Pe 是一个复杂的编辑器，具有语法高亮度特性，适用于程序员和HTML编辑人员。它的原作者是 Maarten Hekkelmann，现在属于开源软件，由Haiku开发人员负责维护。有关错误跟踪和更多相关信息，可以参阅 <a href="http://pe-editor.berlios.de/">Pe 项目页面</a>。</p>
-<p>Find out more about Pe's features in its local <a href="file:///boot/apps/Pe/Documentation.html">documentation</a>.</p>
+<p>有关Pe的特性，可以参阅它的本地<a href="file:///boot/apps/Pe/Documentation.html">文档</a>。</p>
 </div>
 </div>
@@ -67,8 +68,8 @@
 <div class="nav">
 <div class="inner"><span>
  «  <a href="bepdf.html">BePDF</a> 
-::  <a href="../applications.html#list-of-bundled-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-bundled-apps" class="uplink">Applications</a> 
-::  <a href="vision.html">Vision聊天客户端</a>  »
+::  <a href="vision.html">Vision</a>  »
 </span></div>
 </div>
 -->
@@ -9,18 +9,20 @@
 *
 * Authors:
 *		Humdinger <humdingerb@gmail.com>
 * Translators:
 *		Pengphei Han
 *
 -->
 	<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>People</title>
+	<title>联系人</title>
 	<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
 </head>
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -39,17 +41,16 @@
 <li><a href="../../en/applications/people.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="packageinstaller.html">软件包安装器</a> 
+ «  <a href="packageinstaller.html">PackageInstaller</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
 ::  <a href="poorman.html">PoorMan</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
 <div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
-<h2><img src="../../images/apps-images/people-icon_64.png" alt="people-icon_64.png" width="64" height="64" />People</h2>
+<h2><img src="../../images/apps-images/people-icon_64.png" alt="people-icon_64.png" width="64" height="64" />联系人</h2>
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
 <tr><td>桌面栏：</td><td style="width:15px;"></td><td><span class="menu">应用程序</span></td></tr>
 <tr><td>位置：</td><td></td><td><span class="path">/boot/system/apps/People</span></td></tr>
@@ -57,25 +58,25 @@
 </td><td></td><td><span class="path">~/config/settings/People_data</span></td></tr>
 </table>
 <p><br /></p>
-<p>People is a simple contact database using the <a href="../attributes.html">attributes</a> of Haiku's filesystem to store addresses and other contact information. Every contact is saved as one Person file with its data in separate attributes. All are indexed and therefore searchable with a <a href="../queries.html">query</a>.</p>
+<p>“联系人”程序是一个小型的联系人数据库，它使用了Haiku文件系统中的<a href="../attributes.html">属性</a>存储地址和其他的联系人信息。所有的联系方式都保存为单个文件，而它的数据则保存在独立的属性中。联系人程序中的所有文件都做了索引，它们可以在 <a href="../queries.html">查询</a> 中进行搜索。</p>
 <img src="../images/apps-images/people.png" alt="people.png" />
-<p>The Group attribute at the bottom allows assigning a person to one or more groups. Useful for "mass mailing" a number of people who, for example, work on a specific project. The pop-up menu offers all currently existing groups. If a person belongs to more than one group, the group names are delimited with a "<tt>,</tt>".</p>
+<p>面板底部的 Group 属性用于将一个联系人添加到一个躲着多个群组。如果需要给从事于同一项目的多个人发送“群发邮件”，这项功能则将非常有用。弹出菜单提供了所有当前存在的群组。如果某个联系人属于多个群组，群组名之间以 "<tt>,</tt>" 分开。</p>
-<p>These Person files are usually all saved in <span class="path">/boot/home/people/</span>. To get a list of all your contacts, just open your people folder and display all attributes of interest. If you choose to organize your Person files in different folders, just use a query to display them all in one window. </p>
+<p>联系人记录文件通常保存在 <span class="path">/boot/home/people/</span> 。 为了显示所有的联系人列表，您只需要打开该文件夹，然后显示所有感兴趣的属性。如果您把联系人文件放置在不同的文件夹，您只需要使用一个查询将它们都显示在一个窗口。</p>
 <img src="../images/apps-images/people-files.png" alt="people-files.png" />
-<p>You can treat these files like any other: You can sort according to attributes (even a second sorting order by holding <span class="key">SHIFT</span> while clicking) and of course delete, duplicate or rename Person files. Even the contact information can be edited directly: Clicking on an attribute (or <span class="key">ALT</span> <span class="key">E</span>) to edit works just like renaming a file. Once you're in edit mode, <span class="key">TAB</span> and <span class="key">SHIFT</span> <span class="key">TAB</span> will jump from column to column.</p>
+<p>您可以如下处理这些文件：您可以依据属性对他们进行排序（在点击时，同时按下 <span class="key">SHIFT</span> 键进行二次排序），当然也可以删除，复制和重命名联系人文件。甚至联系人信息也可以直接进行编辑：点击一个属性（或者使用<span class="key">ALT</span> <span class="key">E</span>）来进行编辑工作，例如重命名文件。如果您进入了编辑模式，<span class="key">TAB</span> 和 <span class="key">SHIFT</span> <span class="key">TAB</span> 在行与行之间进行切换。</p>
 </div>
 </div>
 <div class="nav">
 <div class="inner"><span>
- «  <a href="packageinstaller.html">软件包安装器</a> 
+ «  <a href="packageinstaller.html">PackageInstaller</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
 ::  <a href="poorman.html">PoorMan</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,25 +41,25 @@
 <li><a href="../../en/applications/textsearch.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="terminal.html">终端</a> 
+ «  <a href="terminal.html">Terminal</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
-::  <a href="tv.html">虚拟电视</a>  »
+::  <a href="tv.html">TV</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
-<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</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><img src="../../images/apps-images/textsearch-icon_64.png" alt="textsearch-icon_64.png" width="64" height="64" />文本搜索</h2>
 <table summary="layout" border="0" cellspacing="0" cellpadding="2">
-<tr><td>桌面栏：</td><td style="width:15px;"></td><td><i>No entry, normally launched via Tracker Add-on</i></td></tr>
+<tr><td>桌面栏：</td><td style="width:15px;"></td><td><i>没有入口，通常通过Tracker的附加组进行启动</i></td></tr>
 <tr><td>位置：</td><td></td><td><span class="path">/boot/system/apps/TextSearch</span></td></tr>
 <tr><td>设置：
 </td><td></td><td><span class="path">~/config/settings/TextSearch</span></td></tr>
 </table>
 <p><br /></p>
-<p>TextSearch looks for a string in text files. Typically it is invoked from <a href="../tracker-add-ons.html">Tracker's Add-on</a> context menu on the selection of files or folders you want to search.</p>
+<p>文本搜索用于查询文本文件中的字符串。通常，它通过选中文件或者文件夹右键菜单的 <a href="../tracker-add-ons.html">Tracker附加组件</a> 实现启动。</p>
 <img src="../images/apps-images/textsearch.png" alt="textsearch.png" />
@@ -67,32 +67,32 @@
 <p>Only a few words on some of the otherwise self-explaining menu items:</p>
 <table summary="menus" border="0" cellpadding="2" cellspacing="0">
-<tr><td colspan="5"><h3>File menu</h3></td></tr>
+<tr><td colspan="5"><h3>File 菜单</h3></td></tr>
 <tr><td class="onelinetop"><span class="menu">New window</span></td><td></td><td><span class="key">ALT</span> <span class="key">N</span></td><td> </td><td>Opens a new window where you can enter another string and search through the same files/folders.
 </td></tr>
 <tr><td><span class="menu">Set target...</span></td><td></td><td><span class="key">ALT</span> <span class="key">F</span></td><td></td><td>Lets you choose a new set of files and folders to search through.</td></tr>
-<tr><td colspan="5"><h3>Action menu</h3></td></tr>
+<tr><td colspan="5"><h3>Action 菜单</h3></td></tr>
-<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries form the list that are not currently selected.</td></tr>
+<tr><td><span class="menu">Trim selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">T</span></td><td> </td><td>Removes all entries from the list that are not currently selected.</td></tr>
 <tr><td><span class="menu">Open selection</span></td><td></td><td><span class="key">ALT</span> <span class="key">O</span></td><td></td><td>Opens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.</td></tr>
 <tr><td><span class="menu">Open files in Tracker</span></td><td></td><td><span class="key">ALT</span> <span class="key">K</span></td><td></td><td>Opens the location of the currently selected files in Tracker.</td></tr>
-<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">C</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Copy text to clipboard</span></td><td></td><td><span class="key">ALT</span> <span class="key">B</span></td><td></td><td>Copies the current selection to the clipboard.</td></tr>
-<tr><td colspan="5"><h3>Settings menu</h3></td></tr>
+<tr><td colspan="5"><h3>Settings 菜单</h3></td></tr>
 <tr><td colspan="3" class="onelinetop"><span class="menu">Skip folders starting with a dot</span></td><td> </td><td>This is useful when working in a "unixy" environment, where often administrative files are hidden inside "<tt>.folders/</tt>". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.</td></tr>
-<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line command <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a>.</td></tr>
+<tr><td colspan="3"><span class="menu">Escape search text</span></td><td> </td><td>TextSearch uses the command line tool <span class="cli">grep</span>. For it, special characters like <tt>'"*\$?!</tt> and spaces have to be escaped with a <tt>\</tt>. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expressions" rel="nofollow">regular expressions</a>.</td></tr>
 <tr><td colspan="3"><span class="menu">Text files only</span></td><td> </td><td>TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.</td></tr>
-<tr><td colspan="5"><h3>History menu</h3></td></tr>
+<tr><td colspan="5"><h3>History 菜单</h3></td></tr>
-<tr><td colspan="4"></td><td>Contains recently used search strings.</td></tr>
+<tr><td colspan="4"></td><td>包含最近查询的字符。</td></tr>
-<tr><td colspan="5"><h3>Encoding menu</h3></td></tr>
+<tr><td colspan="5"><h3>Encoding 菜单</h3></td></tr>
-<tr><td colspan="4"></td><td>Lets you choose different character encodings if needed.</td></tr>
+<tr><td colspan="4"></td><td>根据需要选择不同的字符编码。</td></tr>
 </table>
 </div>
 </div>
 <div class="nav">
 <div class="inner"><span>
- «  <a href="terminal.html">终端</a> 
+ «  <a href="terminal.html">Terminal</a> 
-::  <a href="../applications.html#list-of-apps" class="uplink">应用程序</a> 
+::  <a href="../applications.html#list-of-apps" class="uplink">Applications</a> 
-::  <a href="tv.html">虚拟电视</a>  »
+::  <a href="tv.html">TV</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -121,9 +121,9 @@
 		<td>利用索引来实现属性的查找。</td></tr>
 	<tr><td valign="top"><a href="queries.html">查询</a><ul>
 		<li><a href="queries.html#find-window">查找窗口</a></li>
-		<li><a href="queries.html#basic-query">基本查询 - "利用文件名"</a></li>
+		<li><a href="queries.html#basic-query">基本查询 - "使用文件名"</a></li>
-		<li><a href="queries.html#adv-query">标准查询 - "利用属性"</a></li>
+		<li><a href="queries.html#adv-query">标准查询 - "使用属性"</a></li>
-		<li><a href="queries.html#more-adv-query">高级查询 - "利用表达式</a></li>
+		<li><a href="queries.html#more-adv-query">高级查询 - "使用表达式</a></li>
 		<li><a href="queries.html#result-window">结果窗口</a></li>
 		<li><a href="queries.html#query-template">查询模板</a></li>
 </ul></td>
@@ -16,13 +16,13 @@
 	<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>LaunchBox</title>
+	<title>快速启动</title>
 	<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
 </head>
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,29 +41,28 @@
 <li><a href="../../en/desktop-applets/launchbox.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
-    <a href="../desktop-applets.html" class="uplink">桌面小程序</a> 
+    <a href="../desktop-applets.html" class="uplink">Desktop Applets</a> 
-::  <a href="networkstatus.html">网络状态</a>  »
+::  <a href="networkstatus.html">NetworkStatus</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
 <div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
-<h2><img src="../../images/desktop-applets-images/launchbox-icon_64.png" alt="launchbox-icon_64.png" width="64" height="64" />LaunchBox</h2>
+<h2><img src="../../images/desktop-applets-images/launchbox-icon_64.png" alt="launchbox-icon_64.png" width="64" height="64" />快速启动</h2>
 <table summary="quickinfo" border="0" cellspacing="0" cellpadding="2">
 <tr><td>桌面栏：</td><td style="width:15px;"></td><td><span class="menu">桌面小程序</span></td></tr>
 <tr><td>位置：</td><td></td><td><span class="path">/boot/system/apps/LaunchBox</span></td></tr>
 <tr><td>设置：
 </td><td></td><td><span class="path">~/config/settings/LaunchBox/*</span></td></tr>
 </table>
-<p>One or more LaunchBox applets can be started to organize shortcuts to your favorite applications or documents. You decide if each is shown on all or just the current workspace. They can also serve to quickly open a document in a specific application. For example, you could drag&amp;drop a HTML file onto a text editor in a LaunchBox to open it in the editor instead of its preferred application, the browser.</p>
+<p>你可以启动一个或者多个快速启动小程序，然后使用它们来组织您的收藏程序和文档的快捷方式。您可以决定是否显示所有工作区或者当前工作区的快捷方式。它们也可以用于快速的在某个程序中打开文档。 例如，您可以拖拽一个HTML文件到快速启动栏中的文本编辑器中，然后通过该编辑器打开它，而不是它的首选程序，浏览器。</p>
 <img src="../images/desktop-applets-images/launchbox.png" alt="launchbox.png" />
-<p>All options are reached from the context menu:</p>
+<p>所有的选项都可以从右键菜单中进行设置：</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="menu">Add Button Here</span></td><td style="width:10px;"> </td><td>Adds an empty button.</td></tr>
+<tr><td><span class="menu">Add Button Here</span></td><td style="width:10px;"> </td><td>添加一个空按钮。</td></tr>
-<tr><td><span class="menu">Clear Button</span></td><td> </td><td>Empties a button.</td></tr>
+<tr><td><span class="menu">Clear Button</span></td><td> </td><td>清空一个按钮。</td></tr>
-<tr><td><span class="menu">Remove Button</span></td><td> </td><td>Removes a button.</td></tr>
+<tr><td><span class="menu">Remove Button</span></td><td> </td><td>删除一个按钮。</td></tr>
 <tr><td class="onelinetop"><span class="menu">Settings</span><br />
 <span class="menu">- Horizontal Layout</span><br />
 <span class="menu">- Icon size</span><br />
@@ -71,24 +70,32 @@
 <span class="menu">- Show Window Border</span><br />
 <span class="menu">- Auto Raise</span><br />
 <span class="menu">- Show On All Workspaces</span></td><td> </td><td class="onelinetop"><br />
-Aligns the buttons horizontally.<br />
+横向排列程序按钮。
-Sets the icon size between 16 and 64 pixel.<br />
+<br />
-Launches the object only once, even when you (accidentally) double-click.<br />
+设置图标尺寸，从16像素到64像素。
-Shows the window border.<br />
+<br />
-LaunchBox pops up if the mouse is near the screen edge.<br />
+忽略双击，点击对象只启动一次。
-Shows the LaunchBox on every workspace.</td></tr>
+<br />
 显示窗口边缘。
 <br />
 鼠标靠近屏幕边缘时，弹出快速启动。
 <br />
 在所有工作区中显示快速启动。</td></tr>
 <tr><td><span class="menu">Pad</span><br />
 <span class="menu">- New</span><br />
 <span class="menu">- Clone</span><br />
 <span class="menu">- Close</span></td><td> </td><td><br />
-Add a new pad.<br />
+新建一个快速启动面板。
-Duplicate the current pad.<br />
+<br />
-Close the current pad.</td></tr>
+复制当前快速启动面板。
 <br />
 关闭当前快速启动面板。</td></tr>
 <tr><td><span class="menu">LaunchBox</span><br />
 <span class="menu">- About...</span><br />
 <span class="menu">- Quit</span></td><td> </td><td><br />
-Shows the About window.<br />
+显示简介窗口。
-Quits all LaunchBox pads.</td><td> </td></tr>
+<br />
 退出快速启动</td><td> </td></tr>
 </table>
 </div>
@@ -96,8 +103,8 @@ Quits all LaunchBox pads.</td><td> </td></tr>
 <div class="nav">
 <div class="inner"><span>
-    <a href="../desktop-applets.html" class="uplink">桌面小程序</a> 
+    <a href="../desktop-applets.html" class="uplink">Desktop Applets</a> 
-::  <a href="networkstatus.html">网络状态</a>  »
+::  <a href="networkstatus.html">NetworkStatus</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,15 +41,14 @@
 <li><a href="../en/filetypes.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="deskbar.html">桌面栏</a> 
+ «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="attributes.html">Attributes（属性）</a>  »
+::  <a href="attributes.html">Attributes</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
 <div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
 <h1>文件类型</h1>
@@ -57,8 +56,8 @@
 <div class="box-info">由于在Haiku中没有必要使用文件扩展，但是您需要注意的是，当您和其他系统的用户分享文件时，您需要添加上扩展名，例如，通过邮件，上传到服务器或者交换闪盘。否则，他们的系统将无法识别出文件类型。</div>
 <h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="specific-file" name="specific-file">设置特定文件的文件类型</a></h2>
+<a id="specific-file" name="specific-file">文件类型设置</a></h2>
-<p>您可以修改特定文件的类型，它的图标，以及相关联的程序。选择该文件，然后从右键菜单中调用 <span class="menu">Add-Ons | Filetype add-on</span> 。</p>
+<p>您可以修改单个文件的类型，图标，以及相关联的程序。选择该文件，然后从右键菜单中调用 <span class="menu">Add-Ons | Filetype add-on</span> 。</p>
 <img src="images/filetypes-images/filetype-addon.png" alt="filetype-addon.png" />
 <h3>
@@ -73,47 +72,47 @@
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="preferred-app" name="preferred-app">首选应用程序</a></h3>
-<p>This pop-up menu shows a list of all applications that can handle this particular filetype. From here you can choose which program should open this specific file when it's double-clicked. You could, for example, change a HTML file's preferred application from the browser to a text editor while you're working on it. Every other HTML file still opens in the browser, only this particular one starts in your text editor.</p>
+<p>弹出菜单中显示了一个可以处理该特定类型文件的所有程序的列表。您可以选择某个程序，当双击打该类型文件时，该程序将会自动启动。例如，您可以将一个HTML文件的首选程序修改为您正在使用的文本编辑器。那么所有其他的HTML文件仍会在浏览器中打开，仅该文件在您的文本编辑器中打开。</p>
-<p>The <span class="menu">Default Application</span> is the one that's set globally for that filetype. If you don't find the program you want to associate with this file in the pop-up menu, you'll again find the buttons <span class="button">Select...</span> and <span class="button">Same As...</span> which do the similar thing described under "The File Type" above.</p>
+<p><span class="menu">Default Application</span> 是用于全局设置的文件类型首选程序。如果您在弹出菜单中没有找出关联到该文件的程序，您会再次找到 <span class="button">Select...</span> 和 <span class="button">Same As...</span> 按钮，它们两个具有类似于“文件类型”下描述的功能。</p>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="icon" name="icon">图标</a></h3>
+<a id="icon" name="icon">图标设置</a></h3>
-<p>If you're wondering why the icon well on the top right is empty: Icons are normally inherited from the system default for that filetype. You can open the <span class="app">Filetype Add-On</span> of a file that contains an icon and drag&amp;drop it into your file's icon well. Or you double-click the icon well and create or edit your own icon. For more info on icons and how to create your own, see topic <a href="applications/icon-o-matic.html">Icon-O-Matic</a>.</p>
+<p>如果您对左上角的图标为空产生疑问：图标通常从系统为文件类型默认的图标中继承而来。您可以打开一个带有图标文件的 <span class="app">Filetype Add-On</span>，然后将它的图标拖拽到您的文件的图标栏中。或者您可以双击图标，然后创建和F编辑自己的图标。更多有关图标的信息和如何创建图标，您可以参阅 <a href="applications/icon-o-matic.html">Icon-O-Matic</a> 主题。</p>
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="settings-apps" name="settings-apps">应用程序的特殊设置</a></h2>
+<a id="settings-apps" name="settings-apps">程序的特殊设置</a></h2>
-<p>If you invoke the <span class="app">Filetype Add-On</span> on an executable (here: <span class="app">StyledEdit</span>), you'll get a different dialog:</p>
+<p>如果您调用可执行文件的 <span class="app">Filetype Add-On</span> （此处使用的是 <span class="app">StyledEdit</span>），您会打开一个不同的对话框：</p>
 <img src="images/filetypes-images/filetype-addon-stylededit.png" alt="filetype-addon-stylededit.png" />
-<p>On top, you'll see, instead of a standardized MIME string, the unique application signature. With it, the system finds the program wherever it's installed.</p>
+<p>在顶部，您可以看到，它不是一个标准的MIME字符串，而是唯一的程序署名。通过它，操作系统可以找出程序的安装位置。</p>
-<p>Below it are several flags, controlling the app's behaviour:</p>
+<p>在它的下面，是用于控制程序的行为的标记：</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="menu">Single Launch</span></td><td> </td><td>Only one instance of the app can be running per executable file. If you have two copies of that app, however, they can run side by side.</td></tr>
+<tr><td><span class="menu">Single Launch</span></td><td> </td><td>对于每个可执行文件，仅有其中一个实例可以运行。如果您拥有两份该程序，它们可以依次运行。</td></tr>
-<tr><td><span class="menu">Multiple Launch</span></td><td> </td><td>Many instances of the app can run simultaneously.</td></tr>
+<tr><td><span class="menu">Multiple Launch</span></td><td> </td><td>程序的许多实例可以同步运行。</td></tr>
-<tr><td class="onelinetop"><span class="menu">Exclusive Launch</span></td><td> </td><td>Really only one instance with that app's signature is allowed to run at a time.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Exclusive Launch</span></td><td> </td><td>每次只允许具有该程序的署名的一个实例运行。</td></tr>
-<tr><td><span class="menu">Args Only</span></td><td> </td><td>Indicates the app doesn't respond to messages.</td></tr>
+<tr><td><span class="menu">Args Only</span></td><td> </td><td>指出该程序对于调用消息不作出响应。</td></tr>
-<tr><td><span class="menu">Background App</span></td><td> </td><td>The app won't appear in <a href="twitcher.html">Twitcher</a> or the list of running apps of the Deskbar.</td></tr>
+<tr><td><span class="menu">Background App</span></td><td> </td><td>该程序不出现在 <a href="twitcher.html">任务切换器</a> 或者桌面栏的运行程序列表中。</td></tr>
 </table>
-<p>Then there's the list of supported filetypes. You can add (and remove) filetypes if you think the application can handle them. As a consequence, the app will appear in the menu for preferred applications or Tracker's <span class="menu">Open with...</span> context menu when you right-click on a file of that type.</p>
+<p>然后，有一个支持文件类型的列表。如果您认为该程序可以处理此文件类型，您可以在这里进行添加或者删除。结果是，当您右键点击一个该类型的文件时，该程序将会出现在首选程序菜单，或者 Tracker 的  <span class="menu">Open with...</span> 右键菜单中。</p>
-<p>At the bottom are version and copyright information. Like the application signature, they are filled in by the app's author and shouldn't be altered.</p>
+<p>在底部是程序的版本和授权信息。它们同程序的署名相类似，其中写入了程序创建者的名字，而且这些名字是不可更改的。</p>
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="filetypes-preferences" name="filetypes-preferences">Global settings with the FileTypes Preferences</a></h2>
+<a id="filetypes-preferences" name="filetypes-preferences">全局设置</a></h2>
-<p>The <span class="app">FileTypes</span> preferences don't deal with individual files but with global settings of filetypes. You can change default icons and preferred applications or add, remove, or alter attributes of whole filetypes. You can even create your own filetype from scratch.</p>
+<p><span class="app">文件类型</span> 首选项不用于处理单个文件，而是文件类型的全局设置。您可以修改所有文件类型的默认图标，首选程序，或者添加，删除，和修改属性。您甚至可以从头开始创建自己的文件类型。</p>
-<p>All filetypes and their configurations are stored in <span class="path">/boot/home/config/settings/beos_mime/</span>. Before you start experimenting, it may be prudent to make a backup of that folder...</p>
+<p>所有的文件类型和它们的配置文件保存在 <span class="path">/boot/home/config/settings/beos_mime/</span> 。在您开始尝试作出改动之前，您最好对该文件夹做个备份以防出错。</p>
-<p>To learn more about the <span class="app">FileTypes</span> preferences see the workshop: <a href="workshop-filetypes+attributes.html">Filetypes, Attributes, Index and Queries</a>.</p>
+<p>了解更多有关 <span class="app">文件类型</span> 首选项的信息，可以参阅<a href="workshop-filetypes+attributes.html">操作练习：文件类型，属性，索引和查询</a>。</p>
 </div>
 </div>
 <div class="nav">
 <div class="inner"><span>
- «  <a href="deskbar.html">桌面栏</a> 
+ «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="attributes.html">Attributes（属性）</a>  »
+::  <a href="attributes.html">Attributes</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,15 +41,15 @@
 <li><a href="../en/gui.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="filesystem-layout.html">文件系统布局</a> 
+ «  <a href="filesystem-layout.html">Filesystem layout</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workspaces.html">Workspaces（工作区）</a>  »
+::  <a href="workspaces.html">Workspaces</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
-<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
+<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
 <h1>Haiku的图形用户界面</h1>
@@ -61,7 +61,7 @@
 <li><p>桌面栏可以看做是Haiku的"开始"菜单和任务栏（如果您愿意这样认为的话），详情参阅<a href="deskbar.html">桌面栏</a>主题。</p></li>
 <li>黄色的标签不仅仅提供了程序名或者文档的文件名：
 <ul><li>在拖动窗口时，您可以同时按下 <span class="key">SHIFT</span> 键来移动标签，这样您可以将许多窗口进行叠加，而只需要点击标签即可方便的进行访问。</li>
-<li>双击标签可以最小化窗口（或者使用 <span class="key">CTRL</span> <span class="key">ALT</span> <span class="key">M</span> 组合键）。通过这种方式隐藏的窗口可以通过 <a href="deskbar.html">桌面栏</a> 或者 <a href="twitcher.html">Twitcher</a> 进行访问。</li>
+<li>双击标签可以最小化窗口（或者使用 <span class="key">CTRL</span> <span class="key">ALT</span> <span class="key">M</span> 组合键）。通过这种方式隐藏的窗口可以通过 <a href="deskbar.html">桌面栏</a> 或者 <a href="twitcher.html">任务切换器</a> 进行访问。</li>
 <li>您可以通过右键点击标签（或者窗口边界）来置后窗口。</li></ul></li>
 <li><p>关闭按钮</p></li>
 <li><p>“缩放”按钮（也可以通过<span class="key">CTRL</span> <span class="key">ALT</span> <span class="key">Z</span> 组合键进行缩放）。对于大多数的程序，该按钮将会把窗口最大化。但并不是都如此，例如Tracker窗口，该按钮将会依据其内容将窗口放大至合适大小。</p></li>
@@ -72,32 +72,32 @@
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="open-save-panel" name="open-save-panel">打开和保存面板</a></h2>
-<p>从任意的程序打开或保存文件都将会打开类似于下面的面板：</p>
+<p>从任意的程序打开或保存文件都将会打开类似于如下所示的面板：</p>
 <img src="images/gui-images/open-save.png" alt="open-save.png" />
-<p>It has all the usual things: A list of files of the current folder to choose from, in case of a save panel, a text field to enter a filename and a pop-up menu for different file formats and their settings.<br />
+<p>它具有所有常用的东西：当前文件夹下可选的文件列表，用于输入文件名的文本框，用于不同文件格式的弹出菜单，以及有关的设置。<br />
-You can enter parent folders with the pop-up menu above the file listing.</p>
+您可以使用文件列表上面的弹出菜单进入上层文件夹。</p>
-<p>If you already have a Tracker window with the location for a file open, you can simply drag either any file or the folder-representation (i.e. the symbol to the far right in its menu bar) into the panel. This changes the panel to that new location.</p>
+<p>如果您已经拥有一个Tracker窗口用于打开文件，您可以将任何的文件或者代表的文件夹（例如，在菜单栏最右边的标志）拖拽到该面板。然后，它将会修改面板指向新的位置。</p>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="open-save-shortcuts" name="open-save-shortcuts">快捷键</a></h3>
-<p>Many shortcuts in open and save panels are the same used in Tracker. Besides the commands that are also available through the <span class="menu">File</span> menu, there are a few not that obvious:</p>
+<p>在打开和保存面板中的许多快捷键和在Tracker中使用的相同。除了在 <span class="menu">File</span> 菜单中也可用的命令之外，还有些不是很明显的命令：</p>
 <table summary="shortcuts" border="0" cellspacing="0" cellpadding="2">
-<tr><td><span class="key">ALT</span> <span class="key">N</span></td><td></td><td> Creates a new folder.</td></tr>
+<tr><td><span class="key">ALT</span> <span class="key">N</span></td><td></td><td>新建一个文件夹。</td></tr>
-<tr><td><span class="key">ALT</span> <span class="key">E</span></td><td></td><td> Lets you rename the selected entry.</td></tr>
+<tr><td><span class="key">ALT</span> <span class="key">E</span></td><td></td><td>重命名选中的文件。</td></tr>
-<tr><td><span class="key">ALT</span> <span class="key">↑</span></td><td style="width:24px;"></td><td> Moves into the parent folder.</td></tr>
+<tr><td><span class="key">ALT</span> <span class="key">↑</span></td><td style="width:24px;"></td><td>移动到上层文件夹。</td></tr>
-<tr><td class="onelinetop"><span class="key">ALT</span> <span class="key">↓</span> or <span class="key">ENTER</span></td><td></td><td> Moves into the selected folder.</td></tr>
+<tr><td class="onelinetop"><span class="key">ALT</span> <span class="key">↓</span> or <span class="key">ENTER</span></td><td></td><td>进入选中的文件夹。</td></tr>
-<tr><td><span class="key">ALT</span> <span class="key">D</span></td><td></td><td> Takes you to your Desktop.</td></tr>
+<tr><td><span class="key">ALT</span> <span class="key">D</span></td><td></td><td>返回桌面。</td></tr>
-<tr><td><span class="key">ALT</span> <span class="key">H</span></td><td></td><td> Takes you to your Home folder.</td></tr>
+<tr><td><span class="key">ALT</span> <span class="key">H</span></td><td></td><td>返回home文件夹。</td></tr>
 </table>
 <h3>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="favorites-recent" name="favorites-recent">收藏夹和最近的文件夹</a></h3>
-<p>The <span class="menu">Favorites</span> menu in open and save panels provides recently visited folders and favorite locations that you can set up yourself. As indicated by the little arrow, you can also use these locations to navigate further down the hierarchy via submenus.</p>
+<p>在打开和保存面板中的 <span class="menu">收藏夹</span> 菜单提供了您可以自主设置的最近访问文件夹和收藏夹的位置。根据小箭头的指示，您也可以使用这些位置通过子菜单导航至下面的文件层次。</p>
 <img src="images/gui-images/favorites.png" alt="favorites.png" />
-<p>To add a Favorite, you simply navigate to your destination and choose <span class="menu">Favorites | Add Current Folder</span>. From now on it will appear in every open/save panel. To remove a Favorite, choose <span class="menu">Favorites | Configure Favorites...</span> and delete its entry.<br />
+<p>为了添加收藏项目，您可以导航至目标，然后选择 <span class="menu">Favorites | Add Current Folder</span> 。那么之后，它将会出现在每个打开/保存面板。为了删除收藏项目，选择 <span class="menu">Favorites | Configure Favorites...</span> ，然后在其中删除该入口。<br />
-All Favorites are kept in <span class="path">/boot/home/config/settings/Tracker/Go/</span>. So you might as well add and remove links to files and folders there directly.</p>
+所有的收藏项目保存在 <span class="path">/boot/home/config/settings/Tracker/Go/</span>。所以您可以直接在那里添加或者删除相关的文件和文件夹的链接。</p>
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -113,9 +113,9 @@ A right-click on a Replicant handle offers a context menu to show the originatin
 <div class="nav">
 <div class="inner"><span>
- «  <a href="filesystem-layout.html">文件系统布局</a> 
+ «  <a href="filesystem-layout.html">Filesystem layout</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workspaces.html">Workspaces（工作区）</a>  »
+::  <a href="workspaces.html">Workspaces</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,9 +41,9 @@
 <li><a href="../en/keyboard-shortcuts.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="tracker-add-ons.html">Tracker 附加组件</a> 
+ «  <a href="tracker-add-ons.html">Tracker Add-Ons</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="deskbar.html">桌面栏</a>  »
+::  <a href="deskbar.html">Deskbar</a>  »
 </span></div>
 </div>
@@ -129,9 +129,9 @@
 <div class="nav">
 <div class="inner"><span>
- «  <a href="tracker-add-ons.html">Tracker 附加组件</a> 
+ «  <a href="tracker-add-ons.html">Tracker Add-Ons</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="deskbar.html">桌面栏</a>  »
+::  <a href="deskbar.html">Deskbar</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,8 +41,8 @@
 <li><a href="../../en/preferences/appearance.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
-    <a href="../preferences.html" class="uplink">首选项</a> 
+    <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="backgrounds.html">背景</a>  »
+::  <a href="backgrounds.html">Backgrounds</a>  »
 </span></div>
 </div>
@@ -99,7 +99,7 @@ Glyph hinting</h3>
 <p><br /></p>
 <p>在本面板底部有两个按钮：</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复所有设置为默认状态。</td></tr>
+<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复到系统默认的设置状态。</td></tr>
 <tr><td><span class="button">Revert</span></td><td> </td><td>取消设置，恢复到打开外观首选项前的设置状态。</td></tr>
 </table>
@@ -108,8 +108,8 @@ Glyph hinting</h3>
 <div class="nav">
 <div class="inner"><span>
-    <a href="../preferences.html" class="uplink">首选项</a> 
+    <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="backgrounds.html">背景</a>  »
+::  <a href="backgrounds.html">Backgrounds</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,15 +41,14 @@
 <li><a href="../../en/preferences/datatranslations.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="backgrounds.html">背景</a> 
+ «  <a href="backgrounds.html">Backgrounds</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="deskbar.html">桌面栏</a>  »
+::  <a href="deskbar.html">Deskbar</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
 <div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
 <h2><img src="../../images/prefs-images/datatranslations-icon_64.png" alt="datatranslations-icon_64.png" width="64" height="64" />数据转换</h2>
 <table summary="quickinfo" border="0" cellspacing="0" cellpadding="2">
@@ -59,43 +58,47 @@
 </td><td></td><td><span class="path">~/config/settings/*</span> - 在改变默认设置之后，每个解析器都将创建它自己的设置文件。<br />
 <span class="path">~/config/settings/system/DataTranslations settings</span> - 保存了面板的窗口位置。</td></tr>
 </table>
-<p>Every application has the ability to open and save every file format for which there's a Translator installed. The settings for these Translators are configured in the DataTranslations preferences.</p>
+<p>每个程序都可以打开和保存任何安装了转换器的文件格式。而有关这些转换器的设置可以在数据转换首选项中进行配置。</p>
 <p><br /></p>
 <img src="../images/prefs-images/datatranslations.png" alt="datatranslations.png" />
-<p>Depending on its capabilities, each Translator offers different settings. At least you'll get an <span class="button">Info...</span> button that opens a window with the credits and the installation path.<br />
+<p>根据各自功能的不同，每个转换器具有不同的设置。 但是至少您可以使用 <span class="button">Info...</span> 按钮打开一个显示致谢名单和安装路径的窗口。<br />
-The following table gives an overview of the default Translators and their most useful options.</p>
+下面的表格给出了默认转换器的概况和他们最常用的选项。</p>
 <table summary="translators" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="menu">BMP Images</span></td><td>24bit, uncompressed, no transparency</td></tr>
+<tr><td><span class="menu">BMP Images</span></td><td>24位，未压缩格式，无透明效果</td></tr>
-<tr><td><span class="menu">EXR Images</span></td><td><acronym title="Industrial Light &amp; Magic">ILM</acronym>'s high dynamic-range (HDR) format</td></tr>
+<tr><td><span class="menu">EXR Images</span></td><td><acronym title="Industrial Light &amp; Magic">ILM</acronym>的高动态范围图像格式（HDR）</td></tr>
-<tr><td><span class="menu">GIF Images</span></td><td>8bit, lossless compression, transparency<br />
+<tr><td><span class="menu">GIF Images</span></td><td>8位，无损压缩，透明效果
-You can reduce the filesize by limiting the number of used colors and the palette.<br />
+<br />
-You can write images with transparency, either by automatically using the alpha channel or by setting the RGB value that will be transparent by hand.</td></tr>
+您可以通过限制使用颜色和调色板的数量来减小文件大小。
-<tr><td><span class="menu">JPEG2000 Images</span></td><td>24bit, compressed, no transparency<br />
+<br />
-Here, you normally only care about the output quality.</td></tr>
+通过使用自动的alpha频道，或者设置三种原色的值，您可以使用透明效果来处理图片。</td></tr>
-<tr><td><span class="menu">JPEG Images</span></td><td>24bit, compressed, no transparency<br />
+<tr><td><span class="menu">JPEG2000 Images</span></td><td>24位，压缩格式，无透明效果
-Besides the output quality you can also set a smoothing that will lessen compression artefacts but can blur the picture a little.</td></tr>
+<br />
-<tr><td><span class="menu">PCX Images</span></td><td>24bit, uncompressed, no transparency, PC Paintbrush Exchange format</td></tr>
+在这里，通常您只关心图像的输出效果。</td></tr>
-<tr><td><span class="menu">PNG Images</span></td><td>32bit, lossless compression, transparency</td></tr>
+<tr><td><span class="menu">JPEG Images</span></td><td>24位，压缩格式，无透明效果
-<tr><td><span class="menu">PPM Images</span></td><td>24bit, uncompressed, no transparency, Portable PixMap format</td></tr>
+<br />
-<tr><td><span class="menu">RAW Images</span></td><td>up to 48bit, uncompressed, no transparency</td></tr>
+除了输出质量，您也可以设置平滑处理，从而减轻压缩伪像，但是这将会是图像变得模糊。</td></tr>
 <tr><td><span class="menu">PCX Images</span></td><td>24位，未压缩格式，无透明效果，PC画笔交换格式</td></tr>
 <tr><td><span class="menu">PNG Images</span></td><td>32位，无损压缩，透明效果</td></tr>
 <tr><td><span class="menu">PPM Images</span></td><td>24位，未压缩，无透明效果，便携式位图格式</td></tr>
 <tr><td><span class="menu">RAW Images</span></td><td>48位，未压缩格式，无透明效果</td></tr>
 <tr><td><span class="menu">RTF Text Files</span></td><td>格式化文本</td></tr>
-<tr><td><span class="menu">SGI Images</span></td><td>24bit, optional lossless compression, transparency</td></tr>
+<tr><td><span class="menu">SGI Images</span></td><td>24位，可选无损压缩，透明效果</td></tr>
 <tr><td><span class="menu">StyledEdit Files</span></td><td>格式化文本</td></tr>
-<tr><td><span class="menu">TGA Images</span></td><td>32bit, optional lossless compression, transparency</td></tr>
+<tr><td><span class="menu">TGA Images</span></td><td>32位，可选无损压缩，透明效果</td></tr>
-<tr><td><span class="menu">TIFF Images</span></td><td>24bit, optional lossless compression, layers, transparency</td></tr>
+<tr><td><span class="menu">TIFF Images</span></td><td>24位，可选无损压缩，具有图层，透明效果</td></tr>
-<tr><td class="onelinetop"><span class="menu">WonderBrush Images</span></td><td>32bit, layers, transparency, vector/pixel data</td></tr>
+<tr><td class="onelinetop"><span class="menu">WonderBrush Images</span></td><td>32位，具有图层，透明效果，位图/矢量数据</td></tr>
 </table>
 <p><br /></p>
-<div class="box-info">Screenshots, charts, black&amp;white drawings and other images with few used colors, as well as small pictures are best saved as GIF (up to 256 colors) or PNG (millions of colors). JPEG, for example, introduces compression artefacts without gain in smaller filesize.</div>
+<div class="box-info">屏幕截图，图表，黑白图纸，以及其他使用颜色很少图像，包括小图片，最好将它们保存为GIF（256色）或者PNG（上万种颜色）格式。例如，JPEG格式，引入了压缩伪像，但是没有增加文件大小。</div>
 </div>
 </div>
 <div class="nav">
 <div class="inner"><span>
- «  <a href="backgrounds.html">背景</a> 
+ «  <a href="backgrounds.html">Backgrounds</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="deskbar.html">桌面栏</a>  »
+::  <a href="deskbar.html">Deskbar</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,15 +41,15 @@
 <li><a href="../../en/preferences/e-mail.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="deskbar.html">桌面栏</a> 
+ «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="filetypes.html">文件类型</a>  »
+::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
-<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</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>索引</td></tr>
@@ -75,10 +75,10 @@ The configuration is done in the E-Mail preference panel.</p>
 <h2>
 <a href="#"><img src="../../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="creating" name="creating">新建邮箱账户</a></h2>
-<p>Let's go through the process of setting up an e-mail account.<br />
+<p>让我们开始了解有关邮箱账户的设置过程。<br />
-You start by clicking the <span class="button">Add</span> button to create a new, unnamed account. This opens a panel where you fill in your account info:</p>
+您可以点击 <span class="button">Add</span> 按钮新建一个未命名账户。它将会打开一个用于填写有关您的账户信息的面板：</p>
 <img src="../images/prefs-images/e-mail-new-account.png" alt="e-mail-new-account.png" />
-<p>First, declare the <i>Account Type</i> which is either <span class="menu">Receive Mail Only</span>, <span class="menu">Send Mail Only</span>, or the most usual type, <span class="menu">Send and Receive Mail</span>. Then you set how you get your mail, via <span class="menu">POP3</span> or <span class="menu">IMAP</span>.</p>
+<p>首先， declare the <i>Account Type</i> which is either <span class="menu">Receive Mail Only</span>, <span class="menu">Send Mail Only</span>, or the most usual type, <span class="menu">Send and Receive Mail</span>. Then you set how you get your mail, via <span class="menu">POP3</span> or <span class="menu">IMAP</span>.</p>
 <p>Now you enter your <i>E-mail Address</i>, <i>Login Name</i> and <i>Password</i>, give an <i>Account Name</i> under which it will be known under Haiku and your <i>Real Name</i>.</p>
 <p>If your account is from a major e-mail provider, Haiku already knows all technical details like server IP addresses and the following information is already filled in automatically. If that is not the case, just follow this guide and fill in the details to your e-mail account accordingly.</p>
@@ -154,7 +154,7 @@ With the first text field you specify which header to check against. These are a
 	<tr><td><span class="menu">Spam/Genuine Estimate</span></td><td> </td>
 		<td>this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065.</td></tr>
 </table>
-<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
+<p>The second text field holds your search pattern. It accepts <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression" rel="nofollow">regular expressions</a> which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't <i>that</i> complicated at all.</p>
 <p>With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.</p>
 <h3>
@@ -182,9 +182,9 @@ If you're on a dial-up connection, you may want to do that <span class="menu">On
 <div class="nav">
 <div class="inner"><span>
- «  <a href="deskbar.html">桌面栏</a> 
+ «  <a href="deskbar.html">Deskbar</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="filetypes.html">文件类型</a>  »
+::  <a href="filetypes.html">FileTypes</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,8 +41,8 @@
 <li><a href="../../en/preferences/fonts.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="filetypes.html">文件类型</a> 
+ «  <a href="filetypes.html">FileTypes</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="keyboard.html">键盘</a>  »
 </span></div>
 </div>
@@ -62,7 +62,7 @@
 <img src="../images/prefs-images/fonts.png" alt="fonts.png" />
 <p>Haiku 定义了三种标准字体用于不同的目的。您可以设置简单，粗体，和等宽字体和字体大小以用于整个系统。除此之外，还有对于菜单中字体的单独设置。</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复所有设置为默认状态。</td></tr>
+<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复到系统默认的设置状态。</td></tr>
 <tr><td><span class="button">Revert</span></td><td> </td><td>恢复设置到程序启动时的状态。</td></tr>
 </table>
@@ -76,8 +76,8 @@
 <div class="nav">
 <div class="inner"><span>
- «  <a href="filetypes.html">文件类型</a> 
+ «  <a href="filetypes.html">FileTypes</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="keyboard.html">键盘</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,8 +42,8 @@
 </ul>
 <span>
  «  <a href="fonts.html">字体</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="keymap.html">终端键盘映射</a>  »
+::  <a href="keymap.html">键盘映射</a>  »
 </span></div>
 </div>
@@ -61,7 +61,7 @@
 <img src="../images/prefs-images/keyboard.png" alt="keyboard.png" />
 <p>设置重复速度和两次按键之间的延迟时间。您可以在底部的文本框内对相关设置进行测试。</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复所有设置为默认状态。</td></tr>
+<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复到系统默认的设置状态。</td></tr>
 <tr><td><span class="button">Revert</span></td><td> </td><td>恢复键盘设置启动之前的设置状态。</td></tr>
 </table>
@@ -72,8 +72,8 @@
 <div class="nav">
 <div class="inner"><span>
  «  <a href="fonts.html">字体</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="keymap.html">终端键盘映射</a>  »
+::  <a href="keymap.html">键盘映射</a>  »
 </span></div>
 </div>
 -->
@@ -16,13 +16,13 @@
 	<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>终端键盘映射</title>
+	<title>键盘映射</title>
 	<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
 </head>
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,16 +42,16 @@
 </ul>
 <span>
 «  <a href="keyboard.html">键盘</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="locale.html">本地化</a>  »
+::  <a href="locale.html">Locale</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
-<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</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><img src="../../images/prefs-images/keymap-icon_64.png" alt="keymap-icon_64.png" width="64" height="64" />终端键盘映射</h2>
+<h2><img src="../../images/prefs-images/keymap-icon_64.png" alt="keymap-icon_64.png" width="64" height="64" />键盘映射</h2>
 <table summary="quickinfo" border="0" cellspacing="0" cellpadding="2">
 <tr><td>桌面栏：</td><td style="width:15px;"></td><td><span class="menu">首选项</span></td></tr>
 <tr><td>位置：</td><td></td><td><span class="path">/boot/system/preferences/Keymap</span></td></tr>
@@ -61,35 +61,37 @@
 </table>
 <p><br /></p>
 <img src="../images/prefs-images/keymap.png" alt="keymap.png" />
-<p>To the right, the Keymap window shows a representation of your keyboard. When you press a key, the corresponding key is darkened and the assigned symbol is entered into the <i>Sample and Clipboard</i> text field at the bottom. From there you can also copy and paste it into a document.<br />
+<p>在面板右侧，键盘映射窗口显示了一个键盘。当你按下某个按键时，所要响应的按键将会变暗，然后指定的符号将会输入到底部的 <i>Sample and Clipboard</i> 文本框。您也可以从这儿复制里面的内容，将粘贴到文档中。
-Thus, the Keymap preferences are not only for configuring your local keymap, but are also useful when looking for a special symbol used in other languages. For example, you can switch the keymap to "French", find the "ç" and copy it into your mail to François. (Though you'll find the "cedil" also in other keymaps...)</p>
+<br />
-<p>Pressing modifier keys like <span class="key">SHIFT</span>, <span class="key">CONTROL</span> or <span class="key">OPTION</span> changes the displayed keyboard accordingly.</p>
+如此，键盘映射首选项不仅可以用于配置您的本地键盘映射，还可用于寻找其他语言的特殊符号。例如，您可以将键盘映射切换为"法语"，找出 "ç" 然后将其复制到您邮件中的 François。（尽管您也可以在其他的键盘映射中找出 "cedil"...）</p>
-<p>Then there are the keys that are marked with a blue background. These keys are called <i>Dead Keys</i> that can change the key you press after that. If you click on such a blue key with your mouse, those changeable keys light up yellow. Click again and everything's back to normal. Examples are é, ñ, ó or ë.</p>
+<p>按下辅助按键，例如 <span class="key">SHIFT</span>，<span class="key">CONTROL</span> 或者 <span class="key">OPTION</span> 来改变显示的键盘类型。</p>
-<p>Below the keyboard representation are two more options:</p>
+<p>还有些按键的背景标记为蓝色，这些按键称为 <i>Dead Keys</i> ，它们可以改变您在按下它们之后所按下的按键。如果您点击了这些蓝色的按键，那些可以改变的按键显示为黄色；再次点击，所有的按键将恢复正常。例如 é，ñ，ó或者ë。</p>
 <p>在键盘显示的下面，还有两个选项：</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="menu">Select Dead Keys</span></td><td> </td><td>for setting the above mentioned blue keys.</td></tr>
+<tr><td><span class="menu">Select Dead Keys</span></td><td> </td><td>用于设置上述的蓝色按键。</td></tr>
-<tr><td class="onelinetop"><span class="menu">Switch Shortcut Key...</span></td><td> </td><td>for using the shortcut key in Windows/Linux mode, i.e. <span class="key">CONTROL</span> (normally <span class="key">CTRL</span>) or Haiku mode, i.e. <span class="key">COMMAND</span> (normally <span class="key">ALT</span>).</td></tr>
+<tr><td class="onelinetop"><span class="menu">Switch Shortcut Key...</span></td><td> </td><td>用于使用 Windows/Linux 模式的快捷键，例如 <span class="key">CONTROL</span>（通常为 <span class="key">CTRL</span>）或者 Haiku 模式，例如 <span class="key">COMMAND</span>（通常为 <span class="key">ALT</span>）。</td></tr>
 </table>
-<p>The lists on the left offer the available pre-configured keymaps of the system, and below that, if available, user-defined maps. You can change a keymap via drag&amp;drop in the keyboard representation: a left-click-drag copies a key, a right-click-drag exchanges the two keys.<br />
+<p>左边的列表提供了可用的系统预设值键盘映射，在它的下面还提供了可用的用户定义键盘映射。您可以通过拖拽来改变键盘映射：左键点击拖拽复制一个按键，而右键点击拖拽调换两个按键。
-When you're done you can save the result from the menu <span class="menu">File | Save...</span>. Your modified map will only appear in the user-defined list if it's stored in <span class="path">~/config/settings/Keymap/</span>. Otherwise you'll have to manually load it via <span class="menu">File | Open...</span>.</p>
+<br />
-<p>To better match the Keymap panel to your physical keyboard, there are several different settings available from the <span class="menu">Layout</span> menu.</p>
+修改完成之后，您可以使用菜单 <span class="menu">File | Save...</span> 来保存结果。如果结果保存在 <span class="path">~/config/settings/Keymap/</span>，那么您修改后的映射将会只出现在用户定义的列表，否则，您需要通过 <span class="menu">File | Open...</span> 对其进行手动的加载。</p>
-<p>The font used in the keyboard representation is set from the <span class="menu">Font</span> menu. Note, that it may or may not contain all symbols for a specific keymap.</p>
+<p>为了使键盘映射面板更好的对应于您实际的键盘，在 <span class="menu">Layout</span> 菜单中有几个不同的设置可供选择。</p>
-<p>Finally, there's a <span class="button">Revert</span> button to bring back the settings that were active when you started the Keymap preferences.</p>
+<p>在键盘显示面板中的字体可以通过 <span class="menu">Font</span> 菜单进行设置。需要注意的是，它可能不包含某种特别映射的所有符号。</p>
 <p>最后，有一个 <span class="button">Revert</span> 按钮，它用于恢复设置到键盘映射首选项启动之前的状态。</p>
 <h2>
 <a href="#"><img src="../../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="advanced-keymapping" name="advanced-keymapping">Advanced keymap manipulation</a></h2>
+<a id="advanced-keymapping" name="advanced-keymapping">高级键盘映射操作</a></h2>
-<p>There's another method to customize your keymap besides the Keymap preference panel. It involves editing a text file containing loads of hex values, which may appear daunting on first sight, but isn't really that impossible to grasp.</p>
+<p>除了使用键盘映射首选项面板之外，还有一种方法可以用于定制键盘映射。它涉及到编辑包含十六进制值的文本文件，看起来难度很大，但是它并非无法掌握。</p>
-<p>You can dump the current keymap with a command in Terminal:</p>
+<p>您可以在终端中使用下述命令卸载当前的键盘映射：</p>
 <pre class="terminal">keymap -d &gt; MyKeymap</pre>
 <p>The generated text file can then be opened in a text editor. Make sure to use a fixed font in that editor or you'll never grok that file...<br />
 At the beginning of that file, you'll find a legend of a stylized keyboard with the hex value corresponding to each key. Below that are the actual assignments of every value. You can do all the customizing that's also available from the Keymap preference panel, and then some. If you happen to have some special keys on your keyboard, you may be able to activate them. That is, use them as ordinary keys or like an option or control key. You won't be able to, for example, have your multimedia keys de/increase the volume or start some application. For this you can use e.g. <a href="http://www.haikuware.com/directory/view-details/utilities/desktop-accessories/spicykeys" class="noprinturl">SpicyKeys</a>.</p>
-<p>When you're finished, you'll save the file and have your system load the modified keymap with this command:</p>
+<p>在完成修改之后，为了保存文件，并且使系统启用修改后的键盘映射，您可以使用下述命令：</p>
 <pre class="terminal">keymap -s &lt; MyKeymap</pre>
-<p>If you'd like to import this keymap into the Keymap panel, you have to compile it first to a binary format:</p>
+<p>如果您希望将该键盘映射引入映射面板，您必须首先将它编译为二进制格式：</p>
 <pre class="terminal">keymap -c &lt; MyKeymap</pre>
-<p>This will produce a file <span class="cli">keymap.out</span> which you can load into Keymap via its <span class="menu">Open...</span> menu. By the way, the keymap command is able to load this binary format as well: <span class="cli">keymap -l &lt; keymap.out</span></p>
+<p>该命令将会创建一个文件 <span class="cli">keymap.out</span>，您可以通过 <span class="menu">Open...</span> 菜单载入键盘映射。还需要说明的是，keymap命令也可以载入该二进制格式： <span class="cli">keymap -l &lt; keymap.out</span></p>
-<p>This is the dumped file (the rightmost keys of the stylized keyboard are cut-off for a nicer display on this page):</p>
+<p>下面是卸载后的文件（为了使该页面有更好的显示效果，我们剪切了键盘最右边的按键设置）：</p>
 <pre>#!/bin/keymap -s
 #
@@ -372,8 +374,8 @@ TildeTab = Normal Shift Option Option-Shift CapsLock CapsLock-Shift CapsLock-Opt
 <div class="nav">
 <div class="inner"><span>
 «  <a href="keyboard.html">键盘</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="locale.html">本地化</a>  »
+::  <a href="locale.html">Locale</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,15 +41,14 @@
 <li><a href="../../en/preferences/mouse.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="media.html">媒体</a> 
+ «  <a href="media.html">Media</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="network.html">网络</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
 <div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
 <h2><img src="../../images/prefs-images/mouse-icon_64.png" alt="mouse-icon_64.png" width="64" height="64" />鼠标</h2>
 <table summary="quickinfo" border="0" cellspacing="0" cellpadding="2">
@@ -60,19 +59,19 @@
 </table>
 <p><br /></p>
 <img src="../images/prefs-images/mouse.png" alt="mouse.png" />
-<p>Set your type of mouse: 1, 2 or 3 button mouse. You can simulate the 2nd (=right) mouse button by holding down <span class="key">CTRL</span> while left-clicking. For the 3rd (=middle) mouse button, it's <span class="key">CTRL</span> <span class="key">ALT</span> and a left-click. A middle-click is also simulated by clicking left and right button together. Useful for notebooks, which mostly don't have a 3rd button.</p>
+<p>设置鼠标类型：单键，双键或者三键鼠标。您可以通过左键点击的同时按下 <span class="key">CTRL</span> 来模拟第二个鼠标键（右键）。至于第三个鼠标键（中间键），它等同于 <span class="key">CTRL</span> <span class="key">ALT</span> 联合左键点击。中间点击也可以使用同时按下左右键来模拟。对于笔记本电脑，通常不需要使用第三个鼠标键。</p>
-<p>You can rearrange the mouse buttons by clicking on them and choosing their new meaning from the pop-up menu.</p>
+<p>您可以通过点击在鼠标按钮，从弹出菜单中选择它们的新功能来对其进行重新排序。</p>
-<p>With the sliders to the right, you adjust double-click speed, mouse speed and acceleration.</p>
+<p>使用右边的滑动条，您可以调整双击的速度，鼠标的移动速度和加速度。</p>
-<p><span class="menu">Focus follows mouse</span> means, that you don't have to click into a window to activate it. There are three modes:</p>
+<p><span class="menu">Focus follows mouse</span> 意味着，您无须点击窗口来对其进行激活。它具有三种模式：</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="menu">Enabled</span></td><td> </td><td>The window under the mouse pointer is always activated automatically, but doesn't pop to the front.</td></tr>
+<tr><td><span class="menu">Enabled</span></td><td> </td><td>鼠标指针下的窗口总是自动激活，但是不会自动弹出。</td></tr>
-<tr><td><span class="menu">Warping</span></td><td> </td><td>Choosing a window from Deskbar or the <a href="../twitcher.html">Twitcher</a> will have the mouse pointer glide smoothly toward it.</td></tr>
+<tr><td><span class="menu">Warping</span></td><td> </td><td>从桌面栏或者<a href="../twitcher.html">任务切换器</a>中选中的窗口将会平滑的获取鼠标指针。</td></tr>
-<tr><td class="onelinetop"><span class="menu">Instant-Warping</span></td><td> </td><td>Choosing a window from Deskbar or the Twitcher will have the mouse pointer jump instantly toward it.</td></tr>
+<tr><td class="onelinetop"><span class="menu">Instant-Warping</span></td><td> </td><td>从桌面栏或者任务切换器中选中的窗口将会立即自动获取鼠标指针，</td></tr>
 </table>
-<p>All settings are immediately applied.</p>
+<p>所有的设置将会被立即应用。</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复所有设置为默认状态。</td></tr>
+<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复到系统默认的设置状态。</td></tr>
-<tr><td><span class="button">Revert</span></td><td> </td><td>brings back the settings that were active when you started the Mouse preferences.</td></tr>
+<tr><td><span class="button">Revert</span></td><td> </td><td>恢复到鼠标首选项启动时的设置状态。</td></tr>
 </table>
 </div>
@@ -80,8 +79,8 @@
 <div class="nav">
 <div class="inner"><span>
- «  <a href="media.html">媒体</a> 
+ «  <a href="media.html">Media</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="network.html">网络</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,14 +42,13 @@
 </ul>
 <span>
  «  <a href="mouse.html">鼠标</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="printers.html">打印机</a>  »
+::  <a href="printers.html">Printers</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
 <div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</div>
 <h2><img src="../../images/prefs-images/network-icon_64.png" alt="network-icon_64.png" width="64" height="64" />网络</h2>
 <table summary="quickinfo" border="0" cellspacing="0" cellpadding="2">
@@ -60,11 +59,11 @@
 </table>
 <p><br /></p>
 <img src="../images/prefs-images/network.png" alt="network.png" />
-<p>At the top, you choose which network adapter to configure.</p>
+<p>在窗口顶部，您可以选择进行配置的网络适配器。</p>
-<p>Then you specify if you get your network automatically (via <acronym title="Dynamic Host Configuration Protocol">DHCP</acronym>) or if you're using static addresses. If it's the latter, you'll have to fill out IP Address, Netmask, Gateway and DNS Servers yourself. Otherwise the panel will show the addresses currently set with DHCP.</p>
+<p>然后您可以指定，是否您的网络自动进行配置（通过 <acronym title="Dynamic Host Configuration Protocol">DHCP</acronym>），是否您使用的是静态地址。如果是后一种情况，您需要手动填写自己的IP地址，子网掩码，网关和DNS服务器。否则，面板将会显示当前通过DHCP设置的地址。</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="button">Revert</span></td><td> </td><td>brings back the settings that were active when you started the Network preferences.</td></tr>
+<tr><td><span class="button">Revert</span></td><td> </td><td>恢复到网络首选项启动时的设置状态。</td></tr>
-<tr><td><span class="button">Apply</span></td><td> </td><td>sets the entered configuration.</td></tr>
+<tr><td><span class="button">Apply</span></td><td> </td><td>使用输入的配置信息。</td></tr>
 </table>
 </div>
@@ -74,8 +73,8 @@
 <div class="nav">
 <div class="inner"><span>
  «  <a href="mouse.html">鼠标</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
-::  <a href="printers.html">打印机</a>  »
+::  <a href="printers.html">Printers</a>  »
 </span></div>
 </div>
 -->
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -50,7 +50,7 @@
 <div id="content">
 <div>
-<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</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><img src="../../images/prefs-images/touchpad-icon_64.png" alt="touchpad-icon_64.png" width="64" height="64" />触摸板</h2>
 <table summary="quickinfo" border="0" cellspacing="0" cellpadding="2">
@@ -71,7 +71,7 @@ The acceleration setting decides how much quicker a list scrolls by if you swish
 If you feel comfortable using this feature, you can dispense with setting scroll areas and instead use the whole pad for normal navigation.</p>
 <p>At the bottom is another slider to set the tap click sensitivity. If your taps keep getting ignored, increase the sensitivity. If the system registers clicks all the time, while all you want is to move the mouse pointer, try decreasing it.</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复所有设置为默认状态。</td></tr>
+<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复到系统默认的设置状态。</td></tr>
 <tr><td><span class="button">Revert</span></td><td> </td><td>返回到您启动触摸板首选项之前的设置状态。</td></tr>
 </table>
 <p>Here is a tip that's not related to the Touchpad preferences, but fits the general topic:<br />
@@ -84,8 +84,8 @@ Depending on your hardware, there's a nifty feature: just leave your finger with
 <div class="nav">
 <div class="inner"><span>
- «  <a href="tracker.html">Tracker 文件浏览器</a> 
+ «  <a href="tracker.html">Tracker </a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="virtualmemory.html">虚拟内存</a>  »
 </span></div>
 </div>
@@ -9,18 +9,20 @@
 *
 * Authors:
 *		Humdinger <humdingerb@gmail.com>
 * Translators:
 *		Pengphei Han
 *
 -->
 	<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>Tracker 文件浏览器</title>
+	<title>Tracker </title>
 	<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
 </head>
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -39,15 +41,15 @@
 <li><a href="../../en/preferences/tracker.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="time.html">时间</a> 
+ «  <a href="time.html">Time</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="touchpad.html">触摸板</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
-<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</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><img src="../../images/prefs-images/tracker-icon_64.png" alt="tracker-icon_64.png" width="64" height="64" />Tracker</h2>
 <table summary="quickinfo" border="0" cellspacing="0" cellpadding="2">
@@ -57,8 +59,9 @@
 </td><td></td><td><span class="path">~/config/settings/Tracker/TrackerSettings</span></td></tr>
 </table>
 <p><br /></p>
-<p>The Tracker preference panel is also available from every Tracker window with the menu <span class="menu">Window | Preferences...</span>.<br />
+<p>Tracker首选项面板可以通过每个Tracker窗口的 <span class="menu">Window | Preferences...</span> 菜单进行启用。
-Its functions are discussed in the topic on <a href="../tracker.html#tracker-preferences">Tracker</a>.</p>
+<br />
 有关它的功能可以查阅 <a href="../tracker.html#tracker-preferences">Tracker</a> 主题。</p>
 </div>
 </div>
@@ -66,8 +69,8 @@ Its functions are discussed in the topic on <a href="../tracker.html#tracker-pre
 <!--
 <div class="nav">
 <div class="inner"><span>
- «  <a href="time.html">时间</a> 
+ «  <a href="time.html">Time</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a> 
+::  <a href="../preferences.html" class="uplink">Preferences</a> 
 ::  <a href="touchpad.html">触摸板</a>  »
 </span></div>
 </div>
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,7 +42,7 @@
 </ul>
 <span>
  «  <a href="touchpad.html">触摸板</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a>
+::  <a href="../preferences.html" class="uplink">Preferences</a>
 </span></div>
 </div>
@@ -63,7 +63,7 @@
 <p>通常，交换文件将会写入到您的启动分区。如果由于虚拟内存系统的交换文件而经常导致磁盘超荷，您可以尝试使用独立的硬盘用于交换文件。简单的使用同一硬盘的其他分区用于系统和数据将不会有任何效果。<br />
 当然，升级您的内存将会是最有效的解决方法。</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
-<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复所有设置为默认状态。</td></tr>
+<tr><td><span class="button">Defaults</span></td><td> </td><td>恢复到系统默认的设置状态。</td></tr>
 <tr><td><span class="button">Revert</span></td><td> </td><td>返回到启动虚拟内存首选项之前的设置状态。</td></tr>
 </table>
@@ -74,7 +74,7 @@
 <div class="nav">
 <div class="inner"><span>
  «  <a href="touchpad.html">触摸板</a> 
-::  <a href="../preferences.html" class="uplink">首选项</a>
+::  <a href="../preferences.html" class="uplink">Preferences</a>
 </span></div>
 </div>
 -->
@@ -22,7 +22,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,23 +42,23 @@
 </ul>
 <span>
 «  <a href="index.html">索引</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workshop-filetypes+attributes.html">操作讲解</a>  »
+::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
-<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</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>索引</td></tr>
 <tr class="index"><td>
 	<a href="#find-window">查询窗口</a><br />
-	<a href="#basic-query">基本查询 - "by Name"</a><br />
+	<a href="#basic-query">基本查询 - "使用名字"</a><br />
-	<a href="#adv-query">标准查询 - "by Attribute"</a><br />
+	<a href="#adv-query">标准查询 - "使用属性"</a><br />
-	<a href="#more-adv-query">高级查询 - "by Formula"</a><br />
+	<a href="#more-adv-query">高级查询 - "使用表达式"</a><br />
 	<a href="#result-window">结果窗口</a><br />
 	<a href="#query-template">查询模板</a>
 </td></tr>
@@ -92,12 +92,12 @@ Even better, you don't have to double-click to re-do a query. You can <a href="t
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="basic-query" name="basic-query">基本查询 - "by Name"</a></h2>
+<a id="basic-query" name="basic-query">基本查询 - "使用名字"</a></h2>
 <p>If you simply want to find all files and folders on your mounted disks that match a certain pattern, simply leave the search method at <span class="menu">by Name</span>, enter the search term into the text box and press <span class="key">ENTER</span>.</p>
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="adv-query" name="adv-query">标准查询 - "by Attribute"</a></h2>
+<a id="adv-query" name="adv-query">标准查询 - "使用属性"</a></h2>
 <p>You can create more advanced queries by searching within the attributes of specific file types. For that to work, these attributes have to be <a href="index.html">indexed</a>.</p>
 <img src="images/queries-images/query-window.png" alt="query-window.png" />
 <p>You start by setting the filetype from <span class="menu">All files and folders</span> to, for example, <span class="menu">Text | E-mail</span> and change the search method to <span class="menu">by Attribute</span>.</p>
@@ -110,7 +110,7 @@ A good way to cut down the number of search results.</p>
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<a id="more-adv-query" name="more-adv-query">高级查询 - "by Formula"</a></h2>
+<a id="more-adv-query" name="more-adv-query">高级查询 - "使用表达式"</a></h2>
 <p>Typing in a formula query by hand is daunting and really quite unpractical. It still has its uses.</p>
 <p>Take the above query by attribute of Clara's mails concerning vibraphones etc. If you have all the attributes and their search terms set, try switching to <span class="menu">by Formula</span> mode and be overwhelmed by this one line query string:</p>
 <img src="images/queries-images/formula-query.png" alt="formula-query.png" />
@@ -124,7 +124,7 @@ A good way to cut down the number of search results.</p>
 <ul>
 <li><p>You could copy and paste the string into an email, forum or IRC for others to use or debug.</p></li>
 <li><p>You can use this method to construct a query in <span class="menu">Attribute</span> mode and then switch to <span class="menu">Formula</span> mode, to comfortably generate a search string to use for a query in Terminal or a script.</p></li>
-<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
+<li><p>You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "<tt>==</tt>" to "<tt>!=</tt>" for a NOT AND. All you need is a basic understanding of <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expressions</a> and maybe some scripting basics.</p></li>
 </ul>
 <h2>
@@ -154,8 +154,8 @@ By using the <span class="menu">Save Query as Template</span> menu item (see <a
 <div class="nav">
 <div class="inner"><span>
 «  <a href="index.html">索引</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="workshop-filetypes+attributes.html">操作讲解</a>  »
+::  <a href="workshop-filetypes+attributes.html">Workshop</a>  »
 </span></div>
 </div>
@@ -16,13 +16,13 @@
 	<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>Tracker 文件浏览器</title>
+	<title>Tracker </title>
 	<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
 </head>
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -41,15 +41,15 @@
 <li><a href="../en/tracker.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
 </ul>
 <span>
- «  <a href="teammonitor.html">程序监控器</a> 
+ «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Tracker 附加组件</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
 <div id="content">
 <div>
-<div class="box-info">本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。</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">
@@ -64,7 +64,7 @@
 </td></tr>
 </table>
-<h1>Tracker 文件浏览器</h1>
+<h1>Tracker </h1>
 <p>Tracker是所有文件的图形界面显示工具。它允许您新建文件和文件夹，复制和删除文件，并且还可以对文件进行查询，启动和重命名等操作。</p>
 <p>同其他的应用程序一样 (the Desktop with its icons is really just a fullscreen window in the background)，Tracker与它的窗口出现在桌面栏，并且可以关闭和重启。 The easiest way to quit and restart a crashed or frozen Tracker (or a wayward Deskbar) is to call the <a href="teammonitor.html">Team Monitor</a>.</p>
@@ -72,22 +72,23 @@
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="mounting-volumes" name="mounting-volumes">挂载磁卷</a></h2>
-<p>In order to access a harddisk, CD, USB stick etc., you first have to mount the volume, that is, let the system know it's there. This is done with a right-click on the Desktop or an already mounted volume (like the boot disk) and choosing the volume from the <span class="menu">Mount</span> submenu. You find the same <span class="menu">Mount</span> menu in the Deskbar.</p>
+<p>为了能够访问硬盘，CD，USB磁盘等，您首先需要挂载这些磁卷，也就是告诉系统，它们存在。 右键点击桌面，或者已经挂载的刺卷（如启动盘），然后从 <span class="menu">Mount</span> 子菜单中选择磁卷。您也可以在桌面栏中找到相同的 <span class="menu">Mount</span> 菜单。</p>
 <img src="images/tracker-images/mount-settings.png" alt="drill-down.png" />
-<p>There are also <span class="menu">Mount Settings</span> so you don't have to mount everything manually after every bootup.<br />
+<p>还有一个 <span class="menu">Mount Settings</span> ，因此你不需要每次启动时都手动挂载所有磁卷。
-The above settings will automatically mount any storage device you connect/insert and also mount all disks on bootup that were mounted previously.</p>
+<br />
-<div class="box-warning">Before you disconnect e.g. a harddrive or USB stick, make sure you have successfully unmounted the volume. This guarantees that all data transfer has finished. Otherwise you may lose data or corrupt the disk!</div>
+上述的设置将会自动挂载您所连接/插入的所有存储设备，然后在启动时挂载所有曾经挂载过的磁盘。</p>
 <div class="box-warning">在您断开硬件设备或者USB磁盘的连接时，一定要保证您已经成功的卸载了该磁卷。这样可以保证所有的数据传输已经结束，否则可能会导致数据的丢失或者损坏磁盘。</div>
 <h2>
 <a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="navigating" name="navigating">文件导航</a></h2>
-<p>By default, when you double-click a folder, Tracker opens a new window while leaving the parent window open. This can quickly lead to an overcrowded desktop.<br />
+<p>默认情况下，双击文件夹，Tracker打开新窗口，并且保持先前的打开窗口。这将会很快导致桌面的拥挤。<br />
-You can prevent that by holding down the <span class="key">OPT</span> key, which automatically closes the parent window.<br />
+您可以使用 <span class="key">OPT</span> 键来阻止这种情况发生，它将会自动关闭先前的窗口。<br />
-This is also true for keyboard navigation. For more on that, see topic <a href="keyboard-shortcuts.html">Shortcuts and key combinations</a>.</p>
+这也同样适用于键盘导航，更多的信息可以参阅主题 <a href="keyboard-shortcuts.html">快捷键和组合键</a>。</p>
 <p>Moving through your folders is one of Trackers main purposes, just like the file managers on other platforms. Haiku's Tracker has some unique features that will help you doing that efficiently.</p>
 <h3>
-<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a><a id="drill-down" name="drill-down">Drilling down the submenus</a></h3>
+<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a><a id="drill-down" name="drill-down">进入子菜单</a></h3>
 <p>Instead of double-clicking your way down folder after folder, there's a better way to drill down:</p>
 <img src="images/tracker-images/drill-down.png" alt="drill-down.png" />
 <!-- screenshot needs updating to show /boot/system/documentation -->
@@ -126,7 +127,7 @@ This type-ahead filtering is set in the <a href="#tracker-preferences.html">Trac
 <ul>
 <li><p><b>Resize Window</b> (<span class="key">ALT</span> <span class="key">Y</span>) - Resizes the window to its ideal size.</p></li>
 <li><p><b>Clean Up</b> (<span class="key">ALT</span> <span class="key">K</span>) - Aligns all icons to an invisible grid. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Clean Up All</span> which additionally sorts all icons alphabetically.</p></li>
-<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="http://en.wikipedia.org/wiki/Regular expression">regular expression</a>.</p></li>
+<li><p><b>Select...</b> (<span class="key">SHIFT</span> <span class="key">ALT</span> <span class="key">A</span>) - Select files according to a <a href="http://en.wikipedia.org/wiki/Regular_expression" class="external free" title="Wikipedia: Regular expression">regular expression</a>.</p></li>
 <li><p><b>Close</b> (<span class="key">ALT</span> <span class="key">W</span>) - Closes the window. Hold down <span class="key">SHIFT</span> and the menu becomes <span class="menu">Close All</span> which closes every Tracker window.</p></li>
 <li><p><b>Close All in Workspace</b> (<span class="key">ALT</span> <span class="key">Q</span>) - Closes every Tracker window in the current workspace. A useful shortcut if you forgot to hold the <span class="key">OPT</span> key while clicking through folders and all those still open Tracker windows clutter your workspace.</p></li>
 </ul>
@@ -193,9 +194,9 @@ This type-ahead filtering is set in the <a href="#tracker-preferences.html">Trac
 <div class="nav">
 <div class="inner"><span>
- «  <a href="teammonitor.html">程序监控器</a> 
+ «  <a href="teammonitor.html">Team Monitor</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="tracker-add-ons.html">Tracker 附加组件</a>  »
+::  <a href="tracker-add-ons.html">Tracker Add-Ons</a>  »
 </span></div>
 </div>
@@ -16,13 +16,13 @@
 	<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>讨论：文件类型， 属性，索引和查询</title>
+	<title>操作练习：文件类型， 属性，索引和查询</title>
 	<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
 </head>
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -42,8 +42,8 @@
 </ul>
 <span>
 «  <a href="queries.html">查询</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="applications.html">应用程序</a>  »
+::  <a href="applications.html">Applications</a>  »
 </span></div>
 </div>
@@ -70,7 +70,7 @@
 </td></tr>
 </table>
-<h1>讨论：文件类型， 属性，索引和查询</h1>
+<h1>操作练习：文件类型， 属性，索引和查询</h1>
 <p>本篇文档主要用于展示 <a href="attributes.html">属性</a>，<a href="queries.html">查询</a>，<a href="index.html">索引</a>和定制<a href="filetypes.html">文件类型</a>。我们将会创建一个数据库来记录我们的DVD库。</p>
@@ -222,8 +222,8 @@ mkindex -t int DVDdb:rating</pre>
 <div class="nav">
 <div class="inner"><span>
 «  <a href="queries.html">查询</a> 
-::  <a href="contents.html" class="uplink">内容</a> 
+::  <a href="contents.html" class="uplink">Contents</a> 
-::  <a href="applications.html">应用程序</a>  »
+::  <a href="applications.html">Applications</a>  »
 </span></div>
 </div>
@@ -4,25 +4,27 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 * Translators:
 *		Matthias
 *		Humdinger
 *
 -->
 	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
 	<meta name="robots" content="all" />
-	<title>Fehler melden</title>
+	<title>Bugs melden</title>
 	<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
 </head>
 <body>
 <div id="banner">
-<div><span>User Guide</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -48,48 +50,108 @@
 <div id="content">
 <div>
-<h1>Fehler melden</h1>
+<table class="index" id="index" summary="index">
 <tr class="heading"><td>Bugs melden</td></tr>
 <tr class="index"><td><a href="#account">Zugang zu Trac</a><br />
                <a href="#report">Bugreport erstellen</a><br />
                <a href="#app">Bugs in Anwendungen</a><br />
                  <a href="#server">Bugs in Servern</a><br />
                  <a href="#kernel">Bugs im Kernel</a><br />
                  <a href="#kdl">Kernel Debugging Land - KDL</a><br />
                  <a href="#syslog">Syslog</a><br />
                  <a href="#onscreen">Debug Ausgabe auf dem Bildschirm</a><br />
                  <a href="#hardware">Bugs von Hardware/Treiber</a><br />
                  <a href="#next">Bug gemeldet, und dann?</a></td></tr>
 </table>
-<p>Da es für die Haiku-Entwickler unmöglich ist, jede denkbare Hardware-Kombination oder jede mögliche Anwendungsweise eines Programmes zu testen, ist es eine große Hilfe, wenn erkannte Fehler von Anwendern gemeldet werden. Da Haiku noch nicht vollständig ausgereift ist - aktuell befindet es sich in der Alpha-Phase - ist es nicht unwahrscheinlich, dass Fehler auftreten. Nur mit Hilfe der Anwender können wir Haiku Stück für Stück perfektionieren.</p>
+<h1>Bugs melden</h1>
 <p>Um unseren "Bugtracker" - also die Liste aller gefundenen Fehler - effektiv zu halten, ist es notwendig, eine grundlegende Etikette, die "<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>" zu wahren.</p>
-<h2>Wie man einen Zugang zum Trac erhält</h2>
+<p>Da es für die Haiku-Entwickler unmöglich ist, jede denkbare Hardware-Kombination oder jede mögliche Anwendungsweise eines Programms zu testen, ist es eine große Hilfe, wenn Fehler  gemeldet werden. Da Haiku noch recht jung ist, sind Bugs nicht Ungewöhnliches. Nur mit Hilfe der Anwender können wir Haiku gemeinsam Stück für Stück perfektionieren.</p>
-<p>Um ein Fehler-Ticket einzureichen, muss man registrierter Benutzer beim <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Bugtracker</a> sein.<br /> Um sich anzumelden ist eine <b>gültige E-Mail Adresse</b> notwendig. Sollte nach dem Anmelden keine Bestätigungsmail erhalten werden, lohnt es sich, seinen <b>Spam-Filter</b> zu überprüfen.</p>
+<p>Damit unser "Bugtracker" - also die Liste aller gefundenen Fehler - effektiv funktioniert, ist eine grundlegende <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a> zu wahren.</p>
-<h2>Einen Fehlerbericht erstellen</h2>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Ehe man einen Fehler meldet, sollte man sich <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">sicher sein</a>, dass er nicht schon gemeldet wurde. Hierzu kann auch die <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">Suchfunktion</a> verwendet werden.<br />
+<a id="account" name="accout">Zugang zu Trac</a></h2>
 <p>Um ein Fehler-Ticket aufzugeben, muss man registrierter Benutzer beim <a href="http://dev.haiku-os.org/register" title="Registerierung bei Haikus Bugtracker">Bugtracker</a> sein.<br /> Um sich anzumelden ist eine <b>gültige E-Mail Adresse</b> notwendig. Sollte nach dem Anmelden keine Bestätigungsmail ankommen, sollte man mal seinen <b>Spam-Ordner</b> überprüfen.</p>
 <h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="report" name="report">Bugreport erstellen</a></h2>
 <p>Bevor man einen Fehler meldet, sollte man sich <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">sicher sein</a>, dass das nicht schon geschehen ist. Hierzu kann auch die <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">Suchfunktion</a> verwendet werden.<br />
 Nach dieser Überprüfung sollte man so genau wie möglich den Fehler beschreiben:</p>
 <ul>
-	<li><p>Wie wurde Haiku verwendet (auf echter Hardware oder virtualisiert unter VMWare, QEMU oder ähnlichem)</p></li>
+	<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>Welche Versionsnummer des <acronym title="Subversion, the source code management system we use">SVN</acronym> wurde verwendet?. Die Nummer ist auch unter '<i>About This System...</i>' im Deskbar-Menü abzulesen.</p></li>
+	<li><p>Wie wurde Haiku verwendet (auf echter Hardware oder virtualisiert unter VMWare, QEMU oder ähnlichem)?</p></li>
-	<li><p>Der Fehler sollte so präzise wie möglich beschrieben werden. Wie war das tatsächliche Verhalten im Gegensatz zum Erwarteten?</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>Wann ist der Fehler aufgetreten? Welche Schritte führten dazu? Nur so können die Entwickler den Fehler nachstellen und erkennen.</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>An den Fehlerbericht sollten so viele Informationen wie möglich angehängt werden. Log-Dateien oder Bildschirmphotos (die Taste <span class="key">PRINT</span> speichert den Bildschirm als <acronym title="Portable Network Graphics image format">PNG</acronym> im Verzeichnis <span class="path">/boot/home/</span>) sind sehr hilfreich.</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>
 </ul>
-<h3>Fehler in Anwendungen</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Wenn eine Anwendung unerwartet abstürzt, sollte man den "Debugger" aus dem erscheinenden Hinweisfenster aufrufen. Ein <span class="cli">bt</span> im daraufhin startenden Terminal erstellt einen sogenannten "backtrace" der mit an die Fehlermeldung angehängt werden sollte.</p>
+<a id="app" name="app">Bugs in Anwendungen</a></h2>
 <p>Stürzt eine Anwendung ab, sollte man den Debugger aus dem erscheinenden Hinweisfenster aufrufen. Dadurch wird ein Terminal mit gdb (dem GNU Debugger) geöffnet. Gibt man dort <span class="cli">bt</span> ein, wird ein sogenannter "backtrace" erstellt, der komplett (auch mit dem Teil bevor <span class="cli">bt</span> eingegeben wurde) mit an die Fehlermeldung angehängt werden sollte.</p>
-<h3>Fehler auf Grund Hardware</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Wenn ein Fehler gemeldet wird, der Hardware oder Treiber betrifft, sollten mindestens diese Informationen an den Fehlerbericht angehängt werden:</p>
+<a id="server" name="server">Bugs in Servern</a></h2>
 <p>Stürzen lebenswichtige Server wie der App Server, der Registrar oder der Input Server ab, bekommt man nicht den gewöhnlichen Crash-Hinweis zu sehen. Stattdessen wird der gesamte Bildschirm weiß und der gdb wird gestartet, der seine Ausgabe direkt auf den Bildschirm schreibt. Unter Umständen kann man immer noch die Maus bewegen, die daraufhin das Weiß und die gdb Ausgabe übermalt. Noch laufende Anwendungen wie ProcessController oder die Uhr in der Deskbar, tun das vielleicht auch noch.<br />
 Außer dass alles etwas unansehnlicher und unbequemer ist, gilt eigentlich das gleiche wie für Bugs in Anwendungen. Am wichtigsten ist das sichern eines "backtrace" mittels <span class="cli">bt</span>. Weil man den Text ja nicht mehr irgendwohin kopieren kann, müsste man die Ausgabe per Kamera festhalten.</p>
 <h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="kernel" name="kernel">Bugs im Kernel</a></h2>
 <p>Fehler im Kernel haben normalerweise die schwersten Auswirkungen und sind zugleich am schwierigsten zu debuggen. Es gibt unterschiedliche Symptome, die auf ein Problem von Kernel oder Treiber hindeuten:</p>
 <ul>
-<li><span class="cli">listdev</span> - eine detaillierte Auflistung aller vorhandener Hardware inklusive "vendor id" und "pci id"; ähnlich den Befehlen <span class="cli">lshw</span> und <span class="cli">lspci</span> unter Linux.</li>
+<li><p>Das System betritt selbständig das Kernel Debugging Land (KDL) . Der obere Teil des Bildschirms wird weiß und einige Zeilen Text erscheinen. Die zweite Zeile verkündet "<i>Welcome to Kernel Debugging Land...</i>", die darüber beschreibt den unmittelbaren Grund für die Reise ins KDL.</p></li>
-<li><span class="cli">listusb -v</span> - bei einem Fehler im Zusammenhang mit USB; ähnlich dem Befehlt <span class="cli">lsusb</span>.</li>
+<li><p>Das System führt einen spontanen Neustart aus.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - die zentrale Log-Datei in Haiku. Mit dem Befehl <span class="cli">open</span> kann das Log auf eine sinnvolle Länge gekürzt werden.</li>
+<li><p>Das System friert komplett ein. Die Maus lässt sich nicht mehr bewegen und Anwendungen aktualisieren ihre Oberfläche nicht mehr. Ein wichtiger Test in so einer Situation ist, ob man das KDL noch mit der Tastenkombination <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> ist dabei meist die <span class="key">DRUCK</span> Taste) erreichen kann. Man sollte  zumindest eine Minute warten, ob sich was tut.</p></li>
-<li><span class="cli">listimage | grep drivers/</span> - eine Auflistung aller verwendeter Treiber.</li>
+<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><span class="cli">ints</span> - nur im <i>Kernel Debugging Land</i> (siehe weiter unten) möglich. Es zeigt eine Liste aller verwendeter "Interrupts".</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>Die genannten Befehle sind im Terminal einzugeben. Mit dem Anhang "<span class="cli"> &gt; output.txt</span>" an den Befehl wird dessen Ausgabe in die Datei output.txt gespeichert, die dann an den Fehlerbericht angehängt werden kann.</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">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
-<h3>Kernel Debugging Land - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Wenn grundlegende Systemkomponenten abgestürzt sind, dann friert das System ein und es wird das KDL aufgerufen. Man kann auch absichtlich dorthin wechseln durch Drücken von <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> ist in den meisten Fällen die Taste <span class="key">PRINT</span>).</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<p>Stürzt das System nicht von selbst ins KDL, kann man das auch absichtlich mit der Tastenkombination <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> erreichen.<br />
-<li><span class="cli">co</span> - beendet das KDL und das System läuft - soweit möglich - normal weiter.</li>
+Im KDL kann es passieren, dass die Tastatur nicht mehr funktioniert. PS/2 Tastaturen gehen immer, USB Tastaturen an UHCI Controllern nur wenn man vorher schonmal per Tastenkombination das KDL betreten hat. USB OHCI wird zur Zeit noch gar nicht unterstützt.</p>
-<li><span class="cli">int</span> - zeigt die verwendeten Interrupts (wie oben beschrieben).</li>
+<p>Das KDL ist eine Art Konsole. Es lassen sich Befehle eingeben, die Informationen über das System ausgeben. Folgende Befehle sind von besonderen Interesse:</p>
-<li><span class="cli">bt</span> - zeigt einen backtrace wo genau der Fehler aufgetreten ist.</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<tr><td><span class="cli">bt</span> (auch "sc")</td><td> </td><td>Zeigt einen "backtrace" wo genau der Fehler aufgetreten ist. Ist das System von selbst ins KDL gefallen, sollte man diesen Befehl unbedingt ausführen.</td></tr>
 <tr><td><span class="cli">ints</span></td><td> </td><td>Zeigt die unbenutzten und verwendeten Interrupts.</td></tr>
 <tr><td class="onelinetop"><span class="cli">co</span> (auch "continue")</td><td> </td><td>Verlässt den Kernel Debugger und das System läuft - soweit möglich - normal weiter.</td></tr>
 <tr><td><span class="cli">reboot</span></td><td> </td><td>Führt einen unmittelbaren Neustart durch. Alle ungespeicherten Daten gehen verloren und selbst was man gespeichert hat, aber noch nicht auf die Platte geschrieben wurde, ist weg.</td></tr>
 </table>
 <p>Weitere Infos gibt es im Artikel <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a> (Englisch).</p>
 <p>Die Ausgaben im KDL werden zum seriellen Port geschickt (falls man einen hat und ein entsprechendes Nullmodemkabel samt zweiten Rechner, kann man die Ausgaben in einem Terminalprogramm aufnehmen). Außerdem werden sie ins Syslog geschrieben. Wenn man das KDL allerdings nicht verlassen kann, wird auch nichts ins Syslog geschrieben. Es gibt aber eine Bootloader Debug Option, die das trotzdem möglich macht (siehe weiter unten).</p>
-<h2>Fehler gemeldet, und dann?</h2>
+<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>
 <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>
 <h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="onscreen" name="onscreen">Debug Ausgabe auf den Bildschirm</a></h3>
 <p><b>Die Ausgabe auf dem Bildschirm ist nur bei ganz bestimmten Situationen sinnvoll und hat bekanntermaßen Timing-Probleme. Es sollte also wirklich nur im Notfall benutzt werden.</b><br />
 Das ist zum Beispiel der Fall wenn Haiku nicht ganz hochfährt und Bootloader's <span class="menu">Debug syslog option</span> irgendwie nicht funktioniert. Noch bevor das Haiku Bootlogo erscheint, die <span class="key">SHIFT</span> Taste gedrückt halten, um das Bootloader Menü aufzurufen. Von hier in das Menü <span class="menu">Select safe mode options</span> wechseln und dort weiter unten <span class="menu">[ ] Enable on screen debug output</span> aktivieren. (Die anderen Optionen kann man auch mal probieren, um zu versuchen Haiku erfolgreich zu booten. Wenn Haiku nur mit einer oder mehreren aktivierten Optionen hochfahren kann, sollte man natürlich erwähnen welche das sind.)<br />
 Abschließend geht man auf <span class="menu">Return to main menu</span> und dann <span class="menu">Continue booting</span>.<br />
 Auf dem Bildschirm werden einige Seiten Text ausgegeben, von denen aber nur die letzten paar für einen Bugreport interessant sind. Der Userguide hat noch weitere Infos zum <a href="../../../userguide/de/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">Bugs von Hardware/Treiber</a></h2>
 <p>Wenn ein Fehler gemeldet wird, der Hardware oder Treiber betrifft, sollten folgende Informationen als Textdateien an den Fehlerbericht angehängt werden:</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
 <tr><td>- <span class="cli">listdev</span></td><td> </td><td>Eine detaillierte Auflistung aller vorhandener Hardware inklusive "vendor id" und "pci id"; ähnlich den Befehlen <span class="cli">lshw</span> und <span class="cli">lspci</span> unter Linux.</td></tr>
 <tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Bei Fehlern im Zusammenhang mit USB, ähnlich dem Befehlt <span class="cli">lsusb</span> unter Linux.</td></tr>
 <tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Die zentrale Log-Datei von Haiku. Mit dem Befehl <span class="cli">open</span> kann das Log im Texteditor auf eine sinnvolle Länge gekürzt werden.</td></tr>
 <tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Eine Auflistung aller verwendeten Treiber.</td></tr>
 <tr><td>- <span class="cli">ints</span></td><td> </td><td>Nur im <i>Kernel Debugging Land</i> (siehe weiter oben). Es zeigt eine Liste aller verwendeter "Interrupts". Wenn sich mehrere Geräte zuviele von ihnen teilen, ist das schlecht.</td></tr>
 <tr><td colspan="3">- "On screen debug output" (die Bootloader Debug Option zur Ausgabe auf dem Bildschirm).</td></tr>
 </table>
 <p>Die ersten vier dieser Befehle sind im Terminal einzugeben. Mit dem Zusatz "<span class="cli"> &gt; output.txt</span>" an den Befehl wird dessen Ausgabe in die Datei "output.txt" gespeichert, die dann an den Fehlerbericht angehängt werden kann.</p>
 <h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="next" name="next">Bug gemeldet, und dann?</a></h2>
 <p>Nachdem ein Fehler gemeldet wurde wird sich ein Entwickler ihm annehmen und bewerten. Da es sich bei allen Entwicklern um Freiwillige handelt, die in ihrer Freizeit programmieren, kann es durchaus etwas dauern, bis man eine Rückmeldung erhält. Je mehr Informationen man einer Fehlermeldung beifügt oder nachreicht, um so leichter ist es für den Programmierer, diesen zu beheben.</p>
 <p>Wenn man einen Fehler gemeldet hat ist es damit nicht abgeschlossen, eigentlich ist es erst der Anfang und man wird Teil des Entwicklungs-Prozesses von Haiku. Es ist durchaus möglich und eigentlich auch zu erwarten, dass sich ein Entwickler meldet, um näheres zu den Umständen des Fehler-Reports zu erfahren. Hier gilt wieder: je mehr man dem Entwickler helfen kann, um so leichter tut er sich mit der Fehlerbehebung. Erst wenn der Fehler als 'fixed' - also behoben - markiert ist, kann man sich zurücklehnen, mit dem guten Gefühl etwas beigetragen zu haben.</p>
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 *
 -->
@@ -46,49 +47,109 @@
 <div id="content">
 <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>Getting a Trac account</h2>
+<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>Creating a bug report</h2>
+<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 '<i>About This System...</i>' from the Deskbar menu.</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 make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
+	<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>
-<h3>Software Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
+<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>
-<h3>Hardware Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
+<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><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
+<li><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><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
+<li><p>The system reboots spontaneously.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
+<li><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><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</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><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
+<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>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
+<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>Kernel Debugging Land - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<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 />
-<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
+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>
-<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
+<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>
-<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<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>
-<h2>What's next?</h2>
+<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/en/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
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 * Translators:
 *		miguel~1.mx
@@ -22,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>Guía del usuario</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -47,50 +48,111 @@
 <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>Reportar fallos</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>Reportar fallos</h1>
 <p>Ya que nuestros desarrolladores no pueden verificar todas las combinaciones de hardware, ni todas las posibles maneras de interactuar con el sistema operativo, confiamos que los usuarios nos den retroalimentación sobre cómo funcionan las cosas de su lado. Dado que Haiku todavía es muy joven, muy probablemente encontrará fallos. Le agradecemos por tomarse el tiempo para reportarlos. Juntos podemos mejorar a Haiku, bit a bit.</p>
 <p>Para mantener nuestro rastreador de fallos efectivo, es esencial supeditarse a la <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Etiqueta del rastreador de fallos</a>.</p>
-<h2>Obtener una cuenta de Trac</h2>
+<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>Para llenar un reporte, necesita tener una cuenta en <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">el Rastreador de fallos de Haiku</a>.<br />
 Cuando se cree una cuenta nueva, asegurese de <b>proporcionar su correo electrónico</b> pues es necesario obtener privilegios de modificación básica del reporte. Asegúrese de <b>comprobar su carpeta de correo no deseado (spam)</b> brevemente después, ya que a menudo toda verificación de correo importante termina allí.</p>
-<h2>Crear un reporte de fallo</h2>
+<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>Antes de reportar un fallo, por favor <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">asegúrese</a> que aún no exista. Puede también usar la función de <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">búsqueda</a> para esto.<br />
 Tras haber establecido que es un fallo nuevo, haga su información tan puntual como sea posible:</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>Incluya información básica tal como dónde está probando a Haiku (sobre hardware real, en VMWare, en QEMU, etc.).</p></li>
-	<li><p>Mencione cuál revisión de <acronym title="Subversion, the source code management system we use">SVN</acronym> esté corriendo. Puede encontrar esta información en '<i>About This System...</i>' (Acerca de este sistema) desde el menú Deskbar.</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>Describa el problema que esté experimentando. Intente ser tan preciso como pueda: describa el comportamiento actual, y el comportamiento esperado.</p></li>
 	<li><p>Describa qué pasos necesita realizar para exponer el fallo. Esto ayudará a los desarrolladores a reproducir el fallo.</p></li>
-	<li><p>Adjunte tanta información como tenga. Si es un fallo de interfaz de usuario, o un fallo en una de las aplicaciones, intente hacer una captura de pantalla (la tecla <span class="key">Impr pant</span> guarda un <acronym title="Portable Network Graphics image format">PNG</acronym> en <span class="path">/boot/home/</span>).</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>
-<h3>Fallos de software</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Cuando falla una aplicación, debería invocar el depurador desde la alerta que aparece. Al ingresar <span class="cli">bt</span> dentro de la terminal de depuración ejecutada, se crea un "backtrace" que debiera copiarse dentro del reporte de fallo.</p>
+<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>
-<h3>Fallos de hardware</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Cuando se enfrente a fallos relacionados con hardware/controladores, debería adjuntarse la siguiente información:</p>
+<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><span class="cli">listdev</span> - un listado detallado de su hardware, incluyendo las IDs de fabricante y dispositivo PCI, similar a los comandos <span class="cli">lshw</span> y <span class="cli">lspci</span> de Linux.</li>
+<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><span class="cli">listusb -v</span> - asumiendo que el conflicto se relacione con USB, de manera similar a <span class="cli">lsusb</span>.</li>
+<li><p>The system reboots spontaneously.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - el historial de sucesos de sitema primario utilizado por Haiku, análogamente a la pantalla de depuración durante el arranque. Con el comando <span class="cli">open</span> se puede acortar la parte relevante de los sucesos de sistema en un editor de textos.</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><span class="cli">listimage | grep drivers/</span> - lista todos los controladores utilizados.</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><span class="cli">ints</span> - sólo disponible en la <i>Tierra de depuración del núcleo</i> (ve debajo). Muestra el uso de interrupciones. No debería haber demasiados que se compartan por dispositivos diferentes.</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>Se pueden ingresar estos comandos en la Terminal. Agregue un <span class="cli"> &gt; output.txt</span> tras un comando, y se hará una operación de tubería dentro de un texto llamado "output.txt" que se puede adjuntar al reporte de fallos o correo electrónico.</p>
+<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>Tierra de depuración del núcleo - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Cuando algún componente de sistema de muy bajo nivel deja de funcionar, se puede terminar en el depurador de núcleo (KDL por sus siglas en inglés, Kernel Debugging Land). También puede ingresarse deliberadamente con <span class="key">ALT</span> <span class="key">PetSis</span> <span class="key">D</span> (siendo <span class="key">PetSis</span> el mismo botón que <span class="key">Impr pant</span> en la mayoría de los teclados).</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<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 />
-<li><span class="cli">co</span> - saldrá de KDL y continuará la operación del sistema, si es posible.</li>
+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>
-<li><span class="cli">int</span> - mostrará el uso de interrupciones (como se describió arriba).</li>
+<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>
-<li><span class="cli">bt</span> - muestra el "backtrace", detallando dónde exactamente sucedió el fallo.</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<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>
-<h2>¿Qué sigue?</h2>
+<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/es/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>Después que un fallo se ha reportado, un desarrollador verá el reporte e intentará clasificarlo. Recuerde, todos somos voluntarios, y por ello, algunas veces un fallo pudiera estar sin responderse por un tiempo. Agregar nueva información cuando esté disponible usualmente ayuda a que se escoja un fallo más rápidamente, pero no intente 'levantar' el fallo agregando comentarios no descriptivos.</p>
 <p>Recuerde, reportar un fallo no es algo en lo que tome un poquito de tiempo y sea todo. Si se reporta un fallo, se vuelve parte del proceso de desarrollo de Haiku. Los desarrolladores podrían llegar con preguntas mientras intentan arreglar el fallo reportado. Por favor, permanezca atento para responderlas. Considere su participación 'terminada' cuando el fallo se marque como 'arreglado'.</p>
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 * Translators:
 *		Loïc
@@ -23,7 +24,7 @@
 <body>
 <div id="banner">
-<div><span>Guide de l’utilisateur</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -48,52 +49,117 @@
 <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>Signaler les bogues</td></tr>
 <tr class="index"><td><a href="#account">Obtenir un compte Trac</a><br />
 <a href="#report">Créer un rapport de bogue</a><br />
 <a href="#app">Bogues logiciels</a><br />
 <a href="#server">Bogues dans les Serveurs</a><br />
 <a href="#kernel">Bogues du noyau</a><br />
 <a href="#kdl">Le mode débogage noyau - KDL</a><br />
 <a href="#syslog">Le journal système</a><br />
 <a href="#onscreen">Les sorties écran du débogueur</a><br />
 <a href="#hardware">Bogues liés au matériel ou aux pilotes</a><br />
 <a href="#next">Et après ?</a></td></tr>
 </table>
 <h1>Signaler les bogues</h1>
 <p>Comme il est impossible pour nos développeurs de tester toutes les combinaisons de matériel, ni tous les cas de figure pouvant interagir avec le système d'exploitation, nous comptons sur les utilisateurs pour nous dire si les choses fonctionnent pour eux. puisque Haiku est encore tout jeune, il est très probable que vous rencontriez des bogues. Nous vous remercions de bien vouloir prendre le temps de nous les signaler. Ensemble, nous pourrons, petit à petit, améliorer Haiku.</p>
 <p>Afin que le suivi de nos bogues reste efficace, il est essentiel de respecter l'<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Étiquette de suivi des bogues</a>.</p>
-<h2>Obtenir un compte Trac</h2>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="account" name="accout">Obtenir un compte Trac</a></h2>
 <p>Pour remplir un rapport (ticket), vous aurez besoin d’un compte utilisateur sur le <a href="http://dev.haiku-os.org/register" title="Traqueur de bogues de Haiku">Traqueur de bogues de Haiku</a>.<br />
 Lors de la création d’un nouveau compte, pensez à <b>indiquer votre adresse e-mail</b> afin d’obtenir les privilèges basiques de gestions des tickets. N’oubliez pas de <b>Vérifier votre dossier de pourriel</b> après, car les e-mails de vérifications s’y retrouvent souvent.</p>
-<h2>Créer un rapport de bogue</h2>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="report" name="report">Créer un rapport de bogue</a></h2>
 <p>Avant de rapporter un bogue, veuillez <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">vérifier</a> qu’il n’est pas déjà répertorié. Vous pouvez aussi utiliser la <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">fonction de recherche</a> pour cela.<br />
 Après vous être assuré que votre bogue est unique, obtenez des informations précises sur votre environnement :</p>
 <ul>
 	<li><p>Essayez de reproduire votre problème avec la version actuelle d'Haiku. Des <a href="http://haiku-files.org/">images préfabriqués</a> sont disponible à cet usage.</p></li>
 	<li><p>Indiquez comment vous testez Haiku (sur machine réelle, dans VMware, dans Qemu…)</p></li>
-	<li><p>Indiquez quelle révision <acronym title="Subversion, le système de gestion de code source que nous utilisons">SVN</acronym> de Haiku vous utilisez. Vous pouvez trouver des informations à ce sujet dans le menu « <i>About This System…</i> » de la Deskbar.</p></li>
+	<li><p>Indiquez quelle révision <acronym title="Subversion, le système de gestion de code source que nous utilisons">SVN</acronym> de Haiku vous utilisez. Vous pouvez trouver cette information dans le menu « <i>About This System…</i> » de la Deskbar.
 N'oubliez pas de mentionner de quel type de construction est issu le système Haiku que vous testez (gcc2, gcc4, gcc2hybrid, gcc4hybrid). 
 Les images téléchargeables sont nommés en conséquence. Si vous avez construit l'image vous-même, vous devriez savoir comment vous l'avez compilé.</p></li>
 	<li><p>Décrivez le problème que vous rencontrez. soyez aussi précis que possible : décrivez le comportement réel, et celui que vous attendiez.</p></li>
 	<li><p>Décrivez les actions que vous avez effectuées avant de faire ressortir le bogue. Cela permettra aux développeurs de le reproduire.</p></li>
-	<li><p>Attachez au rapport le plus d’informations possibles. Si le bogue concerne l’interface graphique ou une application, essayez de faire une capture d’écran (la touche <span class="key">IMPR ÉCRAN</span> créera une image <acronym title="Portable Network Graphics image format">PNG</acronym> dans le dossier <span class="path">/boot/home/</span>).</p></li>
+	<li><p>Attachez au rapport le plus d’informations possibles. Si le bogue concerne l’interface graphique ou une application, essayez de faire une capture d’écran à l'aide de la la touche <span class="key">IMPR ÉCRAN</span>.</p></li>
 </ul>
-<h3>Bogues logiciels</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Lorsqu'une application se plante, vous devez appeler le débogueur depuis le message d'alerte qui s'affiche. Saisissez <span class="cli">bt</span> dans le Terminal de débogage qui est lancé. Vous obtiendrez ainsi une trace de la « pile d'appel » (<i>backtrace</i>) que vous devez joindre à votre rapport de bogue.</p>
+<a id="app" name="app">Bogues logiciels</a></h2>
 <p>Lorsqu'une application se plante, vous devez appeler le débogueur depuis le message d'alerte qui s'affiche. 
 Une fenêtre de Terminal devrait s'ouvrir avec gdb (le débogueur GNU) lancé à l'intérieur.
 En saisissant <span class="cli">bt</span>, vous obtiendrez ainsi une trace de la « pile d'appel » (<i>backtrace</i>) que vous devez joindre en intégralité (y compris la partie précédant l'appel à la commande <span class="cli">bt</span>) à votre rapport de bogue.</p>
-<h3>Bogues matériels</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Lorsque le bogue concerne un matériel ou son pilote, vous devez fournir les renseignements suivants :</p>
+<a id="server" name="server">Bogues dans les serveurs</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">Bogues du noyau</a></h2>
 <p>Les bogues du noyau sont habituellement ceux qui ont les effets les plus graves, tout en étant les plus difficiles à déboguer. Il existe différents types de symptômes, qui révèlent généralement un problème du noyau ou d'un pilote :</p>
 <ul>
-<li><span class="cli">listdev</span> - fait une liste détaillée de votre matériel, en y incluant les identifiants PCI des fournisseurs, à la manière de <span class="cli">lshw</span> ou <span class="cli">lspci</span> dans GNU/Linux .</li>
+<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><span class="cli">listusb -v</span> - en supposant que c'est un problème lié à l'USB, comme le fait <span class="cli">lsusb</span>.</li>
+<li><p>Le système redémarre spontanément.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - 
+<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>
-le système de journal d’événements principal de Haiku, similaire au déboguage sur écran durant le démarrage. En l’ouvrant dabs un éditeur de texte avec la commande <span class="cli">open</span> vous pourrez n’en conserver que la partie utile.</li>
+<li><p>Le système ne démarre pas correctement. Il peut redémarrer spontanément ou s'arrêter à un moment donné (par exemple au niveau d'une icône de l'écran de démarrage). Dans ce dernier cas vous pouvez essayer aussi <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
-<li><span class="cli">listimage | grep drivers/</span> - liste tous les drivers utilisés.</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>
 <li><span class="cli">ints</span> - seulement disponible dans le <i>mode débogage du noyau</i> (voir ci-dessous). Montre l'utilisation des interruptions. 
 Il ne devrait pas y avoir trop d'interruptions partagées par plusieurs périphériques.</li>
 </ul>
-<p>Ces commandes peuvent être entrées dans le Terminal. Si vous ajoutez <span class="cli"> &gt; sortie.txt</span> après une commande, sa sortie sera redirigée dans un fichier texte nommé « sortie.txt » que vous pourrez attachez à votre rapport de bogue ou e-mail.</p>
+<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>Le mode débogage noyau - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Lorsque certains composants systèmes de bas niveau se plantent, vous pouvez être envoyé dans le débogueur du noyau. Vous pouvez également y entrer volontairement avec <span class="key">ALT</span><span class="key">SYST</span><span class="key">D</span> (<span class="key">SYST</span> correspond à <span class="key">IMPR ÉCRAN</span> sur la plupart des claviers). Attention : l'ordre des touches compte.</p>
+<a id="kdl" name="kdl">Le mode débogage noyau - KDL</a></h3>
-<ul>
+<p>Si le système n'entre pas de lui même en mode déboguage du noyau (KDL) vous pouvez le faire volontairement en invoquant le raccourci clavier <span class="key">ALT</span> <span class="key">Syst</span> <span class="key">D</span> Attention : l'ordre des touches compte (<span class="key">SYST</span> correspond à <span class="key">Impr Écran</span> sur la plupart des claviers).
-<li><span class="cli">co</span> - sortira du KDL et reprendra l’exécution normale, si possible.</li>
+Notez bien que votre clavier pourrait ne pas fonctionner en mode déboguage du noyau. Alors que les claviers PS/2
-<li><span class="cli">int</span> - affichera l’utilisation des interruptions (comme décrit ci-dessus).</li>
+ne posent pas de problème, les claviers USB connecté à un controleur UHCI ne fonctionne que si vous être entré au moins une fois en mode débogage à l'aide du raccourci clavier. Pour le moment l'USB OHCI n'est pas supporté.</p>
-<li><span class="cli">bt</span> - affiche une trace de déboguage (backtrace), indiquant exactement comment le plantage s’est produit.</li>
+<p>KDL est, par lui-même, une sorte d'interpréteur de commande. On peut exécuter des instructions pour afficher des informations sur le système. Les commandes suivantes pourraient vous intéresser :</p>
-</ul>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
 <tr><td><span class="cli">bt</span> (alias sc)</td><td> </td><td>Affiche une trace de débogage (backtrace), Faites systematiquement cette commande quand le système entre dans le débogueur de lui même.</td></tr>
 <tr><td><span class="cli">ints</span></td><td> </td><td>Affichera les interruptions matérielles qui sont gérées, ainsi que celles qui sont ignorées.</td></tr>
 <tr><td class="onelinetop"><span class="cli">co</span> (alias continue)</td><td> </td><td>Quitte le débogueur pour reprendre, si possible, les opérations normales du système.</td></tr>
 <tr><td><span class="cli">reboot</span></td><td> </td><td>Redémarre le système immédiatement. Vous perdrez toutes les données non enregistrées, ainsi que celles qui ont été enregistrés, mais qui n'ont pas encore été écrites sur le disque.</td></tr>
 </table>
 <p>Pour plus d'information, consultez l'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>
-<h2>Et après ?</h2>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="syslog" name="syslog">Le journal système</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">Les sorties écran du débogueur</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/fr/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">Bogues liés au matériel ou aux pilotes</a></h2>
 <p>Lorsque le bogue concerne un matériel ou son pilote, veuillez attacher au rapport, un fichier texte contenant les renseignements suivants :</p>
 <table summary="layout" border="0" cellpadding="2" cellspacing="0">
 <tr><td>- <span class="cli">listdev</span></td><td> </td><td>Fait une liste détaillée de votre matériel, en y incluant les identifiants des périphériques PCI et de leurs fabriquants, à la manière de <span class="cli">lshw</span> ou <span class="cli">lspci</span> dans GNU/Linux.</td></tr>
 <tr><td>- <span class="cli">listusb -v</span></td><td> </td><td>Fait comme <span class="cli">lsusb</span> en supposant que c'est un problème lié à l'USB.</td></tr>
 <tr><td>- <span class="cli">open /var/log/syslog</span></td><td> </td><td>Le journal système principal utilisé par Haiku, semblable à celui de l'écran de débogage pendant le démarrage. Avec la commande <span class="cli">open</span>, vous pouvez modifier ce journal dans un éditeur de texte pour n'en conserver que la partie la plus pertinente.</td></tr>
 <tr><td class="onelinetop">- <span class="cli">listimage | grep drivers/</span></td><td> </td><td>Liste tous les drivers utilisés.</td></tr>
 <tr><td>- <span class="cli">ints</span></td><td> </td><td>Seulement disponible dans le <i>mode débogage du noyau</i> (voir ci-dessous). Montre l'utilisation des interruptions. 
 Il ne devrait pas y avoir trop d'interruptions partagées par plusieurs périphériques.</td></tr>
 <tr><td colspan="3">- Les sorties écran du débogueur (une option de mode sans échec du démarrage).</td></tr>
 </table>
 <p>Les 4 premières commandes sont à exécuter dans le Terminal. Si vous ajoutez <span class="cli"> &gt; sortie.txt</span> après une commande, sa sortie sera redirigée dans un fichier texte nommé « sortie.txt » que vous pourrez attachez à votre rapport de bogue ou e-mail.</p>
 <h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
 <a id="next" name="next">Et après ?</a></h2>
 <p>Une fois le bogue rapporté, un développeur le consultera et essayera de le cataloguer. Retenez que tous les développeurs sont des volontaires; un long délai avant réponse peut s’écouler après le rapport de bogue. L’ajout de nouvelles informations une fois celles-ci disponibles peut généralement permettre à un bogue d’être analysé plus rapidement. Néanmoins, n’essayez pas de « faire remonter » un bogue en ajoutant des commentaires non pertinents.</p>
 <p>N’oubliez pas, le rapport d’un bogue ne se limite pas à sa soumission. Une fois cette tâche faite, vous ferez partie du processus de développement de Haiku. Les développeurs pourront vous poser des question pour essayer de résoudre votre bogue. Merci de rester disponible pour y répondre. Vous pourrez considérer votre travail « terminé » quand le bogue sera marqué comme étant « corrigé ».</p>
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 *
 -->
@@ -47,49 +48,109 @@
 <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>
 <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>Getting a Trac account</h2>
+<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>Creating a bug report</h2>
+<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 '<i>About This System...</i>' from the Deskbar menu.</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 make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
+	<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>
-<h3>Software Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
+<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>
-<h3>Hardware Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
+<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><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
+<li><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><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
+<li><p>The system reboots spontaneously.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
+<li><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><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</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><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
+<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>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
+<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>Kernel Debugging Land - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<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 />
-<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
+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>
-<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
+<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>
-<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<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>
-<h2>What's next?</h2>
+<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/it/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
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 *
 -->
@@ -47,49 +48,109 @@
 <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>Getting a Trac account</h2>
+<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>Creating a bug report</h2>
+<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 '<i>About This System...</i>' from the Deskbar menu.</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 make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
+	<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>
-<h3>Software Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
+<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>
-<h3>Hardware Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
+<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><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
+<li><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><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
+<li><p>The system reboots spontaneously.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
+<li><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><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</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><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
+<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>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
+<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>Kernel Debugging Land - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<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 />
-<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
+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>
-<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
+<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>
-<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<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>
-<h2>What's next?</h2>
+<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/jp/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
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 *
 -->
@@ -47,49 +48,109 @@
 <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>Getting a Trac account</h2>
+<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>Creating a bug report</h2>
+<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 '<i>About This System...</i>' from the Deskbar menu.</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 make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
+	<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>
-<h3>Software Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
+<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>
-<h3>Hardware Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
+<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><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
+<li><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><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
+<li><p>The system reboots spontaneously.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
+<li><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><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</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><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
+<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>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
+<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>Kernel Debugging Land - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<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 />
-<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
+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>
-<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
+<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>
-<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<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>
-<h2>What's next?</h2>
+<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/pt_PT/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
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 * Translators:
 *		Michael Smirnov
@@ -23,7 +24,7 @@
 <body>
 <div id="banner">
-<div><span>Руководство пользователя</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -48,50 +49,111 @@
 <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>Отчёт об ошибках (багах)</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>Отчёт об ошибках (багах)</h1>
 <p>Так как наши разработчики не в состоянии проверить все комбинации компьютерных комплектующих и программных средств при их работе в Haiku, то мы полагаемся на пользователей, надеясь, что вы сообщите нам об обнаруженных ошибках, которых, ввиду молодости Haiku, может быть немало. Мы будем благодарны вам за потраченное на составление отчёта время, только вместе мы сможем сделать Haiku лучше.</p>
 <p>Для продуктивной работы c системой отслеживания ошибок (багтрекером) важно соблюдать принятый в нём <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">этикет</a>.</p>
-<h2>Получение аккаунта в Trac</h2>
+<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>Чтобы создать новый багрепорт, у вас должен быть заведён аккаунт в <a href="http://dev.haiku-os.org/register" title="Регистрация в багтрекере Haiku">багтрекере Haiku</a>.<br />
 Создавая новый аккаунт <b>обязательно введите адрес электронной почты</b>, так как на него будут приходить все сведения, связанные с изменением багрепорта. Убедитесь, что приходящие с багтрекера письма <b>не помечаются как спам,</b> так как это вполне возможно.</p>
-<h2>Создание отчёта об ошибках</h2>
+<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>Прежде чем сообщать об ошибке, пожалуйста, <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Eтекст,+который+вы+ищите&amp;order=priority">убедитесь</a>, что аналогичного багрепорта ещё не существует. Для этого также можно воспользоваться функцией <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">поиска</a>.<br />
 После того как вы установили, что подобных багрепортов не имеется, то оформите вашу информацию как можно точнее:</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>Включите информацию о том как вы тестируете Haiku (на реальном компьютере, в эмуляторе VMWare, QEMU, и т. д.).</p></li>
-	<li><p>Укажите какую <acronym title="Subversion - система управления версиями, используемая нами">SVN</acronym> ревизию Haiku вы используете. Эту информацию можно найти в '<i>Сведениях о системе (About This System)...</i>' в меню Deskbar.</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>Опишите проблему, с которой вы столкнулись, попытайтесь описать её наиболее точно: как именно она проявилась, и как правильно должен бы был действовать проблемный объект при её отсутствии.</p></li>
 	<li><p>Расскажите какие шаги нужно выполнить для её возникновения, что поможет разработчикам воспроизвести эту ошибку.</p></li>
-	<li><p>Прикрепите всю имеющуюся информацию. Если это ошибка графического интерфейса или баг в каком-либо приложении, то попытайтесь сделать скриншот (клавиша <span class="key">PrintScreen</span> сохраняет PNG изображение в папке <span class="path">/boot/home/</span>).</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>
-<h3>Программные ошибки</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Когда приложение аварийно завершилось, вы должны использовать автоматически открывающийся отладчик. Введя в окне терминала с дебагером <span class="cli">bt</span>, вы создаёте "трассировку", которую необходимо скопировать в ваш багрепорт.</p>
+<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>
-<h3>Аппаратные ошибки</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Если вы столкнулись с ошибкой работы оборудования и/или драйвера, то вы должны приложить следующую информацию:</p>
+<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><span class="cli">listdev</span> - подробный список оборудования, включающий ID поставщиков и отдельных устройств, схожа с командами Linux <span class="cli">lshw</span> и <span class="cli">lspci</span>.</li>
+<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><span class="cli">listusb -v</span> - при ошибке, связанной с USB, аналогична команде <span class="cli">lsusb</span>.</li>
+<li><p>The system reboots spontaneously.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - основной системный лог, используемый Haiku, сродни выводимой на экран отладочной информации при загрузке в соответствующем режиме. С командой <span class="cli">open</span> можно вырезать нужную часть лога в текстовом редакторе.</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><span class="cli">listimage | grep drivers/</span> - список всех задействованных драйверов.</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><span class="cli">ints</span> - доступна только в режиме <i>Царства отладки ядра (Kernel Debugging Land - KDL)</i> (см. ниже), отображает используемые прерывания. Не должно быть слишком много устройств, использующих одно прерывание.</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>Все эти команды вводитятся в терминале, если не указано иное. Если добавить <span class="cli"> &gt; output.txt</span> после команды, то результат её работы сохранится в текстовый файл "output.txt", который можно прикрепить к своему сообщению об ошибках или отправить по электронной почте.</p>
+<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>Царство отладки ядра - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>Когда какой-либо системный низкоуровневый компонент вызывает фатальную ошибку, то вы, с большой долей вероятности, окажетесь в отладчике ядра. Также он может быть вызван намеренно при нажатии на клавиши <span class="key">ALT</span>+<span class="key">SysReq</span>+<span class="key">D</span> (клавиша <span class="key">SysReq</span> называется <span class="key">PrintScreen</span> на большинстве клавиатур).</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<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 />
-<li><span class="cli">co</span> - выведет систему из KDL и продолжит нормальную работу Haiku, если это возможно.</li>
+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>
-<li><span class="cli">int</span> - отобразит используемые прерывания (как описано выше).</li>
+<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>
-<li><span class="cli">bt</span> - покажет трассировку, уточняющую где именно произошла ошибка.</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<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>
-<h2>Что дальше?</h2>
+<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/ru/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>После того как багрепорт отправлен, разработчик рассмотрит вашу ошибку и попытаться классифицировать ее. Помните, что мы все добровольцы, и  иногда багрепорт может оставаться без ответа некоторое время. Добавление новой информации к этой ошибке помогает исправить её быстрее, но не пытайтесь увеличить её значимость, добавляя не относящиеся к делу комментарии.</p>
 <p>Помните, что отправка багрепорта, на который вы потратили некоторое время - это ещё полдела, и желательно чтобы вы следили за его состоянием. Только в этом случае вы внесёте ощутимую часть в процесс развития Haiku. У разработчиков могут возникнуть вопросы, относящиеся к багу во время его исправления, пожалуйста, не игнорируйте их, постаравшись как можно подробней ответить. Считайте свое участие законченным, только когда ошибка приобретёт статус "исправлено (fixed)".</p>
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 *
 -->
@@ -47,49 +48,109 @@
 <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>Getting a Trac account</h2>
+<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>Creating a bug report</h2>
+<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 '<i>About This System...</i>' from the Deskbar menu.</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 make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
+	<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>
-<h3>Software Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
+<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>
-<h3>Hardware Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
+<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><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
+<li><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><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
+<li><p>The system reboots spontaneously.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
+<li><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><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</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><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
+<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>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
+<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>Kernel Debugging Land - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<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 />
-<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
+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>
-<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
+<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>
-<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<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>
-<h2>What's next?</h2>
+<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/sv_SE/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
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 *
 -->
@@ -47,49 +48,109 @@
 <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>Getting a Trac account</h2>
+<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>Creating a bug report</h2>
+<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 '<i>About This System...</i>' from the Deskbar menu.</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 make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
+	<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>
-<h3>Software Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
+<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>
-<h3>Hardware Bugs</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
+<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><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
+<li><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><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
+<li><p>The system reboots spontaneously.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
+<li><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><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</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><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
+<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>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
+<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>Kernel Debugging Land - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<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 />
-<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
+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>
-<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
+<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>
-<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<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>
-<h2>What's next?</h2>
+<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/uk/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
@@ -4,11 +4,12 @@
 <head>
 <!-- 
 *
- * Copyright 2008-2009, Haiku. All rights reserved.
+ * Copyright 2008-2010, Haiku. All rights reserved.
 * Distributed under the terms of the MIT License.
 *
 * Authors:
- * 		Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki 
+ * 		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>
 * Translators:
 *		Pengphei Han
@@ -22,7 +23,7 @@
 <body>
 <div id="banner">
-<div><span>用户指南</span></div>
+<div><span>User guide</span></div>
 </div>
 <div class="nav">
@@ -47,52 +48,113 @@
 <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>报告错误</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>报告错误</h1>
 <p>由于我们的开发人员不可能测试每种硬件组合和每种不同的系统交互方式，所以我们依赖于用户，通过用户来给予我们Haiku的运行情况。由于Haiku还很年轻，您在使用时很有可能会遇到错误。我们非常感谢您能够分出时间来提交这些错误报告。我们可以共同的一位一位的提高Haiku的性能。</p>
 <p>为了确保我们的错误跟踪系统的有效性，遵守共同的<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">错误报告规范</a>是很有必要的。</p>
-<h2>获取Trac账户</h2>
+<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>为了提交任务单，您需要在<a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku的错误跟踪系统</a>中注册一个账户。
 <br />
 在新建账户时，你需要<b>提供自己的电子邮箱</b> ，否则您将不具有基本的任务单修改权限。之后，您一定要保证<b>检查您的垃圾邮件文件夹</b>，因为所有重要的验证邮件都会被发送到那儿去。</p>
-<h2>创建错误报告</h2>
+<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>在报告一个错误之前，请您<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">确保</a>该错误报告之前不存在。你可以使用<a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">查找</a>功能来查找其是否存在。
 <br />
 在确定它是一个独特的错误之后，您需要尽可能的找出有关的详细信息：</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>包括基本的信息，例如以何种方式测试Haiku（利用真实的硬件，VMware，还是QEMU）。</p></li>
-	<li><p>提及您正在运行的系统的 <acronym title="Subversion, the source code management system we use">SVN</acronym> 发布版本。你可以在桌面栏菜单中的 '<i>About This System...</i>' 中找出相关信息。</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>描述您所遇到的问题。尽量把问题讲得精确和明白：描述详细的系统行为反馈，和您期望的反馈。</p></li>
 	<li><p>描述暴露该错误所需要的操作步骤。这将会有助于开发者重现该错误，并对其进行修复和完善。</p></li>
-	<li><p>附带你所掌握的尽可能多的信息。如果是一个GUI错误，或者图形程序错误，尽量附带出现错误时的屏幕截图。（<span class="key">PRINT</span> 键保存了一个<acronym title="Portable Network Graphics image format">PNG</acronym> 图像到 <span class="path">/boot/home/</span>）。</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>
-<h3>软件错误</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>如果出现了程序崩溃，您应该从弹出的警告窗口中启动调试程序。 在启动的调试终端中，输入<span class="cli">bt</span>，你将会创建关于调试信息的“回溯”，然后你应该把它复制到您的错误报告中。</p>
+<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>
-<h3>硬件错误</h3>
+<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>如果遇到了硬件或者驱动相关的错误，您应该附带下列信息：</p>
+<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><span class="cli">listdev</span> - 有关您的硬件的详细列表，包括提供商和PCI ID。类似于Linux下的 <span class="cli">lshw</span> 和 <span class="cli">lspci</span> 。</li>
+<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><span class="cli">listusb -v</span> - 如果存在USB相关的问题；类似于Linux下的 <span class="cli">lsusb</span>。</li>
+<li><p>The system reboots spontaneously.</p></li>
-<li><span class="cli">open /var/log/syslog</span> - Haiku主要的系统日志，近似于在启动期间的屏幕调试。使用 <span class="cli">open</span> 命令，您可以把在文本编辑器中把系统日志中重要的部分裁剪下来。</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><span class="cli">listimage | grep drivers/</span> - 列出所有使用的驱动。</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><span class="cli">ints</span> - 只在 <i>内核调试状态</i> 下才可用（参见下文）。它显示了中断的使用情况，而由不同的硬件所共享的中断并不是很多。</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>您在终端中输入这些命令，在每个命令后面添加 <span class="cli"> &gt; output.txt</span> 。 然后命令输出的结果就被重定向到一个称为 “output.txt” 的文本文件；您可以把它附带到您的错误报告或者邮件中。</p>
+<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>内核调试 - KDL</h3>
+<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
-<p>如果某些底层的系统组件发生了崩溃，您可能就会进入了内核调试状态。您也可以有意识的使用 <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span>（<span class="key">SysReq</span> 在多数键盘中都是 <span class="key">PRINT</span>）来进入内核调试状态。</p>
+<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
-<ul>
+<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 />
-<li><span class="cli">co</span> - 如果可能的话，系统将会结束内核调试状态，返回正常的系统操作界面。</li>
+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>
-<li><span class="cli">int</span> - 将会显示中断使用情况（如上所述）。</li>
+<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>
-<li><span class="cli">bt</span> - 显示一个调试信息的回溯，详细的给出了崩溃发生的地方。</li>
+<table summary="layout" border="0" cellpadding="2" cellspacing="0">
-</ul>
+<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>
-<h2>下一步？</h2>
+<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/zh_CN/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>在您提交了错误报告之后，开发人员将会检查您的错误，然后尝试进行修复。但是需要注意的是，我们所有的人员都是志愿者，有时候一个错误报告可能会很长时间没有人来进行回答。如果可以的话，添加新的信息将会有助于早点修复错误，但是请不要添加非描述性的评论来将“炒热”该错误。</p>
 <p>切记，提交错误报告不是花些很少的时间写个报告的事。如果您提交了一个错误，然后您属于Haiku开发过程中的一部分。开发人员在解决您的错误过程中可能会遇到问题，因此请你一定要始终关注该错误，然后回答相关的问题。如果该问题没有“fixed”，你的任务就没有“done”。</p>