i2p/haiku-beta6
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial import of the user guide translations from http://userguide.haikuzone.net. Thanks to Vincent for providing all the necessary tools and to all translators for their work so far!

Browse Source 
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@35067 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Joachim Seemer
2010-01-14 07:00:47 +00:00
parent bcc2c157a1
commit ee7dedc859
1233 changed files with 58973 additions and 4098 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/welcome/de/bugreports.html
+103
View File
@@ -0,0 +1,103 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki
* Humdinger <[email protected]>
* Translators:
* Matthias
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Fehler melden</title>
<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../../images/flags/de.png" alt="" /> Deutsch</li>
<li><a href="../fr/bugreports.html"><img src="../../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../it/bugreports.html"><img src="../../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/bugreports.html"><img src="../../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/bugreports.html"><img src="../../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/bugreports.html"><img src="../../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="../jp/bugreports.html"><img src="../../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../en/bugreports.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_de.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h1>Fehler melden</h1>
<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>
<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>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>
<h2>Einen Fehlerbericht erstellen</h2>
<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 />
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>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>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>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>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>
</ul>
<h3>Fehler in Anwendungen</h3>
<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>
<h3>Fehler auf Grund Hardware</h3>
<p>Wenn ein Fehler gemeldet wird, der Hardware oder Treiber betrifft, sollten mindestens diese Informationen an den Fehlerbericht angehängt werden:</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><span class="cli">listusb -v</span> - bei einem Fehler im Zusammenhang mit USB; ähnlich dem Befehlt <span class="cli">lsusb</span>.</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><span class="cli">listimage | grep drivers/</span> - eine Auflistung aller verwendeter Treiber.</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>
</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>
<h3>Kernel Debugging Land - KDL</h3>
<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>
<ul>
<li><span class="cli">co</span> - beendet das KDL und das System läuft - soweit möglich - normal weiter.</li>
<li><span class="cli">int</span> - zeigt die verwendeten Interrupts (wie oben beschrieben).</li>
<li><span class="cli">bt</span> - zeigt einen backtrace wo genau der Fehler aufgetreten ist.</li>
</ul>
<h2>Fehler gemeldet, und dann?</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>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_de.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/en/bugreports.html
+68 -30
View File
@@ -1,6 +1,5 @@
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"../../html-dtd/xhtml1-strict.dtd">
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
@@ -9,7 +8,7 @@
* Distributed under the terms of the MIT License.
*
* Authors:
* Whoever wrote http://dev.haiku-os.org/wiki (Niels Reedijk?)
* Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki
* Humdinger <[email protected]>
*
-->
@@ -20,46 +19,85 @@
</head>
<body>
<div class="logo">
<img src="./images/logo.png" alt="logo" class="noprint" id="logo" name="logo" />
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="topnav">
<p><a href="../welcome.html" class="uplink">Welcome</a></p>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../../images/flags/gb.png" alt="" /> English</li>
<li><a href="../fr/bugreports.html"><img src="../../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/bugreports.html"><img src="../../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/bugreports.html"><img src="../../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/bugreports.html"><img src="../../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/bugreports.html"><img src="../../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/bugreports.html"><img src="../../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="../jp/bugreports.html"><img src="../../images/flags/jp.png" alt="" />日本語</a></li>
</ul>
<span>
<a href="../welcome_en.html" class="uplink">Welcome</a>
</span></div>
</div>
<div class="content">
<div id="content">
<div>
<div class="title">Reporting bugs</div>
<h1>Reporting bugs</h1>
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on you to give us some input on how things work at your end. Since this is a very early product, it is very likely that you will encounter bugs. We thank you for taking the time to report these.<br /><br />
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>. Besides, please follow these guidelines to create helpful bug reports:</p>
<ol>
<li><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=~text+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.</p></li>
<li><p>After you have established this is a unique bug, make your information as accurate as possible:
<ul>
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
<h2>Getting a Trac account</h2>
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
<h2>Creating a bug report</h2>
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">search</a> function for this.<br />
After you have established that it's a unique bug, make your information as accurate as possible:</p>
<ul>
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in '<i>About This System...</i>' from the Deskbar menu.</p></li>
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the <span class="key">PRINT</span> key files a <acronym title="Portable Network Graphics image format">PNG</acronym> into <span class="path">/boot/home/</span>).</p></li>
</ul>
</p>
<p>If it is a hardware problem, include a copy of the <span class="cli">syslog</span> file (just query for "<tt>syslog</tt>" to find it).</p>
<p>Also interesting when dealing with hardware issues, is the output of <span class="cli">listdev</span> and <span class="cli">sysinfo</span>. This will pipe the output into text files that you can attach to your bugreport or email:</p>
<pre class="terminal">listdev &gt; listdev-output.txt
sysinfo &gt; sysinfo-output.txt</pre>
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
</ul>
<h3>Software Bugs</h3>
<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
</li>
<li><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 bugreport.</p></li>
<li><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></li>
<li><p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked as 'fixed'. Together we can improve Haiku, bit by bit.</p></li>
</ol>
<h3>Hardware Bugs</h3>
<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
<ul>
<li><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
<li><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
<li><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</li>
<li><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
</ul>
<p>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
<h3>Kernel Debugging Land - KDL</h3>
<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
<ul>
<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
</ul>
<h2>What's next?</h2>
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
non-descriptive comments.</p>
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
as 'fixed'.</p>
</div>
</div>
<div class="bottomnav">
<p><a href="../welcome.html" class="uplink">Welcome</a></p>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_en.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
docs/welcome/en/images/logo.png
BIN
View File
Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 9.9 KiB

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

