From 36361905760cce6362bf398d238497aecb412e5a Mon Sep 17 00:00:00 2001 From: Joachim Seemer Date: Tue, 4 May 2010 18:32:21 +0000 Subject: [PATCH] Latest Welcome package changes for luroh's proof reading :) git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36615 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- docs/welcome/de/bugreports.html | 6 +- docs/welcome/de/wifi.html | 134 ++++++++++++++++++++++++++ docs/welcome/en/bugreports.html | 4 +- docs/welcome/en/wifi.html | 140 ++++++++++++++++++++++++++++ docs/welcome/es/bugreports.html | 74 +++++++-------- docs/welcome/es/wifi.html | 140 ++++++++++++++++++++++++++++ docs/welcome/fr/bugreports.html | 71 +++++++------- docs/welcome/fr/wifi.html | 140 ++++++++++++++++++++++++++++ docs/welcome/images/flags/it.png | Bin 291 -> 0 bytes docs/welcome/images/flags/jp.png | Bin 390 -> 0 bytes docs/welcome/images/flags/sv_SE.png | Bin 285 -> 0 bytes docs/welcome/images/flags/uk.png | Bin 625 -> 256 bytes docs/welcome/it/bugreports.html | 104 --------------------- docs/welcome/jp/bugreports.html | 104 --------------------- docs/welcome/ru/bugreports.html | 8 +- docs/welcome/ru/wifi.html | 140 ++++++++++++++++++++++++++++ docs/welcome/sv_SE/bugreports.html | 104 --------------------- docs/welcome/uk/bugreports.html | 3 - docs/welcome/uk/wifi.html | 140 ++++++++++++++++++++++++++++ docs/welcome/welcome_de.html | 27 +++--- docs/welcome/welcome_en.html | 35 ++++--- docs/welcome/welcome_es.html | 40 ++++---- docs/welcome/welcome_fr.html | 40 ++++---- docs/welcome/welcome_it.html | 127 ------------------------- docs/welcome/welcome_jp.html | 129 ------------------------- docs/welcome/welcome_ru.html | 37 ++++---- docs/welcome/welcome_sv_SE.html | 127 ------------------------- docs/welcome/welcome_uk.html | 35 ++++--- 28 files changed, 1018 insertions(+), 891 deletions(-) create mode 100644 docs/welcome/de/wifi.html create mode 100644 docs/welcome/en/wifi.html create mode 100644 docs/welcome/es/wifi.html create mode 100644 docs/welcome/fr/wifi.html delete mode 100644 docs/welcome/images/flags/it.png delete mode 100644 docs/welcome/images/flags/jp.png delete mode 100644 docs/welcome/images/flags/sv_SE.png delete mode 100644 docs/welcome/it/bugreports.html delete mode 100644 docs/welcome/jp/bugreports.html create mode 100644 docs/welcome/ru/wifi.html delete mode 100644 docs/welcome/sv_SE/bugreports.html create mode 100644 docs/welcome/uk/wifi.html delete mode 100644 docs/welcome/welcome_it.html delete mode 100644 docs/welcome/welcome_jp.html delete mode 100644 docs/welcome/welcome_sv_SE.html diff --git a/docs/welcome/de/bugreports.html b/docs/welcome/de/bugreports.html index 51d73125d7..8718fab9c1 100644 --- a/docs/welcome/de/bugreports.html +++ b/docs/welcome/de/bugreports.html @@ -22,7 +22,7 @@
@@ -30,11 +30,9 @@ diff --git a/docs/welcome/de/wifi.html b/docs/welcome/de/wifi.html new file mode 100644 index 0000000000..676e30dfbd --- /dev/null +++ b/docs/welcome/de/wifi.html @@ -0,0 +1,134 @@ + + + + + + + + + WLAN + + + + + + +
+
+ + + + Welcome +
+
+ +
+
+ +

WLAN in Haiku

+

index +Wahrscheinlich unterstützte Hardware

+

Alle FreeBSD 8 WLAN Treiber sollten funktionieren. Jedoch keine PCMCIA, CardBus, ExpressCard, USB oder ISA basierte Karten. Unterstützt wird nur PCI, miniPCI, PCI-Express, miniPci-Express und PCI-X.
+Darunter:

+
    +

  • aironetwifi unterstützt zumindest
    +Cisco Aironet 350 Serie
    +Aironet PCI4500
    +Aironet PCI4800
    +

    • +

  • atheroswifi unterstützt fast alle Chipsets (allerdings keine AR9285 Chips)

    • +

  • broadcom43xx unterstützt
    +BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 und BCM4318

    +
    • +

  • iprowifi2100 unterstützt 2100 Chips

    • +

  • iprowifi2200 unterstützt
    +2200BG
    +2225BG
    +2915ABG

    +
    • +

  • iprowifi3945 unterstützt 3945 Chips

    • +

  • iprowifi4965 unterstützt 4965 Chips

    • +

  • marvell88w8335 unterstützt
    +Marvell Libertas 88W8310
    +Marvell Libertas 88W8335

    • +

  • marvell88w8363 unterstützt 88W8363 Chips

    • +

  • ralinkwifi unterstützt
    +RT2560
    +RT2561S
    +RT2561
    +RT2661

    +
    • +

  • wavelanwifi unterstützt zumindest
    +3Com Airconnect
    +GLPRISM2 WaveLAN
    +Intersil Prism3
    +Intersil Prism2.5
    +Linksys WDT11
    +Netgear MA301
    +PRISM2STA WaveLAN
    +Siemens SpeedStream
    +SMC 2602W
    +Us Robotics 2415
    +Addtron AWA-100 PCI

    • +
+

index +WEP Verschlüsselung

+

WEP Verschlüsselung ist durch das Kommandozeilen-Programm setwep verfügbar. Es ist ein Provisorium, um sich in ein nicht oder per WEP verschlüsseltes Netzwerk einzuklinken. setwep funktioniert mit 64- und 128-bit WEP und unterstützt Passwörter als Text und Hex-Werte (siehe WEP Info weiter unten).

+

Der Gebrauch ist: setwep Geräte_Pfad [ssid] [key]. Nachfolgend einige Beispiele.

+

In diesen Beispielen gehen wir von einer Netzwerkkarte "/dev/net/iprowifi3945/0" und einem Funknetzwerk mit dem Namen "haikuwifi" aus.

+

Beispiel 1: Verbindung mit einer 64-bit WEP Verschlüsselung und einem Hex-Passwort

+
setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
+

Beispiel 2: Verbindung mit einem unverschlüsselten Funknetzwerk

+
setwep /dev/net/iprowifi3945/0 haikuwifi
+
+
  • Den Pfad zu seinem Gerät findet man unter Preferences -> Network.
    • +
  • Um sich bei jedem Hochfahren mit dem Netzwerk unter dieser SSID zu verbinden, schreibt man den setwep Befehl ins home/config/boot/UserBootscript.
    • +
    +

    WEP Info

    +
      +
    • 64-bit WEP benutzt ein 40-bit Passwort, das sind 5 Buchstaben oder 10 Hex-Werte
      • +
    • 128-bit WEP benutzt ein 104-bit Passwort, das sind 13 Buchstaben oder 26 Hex-Werte
      • +
    • Hex-Werte sind die Zahlen 0-9 und Buchstaben A bis F (mit einem vorangestellten '0x')
      • +
    +

    index +WPA Verschlüsselung

    +

    Momentan gibt es noch keine WPA Verschlüsselung unter Haiku. Es existiert allerdings vorläufiger und unvollständiger Code für eine WPA Implementierung. Um weiter zu kommen, müsste er in den wpa_supplicant Build-Prozess integriert und Kompilier- und Laufzeitfehler behoben werden.

    +

    index +install-wifi-firmwares.sh

    +

    Um die Firmware für Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335 zu installieren, started man

    +
    ~> install-wifi-firmwares.sh
+
    +

    Die Intel ipw2100/2200 benötigen zur Installation keine Internetverbindung, da es die Lizenzbestimmungen erlauben die Original-Firmware gleich mitzuliefern. Sie verlangen jedoch eine Zustimmung des Benutzer vor ihrer Installtion. Für Broadcom 43xx & Marvell 88W8335 ist hingegen eine funktionierende Internetverbindung nötig, da die entsprechenden Dateien mit der Firmware Haiku nicht beiliegen dürfen.

    +

    Leute, die ihr eigenes Haiku Image bauen, können ihre build/jam/UserBuildConfig entsprechend anpassen. Details dazu und eventuelle Updates zum WLAN-Thema finden sich in der Online-Version dieses Dokuments (Englisch).

    +

    Wer die Firmware runterladen muss, aber unter Haiku keine Internetverbindung hat, kann das in diesem Online Dokument angebotene Shell Skript benutzen. Damit werden alle nötigen Dateien heruntergeladen und in ein Zip gepackt, das man unter Haiku in /boot entpacken kann. Dann stehen alle Dateien zur Verfügung, die von install-wifi-firmwares.sh benötigt werden.

    +
    +
    + +
    +
    + Welcome +
    +
    + + + diff --git a/docs/welcome/en/bugreports.html b/docs/welcome/en/bugreports.html index 518d56b204..3e40a1cf4c 100644 --- a/docs/welcome/en/bugreports.html +++ b/docs/welcome/en/bugreports.html @@ -29,11 +29,9 @@
  • English
  • Français
  • Deutsch
    • -
  • Italiano
  • Русский
  • Español
    • -
  • Svensk
    • -
  • 日本語
    • +
  • Українська
    • Welcome diff --git a/docs/welcome/en/wifi.html b/docs/welcome/en/wifi.html new file mode 100644 index 0000000000..0004bf8ecd --- /dev/null +++ b/docs/welcome/en/wifi.html @@ -0,0 +1,140 @@ + + + + + + + + + Wifi + + + + + + +
    +
    + + + + Welcome +
    +
    + +
    +
    + +

    Wifi in Haiku

    +

    +index +Expected supported hardware

    +

    All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.
    +This includes: +

    +
      +

    • aironetwifi supporting at least
      +Cisco Aironet 350 Series
      +Aironet PCI4500
      +Aironet PCI4800
      +

      • +

    • atheroswifi supporting almost every chipset outthere (though no AR9285 chips)

      • +

    • broadcom43xx supporting
      +BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318 +

      • +

    • iprowifi2100 supporting the 2100 chips

      • +

    • iprowifi2200 supporting
      +2200BG
      +2225BG
      +2915ABG +

      • +

    • iprowifi3945 supporting the 3945 chips

      • +

    • iprowifi4965 supporting the 4965 chips

      • +

    • marvell88w8335 supporting
      +Marvell Libertas 88W8310
      +Marvell Libertas 88W8335 +

      • +

    • marvell88w8363 supporting the 88W8363 chips

      • +

    • ralinkwifi supporting
      +RT2560
      +RT2561S
      +RT2561
      +RT2661 +

      • +

    • wavelanwifi supporting at least
      +3Com Airconnect
      +GLPRISM2 WaveLAN
      +Intersil Prism3
      +Intersil Prism2.5
      +Linksys WDT11
      +Netgear MA301
      +PRISM2STA WaveLAN
      +Siemens SpeedStream
      +SMC 2602W
      +Us Robotics 2415
      +Addtron AWA-100 PCI +

      • +
    +

    +index +WEP encryption

    +

    WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below) +

    +

    The usage is: setwep device_path [ssid] [key]. Below are some examples.

    +

    In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".

    +

    Example 1: Connect with 64-bit WEP encryption using a hex digit key

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
+

    Example 2: Connect to an unencrypted wireless network

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi
+
    +
  • To find out what your device_path is, have a look in Preferences -> Network.
    • +
  • To make your wifi device connect to a given SSID at each boot, add the setwep command to your home/config/boot/UserBootscript.
    • +
    +

    WEP notes

    +
      +
    • 64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits
      • +
    • 128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits
      • +
    • hexadecimal digits = characters 0-9 and A through F (prepended with '0x')
      • +
    +

    +index +WPA encryption

    +

    At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.

    +

    +index +install-wifi-firmwares.sh

    +

    To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run

    +
    ~> install-wifi-firmwares.sh
