From 4c5f6f864d34f956515c883a7235f4cebf28cf8b Mon Sep 17 00:00:00 2001 From: Joachim Seemer Date: Wed, 11 Aug 2010 17:56:45 +0000 Subject: [PATCH] Update of user guide and welcome page and their translations. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@38032 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- userguide/de/applications/magnify.html | 2 +- userguide/de/applications/textsearch.html | 42 +++--- userguide/de/gui.html | 10 +- userguide/de/keyboard-shortcuts.html | 6 +- userguide/de/preferences/e-mail.html | 8 +- userguide/de/queries.html | 10 +- userguide/de/tracker.html | 8 +- userguide/en/applications/textsearch.html | 6 +- userguide/en/preferences/e-mail.html | 2 +- userguide/en/queries.html | 2 +- userguide/en/tracker.html | 2 +- userguide/es/applications/textsearch.html | 6 +- userguide/es/preferences/e-mail.html | 14 +- userguide/es/queries.html | 10 +- userguide/es/tracker.html | 14 +- userguide/fr/applications/drivesetup.html | 4 +- userguide/fr/applications/magnify.html | 8 +- userguide/fr/applications/textsearch.html | 45 +++--- userguide/fr/gui.html | 14 +- userguide/fr/keyboard-shortcuts.html | 10 +- userguide/fr/preferences/e-mail.html | 6 +- userguide/fr/queries.html | 10 +- userguide/fr/tracker.html | 10 +- userguide/it/applications/textsearch.html | 10 +- userguide/it/desktop-applets/workspaces.html | 4 +- userguide/it/preferences/appearance.html | 9 +- userguide/it/preferences/backgrounds.html | 3 +- userguide/it/preferences/deskbar.html | 3 +- userguide/it/preferences/e-mail.html | 2 +- userguide/it/queries.html | 2 +- userguide/it/tracker.html | 2 +- userguide/jp/applications/bepdf.html | 13 +- userguide/jp/applications/pe.html | 6 +- userguide/jp/applications/textsearch.html | 10 +- userguide/jp/applications/wonderbrush.html | 6 +- userguide/jp/bash-scripting.html | 45 +++--- userguide/jp/preferences/e-mail.html | 2 +- userguide/jp/queries.html | 2 +- userguide/jp/tracker.html | 2 +- userguide/pt_PT/applications/textsearch.html | 6 +- userguide/pt_PT/preferences/deskbar.html | 5 +- userguide/pt_PT/preferences/e-mail.html | 2 +- userguide/pt_PT/queries.html | 2 +- userguide/pt_PT/tracker.html | 2 +- userguide/ru/applications/textsearch.html | 6 +- userguide/ru/preferences/e-mail.html | 10 +- userguide/ru/queries.html | 10 +- userguide/ru/tracker.html | 14 +- userguide/sv_SE/applications/textsearch.html | 6 +- userguide/sv_SE/preferences/e-mail.html | 2 +- userguide/sv_SE/queries.html | 2 +- userguide/sv_SE/tracker.html | 6 +- userguide/uk/applications/textsearch.html | 6 +- userguide/uk/preferences/e-mail.html | 6 +- userguide/uk/queries.html | 2 +- userguide/uk/tracker.html | 2 +- userguide/zh_CN/applications/installer.html | 12 +- userguide/zh_CN/applications/magnify.html | 60 ++++---- userguide/zh_CN/applications/pe.html | 17 +-- userguide/zh_CN/applications/people.html | 25 ++-- userguide/zh_CN/applications/textsearch.html | 40 +++--- userguide/zh_CN/contents.html | 8 +- .../zh_CN/desktop-applets/launchbox.html | 55 ++++---- userguide/zh_CN/filetypes.html | 57 ++++---- userguide/zh_CN/gui.html | 46 +++---- userguide/zh_CN/keyboard-shortcuts.html | 14 +- userguide/zh_CN/preferences/appearance.html | 12 +- .../zh_CN/preferences/datatranslations.html | 61 ++++---- userguide/zh_CN/preferences/e-mail.html | 24 ++-- userguide/zh_CN/preferences/fonts.html | 12 +- userguide/zh_CN/preferences/keyboard.html | 12 +- userguide/zh_CN/preferences/keymap.html | 56 ++++---- userguide/zh_CN/preferences/mouse.html | 31 ++--- userguide/zh_CN/preferences/network.html | 19 ++- userguide/zh_CN/preferences/touchpad.html | 10 +- userguide/zh_CN/preferences/tracker.html | 21 +-- .../zh_CN/preferences/virtualmemory.html | 8 +- userguide/zh_CN/queries.html | 26 ++-- userguide/zh_CN/tracker.html | 39 +++--- .../zh_CN/workshop-filetypes+attributes.html | 14 +- welcome/de/bugreports.html | 130 +++++++++++++----- welcome/en/bugreports.html | 109 +++++++++++---- welcome/es/bugreports.html | 112 +++++++++++---- welcome/fr/bugreports.html | 120 ++++++++++++---- welcome/it/bugreports.html | 109 +++++++++++---- welcome/jp/bugreports.html | 109 +++++++++++---- welcome/pt_PT/bugreports.html | 109 +++++++++++---- welcome/ru/bugreports.html | 112 +++++++++++---- welcome/sv_SE/bugreports.html | 109 +++++++++++---- welcome/uk/bugreports.html | 109 +++++++++++---- welcome/zh_CN/bugreports.html | 112 +++++++++++---- 91 files changed, 1541 insertions(+), 837 deletions(-) diff --git a/userguide/de/applications/magnify.html b/userguide/de/applications/magnify.html index 677f6db9..ba40fb19 100644 --- a/userguide/de/applications/magnify.html +++ b/userguide/de/applications/magnify.html @@ -70,7 +70,7 @@ Das jeweils aktivierte, durch ein X markierte der beiden kann mit Save ImageALT S Die aktuelle Darstellung wird als "Resource"-Datei gespeichert. Copy ImageALT C Die aktuelle Darstellung wird in die Ablage kopiert. -Hide/Show InfoALT T Die Informationen im Programmfenster oben und unten werden ein/ausgeblendet. +Hide/Show InfoALT T Die Informationen im Programmfenster oben und unten werden ein/ausgeblendet. Add a CrosshairALT H Fügt ein von maximal zwei blauen Fadenkreuzen hinzu. Remove a CrosshairALT SHIFT H Entfernt das zuletzt hinzugefügte blaue Fadenkreuz. Hide/Show GridALT G Hier kann das angezeigte Gitternetz ein/ausgeschaltet werden. diff --git a/userguide/de/applications/textsearch.html b/userguide/de/applications/textsearch.html index ab294fb6..beb19359 100644 --- a/userguide/de/applications/textsearch.html +++ b/userguide/de/applications/textsearch.html @@ -49,40 +49,38 @@
-
The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.

textsearch-icon_64.pngTextSearch

- +
Deskbar:No entry, normally launched via Tracker Add-on
Deskbar:Kein Eintrag; wird normalerweise über das Tracker Add-on gestartet.
Ort:/boot/system/apps/TextSearch
Einstellungen:~/config/settings/TextSearch


-

TextSearch looks for a string in text files. Typically it is invoked from Tracker's Add-on context menu on the selection of files or folders you want to search.

+

TextSearch sucht nach Zeichenfolgen in Textdateien. Normalerweise wählt man dazu die Dateien oder Ordner aus, die durchsucht werden sollen und wählt TextSearch aus Trackers Add-on Kontextmenü.

textsearch.png -

You enter a search string in the text box on top and hit RETURN or click Search to start. If Show lines is checked, the hits are automatically expanded to show the lines of the file containing the search string.

+

Im Textfeld oben wird der Suchbegriff eingegeben und die Suche per RETURN oder Klick auf Search gestartet. Ist die Show lines Option aktiviert, werden die Suchergebnisse automatisch aufgeklappt und zeigen dann die Zeilennummern der Fundstellen in den Dateien, die den Suchbegriff enthalten.

-

Only a few words on some of the otherwise self-explaining menu items:

+

Nur ein paar kurze Erläuterungen zu den ansonsten sich selbst erklärenden Menüpunkten:

- - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + +

File menu

New windowALT N Opens a new window where you can enter another string and search through the same files/folders. -
Set target...ALT FLets you choose a new set of files and folders to search through.

Action menu

Trim selectionALT T Removes all entries form the list that are not currently selected.
Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.
Open files in TrackerALT KOpens the location of the currently selected files in Tracker.
Copy text to clipboardALT CCopies the current selection to the clipboard.

Settings menu

Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.
Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions.
Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

History menu

Contains recently used search strings.

Encoding menu

Lets you choose different character encodings if needed.

File Menü

New windowALT N Öffnet ein neues Fenster, um dieselben Dateien/Ordner nach einem neuen Begriff zu durchsuchen.
Set target...ALT FZum Ändern der Dateien oder Ordner, die durchsucht werden sollen.

Action Menü

Trim selectionALT T Entfernt alle Suchergebnisse aus der Liste, die nicht ausgewählt sind.
Open selectionALT OÖffnet die ausgewählten Dateien mit ihrer bevorzugten Anwendung (wie bei einem Doppelklick). Falls es sich um einen Texteditor handelt, der das unterstützt (wie Pe), lässt sich auch genau zu der Zeile der Fundstelle springen.
Open files in TrackerALT KÖffnet die Speicherorte der gerade ausgewählten Dateien im Tracker.
Copy text to clipboardALT BKopiert die momentane Auswahl in die Ablage.

Settings Menü

Skip folders starting with a dot Nützlich wenn man sich in einer Unix-Umgebung bewegt, in der Verwaltungsdateien oft in ".Ordner" versteckt werden. Sourcecode Versionierungssysteme wie SVN und CVS sind Beispiele für Anwendungen, die das so machen und auch unter Haiku weit verbreitet sind.
Escape search text TextSearch benutzt das Konsolenprogramm grep. Dazu müssen spezielle Zeichen wie '"*\$?! und Leerzeichen mit einem \ "escaped" werden. Deaktiviert man diese Option, heißt das, dass man das von Hand machen muss, im Gegenzug erhält man allerdings die mächtigen Möglichkeiten von Regulären Ausdrücken.
Text files only TextSearch ist momentan nur zur Suche von Begriffen in reinen Textdateien sinnvoll zu gebrauchen. Deaktiviert man diese Option, werden alle Arten von Dateien durchsucht.

History Menü

Enthält kürzlich benutzte Suchbegriffe.

Encoding Menü