Before

Width:  |  Height:  |  Size: 164 B

docs/welcome/it/bugreports.html
+104
View File
@@ -0,0 +1,104 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki
* Humdinger <[email protected]>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Reporting bugs</title>
<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../../images/flags/it.png" alt="" /> Italiano</li>
<li><a href="../fr/bugreports.html"><img src="../../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/bugreports.html"><img src="../../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../ru/bugreports.html"><img src="../../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/bugreports.html"><img src="../../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/bugreports.html"><img src="../../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="../jp/bugreports.html"><img src="../../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../en/bugreports.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_it.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h1>Reporting bugs</h1>
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
<h2>Getting a Trac account</h2>
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
<h2>Creating a bug report</h2>
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">search</a> function for this.<br />
After you have established that it's a unique bug, make your information as accurate as possible:</p>
<ul>
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in '<i>About This System...</i>' from the Deskbar menu.</p></li>
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
</ul>
<h3>Software Bugs</h3>
<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
<h3>Hardware Bugs</h3>
<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
<ul>
<li><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
<li><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
<li><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</li>
<li><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
</ul>
<p>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
<h3>Kernel Debugging Land - KDL</h3>
<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
<ul>
<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
</ul>
<h2>What's next?</h2>
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
non-descriptive comments.</p>
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
as 'fixed'.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_it.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/jp/bugreports.html
+104
View File
@@ -0,0 +1,104 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki
* Humdinger <[email protected]>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Reporting bugs</title>
<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../../images/flags/jp.png" alt="" /> 日本語</li>
<li><a href="../fr/bugreports.html"><img src="../../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/bugreports.html"><img src="../../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/bugreports.html"><img src="../../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/bugreports.html"><img src="../../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/bugreports.html"><img src="../../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/bugreports.html"><img src="../../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="../en/bugreports.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_jp.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h1>Reporting bugs</h1>
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
<h2>Getting a Trac account</h2>
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
<h2>Creating a bug report</h2>
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">search</a> function for this.<br />
After you have established that it's a unique bug, make your information as accurate as possible:</p>
<ul>
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in '<i>About This System...</i>' from the Deskbar menu.</p></li>
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
</ul>
<h3>Software Bugs</h3>
<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
<h3>Hardware Bugs</h3>
<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
<ul>
<li><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
<li><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
<li><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</li>
<li><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
</ul>
<p>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
<h3>Kernel Debugging Land - KDL</h3>
<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
<ul>
<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
</ul>
<h2>What's next?</h2>
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
non-descriptive comments.</p>
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
as 'fixed'.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_jp.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/ru/bugreports.html
+104
View File
@@ -0,0 +1,104 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki
* Humdinger <[email protected]>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Reporting bugs</title>
<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../../images/flags/ru.png" alt="" /> Русский</li>
<li><a href="../fr/bugreports.html"><img src="../../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/bugreports.html"><img src="../../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/bugreports.html"><img src="../../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../es/bugreports.html"><img src="../../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../sv_SE/bugreports.html"><img src="../../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="../jp/bugreports.html"><img src="../../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../en/bugreports.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_ru.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h1>Reporting bugs</h1>
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
<h2>Getting a Trac account</h2>
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
<h2>Creating a bug report</h2>
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">search</a> function for this.<br />
After you have established that it's a unique bug, make your information as accurate as possible:</p>
<ul>
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in '<i>About This System...</i>' from the Deskbar menu.</p></li>
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
</ul>
<h3>Software Bugs</h3>
<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
<h3>Hardware Bugs</h3>
<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
<ul>
<li><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
<li><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
<li><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</li>
<li><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
</ul>
<p>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
<h3>Kernel Debugging Land - KDL</h3>
<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
<ul>
<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
</ul>
<h2>What's next?</h2>
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
non-descriptive comments.</p>
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
as 'fixed'.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_ru.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/sv_SE/bugreports.html
+104
View File
@@ -0,0 +1,104 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki
* Humdinger <[email protected]>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Reporting bugs</title>
<link rel="stylesheet" type="text/css" href="../../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../../images/flags/sv_SE.png" alt="" /> Svensk</li>
<li><a href="../fr/bugreports.html"><img src="../../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="../de/bugreports.html"><img src="../../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="../it/bugreports.html"><img src="../../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="../ru/bugreports.html"><img src="../../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="../es/bugreports.html"><img src="../../images/flags/es.png" alt="" />Español</a></li>
<li><a href="../jp/bugreports.html"><img src="../../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="../en/bugreports.html"><img src="../../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
<a href="../welcome_sv_SE.html" class="uplink">Welcome</a>
</span></div>
</div>
<div id="content">
<div>
<h1>Reporting bugs</h1>
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
<h2>Getting a Trac account</h2>
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
<h2>Creating a bug report</h2>
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">search</a> function for this.<br />
After you have established that it's a unique bug, make your information as accurate as possible:</p>
<ul>
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in '<i>About This System...</i>' from the Deskbar menu.</p></li>
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
</ul>
<h3>Software Bugs</h3>
<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
<h3>Hardware Bugs</h3>
<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
<ul>
<li><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
<li><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
<li><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</li>
<li><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
</ul>
<p>You enter these commands into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
<h3>Kernel Debugging Land - KDL</h3>
<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
<ul>
<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
</ul>
<h2>What's next?</h2>
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
non-descriptive comments.</p>
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
as 'fixed'.</p>
</div>
</div>
<div class="nav">
<div class="inner"><span>
<a href="../welcome_sv_SE.html" class="uplink">Welcome</a>
</span></div>
</div>
</body>
</html>
docs/welcome/welcome_de.html
+125
View File
@@ -0,0 +1,125 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Humdinger <[email protected]>
* Stephan Aßmus <[email protected]>
* Translators:
* Matthias
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Willkommen zu Haiku!</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/de.png" alt="" /> Deutsch</li>
<li><a href="welcome_fr.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="welcome_it.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="welcome_ru.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="welcome_es.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="welcome_sv_SE.html"><img src="../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="welcome_jp.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="welcome_en.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
 