+
    +

    The Intel ipw2100 and ipw22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.

    +

    People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.

    +

    If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.

    +
    +
    + +
    +
    + Welcome +
    +
    + + + diff --git a/docs/welcome/es/bugreports.html b/docs/welcome/es/bugreports.html index c7ad2d2825..7ab4b27ba7 100644 --- a/docs/welcome/es/bugreports.html +++ b/docs/welcome/es/bugreports.html @@ -10,11 +10,13 @@ * Authors: * Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki * Humdinger + * Translators: + * miguel~1.mx * --> - Reporting bugs + Reportar fallos @@ -29,10 +31,8 @@
  • Español
  • Français
  • Deutsch
    • -
  • Italiano
  • Русский
    • -
  • Svensk
    • -
  • 日本語
    • +
  • Українська
  • English
    • @@ -43,53 +43,51 @@
    -

    Reporting bugs

    +

    Reportar fallos

    -

    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.

    -

    To keep our bugtracker effective, it's essential to abide by the Bug Tracker Etiquette.

    +

    Ya que nuestros desarrolladores no pueden verificar todas las combinaciones de hardware, ni todas las posibles maneras de interactuar con el sistema operativo, confiamos que los usuarios nos den retroalimentación sobre cómo funcionan las cosas de su lado. Dado que Haiku todavía es muy joven, muy probablemente encontrará fallos. Le agradecemos por tomarse el tiempo para reportarlos. Juntos podemos mejorar a Haiku, bit a bit.

    +

    Para mantener nuestro rastreador de fallos efectivo, es esencial supeditarse a la Etiqueta del rastreador de fallos.

    -

    Getting a Trac account

    -

    To file a ticket, you need to have an account at Haiku's Bugtracker.
    -When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the all important verification mail often ends up there.

    +

    Obtener una cuenta de Trac

    +

    Para llenar un reporte, necesita tener una cuenta en el Rastreador de fallos de Haiku.
    +Cuando se cree una cuenta nueva, asegurese de proporcionar su correo electrónico pues es necesario obtener privilegios de modificación básica del reporte. Asegúrese de comprobar su carpeta de correo no deseado (spam) brevemente después, ya que a menudo toda verificación de correo importante termina allí.

    -

    Creating a bug report

    -

    Before reporting a bug, please make sure that it does not yet exist. You can also use the search function for this.
    -After you have established that it's a unique bug, make your information as accurate as possible:

    +

    Crear un reporte de fallo

    +

    Antes de reportar un fallo, por favor asegúrese que aún no exista. Puede también usar la función de búsqueda para esto.
    +Tras haber establecido que es un fallo nuevo, haga su información tan puntual como sea posible:

      -

    • Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).

      • -

    • Mention which revision from SVN you are running. You can find this information in 'About This System...' from the Deskbar menu.

      • -

    • Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.

      • -

    • Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.

      • -

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the PRINT key saves a PNG in /boot/home/).

      • +

    • Incluya información básica tal como dónde está probando a Haiku (sobre hardware real, en VMWare, en QEMU, etc.).

      • +

    • Mencione cuál revisión de SVN esté corriendo. Puede encontrar esta información en 'About This System...' (Acerca de este sistema) desde el menú Deskbar.

      • +

    • Describa el problema que esté experimentando. Intente ser tan preciso como pueda: describa el comportamiento actual, y el comportamiento esperado.

      • +

    • Describa qué pasos necesita realizar para exponer el fallo. Esto ayudará a los desarrolladores a reproducir el fallo.

      • +

    • Adjunte tanta información como tenga. Si es un fallo de interfaz de usuario, o un fallo en una de las aplicaciones, intente hacer una captura de pantalla (la tecla Impr pant guarda un PNG en /boot/home/).

    -

    Software Bugs

    -

    When an application crashed, you should invoke the debugger from the alert that pops up. Entering bt into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.

    +

    Fallos de software

    +

    Cuando falla una aplicación, debería invocar el depurador desde la alerta que aparece. Al ingresar bt dentro de la terminal de depuración ejecutada, se crea un "backtrace" que debiera copiarse dentro del reporte de fallo.

    -

    Hardware Bugs

    -

    When dealing with a hardware/driver related bug, you should attach the following information:

    +

    Fallos de hardware

    +

    Cuando se enfrente a fallos relacionados con hardware/controladores, debería adjuntarse la siguiente información:

      -
    • listdev - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' lshw and lspci.
      • -
    • listusb -v - assuming its a USB related issue, similar to lsusb.
      • -
    • open /var/log/syslog - the primary system log used by Haiku, akin to on screen debugging during boot. With the open command you can crop down the relevant part of the syslog in a text editor.
      • -
    • listimage | grep drivers/ - lists all used drivers.
      • -
    • ints - only available within Kernel Debugging Land (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
      • +
    • listdev - un listado detallado de su hardware, incluyendo las IDs de fabricante y dispositivo PCI, similar a los comandos lshw y lspci de Linux.
      • +
    • listusb -v - asumiendo que el conflicto se relacione con USB, de manera similar a lsusb.
      • +
    • open /var/log/syslog - el historial de sucesos de sitema primario utilizado por Haiku, análogamente a la pantalla de depuración durante el arranque. Con el comando open se puede acortar la parte relevante de los sucesos de sistema en un editor de textos.
      • +
    • listimage | grep drivers/ - lista todos los controladores utilizados.
      • +
    • ints - sólo disponible en la Tierra de depuración del núcleo (ve debajo). Muestra el uso de interrupciones. No debería haber demasiados que se compartan por dispositivos diferentes.
    -

    You enter these commands into Terminal. Add a > output.txt after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.

    +

    Se pueden ingresar estos comandos en la Terminal. Agregue un > output.txt tras un comando, y se hará una operación de tubería dentro de un texto llamado "output.txt" que se puede adjuntar al reporte de fallos o correo electrónico.

    -

    Kernel Debugging Land - KDL

    -

    When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with ALTSysReqD (SysReq being PRINT on most keyboards).

    +

    Tierra de depuración del núcleo - KDL

    +

    Cuando algún componente de sistema de muy bajo nivel deja de funcionar, se puede terminar en el depurador de núcleo (KDL por sus siglas en inglés, Kernel Debugging Land). También puede ingresarse deliberadamente con ALT PetSis D (siendo PetSis el mismo botón que Impr pant en la mayoría de los teclados).

      -
    • co - will exit KDL and continue normal system operation, if possible.
      • -
    • int - will show interrupt usage (as described above).
      • -
    • bt - shows a backtrace, detailing where exactly the crash happened.
      • +
    • co - saldrá de KDL y continuará la operación del sistema, si es posible.
      • +
    • int - mostrará el uso de interrupciones (como se describió arriba).
      • +
    • bt - muestra el "backtrace", detallando dónde exactamente sucedió el fallo.
    -

    What's next?

    -

    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.

    -

    Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked -as 'fixed'.

    +

    ¿Qué sigue?

    +

    Después que un fallo se ha reportado, un desarrollador verá el reporte e intentará clasificarlo. Recuerde, todos somos voluntarios, y por ello, algunas veces un fallo pudiera estar sin responderse por un tiempo. Agregar nueva información cuando esté disponible usualmente ayuda a que se escoja un fallo más rápidamente, pero no intente 'levantar' el fallo agregando comentarios no descriptivos.

    +

    Recuerde, reportar un fallo no es algo en lo que tome un poquito de tiempo y sea todo. Si se reporta un fallo, se vuelve parte del proceso de desarrollo de Haiku. Los desarrolladores podrían llegar con preguntas mientras intentan arreglar el fallo reportado. Por favor, permanezca atento para responderlas. Considere su participación 'terminada' cuando el fallo se marque como 'arreglado'.

    diff --git a/docs/welcome/es/wifi.html b/docs/welcome/es/wifi.html new file mode 100644 index 0000000000..2ecca3424f --- /dev/null +++ b/docs/welcome/es/wifi.html @@ -0,0 +1,140 @@ + + + + + + + + + Wifi + + + + + + +
    +
    + + + + Welcome +
    +
    + +
    +
    + +

    Wifi in Haiku

    +

    +index +Expected supported hardware

    +

    All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.
    +This includes: +

    +
      +

    • aironetwifi supporting at least
      +Cisco Aironet 350 Series
      +Aironet PCI4500
      +Aironet PCI4800
      +

      • +

    • atheroswifi supporting almost every chipset outthere (though no AR9285 chips)

      • +

    • broadcom43xx supporting
      +BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318 +

      • +

    • iprowifi2100 supporting the 2100 chips

      • +

    • iprowifi2200 supporting
      +2200BG
      +2225BG
      +2915ABG +

      • +

    • iprowifi3945 supporting the 3945 chips

      • +

    • iprowifi4965 supporting the 4965 chips

      • +

    • marvell88w8335 supporting
      +Marvell Libertas 88W8310
      +Marvell Libertas 88W8335 +

      • +

    • marvell88w8363 supporting the 88W8363 chips

      • +

    • ralinkwifi supporting
      +RT2560
      +RT2561S
      +RT2561
      +RT2661 +

      • +

    • wavelanwifi supporting at least
      +3Com Airconnect
      +GLPRISM2 WaveLAN
      +Intersil Prism3
      +Intersil Prism2.5
      +Linksys WDT11
      +Netgear MA301
      +PRISM2STA WaveLAN
      +Siemens SpeedStream
      +SMC 2602W
      +Us Robotics 2415
      +Addtron AWA-100 PCI +

      • +
    +

    +index +WEP encryption

    +

    WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below) +

    +

    The usage is: setwep device_path [ssid] [key]. Below are some examples.

    +

    In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".

    +

    Example 1: Connect with 64-bit WEP encryption using a hex digit key

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
+

    Example 2: Connect to an unencrypted wireless network

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi
+
    +
  • To find out what your device_path is, have a look in Preferences -> Network.
    • +
  • To make your wifi device connect to a given SSID at each boot, add the setwep command to your home/config/boot/UserBootscript.
    • +
    +

    WEP notes

    +
      +
    • 64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits
      • +
    • 128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits
      • +
    • hexadecimal digits = characters 0-9 and A through F (prepended with '0x')
      • +
    +

    +index +WPA encryption

    +

    At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.

    +

    +index +install-wifi-firmwares.sh

    +

    To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run

    +
    ~> install-wifi-firmwares.sh