Erlaubt bei Bedarf verschiedene Zeichencodierungen.
diff --git a/userguide/de/gui.html b/userguide/de/gui.html index a5fd5c63..35cd11e6 100644 --- a/userguide/de/gui.html +++ b/userguide/de/gui.html @@ -22,7 +22,7 @@
@@ -41,8 +41,8 @@
  • English
    • - « Dateisystem Layout -:: Inhalt + « Filesystem layout +:: Contents :: Workspaces »
    @@ -113,8 +113,8 @@ Ein Rechtsklick auf ein Replikanten-Symbol öffnet ein Kontextmenü, um das
    - « Dateisystem Layout -:: Inhalt + « Filesystem layout +:: Contents :: Workspaces »
    diff --git a/userguide/de/keyboard-shortcuts.html b/userguide/de/keyboard-shortcuts.html index fa268881..80d8a0c8 100644 --- a/userguide/de/keyboard-shortcuts.html +++ b/userguide/de/keyboard-shortcuts.html @@ -24,7 +24,7 @@
    @@ -44,7 +44,7 @@ « Tracker Add-Ons -:: Inhalt +:: Contents :: Deskbar »
    @@ -133,7 +133,7 @@ Die eingegebenen Zeichen erscheinen unten links, wo ansonsten die Anzahl der Obj
    « Tracker Add-Ons -:: Inhalt +:: Contents :: Deskbar »
    diff --git a/userguide/de/preferences/e-mail.html b/userguide/de/preferences/e-mail.html index ffe8655c..dacc1183 100644 --- a/userguide/de/preferences/e-mail.html +++ b/userguide/de/preferences/e-mail.html @@ -23,7 +23,7 @@
    @@ -43,7 +43,7 @@ « Deskbar -:: Einstellungen +:: Preferences :: FileTypes »
    @@ -153,7 +153,7 @@ Im ersten Textfeld gibt man die zu prüfende Kopfzeile an. Diese Werte möglich: Spam/Genuine Estimate der errechnete Wert des Spam-Filters für diese Mail; dieser Wert wird in wissenschaftlicher Schreibweise notiert, so steht zum Beispiel 1.065e-12 für 1,065/(10^12), also für "1,065 dividiert durch 10 hoch 12" - was ausgeschrieben 0,000000000001065 ergibt -

    Das zweite Textfeld ist für das Suchmuster. Hier können "reguläre Ausdrücke" - sogenannte Reguläre Ausdrücke (reg_ex) - verwendet werden. Damit erreicht man zwar eine sehr hohe Flexibilität bei den Suchmustern, unglücklicherweise sind reguläre Ausdrücke aber nicht leicht anzuwenden. Ein wenig Einarbeitung ist es aber wert und einfache reg_ex sind auch nicht zu schwer.

    +

    Das zweite Textfeld ist für das Suchmuster. Hier können "reguläre Ausdrücke" - sogenannte Reguläre Ausdrücke - verwendet werden. Damit erreicht man zwar eine sehr hohe Flexibilität bei den Suchmustern, unglücklicherweise sind reguläre Ausdrücke aber nicht leicht anzuwenden. Ein wenig Einarbeitung ist es aber wert und einfache reg_ex sind auch nicht zu schwer.

    Über das Menü darunter lässt sich eine Aktion ausführen, wenn das Suchmuster erkannt wurde. So kann der Status der Mail verändert, oder die Mail an sich verschoben oder direkt gelöscht werden.

    @@ -182,7 +182,7 @@ Wenn man seine Netzwerkverbindung über eine Wählverbindung aufbaut, ist es rat
    « Deskbar -:: Einstellungen +:: Preferences :: FileTypes »
    diff --git a/userguide/de/queries.html b/userguide/de/queries.html index f7b7dfc6..adcb5dd0 100644 --- a/userguide/de/queries.html +++ b/userguide/de/queries.html @@ -23,7 +23,7 @@
    @@ -43,7 +43,7 @@ « Index -:: Inhalt +:: Contents :: Workshop »
    @@ -124,13 +124,13 @@ So lässt sich die Trefferzahl sehr gut einschränken.

    • Die Suchformel lässt sich in eine E-Mail oder Forumbeitrag kopieren oder im IRC erwähnen, damit sie von anderen benutzt oder verbessert werden kann.

    • Mit dieser Methode lassen sich Queries entspannt im Attribute Modus konstruieren. Anschließend wechselt man in den Formula Modus, um die Formel der so erstellten Query im Terminal oder einem Skript zu nutzen.

      • -

    • Eine Query lässt sich so fein anpassen, indem man zusätzliche Klammern setzt, in bestimmten Abschnitten auf Groß- und Kleinschreibung achtet oder einige logische Verknüpfungen verneint durch Ändern von "==" zu "!=" für ein NOT AND. Dazu benötigt man nur ein gewisses Basiswissen über Reguläre Ausdrücke und ein klein wenig Programmier-Kenntnisse.

      • +

    • Eine Query lässt sich so fein anpassen, indem man zusätzliche Klammern setzt, in bestimmten Abschnitten auf Groß- und Kleinschreibung achtet oder einige logische Verknüpfungen verneint durch Ändern von "==" zu "!=" für ein NOT AND. Dazu benötigt man nur ein gewisses Basiswissen über Reguläre Ausdrücke und ein klein wenig Programmier-Kenntnisse.

    index Das Ergebnisfenster

    -

    Hat man die Suche gestartet, wird das FInd-Fenster durch ein Ergebnisfenster ersetzt. Hier ein Beispiel einer Suche nach "server":

    +

    Hat man die Suche gestartet, wird das Find-Fenster durch ein Ergebnisfenster ersetzt. Hier ein Beispiel einer Suche nach "server":

    result-window.png

    Außer ihrem grauen Hintergrund, unterscheidet Ergebnisfenster nichts von jedem anderen Trackerfenster. Einige Dinge gehören erwähnt:

      @@ -154,7 +154,7 @@ Mit dem Menüpunkt Save Query as Template (siehe (1) i
      « Index -:: Inhalt +:: Contents :: Workshop »
      diff --git a/userguide/de/tracker.html b/userguide/de/tracker.html index 7d6e44ac..d675e180 100644 --- a/userguide/de/tracker.html +++ b/userguide/de/tracker.html @@ -23,7 +23,7 @@
      @@ -43,7 +43,7 @@
    « Team Monitor -:: Inhalt +:: Contents :: Tracker Add-Ons » @@ -126,7 +126,7 @@ Dieses "type-ahead" filtern wird in den Trac @@ -197,7 +197,7 @@ Dieses "type-ahead" filtern wird in den Trac
    « Team Monitor -:: Inhalt +:: Contents :: Tracker Add-Ons »
    diff --git a/userguide/en/applications/textsearch.html b/userguide/en/applications/textsearch.html index 978d00d6..57ed7cf2 100644 --- a/userguide/en/applications/textsearch.html +++ b/userguide/en/applications/textsearch.html @@ -68,13 +68,13 @@ Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    -Trim selectionALT T Removes all entries form the list that are not currently selected. +Trim selectionALT T Removes all entries from the list that are not currently selected. Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found. Open files in TrackerALT KOpens the location of the currently selected files in Tracker. -Copy text to clipboardALT CCopies the current selection to the clipboard. +Copy text to clipboardALT BCopies the current selection to the clipboard.

    Settings menu

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku. -Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. +Escape search text TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings. diff --git a/userguide/en/preferences/e-mail.html b/userguide/en/preferences/e-mail.html index adcb57e4..ced2a155 100644 --- a/userguide/en/preferences/e-mail.html +++ b/userguide/en/preferences/e-mail.html @@ -150,7 +150,7 @@ With the first text field you specify which header to check against. These are a Spam/Genuine Estimate this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065. -

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    +

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.

    diff --git a/userguide/en/queries.html b/userguide/en/queries.html index 327deb60..77e31543 100644 --- a/userguide/en/queries.html +++ b/userguide/en/queries.html @@ -121,7 +121,7 @@ A good way to cut down the number of search results.

    • You could copy and paste the string into an email, forum or IRC for others to use or debug.

    • You can use this method to construct a query in Attribute mode and then switch to Formula mode, to comfortably generate a search string to use for a query in Terminal or a script.

      • -

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

      • +

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

    diff --git a/userguide/en/tracker.html b/userguide/en/tracker.html index 877bf525..c90a5801 100644 --- a/userguide/en/tracker.html +++ b/userguide/en/tracker.html @@ -123,7 +123,7 @@ This type-ahead filtering is set in the Trac diff --git a/userguide/es/applications/textsearch.html b/userguide/es/applications/textsearch.html index af9c1040..293f6535 100644 --- a/userguide/es/applications/textsearch.html +++ b/userguide/es/applications/textsearch.html @@ -71,13 +71,13 @@ Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    -Trim selectionALT T Removes all entries form the list that are not currently selected. +Trim selectionALT T Removes all entries from the list that are not currently selected. Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found. Open files in TrackerALT KOpens the location of the currently selected files in Tracker. -Copy text to clipboardALT CCopies the current selection to the clipboard. +Copy text to clipboardALT BCopies the current selection to the clipboard.

    Settings menu

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku. -Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. +Escape search text TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings. diff --git a/userguide/es/preferences/e-mail.html b/userguide/es/preferences/e-mail.html index f87cdb97..7b6caf8a 100644 --- a/userguide/es/preferences/e-mail.html +++ b/userguide/es/preferences/e-mail.html @@ -23,7 +23,7 @@
    @@ -42,9 +42,9 @@
  • English
    • - « Deskbar (Barra de Escritorio) -:: Preferencias -:: Tipos de archivo » + « Deskbar +:: Preferences +:: FileTypes »
    @@ -182,9 +182,9 @@ Si tiene una conexión de marcado, puede verificar la opción
    - « Deskbar (Barra de Escritorio) -:: Preferencias -:: Tipos de archivo » + « Deskbar +:: Preferences +:: FileTypes »
    diff --git a/userguide/es/queries.html b/userguide/es/queries.html index 1c4f14b9..58e2b93a 100644 --- a/userguide/es/queries.html +++ b/userguide/es/queries.html @@ -22,7 +22,7 @@
    @@ -42,8 +42,8 @@ « Índice -:: Contenidos -:: Taller » +:: Contents +:: Workshop »
    @@ -146,8 +146,8 @@ Usando el elemento del menú Save Query as Template (G
    « Índice -:: Contenidos -:: Taller » +:: Contents +:: Workshop »
    diff --git a/userguide/es/tracker.html b/userguide/es/tracker.html index 35c28149..dc008c31 100644 --- a/userguide/es/tracker.html +++ b/userguide/es/tracker.html @@ -22,7 +22,7 @@
    @@ -41,9 +41,9 @@
  • English
    • - « Monitor de actividad (Team Monitor) -:: Contenidos -:: Agregados de Tracker » + « Team Monitor +:: Contents +:: Tracker Add-Ons »
    @@ -194,9 +194,9 @@ Este filtrado de type-ahead se selecciona en las
    - « Monitor de actividad (Team Monitor) -:: Contenidos -:: Agregados de Tracker » + « Team Monitor +:: Contents +:: Tracker Add-Ons »
    diff --git a/userguide/fr/applications/drivesetup.html b/userguide/fr/applications/drivesetup.html index 1cb5f89b..adc3d8f6 100644 --- a/userguide/fr/applications/drivesetup.html +++ b/userguide/fr/applications/drivesetup.html @@ -24,7 +24,7 @@
    @@ -59,7 +59,7 @@ Réglages :~/config/settings/DriveSetup


    -

    DriveSetup est un outils pour créer, supprimer et initialiser des partitions. Pour le moment, il ne peu pas redimensionner ou déplacer une partition existante, de sorte que vous aurez besoin soit d'un volume avec un espace non partitionné (peut-être un disque USB externe ou un autre disque dur) ou modifier la configuration avec un outil comme GParted LiveCD pour fournir l'espace pour une nouvelle partition.

    +

    DriveSetup est un outils pour créer, supprimer et initialiser des partitions. Pour le moment, il ne peut pas redimensionner ou déplacer une partition existante, de sorte que vous aurez besoin soit d'un volume avec un espace non partitionné (peut-être un disque USB externe ou un autre disque dur) ou modifier la configuration avec un outil comme GParted LiveCD pour fournir l'espace pour une nouvelle partition.

    drivesetup.png

    Au sommet se trouve une représentation graphique de toutes les partitions à l'intérieur du lecteur choisi dans la liste en dessous. Vous pouvez avoir jusqu'à 4 partitions primaires au maximum, chacune d'entre elles pouvant contenir un certain nombre de partitions logiques. diff --git a/userguide/fr/applications/magnify.html b/userguide/fr/applications/magnify.html index adf9fc2c..ff936e7a 100644 --- a/userguide/fr/applications/magnify.html +++ b/userguide/fr/applications/magnify.html @@ -22,7 +22,7 @@

    @@ -71,12 +71,12 @@ elles peuvent aussi être déplacées avec les touches ← - - + + - + diff --git a/userguide/fr/applications/textsearch.html b/userguide/fr/applications/textsearch.html index 451ea1f7..9b2b9cd6 100644 --- a/userguide/fr/applications/textsearch.html +++ b/userguide/fr/applications/textsearch.html @@ -49,40 +49,41 @@
    -
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.

    textsearch-icon_64.pngTextSearch

    Save ImageALT S Sauvegarde la visualisation en cours dans un fichier de ressource
    Copy ImageALT C Copie la visualisation en cours dans le presse papier.
    Hide/Show InfoALT T Bascule l'affichage de toutes les informations complémentaires.
    Copy ImageCMD C Copie la visualisation en cours dans le presse papier.
    Hide/Show InfoCMD T Bascule l'affichage de toutes les informations complémentaires.
    Add a CrosshairALT H Ajoute une croix que vous pouvez déplacer.
    Remove a CrosshairALT MAJ H Retire la dernière croix que vous avez ajoutée.
    Hide/Show GridALT G Affiche la grille en surimpression.
    Freeze/Unfreeze imageALT F Arrête/reprend la mise à jour de la zone d'agrandissement.
    Freeze/Unfreeze imageCMD F Arrête/reprend la mise à jour de la zone d'agrandissement.
    Stick CoordinatesALT I Continue de mettre à jour la zone agrandie, mais sans suivre plus longtemps le pointeur de la souris.
    Make SquareALT / Revient à un écran carré après le redimensionnement de la fenêtre.
    Decrease Window SizeALT - Rétrécit la zone la zone prise en compte autour du pointeur de la souris.
    - +
    Deskbar :No entry, normally launched via Tracker Add-on
    Deskbar :Pas d'entrée, normalement vous y accédez via les Extensions du Tracker
    Localisation :/boot/system/apps/TextSearch
    Réglages :~/config/settings/TextSearch


    -

    TextSearch looks for a string in text files. Typically it is invoked from Tracker's Add-on context menu on the selection of files or folders you want to search.

    +

    TextSearch recherche une chaîne de caractères dans des fichiers texte. En général, il est appelé à partir du menu contextuel Extensions du Tracker sur la selection de fichiers ou dossiers que vous souhaitez examiner.

    textsearch.png -

    You enter a search string in the text box on top and hit RETURN or click Search to start. If Show lines is checked, the hits are automatically expanded to show the lines of the file containing the search string.

    +

    Entrez la chaîne à rechercher dans la zone de texte en haut, puis pressez ENTRÉE ou cliquez sur Search(Rechercher) pour démarrer la recherche. Si Show lines(Afficher les lignes) est coché, les résultats sont automatiquement développés pour afficher les lignes du fichier contenant la chaîne de recherche.

    -

    Only a few words on some of the otherwise self-explaining menu items:

    +

    Juste quelques mots sur les éléments de menu les moins évidents :

    - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + +

    File menu

    New windowALT N Opens a new window where you can enter another string and search through the same files/folders. -
    Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    Trim selectionALT T Removes all entries form the list that are not currently selected.
    Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.
    Open files in TrackerALT KOpens the location of the currently selected files in Tracker.
    Copy text to clipboardALT CCopies the current selection to the clipboard.

    Settings menu

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.
    Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions.
    Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings.

    Encoding menu

    Lets you choose different character encodings if needed.

    Le menu Fichier (File)

    New windowCMD N Ouvre une nouvelle fenêtre où vous pouvez entrer une autre chaîne à rechercher dans les mêmes fichiers ou dossiers.
    Set target...CMD FVous permet de choisir un nouvel ensemble de fichiers et de dossiers à examiner.

    Le menu Action

    Trim selectionCMD T Supprime toutes les entrées de la liste qui ne sont pas actuellement sélectionnées.
    Open selectionCMD OOuvre les fichiers sélectionnés avec leurs applications préférées (comme avec un double-clic). Si c'est un éditeur de texte qui le supporte (comme Pe), vous pouvez passer à la ligne exacte où la chaîne a été trouvé.
    Open files in TrackerCMD KOuvre l'emplacement des fichiers sélectionnés dans Tracker.
    Copy text to clipboardCMD CCopie la sélection actuelle dans le presse papier.

    Le menu Réglage (Settings)

    Skip folders starting with a dot C'est utile lorsque vous travaillez dans un environnement « à la Unix », où, souvent, les fichiers d'administration sont cachés à l'intérieur de « .dossiers/ ». Par exemples, les systèmes de gestion de versions de sources comme SVN et CVS, qui sont largement utilisés dans le Haiku, utilisent cela.
    Escape search text TextSearch utilise l'outil en ligne de commande grep. +Pour ce faire, les caractères spéciaux comme '"*\$?! et espace, doivent +être précédés du caractère d'échappement \. +Désactiver ce paramètre signifie que vous devez le faire vous-même, mais en échange, vous bénéficierez de la puissance des expressions régulières.
    Text files only TextSearch n'est actuellement utile que pour trouver des chaînes dans les fichiers de texte brut. En désactivant ce paramètre, tous les types de fichiers seront examinées.

    Le menu Historique (History)

    Contient les chaînes recherchées récemment.

    Le menu Encodage (Encoding)

    Vous permet de choisir un jeu de caractères différents, si nécessaire.
    diff --git a/userguide/fr/gui.html b/userguide/fr/gui.html index aa6ee850..1c31dc91 100644 --- a/userguide/fr/gui.html +++ b/userguide/fr/gui.html @@ -22,7 +22,7 @@
    @@ -41,9 +41,9 @@
  • English
    • - « Structure du système de fichiers -:: Sommaire -:: Espaces de travail » + « Filesystem layout +:: Contents +:: Workspaces »
    @@ -116,9 +116,9 @@ Un clic droit sur la poignée d'un Réplicant ouvrira un menu contextuel, où
    - « Structure du système de fichiers -:: Sommaire -:: Espaces de travail » + « Filesystem layout +:: Contents +:: Workspaces »
    diff --git a/userguide/fr/keyboard-shortcuts.html b/userguide/fr/keyboard-shortcuts.html index 10551ecc..97e35632 100644 --- a/userguide/fr/keyboard-shortcuts.html +++ b/userguide/fr/keyboard-shortcuts.html @@ -23,7 +23,7 @@
    @@ -42,8 +42,8 @@
  • English
    • - « Extensions du Tracker -:: Sommaire + « Tracker Add-Ons +:: Contents :: Deskbar »
    @@ -130,8 +130,8 @@ Les lettres que vous tapez apparaîtront en bas à gauche de la fenêtre, là ou
    - « Extensions du Tracker -:: Sommaire + « Tracker Add-Ons +:: Contents :: Deskbar »
    diff --git a/userguide/fr/preferences/e-mail.html b/userguide/fr/preferences/e-mail.html index cc8671ef..f12a8679 100644 --- a/userguide/fr/preferences/e-mail.html +++ b/userguide/fr/preferences/e-mail.html @@ -23,7 +23,7 @@
    @@ -43,7 +43,7 @@ « Deskbar -:: Préférences +:: Preferences :: FileTypes »
    @@ -188,7 +188,7 @@ Tous les dossiers ou requêtes placés dans ce dossier apparaîtront dans le men
    « Deskbar -:: Préférences +:: Preferences :: FileTypes »
    diff --git a/userguide/fr/queries.html b/userguide/fr/queries.html index 08160fd9..1d658cd9 100644 --- a/userguide/fr/queries.html +++ b/userguide/fr/queries.html @@ -23,7 +23,7 @@
    @@ -43,8 +43,8 @@ « Index -:: Sommaire -:: Atelier » +:: Contents +:: Workshop »
    @@ -152,8 +152,8 @@ En utilisant la méthode Save Query as Template du men
    « Index -:: Sommaire -:: Atelier » +:: Contents +:: Workshop »
    diff --git a/userguide/fr/tracker.html b/userguide/fr/tracker.html index d20d4ca3..1e312f58 100644 --- a/userguide/fr/tracker.html +++ b/userguide/fr/tracker.html @@ -23,7 +23,7 @@
    @@ -43,8 +43,8 @@ « Team Monitor -:: Sommaire -:: Extensions du Tracker » +:: Contents +:: Tracker Add-Ons »
    @@ -199,8 +199,8 @@ Si vous démarrez plusieurs tâches, un indicateur apparaît pour chacune d’en
    « Team Monitor -:: Sommaire -:: Extensions du Tracker » +:: Contents +:: Tracker Add-Ons »
    diff --git a/userguide/it/applications/textsearch.html b/userguide/it/applications/textsearch.html index 469aa64d..b078af78 100644 --- a/userguide/it/applications/textsearch.html +++ b/userguide/it/applications/textsearch.html @@ -20,7 +20,7 @@
    @@ -47,7 +47,7 @@
    -
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    +
    La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.

    textsearch-icon_64.pngTextSearch

    @@ -69,13 +69,13 @@ - + - + - + diff --git a/userguide/it/desktop-applets/workspaces.html b/userguide/it/desktop-applets/workspaces.html index e8d1743d..5a109135 100644 --- a/userguide/it/desktop-applets/workspaces.html +++ b/userguide/it/desktop-applets/workspaces.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * MichaelPeppers * --> @@ -72,7 +74,7 @@

    The Workspaces applet provides some additional functionality when clicking on a window while holding certain modifier keys:

    Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    Trim selectionALT T Removes all entries form the list that are not currently selected.
    Trim selectionALT T Removes all entries from the list that are not currently selected.
    Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.
    Open files in TrackerALT KOpens the location of the currently selected files in Tracker.
    Copy text to clipboardALT CCopies the current selection to the clipboard.
    Copy text to clipboardALT BCopies the current selection to the clipboard.

    Settings menu

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.
    Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions.
    Escape search text TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions.
    Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings.
    - +
    CTRLBrings the window to the front.
    CTRL SHIFTMinimizes the window.
    CTRL SHIFTMinimizza la finestra.
    OPTSends the window to the back.
    diff --git a/userguide/it/preferences/appearance.html b/userguide/it/preferences/appearance.html index 39acef8f..ddbf755d 100644 --- a/userguide/it/preferences/appearance.html +++ b/userguide/it/preferences/appearance.html @@ -11,6 +11,7 @@ * Humdinger * Translators: * Giuseppe Gargaro + * MichaelPeppers * --> @@ -56,13 +57,13 @@ Posizione:/boot/system/preferences/Appearance Impostazioni:~/config/settings/system/app_server/appearance -

    Le preferenze Appearance permettono di cambiare alcuni aspetti visivi di Haiku .

    +

    Le preferenze in Appearance permettono di cambiare alcuni aspetti visivi di Haiku .

    index -Colors

    +Colori appearance-colors.png -

    In the first tab, Colors, you can change the colors of different parts of the user interface. The color well accepts drag&drops from other programs, letting you drag colors over from e.g. WonderBrush, Icon-O-Matic or the Backgrounds panel.

    +

    Nella pima tab, Colori, puoi cambiare i colori di diverse parti dell'interfaccia utente. Il colore accetta anche drag&drop da altri programmi, permettendo di prendere colori da, per esempio, WonderBrush, Icon-O-Matic o dal pannello di Backgrounds.

    index @@ -97,7 +98,7 @@ Antialiasing type

    appearance-glyph-on.png
    Grayscale, Hinting: onappearance-glyph-on-subpixel.png
    LCD subpixel, Hinting: on


    -

    At the bottom of the panel are two buttons:

    +

    Nel fondo del pannello ci sono due pulsanti:

    diff --git a/userguide/it/preferences/backgrounds.html b/userguide/it/preferences/backgrounds.html index 1b7af293..324b4479 100644 --- a/userguide/it/preferences/backgrounds.html +++ b/userguide/it/preferences/backgrounds.html @@ -11,6 +11,7 @@ * Humdinger * Translators: * Andrea Bernardi + * MichaelPeppers * --> @@ -74,7 +75,7 @@

    Whether an icon label's actual text is black or white depends on the setting of the color picker. A dark color sets the text to white, a light color to black. So, if you assign a very bright image to the background, you should also set the color picker to a bright color in order to have icon labels readable in black. (Or use the outline option above.)
    The selected color is also reflected in the Workspaces applet, which ignores images as backgrounds.

    Defaults resets everything to default values.
    Annulla brings back the settings that were active when you started the Appearance preferences.
    - +
    Annulla Ripristina le impostazioni iniziali all'appertura della preferences Backgrounds
    Annulla Ripristina le impostazioni presenti all'apertura di Backgrounds.
    Applica Applica i tuoi cambiamenti.
    diff --git a/userguide/it/preferences/deskbar.html b/userguide/it/preferences/deskbar.html index 2dd0691f..b67ef9ad 100644 --- a/userguide/it/preferences/deskbar.html +++ b/userguide/it/preferences/deskbar.html @@ -49,7 +49,6 @@
    -
    La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.

    deskbar-icon_64.pngDeskbar

    @@ -59,7 +58,7 @@ ~/config/settings/Deskbar_security_code


    -

    The Deskbar preference panel is also available from the Deskbar. Its settings are discussed in the topic on Deskbar.

    +

    Il pannello delle preferenze del Deskbar è disponibile anche attraverso il Deskbar stesso. Le sue impostazioni sono discusse in un paragrafo apposito nella pagina del Deskbar.

    diff --git a/userguide/it/preferences/e-mail.html b/userguide/it/preferences/e-mail.html index 666d7208..69862b25 100644 --- a/userguide/it/preferences/e-mail.html +++ b/userguide/it/preferences/e-mail.html @@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a Spam/Genuine Estimate this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065. -

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    +

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.

    diff --git a/userguide/it/queries.html b/userguide/it/queries.html index 490679ed..50b39076 100644 --- a/userguide/it/queries.html +++ b/userguide/it/queries.html @@ -122,7 +122,7 @@ A good way to cut down the number of search results.

    • You could copy and paste the string into an email, forum or IRC for others to use or debug.

    • You can use this method to construct a query in Attribute mode and then switch to Formula mode, to comfortably generate a search string to use for a query in Terminal or a script.

      • -

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

      • +

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

    diff --git a/userguide/it/tracker.html b/userguide/it/tracker.html index a44fcdaf..d91859b5 100644 --- a/userguide/it/tracker.html +++ b/userguide/it/tracker.html @@ -124,7 +124,7 @@ This type-ahead filtering is set in the Trac diff --git a/userguide/jp/applications/bepdf.html b/userguide/jp/applications/bepdf.html index 0f3cc795..148fe226 100644 --- a/userguide/jp/applications/bepdf.html +++ b/userguide/jp/applications/bepdf.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * log-1 * --> @@ -42,25 +44,24 @@ - アプリケーション  + Applications  ::  Pe  »

    -
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.

    bepdf-icon_64.pngBePDF

    - +
    Deskbarメニュー:Applications
    場所:/boot/apps/BePDF/BePDF
    Documentation:/boot/apps/BePDF/docs/*
    ドキュメント:/boot/apps/BePDF/docs/*
    設定ファイル:/boot/common/settings/BePDF


    -

    BePDF is a fast launching PDF viewer. Besides viewing, it supports annotating and user-defined bookmarking for unencrypted PDFs. It's fully localized for 20 languages at the moment with additional languages being easily added via text files.

    -

    Documentation is available as HTML or PDF. The latter will also open from the menu Help | Show Help....

    +

    BePDFは起動が高速なPDFビューアです。PDFを表示することに加えて、暗号化されていないPDFに注釈を加える機能や、ユーザーがブックマークを定義する機能をサポートしています。現在20カ国語について完全にローカライズされています。テキスト・ファイルを編集することで、簡単に新しい言語を追加することができます。

    +

    ドキュメントはHTML形式またはPDF形式で入手することができます。PDF形式のドキュメントは、メニューのHelp | Show Help...から開くこともできます。

    @@ -68,7 +69,7 @@
    «  ActivityMonitor  -::  アプリケーション  +::  Applications  ::  Pe  »
    diff --git a/userguide/jp/applications/pe.html b/userguide/jp/applications/pe.html index 434ce3f7..39164d43 100644 --- a/userguide/jp/applications/pe.html +++ b/userguide/jp/applications/pe.html @@ -40,7 +40,7 @@  «  BePDF  -::  アプリケーション  +::  Applications  ::  Vision  »
    @@ -53,7 +53,7 @@ - +
    Deskbarメニュー:Applications
    場所:/boot/apps/Pe/Pe
    Documentation:/boot/apps/Pe/Documentation.html
    ドキュメント:/boot/apps/Pe/Documentation.html
    設定ファイル:~/config/settings/pe/*


    @@ -66,7 +66,7 @@
     «  BePDF  -::  アプリケーション  +::  Applications  ::  Vision  »
    diff --git a/userguide/jp/applications/textsearch.html b/userguide/jp/applications/textsearch.html index 67ba8d3e..80c4a0e8 100644 --- a/userguide/jp/applications/textsearch.html +++ b/userguide/jp/applications/textsearch.html @@ -40,7 +40,7 @@  «  Terminal  -::  アプリケーション  +::  Applications  ::  TV  » @@ -69,13 +69,13 @@ Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    -Trim selectionALT T Removes all entries form the list that are not currently selected. +Trim selectionALT T Removes all entries from the list that are not currently selected. Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found. Open files in TrackerALT KOpens the location of the currently selected files in Tracker. -Copy text to clipboardALT CCopies the current selection to the clipboard. +Copy text to clipboardALT BCopies the current selection to the clipboard.

    Settings menu

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku. -Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. +Escape search text TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings. @@ -88,7 +88,7 @@
     «  Terminal  -::  アプリケーション  +::  Applications  ::  TV  »
    diff --git a/userguide/jp/applications/wonderbrush.html b/userguide/jp/applications/wonderbrush.html index 6a7c8248..62c45b0a 100644 --- a/userguide/jp/applications/wonderbrush.html +++ b/userguide/jp/applications/wonderbrush.html @@ -40,7 +40,7 @@  «  Vision  -::  アプリケーション +::  Applications @@ -52,7 +52,7 @@ - +
    Deskbarメニュー:Applications
    場所:/boot/apps/WonderBrush/WonderBrush
    Documentation:/boot/apps/WonderBrush/Documentation {language}
    ドキュメント:/boot/apps/WonderBrush/Documentation {language}
    設定ファイル:~/config/settings/WonderBrush


    @@ -65,7 +65,7 @@
    «  Vision  -::  アプリケーション +::  Applications
    --> diff --git a/userguide/jp/bash-scripting.html b/userguide/jp/bash-scripting.html index 4851148d..933641d6 100644 --- a/userguide/jp/bash-scripting.html +++ b/userguide/jp/bash-scripting.html @@ -9,12 +9,14 @@ * * Authors: * Humdinger + * Translators: + * log-1 * --> - Bash and Scripting + Bashとスクリプト化 @@ -47,50 +49,49 @@
    -
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    -

    Bash and Scripting

    +

    Bashとスクリプト化

    -

    "Scripting" is the technique of automating procedures by stringing together commands and saving it all as text files, so called "scripts". Every time you run such a script, the commands are processed one after the other just like they would if you entered them into the Terminal by hand.
    -Scripts can range from simply executing a few commands in a specific order to sophisticated pieces of code that solve complex tasks.

    +

    「スクリプト化」とは、複数のコマンドを並べて書き、「スクリプト」と呼ばれるテキスト・ファイルとして保存することにより処理を自動化する方法のことです。スクリプトを走らせる度に、あたかもTerminalでそれらコマンドを1つ1つ手で打ち込んでいるようにコマンドが実行されます。
    +スクリプトは、単に数個のコマンドをある特定の順番で実行するものから、複雑なタスクを処理するための高度なコードのかたまりまで、多岐にわたります。

    index -The Bash

    -

    Since scripts rely naturally a lot on the shell they are interpreted by, you should first familiarize yourself with the BASH that's used by Haiku. There are many resources online as it's a widely used shell. One nice document is Johan Jansson's Introduction to bash - a tutorial for bash under BeOS.

    +Bash +

    そもそもスクリプトはそれを解釈するシェルに大きく依存するため、まずはHaikuで使用されているBASHに精通する必要があります。BASHは広く使用されているシェルであるため、オンライン上に資料が豊富に存在します。すばらしいドキュメントの1つに、Johan Jansson氏のIntroduction to bash - a tutorial for bash under BeOSがあります。

    index -The Scripting Bible

    -

    After you've learned a few basics about working in the shell, it's time to slowly ease yourself into the world of scripting. Again, you'll find loads of tutorials and reference material online as well as in bookstores. A very nice introduction that's practically tailor-made for Haiku is the online available Scripting Chapter (PDF, 900kb) of Scot Hacker's BeOS Bible.

    +スクリプト化のための必読書 +

    シェル内で作業するためのいくつかの基礎を学んだあとは、スクリプト化の世界にゆっくりと歩み出しましょう。このときも、本屋と同じくらい豊富なチュートリアルやリファレンスをオンライン上で見つけられるでしょう。Haikuにほぼピッタリの非常にすばらしい入門編に、オンラインで入手可能なScot Hacker氏によるBeOSの必読書のScripting Chapter (PDF, 900kb)があります。

    -indexScripts in Haiku

    -

    In Haiku, the system makes of course also use of scripting. Booting and shutting down are typical scripting procedures. These defined sequences can be augmented by the user with certain user scripts.
    -If they don't exist already, you'll have to create the needed files yourself. Otherwise simply add your commands where in the process you want them to be executed.

    +indexHaikuにおけるスクリプト +

    Haikuでは、当然のことながらシステムもまたスクリプト化機能を使用しています。起動とシャット・ダウンはスクリプト化された手続きの典型です。はじめから定義されたこれら手続きは、特定のユーザー・スクリプトを用いてユーザーが拡張することができます。
    +もしこれらユーザー・スクリプトがまだ存在しない場合は、手動でこれらファイルを作成する必要があります。ユーザー・スクリプトが存在する場合は、処理を実行したい場所に必要なコマンドを追加するだけで済みます。

    index -The UserBootscript

    -

    /boot/home/config/boot/UserBootscript will be executed after the system has finished its boot process. For example, you could launch a number of programs that would then be automatically started on every boot up:

    -
    # Start LaunchBox
+UserBootscript
+
    システムの起動プロセスが完了すると、/boot/home/config/boot/UserBootscriptが実行されます。例えば次のように、システムが起動した直後に毎回いくつかのプログラムを自動起動させることができます:
    
+
    # LaunchBox を起動する
 /boot/system/apps/LaunchBox &
 
-# Start Workspaces Applet
+# Workspaces アプレットを起動する
 /boot/system/apps/Workspaces &
    
-
    Remember to end a command with an "&" to start it as a background process, or the script will halt until that command has finished (in this case: the launched app was closed again).
    
+
    コマンドをバックグラウンド・プロセスとして実行するために、コマンドの末尾は"&"で終わらせることを覚えておいてください。さもなくばそのコマンドが完了するまで(この例では、起動したアプリケーションが再度閉じられるまで)スクリプトが停止してしまいます。
    
 
-
    A simple alternative to the above for launching applications at boot up is to put links to them in the /boot/home/config/boot/launch directory. This can be done simply by right-clicking on the application you wish to have started automatically, going to Create Link and then navigating to the above directory.
    
+
    システムの起動時にアプリケーションを起動させるための、上記とは違うシンプルな方法の1つに、それらアプリケーションへのリンクを/boot/home/config/boot/launchディレクトリに置くという方法があります。この方法は、自動起動させたいアプリケーションを右クリックして、Create Linkにマウスカーソルを合わせたあと、前述のディレクトリへナビゲートすることで簡単に実現できます。
    
 
 
    
 index
-The UserShutdownScript
    
-
    /boot/home/config/boot/UserShutdownScript will be executed as the first step in the shutdown process. If the script returns a non-zero exit status, the shutdown is aborted.
    
+UserShutdownScript
+
    /boot/home/config/boot/UserShutdownScriptはシャットダウン・プロセスの最初のステップで実行されます。このスクリプトが0でない終了ステータスを返すと、シャットダウンは中断されます。
    
 
 
    
 index
-The UserShutdownFinishScript
    
-
    /boot/home/config/boot/UserShutdownFinishScript is executed as the last step in the shutdown process. Note, that most parts of the system have terminated by the time this script is executed.
    
+UserShutdownFinishScript
+
    /boot/home/config/boot/UserShutdownFinishScriptはシャットダウンの最終ステップで実行されます。このスクリプトが実行されるときには、システムの大部分が終了していることに注意してください。
    diff --git a/userguide/jp/preferences/e-mail.html b/userguide/jp/preferences/e-mail.html index e0d1293c..b8822b80 100644 --- a/userguide/jp/preferences/e-mail.html +++ b/userguide/jp/preferences/e-mail.html @@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a Spam/Genuine Estimate this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065. -

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    +

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.

    diff --git a/userguide/jp/queries.html b/userguide/jp/queries.html index 37ba8314..42f15966 100644 --- a/userguide/jp/queries.html +++ b/userguide/jp/queries.html @@ -122,7 +122,7 @@ A good way to cut down the number of search results.

    • You could copy and paste the string into an email, forum or IRC for others to use or debug.

    • You can use this method to construct a query in Attribute mode and then switch to Formula mode, to comfortably generate a search string to use for a query in Terminal or a script.

      • -

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

      • +

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

    diff --git a/userguide/jp/tracker.html b/userguide/jp/tracker.html index 1ed2cea8..74ff1cd6 100644 --- a/userguide/jp/tracker.html +++ b/userguide/jp/tracker.html @@ -124,7 +124,7 @@ This type-ahead filtering is set in the Trac diff --git a/userguide/pt_PT/applications/textsearch.html b/userguide/pt_PT/applications/textsearch.html index c5dc7516..1f398af9 100644 --- a/userguide/pt_PT/applications/textsearch.html +++ b/userguide/pt_PT/applications/textsearch.html @@ -71,13 +71,13 @@ Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    -Trim selectionALT T Removes all entries form the list that are not currently selected. +Trim selectionALT T Removes all entries from the list that are not currently selected. Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found. Open files in TrackerALT KOpens the location of the currently selected files in Tracker. -Copy text to clipboardALT CCopies the current selection to the clipboard. +Copy text to clipboardALT BCopies the current selection to the clipboard.

    Settings menu

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku. -Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. +Escape search text TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings. diff --git a/userguide/pt_PT/preferences/deskbar.html b/userguide/pt_PT/preferences/deskbar.html index b85d5892..8e3ec8a7 100644 --- a/userguide/pt_PT/preferences/deskbar.html +++ b/userguide/pt_PT/preferences/deskbar.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * Vasco Costa * --> @@ -47,7 +49,6 @@
    -
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.

    deskbar-icon_64.pngDeskbar

    @@ -57,7 +58,7 @@ ~/config/settings/Deskbar_security_code


    -

    The Deskbar preference panel is also available from the Deskbar. Its settings are discussed in the topic on Deskbar.

    +

    O painel de preferências da Deskbar também está acessível a partir da Deskbar. As definições estão documentadas no tópico Deskbar.

    diff --git a/userguide/pt_PT/preferences/e-mail.html b/userguide/pt_PT/preferences/e-mail.html index 1444ee3b..aa196873 100644 --- a/userguide/pt_PT/preferences/e-mail.html +++ b/userguide/pt_PT/preferences/e-mail.html @@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a Spam/Genuine Estimate this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065. -

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    +

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.

    diff --git a/userguide/pt_PT/queries.html b/userguide/pt_PT/queries.html index b98d5673..b6200a8e 100644 --- a/userguide/pt_PT/queries.html +++ b/userguide/pt_PT/queries.html @@ -122,7 +122,7 @@ A good way to cut down the number of search results.

    • You could copy and paste the string into an email, forum or IRC for others to use or debug.

    • You can use this method to construct a query in Attribute mode and then switch to Formula mode, to comfortably generate a search string to use for a query in Terminal or a script.

      • -

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

      • +

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

    diff --git a/userguide/pt_PT/tracker.html b/userguide/pt_PT/tracker.html index f2e0d9eb..6407b64a 100644 --- a/userguide/pt_PT/tracker.html +++ b/userguide/pt_PT/tracker.html @@ -124,7 +124,7 @@ This type-ahead filtering is set in the Trac diff --git a/userguide/ru/applications/textsearch.html b/userguide/ru/applications/textsearch.html index 6f3d6334..e1ced2b4 100644 --- a/userguide/ru/applications/textsearch.html +++ b/userguide/ru/applications/textsearch.html @@ -71,13 +71,13 @@ Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    -Trim selectionALT T Removes all entries form the list that are not currently selected. +Trim selectionALT T Removes all entries from the list that are not currently selected. Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found. Open files in TrackerALT KOpens the location of the currently selected files in Tracker. -Copy text to clipboardALT CCopies the current selection to the clipboard. +Copy text to clipboardALT BCopies the current selection to the clipboard.

    Settings menu

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku. -Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. +Escape search text TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings. diff --git a/userguide/ru/preferences/e-mail.html b/userguide/ru/preferences/e-mail.html index 9cc3bbf0..7bbdd356 100644 --- a/userguide/ru/preferences/e-mail.html +++ b/userguide/ru/preferences/e-mail.html @@ -23,7 +23,7 @@
    @@ -43,8 +43,8 @@ « Deskbar -:: Настройки -:: Типы файлов » +:: Preferences +:: FileTypes »
    @@ -183,8 +183,8 @@
    « Deskbar -:: Настройки -:: Типы файлов » +:: Preferences +:: FileTypes »
    diff --git a/userguide/ru/queries.html b/userguide/ru/queries.html index 655b2140..805a6f70 100644 --- a/userguide/ru/queries.html +++ b/userguide/ru/queries.html @@ -24,7 +24,7 @@
    @@ -44,8 +44,8 @@ « Индексация -:: Содержание -:: Семинар » +:: Contents +:: Workshop »
    @@ -156,8 +156,8 @@
    « Индексация -:: Содержание -:: Семинар » +:: Contents +:: Workshop »
    diff --git a/userguide/ru/tracker.html b/userguide/ru/tracker.html index eab2dd8b..7c5de69b 100644 --- a/userguide/ru/tracker.html +++ b/userguide/ru/tracker.html @@ -23,7 +23,7 @@
    @@ -42,9 +42,9 @@
  • English
    • - « Team Monitor - диспетчер задач -:: Содержание -:: Дополнения для Tracker (Tracker add-ons) » + « Team Monitor +:: Contents +:: Tracker Add-Ons »
    @@ -195,9 +195,9 @@
    - « Team Monitor - диспетчер задач -:: Содержание -:: Дополнения для Tracker (Tracker add-ons) » + « Team Monitor +:: Contents +:: Tracker Add-Ons »
    diff --git a/userguide/sv_SE/applications/textsearch.html b/userguide/sv_SE/applications/textsearch.html index 92267f93..3ff377a7 100644 --- a/userguide/sv_SE/applications/textsearch.html +++ b/userguide/sv_SE/applications/textsearch.html @@ -72,13 +72,13 @@ Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    -Trim selectionALT T Removes all entries form the list that are not currently selected. +Trim selectionALT T Removes all entries from the list that are not currently selected. Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found. Open files in TrackerALT KOpens the location of the currently selected files in Tracker. -Copy text to clipboardALT CCopies the current selection to the clipboard. +Copy text to clipboardALT BCopies the current selection to the clipboard.

    Settings menu

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku. -Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. +Escape search text TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings. diff --git a/userguide/sv_SE/preferences/e-mail.html b/userguide/sv_SE/preferences/e-mail.html index 56cc4dda..f98d28de 100644 --- a/userguide/sv_SE/preferences/e-mail.html +++ b/userguide/sv_SE/preferences/e-mail.html @@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a Spam/Genuine Estimate this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065. -

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    +

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.

    diff --git a/userguide/sv_SE/queries.html b/userguide/sv_SE/queries.html index ffaed7dc..78e752f1 100644 --- a/userguide/sv_SE/queries.html +++ b/userguide/sv_SE/queries.html @@ -122,7 +122,7 @@ A good way to cut down the number of search results.

    • You could copy and paste the string into an email, forum or IRC for others to use or debug.

    • You can use this method to construct a query in Attribute mode and then switch to Formula mode, to comfortably generate a search string to use for a query in Terminal or a script.

      • -

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

      • +

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

    diff --git a/userguide/sv_SE/tracker.html b/userguide/sv_SE/tracker.html index e18a0d56..bd7443b5 100644 --- a/userguide/sv_SE/tracker.html +++ b/userguide/sv_SE/tracker.html @@ -41,7 +41,7 @@ « Team Monitor :: Contents -:: Tracker-tillägg » +:: Tracker Add-Ons » @@ -124,7 +124,7 @@ This type-ahead filtering is set in the Trac @@ -193,7 +193,7 @@ This type-ahead filtering is set in the Trac
    « Team Monitor :: Contents -:: Tracker-tillägg » +:: Tracker Add-Ons »
    diff --git a/userguide/uk/applications/textsearch.html b/userguide/uk/applications/textsearch.html index 80da6832..af0f9182 100644 --- a/userguide/uk/applications/textsearch.html +++ b/userguide/uk/applications/textsearch.html @@ -69,13 +69,13 @@ Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    -Trim selectionALT T Removes all entries form the list that are not currently selected. +Trim selectionALT T Removes all entries from the list that are not currently selected. Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found. Open files in TrackerALT KOpens the location of the currently selected files in Tracker. -Copy text to clipboardALT CCopies the current selection to the clipboard. +Copy text to clipboardALT BCopies the current selection to the clipboard.

    Settings menu

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku. -Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. +Escape search text TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions. Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings. diff --git a/userguide/uk/preferences/e-mail.html b/userguide/uk/preferences/e-mail.html index 4ce6f3fd..835a83e5 100644 --- a/userguide/uk/preferences/e-mail.html +++ b/userguide/uk/preferences/e-mail.html @@ -41,7 +41,7 @@ « Deskbar :: Preferences -:: Типи файлів (FileTypes) » +:: FileTypes » @@ -151,7 +151,7 @@ With the first text field you specify which header to check against. These are a Spam/Genuine Estimate this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065. -

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    +

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.

    @@ -181,7 +181,7 @@ If you're on a dial-up connection, you may want to do that On
    « Deskbar :: Preferences -:: Типи файлів (FileTypes) » +:: FileTypes »
    diff --git a/userguide/uk/queries.html b/userguide/uk/queries.html index 7d3aaa5e..7f4f559e 100644 --- a/userguide/uk/queries.html +++ b/userguide/uk/queries.html @@ -122,7 +122,7 @@ A good way to cut down the number of search results.

    • You could copy and paste the string into an email, forum or IRC for others to use or debug.

    • You can use this method to construct a query in Attribute mode and then switch to Formula mode, to comfortably generate a search string to use for a query in Terminal or a script.

      • -

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

      • +

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

    diff --git a/userguide/uk/tracker.html b/userguide/uk/tracker.html index d890b3c5..2ca5cf08 100644 --- a/userguide/uk/tracker.html +++ b/userguide/uk/tracker.html @@ -124,7 +124,7 @@ This type-ahead filtering is set in the Trac diff --git a/userguide/zh_CN/applications/installer.html b/userguide/zh_CN/applications/installer.html index 06f1bc27..cc19b3d9 100644 --- a/userguide/zh_CN/applications/installer.html +++ b/userguide/zh_CN/applications/installer.html @@ -16,13 +16,13 @@ - Installer（安装器） + 安装器
    @@ -42,8 +42,8 @@ « Icon-O-Matic -:: 应用程序 -:: Magnify » +:: Applications +:: 放大镜 »
    @@ -93,8 +93,8 @@ chainloader +1
    « Icon-O-Matic -:: 应用程序 -:: Magnify » +:: Applications +:: 放大镜 »
    diff --git a/userguide/zh_CN/applications/magnify.html b/userguide/zh_CN/applications/magnify.html index 63ae4569..e7f2b9cd 100644 --- a/userguide/zh_CN/applications/magnify.html +++ b/userguide/zh_CN/applications/magnify.html @@ -9,18 +9,20 @@ * * Authors: * Humdinger + * Translators: + * Pengphei Han * --> - Magnify + 放大镜
    @@ -40,16 +42,16 @@  «  Icon-O-Matic  -::  应用程序  -::  电子邮箱  » +::  Applications  +::  Mail  »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    +
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    -

    magnify-icon_64.pngMagnify

    +

    magnify-icon_64.png放大镜

    @@ -57,29 +59,31 @@
    桌面栏：应用程序
    位置：/boot/system/apps/Magnify
    ~/config/settings/Magnify_prefs


    -

    Magnify shows an enlarged version of the area around your mouse pointer.

    +

    放大镜对您的鼠标指针周围区域进行了放大显示。

    magnify.png -

    At the top you'll find the size and magnification level of the area. "32 x 32 @ 8 pixels/pixel" means that you look at a 32x32 pixel square around your mouse pointer and every pixel is enlarged by a factor of 8.

    -

    Below that is the color of the pixel that's marked by a red outline. Its color is presented as RGB and hex value.
    -You can move the red outline with ← / → / ↑ / ↓.

    -

    To measure distances and align objects, you can add up to two blue crosshairs with ALT H. Their X/Y coordinates toward the top left corner and, if both are added, their X/Y distance from each other, are displayed at the bottom.
    -They can also be moved with ← / → / ↑ / ↓. The active crosshair is marked with an "x".

    -

    You can move the mouse pointer pixel by pixel with OPT ← / → / ↑ / ↓.

    -

    Clicking on the pop-up menu gives you a number of options:

    +

    在顶部，您可以找到该区域的尺寸和放大倍数。 "32 x 32 @ 8 pixels/pixel" 表示，您正在查看鼠标周围 32x32 的像素面积，而且每个像素都放大了8倍。

    +

    下面是一个具有红色轮廓的的像素。它的颜色以RGB和十六进制值表示。
    +您可以使用 ← / → / ↑ / ↓ 移动红色的轮廓。

    +

    为了量度距离和排列的对象，您可以使用 ALT H 添加两个蓝色的十字丝。它们的 X/Y 坐标趋向于左上角，如果添加了两个十字丝，它们的之间的 X/Y 距离显示于窗口的底部。 + +
    +十字丝也可以通过 ← / → / ↑ / ↓ 进行移动，而活动的十字丝则标记为 "x" 。

    +

    您可以使用 OPT ← / → / ↑ / ↓ 控制鼠标指针，使指针以像素为单位移动。

    +

    点击弹出菜单将会给出下面的选项：

    - - - - - - - - + + + + + + + + - - - - + + + +
    Save ImageALT S Saves the current display as a resource file.
    Copy ImageALT C Copies the current display to the clipboard.
    Hide/Show InfoALT T Toggles the display of all the additional information.
    Add a CrosshairALT H Adds a crosshair you can drag around.
    Remove a CrosshairALT SHIFT H Removes the last added crosshair.
    Hide/Show GridALT G Toggles the overlayed grid.
    Freeze/Unfreeze imageALT F Stops/continues updating the magnification area.
    Stick CoordinatesALT I Keeps updating the magnification area, but don't follow the mouse pointer any more.
    Save ImageALT S 保存当前显示图像为源文件。
    Copy ImageALT C 复制当前显示到剪贴板。
    Hide/Show InfoALT T 切换显示所有的附加信息。
    Add a CrosshairALT H 添加可以移动的十字丝。
    Remove a CrosshairALT SHIFT H 删除最近添加的十字丝。
    Hide/Show GridALT G 在覆盖网格之间进行切换。
    Freeze/Unfreeze imageALT F 停止/继续更新放大区域。
    Stick CoordinatesALT I 持续更新放大区域，但是不再追踪鼠标指针。
    Make SquareALT / Reverts back to a square display after resizing the window.
    Decrease Window SizeALT - Shrinks the magnified area around the mouse pointer.
    Increase Window SizeALT + Enlarges the magnified area around the mouse pointer.
    Decrease Pixel SizeALT , Lowers magnification.
    Increase Pixel SizeALT . Increases magnification.
    Decrease Window SizeALT - 缩小鼠标指针周围放大区域的面积。
    Increase Window SizeALT + 增加鼠标指针周围放大区域的面积。
    Decrease Pixel SizeALT , 缩小放大倍数。
    Increase Pixel SizeALT . 增加放大倍数。
    @@ -88,8 +92,8 @@ They can also be moved with ← / →
     «  Icon-O-Matic  -::  应用程序  -::  电子邮箱  » +::  Applications  +::  Mail  »
    diff --git a/userguide/zh_CN/applications/pe.html b/userguide/zh_CN/applications/pe.html index 78a15b87..2a0529f0 100644 --- a/userguide/zh_CN/applications/pe.html +++ b/userguide/zh_CN/applications/pe.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * Pengphei Han * --> @@ -20,7 +22,7 @@
    @@ -40,14 +42,13 @@  «  BePDF  -::  应用程序  -::  Vision聊天客户端  » +::  Applications  +::  Vision  »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。

    pe-icon_64.pngPe

    @@ -58,8 +59,8 @@
    ~/config/settings/pe/*


    -

    Pe is a sophisticated editor, with its syntax highlighting targeted mainly at programmers and HTML writers. Originally created by Maarten Hekkelmann, it's been open sourced and maintained by Haiku developers. A bugtracker and more information is available at the Pe project page.

    -

    Find out more about Pe's features in its local documentation.

    +

    Pe 是一个复杂的编辑器，具有语法高亮度特性，适用于程序员和HTML编辑人员。它的原作者是 Maarten Hekkelmann，现在属于开源软件，由Haiku开发人员负责维护。有关错误跟踪和更多相关信息，可以参阅 Pe 项目页面。

    +

    有关Pe的特性，可以参阅它的本地文档。

    @@ -67,8 +68,8 @@
     «  BePDF  -::  应用程序  -::  Vision聊天客户端  » +::  Applications  +::  Vision  »
    --> diff --git a/userguide/zh_CN/applications/people.html b/userguide/zh_CN/applications/people.html index a6caa746..1015326c 100644 --- a/userguide/zh_CN/applications/people.html +++ b/userguide/zh_CN/applications/people.html @@ -9,18 +9,20 @@ * * Authors: * Humdinger + * Translators: + * Pengphei Han * --> - People + 联系人
    @@ -39,17 +41,16 @@
  • English
    • - «  软件包安装器  -::  应用程序  + «  PackageInstaller  +::  Applications  ::  PoorMan  »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    -

    people-icon_64.pngPeople

    +

    people-icon_64.png联系人

    @@ -57,25 +58,25 @@
    桌面栏：应用程序
    位置：/boot/system/apps/People
    ~/config/settings/People_data


    -

    People is a simple contact database using the attributes of Haiku's filesystem to store addresses and other contact information. Every contact is saved as one Person file with its data in separate attributes. All are indexed and therefore searchable with a query.

    +

    “联系人”程序是一个小型的联系人数据库，它使用了Haiku文件系统中的属性存储地址和其他的联系人信息。所有的联系方式都保存为单个文件，而它的数据则保存在独立的属性中。联系人程序中的所有文件都做了索引，它们可以在 查询 中进行搜索。

    people.png -

    The Group attribute at the bottom allows assigning a person to one or more groups. Useful for "mass mailing" a number of people who, for example, work on a specific project. The pop-up menu offers all currently existing groups. If a person belongs to more than one group, the group names are delimited with a ",".

    +

    面板底部的 Group 属性用于将一个联系人添加到一个躲着多个群组。如果需要给从事于同一项目的多个人发送“群发邮件”，这项功能则将非常有用。弹出菜单提供了所有当前存在的群组。如果某个联系人属于多个群组，群组名之间以 "," 分开。

    -

    These Person files are usually all saved in /boot/home/people/. To get a list of all your contacts, just open your people folder and display all attributes of interest. If you choose to organize your Person files in different folders, just use a query to display them all in one window.

    +

    联系人记录文件通常保存在 /boot/home/people/ 。 为了显示所有的联系人列表，您只需要打开该文件夹，然后显示所有感兴趣的属性。如果您把联系人文件放置在不同的文件夹，您只需要使用一个查询将它们都显示在一个窗口。

    people-files.png -

    You can treat these files like any other: You can sort according to attributes (even a second sorting order by holding SHIFT while clicking) and of course delete, duplicate or rename Person files. Even the contact information can be edited directly: Clicking on an attribute (or ALT E) to edit works just like renaming a file. Once you're in edit mode, TAB and SHIFT TAB will jump from column to column.

    +

    您可以如下处理这些文件：您可以依据属性对他们进行排序（在点击时，同时按下 SHIFT 键进行二次排序），当然也可以删除，复制和重命名联系人文件。甚至联系人信息也可以直接进行编辑：点击一个属性（或者使用ALT E）来进行编辑工作，例如重命名文件。如果您进入了编辑模式，TAB 和 SHIFT TAB 在行与行之间进行切换。

    - «  软件包安装器  -::  应用程序  + «  PackageInstaller  +::  Applications  ::  PoorMan  »
    diff --git a/userguide/zh_CN/applications/textsearch.html b/userguide/zh_CN/applications/textsearch.html index 6c0e1750..cf57f8be 100644 --- a/userguide/zh_CN/applications/textsearch.html +++ b/userguide/zh_CN/applications/textsearch.html @@ -22,7 +22,7 @@
    @@ -41,25 +41,25 @@
  • English
    • - «  终端  -::  应用程序  -::  虚拟电视  » + «  Terminal  +::  Applications  +::  TV  »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    +
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.

    textsearch-icon_64.png文本搜索

    - +
    桌面栏：No entry, normally launched via Tracker Add-on
    桌面栏：没有入口，通常通过Tracker的附加组进行启动
    位置：/boot/system/apps/TextSearch
    设置： ~/config/settings/TextSearch


    -

    TextSearch looks for a string in text files. Typically it is invoked from Tracker's Add-on context menu on the selection of files or folders you want to search.

    +

    文本搜索用于查询文本文件中的字符串。通常，它通过选中文件或者文件夹右键菜单的 Tracker附加组件 实现启动。

    textsearch.png @@ -67,32 +67,32 @@

    Only a few words on some of the otherwise self-explaining menu items:

    - + - - + + - - + + - + - - - - + + + +

    File menu

    File 菜单

    New windowALT N Opens a new window where you can enter another string and search through the same files/folders.
    Set target...ALT FLets you choose a new set of files and folders to search through.

    Action menu

    Trim selectionALT T Removes all entries form the list that are not currently selected.

    Action 菜单

    Trim selectionALT T Removes all entries from the list that are not currently selected.
    Open selectionALT OOpens the currently selected files with their preferred application (same as a double-click). If it's a text editor supporting it (like Pe), you can jump to the exact line the search string was found.
    Open files in TrackerALT KOpens the location of the currently selected files in Tracker.
    Copy text to clipboardALT CCopies the current selection to the clipboard.

    Settings menu

    Copy text to clipboardALT BCopies the current selection to the clipboard.

    Settings 菜单

    Skip folders starting with a dot This is useful when working in a "unixy" environment, where often administrative files are hidden inside ".folders/". Source versioning systems like SVN and CVS are examples of applications using this and are also widely used in Haiku.
    Escape search text TextSearch uses the command line command grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions.
    Escape search text TextSearch uses the command line tool grep. For it, special characters like '"*\$?! and spaces have to be escaped with a \. Deactivating this setting means you have to do this yourself, but in exchange grants you the power of regular expressions.
    Text files only TextSearch is currently only useful for finding strings in plain text files. Deactivating this setting will have it look through any kind of file anyway.

    History menu

    Contains recently used search strings.

    Encoding menu

    Lets you choose different character encodings if needed.

    History 菜单

    包含最近查询的字符。

    Encoding 菜单

    根据需要选择不同的字符编码。
    - «  终端  -::  应用程序  -::  虚拟电视  » + «  Terminal  +::  Applications  +::  TV  »
    diff --git a/userguide/zh_CN/contents.html b/userguide/zh_CN/contents.html index 2acd2d04..e27a29cc 100644 --- a/userguide/zh_CN/contents.html +++ b/userguide/zh_CN/contents.html @@ -22,7 +22,7 @@
    @@ -121,9 +121,9 @@ 利用索引来实现属性的查找。 查询 diff --git a/userguide/zh_CN/desktop-applets/launchbox.html b/userguide/zh_CN/desktop-applets/launchbox.html index edcf8ad3..c87d21fd 100644 --- a/userguide/zh_CN/desktop-applets/launchbox.html +++ b/userguide/zh_CN/desktop-applets/launchbox.html @@ -16,13 +16,13 @@ - LaunchBox + 快速启动
    @@ -41,29 +41,28 @@
  • English
    • - 桌面小程序  -::  网络状态  » + Desktop Applets  +::  NetworkStatus  »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    -

    launchbox-icon_64.pngLaunchBox

    +

    launchbox-icon_64.png快速启动

    桌面栏：桌面小程序
    位置：/boot/system/apps/LaunchBox
    设置： ~/config/settings/LaunchBox/*
    -

    One or more LaunchBox applets can be started to organize shortcuts to your favorite applications or documents. You decide if each is shown on all or just the current workspace. They can also serve to quickly open a document in a specific application. For example, you could drag&drop a HTML file onto a text editor in a LaunchBox to open it in the editor instead of its preferred application, the browser.

    +

    你可以启动一个或者多个快速启动小程序，然后使用它们来组织您的收藏程序和文档的快捷方式。您可以决定是否显示所有工作区或者当前工作区的快捷方式。它们也可以用于快速的在某个程序中打开文档。 例如，您可以拖拽一个HTML文件到快速启动栏中的文本编辑器中，然后通过该编辑器打开它，而不是它的首选程序，浏览器。

    launchbox.png -

    All options are reached from the context menu:

    +

    所有的选项都可以从右键菜单中进行设置：

    - - - + + + +横向排列程序按钮。 +
    +设置图标尺寸，从16像素到64像素。 +
    +忽略双击，点击对象只启动一次。 +
    +显示窗口边缘。 +
    +鼠标靠近屏幕边缘时，弹出快速启动。 +
    +在所有工作区中显示快速启动。 +新建一个快速启动面板。 +
    +复制当前快速启动面板。 +
    +关闭当前快速启动面板。 +显示简介窗口。 +
    +退出快速启动
    Add Button Here Adds an empty button.
    Clear Button Empties a button.
    Remove Button Removes a button.
    Add Button Here 添加一个空按钮。
    Clear Button 清空一个按钮。
    Remove Button 删除一个按钮。
    Settings
    - Horizontal Layout
    - Icon size
    @@ -71,24 +70,32 @@ - Show Window Border
    - Auto Raise
    - Show On All Workspaces    		 
    -Aligns the buttons horizontally.
    -Sets the icon size between 16 and 64 pixel.
    -Launches the object only once, even when you (accidentally) double-click.
    -Shows the window border.
    -LaunchBox pops up if the mouse is near the screen edge.
    -Shows the LaunchBox on every workspace.
    Pad
    - New
    - Clone
    - Close    		 
    -Add a new pad.
    -Duplicate the current pad.
    -Close the current pad.
    LaunchBox
    - About...
    - Quit    		 
    -Shows the About window.
    -Quits all LaunchBox pads.    		 
     
    @@ -96,8 +103,8 @@ Quits all LaunchBox pads. 
    - 桌面小程序  -::  网络状态  » + Desktop Applets  +::  NetworkStatus  »
    diff --git a/userguide/zh_CN/filetypes.html b/userguide/zh_CN/filetypes.html index 7d9edcdf..a3bd6581 100644 --- a/userguide/zh_CN/filetypes.html +++ b/userguide/zh_CN/filetypes.html @@ -22,7 +22,7 @@
    @@ -41,15 +41,14 @@
  • English
    • - « 桌面栏 -:: 内容 -:: Attributes（属性） » + « Deskbar +:: Contents +:: Attributes »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。

    文件类型

    @@ -57,8 +56,8 @@
    由于在Haiku中没有必要使用文件扩展，但是您需要注意的是，当您和其他系统的用户分享文件时，您需要添加上扩展名，例如，通过邮件，上传到服务器或者交换闪盘。否则，他们的系统将无法识别出文件类型。

    index -设置特定文件的文件类型

    -

    您可以修改特定文件的类型，它的图标，以及相关联的程序。选择该文件，然后从右键菜单中调用 Add-Ons | Filetype add-on 。

    +文件类型设置

    +

    您可以修改单个文件的类型，图标，以及相关联的程序。选择该文件，然后从右键菜单中调用 Add-Ons | Filetype add-on 。

    filetype-addon.png

    @@ -73,47 +72,47 @@

    index 首选应用程序

    -

    This pop-up menu shows a list of all applications that can handle this particular filetype. From here you can choose which program should open this specific file when it's double-clicked. You could, for example, change a HTML file's preferred application from the browser to a text editor while you're working on it. Every other HTML file still opens in the browser, only this particular one starts in your text editor.

    +

    弹出菜单中显示了一个可以处理该特定类型文件的所有程序的列表。您可以选择某个程序，当双击打该类型文件时，该程序将会自动启动。例如，您可以将一个HTML文件的首选程序修改为您正在使用的文本编辑器。那么所有其他的HTML文件仍会在浏览器中打开，仅该文件在您的文本编辑器中打开。

    -

    The Default Application is the one that's set globally for that filetype. If you don't find the program you want to associate with this file in the pop-up menu, you'll again find the buttons Select... and Same As... which do the similar thing described under "The File Type" above.

    +

    Default Application 是用于全局设置的文件类型首选程序。如果您在弹出菜单中没有找出关联到该文件的程序，您会再次找到 Select... 和 Same As... 按钮，它们两个具有类似于“文件类型”下描述的功能。

    index -图标

    -

    If you're wondering why the icon well on the top right is empty: Icons are normally inherited from the system default for that filetype. You can open the Filetype Add-On of a file that contains an icon and drag&drop it into your file's icon well. Or you double-click the icon well and create or edit your own icon. For more info on icons and how to create your own, see topic Icon-O-Matic.

    +图标设置

    +

    如果您对左上角的图标为空产生疑问：图标通常从系统为文件类型默认的图标中继承而来。您可以打开一个带有图标文件的 Filetype Add-On，然后将它的图标拖拽到您的文件的图标栏中。或者您可以双击图标，然后创建和F编辑自己的图标。更多有关图标的信息和如何创建图标，您可以参阅 Icon-O-Matic 主题。

    index -应用程序的特殊设置

    -

    If you invoke the Filetype Add-On on an executable (here: StyledEdit), you'll get a different dialog:

    +程序的特殊设置 +

    如果您调用可执行文件的 Filetype Add-On （此处使用的是 StyledEdit），您会打开一个不同的对话框：

    filetype-addon-stylededit.png -

    On top, you'll see, instead of a standardized MIME string, the unique application signature. With it, the system finds the program wherever it's installed.

    -

    Below it are several flags, controlling the app's behaviour:

    +

    在顶部，您可以看到，它不是一个标准的MIME字符串，而是唯一的程序署名。通过它，操作系统可以找出程序的安装位置。

    +

    在它的下面，是用于控制程序的行为的标记：

    - - - - - + + + + +
    Single Launch Only one instance of the app can be running per executable file. If you have two copies of that app, however, they can run side by side.
    Multiple Launch Many instances of the app can run simultaneously.
    Exclusive Launch Really only one instance with that app's signature is allowed to run at a time.
    Args Only Indicates the app doesn't respond to messages.
    Background App The app won't appear in Twitcher or the list of running apps of the Deskbar.
    Single Launch 对于每个可执行文件，仅有其中一个实例可以运行。如果您拥有两份该程序，它们可以依次运行。
    Multiple Launch 程序的许多实例可以同步运行。
    Exclusive Launch 每次只允许具有该程序的署名的一个实例运行。
    Args Only 指出该程序对于调用消息不作出响应。
    Background App 该程序不出现在 任务切换器 或者桌面栏的运行程序列表中。
    -

    Then there's the list of supported filetypes. You can add (and remove) filetypes if you think the application can handle them. As a consequence, the app will appear in the menu for preferred applications or Tracker's Open with... context menu when you right-click on a file of that type.

    -

    At the bottom are version and copyright information. Like the application signature, they are filled in by the app's author and shouldn't be altered.

    +

    然后，有一个支持文件类型的列表。如果您认为该程序可以处理此文件类型，您可以在这里进行添加或者删除。结果是，当您右键点击一个该类型的文件时，该程序将会出现在首选程序菜单，或者 Tracker 的 Open with... 右键菜单中。

    +

    在底部是程序的版本和授权信息。它们同程序的署名相类似，其中写入了程序创建者的名字，而且这些名字是不可更改的。

    index -Global settings with the FileTypes Preferences

    -

    The FileTypes preferences don't deal with individual files but with global settings of filetypes. You can change default icons and preferred applications or add, remove, or alter attributes of whole filetypes. You can even create your own filetype from scratch.

    -

    All filetypes and their configurations are stored in /boot/home/config/settings/beos_mime/. Before you start experimenting, it may be prudent to make a backup of that folder...

    -

    To learn more about the FileTypes preferences see the workshop: Filetypes, Attributes, Index and Queries.

    +全局设置 +

    文件类型 首选项不用于处理单个文件，而是文件类型的全局设置。您可以修改所有文件类型的默认图标，首选程序，或者添加，删除，和修改属性。您甚至可以从头开始创建自己的文件类型。

    +

    所有的文件类型和它们的配置文件保存在 /boot/home/config/settings/beos_mime/ 。在您开始尝试作出改动之前，您最好对该文件夹做个备份以防出错。

    +

    了解更多有关 文件类型 首选项的信息，可以参阅操作练习：文件类型，属性，索引和查询。

    - « 桌面栏 -:: 内容 -:: Attributes（属性） » + « Deskbar +:: Contents +:: Attributes »
    diff --git a/userguide/zh_CN/gui.html b/userguide/zh_CN/gui.html index f94bbe1d..04f8f74c 100644 --- a/userguide/zh_CN/gui.html +++ b/userguide/zh_CN/gui.html @@ -22,7 +22,7 @@
    @@ -41,15 +41,15 @@
  • English
    • - « 文件系统布局 -:: 内容 -:: Workspaces（工作区） » + « Filesystem layout +:: Contents +:: Workspaces »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    +
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.

    Haiku的图形用户界面

    @@ -61,7 +61,7 @@

  • 桌面栏可以看做是Haiku的"开始"菜单和任务栏（如果您愿意这样认为的话），详情参阅桌面栏主题。

  • 黄色的标签不仅仅提供了程序名或者文档的文件名：
    • 在拖动窗口时，您可以同时按下 SHIFT 键来移动标签，这样您可以将许多窗口进行叠加，而只需要点击标签即可方便的进行访问。
      • -
    • 双击标签可以最小化窗口（或者使用 CTRL ALT M 组合键）。通过这种方式隐藏的窗口可以通过 桌面栏 或者 Twitcher 进行访问。
      • +
    • 双击标签可以最小化窗口（或者使用 CTRL ALT M 组合键）。通过这种方式隐藏的窗口可以通过 桌面栏 或者 任务切换器 进行访问。
    • 您可以通过右键点击标签（或者窗口边界）来置后窗口。

  • 关闭按钮

  • “缩放”按钮（也可以通过CTRL ALT Z 组合键进行缩放）。对于大多数的程序，该按钮将会把窗口最大化。但并不是都如此，例如Tracker窗口，该按钮将会依据其内容将窗口放大至合适大小。

    • @@ -72,32 +72,32 @@

    index 打开和保存面板

    -

    从任意的程序打开或保存文件都将会打开类似于下面的面板：

    +

    从任意的程序打开或保存文件都将会打开类似于如下所示的面板：

    open-save.png -

    It has all the usual things: A list of files of the current folder to choose from, in case of a save panel, a text field to enter a filename and a pop-up menu for different file formats and their settings.
    -You can enter parent folders with the pop-up menu above the file listing.

    -

    If you already have a Tracker window with the location for a file open, you can simply drag either any file or the folder-representation (i.e. the symbol to the far right in its menu bar) into the panel. This changes the panel to that new location.

    +

    它具有所有常用的东西：当前文件夹下可选的文件列表，用于输入文件名的文本框，用于不同文件格式的弹出菜单，以及有关的设置。
    +您可以使用文件列表上面的弹出菜单进入上层文件夹。

    +

    如果您已经拥有一个Tracker窗口用于打开文件，您可以将任何的文件或者代表的文件夹（例如，在菜单栏最右边的标志）拖拽到该面板。然后，它将会修改面板指向新的位置。

    index 快捷键

    -

    Many shortcuts in open and save panels are the same used in Tracker. Besides the commands that are also available through the File menu, there are a few not that obvious:

    +

    在打开和保存面板中的许多快捷键和在Tracker中使用的相同。除了在 File 菜单中也可用的命令之外，还有些不是很明显的命令：

    - - - - - - + + + + + +
    ALT N Creates a new folder.
    ALT E Lets you rename the selected entry.
    ALT ↑ Moves into the parent folder.
    ALT ↓ or ENTER Moves into the selected folder.
    ALT D Takes you to your Desktop.
    ALT H Takes you to your Home folder.
    ALT N新建一个文件夹。
    ALT E重命名选中的文件。
    ALT ↑移动到上层文件夹。
    ALT ↓ or ENTER进入选中的文件夹。
    ALT D返回桌面。
    ALT H返回home文件夹。

    index 收藏夹和最近的文件夹

    -

    The Favorites menu in open and save panels provides recently visited folders and favorite locations that you can set up yourself. As indicated by the little arrow, you can also use these locations to navigate further down the hierarchy via submenus.

    +

    在打开和保存面板中的 收藏夹 菜单提供了您可以自主设置的最近访问文件夹和收藏夹的位置。根据小箭头的指示，您也可以使用这些位置通过子菜单导航至下面的文件层次。

    favorites.png -

    To add a Favorite, you simply navigate to your destination and choose Favorites | Add Current Folder. From now on it will appear in every open/save panel. To remove a Favorite, choose Favorites | Configure Favorites... and delete its entry.
    -All Favorites are kept in /boot/home/config/settings/Tracker/Go/. So you might as well add and remove links to files and folders there directly.

    +

    为了添加收藏项目，您可以导航至目标，然后选择 Favorites | Add Current Folder 。那么之后，它将会出现在每个打开/保存面板。为了删除收藏项目，选择 Favorites | Configure Favorites... ，然后在其中删除该入口。
    +所有的收藏项目保存在 /boot/home/config/settings/Tracker/Go/。所以您可以直接在那里添加或者删除相关的文件和文件夹的链接。

    index @@ -113,9 +113,9 @@ A right-click on a Replicant handle offers a context menu to show the originatin
    - « 文件系统布局 -:: 内容 -:: Workspaces（工作区） » + « Filesystem layout +:: Contents +:: Workspaces »
    diff --git a/userguide/zh_CN/keyboard-shortcuts.html b/userguide/zh_CN/keyboard-shortcuts.html index 10b2286d..7f47c06c 100644 --- a/userguide/zh_CN/keyboard-shortcuts.html +++ b/userguide/zh_CN/keyboard-shortcuts.html @@ -22,7 +22,7 @@
    @@ -41,9 +41,9 @@
  • English
    • - « Tracker 附加组件 -:: 内容 -:: 桌面栏 » + « Tracker Add-Ons +:: Contents +:: Deskbar »

    @@ -129,9 +129,9 @@
    - « Tracker 附加组件 -:: 内容 -:: 桌面栏 » + « Tracker Add-Ons +:: Contents +:: Deskbar »
    diff --git a/userguide/zh_CN/preferences/appearance.html b/userguide/zh_CN/preferences/appearance.html index e8ef61d2..cc16f3fd 100644 --- a/userguide/zh_CN/preferences/appearance.html +++ b/userguide/zh_CN/preferences/appearance.html @@ -22,7 +22,7 @@
    @@ -41,8 +41,8 @@
  • English
    • - 首选项  -::  背景  » + Preferences  +::  Backgrounds  »
    @@ -99,7 +99,7 @@ Glyph hinting


    在本面板底部有两个按钮：

    - +
    Defaults 恢复所有设置为默认状态。
    Defaults 恢复到系统默认的设置状态。
    Revert 取消设置，恢复到打开外观首选项前的设置状态。
    @@ -108,8 +108,8 @@ Glyph hinting
    - 首选项  -::  背景  » + Preferences  +::  Backgrounds  »
    diff --git a/userguide/zh_CN/preferences/datatranslations.html b/userguide/zh_CN/preferences/datatranslations.html index 42d40de6..f09dce6c 100644 --- a/userguide/zh_CN/preferences/datatranslations.html +++ b/userguide/zh_CN/preferences/datatranslations.html @@ -22,7 +22,7 @@
    @@ -41,15 +41,14 @@
  • English
    • - «  背景  -::  首选项  -::  桌面栏  » + «  Backgrounds  +::  Preferences  +::  Deskbar  »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。

    datatranslations-icon_64.png数据转换

    @@ -59,43 +58,47 @@
    ~/config/settings/* - 在改变默认设置之后，每个解析器都将创建它自己的设置文件。
    ~/config/settings/system/DataTranslations settings - 保存了面板的窗口位置。
    -

    Every application has the ability to open and save every file format for which there's a Translator installed. The settings for these Translators are configured in the DataTranslations preferences.

    +

    每个程序都可以打开和保存任何安装了转换器的文件格式。而有关这些转换器的设置可以在数据转换首选项中进行配置。


    datatranslations.png -

    Depending on its capabilities, each Translator offers different settings. At least you'll get an Info... button that opens a window with the credits and the installation path.
    -The following table gives an overview of the default Translators and their most useful options.

    +

    根据各自功能的不同，每个转换器具有不同的设置。 但是至少您可以使用 Info... 按钮打开一个显示致谢名单和安装路径的窗口。
    +下面的表格给出了默认转换器的概况和他们最常用的选项。

    - - - - - - - - - + + + + + + + + + - + - - - + + +
    BMP Images24bit, uncompressed, no transparency
    EXR ImagesILM's high dynamic-range (HDR) format
    GIF Images8bit, lossless compression, transparency
    -You can reduce the filesize by limiting the number of used colors and the palette.
    -You can write images with transparency, either by automatically using the alpha channel or by setting the RGB value that will be transparent by hand.
    JPEG2000 Images24bit, compressed, no transparency
    -Here, you normally only care about the output quality.
    JPEG Images24bit, compressed, no transparency
    -Besides the output quality you can also set a smoothing that will lessen compression artefacts but can blur the picture a little.
    PCX Images24bit, uncompressed, no transparency, PC Paintbrush Exchange format
    PNG Images32bit, lossless compression, transparency
    PPM Images24bit, uncompressed, no transparency, Portable PixMap format
    RAW Imagesup to 48bit, uncompressed, no transparency
    BMP Images24位，未压缩格式，无透明效果
    EXR ImagesILM的高动态范围图像格式（HDR）
    GIF Images8位，无损压缩，透明效果 +
    +您可以通过限制使用颜色和调色板的数量来减小文件大小。 +
    +通过使用自动的alpha频道，或者设置三种原色的值，您可以使用透明效果来处理图片。
    JPEG2000 Images24位，压缩格式，无透明效果 +
    +在这里，通常您只关心图像的输出效果。
    JPEG Images24位，压缩格式，无透明效果 +
    +除了输出质量，您也可以设置平滑处理，从而减轻压缩伪像，但是这将会是图像变得模糊。
    PCX Images24位，未压缩格式，无透明效果，PC画笔交换格式
    PNG Images32位，无损压缩，透明效果
    PPM Images24位，未压缩，无透明效果，便携式位图格式
    RAW Images48位，未压缩格式，无透明效果
    RTF Text Files格式化文本
    SGI Images24bit, optional lossless compression, transparency
    SGI Images24位，可选无损压缩，透明效果
    StyledEdit Files格式化文本
    TGA Images32bit, optional lossless compression, transparency
    TIFF Images24bit, optional lossless compression, layers, transparency
    WonderBrush Images32bit, layers, transparency, vector/pixel data
    TGA Images32位，可选无损压缩，透明效果
    TIFF Images24位，可选无损压缩，具有图层，透明效果
    WonderBrush Images32位，具有图层，透明效果，位图/矢量数据


    -
    Screenshots, charts, black&white drawings and other images with few used colors, as well as small pictures are best saved as GIF (up to 256 colors) or PNG (millions of colors). JPEG, for example, introduces compression artefacts without gain in smaller filesize.
    +
    屏幕截图，图表，黑白图纸，以及其他使用颜色很少图像，包括小图片，最好将它们保存为GIF（256色）或者PNG（上万种颜色）格式。例如，JPEG格式，引入了压缩伪像，但是没有增加文件大小。
    - «  背景  -::  首选项  -::  桌面栏  » + «  Backgrounds  +::  Preferences  +::  Deskbar  »
    diff --git a/userguide/zh_CN/preferences/e-mail.html b/userguide/zh_CN/preferences/e-mail.html index 59dc64bb..6a001fca 100644 --- a/userguide/zh_CN/preferences/e-mail.html +++ b/userguide/zh_CN/preferences/e-mail.html @@ -22,7 +22,7 @@
    @@ -41,15 +41,15 @@
  • English
    • - « 桌面栏 -:: 首选项 -:: 文件类型 » + « Deskbar +:: Preferences +:: FileTypes »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    +
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    @@ -75,10 +75,10 @@ The configuration is done in the E-Mail preference panel.

    index 新建邮箱账户

    -

    Let's go through the process of setting up an e-mail account.
    -You start by clicking the Add button to create a new, unnamed account. This opens a panel where you fill in your account info:

    +

    让我们开始了解有关邮箱账户的设置过程。
    +您可以点击 Add 按钮新建一个未命名账户。它将会打开一个用于填写有关您的账户信息的面板：

    e-mail-new-account.png -

    First, declare the Account Type which is either Receive Mail Only, Send Mail Only, or the most usual type, Send and Receive Mail. Then you set how you get your mail, via POP3 or IMAP.

    +

    首先， declare the Account Type which is either Receive Mail Only, Send Mail Only, or the most usual type, Send and Receive Mail. Then you set how you get your mail, via POP3 or IMAP.

    Now you enter your E-mail Address, Login Name and Password, give an Account Name under which it will be known under Haiku and your Real Name.

    If your account is from a major e-mail provider, Haiku already knows all technical details like server IP addresses and the following information is already filled in automatically. If that is not the case, just follow this guide and fill in the details to your e-mail account accordingly.

    @@ -154,7 +154,7 @@ With the first text field you specify which header to check against. These are a
    索引
    Spam/Genuine Estimate this is a numerical estimate that the spam filter assigned to the e-mail. They are shown in scientific notation, where 1.065e-12 translates to 1.065 divided by 10 to the 12th power, which in this case translates to 0.000000000001065.
    -

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    +

    The second text field holds your search pattern. It accepts regular expressions which gives it great flexibility, while unfortunately complicating things a bit. Read up on it a bit, it's well worth it and simple search patterns aren't that complicated at all.

    With the pop-up menu below it, you assign an action when the pattern matches. You can move or delete a mail, set the status to "Read" or anything else or set the e-mail account you'll reply with.

    @@ -182,9 +182,9 @@ If you're on a dial-up connection, you may want to do that On
    - « 桌面栏 -:: 首选项 -:: 文件类型 » + « Deskbar +:: Preferences +:: FileTypes »
    diff --git a/userguide/zh_CN/preferences/fonts.html b/userguide/zh_CN/preferences/fonts.html index 3e4db8f7..b8c1df4e 100644 --- a/userguide/zh_CN/preferences/fonts.html +++ b/userguide/zh_CN/preferences/fonts.html @@ -22,7 +22,7 @@
    @@ -41,8 +41,8 @@
  • English
    • - «  文件类型  -::  首选项  + «  FileTypes  +::  Preferences  ::  键盘  »

    @@ -62,7 +62,7 @@ fonts.png

    Haiku 定义了三种标准字体用于不同的目的。您可以设置简单，粗体，和等宽字体和字体大小以用于整个系统。除此之外，还有对于菜单中字体的单独设置。

    - +
    Defaults 恢复所有设置为默认状态。
    Defaults 恢复到系统默认的设置状态。
    Revert 恢复设置到程序启动时的状态。
    @@ -76,8 +76,8 @@
    - «  文件类型  -::  首选项  + «  FileTypes  +::  Preferences  ::  键盘  »
    diff --git a/userguide/zh_CN/preferences/keyboard.html b/userguide/zh_CN/preferences/keyboard.html index 6270dbb4..d3483ffb 100644 --- a/userguide/zh_CN/preferences/keyboard.html +++ b/userguide/zh_CN/preferences/keyboard.html @@ -22,7 +22,7 @@
    @@ -42,8 +42,8 @@  «  字体  -::  首选项  -::  终端键盘映射  » +::  Preferences  +::  键盘映射  »
    @@ -61,7 +61,7 @@ keyboard.png

    设置重复速度和两次按键之间的延迟时间。您可以在底部的文本框内对相关设置进行测试。

    - +
    Defaults 恢复所有设置为默认状态。
    Defaults 恢复到系统默认的设置状态。
    Revert 恢复键盘设置启动之前的设置状态。
    @@ -72,8 +72,8 @@
     «  字体  -::  首选项  -::  终端键盘映射  » +::  Preferences  +::  键盘映射  »
    --> diff --git a/userguide/zh_CN/preferences/keymap.html b/userguide/zh_CN/preferences/keymap.html index 954f91be..40b7050f 100644 --- a/userguide/zh_CN/preferences/keymap.html +++ b/userguide/zh_CN/preferences/keymap.html @@ -16,13 +16,13 @@ - 终端键盘映射 + 键盘映射
    @@ -42,16 +42,16 @@ « 键盘 -:: 首选项 -:: 本地化 » +:: Preferences +:: Locale »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    +
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    -

    keymap-icon_64.png终端键盘映射

    +

    keymap-icon_64.png键盘映射

    @@ -61,35 +61,37 @@
    桌面栏：首选项
    位置：/boot/system/preferences/Keymap


    keymap.png -

    To the right, the Keymap window shows a representation of your keyboard. When you press a key, the corresponding key is darkened and the assigned symbol is entered into the Sample and Clipboard text field at the bottom. From there you can also copy and paste it into a document.
    -Thus, the Keymap preferences are not only for configuring your local keymap, but are also useful when looking for a special symbol used in other languages. For example, you can switch the keymap to "French", find the "ç" and copy it into your mail to François. (Though you'll find the "cedil" also in other keymaps...)

    -

    Pressing modifier keys like SHIFT, CONTROL or OPTION changes the displayed keyboard accordingly.

    -

    Then there are the keys that are marked with a blue background. These keys are called Dead Keys that can change the key you press after that. If you click on such a blue key with your mouse, those changeable keys light up yellow. Click again and everything's back to normal. Examples are é, ñ, ó or ë.

    -

    Below the keyboard representation are two more options:

    +

    在面板右侧，键盘映射窗口显示了一个键盘。当你按下某个按键时，所要响应的按键将会变暗，然后指定的符号将会输入到底部的 Sample and Clipboard 文本框。您也可以从这儿复制里面的内容，将粘贴到文档中。 +
    +如此，键盘映射首选项不仅可以用于配置您的本地键盘映射，还可用于寻找其他语言的特殊符号。例如，您可以将键盘映射切换为"法语"，找出 "ç" 然后将其复制到您邮件中的 François。（尽管您也可以在其他的键盘映射中找出 "cedil"...）

    +

    按下辅助按键，例如 SHIFT，CONTROL 或者 OPTION 来改变显示的键盘类型。

    +

    还有些按键的背景标记为蓝色，这些按键称为 Dead Keys ，它们可以改变您在按下它们之后所按下的按键。如果您点击了这些蓝色的按键，那些可以改变的按键显示为黄色；再次点击，所有的按键将恢复正常。例如 é，ñ，ó或者ë。

    +

    在键盘显示的下面，还有两个选项：

    - - + +
    Select Dead Keys for setting the above mentioned blue keys.
    Switch Shortcut Key... for using the shortcut key in Windows/Linux mode, i.e. CONTROL (normally CTRL) or Haiku mode, i.e. COMMAND (normally ALT).
    Select Dead Keys 用于设置上述的蓝色按键。
    Switch Shortcut Key... 用于使用 Windows/Linux 模式的快捷键，例如 CONTROL（通常为 CTRL）或者 Haiku 模式，例如 COMMAND（通常为 ALT）。
    -

    The lists on the left offer the available pre-configured keymaps of the system, and below that, if available, user-defined maps. You can change a keymap via drag&drop in the keyboard representation: a left-click-drag copies a key, a right-click-drag exchanges the two keys.
    -When you're done you can save the result from the menu File | Save.... Your modified map will only appear in the user-defined list if it's stored in ~/config/settings/Keymap/. Otherwise you'll have to manually load it via File | Open....

    -

    To better match the Keymap panel to your physical keyboard, there are several different settings available from the Layout menu.

    -

    The font used in the keyboard representation is set from the Font menu. Note, that it may or may not contain all symbols for a specific keymap.

    -

    Finally, there's a Revert button to bring back the settings that were active when you started the Keymap preferences.

    +

    左边的列表提供了可用的系统预设值键盘映射，在它的下面还提供了可用的用户定义键盘映射。您可以通过拖拽来改变键盘映射：左键点击拖拽复制一个按键，而右键点击拖拽调换两个按键。 +
    +修改完成之后，您可以使用菜单 File | Save... 来保存结果。如果结果保存在 ~/config/settings/Keymap/，那么您修改后的映射将会只出现在用户定义的列表，否则，您需要通过 File | Open... 对其进行手动的加载。

    +

    为了使键盘映射面板更好的对应于您实际的键盘，在 Layout 菜单中有几个不同的设置可供选择。

    +

    在键盘显示面板中的字体可以通过 Font 菜单进行设置。需要注意的是，它可能不包含某种特别映射的所有符号。

    +

    最后，有一个 Revert 按钮，它用于恢复设置到键盘映射首选项启动之前的状态。

    index -Advanced keymap manipulation

    -

    There's another method to customize your keymap besides the Keymap preference panel. It involves editing a text file containing loads of hex values, which may appear daunting on first sight, but isn't really that impossible to grasp.

    -

    You can dump the current keymap with a command in Terminal:

    +高级键盘映射操作 +

    除了使用键盘映射首选项面板之外，还有一种方法可以用于定制键盘映射。它涉及到编辑包含十六进制值的文本文件，看起来难度很大，但是它并非无法掌握。

    +

    您可以在终端中使用下述命令卸载当前的键盘映射：

    keymap -d > MyKeymap

    The generated text file can then be opened in a text editor. Make sure to use a fixed font in that editor or you'll never grok that file...
    At the beginning of that file, you'll find a legend of a stylized keyboard with the hex value corresponding to each key. Below that are the actual assignments of every value. You can do all the customizing that's also available from the Keymap preference panel, and then some. If you happen to have some special keys on your keyboard, you may be able to activate them. That is, use them as ordinary keys or like an option or control key. You won't be able to, for example, have your multimedia keys de/increase the volume or start some application. For this you can use e.g. SpicyKeys.

    -

    When you're finished, you'll save the file and have your system load the modified keymap with this command:

    +

    在完成修改之后，为了保存文件，并且使系统启用修改后的键盘映射，您可以使用下述命令：

    keymap -s < MyKeymap
    -

    If you'd like to import this keymap into the Keymap panel, you have to compile it first to a binary format:

    +

    如果您希望将该键盘映射引入映射面板，您必须首先将它编译为二进制格式：

    keymap -c < MyKeymap
    -

    This will produce a file keymap.out which you can load into Keymap via its Open... menu. By the way, the keymap command is able to load this binary format as well: keymap -l < keymap.out

    -

    This is the dumped file (the rightmost keys of the stylized keyboard are cut-off for a nicer display on this page):

    +

    该命令将会创建一个文件 keymap.out，您可以通过 Open... 菜单载入键盘映射。还需要说明的是，keymap命令也可以载入该二进制格式： keymap -l < keymap.out

    +

    下面是卸载后的文件（为了使该页面有更好的显示效果，我们剪切了键盘最右边的按键设置）：

    #!/bin/keymap -s
 #
@@ -372,8 +374,8 @@ TildeTab = Normal Shift Option Option-Shift CapsLock CapsLock-Shift CapsLock-Opt
 
    
 
    
  «  键盘 
-::  首选项 
-::  本地化  »
+::  Preferences 
+::  Locale  »
 
    
 
    
 
diff --git a/userguide/zh_CN/preferences/mouse.html b/userguide/zh_CN/preferences/mouse.html
index edb101cd..2c3a1ceb 100644
--- a/userguide/zh_CN/preferences/mouse.html
+++ b/userguide/zh_CN/preferences/mouse.html
@@ -22,7 +22,7 @@
 
 
 
 
 
    
@@ -41,15 +41,14 @@
 
  • English
    • 
 
 
- «  媒体 
-::  首选项 
+ «  Media 
+::  Preferences 
 ::  网络  »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。

    mouse-icon_64.png鼠标

    @@ -60,19 +59,19 @@


    mouse.png -

    Set your type of mouse: 1, 2 or 3 button mouse. You can simulate the 2nd (=right) mouse button by holding down CTRL while left-clicking. For the 3rd (=middle) mouse button, it's CTRL ALT and a left-click. A middle-click is also simulated by clicking left and right button together. Useful for notebooks, which mostly don't have a 3rd button.

    -

    You can rearrange the mouse buttons by clicking on them and choosing their new meaning from the pop-up menu.

    -

    With the sliders to the right, you adjust double-click speed, mouse speed and acceleration.

    -

    Focus follows mouse means, that you don't have to click into a window to activate it. There are three modes:

    +

    设置鼠标类型：单键，双键或者三键鼠标。您可以通过左键点击的同时按下 CTRL 来模拟第二个鼠标键（右键）。至于第三个鼠标键（中间键），它等同于 CTRL ALT 联合左键点击。中间点击也可以使用同时按下左右键来模拟。对于笔记本电脑，通常不需要使用第三个鼠标键。

    +

    您可以通过点击在鼠标按钮，从弹出菜单中选择它们的新功能来对其进行重新排序。

    +

    使用右边的滑动条，您可以调整双击的速度，鼠标的移动速度和加速度。

    +

    Focus follows mouse 意味着，您无须点击窗口来对其进行激活。它具有三种模式：

    - - - + + +
    Enabled The window under the mouse pointer is always activated automatically, but doesn't pop to the front.
    Warping Choosing a window from Deskbar or the Twitcher will have the mouse pointer glide smoothly toward it.
    Instant-Warping Choosing a window from Deskbar or the Twitcher will have the mouse pointer jump instantly toward it.
    Enabled 鼠标指针下的窗口总是自动激活，但是不会自动弹出。
    Warping 从桌面栏或者任务切换器中选中的窗口将会平滑的获取鼠标指针。
    Instant-Warping 从桌面栏或者任务切换器中选中的窗口将会立即自动获取鼠标指针，
    -

    All settings are immediately applied.

    +

    所有的设置将会被立即应用。

    - - + +
    Defaults 恢复所有设置为默认状态。
    Revert brings back the settings that were active when you started the Mouse preferences.
    Defaults 恢复到系统默认的设置状态。
    Revert 恢复到鼠标首选项启动时的设置状态。
    @@ -80,8 +79,8 @@
    - «  媒体  -::  首选项  + «  Media  +::  Preferences  ::  网络  »
    diff --git a/userguide/zh_CN/preferences/network.html b/userguide/zh_CN/preferences/network.html index 1ea68427..e397d9ee 100644 --- a/userguide/zh_CN/preferences/network.html +++ b/userguide/zh_CN/preferences/network.html @@ -22,7 +22,7 @@
    @@ -42,14 +42,13 @@  «  鼠标  -::  首选项  -::  打印机  » +::  Preferences  +::  Printers  »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。

    network-icon_64.png网络

    @@ -60,11 +59,11 @@


    network.png -

    At the top, you choose which network adapter to configure.

    -

    Then you specify if you get your network automatically (via DHCP) or if you're using static addresses. If it's the latter, you'll have to fill out IP Address, Netmask, Gateway and DNS Servers yourself. Otherwise the panel will show the addresses currently set with DHCP.

    +

    在窗口顶部，您可以选择进行配置的网络适配器。

    +

    然后您可以指定，是否您的网络自动进行配置（通过 DHCP），是否您使用的是静态地址。如果是后一种情况，您需要手动填写自己的IP地址，子网掩码，网关和DNS服务器。否则，面板将会显示当前通过DHCP设置的地址。

    - - + +
    Revert brings back the settings that were active when you started the Network preferences.
    Apply sets the entered configuration.
    Revert 恢复到网络首选项启动时的设置状态。
    Apply 使用输入的配置信息。
    @@ -74,8 +73,8 @@
     «  鼠标  -::  首选项  -::  打印机  » +::  Preferences  +::  Printers  »
    --> diff --git a/userguide/zh_CN/preferences/touchpad.html b/userguide/zh_CN/preferences/touchpad.html index 210635fe..9b8f6138 100644 --- a/userguide/zh_CN/preferences/touchpad.html +++ b/userguide/zh_CN/preferences/touchpad.html @@ -22,7 +22,7 @@
    @@ -50,7 +50,7 @@
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    +
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.

    touchpad-icon_64.png触摸板

    @@ -71,7 +71,7 @@ The acceleration setting decides how much quicker a list scrolls by if you swish If you feel comfortable using this feature, you can dispense with setting scroll areas and instead use the whole pad for normal navigation.

    At the bottom is another slider to set the tap click sensitivity. If your taps keep getting ignored, increase the sensitivity. If the system registers clicks all the time, while all you want is to move the mouse pointer, try decreasing it.

    - +
    Defaults 恢复所有设置为默认状态。
    Defaults 恢复到系统默认的设置状态。
    Revert 返回到您启动触摸板首选项之前的设置状态。

    Here is a tip that's not related to the Touchpad preferences, but fits the general topic:
    @@ -84,8 +84,8 @@ Depending on your hardware, there's a nifty feature: just leave your finger with

    - «  Tracker 文件浏览器  -::  首选项  + «  Tracker   +::  Preferences  ::  虚拟内存  »
    diff --git a/userguide/zh_CN/preferences/tracker.html b/userguide/zh_CN/preferences/tracker.html index e2ac5040..47e57eb7 100644 --- a/userguide/zh_CN/preferences/tracker.html +++ b/userguide/zh_CN/preferences/tracker.html @@ -9,18 +9,20 @@ * * Authors: * Humdinger + * Translators: + * Pengphei Han * --> - Tracker 文件浏览器 + Tracker
    @@ -39,15 +41,15 @@
  • English
    • - «  时间  -::  首选项  + «  Time  +::  Preferences  ::  触摸板  »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    +
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.

    tracker-icon_64.pngTracker

    @@ -57,8 +59,9 @@
    ~/config/settings/Tracker/TrackerSettings


    -

    The Tracker preference panel is also available from every Tracker window with the menu Window | Preferences....
    -Its functions are discussed in the topic on Tracker.

    +

    Tracker首选项面板可以通过每个Tracker窗口的 Window | Preferences... 菜单进行启用。 +
    +有关它的功能可以查阅 Tracker 主题。

    @@ -66,8 +69,8 @@ Its functions are discussed in the topic on
    - «  时间  -::  首选项  + «  Time  +::  Preferences  ::  触摸板  »
    diff --git a/userguide/zh_CN/preferences/virtualmemory.html b/userguide/zh_CN/preferences/virtualmemory.html index 7843cdd7..2ec94bd1 100644 --- a/userguide/zh_CN/preferences/virtualmemory.html +++ b/userguide/zh_CN/preferences/virtualmemory.html @@ -22,7 +22,7 @@
    @@ -42,7 +42,7 @@  «  触摸板  -::  首选项 +::  Preferences
    @@ -63,7 +63,7 @@

    通常，交换文件将会写入到您的启动分区。如果由于虚拟内存系统的交换文件而经常导致磁盘超荷，您可以尝试使用独立的硬盘用于交换文件。简单的使用同一硬盘的其他分区用于系统和数据将不会有任何效果。
    当然，升级您的内存将会是最有效的解决方法。

    - +
    Defaults 恢复所有设置为默认状态。
    Defaults 恢复到系统默认的设置状态。
    Revert 返回到启动虚拟内存首选项之前的设置状态。
    @@ -74,7 +74,7 @@
     «  触摸板  -::  首选项 +::  Preferences
    --> diff --git a/userguide/zh_CN/queries.html b/userguide/zh_CN/queries.html index 4e81e089..83fc8d70 100644 --- a/userguide/zh_CN/queries.html +++ b/userguide/zh_CN/queries.html @@ -22,7 +22,7 @@
    @@ -42,23 +42,23 @@ « 索引 -:: 内容 -:: 操作讲解 » +:: Contents +:: Workshop »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    +
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    @@ -92,12 +92,12 @@ Even better, you don't have to double-click to re-do a query. You can index -基本查询 - "by Name" +基本查询 - "使用名字"

    If you simply want to find all files and folders on your mounted disks that match a certain pattern, simply leave the search method at by Name, enter the search term into the text box and press ENTER.

    index -标准查询 - "by Attribute"

    +标准查询 - "使用属性"

    You can create more advanced queries by searching within the attributes of specific file types. For that to work, these attributes have to be indexed.

    query-window.png

    You start by setting the filetype from All files and folders to, for example, Text | E-mail and change the search method to by Attribute.

    @@ -110,7 +110,7 @@ A good way to cut down the number of search results.

    index -高级查询 - "by Formula"

    +高级查询 - "使用表达式"

    Typing in a formula query by hand is daunting and really quite unpractical. It still has its uses.

    Take the above query by attribute of Clara's mails concerning vibraphones etc. If you have all the attributes and their search terms set, try switching to by Formula mode and be overwhelmed by this one line query string:

    formula-query.png @@ -124,7 +124,7 @@ A good way to cut down the number of search results.

    • You could copy and paste the string into an email, forum or IRC for others to use or debug.

    • You can use this method to construct a query in Attribute mode and then switch to Formula mode, to comfortably generate a search string to use for a query in Terminal or a script.

      • -

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

      • +

    • You can fine tune your query by inserting parenthesis where needed, make parts case-sensitive or negate logical combinations by changing. e.g. "==" to "!=" for a NOT AND. All you need is a basic understanding of regular expressions and maybe some scripting basics.

    @@ -154,8 +154,8 @@ By using the Save Query as Template menu item (see
    « 索引 -:: 内容 -:: 操作讲解 » +:: Contents +:: Workshop »
    diff --git a/userguide/zh_CN/tracker.html b/userguide/zh_CN/tracker.html index 69191678..7ef6812a 100644 --- a/userguide/zh_CN/tracker.html +++ b/userguide/zh_CN/tracker.html @@ -16,13 +16,13 @@ - Tracker 文件浏览器 + Tracker
    @@ -41,15 +41,15 @@
  • English
    • - « 程序监控器 -:: 内容 -:: Tracker 附加组件 » + « Team Monitor +:: Contents +:: Tracker Add-Ons »
    -
    本节的翻译还未完成。在未完成之前，所有的未完成部分都将使用英语原文。
    +
    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.

    索引
    查询窗口
    - 基本查询 - "by Name"
    - 标准查询 - "by Attribute"
    - 高级查询 - "by Formula"
    + 基本查询 - "使用名字"
    + 标准查询 - "使用属性"
    + 高级查询 - "使用表达式"
    结果窗口
    查询模板
    @@ -64,7 +64,7 @@
    -

    Tracker 文件浏览器

    +

    Tracker

    Tracker是所有文件的图形界面显示工具。它允许您新建文件和文件夹，复制和删除文件，并且还可以对文件进行查询，启动和重命名等操作。

    同其他的应用程序一样 (the Desktop with its icons is really just a fullscreen window in the background)，Tracker与它的窗口出现在桌面栏，并且可以关闭和重启。 The easiest way to quit and restart a crashed or frozen Tracker (or a wayward Deskbar) is to call the Team Monitor.

    @@ -72,22 +72,23 @@

    index 挂载磁卷

    -

    In order to access a harddisk, CD, USB stick etc., you first have to mount the volume, that is, let the system know it's there. This is done with a right-click on the Desktop or an already mounted volume (like the boot disk) and choosing the volume from the Mount submenu. You find the same Mount menu in the Deskbar.

    +

    为了能够访问硬盘，CD，USB磁盘等，您首先需要挂载这些磁卷，也就是告诉系统，它们存在。 右键点击桌面，或者已经挂载的刺卷（如启动盘），然后从 Mount 子菜单中选择磁卷。您也可以在桌面栏中找到相同的 Mount 菜单。

    drill-down.png -

    There are also Mount Settings so you don't have to mount everything manually after every bootup.
    -The above settings will automatically mount any storage device you connect/insert and also mount all disks on bootup that were mounted previously.

    -
    Before you disconnect e.g. a harddrive or USB stick, make sure you have successfully unmounted the volume. This guarantees that all data transfer has finished. Otherwise you may lose data or corrupt the disk!
    +

    还有一个 Mount Settings ，因此你不需要每次启动时都手动挂载所有磁卷。 +
    +上述的设置将会自动挂载您所连接/插入的所有存储设备，然后在启动时挂载所有曾经挂载过的磁盘。

    +
    在您断开硬件设备或者USB磁盘的连接时，一定要保证您已经成功的卸载了该磁卷。这样可以保证所有的数据传输已经结束，否则可能会导致数据的丢失或者损坏磁盘。

    index 文件导航

    -

    By default, when you double-click a folder, Tracker opens a new window while leaving the parent window open. This can quickly lead to an overcrowded desktop.
    -You can prevent that by holding down the OPT key, which automatically closes the parent window.
    -This is also true for keyboard navigation. For more on that, see topic Shortcuts and key combinations.

    +

    默认情况下，双击文件夹，Tracker打开新窗口，并且保持先前的打开窗口。这将会很快导致桌面的拥挤。
    +您可以使用 OPT 键来阻止这种情况发生，它将会自动关闭先前的窗口。
    +这也同样适用于键盘导航，更多的信息可以参阅主题 快捷键和组合键。

    Moving through your folders is one of Trackers main purposes, just like the file managers on other platforms. Haiku's Tracker has some unique features that will help you doing that efficiently.

    -indexDrilling down the submenus

    +index进入子菜单

    Instead of double-clicking your way down folder after folder, there's a better way to drill down:

    drill-down.png @@ -126,7 +127,7 @@ This type-ahead filtering is set in the Trac @@ -193,9 +194,9 @@ This type-ahead filtering is set in the Trac
    - « 程序监控器 -:: 内容 -:: Tracker 附加组件 » + « Team Monitor +:: Contents +:: Tracker Add-Ons »
    diff --git a/userguide/zh_CN/workshop-filetypes+attributes.html b/userguide/zh_CN/workshop-filetypes+attributes.html index a06fa68d..74669628 100644 --- a/userguide/zh_CN/workshop-filetypes+attributes.html +++ b/userguide/zh_CN/workshop-filetypes+attributes.html @@ -16,13 +16,13 @@ - 讨论：文件类型， 属性，索引和查询 + 操作练习：文件类型， 属性，索引和查询
    @@ -42,8 +42,8 @@ « 查询 -:: 内容 -:: 应用程序 » +:: Contents +:: Applications »
    @@ -70,7 +70,7 @@ -

    讨论：文件类型， 属性，索引和查询

    +

    操作练习：文件类型， 属性，索引和查询

    本篇文档主要用于展示 属性，查询，索引和定制文件类型。我们将会创建一个数据库来记录我们的DVD库。

    @@ -222,8 +222,8 @@ mkindex -t int DVDdb:rating
    « 查询 -:: 内容 -:: 应用程序 » +:: Contents +:: Applications »
    diff --git a/welcome/de/bugreports.html b/welcome/de/bugreports.html index c6740420..4ec50e48 100644 --- a/welcome/de/bugreports.html +++ b/welcome/de/bugreports.html @@ -4,25 +4,27 @@ - Fehler melden + Bugs melden
    @@ -48,48 +50,108 @@
    -

    Fehler melden

    + + + +
    Bugs melden
    Zugang zu Trac
    + Bugreport erstellen
    + Bugs in Anwendungen
    + Bugs in Servern
    + Bugs im Kernel
    + Kernel Debugging Land - KDL
    + Syslog
    + Debug Ausgabe auf dem Bildschirm
    + Bugs von Hardware/Treiber
    + Bug gemeldet, und dann?
    -

    Da es für die Haiku-Entwickler unmöglich ist, jede denkbare Hardware-Kombination oder jede mögliche Anwendungsweise eines Programmes zu testen, ist es eine große Hilfe, wenn erkannte Fehler von Anwendern gemeldet werden. Da Haiku noch nicht vollständig ausgereift ist - aktuell befindet es sich in der Alpha-Phase - ist es nicht unwahrscheinlich, dass Fehler auftreten. Nur mit Hilfe der Anwender können wir Haiku Stück für Stück perfektionieren.

    -

    Um unseren "Bugtracker" - also die Liste aller gefundenen Fehler - effektiv zu halten, ist es notwendig, eine grundlegende Etikette, die "Bug Tracker Etiquette" zu wahren.

    +

    Bugs melden

    -

    Wie man einen Zugang zum Trac erhält

    -

    Um ein Fehler-Ticket einzureichen, muss man registrierter Benutzer beim Bugtracker sein.
    Um sich anzumelden ist eine gültige E-Mail Adresse notwendig. Sollte nach dem Anmelden keine Bestätigungsmail erhalten werden, lohnt es sich, seinen Spam-Filter zu überprüfen.

    +

    Da es für die Haiku-Entwickler unmöglich ist, jede denkbare Hardware-Kombination oder jede mögliche Anwendungsweise eines Programms zu testen, ist es eine große Hilfe, wenn Fehler gemeldet werden. Da Haiku noch recht jung ist, sind Bugs nicht Ungewöhnliches. Nur mit Hilfe der Anwender können wir Haiku gemeinsam Stück für Stück perfektionieren.

    +

    Damit unser "Bugtracker" - also die Liste aller gefundenen Fehler - effektiv funktioniert, ist eine grundlegende Bug Tracker Etiquette zu wahren.

    -

    Einen Fehlerbericht erstellen

    -

    Ehe man einen Fehler meldet, sollte man sich sicher sein, dass er nicht schon gemeldet wurde. Hierzu kann auch die Suchfunktion verwendet werden.
    +

    index +Zugang zu Trac

    +

    Um ein Fehler-Ticket aufzugeben, muss man registrierter Benutzer beim Bugtracker sein.
    Um sich anzumelden ist eine gültige E-Mail Adresse notwendig. Sollte nach dem Anmelden keine Bestätigungsmail ankommen, sollte man mal seinen Spam-Ordner überprüfen.

    + +

    index +Bugreport erstellen

    +

    Bevor man einen Fehler meldet, sollte man sich sicher sein, dass das nicht schon geschehen ist. Hierzu kann auch die Suchfunktion verwendet werden.
    Nach dieser Überprüfung sollte man so genau wie möglich den Fehler beschreiben:

      -

    • Wie wurde Haiku verwendet (auf echter Hardware oder virtualisiert unter VMWare, QEMU oder ähnlichem)

      • -

    • Welche Versionsnummer des SVN wurde verwendet?. Die Nummer ist auch unter 'About This System...' im Deskbar-Menü abzulesen.

      • -

    • Der Fehler sollte so präzise wie möglich beschrieben werden. Wie war das tatsächliche Verhalten im Gegensatz zum Erwarteten?

      • -

    • Wann ist der Fehler aufgetreten? Welche Schritte führten dazu? Nur so können die Entwickler den Fehler nachstellen und erkennen.

      • -

    • An den Fehlerbericht sollten so viele Informationen wie möglich angehängt werden. Log-Dateien oder Bildschirmphotos (die Taste PRINT speichert den Bildschirm als PNG im Verzeichnis /boot/home/) sind sehr hilfreich.

      • +

    • Der Fehler sollte mit einer aktuellen Version von Haiku zu reproduzierbar sein. Zum Testen gibt es installierbare Images.

      • +

    • Wie wurde Haiku verwendet (auf echter Hardware oder virtualisiert unter VMWare, QEMU oder ähnlichem)?

      • +

    • Welche Versionsnummer aus dem SVN wurde verwendet? Die Version ist auch unter About Haiku... im Deskbar Menü zu finden. Wie genau Haiku kompiliert wurde (gcc2, gcc4, gcc2hybrid, gcc4hybrid), ist ebenfalls von Interesse. Die runterladbaren Images sind entsprechend benannt; Leute, die sich ihr Haiku selber zusammenbauen, sollten wissen wie sie das gemacht haben.

      • +

    • Der Fehler sollte so präzise wie möglich beschrieben werden. Welches Verhalten wurde erwartet und was wurde statt dessen beobachtet?

      • +

    • Wann tritt der Fehler auf? Nur mit einer Schritt-für-Schritt Anleitung können die Entwickler den Bug nachstellen und beheben.

      • +

    • An den Fehlerbericht sollten so viele Informationen wie möglich angehängt werden. Handelt es sich um einen Bug in der grafischen Oberfläche oder einer der Anwendungen, ist ein Bildschirmfoto mittels der DRUCK Taste hilfreich.

    -

    Fehler in Anwendungen

    -

    Wenn eine Anwendung unerwartet abstürzt, sollte man den "Debugger" aus dem erscheinenden Hinweisfenster aufrufen. Ein bt im daraufhin startenden Terminal erstellt einen sogenannten "backtrace" der mit an die Fehlermeldung angehängt werden sollte.

    +

    index +Bugs in Anwendungen

    +

    Stürzt eine Anwendung ab, sollte man den Debugger aus dem erscheinenden Hinweisfenster aufrufen. Dadurch wird ein Terminal mit gdb (dem GNU Debugger) geöffnet. Gibt man dort bt ein, wird ein sogenannter "backtrace" erstellt, der komplett (auch mit dem Teil bevor bt eingegeben wurde) mit an die Fehlermeldung angehängt werden sollte.

    -

    Fehler auf Grund Hardware

    -

    Wenn ein Fehler gemeldet wird, der Hardware oder Treiber betrifft, sollten mindestens diese Informationen an den Fehlerbericht angehängt werden:

    +

    index +Bugs in Servern

    +

    Stürzen lebenswichtige Server wie der App Server, der Registrar oder der Input Server ab, bekommt man nicht den gewöhnlichen Crash-Hinweis zu sehen. Stattdessen wird der gesamte Bildschirm weiß und der gdb wird gestartet, der seine Ausgabe direkt auf den Bildschirm schreibt. Unter Umständen kann man immer noch die Maus bewegen, die daraufhin das Weiß und die gdb Ausgabe übermalt. Noch laufende Anwendungen wie ProcessController oder die Uhr in der Deskbar, tun das vielleicht auch noch.
    +Außer dass alles etwas unansehnlicher und unbequemer ist, gilt eigentlich das gleiche wie für Bugs in Anwendungen. Am wichtigsten ist das sichern eines "backtrace" mittels bt. Weil man den Text ja nicht mehr irgendwohin kopieren kann, müsste man die Ausgabe per Kamera festhalten.

    + +

    index +Bugs im Kernel

    +

    Fehler im Kernel haben normalerweise die schwersten Auswirkungen und sind zugleich am schwierigsten zu debuggen. Es gibt unterschiedliche Symptome, die auf ein Problem von Kernel oder Treiber hindeuten:

      -
    • listdev - eine detaillierte Auflistung aller vorhandener Hardware inklusive "vendor id" und "pci id"; ähnlich den Befehlen lshw und lspci unter Linux.
      • -
    • listusb -v - bei einem Fehler im Zusammenhang mit USB; ähnlich dem Befehlt lsusb.
      • -
    • open /var/log/syslog - die zentrale Log-Datei in Haiku. Mit dem Befehl open kann das Log auf eine sinnvolle Länge gekürzt werden.
      • -
    • listimage | grep drivers/ - eine Auflistung aller verwendeter Treiber.
      • -
    • ints - nur im Kernel Debugging Land (siehe weiter unten) möglich. Es zeigt eine Liste aller verwendeter "Interrupts".
      • +

    • Das System betritt selbständig das Kernel Debugging Land (KDL) . Der obere Teil des Bildschirms wird weiß und einige Zeilen Text erscheinen. Die zweite Zeile verkündet "Welcome to Kernel Debugging Land...", die darüber beschreibt den unmittelbaren Grund für die Reise ins KDL.

      • +

    • Das System führt einen spontanen Neustart aus.

      • +

    • Das System friert komplett ein. Die Maus lässt sich nicht mehr bewegen und Anwendungen aktualisieren ihre Oberfläche nicht mehr. Ein wichtiger Test in so einer Situation ist, ob man das KDL noch mit der Tastenkombination ALT SysReq D (SysReq ist dabei meist die DRUCK Taste) erreichen kann. Man sollte zumindest eine Minute warten, ob sich was tut.

      • +

    • Das System fährt nicht mehr richtig hoch. Unter Umständen führt es spontan einen Neustart durch oder bleibt an einer Stelle stecken, vielleicht bei einem bestimmten Symbol des Boot Bildschirms. In letzterem Falle sollte man auch mal ein ALT SysReq D versuchen.

      • +

    • Das ganze System oder eine bestimmte Hardwarekomponente funktioniert nicht richtig. Es könnte beispielsweise nur sehr langsam laufen, Fehler könnten auftreten oder etwas funktioniert überhaupt nicht. Verweigert eine Hardwarekomponente die Arbeit komplett, sollte man natürlich erst mal checken, ob Haiku sie momentan überhaupt treibermäßig unterstützt, indem man zum Beispiel auf der Mainlingliste oder im Forum nachfragt.

    -

    Die genannten Befehle sind im Terminal einzugeben. Mit dem Anhang " > output.txt" an den Befehl wird dessen Ausgabe in die Datei output.txt gespeichert, die dann an den Fehlerbericht angehängt werden kann.

    +

    Während nur der letzte Punkt explizit auf eine Hardware-Ursache eingeht, können auch alle anderen Symptome auf Fehler in einem Hardware Treiber hindeuten. Hat man einen Verdacht welche Hardware oder entsprechender Treiber mit dem Problem zu tun haben könnte, sollte man prüfen ob das Entfernen oder Deaktivieren von Hardware oder Treiber Abhilfe schafft. Wenn man das Problem beispielsweise beim WLAN vermutet, könnte diese Funktion vielleicht im BIOS ausgeschaltet werden. Wenn nicht, kann man auch den entsprechenden Treiber aus dem System entfernen (in /boot/system/add-ons/kernel/drivers/bin).

    -

    Kernel Debugging Land - KDL

    -

    Wenn grundlegende Systemkomponenten abgestürzt sind, dann friert das System ein und es wird das KDL aufgerufen. Man kann auch absichtlich dorthin wechseln durch Drücken von ALTSysReqD (SysReq ist in den meisten Fällen die Taste PRINT).

    -
      -
    • co - beendet das KDL und das System läuft - soweit möglich - normal weiter.
      • -
    • int - zeigt die verwendeten Interrupts (wie oben beschrieben).
      • -
    • bt - zeigt einen backtrace wo genau der Fehler aufgetreten ist.
      • -
    +

    index +Kernel Debugging Land - KDL

    +

    Stürzt das System nicht von selbst ins KDL, kann man das auch absichtlich mit der Tastenkombination ALTSysReqD erreichen.
    +Im KDL kann es passieren, dass die Tastatur nicht mehr funktioniert. PS/2 Tastaturen gehen immer, USB Tastaturen an UHCI Controllern nur wenn man vorher schonmal per Tastenkombination das KDL betreten hat. USB OHCI wird zur Zeit noch gar nicht unterstützt.

    +

    Das KDL ist eine Art Konsole. Es lassen sich Befehle eingeben, die Informationen über das System ausgeben. Folgende Befehle sind von besonderen Interesse:

    + + + + + +
    bt (auch "sc") Zeigt einen "backtrace" wo genau der Fehler aufgetreten ist. Ist das System von selbst ins KDL gefallen, sollte man diesen Befehl unbedingt ausführen.
    ints Zeigt die unbenutzten und verwendeten Interrupts.
    co (auch "continue") Verlässt den Kernel Debugger und das System läuft - soweit möglich - normal weiter.
    reboot Führt einen unmittelbaren Neustart durch. Alle ungespeicherten Daten gehen verloren und selbst was man gespeichert hat, aber noch nicht auf die Platte geschrieben wurde, ist weg.
    +

    Weitere Infos gibt es im Artikel Welcome to Kernel Debugging Land (Englisch).

    +

    Die Ausgaben im KDL werden zum seriellen Port geschickt (falls man einen hat und ein entsprechendes Nullmodemkabel samt zweiten Rechner, kann man die Ausgaben in einem Terminalprogramm aufnehmen). Außerdem werden sie ins Syslog geschrieben. Wenn man das KDL allerdings nicht verlassen kann, wird auch nichts ins Syslog geschrieben. Es gibt aber eine Bootloader Debug Option, die das trotzdem möglich macht (siehe weiter unten).

    -

    Fehler gemeldet, und dann?

    +

    index +Syslog

    +

    Dies ist die beste Methode Informationen über ein nicht-bootendes System zu gewinnen.
    +Das Syslog (kurz für System Log) enthält wertvolle Infos was im System abläuft, einschließlich der Ausgaben einer KDL Sitzung. Man sollte es immer an einen Trac Ticket hängen wenn es etwas mit dem Kernel zu tun haben könnte. Das Syslog befindet sich in der Datei /boot/common/var/log/syslog. Um in eine Datei schreiben zu können, braucht man ein funktionierendes System. Tritt ein Problem im Kernel auf (insbesondere bei spontanen Neustarts und nicht-fortsetzbaren KDL Sitzungen), kann es daher passieren dass es die letzten Ausgaben nicht mehr ins Syslog schaffen.

    +

    Durch die Option Enable debug syslog im Debug menu des Bootloaders wird das Syslog im Speicher etwas langlebiger. Das ist standardmäßig aktiviert. "Etwas langlebiger" bedeutet, dass es einen Reset überlebt und direkt danach noch im Bootloader verfübar ist. Bootet man allerdings ein Betriebssystem (zumindest bei Haiku, wahrscheinlich aber bei allen), werden diese Informationen zerstört. Man muss beim Neustart also unbedingt das Bootloader Menü mittels gedrückter SHIFT Taste aufrufen.
    +Dort sollte man im Debug menu jetzt die Einträge Display syslog from previous session und Save syslog from previous session sehen. Ersterer zeigt das Syslog direkt auf dem Bildschirm an, mit letzterem lässt es sich speichern. Momentan geht das nur auf FAT32 formatierten Medien. Möchte man dafür einen USB-Stick benutzen, den man allerdings erst zu spät reingesteckt hat und der deswegen nicht erkannt wurde, kann man den Rechner nochmals resetten und das Bootloader Menü erneut aufrufen. Es gilt aber immer noch: Bootet man ausversehen ein Betriebssystem, sind die Syslog Daten weg.

    + +

    index +Debug Ausgabe auf den Bildschirm

    +

    Die Ausgabe auf dem Bildschirm ist nur bei ganz bestimmten Situationen sinnvoll und hat bekanntermaßen Timing-Probleme. Es sollte also wirklich nur im Notfall benutzt werden.
    +Das ist zum Beispiel der Fall wenn Haiku nicht ganz hochfährt und Bootloader's Debug syslog option irgendwie nicht funktioniert. Noch bevor das Haiku Bootlogo erscheint, die SHIFT Taste gedrückt halten, um das Bootloader Menü aufzurufen. Von hier in das Menü Select safe mode options wechseln und dort weiter unten [ ] Enable on screen debug output aktivieren. (Die anderen Optionen kann man auch mal probieren, um zu versuchen Haiku erfolgreich zu booten. Wenn Haiku nur mit einer oder mehreren aktivierten Optionen hochfahren kann, sollte man natürlich erwähnen welche das sind.)
    +Abschließend geht man auf Return to main menu und dann Continue booting.
    +Auf dem Bildschirm werden einige Seiten Text ausgegeben, von denen aber nur die letzten paar für einen Bugreport interessant sind. Der Userguide hat noch weitere Infos zum Boot Loader.

    + +

    index +Bugs von Hardware/Treiber

    +

    Wenn ein Fehler gemeldet wird, der Hardware oder Treiber betrifft, sollten folgende Informationen als Textdateien an den Fehlerbericht angehängt werden:

    + + + + + + + + +
    - listdev Eine detaillierte Auflistung aller vorhandener Hardware inklusive "vendor id" und "pci id"; ähnlich den Befehlen lshw und lspci unter Linux.
    - listusb -v Bei Fehlern im Zusammenhang mit USB, ähnlich dem Befehlt lsusb unter Linux.
    - open /var/log/syslog Die zentrale Log-Datei von Haiku. Mit dem Befehl open kann das Log im Texteditor auf eine sinnvolle Länge gekürzt werden.
    - listimage | grep drivers/ Eine Auflistung aller verwendeten Treiber.
    - ints Nur im Kernel Debugging Land (siehe weiter oben). Es zeigt eine Liste aller verwendeter "Interrupts". Wenn sich mehrere Geräte zuviele von ihnen teilen, ist das schlecht.
    - "On screen debug output" (die Bootloader Debug Option zur Ausgabe auf dem Bildschirm).
    + +

    Die ersten vier dieser Befehle sind im Terminal einzugeben. Mit dem Zusatz " > output.txt" an den Befehl wird dessen Ausgabe in die Datei "output.txt" gespeichert, die dann an den Fehlerbericht angehängt werden kann.

    + +

    index +

    Nachdem ein Fehler gemeldet wurde wird sich ein Entwickler ihm annehmen und bewerten. Da es sich bei allen Entwicklern um Freiwillige handelt, die in ihrer Freizeit programmieren, kann es durchaus etwas dauern, bis man eine Rückmeldung erhält. Je mehr Informationen man einer Fehlermeldung beifügt oder nachreicht, um so leichter ist es für den Programmierer, diesen zu beheben.

    Wenn man einen Fehler gemeldet hat ist es damit nicht abgeschlossen, eigentlich ist es erst der Anfang und man wird Teil des Entwicklungs-Prozesses von Haiku. Es ist durchaus möglich und eigentlich auch zu erwarten, dass sich ein Entwickler meldet, um näheres zu den Umständen des Fehler-Reports zu erfahren. Hier gilt wieder: je mehr man dem Entwickler helfen kann, um so leichter tut er sich mit der Fehlerbehebung. Erst wenn der Fehler als 'fixed' - also behoben - markiert ist, kann man sich zurücklehnen, mit dem guten Gefühl etwas beigetragen zu haben.

    diff --git a/welcome/en/bugreports.html b/welcome/en/bugreports.html index d7ff6798..274a5495 100644 --- a/welcome/en/bugreports.html +++ b/welcome/en/bugreports.html @@ -4,11 +4,12 @@ @@ -46,49 +47,109 @@
    + + + +
    Reporting bugs
    Getting a Trac account
    + Creating a bug report
    + Application bugs
    + Server bugs
    + Kernel bugs
    + Kernel Debugging Land - KDL
    + Syslog
    + On screen debug output
    + Hardware/Driver bugs
    + What's next?
    +

    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

    +

    index +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

    +

    index +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:

      +

    • Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  available.

    • 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.

      • +

    • Mention which revision from SVN you are running. You can find this information in About Haiku... from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.

    • 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/).

      • +

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the PRINT key.

    -

    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.

    +

    index +Application bugs

    +

    When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering bt, you create a "backtrace" that you should copy in its entirety (including the part before you entered the bt command) and attach it to the ticket.

    -

    Hardware Bugs

    -

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

    +

    index +Server bugs

    +

    When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.
    +Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (bt command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.

    + +

    index +Kernel bugs

    +

    Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:

      -
    • 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.
      • +

    • The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "Welcome to Kernel Debugging Land...", the one above it states the immediate reason for entering KDL.

      • +

    • The system reboots spontaneously.

      • +

    • The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut ALT SysReq D (SysReq being PRINT on most keyboards). Wait at least a minute to see, if anything happens.

      • +

    • The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try ALT SysReq D.

      • +

    • The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).

    -

    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.

    +

    Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in /boot/system/add-ons/kernel/drivers/bin).

    -

    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.
      • -
    +

    index +Kernel Debugging Land - KDL

    +

    If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut ALT SysReq D.
    +Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.

    +

    KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:

    + + + + + +
    bt (aka sc) Prints a back trace. If the system entered KDL on its on volition, always enter that one.
    ints Shows the handled and unhandled hardware interrupts.
    co (aka continue) Leaves the kernel debugger and continues normal operation of the system, if that is possible.
    reboot Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.
    +

    For more information, see the article Welcome to Kernel Debugging Land.

    +

    The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).

    -

    What's next?

    +

    index +Syslog

    +

    This is the preferred method for gaining information from a non-booting system.
    +The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file /boot/common/var/log/syslog. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).

    +

    The option Enable debug syslog in the boot loader's Debug menu makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down SHIFT while booting.
    +In the boot loader's Debug menu you should now find the entries Display syslog from previous session and Save syslog from previous session. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.

    + +

    index +On screen debug output

    +

    The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.
    +This is only relevant when Haiku fails to boot on your machine and the Debug syslog option doesn't work for some reason. Before the Haiku boot logo appears, hold SHIFT to enter the boot loader menu. Select Select safe mode options. Near the bottom, [ ] Enable on screen debug output will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)
    +Finally select Return to main menu and then Continue booting.
    +One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the Boot Loader.

    + +

    index +Hardware/Driver bugs

    +

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

    + + + + + + + + +
    - 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 above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
    - On screen debug output (a safe mode boot time option).
    + +

    The first four commands are entered 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.

    + +

    index +

    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 diff --git a/welcome/es/bugreports.html b/welcome/es/bugreports.html index cd99c977..ab80da1b 100644 --- a/welcome/es/bugreports.html +++ b/welcome/es/bugreports.html @@ -4,11 +4,12 @@ @@ -47,49 +48,109 @@

    La traduzione di questa pagina non è stata completata. Per questo motivo le parti non tradotte sono visibili in inglese.
    + + + +
    Reporting bugs
    Getting a Trac account
    + Creating a bug report
    + Application bugs
    + Server bugs
    + Kernel bugs
    + Kernel Debugging Land - KDL
    + Syslog
    + On screen debug output
    + Hardware/Driver bugs
    + What's next?
    +

    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

    +

    index +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

    +

    index +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:

      +

    • Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  available.

    • 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.

      • +

    • Mention which revision from SVN you are running. You can find this information in About Haiku... from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.

    • 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/).

      • +

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the PRINT key.

    -

    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.

    +

    index +Application bugs

    +

    When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering bt, you create a "backtrace" that you should copy in its entirety (including the part before you entered the bt command) and attach it to the ticket.

    -

    Hardware Bugs

    -

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

    +

    index +Server bugs

    +

    When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.
    +Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (bt command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.

    + +

    index +Kernel bugs

    +

    Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:

      -
    • 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.
      • +

    • The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "Welcome to Kernel Debugging Land...", the one above it states the immediate reason for entering KDL.

      • +

    • The system reboots spontaneously.

      • +

    • The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut ALT SysReq D (SysReq being PRINT on most keyboards). Wait at least a minute to see, if anything happens.

      • +

    • The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try ALT SysReq D.

      • +

    • The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).

    -

    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.

    +

    Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in /boot/system/add-ons/kernel/drivers/bin).

    -

    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.
      • -
    +

    index +Kernel Debugging Land - KDL

    +

    If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut ALT SysReq D.
    +Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.

    +

    KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:

    + + + + + +
    bt (aka sc) Prints a back trace. If the system entered KDL on its on volition, always enter that one.
    ints Shows the handled and unhandled hardware interrupts.
    co (aka continue) Leaves the kernel debugger and continues normal operation of the system, if that is possible.
    reboot Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.
    +

    For more information, see the article Welcome to Kernel Debugging Land.

    +

    The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).

    -

    What's next?

    +

    index +Syslog

    +

    This is the preferred method for gaining information from a non-booting system.
    +The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file /boot/common/var/log/syslog. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).

    +

    The option Enable debug syslog in the boot loader's Debug menu makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down SHIFT while booting.
    +In the boot loader's Debug menu you should now find the entries Display syslog from previous session and Save syslog from previous session. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.

    + +

    index +On screen debug output

    +

    The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.
    +This is only relevant when Haiku fails to boot on your machine and the Debug syslog option doesn't work for some reason. Before the Haiku boot logo appears, hold SHIFT to enter the boot loader menu. Select Select safe mode options. Near the bottom, [ ] Enable on screen debug output will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)
    +Finally select Return to main menu and then Continue booting.
    +One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the Boot Loader.

    + +

    index +Hardware/Driver bugs

    +

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

    + + + + + + + + +
    - 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 above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
    - On screen debug output (a safe mode boot time option).
    + +

    The first four commands are entered 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.

    + +

    index +

    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 diff --git a/welcome/jp/bugreports.html b/welcome/jp/bugreports.html index 98306e26..7805e43b 100644 --- a/welcome/jp/bugreports.html +++ b/welcome/jp/bugreports.html @@ -4,11 +4,12 @@ @@ -47,49 +48,109 @@

    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    + + + +
    Reporting bugs
    Getting a Trac account
    + Creating a bug report
    + Application bugs
    + Server bugs
    + Kernel bugs
    + Kernel Debugging Land - KDL
    + Syslog
    + On screen debug output
    + Hardware/Driver bugs
    + What's next?
    +

    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

    +

    index +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

    +

    index +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:

      +

    • Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  available.

    • 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.

      • +

    • Mention which revision from SVN you are running. You can find this information in About Haiku... from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.

    • 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/).

      • +

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the PRINT key.

    -

    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.

    +

    index +Application bugs

    +

    When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering bt, you create a "backtrace" that you should copy in its entirety (including the part before you entered the bt command) and attach it to the ticket.

    -

    Hardware Bugs

    -

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

    +

    index +Server bugs

    +

    When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.
    +Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (bt command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.

    + +

    index +Kernel bugs

    +

    Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:

      -
    • 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.
      • +

    • The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "Welcome to Kernel Debugging Land...", the one above it states the immediate reason for entering KDL.

      • +

    • The system reboots spontaneously.

      • +

    • The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut ALT SysReq D (SysReq being PRINT on most keyboards). Wait at least a minute to see, if anything happens.

      • +

    • The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try ALT SysReq D.

      • +

    • The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).

    -

    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.

    +

    Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in /boot/system/add-ons/kernel/drivers/bin).

    -

    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.
      • -
    +

    index +Kernel Debugging Land - KDL

    +

    If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut ALT SysReq D.
    +Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.

    +

    KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:

    + + + + + +
    bt (aka sc) Prints a back trace. If the system entered KDL on its on volition, always enter that one.
    ints Shows the handled and unhandled hardware interrupts.
    co (aka continue) Leaves the kernel debugger and continues normal operation of the system, if that is possible.
    reboot Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.
    +

    For more information, see the article Welcome to Kernel Debugging Land.

    +

    The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).

    -

    What's next?

    +

    index +Syslog

    +

    This is the preferred method for gaining information from a non-booting system.
    +The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file /boot/common/var/log/syslog. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).

    +

    The option Enable debug syslog in the boot loader's Debug menu makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down SHIFT while booting.
    +In the boot loader's Debug menu you should now find the entries Display syslog from previous session and Save syslog from previous session. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.

    + +

    index +On screen debug output

    +

    The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.
    +This is only relevant when Haiku fails to boot on your machine and the Debug syslog option doesn't work for some reason. Before the Haiku boot logo appears, hold SHIFT to enter the boot loader menu. Select Select safe mode options. Near the bottom, [ ] Enable on screen debug output will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)
    +Finally select Return to main menu and then Continue booting.
    +One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the Boot Loader.

    + +

    index +Hardware/Driver bugs

    +

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

    + + + + + + + + +
    - 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 above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
    - On screen debug output (a safe mode boot time option).
    + +

    The first four commands are entered 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.

    + +

    index +

    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 diff --git a/welcome/pt_PT/bugreports.html b/welcome/pt_PT/bugreports.html index 22a61629..93efbe05 100644 --- a/welcome/pt_PT/bugreports.html +++ b/welcome/pt_PT/bugreports.html @@ -4,11 +4,12 @@ @@ -47,49 +48,109 @@

    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    + + + +
    Reporting bugs
    Getting a Trac account
    + Creating a bug report
    + Application bugs
    + Server bugs
    + Kernel bugs
    + Kernel Debugging Land - KDL
    + Syslog
    + On screen debug output
    + Hardware/Driver bugs
    + What's next?
    +

    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

    +

    index +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

    +

    index +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:

      +

    • Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  available.

    • 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.

      • +

    • Mention which revision from SVN you are running. You can find this information in About Haiku... from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.

    • 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/).

      • +

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the PRINT key.

    -

    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.

    +

    index +Application bugs

    +

    When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering bt, you create a "backtrace" that you should copy in its entirety (including the part before you entered the bt command) and attach it to the ticket.

    -

    Hardware Bugs

    -

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

    +

    index +Server bugs

    +

    When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.
    +Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (bt command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.

    + +

    index +Kernel bugs

    +

    Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:

      -
    • 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.
      • +

    • The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "Welcome to Kernel Debugging Land...", the one above it states the immediate reason for entering KDL.

      • +

    • The system reboots spontaneously.

      • +

    • The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut ALT SysReq D (SysReq being PRINT on most keyboards). Wait at least a minute to see, if anything happens.

      • +

    • The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try ALT SysReq D.

      • +

    • The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).

    -

    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.

    +

    Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in /boot/system/add-ons/kernel/drivers/bin).

    -

    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.
      • -
    +

    index +Kernel Debugging Land - KDL

    +

    If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut ALT SysReq D.
    +Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.

    +

    KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:

    + + + + + +
    bt (aka sc) Prints a back trace. If the system entered KDL on its on volition, always enter that one.
    ints Shows the handled and unhandled hardware interrupts.
    co (aka continue) Leaves the kernel debugger and continues normal operation of the system, if that is possible.
    reboot Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.
    +

    For more information, see the article Welcome to Kernel Debugging Land.

    +

    The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).

    -

    What's next?

    +

    index +Syslog

    +

    This is the preferred method for gaining information from a non-booting system.
    +The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file /boot/common/var/log/syslog. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).

    +

    The option Enable debug syslog in the boot loader's Debug menu makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down SHIFT while booting.
    +In the boot loader's Debug menu you should now find the entries Display syslog from previous session and Save syslog from previous session. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.

    + +

    index +On screen debug output

    +

    The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.
    +This is only relevant when Haiku fails to boot on your machine and the Debug syslog option doesn't work for some reason. Before the Haiku boot logo appears, hold SHIFT to enter the boot loader menu. Select Select safe mode options. Near the bottom, [ ] Enable on screen debug output will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)
    +Finally select Return to main menu and then Continue booting.
    +One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the Boot Loader.

    + +

    index +Hardware/Driver bugs

    +

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

    + + + + + + + + +
    - 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 above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
    - On screen debug output (a safe mode boot time option).
    + +

    The first four commands are entered 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.

    + +

    index +

    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 diff --git a/welcome/ru/bugreports.html b/welcome/ru/bugreports.html index 3830d155..1fb3694b 100644 --- a/welcome/ru/bugreports.html +++ b/welcome/ru/bugreports.html @@ -4,11 +4,12 @@ @@ -47,49 +48,109 @@

    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    + + + +
    Reporting bugs
    Getting a Trac account
    + Creating a bug report
    + Application bugs
    + Server bugs
    + Kernel bugs
    + Kernel Debugging Land - KDL
    + Syslog
    + On screen debug output
    + Hardware/Driver bugs
    + What's next?
    +

    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

    +

    index +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

    +

    index +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:

      +

    • Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  available.

    • 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.

      • +

    • Mention which revision from SVN you are running. You can find this information in About Haiku... from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.

    • 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/).

      • +

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the PRINT key.

    -

    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.

    +

    index +Application bugs

    +

    When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering bt, you create a "backtrace" that you should copy in its entirety (including the part before you entered the bt command) and attach it to the ticket.

    -

    Hardware Bugs

    -

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

    +

    index +Server bugs

    +

    When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.
    +Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (bt command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.

    + +

    index +Kernel bugs

    +

    Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:

      -
    • 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.
      • +

    • The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "Welcome to Kernel Debugging Land...", the one above it states the immediate reason for entering KDL.

      • +

    • The system reboots spontaneously.

      • +

    • The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut ALT SysReq D (SysReq being PRINT on most keyboards). Wait at least a minute to see, if anything happens.

      • +

    • The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try ALT SysReq D.

      • +

    • The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).

    -

    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.

    +

    Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in /boot/system/add-ons/kernel/drivers/bin).

    -

    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.
      • -
    +

    index +Kernel Debugging Land - KDL

    +

    If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut ALT SysReq D.
    +Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.

    +

    KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:

    + + + + + +
    bt (aka sc) Prints a back trace. If the system entered KDL on its on volition, always enter that one.
    ints Shows the handled and unhandled hardware interrupts.
    co (aka continue) Leaves the kernel debugger and continues normal operation of the system, if that is possible.
    reboot Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.
    +

    For more information, see the article Welcome to Kernel Debugging Land.

    +

    The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).

    -

    What's next?

    +

    index +Syslog

    +

    This is the preferred method for gaining information from a non-booting system.
    +The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file /boot/common/var/log/syslog. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).

    +

    The option Enable debug syslog in the boot loader's Debug menu makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down SHIFT while booting.
    +In the boot loader's Debug menu you should now find the entries Display syslog from previous session and Save syslog from previous session. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.

    + +

    index +On screen debug output

    +

    The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.
    +This is only relevant when Haiku fails to boot on your machine and the Debug syslog option doesn't work for some reason. Before the Haiku boot logo appears, hold SHIFT to enter the boot loader menu. Select Select safe mode options. Near the bottom, [ ] Enable on screen debug output will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)
    +Finally select Return to main menu and then Continue booting.
    +One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the Boot Loader.

    + +

    index +Hardware/Driver bugs

    +

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

    + + + + + + + + +
    - 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 above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
    - On screen debug output (a safe mode boot time option).
    + +

    The first four commands are entered 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.

    + +

    index +

    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 diff --git a/welcome/uk/bugreports.html b/welcome/uk/bugreports.html index 0e556835..40347acd 100644 --- a/welcome/uk/bugreports.html +++ b/welcome/uk/bugreports.html @@ -4,11 +4,12 @@ @@ -47,49 +48,109 @@

    The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.
    + + + +
    Reporting bugs
    Getting a Trac account
    + Creating a bug report
    + Application bugs
    + Server bugs
    + Kernel bugs
    + Kernel Debugging Land - KDL
    + Syslog
    + On screen debug output
    + Hardware/Driver bugs
    + What's next?
    +

    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

    +

    index +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

    +

    index +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:

      +

    • Attempt to reproduce your issue on the current revision of Haiku. Pre-built images for testing purposes are  available.

    • 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.

      • +

    • Mention which revision from SVN you are running. You can find this information in About Haiku... from the Deskbar menu. Also mention what kind of Haiku build you are testing (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.

    • 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/).

      • +

    • Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to take a screenshot by pressing the PRINT key.

    -

    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.

    +

    index +Application bugs

    +

    When an application crashed, you should invoke the debugger from the alert that pops up. This will open a Terminal window with gdb (the GNU debugger) running in it. Entering bt, you create a "backtrace" that you should copy in its entirety (including the part before you entered the bt command) and attach it to the ticket.

    -

    Hardware Bugs

    -

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

    +

    index +Server bugs

    +

    When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.
    +Besides everything being more ugly and inconvenient, basically the same applies as for application bugs. Most importantly procure a back trace (bt command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.

    + +

    index +Kernel bugs

    +

    Kernel bugs are usual the ones with the most severe effects while at the same time being the hardest to debug. There are different kinds of symptoms, which most likely point to a kernel or driver issue:

      -
    • 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.
      • +

    • The system enters kernel debugging land (KDL) on its own volition. The upper part of the screen is cleared white and several lines of text are printed on it. The second line says "Welcome to Kernel Debugging Land...", the one above it states the immediate reason for entering KDL.

      • +

    • The system reboots spontaneously.

      • +

    • The system freezes completely. You can't move the mouse and no application draws anything anymore. An important test in that situation is, whether you still can enter KDL via the shortcut ALT SysReq D (SysReq being PRINT on most keyboards). Wait at least a minute to see, if anything happens.

      • +

    • The system doesn't boot up correctly. It may reboot spontaneously or stop at some point (e.g. at some icon of the boot screen). In the latter case also try ALT SysReq D.

      • +

    • The whole system or some piece of hardware doesn't behave correctly. For example, it could be very slow, errors occur, or something doesn't work at all. If some hardware doesn't work at all, the first obvious check is whether Haiku supports it at all at the moment (e.g. ask on a mailing list or a forum).

    -

    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.

    +

    Note that while only the last point seems to indicate hardware relation, all the other symptoms could be caused by a bug in a hardware driver as well. If you have a suspicion what piece of hardware or corresponding driver might have to do with the problem, check whether removing/disabling the hardware or the driver makes a difference. For example, if you suspect Wifi you may find that your BIOS has an option to disable it. Or if not, you could remove the responsible Wifi driver from your Haiku installation (in /boot/system/add-ons/kernel/drivers/bin).

    -

    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.
      • -
    +

    index +Kernel Debugging Land - KDL

    +

    If the system hasn't entered KDL by itself, you can do that intentionally by invoking the keyboard shortcut ALT SysReq D.
    +Note that in KDL your keyboard may not work. PS/2 keyboards always do, USB keyboards connected via UHCI controllers do only, if one has entered KDL via the keyboard shortcut at least once. USB OHCI is not supported at the moment.

    +

    KDL itself is a kind of a shell. One can execute commands that print information about the system. The following commands might be of interest:

    + + + + + +
    bt (aka sc) Prints a back trace. If the system entered KDL on its on volition, always enter that one.
    ints Shows the handled and unhandled hardware interrupts.
    co (aka continue) Leaves the kernel debugger and continues normal operation of the system, if that is possible.
    reboot Reboots the system immediately. You will lose all unsaved data and even those that have been saved, but have not yet been written back to disk.
    +

    For more information, see the article Welcome to Kernel Debugging Land.

    +

    The KDL output is written to the serial port (if you have one, a respective cable, and a second computer to connect with, you can capture the output there via a terminal program) and to the syslog. If you can't leave KDL it won't be written to the syslog file, though. There's a boot loader debug option that allows you to capture it nonetheless (see below).

    -

    What's next?

    +

    index +Syslog

    +

    This is the preferred method for gaining information from a non-booting system.
    +The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file /boot/common/var/log/syslog. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).

    +

    The option Enable debug syslog in the boot loader's Debug menu makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu by holding down SHIFT while booting.
    +In the boot loader's Debug menu you should now find the entries Display syslog from previous session and Save syslog from previous session. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for saving the file. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.

    + +

    index +On screen debug output

    +

    The on-screen debug output is useful only for debugging very specific issues and is known to have (timing) issues. Don't use it, if you don't have to.
    +This is only relevant when Haiku fails to boot on your machine and the Debug syslog option doesn't work for some reason. Before the Haiku boot logo appears, hold SHIFT to enter the boot loader menu. Select Select safe mode options. Near the bottom, [ ] Enable on screen debug output will be listed. (Note: The other options could be enabled in an attempt to boot Haiku. If Haiku will boot only when one or more options are activated, be sure to mention which ones.)
    +Finally select Return to main menu and then Continue booting.
    +One or more pages of text will display on the screen, only the last few lines need to be included on your ticket. There's more information on the Boot Loader.

    + +

    index +Hardware/Driver bugs

    +

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

    + + + + + + + + +
    - 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 above). Shows interrupt usage. There shouldn't be too many that are shared by different devices.
    - On screen debug output (a safe mode boot time option).
    + +

    The first four commands are entered 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.

    + +

    index +

    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 diff --git a/welcome/zh_CN/bugreports.html b/welcome/zh_CN/bugreports.html index e1d6c008..0a491574 100644 --- a/welcome/zh_CN/bugreports.html +++ b/welcome/zh_CN/bugreports.html @@ -4,11 +4,12 @@