</span></div>
</div>
<div id="content">
<div>
<h2>
<a id="welcome" name="welcome">Willkommen zu Haiku!</a></h2>
<p>Danke, dass Sie sich für Haiku interessieren! Wir hoffen, dass wir durch unsere erste öffentliche Version neue Entwickler für unser Projekt begeistern können und Anwender in die Lage versetzen, Haiku auszuprobieren. Natürlich ist diese <i>Alpha Version</i> noch lange nicht vollständig oder gar fehlerfrei und sie erfüllt auch noch nicht die Ziele, die wir uns selbst gesteckt haben, aber sie zeigt, warum wir uns in diesem Projekt so engagieren und es ermöglicht anderen, das große Potential von Haiku zu erkunden.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">Achtung, Fehler!</a></h2>
<p>So weit es geht, sind alle schwerwiegendere Fehler beseitigt. Da es sich aber trotz alle dem um eine Alpha-Version handelt, muss man davon ausgehen, dass noch Fehler vorhanden sind, die noch nicht entdeckt wurden.</p>
<div class="box-warning">Vom Verwenden dieser Alpha-Version in einer systemkritischen Umgebung wird dringend abgeraten! Obwohl es unwahrscheinlich ist, kann ein Datenverlust nicht ausgeschlossen werden!</div>
<p>Einer der Hauptgründe, diese Alpha-Version zu veröffentlichen war, das System einer Vielzahl von Menschen zum Testen anbieten zu können. Nur so ist es möglich, alle Fehler zu finden und Verbesserungsvorschläge zu erhalten. Deshalb sollte nicht gezögert werden, Fehler auch zu melden!</p>
<ul>
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
<li><a href="de/bugreports.html">Tipps für einen sinnvollen Fehler-Report</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="system" name="system">Das System kennenlernen</a></h2>
<p>Da Haiku darauf abzielt ein würdiger Nachfolger des BeOS R5 zu werden, ist eine Erfahrung mit diesem System natürlich hilfreich. Darüber hinaus sei auf diese Punkte verwiesen:</p>
<ul>
<li><a href="../userguide/en/contents.html">Haiku Benutzer-Handbuch</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">Liste mit BeOS/Haiku Internet-Seiten</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Software installieren</a></h2>
<p>Da Haiku sowohl binärkompatibel als auch code-kompatibel mit dem BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku. Nach dem Herunterladen eines Programm-Paketes muss es lediglich nach <span class="path">/boot/apps/</span> entpackt (ein Doppelklick öffnet den <span class="app">Expander</span>) und von dort gestartet werden.</p>
<div class="box-info">Eine Ausnahme hiervon sind die "OptionalPackages", die normalerweise mit Haiku mitgeliefert werden, wenn es direkt aus dem Quellcode übersetzt wird. Diese können natürlich auch in jedem anderen laufenden Haiku installiert werden, dann aber müssen sie ins Hauptverzeichnis "<span class="path">/</span>" entpackt werden.<br />
Da die "OptionalPackages" eher für Entwickler gedacht sind, findet man oftmals mehrere Versionen die zu unterschiedlichen Revisionen von Haiku nicht kompatibel sind.</div>
<p>Große Software-Verzeichnisse sind:</p>
<ul>
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - hier werden Erweiterungen für portiere Software bereitgehalten.</li>
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - Open Source Programme, die speziell für das BeOS oder Haiku geschrieben wurden.</li>
<li><a href="http://haiku-files.org/files/optional-packages/" class="printurl">OptionalPackages</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Die API stellt sich vor</a></h2>
<p>Da Haiku eine Reimplemention des BeOS R5 ist, sind die API die gleichen (mit einigen Erweiterungen). Deshalb ist die Dokumentation im BeBook immernoch eine hilfreiche Quelle. Dankenswerter weise hat die Firma ACCESS, die alle Rechte von Be Inc. übernommen hat, einer Veröffentlichung des BeBook zugestimmt.</p>
<p>Diese Informationen sollten einen guten Einstieg in die Materie vermitteln:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Browser</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">BeBook</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">BeNewsletter Archive</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Kontakte knüpfen</a></h2>
<p>Um sich mit anderen Entwickler und Anwender auszutauschen muss man nur an den Diskussionen im IRC, unseren Foren oder Mailing-Listen teilnehmen. Wie üblich, wenn sich mehrere Menschen unterhalten, sollte eine gewisse <a href="http://www.haiku-os.org/node/2517">Etikette</a> eingehalten werden.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Foren</a></li>
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Haupt-Mailing-Liste</a></li>
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Entwickler-Mailing-Liste</a></li>
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing-Liste für Programmierer</a></li>
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Zusammenstellung</a> von speziellen Mailing-Listen</li>
</ul>
</div>
</div>
<div class="nav">
<div class="inner"><span>
 
