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

Update userguide from i18n.haiku-os.org.

Browse Source
This commit is contained in:
Niels Sascha Reedijk
2012-08-18 10:28:04 +02:00
parent 9ff0fe5615
commit 5bde1d438b
460 changed files with 5370 additions and 2957 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/welcome/de/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -54,7 +54,7 @@
<div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Bugs melden</td></tr>
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Zugang zu Trac</a><br />
<a href="#report">Bugreport erstellen</a><br />
<a href="#app">Bugs in Anwendungen</a><br />
@@ -123,6 +123,7 @@ Im KDL kann es passieren, dass die Tastatur nicht mehr funktioniert. PS/2 Tastat
</table>
<p>Weitere Infos gibt es im Artikel <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a> (Englisch).</p>
<p>Die Ausgaben im KDL werden zum seriellen Port geschickt (falls man einen hat und ein entsprechendes Nullmodemkabel samt zweiten Rechner, kann man die Ausgaben in einem Terminalprogramm aufnehmen). Außerdem werden sie ins Syslog geschrieben. Wenn man das KDL allerdings nicht verlassen kann, wird auch nichts ins Syslog geschrieben. Es gibt aber eine Bootloader Debug Option, die das trotzdem möglich macht (siehe weiter unten).</p>
<p>Von Ausgaben im KDL lassen sich auch QR-Codes erzeugen, die dann mit einem Smartphone oder ähnlichem zu Text konvertiert werden können. Der Blogpost <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> (Englisch) erklärt wie man mit diesem Feature Daten aus dem Kernel Debugging Land herausbekommt.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Syslog</a></h3>
docs/welcome/en/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -50,7 +50,7 @@
<div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Reporting bugs</td></tr>
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
<a href="#report">Creating a bug report</a><br />
<a href="#app">Application bugs</a><br />
@@ -120,6 +120,7 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
</table>
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Syslog</a></h3>
docs/welcome/es/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -53,7 +53,7 @@
<div class="box-info">La traducción de esta página no está completa aún. Hasta que esté, las partes sin terminar vienen en su inglés original.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Reportar fallos</td></tr>
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
<a href="#report">Creating a bug report</a><br />
<a href="#app">Application bugs</a><br />
@@ -123,6 +123,7 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
</table>
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Syslog</a></h3>
docs/welcome/fi/bugreports.html
+46 -43
View File
@@ -4,24 +4,26 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Niels Reedijk, Matt Madia and Ingo Weinhold who wrote
* http://dev.haiku-os.org/wiki/ and http://dev.haiku-os.org/wiki/ReportingBugs
* Humdinger <[email protected]>
* Translators:
* Karvjorm
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Reporting bugs</title>
<title>Vikojen ilmoittaminen</title>
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
<div><span>Käyttäjäopas</span></div>
</div>
<div class="nav">
@@ -48,62 +50,62 @@
<div id="content">
<div>
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
<div class="box-info">Tämän sivun kotoistaminen ei ole vielä täydellinen. Siihen asti keskeneräiset osat käyttävät englanninkielistä alkuperäistekstiä.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Reporting bugs</td></tr>
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
<a href="#report">Creating a bug report</a><br />
<a href="#app">Application bugs</a><br />
<a href="#server">Server bugs</a><br />
<a href="#kernel">Kernel bugs</a><br />
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Trac-tilin saaminen</a><br />
<a href="#report">Vikailmoituksen luominen</a><br />
<a href="#app">Sovellusviat</a><br />
<a href="#server">Palvelinviat</a><br />
<a href="#kernel">Käyttöjärjestelmäydinviat</a><br />
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
<a href="#syslog">Syslog</a><br />
<a href="#syslog">Järjestelmäloki</a><br />
<a href="#onscreen">On screen debug output</a><br />
<a href="#hardware">Hardware/Driver bugs</a><br />
<a href="#next">What's next?</a></td></tr>
<a href="#hardware">Laitteisto-/Ajuriviat</a><br />
<a href="#next">Mitä seuraavaksi?</a></td></tr>
</table>
<h1>Reporting bugs</h1>
<h1>Vikojen ilmoittaminen</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>
<p>Koska kehittäjämme eivät pysty testaamaan jokaista laitteistoyhdistelmää, eikä jokaista erilaista käyttöjärjestelmän vuorovaikutusta, luotamme käyttäjien antavan meille palautetta siitä, kuinka asiat toimivat heidän laitteissaan. Koska Haiku on aika nuori, on hyvin todennäköistä, että käyttäjä kohtaa vikoja. Kiitämme siitä ajasta, jota käytät niistä ilmoittamiseen. Yhdessä voimme parantaa Haikua pala palalta.</p>
<p>Vianjäljityksen pitämiseksi tehokkaana on olennaista noudattaa <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Vianjäljitysetikettiä</a>.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="account" name="accout">Getting a Trac account</a></h2>
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
<a id="account" name="accout">Trac-tiilin saaminen</a></h2>
<p>Jos luot vikalipun, sinulla on oltava tili <a href="http://dev.haiku-os.org/register" title="Registröidy Haikun vikajäljittäjään">Haikun vikajäljittäjässä</a>.<br />
Luotaessa uutta tiliä muista <b>tarjota sähköpostiosoitteesi</b>, koska se on välttämätön lipun muokkausoikeusien saamiseksi. Tarkista varmuuden vuoksi <b>roskapostikansiosi</b> pian jälkeenpäin, koska kaikki tärkeät vahvistussähköpostiviestit usein päättyvät sinne.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="report" name="report">Creating a bug report</a></h2>
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">search</a> function for this.<br />
After you have established that it's a unique bug, make your information as accurate as possible:</p>
<a id="report" name="report">Vikailmoituksen luominen</a></h2>
<p><a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">Varmista</a> ennen vian ilmoittamista, että vastaavaa vikailmoitusta ei ole jo olemassa. Voit käyttää myös <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">etsi</a>-toimintoa tähän.<br />
Varmista sen jälkeen kun olet esitellyt ainutlaatuisen vian, että tietosi ovat niin tarkkoja kuin mahdollista:</p>
<ul>
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  <a href="http://haiku-files.org/">available</a>.</p></li>
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
<li><p>Yritä toistaa havaitsemasi vika nykyisessä Haikun korjausversiossa. Esirakennetut tiedostovedokset testaustarkoituksiin löytyvät <a href="http://haiku-files.org/">täältä</a>.</p></li>
<li><p>Sisällytä mukaan perustietoa siitä, kuinka testaat Haikua (todellisessa tietokoneessa, VMWare-ympäristössä, QEMU-emulaattorissa, jne.).</p></li>
<li><p>Mainitse, mitä <acronym title="Subversion, käyttämämme lähdekoodin versionhallintajärjestelmä">SVN</acronym>-korjausversiota käytät. Löydät tämän tiedon Työpöytäpalkin valikosta <span class="menu">Haikusta...</span>. Mainitse myös, että minkälaisella rakennusjärjestelmällä (gcc2, gcc4, gcc2hybrid, gcc4hybrid) testaamasi järjestelmä on rakennettu. Ladattavat tiedostovedokset on nimetty niiden mukaan. Itse rakennetuissa tiedostovedoksissa tiedät itse, kuinka se on rakennettu.</p></li>
<li><p>Kuvaile kokemasi pulma. Yritä olla niin tarkka kuin voit: kuvaile todellinen käyttäytyminen, ja se käyttäytyminen, jota odotit.</p></li>
<li><p>Kuvaile, mitä vaiheita pitää suorittaa vian paljastumiseksi. Tämä auttaa kehittäjiä toistamaan vian.</p></li>
<li><p>Liitä mukaan niin paljon tietoja, kuin sinulla on. Jos kyseessä on graafisen käyttöliittymän vika, tai vika yhdessä sovelluksessa, yritä tehdä näytönkaappaus painamalla <span class="key">PRINT SCREEN</span>-näppäintä.</p></li>
</ul>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="app" name="app">Application bugs</a></h2>
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
<a id="app" name="app">Sovellusviat</a></h2>
<p>Kun sovellus kaatuu, sinun pitäisi kutsua vikajäljitintä hälytysikkunasta, joka ponnahtaa näkyviin. Tämä avaa Pääteikkunan gdb-ohjelmalla (GNU-vikajäljitin), joka käynnistyy. Kirjoittamalla <span class="cli">bt</span>, luot "paluujäljen". jonka sinun pitäisi kopioida kokonaisuudessaan (mukaan lukien se osa, joka tuli näkyviin, ennen kuin kirjoitit <span class="cli">bt</span>-komennon) ja liittää se vikalippuun.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="server" name="server">Server bugs</a></h2>
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
<a id="server" name="server">Palvelinviat</a></h2>
<p>Kun elintärkeät palvelimet, kuten app-, registrar- tai input-palvelin kaatuvat, et näe tavallista kaatumishälytystä. Sen sijaan koko näyttö muuttuu valkoiseksi tja gdb-istunto käynnistyy ja sen tuloste ilmaantuu näytölle. Todennäköisesti pystyt yhä liikuttamaan hiiren kohdistinta, mikä ylikirjoittaa valkoisen ja gdb-tulosteen näytöllä. Yhä vielä toimivat sovellukset (kuten Prosessivalvonta tai Työpöytäpalkin kello) saattavat myös kirjoittaa vikajäljitin tulosteen päälle näytölle.<br />
Paitsi että kaikki on rumempaa ja epämukavampaa, sama koskee myös sovellusvikoja. Tärkeintä on hankkia paluujälki (<span class="cli">bt</span>-komento). Sinun on ehkä otettava valokuva näytöstä digitaalikameralla, koska et voi kopioida tekstiä mihinkään.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="kernel" name="kernel">Kernel bugs</a></h2>
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
<a id="kernel" name="kernel">Käyttöjärjestelmäydinviat</a></h2>
<p>Käyttöjärjestelmäydinviat ovat tavallisesti vaikutuksiltaan vakavimmat ja samanaikaisesti niiden vikajäljittäminen on vaikeinta. Käyttöjärjestelmäytimeen tai ajuriin osoittavat selvimmin seuraavat oireet:</p>
<ul>
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
<li><p>The system reboots spontaneously.</p></li>
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
<li><p>Järjestelmä siirtyy Käyttöjärjestelmän vianjäljitysmaahan (KDL) omasta tahdostaan. Näytön ylempi osa muuttuu valkoiseksi ja sille tulostetaan useita rivejä tekstiä. Toinen rivi sanoo "<i>Welcome to Kernel Debugging Land...</i>". Sen yläpuolella oleva rivi kertoo välittömän syyn siirtymisestä KDL:ään.</p></li>
<li><p>Järjestelmä alkulatautuu itsestään.</p></li>
<li><p>Järjestelmä jäätyy täysin. Et voi siirtää hiiren osoitinta ja mikään sovellus ei enää toimi. Tärkeä testi siinä tilanteessa on, että pystytkö siirtymään KDL:ään pikanäppäimellä <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> mikä on <span class="key">PRINT</span> useimmissa näppäimistöissä). Odota vähintään minuutti nähdeksesi, että tapahtuuko jotain.</p></li>
<li><p>Järjestelmä ei alkulataa oikein. Se voi alkulatautua itsestään tai pysähtyä jossain vaiheessa (esimerkiksi jonkun alkaulatausnäytön kuvakkeen kohdalla). Yritä jälkimmäisessä tapauksessa myös <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
</ul>
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
@@ -114,13 +116,14 @@ Besides everything being more ugly and inconvenient, basically the same applies
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
<tr><td><span class="cli">bt</span> (eli sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
<tr><td class="onelinetop"><span class="cli">co</span> (eli jatka)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
</table>
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Syslog</a></h3>
@@ -137,7 +140,7 @@ Finally select <span class="menu">Return to main menu</span> and then <span clas
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/fi/bootloader.html">Boot Loader</a>.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
<a id="hardware" name="hardware">Laitteisto/ajuriviat</a></h2>
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
@@ -152,7 +155,7 @@ One or more pages of text will display on the screen, only the last few lines ne
<p>The first four commands are entered into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="next" name="next">What's next?</a></h2>
<a id="next" name="next">Mitä seuraavaksi?</a></h2>
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
non-descriptive comments.</p>
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
docs/welcome/fr/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -53,7 +53,7 @@
<div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Signaler les bogues</td></tr>
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Obtenir un compte Trac</a><br />
<a href="#report">Créer un rapport de bogue</a><br />
<a href="#app">Bogues logiciels</a><br />
@@ -133,6 +133,7 @@ ne posent pas de problème, les claviers USB connecté à un controleur UHCI ne
</table>
<p>Pour plus d'information, consultez l'article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>La sortie KDL est écrite vers le port série ( si vous en avez un, un câble approprié, et un deuxième ordinateur pour vous connecter, vous pourrez capturer la sortie via un programme de terminal) et le journal système. Nottez que si vous ne pouvez pas sortir du mode de débogage du noyau, le journal ne sera pas écrit dans le fichier. Cependant, Il existe une option dans le menu de démarrage qui permet tout de même sa capture (voir ci-dessous). </p>
<p>Vous pouvez générer des codes QR à partir des sorties du KDL, ce qui vous permet de récupérer le texte en photographiant l'écran avec un un smartphones ou un appareil similaires. Consultez le blog <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> pour obtenir les informations sur l'utilisation de cette fonctionnalité dans le KDL.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Le journal système</a></h3>
docs/welcome/it/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -51,7 +51,7 @@
<div class="box-info">La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Reporting bugs</td></tr>
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
<a href="#report">Creating a bug report</a><br />
<a href="#app">Application bugs</a><br />
@@ -121,6 +121,7 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
</table>
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Syslog</a></h3>
docs/welcome/jp/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -54,7 +54,7 @@
<div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>バグの報告</td></tr>
<tr class="heading"><td>インデックス</td></tr>
<tr class="index"><td><a href="#account">Tracのアカウントを取得する</a><br />
<a href="#report">バグレポートの作成</a><br />
<a href="#app">アプリケーションのバグ</a><br />
@@ -124,6 +124,7 @@ KDL ではキーボードが動作しないかもしれません。PS/2 キー
</table>
<p>詳細は <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Kernel Debugging Land へようこそ</a> も参照してください。</p>
<p>KDL はシリアルポートと syslog にも出力します (もしあるならば。シリアルケーブルをもう一つのコンピュータに接続し、出力を受け取ることが出来ます)。 KDL を終了することができない場合 syslog には出力されませんが、ブートローダーのデバッグ用オプションがそれを可能にするでしょう (下記も参照)。</p>
<p>KDL の出力から QR コードを生成することができます。QR コードは、スマートフォンなどを使ってテキストに変換できます。この機能を使って KDL のデータを取り出すことについては、次のブログ記事を参照してください。 <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> 。</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Syslog</a></h3>
docs/welcome/pt_PT/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -51,7 +51,7 @@
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Reporting bugs</td></tr>
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
<a href="#report">Creating a bug report</a><br />
<a href="#app">Application bugs</a><br />
@@ -121,6 +121,7 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
</table>
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Syslog</a></h3>
docs/welcome/ru/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -55,7 +55,7 @@
<div class="box-info">Перевод этой страницы еще не завершен. Пока это не произойдет, незавершенные части будут на английском.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Отчёт об ошибках (багах)</td></tr>
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Получение аккаунта в Trac</a><br />
<a href="#report">Создание отчёта об ошибке</a><br />
<a href="#app">Ошибки приложений</a><br />
@@ -127,6 +127,7 @@
</table>
<p>Для более подробной информации смотрите статью <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Добро пожаловать в Царство Отладки Ядра</a>.</p>
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Системный журнал</a></h3>
docs/welcome/sk/bugreports.html
+50 -49
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -53,76 +53,77 @@
<div class="box-info">Preklad tejto stránky zatiaľ nie je dokončený. Dovtedy sa nedokončené časti zobrazia v anglickom origináli.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Nahlasovanie chýb</td></tr>
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
<a href="#report">Creating a bug report</a><br />
<a href="#app">Application bugs</a><br />
<a href="#server">Server bugs</a><br />
<a href="#kernel">Kernel bugs</a><br />
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Získanie účtu v Trac</a><br />
<a href="#report">Vytvorenie hlásenia o chybe</a><br />
<a href="#app">Chyby aplikácií</a><br />
<a href="#server">Chyby serverov</a><br />
<a href="#kernel">Chyby jadra</a><br />
<a href="#kdl">Kernel Debugging Land - KDL</a><br />
<a href="#syslog">Syslog</a><br />
<a href="#onscreen">On screen debug output</a><br />
<a href="#hardware">Hardware/Driver bugs</a><br />
<a href="#next">What's next?</a></td></tr>
<a href="#onscreen">Výstup ladenia na obrazovku</a><br />
<a href="#hardware">Chyby hardvéru/ovládačov</a><br />
<a href="#next">Čo ďalej?</a></td></tr>
</table>
<h1>Nahlasovanie chýb</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>
<p>Keďže je nemožné, aby naši vývojári otestovali každú kombináciu hardvéru či každý možný spôsob interakcie s operačným systémom, spoliehame sa na našich používateľov, aby nám poslali spätnú väzbu ako veci fungujú u nich. Keďže Haiku je stále relatívne mladé, je veľmi pravdepodobné, že narazíte na chyby. ďakujeme vám za čas, ktorý venujete ich nahláseniu. Spolu môžeme Haiku vylepšovať, trochu po troche.</p>
<p>Aby bol náš nástroj na sledovanie chýb fungoval efektívne, je nevyhnutné dodržiavať <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Etiketu nástroja na sledovanie chýb</a>.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="account" name="accout">Getting a Trac account</a></h2>
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
<a id="account" name="accout">Získanie účtu v Trac</a></h2>
<p>Aby ste mohli založiť hlásenie, musíte mať účet v <a href="http://dev.haiku-os.org/register" title="Registrácia v nástroji na sledovanie chýb Haiku">Nástroji na sledovanie chýb Haiku</a>.<br />
Pri vytváraní účtu určite poskytnite <b>vašu emailovú adresu</b>, pretože je potrebné získať základné oprávnenia na zmenu hlásení. Určite sa krátko potom <b>pozrite aj do spamového priečinka</b>, pretože dôležité overovacie emaily tam často skončia.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="report" name="report">Creating a bug report</a></h2>
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&amp;status=assigned&amp;status=reopened&amp;status=closed&amp;summary=%7Etext+you+want+to+search+for&amp;order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">search</a> function for this.<br />
After you have established that it's a unique bug, make your information as accurate as possible:</p>
<a id="report" name="report">Vytvorenie hlásenia o chybe</a></h2>
<p>Pred nahlásením chyby sa prosím <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">uisitite</a>, že už nebola nahlásená. Tiež na to môžete použiť funkciu <a href="http://dev.haiku-os.org/search?q=&amp;noquickjump=1&amp;ticket=on">hľadanie</a>.<br />
Potom, ako ste sa uistili, že chyba je jedinečná, uveďte čo najpresnejšie vaše informácie:</p>
<ul>
<li><p>Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  <a href="http://haiku-files.org/">available</a>.</p></li>
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in <span class="menu">About Haiku...</span> from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.</p></li>
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the <span class="key">PRINT</span> key.</p></li>
<li><p>Pokúste sa reprodukovať problém v aktuálnej revízii Haiku. Sú pripravené <a href="http://haiku-files.org/">obrazy na testovacie účely</a>.</p></li>
<li><p>iveďte základné infomrácie o tom ako testujete Haiku (na skutočnom hardvéri, vo VMWare, v QEMU atď.).</p></li>
<li><p>Uveďte, ktorú revíziu zo <acronym title="Subversion, nástroj na správu zdrojového kódu, ktorý používame">SVN</acronym> používate. Túto informáciu nájdete v dialógu <span class="menu">O Haiku...</span> z menu Panela. Tiež uvete, aký druh Haiku testujete (gcc2, gcc4, gcc2hybrid, gcc4hybrid). Obsazy na stiahnutie sú podľa toho pomenované; pri obraze, ktorý ste zostavili sami by ste mali vedieť ako ste ho zostavili.</p></li>
<li><p>Popíšte váš problém. Skúste byč čo najpresnejší: popíšte správanie, ktoré ste očakávali a správanie, ktoré ste dostali.</p></li>
<li><p>Popíšte kroky, ktoré je potrebné vykonať na vyvolanie chyby. To pomôže vývojárom chybu reprodukovať.</p></li>
<li><p>Priložte všetky informácie,ktoré máte k dispozícii. Ak je to chyba používateľského rozhrania alebo chyba v niektorej z aplikácií, skúste urobiť snímku obrazovky stlačením klávesu <span class="key">Print Screen</span>.</p></li>
</ul>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="app" name="app">Application bugs</a></h2>
<p>When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering <span class="cli">bt</span>, you create a "backtrace" that you should copy in its entirety (including the part before you entered the <span class="cli">bt</span> command) and attach it to the ticket.</p>
<a id="app" name="app">Chyby aplikácií</a></h2>
<p>Keď aplikácia havaruje, mali by ste vyvolať ladiaci nástroj z upozornenia, ktoré vyskočí. To otvorí okno Terminálu, v ktorom beží gdb (GNU debugger). Zadaním <span class="cli">bt</span> vytvoríte „backtrace“, ktorý by ste mali kompletne skopírovať (vrátane časti zorbazenej než ste zadali príkaz <span class="cli">bt</span>) a priložiť ho k hláseniu.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="server" name="server">Server bugs</a></h2>
<p>When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.<br />
Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (<span class="cli">bt</span> command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.</p>
<a id="server" name="server">Chyby serverov</a></h2>
<p>Ak havarujú dôležité servery ako aplikačný server, registrátor alebo server vstupu, neuvidíte zvyčajné upozornenie na haváriu. Namiesto toho sa celá obrazovka zmaže na bielu farbu, spustí sa relácia gdb a jej výstup sa objaví priamo na obrazovke. Pravdepodobne budete môcť pohybovať myšou, čo prepíše bielu farbu a výstup gdb na obrazovke. Aplikácie, ktoré ešte bežia (ako ProcessController alebo hodiny v Paneli) tiež možno prekreslia časť ladiaceho výstupu na obrazovke.<br />
Okrem toho, že je všetko škaredšie a nepohodlné platí prakticky to isté ako pri chybách aplikácií. Predovšetkým získajte backtrace (príkaz <span class="cli">bt</span>). Možno budete musieť odfotiť obrazovku digitálnym fotoaparátom, pretože nebudete môcť text nikam skopírovať.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="kernel" name="kernel">Kernel bugs</a></h2>
<p>Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:</p>
<a id="kernel" name="kernel">Chyby jadra</a></h2>
<p>Chyby jadra sú zvyčajne tie, ktoré majú najzávažnejší vplyv a zároveň sa najťažšie ladia. Existujú rôzne druhy symptómov, ktoré pravdepodobne naznačujú problém s jadrom alebo ovládačom:</p>
<ul>
<li><p>The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "<i>Welcome to Kernel Debugging Land...</i>", the one above it states the immediate reason for entering KDL.</p></li>
<li><p>The system reboots spontaneously.</p></li>
<li><p>The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards). Wait at least a minute to see, if anything happens.</p></li>
<li><p>The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
<li><p>The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).</p></li>
<li><p>Systém svojvoľne vstúpi KDL (kernel debugging land). Horná časť obrazovky sa vyčistí do biela a vypíše sa na ňu niekoľko riadkov textu. Druhý riadok bude obsahovať „<i>Welcome to Kernel Debugging Land...</i>“ a ten nad ním bude obsahovať okamžitý dôvod, prečo bolo vyvolané KDL.</p></li>
<li><p>Systém sa spontánne reštartuje.</p></li>
<li><p>Systém kompletne zamrzne. Nemôžete hýbať myšou a žiadna aplikácia nič nevykresľuje. Dôležitý test v tejto situácii je, či ešte môžete vyvolať KDL klávesovou skratkou <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span> (<span class="key">SysReq</span> je na väčšine klávesníc <span class="key">PRINT</span>). Počkajte aspoň minútu, aby ste uvideli, či sa niečo stane.</p></li>
<li><p>Systém nenaštartuje korektne. Môže spontánne naštartovať alebo v niektorom bode zastaviť (napr. na niektorej ikone štartovacej obrazovky). V druhom prípade tiež skúste <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.</p></li>
<li><p>Celý systém alebo niektorá časť hardvéru sa nespráva korektne. Napríklad môže byť veľmi pomalý, vyskytnú sa chyby alebo niečo vôbec nefunguje. Ak nejaký hardvér vôbec nefunguje, prvá vec, ktorú treba skontrolovať je, či ho momentálne Haiku vôbec podporuje (napr. spýtať sa v poštovej konferencii alebo na fóre).</p></li>
</ul>
<p>Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
<p>pamätajte, že hoci iba posledný bod indikuje súvislosť s hardvérom, všetky ostatné symptómy môžu byť spôsobené aj chybou v ovládači hardvéru. Ak máte podozrenie, ktorá časť hardvéru alebo zodpovedajúci ovládač môže súvisieť s problémom, skontrolujte, či odstránenie alebo vypnutie hardvéru či ovládača pomôže. Napríklad ak podozrievate Wi-Fi, možno zistíte, že váš BIOS umožňuje ju vypnúť. Alebo ak nie, môžete odstrániť príslušný ovládač Wi-Fi z vašej inštalácie Haiku (v <span class="path">/boot/system/add-ons/kernel/drivers/bin</span>).</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="kdl" name="kdl">Kernel Debugging Land - KDL</a></h3>
<p>If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.</p>
<p>KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:</p>
<p>Ak systém sám nevstúpil do KDL, môžete ho úmyselne vyvolať klávesovou skratkou <span class="key">ALT</span> <span class="key">SysReq</span> <span class="key">D</span>.<br />
Pamätajte, že v KDL vaša klávesnica nemusí fungovať. Klávesnice PS/2 fungujú vždy, klávesnice USB pripojené prostredníctvom ovládačov UHCI fungujú iba ak už aspoň raz ste vstúpili do KDL použitím klávesovej skratky. USB OHCI momentálne nie je podporované.</p>
<p>Samotné KDL je istým druhom shellu. Môžete vykonávať príkazy, ktoré vypisujú informácie o systéme. Nasledovné príkazy môžu byť zaujímavé:</p>
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
<tr><td><span class="cli">bt</span> (aka sc)</td><td> </td><td>Prints a back trace. If the system entered KDL on its on volition, always enter that one.</td></tr>
<tr><td><span class="cli">ints</span></td><td> </td><td>Shows the handled and unhandled hardware interrupts.</td></tr>
<tr><td class="onelinetop"><span class="cli">co</span> (aka continue)</td><td> </td><td>Leaves the kernel debugger and continues normal operation of the system, if that is possible.</td></tr>
<tr><td><span class="cli">reboot</span></td><td> </td><td>Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.</td></tr>
<tr><td><span class="cli">bt</span> (resp. sc)</td><td> </td><td>Vypíše backtrace. Ak systém svojvoľne vstúpil do KDL, vždy ho spustite.</td></tr>
<tr><td><span class="cli">ints</span></td><td> </td><td>Zobrazí ošetrené a neošetrené hardvérové prerušenia.</td></tr>
<tr><td class="onelinetop"><span class="cli">co</span> (resp. continue)</td><td> </td><td>Opustí ladenie jadra a pokračuje v normálnej prevádzke systému ak je to možné.</td></tr>
<tr><td><span class="cli">reboot</span></td><td> </td><td>Okamžite reštartuje systém. Stratíte všetky neuložené dáta a aj tie, ktoré už boli uložené, ale zatiaľ neboli zapísané na disk.</td></tr>
</table>
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
<p>Ďalšie informácie nájdete v článku <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>Výstup KDL sa zapisuje na sériový port (ak ho máte a ak máte príslušný kábel na pripojenie druhého počítača, môžete prostredníctvom neho zachytiť výstup pomocou terminálového programu) a do syslogu. Ak nemôžete opustiť KDL, nezapíše však sa do súboru syslog. Existuje voľba zavádzača systému, ktorá vám umožňuje zachytiť ho napriek tomu (pozri nižšie).</p>
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Syslog</a></h3>
@@ -132,14 +133,14 @@ The syslog (short for system log) contains valuable information about what has h
In the boot loader's <span class="menu">Debug menu</span> you should now find the entries <span class="menu">Display syslog from previous session</span> and <span class="menu">Save syslog from previous session</span>. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="onscreen" name="onscreen">On screen debug output</a></h3>
<a id="onscreen" name="onscreen">Výstup ladenia na obrazovku</a></h3>
<p><b>The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.</b><br />
This is only relevant when Haiku fails to boot on your machine and the <span class="menu">Debug syslog option</span> doesn't work for some reason. Before the Haiku boot logo appears, hold <span class="key">SHIFT</span> to enter the boot loader menu. Select <span class="menu">Select safe mode options</span>. Near the bottom, <span class="menu">[ ] Enable on screen debug output</span> will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)<br />
Finally select <span class="menu">Return to main menu</span> and then <span class="menu">Continue booting</span>.<br />
One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the <a href="../../../userguide/sk/bootloader.html">Boot Loader</a>.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="hardware" name="hardware">Hardware/Driver bugs</a></h2>
<a id="hardware" name="hardware">Chyby hardvéru/ovládačov</a></h2>
<p>When dealing with a hardware/driver related bug, you should attach the following information as text files:</p>
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
@@ -154,7 +155,7 @@ One or more pages of text will display on the screen, only the last few lines ne
<p>The first four commands are entered into Terminal. Add a <span class="cli"> &gt; output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
<h2><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="next" name="next">What's next?</a></h2>
<a id="next" name="next">Čo ďalej?</a></h2>
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
non-descriptive comments.</p>
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
docs/welcome/sv_SE/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -53,7 +53,7 @@
<div class="box-info">Översättningen av denna sida är inte komplett. Delar av innehållet kommer därför att visas på engelska.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Buggrapportering</td></tr>
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
<a href="#report">Creating a bug report</a><br />
<a href="#app">Application bugs</a><br />
@@ -123,6 +123,7 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
</table>
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Systemloggen</a></h3>
docs/welcome/uk/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -51,7 +51,7 @@
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Reporting bugs</td></tr>
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td><a href="#account">Getting a Trac account</a><br />
<a href="#report">Creating a bug report</a><br />
<a href="#app">Application bugs</a><br />
@@ -121,6 +121,7 @@ Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keybo
</table>
<p>For more information, see the article <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">Welcome to Kernel Debugging Land</a>.</p>
<p>The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).</p>
<p>You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> on how to get data out of KDL using that feature.</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">Syslog</a></h3>
docs/welcome/welcome_de.html
+20 -4
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -52,9 +52,23 @@
<div id="content">
<div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Willkommen zu Haiku!</a><br />
<a href="#bugreport">Achtung, Bugs!</a><br />
<a href="#system">Das System kennenlernen</a><br />
<a href="#software">Software installieren</a><br />
<a href="#wifi">WLAN in Haiku</a><br />
<a href="#api">Die API kennenlernen</a><br />
<a href="#contact">Kontakte knüpfen</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Willkommen zu Haiku!</a></h2>
<p>Danke, für das Interesse an Haiku! Wir hoffen, dass wir durch die dritte öffentliche Version neue Entwickler für unser Projekt begeistern können und Anwendern die Möglichkeit geben, Haiku kennenzulernen. Natürlich ist diese <i>Alpha Version</i> noch 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>
<p>Auf der Projektseite <a hrf="http://www.haiku-os.org">Haiku-os.org</a> finden sich immer die neuesten Ankündigungen und Entwicklungen.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -96,25 +110,27 @@ Dazu benutzt man einen Befehl im Terminal: <tt>installoptionalpackage -h</tt> er
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">WLAN in Haiku</a></h2>
<p>WLAN funktioniert in gewissem Rahmen. Momentan kann man nur ungeschützte oder WEP verschlüsselte Funknetzwerke nutzen. Wegen verschiedener Lizenzbedingungen der unterschiedlichen Hersteller, ist gegebenenfalls eine manuelle Installation der Firmware nötig. Eine Liste der unterstützten Geräte und Hinweise für eine eventuell erforderliche Installation befindet sich auf der <a href="de/wifi.html">WLAN</a> Seite (auch <a href="http://www.haiku-os.org/guides/wifi">online</a> auf Englisch).</p>
<p>Haiku unterstützt neben unverschlüsselten Funknetzwerken auch mittels WPA/WPA2 und WEP gesicherte Verbindungen. Wegen verschiedener Lizenzbedingungen der unterschiedlichen Hardware-Hersteller, ist gegebenenfalls eine manuelle Installation von Firmware nötig. Mehr Information zu unterstützter Hardware, Installieren von Firmware und wie man eine WLAN-Verbindung herstellt, finden sich im <a href="../userguide/de/workshop-wlan.html">Workshop: Funknetzwerke nutzen</a> des Haiku User Guides.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Die API kennenlernen</a></h2>
<p>Da Haiku eine Reimplementierung des BeOS R5 ist, sind die API die gleichen (mit einigen Erweiterungen). Deshalb ist die Dokumentation im Be Book immer noch eine hilfreiche Quelle. Dankenswerterweise hat die Firma ACCESS, die alle Rechte von Be Inc. übernommen hat, einer Veröffentlichung des Be Book zugestimmt.</p>
<p>Da Haiku eine Reimplementierung des BeOS R5 ist, sind die API die gleichen (mit einigen Erweiterungen). Deshalb ist die Dokumentation im Be Book immer noch eine hilfreiche Quelle. Dankenswerterweise hat die Firma ACCESS, die alle Rechte von Be Inc. übernommen hat, einer Veröffentlichung des Be Book zugestimmt.<br />
Abweichungen von der BeOS API und Haiku-spezifische Erweiterungen werden im Haiku Book gesammelt.</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">Entwickler FAQ</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Sourcecode-Browser</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Be Book</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archiv</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 Entwicklern und Anwendern auszutauschen, muss man nur an den Diskussionen im IRC, unseren Foren oder Mailinglisten teilnehmen. Wie üblich, wenn sich mehrere Menschen unterhalten, sollte eine gewisse <a href="http://www.haiku-os.org/community/ml/etiquette">Etikette</a> eingehalten werden.</p>
<p>Um sich mit anderen Entwicklern und Anwendern auszutauschen, kann man an Diskussionen im IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>), in den Foren oder auf Mailinglisten teilnehmen. Wie üblich, wenn sich mehrere Menschen unterhalten, sollte eine gewisse <a href="http://www.haiku-os.org/community/ml/etiquette">Etikette</a> eingehalten werden.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC Kanäle</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Foren</a></li>
docs/welcome/welcome_en.html
+21 -5
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -48,9 +48,23 @@
<div id="content">
<div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Welcome to Haiku!</a><br />
<a href="#bugreport">Beware of Bugs</a><br />
<a href="#system">Getting to know the system</a><br />
<a href="#software">Installing new software</a><br />
<a href="#wifi">Wifi in Haiku</a><br />
<a href="#api">Getting to know the API</a><br />
<a href="#contact">Getting in contact</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
<p>Thank you very much for checking out Haiku! This is our third public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -92,25 +106,27 @@ You'll have to run a command in Terminal: <tt>installoptionalpackage -h</tt> exp
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Wifi in Haiku</a></h2>
<p>Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our <a href="en/wifi.html">Wifi</a> page (also <a href="http://www.haiku-os.org/guides/wifi">online</a>).</p>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/en/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Getting to know the API</a></h2>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.</p>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>There are additional resources that should help you getting started:</p>
<p>There are some resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Browser</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Getting in contact</a></h2>
<p>Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
docs/welcome/welcome_es.html
+21 -5
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -52,9 +52,23 @@
<div>
<div class="box-info">La traducción de esta página no está completa aún. Hasta que esté, las partes sin terminar vienen en su inglés original.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Welcome to Haiku!</a><br />
<a href="#bugreport">Beware of Bugs</a><br />
<a href="#system">Getting to know the system</a><br />
<a href="#software">Installing new software</a><br />
<a href="#wifi">Wifi in Haiku</a><br />
<a href="#api">Getting to know the API</a><br />
<a href="#contact">Getting in contact</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">¡Bienvenido a Haiku!</a></h2>
<p>Thank you very much for checking out Haiku! This is our third public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -96,25 +110,27 @@ Al correrse el siguiente comando en una Terminal: <tt>installoptionalpackage -h<
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Wifi en Haiku</a></h2>
<p>La red inalámbrica (Wifi) trabaja hasta cierto punto. Al momento se puede conectar a redes inalámbricas con encripción WEP. Debido a políticas de licencias diferentes de fabricantes diferengtes, se puede requerir un proceso de instalación manual del firmware. Una lista de dispositivos funcionando e instrucciones para instalación se pueden encontrar en nuestra página <a href="es/wifi.html">Wifi</a> (también disponible <a href="http://www.haiku-os.org/guides/wifi">en línea</a>).</p>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/es/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Habituándose a 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, quien tiene los derechos de la antigua Be Inc., se nos permite distribuir una copia del BeBook.</p>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>Existen algunos recursos que le pueden ayudar a comenzar:</p>
<p>There are some resources that should help you getting started:</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">El BeBook (Descripción de la API de Be)</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">El archivo de la revista 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">Ponerse en contacto</a></h2>
<p>Le invitamos a entrar en contacto con otros desarrolladores y usuarios y unirse a las conversaciones del canal IRC, los foros 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>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canales IRC</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Foros</a></li>
docs/welcome/welcome_fi.html
+56 -40
View File
@@ -4,23 +4,25 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Humdinger <humdingerb@gmail.com>
* Stephan Aßmus <superstippi@gmx.de>
* Translators:
* Karvjorm
*
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Welcome to Haiku!</title>
<title>Tervetuloa Haikuun!</title>
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
</head>
<body>
<div id="banner">
<div><span>User guide</span></div>
<div><span>Käyttäjäopas</span></div>
</div>
<div class="nav">
@@ -47,78 +49,92 @@
<div id="content">
<div>
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
<div class="box-info">Tämän sivun kotoistaminen ei ole vielä täydellinen. Siihen asti keskeneräiset osat käyttävät englanninkielistä alkuperäistekstiä.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Tervetuloa Haikuun!</a><br />
<a href="#bugreport">Varo ohjelmistovikoja</a><br />
<a href="#system">Järjestelmään tutustuminen</a><br />
<a href="#software">Lisäohjelmistojen asentaminen</a><br />
<a href="#wifi">Wifi-verkot Haikussa</a><br />
<a href="#api">Tutustuminen sovellusohjelmointirajapintaan</a><br />
<a href="#contact">Yhteydenotot</a></td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
<p>Thank you very much for checking out Haiku! This is our third public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
<a id="welcome" name="welcome">Tervetuloa Haikuun!</a></h2>
<p>Kiitoksia oikein paljon, että latasit Haiku-käyttöjärjestelmän! Tämä on kolmas julkinen julkaisumme. Toivomme houkuttelevamme uusia kehittäjiä hankkeeseemme ja antavamme tuleville käyttäjillä mahdollisuuden tutustua Haikuun. Tiedämme, että tämä <i>alfa-julkaisu</i> ei vielä täytä niitä odotuksia, jotka olemme asettaneet itsellemme ja se ei tarjoa kaikkia ominaisuuksia ja lopullisen R1-version täysiä käyttäjäkokemuksia. Toivomme kuitenkin, että tämä julkaisu antaa sinulle mahdollisuuden löytää Haikun suuren potentiaalin ja että jaat meidän innostuksemme.</p>
<p>Vieraile projektimme kotisivulla <a hrf="http://www.haiku-os.org">Haiku-os.org</a> saadaksesi viimeisimmät uutiset ja tiedonannot.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">Beware of Bugs</a></h2>
<p>We have been working hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.</p>
<div class="box-warning">We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.</div>
<a id="bugreport" name="bugreport">Varo ohjelmistovikoja</a></h2>
<p>Olemme työskennelleet kovasti korjataksemme kaikki mahdolliset esityksen pysäyttävät viat, mutta kuitenkin tämä on ohjelmiston alfa-julkaisu, ja siinä on jäljellä runsaasti löytämättömiä vikoja</p>
<div class="box-warning">Emme suosittele käyttämään alfa-versioita tuotantojärjestelmänä. Tietosi voivat aivan hyvin muuttua, vääristyä tai suorastaan tuhoutua.</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>
<p>Yksi pääsyy alfa-versioiden julkaisemiseen on houkutella lisää ihmisiä järjestelmän testaamiseen ja vikojen havaitsemiseen tai tarjota ehdotuksia tulevista laajennuksista. Ilmoita vioista ja laajennuksista vikaseuraajajärjestelmässämme sen jälkeen kun olet käyttänyt sen etsintätoimintoa kaksoiskappaleilmoitusten estämiseksi.</p>
<ul>
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku Bug Tracker</a></li>
<li><a href="fi/bugreports.html">Tips for a helpful bug report</a></li>
<li><a href="http://dev.haiku-os.org/wiki" class="printurl">Haiku-vikaseuraaja</a></li>
<li><a href="fi/bugreports.html">Vihjeitä hyödyllisiä vikailmoituksia varten</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>
<a id="system" name="system">Järjestelmään tutustuminen</a></h2>
<p>Haikun ensimmäiset julkaisut ovat paljolti kuin BeOS R5, käyttöjärjestelmän uudelleentoteutus. Jos et ole koskaan kokenut sitä, vilkaise näitä linkkejä:</p>
<ul>
<li><a href="../userguide/fi/contents.html">Haiku User Guide</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">List of BeOS/Haiku websites</a></li>
<li><a href="../userguide/fi/contents.html">Haiku-käyttäjäopas</a></li>
<li><a href="http://www.haiku-os.org/community/" class="printurl">BeOS/Haiku -webbisivustojen luettelo</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">Installing more software</a></h2>
<p>Because of our binary and source compatibility, many BeOS applications run on Haiku (you may have to install the optional package "beoscompatibility" for some programs, see below). After downloading a package, simply unzip it (double clicking opens <span class="app">Expander</span>) to <span class="path">/boot/apps/</span> and start the application from there.</p>
<a id="software" name="software">Lisäohjelmistojen asentaminen</a></h2>
<p>Binaari- ja lähdekoodiyhteensopivuuden vuoksi monia BeOS-sovelluksia voidaan suorittaa Haikussa (sinun on ehkä asennettava valinnainen paketti ”beoscompatibility” joitakin ohjelmia varten, katso alla). Yksinkertaisesti pura pakkaus latauksen jälkeen (hiiren kaksoisnapsautus avaa <span class="app">Laajentaja</span>n) kansioon <span class="path">/boot/apps/</span> ja käynnistä sovellus sieltä.</p>
<p>Popular software repositories are:</p>
<p>Suosittuja ohjelmistovarastoja ovat:</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://ports.haiku-files.org/" class="printurl">HaikuPorts</a> - ylläpitää siirretyn ohjelmiston korjauksia</li>
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - ylläpitää aitoja BeOS- ja Haiku open source -ohjelmistohankkeita</li>
</ul>
<p>There are also so-called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. Instead, a utility script is provided, <tt>installoptionalpackage</tt>. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.<br />
You'll have to run a command in Terminal: <tt>installoptionalpackage -h</tt> explains its usage.</p>
<p>Haikun rakentamisjärjestelmässä käytetään myös niin sanottuja valinnaisia pakkauksia. Ei ole tarkoitus, että loppukäyttäjät manuaalisesti purkavat ja asentavat pakkaukset. Sen sijaan tarkoitusta varten on apuohjelmaskripti <tt>installoptionalpackage</tt>. Tämän skriptin tarkoitus on täyttää aukko, joka johtuu siitä, että Haikun pakettihallinta on vielä suunnitteilla. Skripti sallii sinun asentaa useimmat saatavilla olevat valinnaiset pakkaukset.<br />Sinun on suoritettava komento Pääteikkunassa: <tt>installoptionalpackage -h</tt> selittää sen käytön.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Wifi in Haiku</a></h2>
<p>Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our <a href="fi/wifi.html">Wifi</a> page (also <a href="http://www.haiku-os.org/guides/wifi">online</a>).</p>
<a id="software" name="wifi">Wifi-verkot Haikussa</a></h2>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/fi/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Getting to know the API</a></h2>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.</p>
<a id="api" name="api">Tutustuminen sovellusohjelmointirajapintaan</a></h2>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>There are additional resources that should help you getting started:</p>
<p>There are some resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Browser</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Kehitys-UKK</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Lähdekoodiselain</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Be-kirja</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">Haiku-kirja</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be-uutiskirjearkisto</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Getting in contact</a></h2>
<p>Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<a id="contact" name="contact">Yhteydenotot</a></h2>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
<li><a href="http://www.freelists.org/list/haiku" class="printurl">General mailing list</a></li>
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Development mailing list concerning Haiku itself</a></li>
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Mailing list for 3rd party application programmers</a></li>
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Overview of all mailing lists</a></li>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC-kanavat</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Foorumit</a></li>
<li><a href="http://www.freelists.org/list/haiku" class="printurl">Yleinen sähköpostilista</a></li>
<li><a href="http://www.freelists.org/list/haiku-development" class="printurl">Haikua itseä koskeva kehityssähköpostilista</a></li>
<li><a href="http://www.freelists.org/list/haiku-3rdparty-dev" class="printurl">Kolmannen osapuolen sovellusohjelmoijien sähköpostilista</a></li>
<li><a href="http://www.haiku-os.org/community/ml" class="printurl">Kaikkien sähköpostilistojen yleiskatsaus</a></li>
</ul>
</div>
docs/welcome/welcome_fr.html
+22 -8
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -51,10 +51,25 @@
<div id="content">
<div>
<div class="box-info">Cette page n'est pas encore entièrement traduite. Les parties non encore traduites seront en anglais.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Welcome to Haiku!</a><br />
<a href="#bugreport">Beware of Bugs</a><br />
<a href="#system">Getting to know the system</a><br />
<a href="#software">Installing new software</a><br />
<a href="#wifi">Wifi in Haiku</a><br />
<a href="#api">Getting to know the API</a><br />
<a href="#contact">Getting in contact</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Bienvenue sur Haiku !</a></h2>
<p>Merci beaucoup d’essayer Haiku ! Voici notre troisième 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 tous 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 version (même inachevée) vous permettra de découvrir le potentiel de Haiku et de partager notre enthousiasme.</p>
<p>Visitez le site de notre projet <a hrf="http://www.haiku-os.org">Haiku-os.org</a> pour rester informé des dernières évolutions.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -99,28 +114,27 @@ Vous devrez saisir une ligne de commande dans le Terminal :
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Le wifi dans Haiku</a></h2>
<p>Le Wifi ne fonctionne que partiellement. Pour le moment vous ne pouvez vous connecter qu'à des réseaux sans fils non-sécurisés ou à ceux cryptés en WEP. En raison des politiques de licence de certains fournisseurs, il peut être nécessaire d'installer manuellement le micro-logiciel de votre adaptateur réseau. Une liste des périphériques et leurs instructions d'installation peuvent être trouvées sur notre page <a href="fr/wifi.html">Wifi</a> (ou <a href="http://www.haiku-os.org/guides/wifi">en ligne</a>).</p>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/fr/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<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 la 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>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>Quelques ressources supplémentaires sont susceptible de vous aider à commencer :</p>
<p>Quelques ressources sont susceptibles 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">Le BeBook</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">Le Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">L'archive 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">Rester en contact</a></h2>
<p>Entrez en contact avec les autres développeurs et utilisateurs, participez 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. Veuillez respecter
<a href="http://www.haiku-os.org/node/2517">l'étiquette de notre liste de diffusion</a>.</p>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canaux IRC</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
docs/welcome/welcome_it.html
+22 -5
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -49,11 +49,26 @@
<div id="content">
<div>
<div class="box-info">La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Welcome to Haiku!</a><br />
<a href="#bugreport">Beware of Bugs</a><br />
<a href="#system">Getting to know the system</a><br />
<a href="#software">Installing new software</a><br />
<a href="#wifi">Wifi in Haiku</a><br />
<a href="#api">Getting to know the API</a><br />
<a href="#contact">Getting in contact</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Benvenuto in Haiku!</a></h2>
<p>Grazie per aver deciso di provare Haiku! Questa è la nostra terza release al pubblico. Speriamo di attrarre nuovi sviluppatori al nostro progetto e dare agli utenti futuri una possibilità di provare Haiku. Ci rendiamo conto che quest'<i>alpha release</i> non è ancora completamente all'altezza degli obiettivi che ci siamo fissati e non offre tutte le funzionalità e un'esperienza piacevole e bilanciata per l'utente finale pianificate per la versione R1 definitiva. Comunque, speriamo che questa release ti faccia scoprire il grande potenziale di Haiku e ti faccia condividere il nostro entusiasmo.
</p>
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
@@ -95,25 +110,27 @@ Dovrai far partire il comando nel terminale; <tt>installoptionalpackage -h</tt>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
<a id="software" name="wifi">Il Wifi in Haiku</a></h2>
<p>Il Wifi funziona fino ad un certo punto. Per il momento puoi solo connetterti in network wireless non criptati o che sono criptati attraverso il protocollo WEP. A causa di politiche di licenza diverse a seconda del fornitore, il firmware potrebbe richiedere un processo di installazione manuale. Una lista dei dispositivi funzionanti e delle relative istruzioni per la loro installazione può essere trovata nella nostra pagina sul <a href="it/wifi.html">Wifi</a> (disponibile anche <a href="http://www.haiku-os.org/guides/wifi">online</a>).</p>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/it/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
<a id="api" name="api">Per conoscere l'API</a></h2>
<p>Essendo Haiku una re-implementazione, l'API è ancora la stessa del BeOS R5 (con alcune aggiunte), quindi la documentazione presente nel Be Book è ancora una risorsa valida di informazioni. Grazie ad ACCESS, azienda proprietaria dei diritti sulle risorse un tempo della Be Inc., abbiamo il permesso di fornire una copia del Be Book.</p>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>Ci sono altre risorse che dovrebbero aiutarti nell'iniziare a programmare per Haiku:</p>
<p>There are some resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ degli sviluppatori</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Browser del codice sorgente</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Il Be Book</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Achivio delle newsletter della Be Inc.</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="indice" /></a>
<a id="contact" name="contact">Entrare in contatto</a></h2>
<p>Entra in contatto con altri sviluppatori e utenti e partecipa alle discussioni in chat, nei nostri forum o mailing list. Quando molte persone diverse si incontrano, si devono stabilire regole per fare in modo che la comunicazione sia fruttifera, ti preghiamo quindi di rispettare la nostra <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Canali di chat</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">I forum</a></li>
docs/welcome/welcome_jp.html
+26 -11
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -18,7 +18,7 @@
-->
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="robots" content="all" />
<title>Haikuへようこそ！</title>
<title>Haiku へようこそ！</title>
<link rel="stylesheet" type="text/css" href="Haiku-doc.css" />
</head>
<body>
@@ -52,15 +52,29 @@
<div id="content">
<div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>インデックス</td></tr>
<tr class="index"><td>
<a href="#welcome">Haiku へようこそ!</a><br />
<a href="#bugreport">バグに注意</a><br />
<a href="#system">システムを把握する</a><br />
<a href="#software">ソフトウェアを追加する</a><br />
<a href="#wifi">Haiku での Wifi</a><br />
<a href="#api">API を理解する</a><br />
<a href="#contact">連絡を取り合う</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Haikuへようこそ！</a></h2>
<a id="welcome" name="welcome">Haiku へようこそ！</a></h2>
<p>Haiku を選んでくれてとてもうれしいよ！これは私たちの 3 番目の公式リリースです。私たちは新しい開発者をプロジェクトに迎え入れて、将来のユーザーに Haiku を選択してもらう機会を与えたいと考えています。この<i>アルファ版</i>が私たちが設定した目標を完全に満たしているものではなく、すべての機能を提供しているわけではないと理解しています。また、幅広いエンドユーザー・エクスペリエンスによって最終的な R1 バージョンの計画を立てました。しかしながら、あなたがこのリリースで Haiku の素晴らしいポテンシャルに気づき、私たちの興奮を共有してくれることを願っています。</p>
<p>最新のニュースとお知らせは、私たちのプロジェクトのウエブサイト、<a hrf="http://www.haiku-os.org">Haiku-os.org</a> にアクセスしてください。</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="bugreport" name="bugreport">バグに注意</a></h2>
<p>私たち開発チームはできるだけバグを修正することに努めています。しかし、これはアルファ版です。まだ見つかっていないたくさんのバグが残っているかもしれません。</p>
<div class="box-warning">私たちはアルファ版を実際の場面で使うことを望んではいません。あなたのデータは壊れたり、無くなったりするかもしれません。</div>
<div class="box-warning">私たちはアルファ版を実際の場面で使うことを望んではいません。あなたのデータは壊れたり、めちゃくちゃになったり、無くなったりするかもしれません。</div>
<p>私たちがアルファ版をリリースした理由の一つに、もっとたくさんの人に Haiku を触ってもらい、システムのテストとバグの発見など、Haiku の向上を目指すためがあります。バグを見つけた場合、バグトラッカーで検索してまだ報告されていなければ (重複を防ぐために) 報告していただけると助かります。</p>
<ul>
@@ -80,7 +94,7 @@
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="software">ソフトウェアを追加する</a></h2>
<p>だいたいの BeOS 向けアプリケーションは Haiku でもバイナリとソースコードの互換性から動くと思われます。 (ただし、オプションの "beoscompatibility" パッケージのインストールが必要です) パッケージをダウンロードし、<span class="path">/boot/apps/</span> に unzip (ダブルクリックで <span class="app">ファイル解凍</span> が開きます) することでアプリケーションを起動できます。</p>
<p>だいたいの BeOS 向けアプリケーションは Haiku でもバイナリとソースコードの互換性から動くと思われます (ただし、オプションの "beoscompatibility" パッケージのインストールが必要です)。パッケージをダウンロードし、<span class="path">/boot/apps/</span> に unzip (ダブルクリックで、<span class="app">ファイル解凍</span>が開きます) することでアプリケーションを起動できます。</p>
<p>有名なソフトウェアのレポジトリの一覧:</p>
<ul>
@@ -90,31 +104,32 @@
<li><a href="http://www.osdrawer.net/" class="printurl">OsDrawer</a> - ネイティブ BeOS と Haiku のソフトウェアを提供しています</li>
</ul>
<p>Haiku のビルドシステムで使われているオプショナルパッケージというものがあります。これはユーザーが手動で展開・インストールを行うために用意はされていません。そのかわり、<tt>installoptionalpackage</tt> というユーティリティスクリプトが用意されています。このスクリプトは Haiku のパッケージ管理システム (まだ未完成) の穴を埋めるためのもので、たくさんのオプショナルパッケージのインストールを容易にするために用意されています。<br />
<p>Haiku のビルドシステムで使われているオプショナルパッケージというものがあります。これはユーザーが手動で展開・インストールを行うために用意はされていません。そのかわり、<tt>installoptionalpackage</tt> というユーティリティスクリプトが用意されています。このスクリプトは未完成の Haiku のパッケージ管理システムの穴を埋めるためのもので、たくさんのオプショナルパッケージのインストールを容易にするために用意されています。<br />
以下のコマンドをターミナルで実行することで使い方を知ることができます: <tt>installoptionalpackage -h</tt></p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Haiku での Wifi</a></h2>
<p>Wifi は一部動作します。今現在、WEP で暗号化されているか、暗号化されていないワイヤレスネットワークのみサポートされています。これはいくつかのベンダーの異なるライセンスによるもので、Wifi のファームウェアの手動インストールが必要です。動作するデバイスのリストとファームウェアのインストールプロセスは <a href="jp/wifi.html">Wifi</a> ページを参照ください。 (そのページの<a href="http://www.haiku-os.org/guides/wifi">オンライン版</a>もあわせてご覧ください)。</p>
<p>Haiku は、WPA/WPA2 または WEP で暗号化されているか、または暗号化されていないワイヤレスネットワークをサポートしています。異なるハードウェアベンダーの様々なライセンスポリシーのため、ファームウェアインストールプロセスのマニュアルが必要となるでしょう。サポートされたハードウェア、ファームウェアのインストール、そしてワイヤレスネットワークへの接続方法についての詳しい情報は、ユーザーガイドの <a href="../userguide/jp/workshop-wlan.html">ワークショップ: ワイヤレスネットワーク</a>で見つかるでしょう。</p>
<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 は再実装のため、APIは BeOS R5 と同じで少しの追加だけになっています。そのため、Be Book にあるドキュメントはまだ有用な情報です。 Be Inc. を持つ ACCESS に感謝します。私たちは Be Book のコピーを提供することを許可されました。</p>
<a id="api" name="api">API を理解する</a></h2>
<p>Haiku は再実装のため、API は BeOS R5 とまだ同じです (少しの追加があります)。そのため、Be Book にあるドキュメントはまだ有用な情報です。Be Inc. を持つ ACCESS に感謝します。私たちは Be Book のコピーを提供することを許可されました。<br />BeOS API から離れたところ、および Haiku 固有の追加事項は Haiku Book に集められています。</p>
<p>以下があなたを助けるであろう追加のドキュメントです:</p>
<p>以下は、読者が始めるのに手助けになると思われる追加のドキュメントです。</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">開発 FAQ</a></li>
<li><a href="http://cgit.haiku-os.org/" class="printurl">ソースブラウザー</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">Be Book</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be ニュースレター アーカイブ</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/community/ml/etiquette">メーリングリストでのルール</a> に準拠して行動をするようにお願いします。</p>
<p>IRC (webchat 上の <a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>) や私たちのフォーラム、メーリングリストでほかの開発者やユーザーと連絡や議論ができます。たくさんの人々が一緒に活動をするには、ルールにしっかりと準拠して行動をする必要があります。<a href="http://www.haiku-os.org/community/ml/etiquette">メーリングリストでのルール</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>
docs/welcome/welcome_pt_PT.html
+21 -5
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -49,9 +49,23 @@
<div>
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Welcome to Haiku!</a><br />
<a href="#bugreport">Beware of Bugs</a><br />
<a href="#system">Getting to know the system</a><br />
<a href="#software">Installing new software</a><br />
<a href="#wifi">Wifi in Haiku</a><br />
<a href="#api">Getting to know the API</a><br />
<a href="#contact">Getting in contact</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Welcome to Haiku!</a></h2>
<p>Thank you very much for checking out Haiku! This is our third public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this <i>alpha release</i> does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.</p>
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -93,25 +107,27 @@ You'll have to run a command in Terminal: <tt>installoptionalpackage -h</tt> exp
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Wifi in Haiku</a></h2>
<p>Wifi does work to some extent. At the moment you can only connect to unencrypted or WEP encrypted wireless networks. Due to several different licensing policies of different vendors, a manual installation process for the firmware may be required. A list of working devices and instructions for installation can be found on our <a href="pt_PT/wifi.html">Wifi</a> page (also <a href="http://www.haiku-os.org/guides/wifi">online</a>).</p>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/pt_PT/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Getting to know the API</a></h2>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.</p>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>There are additional resources that should help you getting started:</p>
<p>There are some resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Development FAQ</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Browser</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be Newsletter Archive</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Getting in contact</a></h2>
<p>Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC channels</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forums</a></li>
docs/welcome/welcome_ru.html
+22 -5
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -52,10 +52,25 @@
<div id="content">
<div>
<div class="box-info">Перевод этой страницы еще не завершен. Пока это не произойдет, незавершенные части будут на английском.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Welcome to Haiku!</a><br />
<a href="#bugreport">Beware of Bugs</a><br />
<a href="#system">Getting to know the system</a><br />
<a href="#software">Installing new software</a><br />
<a href="#wifi">Wifi in Haiku</a><br />
<a href="#api">Getting to know the API</a><br />
<a href="#contact">Getting in contact</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Добро пожаловать в Haiku!</a></h2>
<p>Большое спасибо за проявленный интерес к Haiku! Это наш третий публичный релиз, мы надеемся привлечь новых разработчиков к нашему проекту и дать будущим пользователям шанс увидеть Haiku в деле. Нужно понимать, что этот <i>альфа-релиз</i> далеко не полностью соответствует намеченным нами целям, и не предоставляет все функции, которые мы собирались предоставить конечному пользователю, запланировав их для финальной версии R1. Однако мы надеемся, что этот релиз позволит вам заметить большой потенциал Haiku, и вы уделите немного времени для её изучения.</p>
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -98,25 +113,27 @@
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Wifi в Haiku</a></h2>
<p>Wifi поддерживается частично. В настоящий момент возможно подключение к незащищенным сетям или к сетям, защищенным WEP шифрованием. Из-за разных лицензионных политик разных производителей возможно потребуется ручная установка микропрогаммы (firmware). Список работающих устройств и инструкции по установке можно посмотреть на нашей странице <a href="ru/wifi.html">Wifi</a> (а также <a href="http://www.haiku-os.org/guides/wifi">в Интернете</a>).</p>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/ru/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<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>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>Существуют и другие ресурсы, которые должны помочь Вам начать изучение:</p>
<p>There are some resources that should help you getting started:</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://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Архив Be Newsletter</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/community/ml/etiquette">этикета списков рассылки</a>.</p>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC каналы</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Форумы</a></li>
docs/welcome/welcome_sk.html
+22 -5
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -49,10 +49,25 @@
<div id="content">
<div>
<div class="box-info">Preklad tejto stránky zatiaľ nie je dokončený. Dovtedy sa nedokončené časti zobrazia v anglickom origináli.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Welcome to Haiku!</a><br />
<a href="#bugreport">Beware of Bugs</a><br />
<a href="#system">Getting to know the system</a><br />
<a href="#software">Installing new software</a><br />
<a href="#wifi">Wifi in Haiku</a><br />
<a href="#api">Getting to know the API</a><br />
<a href="#contact">Getting in contact</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Víta vás Haiku!</a></h2>
<p>Ďakujeme vám, že ste vyskúšali Haiku! Toto je naše tretie verejné vydanie. Dúfame, že náš projekt zaujme nových vývojárov a dá budúcim používateľom šancu vyskúšať Haiku. Uvedomujeme si, že toto <i>alfa vydanie</i> zatiaľ celkom nedosahuje cieľov, ktoré sme si stanovili a neponúka všetky možnosti a bezproblémový používateľský zážitok, ktorý je plánovaný pre finálne vydanie R1. Dúfame však, že vám toto vydanie Haiku umožní objaviť veľký potenciál Haiku a že zdieľate naše nadšenie.</p>
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -93,25 +108,27 @@
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Wi-Fi v Haiku</a></h2>
<p>Wi-Fi do určitej miery funguje. Momentálne sa môžete pripojiť iba k nešifrovaným sieťam alebo sieťam šifrovaným pomocou WEP. Z dôvodu niekoľkých odlišných licenčných politík rôznych dodávateľov hardvéru, možno budete musieť firmvér nainštalovať ručne. Zoznam fungujúcich zariadení a inštalačné inštrukcie nájdete na našej stránke <a href="en/wifi.html">Wi-Fi</a> (tiež <a href="http://www.haiku-os.org/guides/wifi">online</a>).</p>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/sk/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Spoznávanie API</a></h2>
<p>Keďže Haiku je reimplementácia, API je stále rovnaké ako mal BeOS R5 (s istými rozšíreniami). Preto dokumentácia v Be Book j stále platný zdroj. Vďaka ACCESS, ktorý vlastní práva k bývalému majetku spoločnosti Be Inc., máme povolenie poskytovať kópiu Be Book.</p>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>Existujú aj ďalšie zdroje, ktoré vám pomôžu začať:</p>
<p>There are some resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Často kladené otázky - vývoj</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Prehliadač zdrojového kódu</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Archív newsletterov Be</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Kontaktujte nás</a></h2>
<p>Kontajtujte ostatných vývojárov a používateľov a pridajte sa do diskusií na IRC, v našich fórach alebo poštových konferenciách. Keď sa zhromaždí veľa rôznych ľudí, musia sa stanoviť pravidlá, aby komunikácia zostala efektívna. Prosím, rešpektujte <a href="http://www.haiku-os.org/community/ml/etiquette">Etiketu našej konferencie</a>.</p>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">Kanály IRC</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Fóra</a></li>
docs/welcome/welcome_sv_SE.html
+22 -5
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -49,10 +49,25 @@
<div id="content">
<div>
<div class="box-info">Översättningen av denna sida är inte komplett. Delar av innehållet kommer därför att visas på engelska.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Welcome to Haiku!</a><br />
<a href="#bugreport">Beware of Bugs</a><br />
<a href="#system">Getting to know the system</a><br />
<a href="#software">Installing new software</a><br />
<a href="#wifi">Wifi in Haiku</a><br />
<a href="#api">Getting to know the API</a><br />
<a href="#contact">Getting in contact</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Välkommen till Haiku!</a></h2>
<p>Tack så mycket för att du provar Haiku! Detta är vår tredje publika utgåva. Vi hoppas kunna locka till oss nya utvecklare till vårt projekt och ge framtida användare en chans att testa Haiku. Vi förstår att denna <i>alfa utgåva</i> ännu inte når upp till de mål som vi har satt upp för oss själva och erbjuder därmed inte all funktionalitet eller den slutgiltiga användarupplevelsen som är planerad för den färdiga R1 versionen. Hur som helst, vi hoppas att denna utgåva låter dig upptäcka Haiku's stora potential och att du kommer att dela vår förtjusning.</p>
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -93,25 +108,27 @@
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Wifi i Haiku</a></h2>
<p>Wifi fungerar tilli viss utsträckning. För tillfället kan du endast ansluta till okrypterade eller WEP-krypterade trådlösa nätverk. På grund av flera olika licens-policys från olika tillverkare kan en manuell installationsprocess för några mikroprogramvaror krävas. En lista över fungerande kort och instruktioner för hur dessa installeras finns på vår <a href="sv_SE/wifi.html">Wifi</a> sida (finns även <a href="http://www.haiku-os.org/guides/wifi">online</a>).</p>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/sv_SE/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">Lär känna Haiku's API</a></h2>
<p>Eftersom Haiku är en omimplementation så är dess API detsamma som för BeOS R5 (med några tillägg). Av den anledningen är dokumentationen i the Be Book fortfarande giltig. Tack vare ACCESS, som äger rättigheterna till tidigare Be Inc.'s egendomar, har vi fått tillåtelse att tillhandahålla en kopia av boken.</p>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>Det finns några extra resurser som kan hjälpa dig att komma igång:</p>
<p>There are some resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">Utvecklings FAQ</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Källkodsläsare</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl">The Be Book</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be's nyhetsbrevsarkiv</a></li>
</ul>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="contact" name="contact">Kom i kontakt med oss</a></h2>
<p>Kom i kontakt med andra utvecklare och användare och delta i diskussionerna på IRC, i våra forum eller på e-postlistorna. När många olika människor samlas krävs regler för att hålla kommunikationen effektiv. Vänligen respektera vår <a href="http://www.haiku-os.org/community/ml/etiquette">etikett för e-postlistor</a>.</p>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC kanaler</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Forum</a></li>
docs/welcome/welcome_uk.html
+22 -5
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -49,10 +49,25 @@
<div id="content">
<div>
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>Index</td></tr>
<tr class="index"><td>
<a href="#welcome">Welcome to Haiku!</a><br />
<a href="#bugreport">Beware of Bugs</a><br />
<a href="#system">Getting to know the system</a><br />
<a href="#software">Installing new software</a><br />
<a href="#wifi">Wifi in Haiku</a><br />
<a href="#api">Getting to know the API</a><br />
<a href="#contact">Getting in contact</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">Вітаємо в Haiku!</a></h2>
<p>Дякуємо за інтерес, який Ви проявляєте до Haiku! Це наш третій публічний реліз, ми маємо надію привернути увагу нових розробників і дати можливість майбутнім користувачам побачити Haiku в дії. Зрозуміло, що цей <i>альфа реліз</i> далеко не повністю відповідає цілям, які поставлені і не надає всіх функцій, які ми збирались надати кінцевому користувачеві, запланувавши їх для фінальної версії R1. Однак, ми маємо надію, що він дозволить Вам помітити значний потенціал Haiku і Ви знайдете хвильку для її вивчення.</p>
<p>Visit our project's website <a hrf="http://www.haiku-os.org">Haiku-os.org</a> for the latest news and announcements.</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -94,25 +109,27 @@
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Wifi в Haiku</a></h2>
<p>Wifi зараз підтримується частково. У даний момент можливе підключення до незахищених мереж або до таких, що захищені WEP шифруванням . Через різну ліцензійну політику виробників, доведеться вручну встановлювати мікропрограму (firmware) . Список приладів, що підтримуються можна знайти на нашій сторінці <a href="uk/wifi.html">Wifi</a> (також <a href="http://www.haiku-os.org/guides/wifi">наживо</a>).</p>
<p>Haiku supports wireless networks that are WPA/WPA2 or WEP encrypted and of course open, unencrypted connections. Due to several different licensing policies of different hardware vendors, a manual installation process for the firmware may be required. You'll find more information on supported hardware, firmware installation and how to join a wireless network in the Haiku User Guide's <a href="../userguide/uk/workshop-wlan.html">Workshop: Wireless networking</a>.</p>
<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 є відтворенням, API її таке ж як у BeOS R5 (з деякими виключеннями), Тому документація у Be Book все ще актуальна. Завдяки компанії ACCESS, котрій належать права на інтелектуальну власність Be Inc., нам дозволено поширювати Be Book.</p>
<p>Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the Be Book is still a valid resource. Thanks to ACCESS, who owns the rights to former Be Inc. property, we are allowed to provide a copy of the Be Book.<br />
Deviations from the BeOS API and Haiku specific additions are collected in the Haiku Book.</p>
<p>Існують інші ресурси, що допоможуть почати вивчення:</p>
<p>There are some resources that should help you getting started:</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">FAQ для розробників</a></li>
<li><a href="http://dev.haiku-os.org/browser/" class="printurl">Source Браузер вихідного коду</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/bebook/" class="printurl"> Be Book</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">The Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Архів Be Newsletter</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/community/ml/etiquette">Етикет списків розсилки</a>.</p>
<p>Get in contact with other developers and users and join the discussions on IRC (<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a> on webchat), in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our <a href="http://www.haiku-os.org/community/ml/etiquette">Mailing List Etiquette</a>.</p>
<ul>
<li><a href="http://www.haiku-os.org/community/irc" class="printurl">IRC канали</a></li>
<li><a href="http://www.haiku-os.org/forum" class="printurl">Форуми</a></li>
docs/welcome/welcome_zh_CN.html
+21 -6
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -50,9 +50,23 @@
<div id="content">
<div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>索引</td></tr>
<tr class="index"><td>
<a href="#welcome">欢迎使用 Haiku！</a><br />
<a href="#bugreport">警惕程序错误</a><br />
<a href="#system">了解 Haiku 系统</a><br />
<a href="#software">安装新软件</a><br />
<a href="#wifi">Haiku 无线网络</a><br />
<a href="#api">了解 Haiku 的API</a><br />
<a href="#contact">联系我们</a>
</td></tr>
</table>
<h2>
<a id="welcome" name="welcome">欢迎使用Haiku！</a></h2>
<p>非常感谢您对Haiku的试用和测试！这是我们公开发布的第三个版本，我们希望能够吸引更多的开发者参与我们的项目，也希望能够为将来的用户提供测试 Haiku 的机会。我们也注意到本<i>试用版本</i> 还远远没有达到既定的目标，没有提供为最终的 R1 版本计划的所有特性和全面用户体验。然而，我们希望这一版本可以让您发现 Haiku 的巨大潜力，让您分享我们的喜悦。</p>
<p>最新新闻和公告请访问我们的网站 <a hrf="http://www.haiku-os.org">Haiku-os.org</a> 。</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
@@ -93,26 +107,27 @@
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="software" name="wifi">Haiku的无线网络</a></h2>
<p>在某种程度上，无线网络可以工作。现在您只能连接到未加密的或者WEP加密的无线网络。由于不同提供商的各种不同的授权政策，对于一些固件，可能需要手动的安装。您可以在我们的<a href="zh_CN/wifi.html">无线网络</a>页面上找到可用硬件和相关的安装说明（当然，还有<a href="http://www.haiku-os.org/guides/wifi">在线</a>文档）。</p>
<a id="software" name="wifi">Haiku 无线网络</a></h2>
<p>Haiku目前支持WPA/WPA2 和 WEP 加密的无线网络，当然也包括开放的和未加密的网络。由于不同提供商的各种不同的授权政策，对于一些固件，可能需要手动的安装。您可以在我们 Haiku 用户指南的<a href="../userguide/zh_CN/workshop-wlan.html">操作练习：无线网络</a>页面上找到更多有关硬件支持，固件安装以及如何进行无线网络连接的详细信息。</p>
<h2>
<a href="#"><img src="images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="api" name="api">了解Haiku的API</a></h2>
<p>由于 Haiku 是 BeOS 系统的重新实现，它的 API 仍然和 BeOS R5 的相同（增添了一些特性）。所以 Be Book 中的文档仍然是非常有用的资源。非常感谢前 BeOS 公司财产的拥有者 - ACCESS，我们才可以提供 Be Book 的副本供大家参考。</p>
<p>由于 Haiku 是 BeOS 系统的重新实现，它的 API 仍然和 BeOS R5 的相同（增添了一些特性）。所以 Be Book 中的文档仍然是非常有用的资源。非常感谢前 BeOS 公司财产的拥有者 - ACCESS，我们才可以提供 Be Book 的副本供大家参考。BeOS API与Haiku之间的不同之处可以参考 Haiku Book。</p>
<p>下面的资源对您的入门会有很多帮助：</p>
<ul>
<li><a href="http://www.haiku-os.org/development/faq" class="printurl">开发FAQ</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">Be Book</a></li>
<li><a href="http://api.haiku-os.org" class="printurl">Haiku Book</a></li>
<li><a href="http://www.haiku-os.org/legacy-docs/benewsletter/" class="printurl">Be 通讯存档</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/community/ml/etiquette">邮件列表规范</a>。</p>
<a id="contact" name="contact">联系我们</a></h2>
<p>通过参加IRC（<a href="http://webchat.freenode.net/?channels=haiku">#haiku</a>聊天室），论坛，邮件列表中的讨论来同其他的开发者和用户保持联系。由于许多不同人员的参与，我们需要制定一些规则使交流变得方便有效。请遵守我们的<a href="http://www.haiku-os.org/community/ml/etiquette">邮件列表规范</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>
docs/welcome/zh_CN/bugreports.html
+3 -2
View File
@@ -4,7 +4,7 @@
<head>
<!--
*
* Copyright 2008-2010, Haiku. All rights reserved.
* Copyright 2008-2012, Haiku. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
@@ -53,7 +53,7 @@
<div>
<table class="index" id="index" summary="index">
<tr class="heading"><td>报告错误</td></tr>
<tr class="heading"><td>索引</td></tr>
<tr class="index"><td><a href="#account">获取Trac账户</a><br />
<a href="#report">创建错误报告</a><br />
<a href="#app">软件错误</a><br />
@@ -126,6 +126,7 @@
</table>
<p>获取更多信息，请参阅 <a href="http://www.haiku-os.org/documents/dev/welcome_to_kernel_debugging_land">欢迎使用内核调试工具</a>。</p>
<p>KDL输出信息将会写入到串行端口（如果您拥有另一台与之相连接的计算机，您可以通过中断程序重定向输出信息）和系统日志。如果您无法离开KDL，它将无法写入系统日志文件。尽管如此，还有一个系统引导调试选项，允许您捕获系统信息（参阅下文）。</p>
<p>您可以从KDL输出中生成 QR 代码，而它们可以通过智能手机或相似设备转换为文本内容。有关如何使用该功能从 KDL 获取数据，详情参考 <a href="http://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output">QR Encode your KDL Output</a> 。</p>
<h3><a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
<a id="syslog" name="syslog">系统日志</a></h3>