+
    +

    The Intel ipw2100 and ipw22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.

    +

    People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.

    +

    If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.

    +
    +
    + +
    +
    + Welcome +
    +
    + + + diff --git a/docs/welcome/fr/bugreports.html b/docs/welcome/fr/bugreports.html index 941290bae5..bc055767b4 100644 --- a/docs/welcome/fr/bugreports.html +++ b/docs/welcome/fr/bugreports.html @@ -12,6 +12,7 @@ * Humdinger * Translators: * Loïc + * Vincent Duvert * --> @@ -22,7 +23,7 @@
    @@ -30,11 +31,9 @@ @@ -47,51 +46,51 @@

    Signaler les bogues

    -

    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.

    -

    To keep our bugtracker effective, it's essential to abide by the Bug Tracker Etiquette.

    +

    Comme il est impossible pour nos développeurs de tester toutes les combinaisons de matériel, ni tous les cas de figure pouvant interagir avec le système d'exploitation, nous comptons sur les utilisateurs pour nous dire si les choses fonctionnent pour eux. puisque Haiku est encore tout jeune, il est très probable que vous rencontriez des bogues. Nous vous remercions de bien vouloir prendre le temps de nous les signaler. Ensemble, nous pourrons, petit à petit, améliorer Haiku.

    +

    Afin que le suivi de nos bogues reste efficace, il est essentiel de respecter l'Étiquette de suivi des bogues.

    -

    Getting a Trac account

    -

    To file a ticket, you need to have an account at Haiku's Bugtracker.
    -When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the all important verification mail often ends up there.

    +

    Obtenir un compte Trac

    +

    Pour remplir un rapport (ticket), vous aurez besoin d’un compte utilisateur sur le Traqueur de bogues de Haiku.
    +Lors de la création d’un nouveau compte, pensez à indiquer votre adresse e-mail afin d’obtenir les privilèges basiques de gestions des tickets. N’oubliez pas de Vérifier votre dossier de pourriel après, car les e-mails de vérifications s’y retrouvent souvent.

    Créer un rapport de bogue

    -

    Before reporting a bug, please make sure that it does not yet exist. You can also use the search function for this.
    -After you have established that it's a unique bug, make your information as accurate as possible:

    +

    Avant de rapporter un bogue, veuillez vérifierqu’il n’est pas déjà répertorié. Vous pouvez aussi utiliser la fonction de recherche pour cela.
    +Après vous être assurer que votre bogue est unique, obtenez des informations précises sur votre environnement :

      -

    • Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).

      • -

    • Mention which revision from SVN you are running. You can find this information in 'About This System...' from the Deskbar menu.

      • -

    • Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.

      • -

    • Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.

      • -

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the PRINT key saves a PNG in /boot/home/).

      • +

    • Indiquez comment vous testez Haiku (sur machine réelle, dans VMware, dans Qemu…)

      • +

    • Indiquez quelle révision SVN de Haiku vous utilisez. Vous pouvez trouver des informations à ce sujet dans le menu « About This System… » de la Deskbar.

      • +

    • Décrire le problème que vous rencontrez. Essayez d'être aussi précis que possible : décrivez le comportement réel, et celui que vous attendiez.

      • +

    • Décrivez les actions que vous avez effectuées avant de faire ressortir le bogue. Cela permettra aux développeurs de le reproduire.

      • +

    • Attachez au rapport le plus d’informations possibles. Si le bogue concerne l’interface graphique ou une application, essayez de faire une capture d’écran (la touche IMPR ÉCRAN créera une image PNG dans le dossier /boot/home/).

    -

    Software Bugs

    -

    When an application crashed, you should invoke the debugger from the alert that pops up. Entering bt into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.

    +

    Bogues logiciels

    +

    Lorsqu'une application se plante, vous devez appeler le débogueur depuis le message d'alerte qui s'affiche. Saisissez bt dans le Terminal de débogage qui est lancé. Vous obtiendrez ainsi une trace de la « pile d'appel » (backtrace) que vous devez joindre à votre rapport de bogue.

    -

    Hardware Bugs

    -

    When dealing with a hardware/driver related bug, you should attach the following information:

    +

    Bogues matériels

    +

    Lorsque le bogue concerne un matériel ou son pilote, vous devez fournir les renseignements suivants :

      -
    • listdev - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' lshw and lspci.
      • -
    • listusb -v - assuming its a USB related issue, similar to lsusb.
      • -
    • open /var/log/syslog - the primary system log used by Haiku, akin to on screen debugging during boot. With the open command you can crop down the relevant part of the syslog in a text editor.
      • -
    • listimage | grep drivers/ - lists all used drivers.
      • -
    • ints - only available within Kernel Debugging Land (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
      • +
    • listdev - fait une liste détaillée de votre matériel, en y incluant les identifiants PCI des fournisseurs, à la manière de lshw ou lspci dans GNU/Linux .
      • +
    • listusb -v - en supposant que c'est un problème lié à l'USB, comme le fait lsusb.
      • +
    • open /var/log/syslog - +le système de journal d’événements principal de Haiku, similaire au déboguage sur écran durant le démarrage. En l’ouvrant dabs un éditeur de texte avec la commande open vous pourrez n’en conserver que la partie utile.
      • +
    • listimage | grep drivers/ - liste tous les drivers utilisés.
      • +
    • ints - seulement disponible dans le mode débogage du noyau (voir ci-dessous). Montre l'utilisation des interruptions. +Il ne devrait pas y avoir trop d'interruptions partagées par plusieurs périphériques.
    -

    You enter these commands into Terminal. Add a > output.txt after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.

    +

    Ces commandes peuvent être entrées dans le Terminal. Si vous ajoutez > sortie.txt après une commande, sa sortie sera redirigée dans un fichier texte nommé « sortie.txt » que vous pourrez attachez à votre rapport de bogue ou e-mail.

    -

    Kernel Debugging Land - KDL

    -

    When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with ALTSysReqD (SysReq being PRINT on most keyboards).

    +

    Le mode débogage noyau - KDL

    +

    Lorsque certains composants systèmes de bas niveau se plantent, vous pouvez être envoyé dans le débogueur du noyau. Vous pouvez également y entrer volontairement avec ALTSYSTD (SYST correspond à IMPR ÉCRAN sur la plupart des claviers). Attention : l'ordre des touches compte.

      -
    • co - will exit KDL and continue normal system operation, if possible.
      • -
    • int - will show interrupt usage (as described above).
      • -
    • bt - shows a backtrace, detailing where exactly the crash happened.
      • +
    • co - sortira du KDL et reprendra l’exécution normale, si possible.
      • +
    • int - affichera l’utilisation des interruptions (comme décrit ci-dessus).
      • +
    • bt - affiche une trace de déboguage (backtrace), indiquant exactement comment le plantage s’est produit.
    -

    What's next?

    -

    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.

    -

    Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked -as 'fixed'.

    +

    Et après ?

    +

    Une fois le bogue rapporté, un développeur le consultera et essayera de le cataloguer. Retenez que tous les développeurs sont des volontaires; un long délai avant réponse peut s’écouler après le rapport de bogue. L’ajout de nouvelles informations une fois celles-ci disponibles peut généralement permettre à un bogue d’être analysé plus rapidement. Néanmoins, n’essayez pas de « faire remonter » un bogue en ajoutant des commentaires non pertinents.

    +

    N’oubliez pas, le rapport d’un bogue ne se limite pas à sa soumission. Une fois cette tâche faite, vous ferez partie du processus de développement de Haiku. Les développeurs pourront vous poser des question pour essayer de résoudre votre bogue. Merci de rester disponible pour y répondre. Considérez votre travail « terminé » quand le bogue sera marqué comme étant « corrigé ».

    diff --git a/docs/welcome/fr/wifi.html b/docs/welcome/fr/wifi.html new file mode 100644 index 0000000000..abf91fc3f9 --- /dev/null +++ b/docs/welcome/fr/wifi.html @@ -0,0 +1,140 @@ + + + + + + + + + Wifi + + + + + + +
    +
    + + + + Welcome +
    +
    + +
    +
    + +

    Wifi in Haiku

    +

    +index +Expected supported hardware

    +

    All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.
    +This includes: +

    +
      +

    • aironetwifi supporting at least
      +Cisco Aironet 350 Series
      +Aironet PCI4500
      +Aironet PCI4800
      +

      • +

    • atheroswifi supporting almost every chipset outthere (though no AR9285 chips)

      • +

    • broadcom43xx supporting
      +BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318 +

      • +

    • iprowifi2100 supporting the 2100 chips

      • +

    • iprowifi2200 supporting
      +2200BG
      +2225BG
      +2915ABG +

      • +

    • iprowifi3945 supporting the 3945 chips

      • +

    • iprowifi4965 supporting the 4965 chips

      • +

    • marvell88w8335 supporting
      +Marvell Libertas 88W8310
      +Marvell Libertas 88W8335 +

      • +

    • marvell88w8363 supporting the 88W8363 chips

      • +

    • ralinkwifi supporting
      +RT2560
      +RT2561S
      +RT2561
      +RT2661 +

      • +

    • wavelanwifi supporting at least
      +3Com Airconnect
      +GLPRISM2 WaveLAN
      +Intersil Prism3
      +Intersil Prism2.5
      +Linksys WDT11
      +Netgear MA301
      +PRISM2STA WaveLAN
      +Siemens SpeedStream
      +SMC 2602W
      +Us Robotics 2415
      +Addtron AWA-100 PCI +

      • +
    +

    +index +WEP encryption

    +

    WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below) +

    +

    The usage is: setwep device_path [ssid] [key]. Below are some examples.

    +

    In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".

    +

    Example 1: Connect with 64-bit WEP encryption using a hex digit key

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
+

    Example 2: Connect to an unencrypted wireless network

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi
+
    +
  • To find out what your device_path is, have a look in Preferences -> Network.
    • +
  • To make your wifi device connect to a given SSID at each boot, add the setwep command to your home/config/boot/UserBootscript.
    • +
    +

    WEP notes

    +
      +
    • 64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits
      • +
    • 128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits
      • +
    • hexadecimal digits = characters 0-9 and A through F (prepended with '0x')
      • +
    +

    +index +WPA encryption

    +

    At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.

    +

    +index +install-wifi-firmwares.sh

    +

    To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run

    +
    ~> install-wifi-firmwares.sh