</span></div>
</div>
</body>
</html>
docs/welcome/welcome.html → docs/welcome/welcome_en.html
+47 -28
View File
@@ -1,6 +1,5 @@
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"../html-dtd/xhtml1-strict.dtd">
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
@@ -20,22 +19,37 @@
</head>
<body>
<div class="logo">
<img src="./en/images/logo.png" alt="logo" class="noprint" id="logo" name="logo" />
</div>
<div class="topnav">
<p>&#160;</p>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="content">
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/gb.png" alt="" /> English</li>
<li><a href="welcome_fr.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="welcome_de.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="welcome_it.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="welcome_ru.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="welcome_es.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="welcome_sv_SE.html"><img src="../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="welcome_jp.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
</ul>
<span>
 
</span></div>
</div>
<h1>
<a id="welcome" name="welcome">Welcome to Haiku!</a></h1>
<div id="content">
<div>
<h2>
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
<p>Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
<h1>
<a href="#logo"><img src="./images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="bugreport" name="bugreport">Beware of Bugs</a></h1>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
<p>We were working very hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
@@ -45,18 +59,18 @@
<li><a href="en/bugreports.html">Tips for a helpful bug report</a></li>
</ul>
<h1>
<a href="#logo"><img src="./images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="system" name="system">Getting to know the system</a></h1>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="system" name="system">Getting to know the system</a></h2>
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
<ul>
<li><a href="../userguide/en/contents.html">Haiku User Guide</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
</ul>
<h1>
<a href="#logo"><img src="./images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="software" name="software">Installing more software</a></h1>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Installing more software</a></h2>
<p>Because of our binary and source compatibility, many BeOS applications run on Haiku. After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
<div class="box-info">An exception are OptionalPackages, which are normally included when building Haiku directly from source. Those can, however, also be downloaded and added to any running Haiku system. The only difference to normal archives: you have to unzip directly to root <span class="path">/</span>.<br />
For debugging purposes the OptionalPackage site keeps older versions which are not compatible with newer Haiku revisions. OptionalPackages are primarily for developers, less so for end-users.</div>
@@ -70,9 +84,9 @@ For debugging purposes the OptionalPackage site keeps older versions which are n
<li><a href="http://haiku-files.org/files/optional-packages/" class="printurl">OptionalPackages</a> are mostly used when building Haiku from source</li>
</ul>
<h1>
<a href="#logo"><img src="./images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="api" name="api">Getting to know the API</a></h1>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Getting to know the API</a></h2>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the BeBook is still a valid resource. Thanks to ACCESS, who own the rights to former Be Inc. property, we are allowed to provide a copy of the BeBook.</p>
<p>There are additional resources that should help you getting started:</p>
@@ -83,9 +97,9 @@ For debugging purposes the OptionalPackage site keeps older versions which are n
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">BeNewsletter Archive</a></li>
</ul>
<h1>
<a href="#logo"><img src="./images/up.png" align="right" alt="index" border="0" class="noprint" /></a>
<a id="contact" name="contact">Getting in contact</a></h1>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Getting in contact</a></h2>
<p>Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/node/2517">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
@@ -97,8 +111,13 @@ For debugging purposes the OptionalPackage site keeps older versions which are n
</ul>
</div>
<div class="bottomnav">
<p>&#160;</p>
</div>
<div class="nav">
<div class="inner"><span>
 
</span></div>
</div>
</body>
</html>
docs/welcome/welcome_es.html
+124
View File
@@ -0,0 +1,124 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Humdinger <[email protected]>
* Stephan Aßmus <[email protected]>
* Translators:
* Oscar Carballal Prego
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>¡Bienvenido a Haiku!</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/es.png" alt="" /> Español</li>
<li><a href="welcome_fr.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="welcome_de.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="welcome_it.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="welcome_ru.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="welcome_sv_SE.html"><img src="../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="welcome_jp.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="welcome_en.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
 
</span></div>
</div>
<div id="content">
<div>
<h2>
<a id="welcome" name="welcome">¡Bienvenido a Haiku!</a></h2>
<p>Muchas gracias por probar Haiku. Este es nuestro primer lanzamiento público. Esperamos poder atraer a nuevos desarrolladores a nuestro proyecto y darle a los usuarios una oportunidad para probar Haiku. Somos conscientes de que esta <i>versión alpha</i> no cumple del todo los requisitos que nos hemos propuesto nosotros mismos, y no ofrece todas las características ni la experiencia de usuario que fueron planificadas para la versión R1 final. De todas maneras, esperamos que esta versión le permita descubrir el gran potencial de Haiku, y que comparta nuestra emoción.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">Cuidado con los bugs</a></h2>
<p>Hemos trabajado muy duro para arreglar todos los fallos posibles, de todas maneras, siendo una versión alpha, es muy probable que haya muchos por descubrir.</p>
<div class="box-warning">No recomendamos utilizar las versiones alpha en un sistema de producción. Sus datos podrían verse alterados, sesgados, o completamente borrados.</div>
<p>Una de las razones principales para liberar una versión alpha es atraer a mucha gente para probar el sistema y descubrir fallos o darnos sugerencias para futuras mejoras. Por favor, archive los fallos y mejoras en nuestro bug tracker después de utilizar su sistema de búsqueda para evitar duplicados.</p>
<ul>
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
<li><a href="es/bugreports.html">Consejos para un buen informe de error</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="system" name="system">Conociendo el sistema</a></h2>
<p>Las primeras versiones de Haiku serán muy similares a BeOS R5, el sistema operativo que está recreando. Si nunca lo ha probado, puede mirar estos enlaces:</p>
<ul>
<li><a href="../userguide/en/contents.html">Guía de usuario de Haiku</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">Lista de sitios web acerca de BeOS/Haiku</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Instalando más software</a></h2>
<p>Debido a nuestra compatibilidad de código binario y código fuente, muchas aplicaciones de BeOS funcionan en Haiku. Tras descargar un paquete, tan sólo debe descomprimirlo (doble clic abre <span class="app">Expander</span>) a <span class="path">/boot/apps/</span> e iniciar la aplicación desde ahí.</p>
<div class="box-info">Una excepción son los OptionalPackages (paquetes opcionales), que habitualmente están incluídos cuando se compila Haiku desde el código fuente. Pueden ser también descargados e instalados en cualquier sistema Haiku ya funcionando. La única diferencia con los ficheros normales es que tiene que descomprimirlos directamente al directorio raíz <span class="path">/</span>.<br /> Para propósitos de depuración de código, la web de los OptionalPackages mantiene versiones antiguas que no son compatibles con las nuevas revisiones de Haiku. Los OptionalPackages son principalmente para desarrolladores, no están pensados para el usuario final.</div>
<p>Repositorios de software populares son:</p>
<ul>
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> mantiene parches para las aplicaciones portadas.</li>
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> hospeda los proyectos de software de código libre para BeOS/Haiku.</li>
<li><a href="http://haiku-files.org/files/optional-packages/" class="printurl">OptionalPackages</a> son usados principalmente cuando se compila Haiku desde el código fuente.</li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Conociendo la API</a></h2>
<p>Como Haiku es una reimplementación, la API es la misma que para BeOS R5 (con algunos añadidos). Por lo tanto la documentación existente en el BeBook es todavía un recurso válido. Gracias a ACCESS, que tiene los derechos de la antigua Be Inc., se nos permite distribuir una copia del BeBook.</p>
<p>Existen algunos recursos que le pueden ayudar a comenzar:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ (preguntas frecuentes) de desarrollo</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Navegador de código fuente</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">BeBook</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Archivo de BeNewsletter</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Poniéndose en contacto</a></h2>
<p>Entre en contacto con otros desarrolladores y usuarios y únase a las conversaciones del IRC, foro o las listas de correo. Cuando tanta gente diferente se junta, es necesario establecer unas normas para que la comunicación sea efectiva. Por favor, respete nuestra <a href="http://www.haiku-os.org/node/2517">Etiqueta de listas de correo</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canales IRC</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Foros</a></li>
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Lista de correo general</a></li>
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Lista de correo de desarrollo de Haiku</a></li>
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Lista de correo para programadores de aplicaciones de terceros</a></li>
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Ver</a> listas de correo más específicas.</li>
</ul>
</div>
</div>
<div class="nav">
<div class="inner"><span>
 
</span></div>
</div>
</body>
</html>
docs/welcome/welcome_fr.html
+132
View File
@@ -0,0 +1,132 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Humdinger <[email protected]>
* Stephan Aßmus <[email protected]>
* Translators:
* Vincent Duvert
* Loïc
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Bienvenue sur Haiku !</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/fr.png" alt="" /> Français</li>
<li><a href="welcome_de.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="welcome_it.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="welcome_ru.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="welcome_es.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="welcome_sv_SE.html"><img src="../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="welcome_jp.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="welcome_en.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
 