+
    +

    The Intel ipw2100 and ipw22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.

    +

    People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.

    +

    If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.

    +
    +
    + +
    +
    + Welcome +
    +
    + + + diff --git a/docs/welcome/images/flags/it.png b/docs/welcome/images/flags/it.png deleted file mode 100644 index e288f40b70f386ca43673b1c13a6e9cb976fed33..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 291 zcmeAS@N?(olHy`uVBq!ia0vp^0zk~o!3-oFZT@ltDb50q$YP+FFbFd;%$g$s6l6(v z^mSxl*w|O|J8&|PuaN8!f4ZKYRAz@;j(q!3lK=n!AY({UO#lFTB>(_`g8%^e{{R4h=>PzA zFaQARU;qF*m;eA5Z<1fdMgRZ+rBF;%MXjx^u&}Vr&CTNC;_~wH^Y8ET^Yiq5ee{!) z^wrh%Bqa4JD)m)W^}D9&J`aweaNJ#pxuloA>`$k6lM@Rd4 zdHd(*{7XyxRaN|cfBe$Y{i>?{ySx4B>izxw{{H^||Np@gVD$h1082?kK~xA^Rmiyk zfG`jPK^Z84h&G`A!X%wc=4Z2=cD~p;vOg{W=sjhN&wz4CG!~Gk8c?D{XMl^MYXMPq k^#Np(WWtSE!-2K$2NfPT=#+=Wa{vGU07*qoM6N<$f<`#BuK)l5 diff --git a/docs/welcome/images/flags/sv_SE.png b/docs/welcome/images/flags/sv_SE.png deleted file mode 100644 index 126a25030c4e4ced89bc100eda55d329c178b1c2..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 285 zcmeAS@N?(olHy`uVBq!ia0vp^0zk~o!3-oFZT@ltDb50q$YP+FFbFd;%$g$s6l6(v z^mSxl*w|O|J8&|PuaN8!Ig&k!_^A!d_M+7{E=gQj(dau!_7S#YUr+10g^ zwN9=v{&mga*EPpq*PMReOZ$B<{rCO!KhGz0M2O4;8tCNd;uyja-Fn85tHD5oF;pVXn^Ewzk`n3`{%>0*nGVmoJF$J_5Rh!PC{xWt~$(69D{` BH2DAk delta 532 zcmV+v0_**N0`UZp83+OZ008-bnr@LHQ-1;HNkl{xO9-iK*xFSX1CqVr9& z&pv$eabNT7y^S-0jQp;nd2Pp2>kib+KC!X1cgLv*4231#|2MAs_wWDhhhG+LxIKUU z9U%Mvl%D^6tw6@4g_nEhUO0K;@xQK`e}8}Ozx;&3CAxLb$#?&kF8_aU@Bjb*+kd8A z1(N?$Gyf+f0_l>zOJ5eP`QF_PWY1f5sjBM;NW;Pnck3ozeYo%bpQif%5D*jdKRg1& z$j$u!;>CqKZyi0C7d0IzYdgR&ZRQe?8_+;#=zl*yG%=vEN6$Yolskw0pWN|3CFOs7 z{QtNgotG4#fV7Hxhy*O;Jwf$pe0WlYd|Ni~^ z=kK52fBrlG+Mw-N-81KWRN9U!SKt4C`{rkIJV=$1$!~o_u!g@+ogDYi+$teGDp>y&xv}m;S658QF(CVow(c)YZJ?{I?3euf|NqOZxi1o8nt!IA%PCvV zkXke8-@m`#+bfP9xLw$AFt6b-(1m|PJbni`|NHwlJZ)QO-0JOzZ~guA<8^}Xs&%Is zg0q{-%>&Frn)sA!xfIISnRc-3wOp%@0iC1%_WD*z(9 WY4Z%MNr(Ud002ovPDHLkU;%=O!5_W= diff --git a/docs/welcome/it/bugreports.html b/docs/welcome/it/bugreports.html deleted file mode 100644 index b3486bcfcd..0000000000 --- a/docs/welcome/it/bugreports.html +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - Reporting bugs - - - - - - -
    -
    - - - Welcome -
    -
    - -
    -
    - -

    Reporting bugs

    - -

    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.

    -

    To keep our bugtracker effective, it's essential to abide by the Bug Tracker Etiquette.

    - -

    Getting a Trac account

    -

    To file a ticket, you need to have an account at Haiku's Bugtracker.
    -When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the all important verification mail often ends up there.

    - -

    Creating a bug report

    -

    Before reporting a bug, please make sure that it does not yet exist. You can also use the search function for this.
    -After you have established that it's a unique bug, make your information as accurate as possible:

    -
      -

    • Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).

      • -

    • Mention which revision from SVN you are running. You can find this information in 'About This System...' from the Deskbar menu.

      • -

    • Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.

      • -

    • Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.

      • -

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the PRINT key saves a PNG in /boot/home/).

      • -
    - -

    Software Bugs

    -

    When an application crashed, you should invoke the debugger from the alert that pops up. Entering bt into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.

    - -

    Hardware Bugs

    -

    When dealing with a hardware/driver related bug, you should attach the following information:

    -
      -
    • listdev - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' lshw and lspci.
      • -
    • listusb -v - assuming its a USB related issue, similar to lsusb.
      • -
    • open /var/log/syslog - the primary system log used by Haiku, akin to on screen debugging during boot. With the open command you can crop down the relevant part of the syslog in a text editor.
      • -
    • listimage | grep drivers/ - lists all used drivers.
      • -
    • ints - only available within Kernel Debugging Land (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
      • -
    -

    You enter these commands into Terminal. Add a > output.txt after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.

    - -

    Kernel Debugging Land - KDL

    -

    When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with ALTSysReqD (SysReq being PRINT on most keyboards).

    -
      -
    • co - will exit KDL and continue normal system operation, if possible.
      • -
    • int - will show interrupt usage (as described above).
      • -
    • bt - shows a backtrace, detailing where exactly the crash happened.
      • -
    - -

    What's next?

    -

    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.

    -

    Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked -as 'fixed'.

    - -
    -
    - -
    -
    - Welcome -
    -
    - - - diff --git a/docs/welcome/jp/bugreports.html b/docs/welcome/jp/bugreports.html deleted file mode 100644 index a8157d748e..0000000000 --- a/docs/welcome/jp/bugreports.html +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - Reporting bugs - - - - - - -
    -
    - - - Welcome -
    -
    - -
    -
    - -

    Reporting bugs

    - -

    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.

    -

    To keep our bugtracker effective, it's essential to abide by the Bug Tracker Etiquette.

    - -

    Getting a Trac account

    -

    To file a ticket, you need to have an account at Haiku's Bugtracker.
    -When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the all important verification mail often ends up there.

    - -

    Creating a bug report

    -

    Before reporting a bug, please make sure that it does not yet exist. You can also use the search function for this.
    -After you have established that it's a unique bug, make your information as accurate as possible:

    -
      -

    • Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).

      • -

    • Mention which revision from SVN you are running. You can find this information in 'About This System...' from the Deskbar menu.

      • -

    • Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.

      • -

    • Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.

      • -

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the PRINT key saves a PNG in /boot/home/).

      • -
    - -

    Software Bugs

    -

    When an application crashed, you should invoke the debugger from the alert that pops up. Entering bt into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.

    - -

    Hardware Bugs

    -

    When dealing with a hardware/driver related bug, you should attach the following information:

    -
      -
    • listdev - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' lshw and lspci.
      • -
    • listusb -v - assuming its a USB related issue, similar to lsusb.
      • -
    • open /var/log/syslog - the primary system log used by Haiku, akin to on screen debugging during boot. With the open command you can crop down the relevant part of the syslog in a text editor.
      • -
    • listimage | grep drivers/ - lists all used drivers.
      • -
    • ints - only available within Kernel Debugging Land (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
      • -
    -

    You enter these commands into Terminal. Add a > output.txt after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.

    - -

    Kernel Debugging Land - KDL

    -

    When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with ALTSysReqD (SysReq being PRINT on most keyboards).

    -
      -
    • co - will exit KDL and continue normal system operation, if possible.
      • -
    • int - will show interrupt usage (as described above).
      • -
    • bt - shows a backtrace, detailing where exactly the crash happened.
      • -
    - -

    What's next?

    -

    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.

    -

    Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked -as 'fixed'.

    - -
    -
    - -
    -
    - Welcome -
    -
    - - - diff --git a/docs/welcome/ru/bugreports.html b/docs/welcome/ru/bugreports.html index 3f454d1c4e..bbf1ce57d1 100644 --- a/docs/welcome/ru/bugreports.html +++ b/docs/welcome/ru/bugreports.html @@ -11,7 +11,7 @@ * Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki * Humdinger * Translators: - * michael_s + * Michael Smirnov * --> @@ -22,7 +22,7 @@
    @@ -31,10 +31,8 @@
  • Русский
  • Français
  • Deutsch
    • -
  • Italiano
  • Español
    • -
  • Svensk
    • -
  • 日本語
    • +
  • Українська
  • English
    • diff --git a/docs/welcome/ru/wifi.html b/docs/welcome/ru/wifi.html new file mode 100644 index 0000000000..4bf3c7cdf6 --- /dev/null +++ b/docs/welcome/ru/wifi.html @@ -0,0 +1,140 @@ + + + + + + + + + Wifi + + + + + + +
    +
    + + + + Welcome +
    +
    + +
    +
    + +

    Wifi in Haiku

    +

    +index +Expected supported hardware

    +

    All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.
    +This includes: +

    +
      +

    • aironetwifi supporting at least
      +Cisco Aironet 350 Series
      +Aironet PCI4500
      +Aironet PCI4800
      +

      • +

    • atheroswifi supporting almost every chipset outthere (though no AR9285 chips)

      • +

    • broadcom43xx supporting
      +BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318 +

      • +

    • iprowifi2100 supporting the 2100 chips

      • +

    • iprowifi2200 supporting
      +2200BG
      +2225BG
      +2915ABG +

      • +

    • iprowifi3945 supporting the 3945 chips

      • +

    • iprowifi4965 supporting the 4965 chips

      • +

    • marvell88w8335 supporting
      +Marvell Libertas 88W8310
      +Marvell Libertas 88W8335 +

      • +

    • marvell88w8363 supporting the 88W8363 chips

      • +

    • ralinkwifi supporting
      +RT2560
      +RT2561S
      +RT2561
      +RT2661 +

      • +

    • wavelanwifi supporting at least
      +3Com Airconnect
      +GLPRISM2 WaveLAN
      +Intersil Prism3
      +Intersil Prism2.5
      +Linksys WDT11
      +Netgear MA301
      +PRISM2STA WaveLAN
      +Siemens SpeedStream
      +SMC 2602W
      +Us Robotics 2415
      +Addtron AWA-100 PCI +

      • +
    +

    +index +WEP encryption

    +

    WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below) +

    +

    The usage is: setwep device_path [ssid] [key]. Below are some examples.

    +

    In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".

    +

    Example 1: Connect with 64-bit WEP encryption using a hex digit key

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
+

    Example 2: Connect to an unencrypted wireless network

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi
+
    +
  • To find out what your device_path is, have a look in Preferences -> Network.
    • +
  • To make your wifi device connect to a given SSID at each boot, add the setwep command to your home/config/boot/UserBootscript.
    • +
    +

    WEP notes

    +
      +
    • 64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits
      • +
    • 128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits
      • +
    • hexadecimal digits = characters 0-9 and A through F (prepended with '0x')
      • +
    +

    +index +WPA encryption

    +

    At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.

    +

    +index +install-wifi-firmwares.sh

    +

    To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run

    +
    ~> install-wifi-firmwares.sh
+
    +

    The Intel ipw2100 and ipw22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.

    +

    People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.

    +

    If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.

    +
    +
    + +
    +
    + Welcome +
    +
    + + + diff --git a/docs/welcome/sv_SE/bugreports.html b/docs/welcome/sv_SE/bugreports.html deleted file mode 100644 index 8455102b22..0000000000 --- a/docs/welcome/sv_SE/bugreports.html +++ /dev/null @@ -1,104 +0,0 @@ - - - - - - - - Reporting bugs - - - - - - -
    -
    - - - Welcome -
    -
    - -
    -
    - -

    Reporting bugs

    - -

    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.

    -

    To keep our bugtracker effective, it's essential to abide by the Bug Tracker Etiquette.

    - -

    Getting a Trac account

    -

    To file a ticket, you need to have an account at Haiku's Bugtracker.
    -When creating a new account, be certain to provide your email address as it is necessary to obtain basic ticket modification privileges. Be sure to check your spam folder shortly afterwards, as the all important verification mail often ends up there.

    - -

    Creating a bug report

    -

    Before reporting a bug, please make sure that it does not yet exist. You can also use the search function for this.
    -After you have established that it's a unique bug, make your information as accurate as possible:

    -
      -

    • Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).

      • -

    • Mention which revision from SVN you are running. You can find this information in 'About This System...' from the Deskbar menu.

      • -

    • Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.

      • -

    • Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.

      • -

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the PRINT key saves a PNG in /boot/home/).

      • -
    - -

    Software Bugs

    -

    When an application crashed, you should invoke the debugger from the alert that pops up. Entering bt into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.

    - -

    Hardware Bugs

    -

    When dealing with a hardware/driver related bug, you should attach the following information:

    -
      -
    • listdev - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' lshw and lspci.
      • -
    • listusb -v - assuming its a USB related issue, similar to lsusb.
      • -
    • open /var/log/syslog - the primary system log used by Haiku, akin to on screen debugging during boot. With the open command you can crop down the relevant part of the syslog in a text editor.
      • -
    • listimage | grep drivers/ - lists all used drivers.
      • -
    • ints - only available within Kernel Debugging Land (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
      • -
    -

    You enter these commands into Terminal. Add a > output.txt after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.

    - -

    Kernel Debugging Land - KDL

    -

    When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with ALTSysReqD (SysReq being PRINT on most keyboards).

    -
      -
    • co - will exit KDL and continue normal system operation, if possible.
      • -
    • int - will show interrupt usage (as described above).
      • -
    • bt - shows a backtrace, detailing where exactly the crash happened.
      • -
    - -

    What's next?

    -

    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.

    -

    Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked -as 'fixed'.

    - -
    -
    - -
    -
    - Welcome -
    -
    - - - diff --git a/docs/welcome/uk/bugreports.html b/docs/welcome/uk/bugreports.html index 17bed56ec0..3e470cacb4 100644 --- a/docs/welcome/uk/bugreports.html +++ b/docs/welcome/uk/bugreports.html @@ -29,11 +29,8 @@
  • Українська
  • Français
  • Deutsch
    • -
  • Italiano
  • Русский
  • Español
    • -
  • Svensk
    • -
  • 日本語
  • English
    • diff --git a/docs/welcome/uk/wifi.html b/docs/welcome/uk/wifi.html new file mode 100644 index 0000000000..cad6323197 --- /dev/null +++ b/docs/welcome/uk/wifi.html @@ -0,0 +1,140 @@ + + + + + + + + + Wifi + + + + + + +
    +
    + + + + Welcome +
    +
    + +
    +
    + +

    Wifi in Haiku

    +

    +index +Expected supported hardware

    +

    All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.
    +This includes: +

    +
      +

    • aironetwifi supporting at least
      +Cisco Aironet 350 Series
      +Aironet PCI4500
      +Aironet PCI4800
      +

      • +

    • atheroswifi supporting almost every chipset outthere (though no AR9285 chips)

      • +

    • broadcom43xx supporting
      +BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318 +

      • +

    • iprowifi2100 supporting the 2100 chips

      • +

    • iprowifi2200 supporting
      +2200BG
      +2225BG
      +2915ABG +

      • +

    • iprowifi3945 supporting the 3945 chips

      • +

    • iprowifi4965 supporting the 4965 chips

      • +

    • marvell88w8335 supporting
      +Marvell Libertas 88W8310
      +Marvell Libertas 88W8335 +

      • +

    • marvell88w8363 supporting the 88W8363 chips

      • +

    • ralinkwifi supporting
      +RT2560
      +RT2561S
      +RT2561
      +RT2661 +

      • +

    • wavelanwifi supporting at least
      +3Com Airconnect
      +GLPRISM2 WaveLAN
      +Intersil Prism3
      +Intersil Prism2.5
      +Linksys WDT11
      +Netgear MA301
      +PRISM2STA WaveLAN
      +Siemens SpeedStream
      +SMC 2602W
      +Us Robotics 2415
      +Addtron AWA-100 PCI +

      • +
    +

    +index +WEP encryption

    +

    WEP encryption is available through a command-line application setwep. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. setwep works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see WEP notes below) +

    +

    The usage is: setwep device_path [ssid] [key]. Below are some examples.

    +

    In this example, let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".

    +

    Example 1: Connect with 64-bit WEP encryption using a hex digit key

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
+

    Example 2: Connect to an unencrypted wireless network

    +
    setwep /dev/net/iprowifi3945/0 haikuwifi
+
    +
  • To find out what your device_path is, have a look in Preferences -> Network.
    • +
  • To make your wifi device connect to a given SSID at each boot, add the setwep command to your home/config/boot/UserBootscript.
    • +
    +

    WEP notes

    +
      +
    • 64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits
      • +
    • 128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits
      • +
    • hexadecimal digits = characters 0-9 and A through F (prepended with '0x')
      • +
    +

    +index +WPA encryption

    +

    At the moment there is no WPA encryption available in Haiku. However, there is some preliminary and unfinished code for implementing WPA available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.

    +

    +index +install-wifi-firmwares.sh

    +

    To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you'll need to run

    +
    ~> install-wifi-firmwares.sh
+
    +

    The Intel ipw2100 and ipw22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.

    +

    People building their own Haiku image can modify their build/jam/UserBuildConfig accordingly. Details for that and general updates on the wifi topic are found at the online version of this document.

    +

    If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a shell script, which will create a zip file for you to extract to Haiku's /boot. After that you'll have all files needed by install-wifi-firmwares.sh.

    +
    +
    + +
    +
    + Welcome +
    +
    + + + diff --git a/docs/welcome/welcome_de.html b/docs/welcome/welcome_de.html index cfa35478f2..fe25a5af8b 100644 --- a/docs/welcome/welcome_de.html +++ b/docs/welcome/welcome_de.html @@ -31,11 +31,8 @@ @@ -49,7 +46,7 @@

    Willkommen zu Haiku!

    -

    Danke, dass Sie sich für Haiku interessieren! Wir hoffen, dass wir durch unsere erste öffentliche Version neue Entwickler für unser Projekt begeistern können und Anwender in die Lage versetzen, Haiku auszuprobieren. Natürlich ist diese Alpha Version noch lange nicht vollständig oder gar fehlerfrei und sie erfüllt auch noch nicht die Ziele, die wir uns selbst gesteckt haben, aber sie zeigt, warum wir uns in diesem Projekt so engagieren und es ermöglicht anderen, das große Potential von Haiku zu erkunden.

    +

    Danke, für das Interesse an Haiku! Wir hoffen, dass wir durch die zweite öffentliche Version neue Entwickler für unser Projekt begeistern können und Anwendern die Möglichkeit geben, Haiku kennenzulernen. Natürlich ist diese Alpha Version noch lange nicht vollständig oder gar fehlerfrei und sie erfüllt auch noch nicht die Ziele, die wir uns selbst gesteckt haben, aber sie zeigt, warum wir uns in diesem Projekt so engagieren und es ermöglicht anderen, das große Potential von Haiku zu erkunden.

    index @@ -75,7 +72,7 @@

    index Software installieren

    -

    Da Haiku sowohl binärkompatibel als auch code-kompatibel mit dem BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku. Nach dem Herunterladen eines Programm-Paketes muss es lediglich nach /boot/apps/ entpackt (ein Doppelklick öffnet den Expander) und von dort gestartet werden.

    +

    Da Haiku sowohl binärkompatibel als auch code-kompatibel mit dem BeOS ist, laufen viele BeOS-Anwendungen auch direkt in Haiku (für manche Programme muss das Optional Package "beoscompatibility" installiert werden, siehe unten). Nach dem Herunterladen eines Programm-Paketes muss es lediglich nach /boot/apps/ entpackt (ein Doppelklick öffnet den Expander) und von dort gestartet werden.

    Große Software-Verzeichnisse sind:

      @@ -86,35 +83,37 @@

    Daneben existieren auch sogenannte "Optional Packages", die beim Erzeugen von Haiku Images zum Einsatz kommen. Sie sind nicht dazu bestimmt vom Benutzer manuell entpackt und installiert zu werden. Dafür gibt es aber das kleine Skript installoptionalpackage. Es dient als Lückenfüller solange noch an Haikus Paketmanagement gearbeitet wird. Mit ihm lassen sich viele der vorhandenen Optional Packages installieren.
    -Dazu benutzt man einen Befehl im Terminal:

    -

    installoptionalpackage -l - listet alle verfügbaren Pakete auf.
    -installoptionalpackage -a {Paketname} - lädt ein Packet herunter und installiert es.
    -installoptionalpackage -a "{Paketname} {packagename}" - installiert mehrere Pakete auf einmal. Anführungszeichen nicht vergessen!

    +Dazu benutzt man einen Befehl im Terminal: installoptionalpackage -h erklärt die verschiedenen Optionen.

    + +

    +index +WLAN in Haiku

    +

    WLAN funktioniert im gewissen 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 sie eventuell erforderliche Installation befindet sich auf der WLAN Seite (auch online auf Englisch).

    index Die API kennenlernen

    -

    Da Haiku eine Reimplemention des BeOS R5 ist, sind die API die gleichen (mit einigen Erweiterungen). Deshalb ist die Dokumentation im BeBook immernoch eine hilfreiche Quelle. Dankenswerter weise hat die Firma ACCESS, die alle Rechte von Be Inc. übernommen hat, einer Veröffentlichung des BeBook zugestimmt.

    +

    Da Haiku eine Reimplemention des BeOS R5 ist, sind die API die gleichen (mit einigen Erweiterungen). Deshalb ist die Dokumentation im Be Book immernoch eine hilfreiche Quelle. Dankenswerter weise hat die Firma ACCESS, die alle Rechte von Be Inc. übernommen hat, einer Veröffentlichung des Be Book zugestimmt.

    Diese Informationen sollten einen guten Einstieg in die Materie vermitteln:

    index Kontakte knüpfen

    -

    Um sich mit anderen Entwickler und Anwender auszutauschen muss man nur an den Diskussionen im IRC, unseren Foren oder Mailinglisten teilnehmen. Wie üblich, wenn sich mehrere Menschen unterhalten, sollte eine gewisse Etikette eingehalten werden.

    +

    Um sich mit anderen Entwickler und Anwender auszutauschen muss man nur an den Diskussionen im IRC, unseren Foren oder Mailinglisten teilnehmen. Wie üblich, wenn sich mehrere Menschen unterhalten, sollte eine gewisse Etikette eingehalten werden.

    diff --git a/docs/welcome/welcome_en.html b/docs/welcome/welcome_en.html index df7a76a093..7efb0f62cd 100644 --- a/docs/welcome/welcome_en.html +++ b/docs/welcome/welcome_en.html @@ -29,11 +29,8 @@
  • English
  • Français
  • Deutsch
    • -
  • Italiano
  • Русский
  • Español
    • -
  • Svensk
    • -
  • 日本語
  • Українська
    • @@ -46,12 +43,12 @@

    Welcome to Haiku!

    -

    Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this alpha release 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.

    +

    Thank you very much for checking out Haiku! This is our second 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 alpha release 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.

    index Beware of Bugs

    -

    We were working very hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.

    +

    We have been working hard to fix all possible to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.

    We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.

    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.

    @@ -72,46 +69,48 @@

    index Installing more software

    -

    Because of our binary and source compatibility, many BeOS applications run on Haiku. After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.

    +

    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 Expander) to /boot/apps/ and start the application from there.

    Popular software repositories are:

    • Haikuware
    • BeBits
      • -
    • HaikuPorts maintains patches for ported software
      • -
    • OsDrawer hosts native BeOS and Haiku open source software projects
      • +
    • HaikuPorts - maintains patches for ported software
      • +
    • OsDrawer - hosts native BeOS and Haiku open source software projects
    -

    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. However, a utility script is provided, installoptionalpackage. 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.
    -You'll have to run a command in Terminal:

    -

    installoptionalpackage -l - lists all available packages.
    -installoptionalpackage -a {packagename} - will download and add the package to your system.
    -installoptionalpackage -a "{packagename} {packagename}" - will install several at once. The quotes are indeed necessary.

    +

    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, installoptionalpackage. 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.
    +You'll have to run a command in Terminal: installoptionalpackage -h explains its usage.

    + +

    +index +Wifi in Haiku

    +

    Wifi does work to some extend. At the moment you can only log into unprotected 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 in our Wifi page (also online).

    index Getting to know the API

    -

    Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the BeBook is still a valid resource. Thanks to ACCESS, who own the rights to former Be Inc. property, we are allowed to provide a copy of the BeBook.

    +

    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.

    There are additional resources that should help you getting started:

    index Getting in contact

    -

    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 Mailing List Etiquette.

    +

    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 Mailing List Etiquette.

    diff --git a/docs/welcome/welcome_es.html b/docs/welcome/welcome_es.html index 0860353768..f99ad1d672 100644 --- a/docs/welcome/welcome_es.html +++ b/docs/welcome/welcome_es.html @@ -13,6 +13,7 @@ * Translators: * Oscar Carballal * Jorge G. Mare + * miguel~1.mx * --> @@ -32,10 +33,7 @@
  • Español
  • Français
  • Deutsch
    • -
  • Italiano
  • Русский
    • -
  • Svensk
    • -
  • 日本語
  • Українська
  • English
    • @@ -49,13 +47,13 @@

    ¡Bienvenido a Haiku!

    -

    Muchas gracias por probar Haiku. Este es nuestro primer lanzamiento público. Esperamos poder atraer a nuevos desarrolladores a nuestro proyecto y darle a los usuarios una oportunidad para probar Haiku. Somos conscientes de que esta versión alpha no cumple del todo los requisitos que nos hemos propuesto nosotros mismos, y no ofrece todas las características ni la experiencia de usuario que fueron planificadas para la versión R1 final. De todas maneras, esperamos que esta versión le permita descubrir el gran potencial de Haiku, y que comparta nuestra emoción.

    +

    Muchas gracias por probar Haiku. Este es nuestro segundo lanzamiento público. Esperamos atraer nuevos desarrolladores a nuestro proyecto y darle a los futuros usuarios una oportunidad para probar Haiku. Estamos conscientes de que esta versión alpha no cumple del todo los objetivos que nos hemos propuesto y no ofrece todas las características ni la experiencia de usuario bien formulada que fueron planificadas para la versión R1 final. No obstante, esperamos que esta versión le permita descubrir el gran potencial de Haiku, y que comparta nuestra emoción.

    index Cuidado con los bugs

    -

    Hemos trabajado muy duro para arreglar todos los fallos posibles, de todas maneras, siendo una versión alpha, es muy probable que haya muchos por descubrir.

    -
    No recomendamos el uso de versiones alfa en sistemas de producción, ya que sus datos podrían verse alterados, estropeados o completamente borrados.
    +

    Hemos trabajado muy duro para arreglar todos los fallos posibles, aún así, siendo una versión alpha, es muy probable que haya muchos por descubrir.

    +
    No se recomienda el uso de versiones alfa como sistemas de producción. Su información podría alterarse, estropearse o destruirse en algún momento.

    Una de las razones principales para liberar una versión alpha es atraer a mucha gente para probar el sistema y descubrir fallos o darnos sugerencias para futuras mejoras. Por favor, archive los fallos y mejoras en nuestro bug tracker después de utilizar su sistema de búsqueda para evitar duplicados.

      @@ -75,46 +73,48 @@

      index Instalando más software

      -

      Debido a nuestra compatibilidad de código binario y código fuente, muchas aplicaciones de BeOS funcionan en Haiku. Tras descargar un paquete, tan sólo debe descomprimirlo (doble clic abre Expander) a /boot/apps/ e iniciar la aplicación desde ahí.

      +

      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 Expander) to /boot/apps/ and start the application from there.

      Repositorios de software populares son:

      • Haikuware
      • BeBits
        • -
      • HaikuPorts mantiene parches para las aplicaciones portadas.
        • -
      • OsDrawer hospeda los proyectos de software de código libre para BeOS/Haiku.
        • +
      • HaikuPorts mantiene actualizaciones y parches para las aplicaciones portadas.
        • +
      • OsDrawer hospeda los proyectos de software de código libre para BeOS y Haiku.
      -

      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. However, a utility script is provided, installoptionalpackage. 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.
      -You'll have to run a command in Terminal:

      -

      installoptionalpackage -l - lists all available packages.
      -installoptionalpackage -a {packagename} - will download and add the package to your system.
      -installoptionalpackage -a "{packagename} {packagename}" - will install several at once. The quotes are indeed necessary.

      +

      También están los así llamados Paquetes opcionales, los cuales se utilizan por el sistema de construcción de Haiku. No se persigue que los usuarios finales los extraigan e instalen manualmente. En su lugar, un script de utilidades se proporciona, installoptionalpackage. La intención de este script es de llenar el vacío mientras el mantenimiento de paquetes de Haiku esté todavía en construcción. Este script permite instalar la mayoría de los Paquetes opcionales disponibles.
      +Al correrse el siguiente comando en una Terminal: installoptionalpackage -h se explica su uso.

      + +

      +index +Wifi in Haiku

      +

      Wifi does work to some extend. At the moment you can only log into unprotected 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 in our Wifi page (also online).

      index Conociendo la API

      -

      Como Haiku es una reimplementación, la API es la misma que para BeOS R5 (con algunos añadidos). Por lo tanto la documentación existente en el BeBook es todavía un recurso válido. Gracias a ACCESS, que tiene los derechos de la antigua Be Inc., se nos permite distribuir una copia del BeBook.

      +

      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.

      Existen algunos recursos que le pueden ayudar a comenzar:

      index -Poniéndose en contacto

      -

      Entre en contacto con otros desarrolladores y usuarios y únase a las conversaciones del IRC, foro o las listas de correo. Cuando tanta gente diferente se junta, es necesario establecer unas normas para que la comunicación sea efectiva. Por favor, respete nuestra Etiqueta de listas de correo.

      +Ponerse en contacto +

      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 Etiqueta de listas de correo.

      diff --git a/docs/welcome/welcome_fr.html b/docs/welcome/welcome_fr.html index 1c8b86193b..683b1cd1ff 100644 --- a/docs/welcome/welcome_fr.html +++ b/docs/welcome/welcome_fr.html @@ -31,11 +31,8 @@ @@ -49,12 +46,12 @@

      Bienvenue sur Haiku !

      -

      Merci beaucoup d’essayer Haiku  ! Voici notre première version publique. Nous espérons encourager de nouveaux développeurs à nous rejoindre et donner aux futurs utilisateurs la possibilité d’essayer Haiku. Nous sommes conscients que cette version alpha ne remplit pas touts les objectifs que nous nous sommes fixés et ne fournit pas toutes les fonctionnalités et l’expérience utilisateur attendues pour la version R1 finale. Néanmoins, nous espérons que cette pré-version vous permettra de découvrir le potentiel de Haiku et de partager notre excitation.

      +

      Merci beaucoup d’essayer Haiku  ! Voici notre seconde 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 version alpha ne remplit pas touts les objectifs que nous nous sommes fixés et ne fournit pas toutes les fonctionnalités et l’expérience utilisateur attendues pour la version R1 finale. Néanmoins, nous espérons que cette version (même inachevée) vous permettra de découvrir le potentiel de Haiku et de partager notre enthousiasme.

      index Attention aux bogues

      -

      Nous travaillons dur pour résoudre les bogues critiques du système. Néanmoins, Haiku n'étant qu'au stade de version alpha, vous risquez d'en rencontrer lors de vos essais.

      +

      Nous avons travaillé dur pour résoudre les bogues critiques du système. Néanmoins, Haiku n'étant qu'au stade d'une version alpha, beaucoup n'ont pas encore été découverts. Vous risquez de les rencontrer lors de vos essais.

      Nous déconseillons l'utilisation des versions Alpha sur un système en production. Les données que vous manipulez pourraient être altérées, corrompues ou tout simplement détruites.

      La sortie d'une version alpha a pour objectif de faire découvrir et tester le système par d'avantage de personnes, afin de trouver les bogues présents et d'obtenir des suggestions d'améliorations futures. Veuillez rapporter d'éventuels bogues et suggestions sur notre traqueur de bogues après avoir utilisé sa fonction de recherche pour éviter les doublons.

      @@ -75,41 +72,46 @@

      index Installer plus de logiciels

      -

      Grace à notre compatibilité binaire et source avec BeOS, de nombreuses applications écrites pour ce système fonctionne sous Haiku. Après avoir téléchargé un paquet, décompressez le (un double-clic lancera Expander) dans /boot/apps/ et démarrez l'application depuis de ce dossier.

      +

      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 Expander) to /boot/apps/ and start the application from there.

      Des sites populaires référencent les logiciels disponibles.

      • Haikuware
      • BeBits
        • -
      • HaikuPorts maintient les correctifs pour les logiciels portés
        • -
      • OsDrawer héberge des projets de logiciels open source natifs pour BeOS et Haiku
        • +
      • HaikuPorts - maintient les correctifs pour les logiciels portés
        • +
      • OsDrawer - héberge des projets de logiciels open source natifs pour BeOS et Haiku
      -

      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. However, a utility script is provided, installoptionalpackage. 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.
      -You'll have to run a command in Terminal:

      -

      installoptionalpackage -l - lists all available packages.
      -installoptionalpackage -a {packagename} - will download and add the package to your system.
      -installoptionalpackage -a "{packagename} {packagename}" - will install several at once. The quotes are indeed necessary.

      +

      Il y a aussi les paquets dits optionnels, qui sont utilisés par le système de compilation d'Haiku. Les utilisateurs finaux ne sont pas sensés les extraire manuellement pour les installer. Toutefois, un script utilitaire est fourni : installoptionalpackage. +Ce script est destiné à combler les lacunes du gestionnaire de paquets en cours de construction. +Il vous permettra d'installer la plus part des paquets optionnels disponibles.
      +Vous devrez saisir une ligne de commande dans le Terminal : +installoptionalpackage -h explique son utilisation.

      + +

      +index +Wifi in Haiku

      +

      Wifi does work to some extend. At the moment you can only log into unprotected 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 in our Wifi page (also online).

      index Apprendre à connaître l'API

      -

      Comme Haiku est une ré-implémentation, l'API est encore le même que celle de BeOS R5 (avec quelques ajouts). +

      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.

      Quelques ressources supplémentaires sont susceptible de vous aider à commencer :

      index Rester en contact

      -

      Entrer en contact avec les autres développeurs et utilisateurs, participer aux discussions sur IRC, dans nos forums ou les listes de diffusion. -Quand beaucoup de gens différents se rencontrent, des règles doivent êtres établies pour maintenir une communication efficace. S'il vous plaît respecter +

      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 l'étiquette de notre liste de diffusion.

      diff --git a/docs/welcome/welcome_it.html b/docs/welcome/welcome_it.html deleted file mode 100644 index a75615db99..0000000000 --- a/docs/welcome/welcome_it.html +++ /dev/null @@ -1,127 +0,0 @@ - - - - - - - - Welcome to Haiku! - - - - - - -
      -
      - - -  -
      -
      - -
      -
      - -

      -Welcome to Haiku!

      -

      Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this alpha release 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.

      - -

      -index -Beware of Bugs

      -

      We were working very hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.

      -
      We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.
      - -

      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.

      - - -

      -index -Getting to know the system

      -

      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:

      - - -

      -index -Installing more software

      -

      Because of our binary and source compatibility, many BeOS applications run on Haiku. After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.

      - -

      Popular software repositories are:

      - - -

      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. However, a utility script is provided, installoptionalpackage. 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.
      -You'll have to run a command in Terminal:

      -

      installoptionalpackage -l - lists all available packages.
      -installoptionalpackage -a {packagename} - will download and add the package to your system.
      -installoptionalpackage -a "{packagename} {packagename}" - will install several at once. The quotes are indeed necessary.

      - -

      -index -Getting to know the API

      -

      Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the BeBook is still a valid resource. Thanks to ACCESS, who own the rights to former Be Inc. property, we are allowed to provide a copy of the BeBook.

      - -

      There are additional resources that should help you getting started:

      - - -

      -index -Getting in contact

      -

      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 Mailing List Etiquette.

      - - -
      -
      - -
      -
      -  -
      -
      - - - diff --git a/docs/welcome/welcome_jp.html b/docs/welcome/welcome_jp.html deleted file mode 100644 index cdcea7c41a..0000000000 --- a/docs/welcome/welcome_jp.html +++ /dev/null @@ -1,129 +0,0 @@ - - - - - - - - Haikuへようこそ! - - - - - - -
      -
      - - -  -
      -
      - -
      -
      - -

      -Haikuへようこそ!

      -

      Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this alpha release 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.

      - -

      -index -バグに注意

      -

      We were working very hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.

      -
      We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.
      - -

      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.

      - - -

      -index -システムを把握する

      -

      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:

      - - -

      -index -Installing more software

      -

      Because of our binary and source compatibility, many BeOS applications run on Haiku. After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.

      - -

      Popular software repositories are:

      - - -

      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. However, a utility script is provided, installoptionalpackage. 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.
      -You'll have to run a command in Terminal:

      -

      installoptionalpackage -l - lists all available packages.
      -installoptionalpackage -a {packagename} - will download and add the package to your system.
      -installoptionalpackage -a "{packagename} {packagename}" - will install several at once. The quotes are indeed necessary.

      - -

      -index -APIを理解する

      -

      Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the BeBook is still a valid resource. Thanks to ACCESS, who own the rights to former Be Inc. property, we are allowed to provide a copy of the BeBook.

      - -

      There are additional resources that should help you getting started:

      - - -

      -index -Getting in contact

      -

      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 Mailing List Etiquette.

      - - -
      -
      - -
      -
      -  -
      -
      - - - diff --git a/docs/welcome/welcome_ru.html b/docs/welcome/welcome_ru.html index d8ffc78718..7ee0453000 100644 --- a/docs/welcome/welcome_ru.html +++ b/docs/welcome/welcome_ru.html @@ -13,6 +13,7 @@ * Translators: * Michael Smirnov * Rustam + * Diver * --> @@ -32,10 +33,7 @@
    • Русский
    • Français
    • Deutsch
      • -
    • Italiano
    • Español
      • -
    • Svensk
      • -
    • 日本語
    • Українська
    • English
    @@ -49,15 +47,15 @@

    Добро пожаловать в Haiku!

    -

    Большое спасибо за проявленный интерес к Haiku! Это наш первый публичный релиз, мы надеемся привлечь новых разработчиков к нашему проекту, и дать будущим пользователям шанс увидеть Haiku в деле. Понятно, что этот альфа-релиз далеко не полностью соответствует намеченным нами целям, и не предоставляет все функции, которые мы собирались дать конечному пользователю, запланировав их для финальной версии R1. Однако, мы надеемся, что этот релиз позволит вам заметить большой потенциал Haiku, и вы найдёте немного времени для её изучения.

    +

    Большое спасибо за проявленный интерес к Haiku! Это наш второй публичный релиз, мы надеемся привлечь новых разработчиков к нашему проекту и дать будущим пользователям шанс увидеть Haiku в деле. Понятно, что этот альфа-релиз далеко не полностью соответствует намеченным нами целям, и не предоставляет все функции, которые мы собирались дать конечному пользователю, запланировав их для финальной версии R1. Однако, мы надеемся, что этот релиз позволит Вам заметить большой потенциал Haiku, и Вы найдёте немного времени для её изучения.

    index Остерегайтесь Ошибок!

    Мы провели тяжёлую работу по выявлению и устранению ошибок ("багов"), однако это только альфа-релиз и в нём обязательно присутствуют немало скрытых ошибок.

    -
    Мы не рекомендуем использовать альфа-версии в качестве основной операционной системы. В ваши данные с большой вероятностью могут быть внесены нежелательные изменения, они могут исказиться или даже уничтожиться.
    +
    Мы не рекомендуем использовать альфа-версии в качестве основной операционной системы. В Ваши данные с большой вероятностью могут быть внесены нежелательные изменения, они могут исказиться или даже могут быть уничтожены.
    -

    Одной из главных причин для выпуска альфа-версии явилось желание привлечь больше пользователей для тестирования и обнаружения ошибок, а также получения от них предложений по дальнейшему улучшению Haiku. Пожалуйста, оставляйте отчёты о найденных багах и предложения по улучшению в нашей системе отслеживания ошибок (bug tracker), но только после использования поиска, чтобы избежать дубликатов.

    +

    Одной из главных причин для выпуска альфа-версии явиляется желание привлечь больше пользователей для тестирования и обнаружения ошибок, а также получения от них предложений по дальнейшему улучшению Haiku. Пожалуйста, оставляйте отчёты о найденных багах и предложения по улучшению в нашей системе отслеживания ошибок (bug tracker), но только после использования поиска, чтобы избежать дубликатов.

    • Система отслеживания ошибок в Haiku (Bug Tracker)
    • Советы по сообщениям об ошибках
      • @@ -66,7 +64,7 @@

      index Знакомство с системой

      -

      Первые релизы Haiku будут похожи по функционалу и вешнему виду на BeOS R5, которую она и призвана повторить. Если вы никогда не пользовались этой операционной системой, то рекомендуется воспользоваться следующими ссылками:

      +

      Первые релизы Haiku будут похожи по функционалу и вешнему виду на BeOS R5, которую она и призвана повторить. Если Вы никогда не пользовались этой операционной системой, то рекомендуется воспользоваться следующими ссылками:

      • Руководство пользователя Haiku
      • Список сайтов о BeOS/Haiku
        • @@ -75,46 +73,49 @@

        index Установка дополнительных программ

        -

        Так как Haiku бинарно и на уровне исходных кодов совместима с BeOS, то многие BeOS-приложения работают и в ней. Загрузив архив с программой, просто распакуйте его (достаточно двойного клика для открытия архива в Expander) в /boot/apps/, и оттуда же запускайте это приложение.

        +

        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 Expander) to /boot/apps/ and start the application from there.

        Популярные каталоги программ:

        • Haikuware сайт с программами, ориентированными на Haiku.
        • BeBits самый популярный каталог программ для BeOS (в последнее время и для Haiku).
          • -
        • HaikuPorts библиотеки, необходимые для портирования приложений.
          • -
        • OsDrawer хранилище для разрабатываемых приложений с открытым исходным кодом для BeOS и Haiku.
          • +
        • HaikuPorts - библиотеки, необходимые для портирования приложений.
          • +
        • OsDrawer - хранилище для разрабатываемых приложений с открытым исходным кодом для BeOS и Haiku.

        Также существуют так называемые дополнительные пакеты (Optional Packages), которые используются при сборке Haiku. Они не предназначены для скачивания и установки конечными пользователями, однако имеется сервисный скрипт, installoptionalpackage, которым можно воспользоваться пока менеджер пакетов для Haiku находится в разработке. Он позволит вам установить большинство доступных дополнительных пакетов.
        -Для этого нужно выполнить команду в терминале:

        -

        installoptionalpackage -l - список всех доступных пакетов
        -installoptionalpackage -a {packagename} - загрузит и добавит пакет в вашу систему.
        -installoptionalpackage -a "{packagename} {packagename}" - установит несколько пакетов сразу, кавычки необходимы.

        +Для этого нужно выполнить команду в терминале: +installoptionalpackage -h описывает как им пользоваться.

        + +

        +index +Wifi in Haiku

        +

        Wifi does work to some extend. At the moment you can only log into unprotected 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 in our Wifi page (also online).

        index Знакомство с интерфейсом программирования приложений (API)

        Так как Haiku повторяет BeOS R5, то и всё, что касается API у них схоже (с некоторыми исключениями), потому документация в BeBook всё ещё актуальна. Благодаря компании ACCESS, которой принадлежат права на интеллектуальную собственность Be Inc., нам позволено распространять BeBook.

        -

        Существуют и другие ресурсы, которые должны помочь вам начать изучение:

        +

        Существуют и другие ресурсы, которые должны помочь Вам начать изучение:

        index Желаете пообщаться?

        -

        Вы можете связаться с разработчиками и другими пользователями, присоединившись к обсуждению на IRC каналах, нашем форуме или в списках рассылки. Когда множество людей обсуждают что-то вместе, то необходимо соблюдать некоторые правила для сохранения эффективности общения. Пожалуйста, соблюдайте этикет списков рассылки.

        +

        Вы можете связаться с разработчиками и другими пользователями, присоединившись к обсуждению на IRC каналах, нашем форуме или в списках рассылки. Когда множество людей обсуждают что-то вместе, то необходимо соблюдать некоторые правила для сохранения эффективности общения. Пожалуйста, придерживайтесь этикета списков рассылки.

        diff --git a/docs/welcome/welcome_sv_SE.html b/docs/welcome/welcome_sv_SE.html deleted file mode 100644 index 4be39af7f2..0000000000 --- a/docs/welcome/welcome_sv_SE.html +++ /dev/null @@ -1,127 +0,0 @@ - - - - - - - - Welcome to Haiku! - - - - - - -
        -
        - - -  -
        -
        - -
        -
        - -

        -Welcome to Haiku!

        -

        Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this alpha release 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.

        - -

        -index -Beware of Bugs

        -

        We were working very hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.

        -
        We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.
        - -

        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.

        - - -

        -index -Getting to know the system

        -

        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:

        - - -

        -index -Installing more software

        -

        Because of our binary and source compatibility, many BeOS applications run on Haiku. After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.

        - -

        Popular software repositories are:

        - - -

        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. However, a utility script is provided, installoptionalpackage. 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.
        -You'll have to run a command in Terminal:

        -

        installoptionalpackage -l - lists all available packages.
        -installoptionalpackage -a {packagename} - will download and add the package to your system.
        -installoptionalpackage -a "{packagename} {packagename}" - will install several at once. The quotes are indeed necessary.

        - -

        -index -Getting to know the API

        -

        Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the BeBook is still a valid resource. Thanks to ACCESS, who own the rights to former Be Inc. property, we are allowed to provide a copy of the BeBook.

        - -

        There are additional resources that should help you getting started:

        - - -

        -index -Getting in contact

        -

        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 Mailing List Etiquette.

        - - -
        -
        - -
        -
        -  -
        -
        - - - diff --git a/docs/welcome/welcome_uk.html b/docs/welcome/welcome_uk.html index 596f04dd74..b17f43a34a 100644 --- a/docs/welcome/welcome_uk.html +++ b/docs/welcome/welcome_uk.html @@ -31,11 +31,8 @@
      • Українська
      • Français
      • Deutsch
        • -
      • Italiano
      • Русский
      • Español
        • -
      • Svensk
        • -
      • 日本語
      • English
      @@ -48,12 +45,12 @@

      Вітаємо в Haiku!

      -

      Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this alpha release 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.

      +

      Thank you very much for checking out Haiku! This is our second 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 alpha release 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.

      index Beware of Bugs

      -

      We were working very hard to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.

      +

      We have been working hard to fix all possible to fix all possibly show stopping bugs, however, being an alpha release, there are bound to be plenty left undiscovered.

      We discourage using alpha versions as a production system. Your data could very well be altered, mangled or downright destroyed.

      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.

      @@ -74,46 +71,48 @@

      index Installing more software

      -

      Because of our binary and source compatibility, many BeOS applications run on Haiku. After downloading a package, simply unzip it (double clicking opens Expander) to /boot/apps/ and start the application from there.

      +

      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 Expander) to /boot/apps/ and start the application from there.

      Popular software repositories are:

      • Haikuware
      • BeBits
        • -
      • HaikuPorts maintains patches for ported software
        • -
      • OsDrawer hosts native BeOS and Haiku open source software projects
        • +
      • HaikuPorts - maintains patches for ported software
        • +
      • OsDrawer - hosts native BeOS and Haiku open source software projects
      -

      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. However, a utility script is provided, installoptionalpackage. 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.
      -You'll have to run a command in Terminal:

      -

      installoptionalpackage -l - lists all available packages.
      -installoptionalpackage -a {packagename} - will download and add the package to your system.
      -installoptionalpackage -a "{packagename} {packagename}" - will install several at once. The quotes are indeed necessary.

      +

      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, installoptionalpackage. 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.
      +You'll have to run a command in Terminal: installoptionalpackage -h explains its usage.

      + +

      +index +Wifi in Haiku

      +

      Wifi does work to some extend. At the moment you can only log into unprotected 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 in our Wifi page (also online).

      index Getting to know the API

      -

      Since Haiku is a reimplementation, the API is still the same as for BeOS R5 (with some additions). Therefore the documentation in the BeBook is still a valid resource. Thanks to ACCESS, who own the rights to former Be Inc. property, we are allowed to provide a copy of the BeBook.

      +

      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.

      There are additional resources that should help you getting started:

      index Getting in contact

      -

      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 Mailing List Etiquette.

      +

      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 Mailing List Etiquette.