</span></div>
</div>
<div id="content">
<div>
<h2>
<a id="welcome" name="welcome">Bienvenue sur Haiku !</a></h2>
<p>Merci beaucoup d’essayer Haiku  ! Voici notre première version publique. Nous espérons encourager de nouveaux développeurs à nous rejoindre et donner aux futurs utilisateurs la possibilité d’essayer Haiku. Nous sommes conscients que cette <i>version alpha</i> ne remplit pas touts les objectifs que nous nous sommes fixés et ne fournit pas toutes les fonctionnalités et l’expérience utilisateur attendues pour la version R1 finale. Néanmoins, nous espérons que cette pré-version vous permettra de découvrir le potentiel de Haiku et de partager notre excitation.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">Attention aux bogues</a></h2>
<p>Nous travaillons dur pour résoudre les bogues critiques du système. Néanmoins, Haiku n'étant qu'au stade de version alpha, vous risquez d'en rencontrer lors de vos essais.</p>
<div class="box-warning">Nous déconseillons l'utilisation des versions Alpha sur un système en production. Les données que vous manipulez pourraient être altérées, corrompues ou tout simplement détruites.</div>
<p>La sortie d'une version alpha a pour objectif de faire découvrir et tester le système par d'avantage de personnes, afin de trouver les bogues présents et d'obtenir des suggestions d'améliorations futures. Veuillez rapporter d'éventuels bogues et suggestions sur notre traqueur de bogues après avoir utilisé sa fonction de recherche pour éviter les doublons.</p>
<ul>
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Traqueur de bogues de Haiku</a> (en anglais)</li>
<li><a href="fr/bugreports.html">Astuces pour un rapport de bogue utile</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="system" name="system">Comment se familiariser avec le système</a></h2>
<p>Les premières versions de Haiku auront une apparence et des fonctionnalités proches de celles de BeOS R5, le système d'exploitation qu'il tente de ré-implémenter. Si vous ne l'avez jamais essayé, jetez un œil à ces liens :</p>
<ul>
<li><a href="../userguide/en/contents.html">Guide de l'utilisateur Haiku</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">Liste de sites web consacrés à BeOS/Haiku</a> (en anglais)</li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Installer plus de logiciels</a></h2>
<p>Grace à notre compatibilité binaire et source avec BeOS, de nombreuses applications écrites pour ce système fonctionne sous Haiku. Après avoir téléchargé un paquet, décompressez le (un double-clic lancera <span class="app">Expander</span>) dans <span class="path">/boot/apps/</span> et démarrez l'application depuis de ce dossier.</p>
<div class="box-info">Les paquets optionnels font exception. ils sont normalement inclus à la compilation de Haiku à partir de leur code source.
Ceux-ci peuvent cependant être téléchargés et ajoutés à n'importe quel système Haiku en cours d'exécution.
Seule différence avec les archives normales : vous devez les décompresser directement à la racine <span class="path">/</span>.<br />
Le site conserve les anciennes versions des paquets optionnels à des fins de débogage qui ne sont pas compatibles avec les nouvelles versions d'Haiku.
Les paquets optionnels sont principalement destinées aux développeurs, et pas aux utilisateurs finaux.</div>
<p>Des sites populaires référencent les logiciels disponibles.</p>
<ul>
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> maintient les correctifs pour les logiciels portés</li>
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> héberge des projets de logiciels open source natifs pour BeOS et Haiku</li>
<li><a href="http://haiku-files.org/files/optional-packages/" class="printurl">OptionalPackages</a> sert principalement pour les programmes construits à partir du code source de Haiku.</li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Apprendre à connaître l'API</a></h2>
<p>Comme Haiku est une ré-implémentation, l'API est encore le même que celle de BeOS R5 (avec quelques ajouts).
Par conséquent, la documentation du BeBook est toujours valable. Nous remercions ACCESS, qui détient les droits de propriété de l'ancien Be Inc, de nous autoriser à fournir une copie du BeBook.</p>
<p>Quelques ressources supplémentaires sont susceptible de vous aider à commencer :</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ Développement</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Explorer le code source</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">BeBook</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">BeNewsletter</a> : archive des informations périodiques</li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Rester en contact</a></h2>
<p>Entrer en contact avec les autres développeurs et utilisateurs, participer aux discussions sur IRC, dans nos forums ou les listes de diffusion.
Quand beaucoup de gens différents se rencontrent, des règles doivent êtres établies pour maintenir une communication efficace. S'il vous plaît respecter
<a href="http://www.haiku-os.org/node/2517">l'étiquette de notre liste de diffusion</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canaux IRC</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Liste de diffusion générale</a></li>
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Liste de diffusion concernant le dévelopment de Haiku, lui même</a></li>
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Liste de diffusion concernant les développeurs d'applications tiers</a></li>
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Présentation</a> des listes de diffusions plus spécifiques</li>
</ul>
</div>
</div>
<div class="nav">
<div class="inner"><span>
 
</span></div>
</div>
</body>
</html>
docs/welcome/welcome_it.html
+123
View File
@@ -0,0 +1,123 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Humdinger <[email protected]>
* Stephan Aßmus <[email protected]>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Welcome to Haiku!</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/it.png" alt="" /> Italiano</li>
<li><a href="welcome_fr.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="welcome_de.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="welcome_ru.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="welcome_es.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="welcome_sv_SE.html"><img src="../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="welcome_jp.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="welcome_en.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
 
</span></div>
</div>
<div id="content">
<div>
<h2>
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
<p>Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
<p>We were working very hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
<ul>
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
<li><a href="it/bugreports.html">Tips for a helpful bug report</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="system" name="system">Getting to know the system</a></h2>
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
<ul>
<li><a href="../userguide/en/contents.html">Haiku User Guide</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Installing more software</a></h2>
<p>Because of our binary and source compatibility, many BeOS applications run on Haiku. After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
<div class="box-info">An exception are OptionalPackages, which are normally included when building Haiku directly from source. Those can, however, also be downloaded and added to any running Haiku system. The only difference to normal archives: you have to unzip directly to root <span class="path">/</span>.<br />
For debugging purposes the OptionalPackage site keeps older versions which are not compatible with newer Haiku revisions. OptionalPackages are primarily for developers, less so for end-users.</div>
<p>Popular software repositories are:</p>
<ul>
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> maintains patches for ported software</li>
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> hosts native BeOS and Haiku open source software projects</li>
<li><a href="http://haiku-files.org/files/optional-packages/" class="printurl">OptionalPackages</a> are mostly used when building Haiku from source</li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Getting to know the API</a></h2>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the BeBook is still a valid resource. Thanks to ACCESS, who own the rights to former Be Inc. property, we are allowed to provide a copy of the BeBook.</p>
<p>There are additional resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Browser</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">BeBook</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">BeNewsletter Archive</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Getting in contact</a></h2>
<p>Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/node/2517">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview</a> of more specific mailing lists</li>
</ul>
</div>
</div>
<div class="nav">
<div class="inner"><span>
 
</span></div>
</div>
</body>
</html>
docs/welcome/welcome_jp.html
+125
View File
@@ -0,0 +1,125 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Humdinger <[email protected]>
* Stephan Aßmus <[email protected]>
* Translators:
* Jorge G. Mare
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Haikuへようこそ!</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/jp.png" alt="" /> 日本語</li>
<li><a href="welcome_fr.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="welcome_de.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="welcome_it.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="welcome_ru.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="welcome_es.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="welcome_sv_SE.html"><img src="../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="welcome_en.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
 
</span></div>
</div>
<div id="content">
<div>
<h2>
<a id="welcome" name="welcome">Haikuへようこそ!</a></h2>
<p>Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">バグに注意</a></h2>
<p>We were working very hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
<ul>
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
<li><a href="jp/bugreports.html">Tips for a helpful bug report</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="system" name="system">システムを把握する</a></h2>
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
<ul>
<li><a href="../userguide/en/contents.html">Haiku User Guide</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Installing more software</a></h2>
<p>Because of our binary and source compatibility, many BeOS applications run on Haiku. After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
<div class="box-info">An exception are OptionalPackages, which are normally included when building Haiku directly from source. Those can, however, also be downloaded and added to any running Haiku system. The only difference to normal archives: you have to unzip directly to root <span class="path">/</span>.<br />
For debugging purposes the OptionalPackage site keeps older versions which are not compatible with newer Haiku revisions. OptionalPackages are primarily for developers, less so for end-users.</div>
<p>Popular software repositories are:</p>
<ul>
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> maintains patches for ported software</li>
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> hosts native BeOS and Haiku open source software projects</li>
<li><a href="http://haiku-files.org/files/optional-packages/" class="printurl">OptionalPackages</a> are mostly used when building Haiku from source</li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">APIを理解する</a></h2>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the BeBook is still a valid resource. Thanks to ACCESS, who own the rights to former Be Inc. property, we are allowed to provide a copy of the BeBook.</p>
<p>There are additional resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Browser</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">BeBook</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">BeNewsletter Archive</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Getting in contact</a></h2>
<p>Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/node/2517">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview</a> of more specific mailing lists</li>
</ul>
</div>
</div>
<div class="nav">
<div class="inner"><span>
 
</span></div>
</div>
</body>
</html>
docs/welcome/welcome_ru.html
+125
View File
@@ -0,0 +1,125 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Humdinger <[email protected]>
* Stephan Aßmus <[email protected]>
* Translators:
* michael_s
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Добро пожаловать в Haiku!</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/ru.png" alt="" /> Русский</li>
<li><a href="welcome_fr.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="welcome_de.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="welcome_it.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="welcome_es.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="welcome_sv_SE.html"><img src="../images/flags/sv_SE.png" alt="" />Svensk</a></li>
<li><a href="welcome_jp.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="welcome_en.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
 
</span></div>
</div>
<div id="content">
<div>
<h2>
<a id="welcome" name="welcome">Добро пожаловать в Haiku!</a></h2>
<p>Большое спасибо за проявленный интерес к Haiku! Это наш первый публичный релиз и мы надеемся привлечь новых разработчиков к нашему проекту и дать будущим пользователям шанс увидеть Haiku в деле. Понятно, что этот <i>альфа-релиз</i> далеко не полностью соответствует тем целям, которые мы сами наметили, и не предоставляет все функции, которые мы собирались дать конечному пользователю, запланировав их для финальной версии R1. Однако, мы надеемся, что этот релиз позволит вам заметить большой потенциал Haiku, и вы найдёте немного времени для её изучения.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">Остерегайтесь Ошибок!</a></h2>
<p>Мы провели тяжёлую работу по выявлению и устранению ошибок ("багов"), однако это только альфа-релиз и в нём обязательно присутствуют немало скрытых ошибок.</p>
<div class="box-warning">Мы не рекомендуем использовать альфа-версии в качестве основной операционной системы. В ваши данные с большой вероятностью могут быть внесены нежелательные изменения, они могут исказиться или же уничтожиться.</div>
<p>Одной из главных причин для выпуска альфа-версии явилось желание привлечь больше пользователей для тестирования и обнаружения ошибок, а также получения от них предложений по дальнейшему улучшению Haiku. Пожалуйста, оставляйте отчёты о найденных багах и предложения по улучшению в нашей системе отслеживания ошибок (bug tracker), но только после использования поиска, чтобы избежать дубликатов.</p>
<ul>
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Система отслеживания ошибок в Haiku (Bug Tracker)</a></li>
<li><a href="ru/bugreports.html">Советы по сообщениям об ошибках</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="system" name="system">Знакомство с системой</a></h2>
<p>Первые релизы Haiku будут похожи по функционалу и вешнему виду на BeOS R5, которую она и призвана повторить. Если вы никогда не пользовались этой операционной системой, то рекомендуется воспользоваться следующими ссылками:</p>
<ul>
<li><a href="../userguide/en/contents.html">Руководство пользователя Haiku</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">Список сайтов о BeOS/Haiku</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Установка дополнительных программ</a></h2>
<p>Так как Haiku бинарно и на уровне исходных кодов совместима с BeOS, то многие BeOS-приложения работают и в ней. Загрузив архив с программой, просто распакуйте его (достаточно двойного клика для открытия архива в <span class="app">Expander</span>) в <span class="path">/boot/apps/</span>, и оттуда же запускайте это приложение.</p>
<div class="box-info">Исключением являются опциональные пакеты (OptionalPackages), которые уже включены в Haiku при её компиляции из исходных кодов, однако их также можно загрузить и добавить в любую установленную копию Haiku. У них одно отличие от обычных архивов с программами: их следует распаковывать в корень загрузочного диска <span class="path">/boot</span>.<br />
Для отладочных целей на сайте с опциональными пакетами хранятся их устаревшие версии, которые не совместимы с новыми ревизиями Haiku, и они в первую очередь предназначены для разработчиков, но не для конечных пользователей.</div>
<p>Популярные каталоги программ:</p>
<ul>
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a> сайт с программами, ориентированными на Haiku.</li>
<li><a href="http://www.bebits.com" class="printurl">BeBits</a> самый популярный каталог программ для BeOS (в последнее время и для Haiku).</li>
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> библиотеки, необходимые для портирования приложений.</li>
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> хранилище для разрабатываемых приложений с открытым исходным кодом для BeOS и Haiku.</li>
<li><a href="http://haiku-files.org/files/optional-packages/" class="printurl">OptionalPackages</a> в основном используется при компиляции Haiku из исходных кодов.</li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Знакомство с интерфейсом программирования приложений (API)</a></h2>
<p>Так как Haiku повторяет BeOS R5, то и всё, что касается API у них схоже (с некоторыми исключениями), потому документация в BeBook всё ещё актуальна. Благодаря компании ACCESS, которой принадлежат права на интеллектуальную собственность Be Inc., нам позволено распространять BeBook.</p>
<p>Существуют и другие ресурсы, которые должны помочь вам начать изучение:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">ЧАВО разработчика</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Браузер исходного кода </a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">BeBook</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Архив BeNewsletter</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Желаете пообщаться?</a></h2>
<p>Вы можете связаться с разработчиками и другими пользователями, присоединившись к обсуждению на IRC каналах, нашем форуме или в списках рассылки. Когда множество людей обсуждают что-то вместе, то необходимо соблюдать некоторые правила для сохранения эффективности общения. Пожалуйста, соблюдайте <a href="http://www.haiku-os.org/node/2517">этикет списков рассылки</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC каналы</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Форумы</a></li>
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Основной список рассылки</a></li>
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Список рассылки непосредственных разработчиков Haiku</a></li>
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Список рассылки для разработчиков сторонних приложений</a></li>
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Обзор остальных специализированных списков рассылки</a></li>
</ul>
</div>
</div>
<div class="nav">
<div class="inner"><span>
 
</span></div>
</div>
</body>
</html>
docs/welcome/welcome_sv_SE.html
+123
View File
@@ -0,0 +1,123 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "../html-dtd/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<!--
*
* Copyright 2008-2009, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Humdinger <[email protected]>
* Stephan Aßmus <[email protected]>
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Welcome to Haiku!</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
</div>
<div class="nav">
<div class="inner">
<ul class="lang-menu">
<li class="now"><img src="../images/flags/sv_SE.png" alt="" /> Svensk</li>
<li><a href="welcome_fr.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
<li><a href="welcome_de.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
<li><a href="welcome_it.html"><img src="../images/flags/it.png" alt="" />Italiano</a></li>
<li><a href="welcome_ru.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
<li><a href="welcome_es.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
<li><a href="welcome_jp.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
<li><a href="welcome_en.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
</ul>
<span>
 
</span></div>
</div>
<div id="content">
<div>
<h2>
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
<p>Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
<p>We were working very hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
<p>One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.</p>
<ul>
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
<li><a href="sv_SE/bugreports.html">Tips for a helpful bug report</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="system" name="system">Getting to know the system</a></h2>
<p>The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:</p>
<ul>
<li><a href="../userguide/en/contents.html">Haiku User Guide</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Installing more software</a></h2>
<p>Because of our binary and source compatibility, many BeOS applications run on Haiku. After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
<div class="box-info">An exception are OptionalPackages, which are normally included when building Haiku directly from source. Those can, however, also be downloaded and added to any running Haiku system. The only difference to normal archives: you have to unzip directly to root <span class="path">/</span>.<br />
For debugging purposes the OptionalPackage site keeps older versions which are not compatible with newer Haiku revisions. OptionalPackages are primarily for developers, less so for end-users.</div>
<p>Popular software repositories are:</p>
<ul>
<li><a href="http://www.haikuware.com" class="printurl">Haikuware</a></li>
<li><a href="http://www.bebits.com" class="printurl">BeBits</a></li>
<li><a href="http://ports.haiku-files.org/" class="printurl">HaikuPorts</a> maintains patches for ported software</li>
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> hosts native BeOS and Haiku open source software projects</li>
<li><a href="http://haiku-files.org/files/optional-packages/" class="printurl">OptionalPackages</a> are mostly used when building Haiku from source</li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Getting to know the API</a></h2>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the BeBook is still a valid resource. Thanks to ACCESS, who own the rights to former Be Inc. property, we are allowed to provide a copy of the BeBook.</p>
<p>There are additional resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Browser</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">BeBook</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">BeNewsletter Archive</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Getting in contact</a></h2>
<p>Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/node/2517">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview</a> of more specific mailing lists</li>
</ul>
</div>
</div>
<div class="nav">
<div class="inner"><span>
 
</span></div>
</div>
</body>
</html>