From 14828064271d4754ba77cae969272bf5afc04eb1 Mon Sep 17 00:00:00 2001 From: autonielx Date: Wed, 1 Feb 2017 04:48:59 +0100 Subject: [PATCH] Update userguide translations, waddlesplash as nielx --- userguide/Haiku-doc.css | 4 +- userguide/ca/applications/cli-apps.html | 20 +++ userguide/ca/applications/debugger.html | 10 +- userguide/ca/applications/haikudepot.html | 35 +++--- userguide/ca/applications/icon-o-matic.html | 2 +- userguide/ca/applications/list-cli-apps.html | 8 +- userguide/ca/applications/magnify.html | 4 +- .../ca/applications/packageinstaller.html | 2 +- userguide/ca/applications/showimage.html | 2 +- userguide/ca/bootloader.html | 5 +- .../ca/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/ca/preferences.html | 4 +- userguide/ca/preferences/printers.html | 8 +- userguide/ca/preferences/repositories.html | 88 ++++++++++++++ userguide/ca/preferences/screen.html | 16 +-- userguide/ca/workshop-email.html | 2 +- userguide/de/applications/cli-apps.html | 19 +++ userguide/de/applications/debugger.html | 11 +- userguide/de/applications/haikudepot.html | 38 +++--- userguide/de/applications/icon-o-matic.html | 2 +- userguide/de/applications/list-cli-apps.html | 11 +- userguide/de/applications/magnify.html | 2 +- .../de/applications/packageinstaller.html | 2 +- userguide/de/applications/showimage.html | 2 +- userguide/de/bootloader.html | 4 +- userguide/de/desktop-applets/workspaces.html | 5 +- .../de/images/apps-images/debugger_alert.png | Bin 8282 -> 9455 bytes .../apps-images/haiku-depot-ratingpanel.png | Bin 11494 -> 12218 bytes .../apps-images/haikudepot-login-tab.png | Bin 22817 -> 23975 bytes .../apps-images/haikudepot-rating-tab.png | Bin 10099 -> 16153 bytes .../de/images/apps-images/haikudepot.png | Bin 80150 -> 90534 bytes .../de/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/de/images/prefs-images/screen.png | Bin 20098 -> 15311 bytes userguide/de/preferences.html | 5 +- userguide/de/preferences/printers.html | 8 +- userguide/de/preferences/repositories.html | 88 ++++++++++++++ userguide/de/preferences/screen.html | 16 +-- userguide/de/workshop-email.html | 2 +- userguide/en/applications/cli-apps.html | 20 +++ userguide/en/applications/debugger.html | 10 +- userguide/en/applications/haikudepot.html | 35 +++--- userguide/en/applications/icon-o-matic.html | 2 +- userguide/en/applications/list-cli-apps.html | 8 +- userguide/en/applications/magnify.html | 4 +- .../en/applications/packageinstaller.html | 2 +- userguide/en/applications/showimage.html | 2 +- userguide/en/bootloader.html | 4 +- .../en/images/apps-images/debugger_alert.png | Bin 6751 -> 8595 bytes .../apps-images/haikudepot-rating-tab.png | Bin 10099 -> 12494 bytes .../en/images/apps-images/haikudepot.png | Bin 80150 -> 76286 bytes .../en/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/en/preferences.html | 4 +- userguide/en/preferences/printers.html | 8 +- userguide/en/preferences/repositories.html | 87 +++++++++++++ userguide/en/preferences/screen.html | 16 +-- userguide/en/workshop-email.html | 2 +- userguide/es/applications/cli-apps.html | 20 +++ userguide/es/applications/debugger.html | 10 +- userguide/es/applications/haikudepot.html | 35 +++--- userguide/es/applications/icon-o-matic.html | 2 +- userguide/es/applications/list-cli-apps.html | 8 +- userguide/es/applications/magnify.html | 3 +- .../es/applications/packageinstaller.html | 2 +- userguide/es/applications/showimage.html | 2 +- userguide/es/bootloader.html | 4 +- .../es/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/es/preferences.html | 4 +- userguide/es/preferences/printers.html | 8 +- userguide/es/preferences/repositories.html | 88 ++++++++++++++ userguide/es/preferences/screen.html | 14 +-- userguide/es/workshop-email.html | 2 +- userguide/fi/applications/cli-apps.html | 20 +++ userguide/fi/applications/debugger.html | 10 +- userguide/fi/applications/haikudepot.html | 58 +++++---- userguide/fi/applications/icon-o-matic.html | 2 +- userguide/fi/applications/list-cli-apps.html | 9 +- userguide/fi/applications/magnify.html | 3 +- .../fi/applications/packageinstaller.html | 2 +- userguide/fi/applications/showimage.html | 3 +- userguide/fi/bootloader.html | 5 +- .../fi/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/fi/preferences.html | 5 +- userguide/fi/preferences/printers.html | 8 +- userguide/fi/preferences/repositories.html | 88 ++++++++++++++ userguide/fi/preferences/screen.html | 15 +-- userguide/fi/workshop-email.html | 3 +- userguide/fr/applications/cli-apps.html | 20 +++ userguide/fr/applications/debugger.html | 10 +- userguide/fr/applications/haikudepot.html | 50 ++++---- userguide/fr/applications/icon-o-matic.html | 2 +- userguide/fr/applications/list-cli-apps.html | 8 +- userguide/fr/applications/magnify.html | 3 +- .../fr/applications/packageinstaller.html | 2 +- userguide/fr/applications/showimage.html | 2 +- userguide/fr/bootloader.html | 5 +- .../fr/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/fr/preferences.html | 5 +- userguide/fr/preferences/printers.html | 8 +- userguide/fr/preferences/repositories.html | 88 ++++++++++++++ userguide/fr/preferences/screen.html | 15 +-- userguide/fr/workshop-email.html | 2 +- userguide/hu/applications/cli-apps.html | 23 +++- userguide/hu/applications/debugger.html | 11 +- userguide/hu/applications/haikudepot.html | 35 +++--- userguide/hu/applications/icon-o-matic.html | 2 +- userguide/hu/applications/list-cli-apps.html | 9 +- userguide/hu/applications/magnify.html | 3 +- .../hu/applications/packageinstaller.html | 2 +- userguide/hu/applications/showimage.html | 3 +- userguide/hu/bootloader.html | 7 +- .../hu/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/hu/keyboard-shortcuts.html | 4 +- userguide/hu/preferences.html | 5 +- userguide/hu/preferences/printers.html | 8 +- userguide/hu/preferences/repositories.html | 88 ++++++++++++++ userguide/hu/preferences/screen.html | 15 +-- userguide/hu/preferences/time.html | 4 +- userguide/hu/workshop-email.html | 3 +- .../prefs-images/repositories-icon_16.png | Bin 0 -> 716 bytes .../prefs-images/repositories-icon_32.png | Bin 0 -> 1738 bytes .../prefs-images/repositories-icon_64.png | Bin 0 -> 3902 bytes userguide/it/applications/cli-apps.html | 20 +++ userguide/it/applications/debugger.html | 10 +- userguide/it/applications/haikudepot.html | 35 +++--- userguide/it/applications/icon-o-matic.html | 2 +- userguide/it/applications/list-cli-apps.html | 8 +- userguide/it/applications/magnify.html | 3 +- .../it/applications/packageinstaller.html | 2 +- userguide/it/applications/showimage.html | 2 +- userguide/it/bootloader.html | 5 +- .../it/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/it/preferences.html | 4 +- userguide/it/preferences/printers.html | 8 +- userguide/it/preferences/repositories.html | 88 ++++++++++++++ userguide/it/preferences/screen.html | 16 +-- userguide/it/preferences/sounds.html | 4 +- userguide/it/workshop-email.html | 2 +- .../jp/applications/activitymonitor.html | 4 +- userguide/jp/applications/bepdf.html | 4 +- userguide/jp/applications/bootmanager.html | 4 +- userguide/jp/applications/charactermap.html | 4 +- userguide/jp/applications/cli-apps.html | 21 +++- userguide/jp/applications/codycam.html | 4 +- userguide/jp/applications/debugger.html | 18 +-- userguide/jp/applications/deskcalc.html | 4 +- userguide/jp/applications/diskprobe.html | 4 +- userguide/jp/applications/diskusage.html | 4 +- userguide/jp/applications/drivesetup.html | 4 +- userguide/jp/applications/expander.html | 4 +- userguide/jp/applications/haikudepot.html | 49 ++++---- userguide/jp/applications/icon-o-matic.html | 6 +- userguide/jp/applications/installer.html | 4 +- userguide/jp/applications/list-cli-apps.html | 11 +- userguide/jp/applications/magnify.html | 8 +- userguide/jp/applications/mail.html | 4 +- userguide/jp/applications/mediaplayer.html | 4 +- userguide/jp/applications/midiplayer.html | 4 +- .../jp/applications/packageinstaller.html | 6 +- userguide/jp/applications/pe.html | 4 +- userguide/jp/applications/people.html | 4 +- userguide/jp/applications/poorman.html | 4 +- userguide/jp/applications/screenshot.html | 4 +- userguide/jp/applications/showimage.html | 10 +- userguide/jp/applications/soundrecorder.html | 4 +- userguide/jp/applications/stylededit.html | 4 +- userguide/jp/applications/terminal.html | 4 +- userguide/jp/applications/textsearch.html | 4 +- userguide/jp/applications/tv.html | 4 +- userguide/jp/applications/vision.html | 4 +- userguide/jp/applications/webpositive.html | 4 +- userguide/jp/applications/wonderbrush.html | 4 +- userguide/jp/bootloader.html | 5 +- userguide/jp/desktop-applets/launchbox.html | 4 +- .../jp/desktop-applets/networkstatus.html | 4 +- userguide/jp/desktop-applets/powerstatus.html | 4 +- .../jp/desktop-applets/processcontroller.html | 4 +- userguide/jp/desktop-applets/workspaces.html | 4 +- .../jp/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/jp/keyboard-shortcuts.html | 4 +- userguide/jp/preferences.html | 16 +-- userguide/jp/preferences/appearance.html | 4 +- userguide/jp/preferences/backgrounds.html | 4 +- .../jp/preferences/datatranslations.html | 4 +- userguide/jp/preferences/deskbar.html | 4 +- userguide/jp/preferences/e-mail.html | 4 +- userguide/jp/preferences/filetypes.html | 4 +- userguide/jp/preferences/keyboard.html | 4 +- userguide/jp/preferences/keymap.html | 4 +- userguide/jp/preferences/locale.html | 4 +- userguide/jp/preferences/media.html | 4 +- userguide/jp/preferences/mouse.html | 4 +- userguide/jp/preferences/network.html | 4 +- userguide/jp/preferences/printers.html | 12 +- userguide/jp/preferences/repositories.html | 91 ++++++++++++++ userguide/jp/preferences/screen.html | 18 +-- userguide/jp/preferences/screensaver.html | 4 +- userguide/jp/preferences/shortcuts.html | 4 +- userguide/jp/preferences/sounds.html | 4 +- userguide/jp/preferences/time.html | 4 +- userguide/jp/preferences/touchpad.html | 4 +- userguide/jp/preferences/tracker.html | 4 +- userguide/jp/preferences/virtualmemory.html | 4 +- userguide/jp/workshop-email.html | 3 +- userguide/pl/applications/cli-apps.html | 20 +++ userguide/pl/applications/debugger.html | 10 +- userguide/pl/applications/diskprobe.html | 2 + userguide/pl/applications/haikudepot.html | 35 +++--- userguide/pl/applications/icon-o-matic.html | 2 +- userguide/pl/applications/list-cli-apps.html | 8 +- userguide/pl/applications/magnify.html | 4 +- .../pl/applications/packageinstaller.html | 2 +- userguide/pl/applications/showimage.html | 2 +- userguide/pl/bootloader.html | 4 +- .../pl/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/pl/preferences.html | 4 +- userguide/pl/preferences/printers.html | 8 +- userguide/pl/preferences/repositories.html | 88 ++++++++++++++ userguide/pl/preferences/screen.html | 16 +-- userguide/pl/workshop-email.html | 2 +- userguide/pt_BR/applications/cli-apps.html | 20 +++ userguide/pt_BR/applications/debugger.html | 10 +- userguide/pt_BR/applications/haikudepot.html | 35 +++--- .../pt_BR/applications/icon-o-matic.html | 2 +- .../pt_BR/applications/list-cli-apps.html | 9 +- userguide/pt_BR/applications/magnify.html | 3 +- .../pt_BR/applications/packageinstaller.html | 2 +- userguide/pt_BR/applications/showimage.html | 3 +- userguide/pt_BR/bootloader.html | 6 +- .../images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes .../pt_BR/images/prefs-images/screen.png | Bin 17126 -> 14982 bytes userguide/pt_BR/preferences.html | 4 +- userguide/pt_BR/preferences/printers.html | 8 +- userguide/pt_BR/preferences/repositories.html | 88 ++++++++++++++ userguide/pt_BR/preferences/screen.html | 15 +-- userguide/pt_BR/workshop-email.html | 3 +- userguide/pt_PT/applications/cli-apps.html | 20 +++ userguide/pt_PT/applications/debugger.html | 10 +- userguide/pt_PT/applications/haikudepot.html | 35 +++--- .../pt_PT/applications/icon-o-matic.html | 2 +- .../pt_PT/applications/list-cli-apps.html | 8 +- userguide/pt_PT/applications/magnify.html | 4 +- .../pt_PT/applications/packageinstaller.html | 2 +- userguide/pt_PT/applications/showimage.html | 2 +- userguide/pt_PT/bootloader.html | 4 +- .../images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/pt_PT/preferences.html | 4 +- userguide/pt_PT/preferences/printers.html | 8 +- userguide/pt_PT/preferences/repositories.html | 88 ++++++++++++++ userguide/pt_PT/preferences/screen.html | 16 +-- userguide/pt_PT/workshop-email.html | 2 +- userguide/ro/applications.html | 79 ++++++------ .../ro/applications/activitymonitor.html | 2 +- userguide/ro/applications/bepdf.html | 11 +- userguide/ro/applications/bootmanager.html | 35 +++--- userguide/ro/applications/charactermap.html | 13 +- userguide/ro/applications/cli-apps.html | 37 ++++-- userguide/ro/applications/codycam.html | 11 +- userguide/ro/applications/debugger.html | 17 ++- userguide/ro/applications/deskcalc.html | 10 +- userguide/ro/applications/diskprobe.html | 9 +- userguide/ro/applications/diskusage.html | 4 +- userguide/ro/applications/drivesetup.html | 14 ++- userguide/ro/applications/expander.html | 25 ++-- userguide/ro/applications/haikudepot.html | 73 ++++++----- userguide/ro/applications/icon-o-matic.html | 84 ++++++------- userguide/ro/applications/installer.html | 20 +-- userguide/ro/applications/list-cli-apps.html | 24 ++-- userguide/ro/applications/magnify.html | 22 ++-- userguide/ro/applications/mail.html | 38 +++--- userguide/ro/applications/mediaplayer.html | 14 +-- userguide/ro/applications/midiplayer.html | 4 +- .../ro/applications/packageinstaller.html | 13 +- userguide/ro/applications/pe.html | 11 +- userguide/ro/applications/people.html | 4 +- userguide/ro/applications/poorman.html | 4 +- userguide/ro/applications/screenshot.html | 8 +- userguide/ro/applications/showimage.html | 35 +++--- userguide/ro/applications/soundrecorder.html | 6 +- userguide/ro/applications/stylededit.html | 6 +- userguide/ro/applications/terminal.html | 20 +-- userguide/ro/applications/textsearch.html | 6 +- userguide/ro/applications/tv.html | 7 +- userguide/ro/applications/vision.html | 54 ++++---- userguide/ro/applications/webpositive.html | 10 +- userguide/ro/applications/wonderbrush.html | 9 +- userguide/ro/attributes.html | 45 ++++--- userguide/ro/bash-scripting.html | 27 ++-- userguide/ro/bootloader.html | 34 +++--- userguide/ro/contents.html | 52 ++++---- userguide/ro/deskbar.html | 24 ++-- userguide/ro/desktop-applets.html | 15 ++- userguide/ro/desktop-applets/launchbox.html | 20 +-- .../ro/desktop-applets/networkstatus.html | 33 ++--- userguide/ro/desktop-applets/powerstatus.html | 29 ++--- .../ro/desktop-applets/processcontroller.html | 22 ++-- userguide/ro/desktop-applets/workspaces.html | 13 +- userguide/ro/filesystem-layout.html | 12 +- userguide/ro/filetypes.html | 22 ++-- userguide/ro/gui.html | 22 ++-- .../ro/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/ro/index.html | 6 +- userguide/ro/preferences.html | 51 ++++---- userguide/ro/preferences/appearance.html | 42 +++---- userguide/ro/preferences/backgrounds.html | 20 +-- .../ro/preferences/datatranslations.html | 20 +-- userguide/ro/preferences/deskbar.html | 7 +- userguide/ro/preferences/e-mail.html | 98 +++++++-------- userguide/ro/preferences/filetypes.html | 9 +- userguide/ro/preferences/keyboard.html | 11 +- userguide/ro/preferences/keymap.html | 24 ++-- userguide/ro/preferences/locale.html | 14 ++- userguide/ro/preferences/media.html | 9 +- userguide/ro/preferences/mouse.html | 10 +- userguide/ro/preferences/network.html | 12 +- userguide/ro/preferences/printers.html | 15 +-- userguide/ro/preferences/repositories.html | 89 ++++++++++++++ userguide/ro/preferences/screen.html | 26 ++-- userguide/ro/preferences/screensaver.html | 11 +- userguide/ro/preferences/shortcuts.html | 7 +- userguide/ro/preferences/sounds.html | 15 +-- userguide/ro/preferences/time.html | 24 ++-- userguide/ro/preferences/touchpad.html | 10 +- userguide/ro/preferences/tracker.html | 9 +- userguide/ro/preferences/virtualmemory.html | 19 +-- userguide/ro/queries.html | 24 ++-- userguide/ro/teammonitor.html | 7 +- userguide/ro/tracker.html | 46 +++---- userguide/ro/twitcher.html | 8 +- userguide/ro/workshop-email.html | 42 +++---- .../ro/workshop-filetypes+attributes.html | 82 ++++++------- userguide/ro/workshop-wlan.html | 38 +++--- userguide/ro/workspaces.html | 9 +- userguide/ru/applications.html | 44 +++---- userguide/ru/applications/bepdf.html | 4 +- userguide/ru/applications/cli-apps.html | 20 +++ userguide/ru/applications/debugger.html | 16 +-- userguide/ru/applications/haikudepot.html | 115 ++++++++++-------- userguide/ru/applications/icon-o-matic.html | 2 +- userguide/ru/applications/list-cli-apps.html | 8 +- userguide/ru/applications/magnify.html | 3 +- .../ru/applications/packageinstaller.html | 2 +- userguide/ru/applications/showimage.html | 2 +- userguide/ru/applications/soundrecorder.html | 2 +- userguide/ru/applications/tv.html | 2 +- userguide/ru/bash-scripting.html | 5 +- userguide/ru/bootloader.html | 21 ++-- userguide/ru/gui.html | 27 ++-- .../apps-images/haiku-depot-ratingpanel.png | Bin 11494 -> 16760 bytes .../ru/images/apps-images/haikudepot.png | Bin 80150 -> 159325 bytes .../prefs-images/appearance-antialiasing.png | Bin 21966 -> 32498 bytes .../images/prefs-images/appearance-colors.png | Bin 21783 -> 26560 bytes .../prefs-images/appearance-decorators.png | Bin 9110 -> 17103 bytes .../images/prefs-images/appearance-fonts.png | Bin 25239 -> 35053 bytes .../images/prefs-images/keymap-modifiers.png | Bin 10943 -> 15799 bytes userguide/ru/images/prefs-images/keymap.png | Bin 42886 -> 58765 bytes .../ru/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/ru/preferences.html | 4 +- userguide/ru/preferences/appearance.html | 11 +- userguide/ru/preferences/keymap.html | 18 +-- userguide/ru/preferences/media.html | 2 +- userguide/ru/preferences/printers.html | 10 +- userguide/ru/preferences/repositories.html | 91 ++++++++++++++ userguide/ru/preferences/screen.html | 16 +-- userguide/ru/preferences/screensaver.html | 4 +- userguide/ru/preferences/shortcuts.html | 15 +-- userguide/ru/preferences/sounds.html | 4 +- userguide/ru/workshop-email.html | 2 +- userguide/sk/applications.html | 33 +++-- .../sk/applications/activitymonitor.html | 2 +- userguide/sk/applications/bepdf.html | 9 +- userguide/sk/applications/bootmanager.html | 2 +- userguide/sk/applications/charactermap.html | 2 +- userguide/sk/applications/cli-apps.html | 46 ++++--- userguide/sk/applications/codycam.html | 6 +- userguide/sk/applications/debugger.html | 33 ++--- userguide/sk/applications/deskcalc.html | 35 +++--- userguide/sk/applications/diskprobe.html | 6 +- userguide/sk/applications/diskusage.html | 15 ++- userguide/sk/applications/drivesetup.html | 2 +- userguide/sk/applications/expander.html | 2 +- userguide/sk/applications/haikudepot.html | 50 ++++---- userguide/sk/applications/icon-o-matic.html | 4 +- userguide/sk/applications/installer.html | 2 +- userguide/sk/applications/list-cli-apps.html | 9 +- userguide/sk/applications/magnify.html | 4 +- userguide/sk/applications/mail.html | 2 +- userguide/sk/applications/mediaplayer.html | 2 +- userguide/sk/applications/midiplayer.html | 2 +- .../sk/applications/packageinstaller.html | 4 +- userguide/sk/applications/pe.html | 2 +- userguide/sk/applications/people.html | 2 +- userguide/sk/applications/poorman.html | 2 +- userguide/sk/applications/screenshot.html | 2 +- userguide/sk/applications/showimage.html | 5 +- userguide/sk/applications/soundrecorder.html | 2 +- userguide/sk/applications/stylededit.html | 2 +- userguide/sk/applications/terminal.html | 2 +- userguide/sk/applications/textsearch.html | 2 +- userguide/sk/applications/tv.html | 2 +- userguide/sk/applications/vision.html | 2 +- userguide/sk/applications/webpositive.html | 2 +- userguide/sk/applications/wonderbrush.html | 7 +- userguide/sk/bash-scripting.html | 5 +- userguide/sk/bootloader.html | 41 +++---- userguide/sk/deskbar.html | 44 +++---- userguide/sk/desktop-applets/launchbox.html | 2 +- .../sk/desktop-applets/networkstatus.html | 2 +- userguide/sk/desktop-applets/powerstatus.html | 2 +- .../sk/desktop-applets/processcontroller.html | 2 +- userguide/sk/desktop-applets/workspaces.html | 2 +- .../sk/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/sk/keyboard-shortcuts.html | 4 +- userguide/sk/preferences.html | 5 +- userguide/sk/preferences/appearance.html | 27 ++-- userguide/sk/preferences/backgrounds.html | 4 +- .../sk/preferences/datatranslations.html | 19 ++- userguide/sk/preferences/deskbar.html | 4 +- userguide/sk/preferences/e-mail.html | 4 +- userguide/sk/preferences/filetypes.html | 4 +- userguide/sk/preferences/keyboard.html | 4 +- userguide/sk/preferences/keymap.html | 7 +- userguide/sk/preferences/locale.html | 4 +- userguide/sk/preferences/media.html | 4 +- userguide/sk/preferences/mouse.html | 4 +- userguide/sk/preferences/network.html | 31 +++-- userguide/sk/preferences/printers.html | 12 +- userguide/sk/preferences/repositories.html | 90 ++++++++++++++ userguide/sk/preferences/screen.html | 19 +-- userguide/sk/preferences/screensaver.html | 4 +- userguide/sk/preferences/shortcuts.html | 4 +- userguide/sk/preferences/sounds.html | 4 +- userguide/sk/preferences/time.html | 4 +- userguide/sk/preferences/touchpad.html | 4 +- userguide/sk/preferences/tracker.html | 4 +- userguide/sk/preferences/virtualmemory.html | 4 +- userguide/sk/workshop-email.html | 3 +- userguide/sv_SE/applications/cli-apps.html | 20 +++ userguide/sv_SE/applications/debugger.html | 10 +- userguide/sv_SE/applications/haikudepot.html | 35 +++--- .../sv_SE/applications/icon-o-matic.html | 2 +- .../sv_SE/applications/list-cli-apps.html | 8 +- userguide/sv_SE/applications/magnify.html | 4 +- .../sv_SE/applications/packageinstaller.html | 2 +- userguide/sv_SE/applications/showimage.html | 2 +- userguide/sv_SE/bootloader.html | 5 +- .../images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/sv_SE/preferences.html | 4 +- userguide/sv_SE/preferences/printers.html | 8 +- userguide/sv_SE/preferences/repositories.html | 88 ++++++++++++++ userguide/sv_SE/preferences/screen.html | 14 +-- userguide/sv_SE/workshop-email.html | 2 +- userguide/uk/applications/cli-apps.html | 20 +++ userguide/uk/applications/debugger.html | 10 +- userguide/uk/applications/haikudepot.html | 35 +++--- userguide/uk/applications/icon-o-matic.html | 2 +- userguide/uk/applications/list-cli-apps.html | 8 +- userguide/uk/applications/magnify.html | 4 +- .../uk/applications/packageinstaller.html | 2 +- userguide/uk/applications/showimage.html | 2 +- userguide/uk/bootloader.html | 5 +- .../uk/images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/uk/preferences.html | 4 +- userguide/uk/preferences/printers.html | 8 +- userguide/uk/preferences/repositories.html | 88 ++++++++++++++ userguide/uk/preferences/screen.html | 16 +-- userguide/uk/workshop-email.html | 2 +- userguide/zh_CN/applications/cli-apps.html | 20 +++ userguide/zh_CN/applications/debugger.html | 10 +- userguide/zh_CN/applications/haikudepot.html | 35 +++--- .../zh_CN/applications/icon-o-matic.html | 2 +- .../zh_CN/applications/list-cli-apps.html | 9 +- userguide/zh_CN/applications/magnify.html | 3 +- .../zh_CN/applications/packageinstaller.html | 2 +- userguide/zh_CN/applications/showimage.html | 2 +- userguide/zh_CN/bootloader.html | 4 +- .../images/prefs-images/repositories.png | Bin 0 -> 19437 bytes .../images/prefs-images/repositories_add.png | Bin 0 -> 2807 bytes userguide/zh_CN/preferences.html | 5 +- userguide/zh_CN/preferences/printers.html | 8 +- userguide/zh_CN/preferences/repositories.html | 88 ++++++++++++++ userguide/zh_CN/preferences/screen.html | 15 +-- userguide/zh_CN/workshop-email.html | 3 +- welcome/Haiku-doc.css | 4 +- welcome/ca/bugreports.html | 7 +- welcome/de/bugreports.html | 7 +- welcome/en/bugreports.html | 7 +- welcome/es/bugreports.html | 7 +- welcome/fi/bugreports.html | 10 +- welcome/fr/bugreports.html | 12 +- welcome/hu/bugreports.html | 16 +-- welcome/it/bugreports.html | 7 +- welcome/jp/bugreports.html | 14 ++- welcome/pl/bugreports.html | 7 +- welcome/pt_BR/bugreports.html | 10 +- welcome/pt_PT/bugreports.html | 7 +- welcome/ro/bugreports.html | 51 ++++---- welcome/ru/bugreports.html | 10 +- welcome/sk/bugreports.html | 10 +- welcome/sv_SE/bugreports.html | 7 +- welcome/uk/bugreports.html | 7 +- welcome/welcome_ca.html | 38 +++--- welcome/welcome_de.html | 40 +++--- welcome/welcome_en.html | 38 +++--- welcome/welcome_es.html | 38 +++--- welcome/welcome_fi.html | 38 +++--- welcome/welcome_fr.html | 40 +++--- welcome/welcome_hu.html | 39 +++--- welcome/welcome_it.html | 38 +++--- welcome/welcome_jp.html | 54 ++++---- welcome/welcome_pl.html | 38 +++--- welcome/welcome_pt_BR.html | 38 +++--- welcome/welcome_pt_PT.html | 38 +++--- welcome/welcome_ro.html | 61 +++++----- welcome/welcome_ru.html | 38 +++--- welcome/welcome_sk.html | 39 +++--- welcome/welcome_sv_SE.html | 38 +++--- welcome/welcome_uk.html | 38 +++--- welcome/welcome_zh_CN.html | 38 +++--- welcome/zh_CN/bugreports.html | 14 +-- 536 files changed, 4859 insertions(+), 2567 deletions(-) create mode 100644 userguide/ca/images/prefs-images/repositories.png create mode 100644 userguide/ca/images/prefs-images/repositories_add.png create mode 100644 userguide/ca/preferences/repositories.html create mode 100644 userguide/de/images/prefs-images/repositories.png create mode 100644 userguide/de/images/prefs-images/repositories_add.png create mode 100644 userguide/de/preferences/repositories.html create mode 100644 userguide/en/images/prefs-images/repositories.png create mode 100644 userguide/en/images/prefs-images/repositories_add.png create mode 100644 userguide/en/preferences/repositories.html create mode 100644 userguide/es/images/prefs-images/repositories.png create mode 100644 userguide/es/images/prefs-images/repositories_add.png create mode 100644 userguide/es/preferences/repositories.html create mode 100644 userguide/fi/images/prefs-images/repositories.png create mode 100644 userguide/fi/images/prefs-images/repositories_add.png create mode 100644 userguide/fi/preferences/repositories.html create mode 100644 userguide/fr/images/prefs-images/repositories.png create mode 100644 userguide/fr/images/prefs-images/repositories_add.png create mode 100644 userguide/fr/preferences/repositories.html create mode 100644 userguide/hu/images/prefs-images/repositories.png create mode 100644 userguide/hu/images/prefs-images/repositories_add.png create mode 100644 userguide/hu/preferences/repositories.html create mode 100644 userguide/images/prefs-images/repositories-icon_16.png create mode 100644 userguide/images/prefs-images/repositories-icon_32.png create mode 100644 userguide/images/prefs-images/repositories-icon_64.png create mode 100644 userguide/it/images/prefs-images/repositories.png create mode 100644 userguide/it/images/prefs-images/repositories_add.png create mode 100644 userguide/it/preferences/repositories.html create mode 100644 userguide/jp/images/prefs-images/repositories.png create mode 100644 userguide/jp/images/prefs-images/repositories_add.png create mode 100644 userguide/jp/preferences/repositories.html create mode 100644 userguide/pl/images/prefs-images/repositories.png create mode 100644 userguide/pl/images/prefs-images/repositories_add.png create mode 100644 userguide/pl/preferences/repositories.html create mode 100644 userguide/pt_BR/images/prefs-images/repositories.png create mode 100644 userguide/pt_BR/images/prefs-images/repositories_add.png create mode 100644 userguide/pt_BR/preferences/repositories.html create mode 100644 userguide/pt_PT/images/prefs-images/repositories.png create mode 100644 userguide/pt_PT/images/prefs-images/repositories_add.png create mode 100644 userguide/pt_PT/preferences/repositories.html create mode 100644 userguide/ro/images/prefs-images/repositories.png create mode 100644 userguide/ro/images/prefs-images/repositories_add.png create mode 100644 userguide/ro/preferences/repositories.html create mode 100644 userguide/ru/images/prefs-images/repositories.png create mode 100644 userguide/ru/images/prefs-images/repositories_add.png create mode 100644 userguide/ru/preferences/repositories.html create mode 100644 userguide/sk/images/prefs-images/repositories.png create mode 100644 userguide/sk/images/prefs-images/repositories_add.png create mode 100644 userguide/sk/preferences/repositories.html create mode 100644 userguide/sv_SE/images/prefs-images/repositories.png create mode 100644 userguide/sv_SE/images/prefs-images/repositories_add.png create mode 100644 userguide/sv_SE/preferences/repositories.html create mode 100644 userguide/uk/images/prefs-images/repositories.png create mode 100644 userguide/uk/images/prefs-images/repositories_add.png create mode 100644 userguide/uk/preferences/repositories.html create mode 100644 userguide/zh_CN/images/prefs-images/repositories.png create mode 100644 userguide/zh_CN/images/prefs-images/repositories_add.png create mode 100644 userguide/zh_CN/preferences/repositories.html diff --git a/userguide/Haiku-doc.css b/userguide/Haiku-doc.css index 59aff8ec..509c9fef 100644 --- a/userguide/Haiku-doc.css +++ b/userguide/Haiku-doc.css @@ -21,7 +21,7 @@ body { line-height: 1.5; margin: 0; padding: 0; - font-family: "Noto Sans", Arial, Helvetica, sans-serif; + font-family: "DejaVu Sans", Arial, Helvetica, sans-serif; } /* link colors and text decoration */ @@ -373,7 +373,7 @@ pre.terminal { /* Terminal output*/ /* some links we want to print the url along with (CSS2) */ a.printurl:after { - content: " <" attr(href) ">"; + content: " <" attr(href) ">"; font-weight: normal; font-size: small; } diff --git a/userguide/ca/applications/cli-apps.html b/userguide/ca/applications/cli-apps.html index b262aaaf..32e9ab55 100644 --- a/userguide/ca/applications/cli-apps.html +++ b/userguide/ca/applications/cli-apps.html @@ -123,6 +123,11 @@ Would you like a link to it?" "On Desktop" "In Deskbar" "No thanks"

diskimage

diskimage lets you register a regular file as disk device. For example, you can register a Haiku anyboot image, mount it in Tracker and copy, edit or remove files there before using it as source in the Installer.

+

launch_roster

+

The launch_daemon starts all sorts of services and applications at boot-up. For some it was instructed to re-start them if they were quit. If you don't want that – maybe you'd like to test a modified Tracker, for example – you use launch_roster to stop the re-starting of the application before quitting it. Similarly, you can start it again or get info about it. Without parameter, launch_roster lists all apps/services that are under its control.
+For example, this will stop the re-launching of the Deskbar:

+
launch_roster stop x-vnd.be-tskb
+

mountvolume
mount

mountvolume is preferred by many to mount local partitions and disks, because its usage is so easy: just call it with the name of the partition and you're done. Try --help for more options.

mount can additionally mount remote disks by using a network filesystem, like NFS4. You specify the used filesystem with the -t parameter and the remote location with the -p parameter. As filesystem parameter you can use anything you find in /system/add-ons/kernel/file_system (and corresponding file hierarchies under ~/config or "non-packaged", of course). You also have to create a folder as mountpoint. Here's an example:

@@ -131,6 +136,21 @@ mount -t nfs4 -p "192.168.178.3:volume1" /DiskStation

open

open is a very handy little tool. With it you open any file with its preferred application, or start a specific application by its signature without the need to know its exact path. It also works with URLs and even with the "virtual" directories . for the current directory and .. for the parent, opening the folder in Tracker.

+

ramdisk

+

A ramdisk is like a harddisk running only in the computer's memory. That makes it very fast but also volatile, because its contents vanishes when you shut down the computer, or it crashes or you experience a blackout.
+To create a ramdisk of 1 GiB, format to the name "RAMses" and mount it, you enter this in Terminal or create a script of it:

+
ramdisk create -s 1gb
+mkfs -q -t bfs /dev/disk/virtual/ram/0/raw RAMses
+mountvolume RAMses
+

Note: When creating a ramdisk, the ramdisk command prints out the path to it. If you create several disks, that path /dev/disk/virtual/ram/0/raw will change!

+

To preserve the contents, at least if no calamity like a blackout etc. strikes, a ramdisk can be set up to read/write an image on the harddisk. For that, you need to supply a file of the desired size that will be read from every time you start your ramdisk, and written to when you unmount it. To create an image file "RAMimage" of 500MiB and format it, do this:

+
dd if=/dev/zero of=RAMimage bs=500M count=1
+mkfs -q -t bfs /dev/disk/virtual/ram/0/raw RAMimage
+

From now on, you start the ramdisk like this:

+
ramdisk create RAMimage
+mountvolume RAMimage
+

It's very important to always cleanly unmount you ramdisk, either from Tracker or with unmount /RAMimage, or the changes won't be written back to the image file!

+ diff --git a/userguide/ca/applications/debugger.html b/userguide/ca/applications/debugger.html index a217d99e..5305ecfa 100644 --- a/userguide/ca/applications/debugger.html +++ b/userguide/ca/applications/debugger.html @@ -4,7 +4,7 @@ +

  • Changelog

    -

    The last tab shows the detailed history of all the versions of the package that have been released so far.

    • +

    Here you find a detailed history of all the versions of the package that have been released so far, if the maintainer of the package provides that information.

    +

  • Contents

    +

    The last tab shows all the files and folders a package contains. This only works for already downloaded packages.

    • index -Tools and Options

    -

    In the Tools menu at the top of the window, you'll find an item to Refresh depots. This will request an up-to-date list of all available packages from the repositories.

    -

    Under Options you can choose to also Show develop packages and Show source packages in the packages list. For the normal user those are of no interest and would only clutter the list. They are important, however, for people who need the libraries, headers etc. of a package to develop and compile programs depending on them.

    -

    Of more interest are the other two items, Show available packages and Show installed packages, which are pretty self-explanatory.

    +Tools and Show +

    In the Tools menu at the top of the window, you'll find an item to Refresh repositories. This will request an up-to-date list of all available packages from the repositories. The other item is to Manage repositories.... It opens the Repositories preferences, to add/remove or disable and enable repositories.

    +

    Under Show you can deactivate Only featured packages. Now you'll always see all packages and not just the featured ones when HaikuDepot starts up or the search text field is empty.
    +Furthermore, you can choose to also Show Develop packages and Source packages in the packages list. For the normal user those are of no interest and would only clutter the list. They are important, however, for people who need the libraries, headers etc. of a package to develop and compile programs depending on them.

    +

    Of more interest are the options to only show Available packages and Installed packages, which are pretty self-explanatory.

    index Creating a User Account

    @@ -138,7 +145,7 @@ With the little thumb up/down icons to the right, you can show your approval or

    After you've created a user account and are logged in, you can rate a package and leave a comment, if you want. Just hover the mouse over the rating stars in the info area of a package and they turn into a Rating... button. Click it to open the rating window:

    haiku-depot-ratingpanel.png

    Here you move the mouse over the stars to light them up and choose your rating, you can also choose from a number of levels to judge the stability of the application and pick the language of your optional comment. To make a comment meaningful, you should have worked with the application you're about to rate for a while to become familiar with its features, bugs and quirks. And don't write the next great American novel... keep it short, sweet and polite. :)
    -After you click Send the data is transmitted to the server. You may have to go to the Tools menu to Refresh depots before you can see your changes.

    +After you click Send the data is transmitted to the server. You may have to go to the Tools menu to Refresh repositories before you can see your changes.

    At any time, you can come back and edit your comment and re-rate it. You can also hide your rating from other users by deactivating the checkbox Other users can see this rating.

    diff --git a/userguide/ca/applications/icon-o-matic.html b/userguide/ca/applications/icon-o-matic.html index 819f1d3c..29d37706 100644 --- a/userguide/ca/applications/icon-o-matic.html +++ b/userguide/ca/applications/icon-o-matic.html @@ -317,7 +317,7 @@ Of course you can move these indicators to change the gradient to your liking. Y Tips & Tricks

    A few things you should keep in mind when working with Icon-O-Matic and some general tips for its usage:

    - «  Printers  + «  Repositories  ::  Preferințe  ::  ScreenSaver  » @@ -58,29 +60,29 @@

    screen-icon_64.pngScreen

    - + +~/config/settings/kernel/drivers/vesa - Doar când se rulează în mod VESA.
    +~/config/settings/Screen_data - Stochează poziția ferestrei panoului.
    Deskbar:Preferințe
    Deskbar:Preferences
    Locație:/boot/system/preferences/Screen
    Configurări:~/config/settings/system/app_server/workspaces
    -~/config/settings/kernel/drivers/vesa - Only when running in VESA mode.
    -~/config/settings/Screen_data - Stores the panel's window position.
    -

    Each of your workspaces can have its own resolution, color depth and refresh rate.

    +

    Fiecare din spațiile de lucru poate să aibă propria rezoluție, adâncime a culorii și rată de actualizare.

    screen.png

    The top menu specifies if your changes are applied only to the current or to all workspaces. Depending on your graphics card, the other menus contain all supported resolution, color depth and refresh rate settings.

    After clicking on Apply, the graphics mode is changed and an alert appears, asking you to keep or cancel the changes. If you don't answer that alert, the graphics mode reverts after 12 seconds to the previous setting. Maybe you couldn't see the alert because your monitor didn't support the setting.

    -

    To the left, you see a representation of your screen with the manufacturer and model it reports and it's resolution in dots per inch (dpi). Hovering the mouse pointer over it shows a tooltip with the name of graphics card if it's supported by a driver. Otherwise it says "VESA", the quick fallback solution that works with pretty much every hardware.

    -

    Revert brings back the setting that was active when you started the Screen preferences.

    +

    There's a key combination that always works, not only when the Screen preferences are open: SHIFT CTRL ALT ESC sets a fall-back video safe mode. Handy if your monitor doesn't report its capabilities correctly and your settings result in a distorted or black screen. Here too, an alert pops up and if you do nothing for 12 seconds or press ESC you'll revert back.

    +

    On the left side of the window, you see a representation of your screen with the manufacturer and model it reports and it's resolution in dots per inch (dpi). It also shows the name of graphics card if it's supported by a driver. Otherwise it says "VESA", the quick fallback solution that works with pretty much every hardware.

    While Haiku's VESA mode performs very well, you may experience some limitations. You may not be able to drive your widescreen display in its native resolution, resulting in a somewhat blurred picture. There may also be limitations with regard to available color depths and refresh rates.
    +

    Revert brings back the setting that was active when you started the Screen preferences.

    To the bottom left you can set the number of workspaces and arrange them in columns and rows and open the Backgrounds preferences.

    -
    - «  Printers  -::  Preferințe  -::  ScreenSaver  » + « Repositories +:: Preferințe +:: ScreenSaver »
    diff --git a/userguide/ro/preferences/screensaver.html b/userguide/ro/preferences/screensaver.html index 18ded5b9..a40df0a4 100644 --- a/userguide/ro/preferences/screensaver.html +++ b/userguide/ro/preferences/screensaver.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * Emrys * --> @@ -57,17 +59,16 @@
    Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.

    screensaver-icon_64.pngScreenSaver

    - +
    Deskbar:Preferințe
    Deskbar:Preferences
    Locație:/boot/system/preferences/Screensaver
    Configurări:~/config/settings/ScreenSaver_settings
    -

    The panel of the ScreenSaver preferences is split into two tabs: -

    +

    Panoul preferințelor ScreenSave este secționat în două tab-uri:

    index -Fade

    +Decolorare screensaver-fade.png

    The top checkbox enables/disables the screen saver.
    @@ -82,7 +83,7 @@ The other, after how many minutes you need a password to unlock your machine.

    index -Screensavers

    +Protectoare de ecran screensaver-modules.png

    The second tab shows a list of all installed screen savers and their individual settings. You can test your settings with the Test button below the list.
    diff --git a/userguide/ro/preferences/shortcuts.html b/userguide/ro/preferences/shortcuts.html index a40b7837..47b8dc1d 100644 --- a/userguide/ro/preferences/shortcuts.html +++ b/userguide/ro/preferences/shortcuts.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * Emrys * --> @@ -54,18 +56,17 @@

    -
    Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.

    shortcuts-icon_64.pngShortcuts

    - +
    Deskbar:Preferințe
    Deskbar:Preferences
    Locație:/boot/system/preferences/Shortcuts
    Configurări:~/config/settings/shortcuts_settings
    ~/config/settings/Shortcuts_window_settings


    -

    Documentation is still missing. If you want to work on it, please announce it on the Documentation mailing list to avoid duplication.

    +

    Documentația lipsește încă. Dacă vreți să lucrați la ea, anunțați pe lista de discuții Documentație pentru a evita o duplicare.

    diff --git a/userguide/ro/preferences/sounds.html b/userguide/ro/preferences/sounds.html index 3b8e6d11..4db0e5d9 100644 --- a/userguide/ro/preferences/sounds.html +++ b/userguide/ro/preferences/sounds.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * Emrys * --> @@ -54,22 +56,21 @@
    -
    Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.

    sounds-icon_64.pngSounds

    - +
    Deskbar:Preferințe
    Deskbar:Preferences
    Locație:/boot/system/preferences/Sounds
    Configurări:~/config/settings/Media/MediaFiles


    sounds.png -

    You can assign sounds to certain events in the system. Just select the event from the list and choose a sound from the pop-up menu below.

    +

    Puteți atribui sunete la anumite evenimente din sistem. Selectați evenimentul din listă și alegeți un sunet din meniul contextual de mai jos.

    - -
    None will silence an event.
    Other... will open a file panel to find a new sound that isn't yet in the menu.
    -

    You can use any format that's supported by the system. If MediaPlayer can deal with it, so can any other program.
    -You can "pre-hear" an event's sound by selecting it and using the Play and Stop buttons.

    +Nimic va reduce la tăcere un eveniment. +Altele... va deschide un panou de fișier pentru a găsi un sunet nou care nu se află încă în meniu. +

    Puteți utiliza orice format care este admis de sistem. Dacă MediaPlayer poate să aibă de a face cu el, atunci și celelalte programe pot să facă asta.
    +Puteți să „ascultați înainte” sunetul unui eveniment prin selectarea acestuia și utilizarea butoanelor Redare și Stop.

    diff --git a/userguide/ro/preferences/time.html b/userguide/ro/preferences/time.html index f7a89022..cd7a5e0e 100644 --- a/userguide/ro/preferences/time.html +++ b/userguide/ro/preferences/time.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * Emrys * --> @@ -58,38 +60,38 @@

    time-icon_64.pngTime

    - + -
    Deskbar:Preferințe
    Deskbar:Preferences
    Locație:/boot/system/preferences/Time
    Configurări:~/config/settings/networktime settings - All the settings concerning synchronizing the time through the network
    -~/config/settings/RTC_time_settings - The setting of the hardware clock (local or GMT)
    -~/config/settings/Time settings - The time zone setting
    -~/config/settings/Time_preflet_window - The panel's window position etc.
    +
    Configurări:~/config/settings/networktime settings - Toate configurările cu privire la sincronizarea orei prin rețea
    +~/config/settings/RTC_time_settings - Configurarea ceasului de hardware (local sau GMT)
    +~/config/settings/Time settings - Configurarea fusului orar
    +~/config/settings/Time_preflet_window - Poziția ferestrei panoului, etc.
    -

    The panel of the Time preferences is split into four tabs:

    +

    Panoul preferințelor Time este secționat în patru tab-uri:

    index -Date and time

    +Dată și oră time-time.png

    On the left side, you can set the day of the month by simply clicking on it in the calendar. You change the month and year by clicking on it and using the up/down arrows to the right or the cursor keys on your keyboard.

    Similarly, you set the time at the right. Or simply move the hands of the clock directly.

    index -Time zone

    +Fus orar time-timezone.png

    Simply find and choose your country in the list of continents and press Set time zone. For countries with more than one time zone you'll have to expand one level deeper.
    To the right you'll find the time of the currently set time zone and the preview time of the the zone you've chosen.

    Also on the right side is a setting for the hardware clock of your computer. There are two modes for the clock:

    - +
    Local timeto display your local time, which you normally want if you dual-boot into Windows.
    Oră localăto display your local time, which you normally want if you dual-boot into Windows.
    GMTto display Greenwich Mean Time, which is the UNIX compatible setting.

    index -Network time

    +Oră rețea

    Setting date and time manually is pretty much obsolete if you're connected to the internet. There are public servers that supply very exact time signals.

    time-network.png

    With the +/- buttons you can add/remove NTP-servers to/from the list.

    @@ -98,7 +100,7 @@ To the right you'll find the time of the currently set time zone and the preview

    index -Clock

    +Ceas time-clock.png

    The last tab shows the options of the clock displayed in the Deskbar. You can disable the clock there completely with the top checkbox. The rest are equally self-explanatory.


    diff --git a/userguide/ro/preferences/touchpad.html b/userguide/ro/preferences/touchpad.html index c31101dd..3202947d 100644 --- a/userguide/ro/preferences/touchpad.html +++ b/userguide/ro/preferences/touchpad.html @@ -9,6 +9,8 @@ * * Authors: * [Insert your name and address here] + * Translators: + * Emrys * --> @@ -59,12 +61,12 @@

    touchpad-icon_64.pngTouchpad

    - +
    Deskbar:Preferințe
    Deskbar:Preferences
    Locație:/boot/system/preferences/Touchpad
    Configurări:~/config/settings/Touchpad_settings
    -

    This panel offers several touchpad related settings that are interesting when you're running on a notebook.

    +

    Acest panou oferă mai multe configurări în legătură cu touchpad-ul care sunt interesante când rulați de pe un laptop.

    touchpad.png @@ -75,8 +77,8 @@ 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 resets everything to default values.
    Revert brings back the settings that were active when you started the Touchpad preferences.
    Implicit resetează totul la valorile implicite.
    Revenire aduce înapoi configurările care au fost active atunci când ați pornit preferințele Touchpad.

    Here is a tip that's not related to the Touchpad preferences, but fits the general topic:
    Did you know that you can do a drag and drop just by using the touchpad, i.e. not using the buttons? Just do a double click without lifting the finger after the second click. The picked up icon will stick to the mouse pointer and you can drag it around by moving your finger. Lifting your finger will drop the icon.

    diff --git a/userguide/ro/preferences/tracker.html b/userguide/ro/preferences/tracker.html index c919f92b..06f49ea5 100644 --- a/userguide/ro/preferences/tracker.html +++ b/userguide/ro/preferences/tracker.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * Emrys * --> @@ -54,17 +56,16 @@
    -
    Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.

    tracker-icon_64.pngTracker

    - +
    Deskbar:Preferințe
    Deskbar:Preferences
    Locație:/boot/system/preferences/Tracker
    Configurări:~/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.

    +

    Panoul de preferințe Tracker este de asemenea disponibil din fiecare fereastră Tracker cu meniul Fereastră | Preferințe....
    +Funcțiile acestuia sunt discutate în subiectul despre Tracker.

    diff --git a/userguide/ro/preferences/virtualmemory.html b/userguide/ro/preferences/virtualmemory.html index 22d53da8..af075b3a 100644 --- a/userguide/ro/preferences/virtualmemory.html +++ b/userguide/ro/preferences/virtualmemory.html @@ -9,6 +9,8 @@ * * Authors: * Humdinger + * Translators: + * Emrys * --> @@ -53,23 +55,22 @@
    -
    Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.

    virtualmemory-icon_64.pngVirtualMemory

    - + +~/config/settings/VM_data - Stochează poziția ferestrei panoului.
    Deskbar:Preferințe
    Deskbar:Preferences
    Locație:/boot/system/preferences/VirtualMemory
    Configurări:~/config/settings/kernel/drivers/virtual_memory
    -~/config/settings/VM_data - Stores the panel's window position.
    -

    Virtual memory let's the system swap out memory to harddisk, if the RAM can be used more sensibly for other things. So, even if you have lots of RAM, providing virtual memory is never a bad idea.

    +

    Memoria virtuală permite sistemului să schimbe memorie la hard disc, dacă memoria RAM poate fi utilizată mai eficient pentru alte lucruri. Prin urmare, deși aveți multă memorie RAM, furnizarea de memorie virtuală nu e niciodată o idee greșită.

    virtualmemory.png -

    You can set the size to even more than your physical memory size if needed. With today's huge harddisks, assigning the physical memory size shouldn't be a problem. Still, you can quickly adjust the size if your free space ever runs low. In that case you should also have a look at DiskUsage to find out what's eating up your diskspace.

    -

    Normally, the swap file's written to your boot partition. If you often run into disk thrashing due to the virtual memory system swapping memory in and out, you can try to use a separate harddisk for you swap file. Simply another partition on the same harddisk with your system/data won't help.
    -Upgrading your RAM is of course the most effective way to go...

    +

    Puteți stabili dimensiunea chiar și peste mărimea fizică a memoriei dacă este necesar. Având în vedere hard discurile uriașe de azi, atribuirea mărimii memoriei fizice nu ar trebui să fie o problemă. Oricum, puteți ajusta dimensiunea rapid dacă spațiul liber devine scăzut vreodată. În acest caz ar trebui de asemenea să vă uitați la DiskUsage pentru a determina sursa care ocupă spațiul pe disc.

    +

    De obicei fișierul swap este scris pe partiția de boot. Dacă întâmpinați vreodată avertismente ale discului din cauza sistemului de memorie virtuală care schimbă memorie, puteți încerca să utilizați un hard disc separat pentru fișierul swap. Doar o partiție pe același hard disc cu sistemul/datele nu va ajuta.
    +Desigur că actualizarea memoriei RAM este cel mai eficient mod de a rezolva...

    - - + +
    Defaults resets everything to default values.
    Revert brings back the settings that were active when you started the VirtualMemory preferences.
    Implicit resetează totul la valorile implicite.
    Revenire aduce înapoi configurările care au fost active când ați pornit preferințele VirtualMemory.
    diff --git a/userguide/ro/queries.html b/userguide/ro/queries.html index c150a19e..1097b486 100644 --- a/userguide/ro/queries.html +++ b/userguide/ro/queries.html @@ -83,17 +83,17 @@ Even better, you don't have to double-click to re-do a query. You can

    1. Select recent or saved queries or save the current search parameters as Query Template.

      2. -

    2. Narrow down your search from All files and folders to specific file types.

      3. +

    3. Restrângeți căutarea de la Toate fișierele și dosarele la tipuri de fișier specifice.

    4. Define the search method:
      • by Name - a basic search by file or folder name
      • by Attribute - an advanced search, you specify search terms for one or more attributes
      • by Formula - an even more advanced search, you can fine-tune a complex query term
      5. -

    5. Select which drives to search on.

      6. -

    6. Enter the search term.

      7. -

    7. The expander hides/unhides the additional options.

      8. +

    8. Selectați dispozitivele în care căutați.

      9. +

    9. Introduceți termenul căutat.

      10. +

    10. Expander ascunde/afișează opțiunile adiționale.

    11. Uncheck the Temporary checkbox if you don't want this query self-destruct after 7 days.

      12. -

    12. Check if your query is supposed to Include trash.

      13. -

    13. Optionally, enter a name for this query if you want to save it.

      14. +

    14. Verificați dacă interogarea ar trebui de asemenea să Include gunoi.

      15. +

    15. Opțional, introduceți un nume pentru această interogare dacă vreți să o salvați.

    16. You can drag&drop the icon anywhere to save a query. Doing that with the right mouse button, offers the option to save as template.

    @@ -109,7 +109,7 @@ Even better, you don't have to double-click to re-do a query. You can

    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.

    This adds a pop-up menu to the left of the textbox and the buttons Add and Remove under that. From the menu you choose which attribute to query. With Add and Remove you can query additional attributes or remove them again. These attributes can be logically linked with AND/OR.

    -

    Let's do an email query as an example:

    +

    Să luăm o interogare de email ca exemplu:

    query-window-filled.png

    This is your Find window when you're looking for all emails Clara Botters has sent to you in the last two months that had in the subject "vibraphone" or "skepticality".
    As you see, searching through time-based attributes supports some useful phrases: besides for the "last 2 months", you could also use "today", "yesterday", "Monday" or "last Monday" (which would be the Monday last week), or "last 2 minutes/hours/days/weeks".
    @@ -121,15 +121,15 @@ A good way to cut down the number of search results.

    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 -

    Once more as text, edited for readability:

    +

    Încă o dată ca text, editat pentru lizibilitate:

    (((((MAIL:from=="*[cC][lL][aA][rR][aA] [bB][oO][tT][tT][eE][rR][sS]*")
        &&(MAIL:when>=%2 months%))
        &&(MAIL:subject=="*[vV][iI][bB][rR][aA][pP][hH][oO][nN][eE]*"))
        ||(MAIL:subject=="*[sS][kK][eE][pP][tT][iI][cC][aA][lL][iI][tT][yY]*"))
        &&(BEOS:TYPE=="text/x-email"))
    -

    What's the use?

    +

    Care este utilizarea?

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

    result-window.png

    Besides the gray background, result windows work exactly like any other Tracker window. Some things are worth noting:

      -

    • You can open the location of a file or folder by double clicking on its path attribute.

      • +

    • Puteți deschide locația unui fișier sau dosar prin dublu clic pe atributul de cale al acestuia.

    • With File | Edit query or ALT G you get back to your Find window to refine your query.

    • A query is live, i.e. if a file that matches your search criteria appears or disappears from your system, this change is reflected in your results in real-time.

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

    Șabloane Interogări

    If you double click a saved query, the file search is at once started and the result window opens immediately. However, you may not want to search with these exact search parameters, but use it as starting point to only slightly tweak the formula.
    By using the Save query as template menu item (see (1) in screenshot at the top) or drag&dropping the icon (10) anywhere with the right mouse button, you can create just such a template. Double clicking it won't open a result window, but the Find panel, giving you the opportunity to quickly change search strings or add/remove attributes.

    -

    Wherever you choose to save query templates, they'll be listed in the Find panel's menu of recent queries.

    +

    Oriunde alegeți să salvați șabloanele de interogări, acestea vor fi listate în meniul panoului Căutare al interogărilor recente.

    diff --git a/userguide/ro/teammonitor.html b/userguide/ro/teammonitor.html index d7623722..07c032a9 100644 --- a/userguide/ro/teammonitor.html +++ b/userguide/ro/teammonitor.html @@ -56,16 +56,15 @@
    -
    Traducerea acestei pagini nu este completă încă. Până când va fi, părțile incomplete utilizează originalul în limba engleză.

    Team Monitor

    Cu CTRL ALT DEL invocați Team Monitor ce listează toate programele care rulează în mod curent.

    teammonitor.png -

    Programs that were launched by the system are blue, those started by the user black.
    -Applications that are unresponsive, which is often a sign the program has crashed, are marked red. You can try to quit a program by selecting it and pressing Quit application (or either DEL or Q). If that doesn't work, try Kill application (or SHIFT DEL or K) instead.

    +

    Programele care au fost lansate de sistem sunt albastre, cele pornite de utilizator sunt negre.
    +Aplicațiile care nu răspund, ceea ce este de obicei un semn că programul este în pană, sunt marcate cu roșu. Puteți încerca să închideți un program prin selectarea acestuia și apăsarea pe Închide aplicația (sau fie DEL sau Q). Dacă asta nu funcționează, încercați Termină aplicația (sau SHIFT DEL or K) în schimb.

    Puteți invoca un Terminal cu OPT ALT T.

    -

    If your Tracker or Deskbar crashed or froze, a new button appears (you may have to kill the offending team first): Restart the desktop will restart Tracker and/or Deskbar for you.

    +

    Dacă Tracker sau Deskbar sunt în pană sau au înghețat, un buton nou apare (e posibil să trebuiască să termini echipa care a cauzat problema mai întâi): Repornire desktop va reporni Tracker și/sau Deskbar.

    diff --git a/userguide/ro/tracker.html b/userguide/ro/tracker.html index b1e90886..ae900802 100644 --- a/userguide/ro/tracker.html +++ b/userguide/ro/tracker.html @@ -73,17 +73,17 @@

    Tracker

    -

    The Tracker is the graphical interface to all your files. It lets you create new files and folders or find, launch or rename as well as copy or delete existing ones.

    +

    Tracker este interfața grafică pentru toate fișierele. Vă permite să creați fișiere și dosare noi sau să căutați, lansați sau redenumiți precum și să copiați sau să ștergeți fișiere și dosare existente.

    Being an application like any other (the Desktop with its icons is really just a fullscreen window in the background), Tracker appears with its windows in the Deskbar and can be quit and restarted. The easiest way to quit and restart a crashed or frozen Tracker (or a wayward Deskbar) is to call the Team Monitor.

    index -Montare volume

    +Montare de volume

    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.

    drill-down.png

    There are also 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!
    +
    Înainte să deconectați de ex: un hard disc sau stick USB, asigurați-vă că ați demontat cu succes volumul. Aceasta garantează că tot transferul de date s-a terminat. Alfel este posibil să pierdeți date sau să corupeți discul!

    index @@ -94,13 +94,13 @@ This is also true for keyboard navigation. For more on that, see topic indexDrilling down the submenus

    -

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

    +indexForare în submeniuri +

    În loc să dați dublu clic dosar după dosar, există o metodă mai bună pentru forare:

    drill-down.png

    Right-click onto a folder, and at the top of the usual context menu you'll find a submenu of the current folder that let's you navigate down a level. Just move down the hierarchy until you find the file or folder you're looking for and click on it to open it. The above shows the contents of the folder /boot/home/config/.
    If you do the above while dragging a file with you, it will be moved to where you eventually drop it.

    -

    A similar method can be used from any Tracker window:

    +

    O metodă similară poate fi utilizată din orice fereastră Tracker:

    window-drill-down.png

    Click on the area in the lower left, where the number of items is listed, and you'll get submenus for every level above your current location. From there you can drill down through the folders as usual.

    Note, that the Desktop is always the topmost level as that is where Tracker shows mounted volumes. So, if you want to go to another disk, you first have to navigate to the top (Desktop) and cross over to your other disk from there.


    @@ -108,13 +108,13 @@ If you do the above while dragging a file with you, it will be moved to where yo

    index -Jumping to files with type-ahead

    +Salt la fișiere cu tastare-înainte

    You may be familiar with the concept from file managers of other operating systems: typing the first few letters of a filename will jump to the first file matching these starting characters. Haiku took the idea a step further. If there isn't a file starting with those letters it will jump to the first file including the string anywhere in its name. And if there's nothing with the string in its filename, the attributes are searched next.

    window-type-ahead.png

    In the above example, there are many files starting with "Haiku logo", rendering simpler approaches to typing ahead quite useless. In Haiku however, typing "web" jumps right to its first occurence in "Haiku logo - website". The characters you enter appear in the bottom left corner where you normally find the item count of all files in the folder. A second after entering a character, the display jumps back to normal and you're ready for a new type ahead search.

    index -Type-ahead filtering

    +Filtrare tastare-înainte

    Instead of jumping to a file while typing, there's also the option to filter out all files not matching your type-ahead string. This can improve clarity dramatically, especially when dealing with crowded folders. By using SHIFT SPACE as delimiter, you can even filter on multiple strings.
    Contrary to type-ahead jumping, the filtering will stick until you press ESC or close the window (or leave the folder if you're using Single Window Navigation).
    This type-ahead filtering is set in the Tracker preferences.

    @@ -123,13 +123,13 @@ This type-ahead filtering is set in the Trac index Aspect window-menu.png -

    Tracker windows offer three different viewing modes from the Window menu:

    +

    Ferestrele Tracker oferă trei moduri de vizualizare diferite din meniul Fereastră:

      -

    • Icon view (ALT 1) - Big icons, you can change the size from the submenu or in/decrease their size with ALT +/-.

      • -

    • Mini icon view (ALT 2) - Small icons.

      • -

    • List view (ALT 3) - A detailed list of your files enabling you to show/hide available attributes. (See topic Attributes.)

      • +

    • Vizualizare pictogramă (ALT 1) - Pictograme mari, puteți modifica dimensiunea din submeniu sau mări/micșora dimensiunea lor cu ALT +/-.

      • +

    • Vizualizare pictogramă mini (ALT 2) - Pictograme mici.

      • +

    • Vizualizare listă (ALT 3) - O listă detaliată a fișierelor, care vă permite afișarea/ascunderea atributelor disponibile. (Vedeți subiectul Attributes.)

    -

    The Window menu offers a number of other functions:

    +

    Meniul Fereastră oferă un număr de alte funcții:

    Sometimes you just want to rearrange a few icons without doing a complete Clean up (ALT K). In that case, you select these icons and start to drag them to their new location. Before you drop them there, keep ALT pressed. This will align the icons to the invisible grid.

    -

    The rest of the functions are pretty self-explanatory, leaving the Tracker preferences.

    +

    Restul funcțiilor se explică de la sine destul de bine, rămân doar preferințele Tracker.

    index @@ -161,15 +161,15 @@ This type-ahead filtering is set in the Trac

  • Volume icons - Set the color of an optional indicator of free space that's shown besides a disk's icon.

  • Disk mount - Define when and what disks are mounted automatically, as described above under "Mounting volumes".

    • -

    This panel, by the way, is also available as Tracker from Deskbar's Preferences.

    +

    Apropo, acest panou este disponibil și ca Tracker din Preferințe Deskbar.

    index -Lucru cu fișiere

    -

    When invoked on a selected file, most of the File menu commands are also offered in the context menu by right-clicking that file.

    -

    As usual the commands are pretty clear.

    +Lucrul cu fișiere +

    Când sunt invocate pentru un fișier selectat, majoritatea comenzilor din meniul Fișier sunt de asemenea oferite de meniul contextual prin clic dreapta pe acel fișier.

    +

    Ca de obicei comenzile sunt destul de clare.

    index -Nástroje a voľby

    -

    In the Tools menu at the top of the window, you'll find an item to Refresh depots. This will request an up-to-date list of all available packages from the repositories.

    -

    Under Options you can choose to also Show develop packages and Show source packages in the packages list. For the normal user those are of no interest and would only clutter the list. They are important, however, for people who need the libraries, headers etc. of a package to develop and compile programs depending on them.

    -

    Of more interest are the other two items, Show available packages and Show installed packages, which are pretty self-explanatory.

    +Nástroje a zobrazenie +

    In the Tools menu at the top of the window, you'll find an item to Refresh repositories. This will request an up-to-date list of all available packages from the repositories. The other item is to Manage repositories.... It opens the Repositories preferences, to add/remove or disable and enable repositories.

    +

    Under Show you can deactivate Only featured packages. Now you'll always see all packages and not just the featured ones when HaikuDepot starts up or the search text field is empty.
    +Furthermore, you can choose to also Show Develop packages and Source packages in the packages list. For the normal user those are of no interest and would only clutter the list. They are important, however, for people who need the libraries, headers etc. of a package to develop and compile programs depending on them.

    +

    Of more interest are the options to only show Available packages and Installed packages, which are pretty self-explanatory.

    index Vytvorenie používateľského účtu

    @@ -139,7 +145,7 @@ With the little thumb up/down icons to the right, you can show your approval or

    After you've created a user account and are logged in, you can rate a package and leave a comment, if you want. Just hover the mouse over the rating stars in the info area of a package and they turn into a Rating... button. Click it to open the rating window:

    haiku-depot-ratingpanel.png

    Here you move the mouse over the stars to light them up and choose your rating, you can also choose from a number of levels to judge the stability of the application and pick the language of your optional comment. To make a comment meaningful, you should have worked with the application you're about to rate for a while to become familiar with its features, bugs and quirks. And don't write the next great American novel... keep it short, sweet and polite. :)
    -After you click Send the data is transmitted to the server. You may have to go to the Tools menu to Refresh depots before you can see your changes.

    +After you click Send the data is transmitted to the server. You may have to go to the Tools menu to Refresh repositories before you can see your changes.

    At any time, you can come back and edit your comment and re-rate it. You can also hide your rating from other users by deactivating the checkbox Other users can see this rating.

    diff --git a/userguide/sk/applications/icon-o-matic.html b/userguide/sk/applications/icon-o-matic.html index 4ff62f8b..b16690cc 100644 --- a/userguide/sk/applications/icon-o-matic.html +++ b/userguide/sk/applications/icon-o-matic.html @@ -77,7 +77,7 @@ - +
    Panel:Aplikácie
    Umiestnenie:/boot/system/apps/Icon-O-Matic
    Nastavenie:~/config/settings/Icon-O-Matic
    Nastavenia:~/config/settings/Icon-O-Matic


    @@ -320,7 +320,7 @@ Samozrejme, tieto indikátory môžete presúvať a meniť tak farebný prechod Tipy & Triky

    Zopár vecí, na ktoré by ste mali myslieť počas práce s Icon-O-Matic a všeobecné tipy pri používaní:

    index -Tools and Options

    -

    In the Tools menu at the top of the window, you'll find an item to Refresh depots. This will request an up-to-date list of all available packages from the repositories.

    -

    Under Options you can choose to also Show develop packages and Show source packages in the packages list. For the normal user those are of no interest and would only clutter the list. They are important, however, for people who need the libraries, headers etc. of a package to develop and compile programs depending on them.

    -

    Of more interest are the other two items, Show available packages and Show installed packages, which are pretty self-explanatory.

    +Tools and Show +

    In the Tools menu at the top of the window, you'll find an item to Refresh repositories. This will request an up-to-date list of all available packages from the repositories. The other item is to Manage repositories.... It opens the Repositories preferences, to add/remove or disable and enable repositories.

    +

    Under Show you can deactivate Only featured packages. Now you'll always see all packages and not just the featured ones when HaikuDepot starts up or the search text field is empty.
    +Furthermore, you can choose to also Show Develop packages and Source packages in the packages list. For the normal user those are of no interest and would only clutter the list. They are important, however, for people who need the libraries, headers etc. of a package to develop and compile programs depending on them.

    +

    Of more interest are the options to only show Available packages and Installed packages, which are pretty self-explanatory.

    index Creating a User Account

    @@ -138,7 +145,7 @@ With the little thumb up/down icons to the right, you can show your approval or

    After you've created a user account and are logged in, you can rate a package and leave a comment, if you want. Just hover the mouse over the rating stars in the info area of a package and they turn into a Rating... button. Click it to open the rating window:

    haiku-depot-ratingpanel.png

    Here you move the mouse over the stars to light them up and choose your rating, you can also choose from a number of levels to judge the stability of the application and pick the language of your optional comment. To make a comment meaningful, you should have worked with the application you're about to rate for a while to become familiar with its features, bugs and quirks. And don't write the next great American novel... keep it short, sweet and polite. :)
    -After you click Send the data is transmitted to the server. You may have to go to the Tools menu to Refresh depots before you can see your changes.

    +After you click Send the data is transmitted to the server. You may have to go to the Tools menu to Refresh repositories before you can see your changes.

    At any time, you can come back and edit your comment and re-rate it. You can also hide your rating from other users by deactivating the checkbox Other users can see this rating.

    diff --git a/userguide/sv_SE/applications/icon-o-matic.html b/userguide/sv_SE/applications/icon-o-matic.html index 3c46de8b..f8c424b3 100644 --- a/userguide/sv_SE/applications/icon-o-matic.html +++ b/userguide/sv_SE/applications/icon-o-matic.html @@ -317,7 +317,7 @@ Of course you can move these indicators to change the gradient to your liking. Y Tips & Tricks

    A few things you should keep in mind when working with Icon-O-Matic and some general tips for its usage:

    -

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    +

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    index Kernel Debugging Land - KDL

    @@ -140,7 +141,7 @@ In the boot loader's Debug menu you should find the en

    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.

    +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

    diff --git a/welcome/es/bugreports.html b/welcome/es/bugreports.html index c0943397..4b61aeb2 100644 --- a/welcome/es/bugreports.html +++ b/welcome/es/bugreports.html @@ -101,7 +101,8 @@ Tras haber establecido que es un fallo nuevo, haga su información tan puntual c

    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.

    +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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Kernel bugs

    @@ -113,7 +114,7 @@ Besides everything being more ugly and inconvenient, basically the same applies

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

    • -

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    +

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    index Kernel Debugging Land - KDL

    @@ -143,7 +144,7 @@ In the boot loader's Debug menu you should find the en

    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.

    +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

    diff --git a/welcome/fi/bugreports.html b/welcome/fi/bugreports.html index bc466bcb..245249ec 100644 --- a/welcome/fi/bugreports.html +++ b/welcome/fi/bugreports.html @@ -13,6 +13,7 @@ * Humdinger * Translators: * Karvjorm + * Humdinger * --> @@ -100,8 +101,9 @@ Varmista sen jälkeen kun olet esitellyt ainutlaatuisen vian, että tietosi ovat

    index Palvelinviat

    -

    Kun elintärkeät palvelimet, kuten app-, registrar- tai input-palvelin kaatuvat, et näe tavallista kaatumishälytystä. Sen sijaan koko näyttö muuttuu valkoiseksi tja gdb-istunto käynnistyy ja sen tuloste ilmaantuu näytölle. Todennäköisesti pystyt yhä liikuttamaan hiiren kohdistinta, mikä ylikirjoittaa valkoisen ja gdb-tulosteen näytöllä. Yhä vielä toimivat sovellukset (kuten Prosessivalvonta tai Työpöytäpalkin kello) saattavat myös kirjoittaa vikajäljitin tulosteen päälle näytölle.
    -Paitsi että kaikki on rumempaa ja epämukavampaa, sama koskee myös sovellusvikoja. Tärkeintä on hankkia paluujälki (bt-komento). Sinun on ehkä otettava valokuva näytöstä digitaalikameralla, koska et voi kopioida tekstiä mihinkään.

    +

    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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Käyttöjärjestelmäydinviat

    @@ -113,7 +115,7 @@ Paitsi että kaikki on rumempaa ja epämukavampaa, sama koskee myös sovellusvik

  • Järjestelmä ei alkulataa oikein. Se voi alkulatautua itsestään tai pysähtyä jossain vaiheessa (esimerkiksi jonkun alkaulatausnäytön kuvakkeen kohdalla). Yritä jälkimmäisessä tapauksessa myös ALT SysReq D.

  • Koko järjestelmä tai joku laitteiston osa ei toimi kunnolla. Esimerkiksi se voisi olla hyvin hidas, tapahtuu virheitä, tai jokin ei toimi ollenkaan. Jos jokin laite ei toimi ollenkaan, ensimmäinen ilmeinen tarkistus on, että tukeeko Haiku sitä ylimalkaan tällä hetkellä (esim.: kysy sähköpostituslistalta tai foorumilta).

    • -

    Huomaa että vaikka ainoastaan viimeinen kohta tuntuu viittaavan laittoistovikaan, kaikki muutkin oireet voivat johtua myös viasta laitteistoajurissa. Jos sinulla on epäilyjä, että mikä laitteiston osa tai vastaava ajuri aiheuttaa pulmia, tarkista, että eroaako tilanne, jos poistat tai otat pois käytöstä laitteen tai ajurin. Esimerkiksi jos epäilet Wifi-verkkoa, saatat huomata, että BIOS-asetuksissa voidaan ottaa se pois käytöstä. Tai jos ei, niin voisit merkata vastuullisen Wifi-ajurin mustalle listalle Haiku-asennuksestasi (katso Käynnistyslataaja).

    +

    Huomaa että vaikka ainoastaan viimeinen kohta tuntuu viittaavan laittoistovikaan, kaikki muutkin oireet voivat johtua myös viasta laitteistoajurissa. Jos sinulla on epäilyjä, että mikä laitteiston osa tai vastaava ajuri aiheuttaa pulmia, tarkista, että eroaako tilanne, jos poistat tai otat pois käytöstä laitteen tai ajurin. Esimerkiksi jos epäilet Wifi-verkkoa, saatat huomata, että BIOS-asetuksissa voidaan ottaa se pois käytöstä. Tai jos ei, niin voisit merkata vastuullisen Wifi-ajurin mustalle listalle Haiku-asennuksestasi (katso Käynnistyslataaja).

    index Käyttöjärjestelmäytimen viajäljitysalue - KDL

    @@ -143,7 +145,7 @@ Käynnistyslataajan Vianjäljitys-valikossa sinun pit

    Vianjäljitystulostus näytölle on hyödyllinen vain hyvin erikoisten kohteiden vianjäljityksessä ja siinä tiedetään olevan (ajoitus) pulmia.
    Se on ajankohtainen vain kun Haikun alkulataus epäonnistuu ja valikkovalinta Vikajäljitä järjestelmäloki ei jostain syystä toimi. Pidä ennen Haikun alkulatauslogon ilmaantumistta alhaalla VAIHTO-näppäintä päästäksesi alkulatausvalikkoon. Valitse Valitse turvatila-valitsimet. Lähellä alareunaa luetelleaan [ ] Ota käyttöön vikajäljitystulostus näytölle. (Huomaa: Toiset valitsime voivat olla käytössä yrityksenä alkuladata Haiku. Jos Haiku alkulatautuu vain kun yksi tai useampi valitsin on käytössä, varmista, että mainitset ne).
    Valitse lopuksi Paluu päävalikkoon ja sitten Jatka alkulatausta.
    -Yksi tai useampia tekstisivuja näytetään näytölle, vain muutama harva viimeinen rivi on liitettävä vikailmoituslippuun. Tässä on lisätietoja Alkulataajasta.

    +Yksi tai useampia tekstisivuja näytetään näytölle, vain muutama harva viimeinen rivi on liitettävä vikailmoituslippuun. Tässä on lisätietoja Alkulataajasta.

    index Laitteisto/ajuriviat

    diff --git a/welcome/fr/bugreports.html b/welcome/fr/bugreports.html index e9fe8529..4a964e4b 100644 --- a/welcome/fr/bugreports.html +++ b/welcome/fr/bugreports.html @@ -15,6 +15,7 @@ * Loïc * Vincent Duvert * roptat + * Humdinger * --> @@ -106,10 +107,9 @@ En saisissant bt, vous obtiendrez ainsi une trace de la

    index Bogues dans les serveurs

    -

    Lorsque les serveurs vitaux comme le serveur d'application, de registre ou d'entré plantent, vous ne verrez pas l'alerte de crash habituelle. à la place, l'écran sera nettoyé de blanc et une session gdb sera lancée, qui affichera directement ses restitutions à l'écran. -Il se pourrait que vous soyez toujours à même de déplacer la souris, qui dessinera alors par dessus l'écran blanc de gdb. Les demandes encore en cours (comme ProcessController ou l'horloge dans la barre de Bureau) pourrait également dessiner au dessus de la sortie du débogueur à l'écran.
    -Bien que tout soit plus laid et peu commode, les même fondamentaux que pour déboguer les applications s'appliquent. -Le plus important est de fournir une trace de la pile d'appel à l'aide de la commande bt (backtrace). Mais comme vous ne serez pas en mesure de copier le texte, vous aurez besoin de prendre une photo de l'écran avec un appareil photo numérique.

    +

    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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Bogues du noyau

    @@ -124,7 +124,7 @@ La seconde ligne dit « Welcome to Kernel Debugging Land… ». Celle a

    Notez que si seul le dernier point semble indiquer une relation avec le matériel, tous les autres symptômes pourraient aussi être causés par un bogue dans un pilote. Si vous soupçonnez un matériel ou son pilote d'être responsable du problème, vérifiez si la suppression ou la désactivation du matériel ou du pilote change quelque chose. -Par exemple, si vous soupçonnez le Wifi, votre BIOS a peut-être une option pour le désactiver. Sinon, vous pouvez supprimer le pilote Wifi installé dans Haiku (voir Chargeur de démarrage).

    +Par exemple, si vous soupçonnez le Wifi, votre BIOS a peut-être une option pour le désactiver. Sinon, vous pouvez supprimer le pilote Wifi installé dans Haiku (voir Chargeur de démarrage).

    index Le mode débogage noyau - KDL

    @@ -155,7 +155,7 @@ In the boot loader's Debug menu you should find the en

    La sortie écran du débogueur n'est utile que pour déboguer certains problèmes bien spécifiques, et est connu pour avoir des problèmes (timing). Ne l'utilisez que si vous en avez vraiment besoin.
    Ce n'est pertinent que si Haiku n'arrive pas à démarrer sur votre machine et que le Debug syslog option ne fonctionne pas pour quelque raison que ce soit. Pour accéder au menu du chargeur de démarrage, maintenez la touche MAJ enfoncée avant que le logo de Haiku n'apparaisse. Choisissez Select safe mode options. Selectionnez [ ] Enable on screen debug output que vous verrez en bas. (Notez que les autres options peuvent êtres activées pour tenter de démarrer Haiku. Si Haiku ne démarre que lorsque certaines options sont activées, n'oubliez pas de mentionner lesquelles )
    Enfin choisissez Return to main menu puis Continue booting.
    -Une ou plusieurs pages de texte seront affiché à l'écran, Seules les quelques dernières lignes ont besoin de figurer dans votre rapport de bogue. Vous trouvez plus d'information dans le sujet consacré au Chargeur de démarrage.

    +Une ou plusieurs pages de texte seront affiché à l'écran, Seules les quelques dernières lignes ont besoin de figurer dans votre rapport de bogue. Vous trouvez plus d'information dans le sujet consacré au Chargeur de démarrage.

    index Bogues liés au matériel ou aux pilotes

    diff --git a/welcome/hu/bugreports.html b/welcome/hu/bugreports.html index 5f8041f5..8716ee4e 100644 --- a/welcome/hu/bugreports.html +++ b/welcome/hu/bugreports.html @@ -13,6 +13,7 @@ * Humdinger * Translators: * Dancsó Róbert + * Humdinger * --> @@ -100,8 +101,9 @@ Miután megbizonyosodtál róla, hogy a hiba egyedi, akkor azt a lehető legpont

    index Kiszolgáló/szolgáltatás hibák

    -

    Amikor egy létfontosságú szolgáltatás, mint például az alkalmazás szolgáltatás (app_server), a registrar vagy a bemeneti eszköz szolgáltatás (input_server) hibásodik meg, akkor nem valószínű, hogy a szokásos üzenetet kapod majd. Ehelyett a teljes képernyő egy Terminálhoz hasonló képernyőre változik, ahol a hibakereső folyamat elindul, és az üzenetek ott jelennek meg. Lehetséges, hogy az egér mozgatható, ekkor azonban az egér-kurzor törli a fehér képernyőn lévő információt. A programok továbbra is futnak (például a Folyamatkezelő vagy az óra az Ásztalsávon), amik szintén törölhetik a fehér képernyőt.
    -Attól, hogy kicsit kényelmetlen, minden épp úgy működik, mint a programhibák esetében. A legfontosabb a hiba visszakövetése (bt parancs). Erről a képernyőről készíthetsz egy képet is egy digitális fényképezőgéppel, itt ugyanis nem használható a kijelölés és másolás.

    +

    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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Kernel hibák

    @@ -113,7 +115,7 @@ Attól, hogy kicsit kényelmetlen, minden épp úgy működik, mint a programhib

  • A rendszer nem megfelelően indul. Néha újraindul vagy megáll egy adott ponton (például egy indító képernyő egyik ikonjának felvillanásakor). Később ismét megpróbálható a ALT SysReq D kombináció.

  • A teljes rendszer, vagy bizonyos eszközök nem működnek megfelelően. Például nagyon lelassul vagy valami egyártalán nem működik. Ha egy eszköz nem működik, akkor elsőként azt kell kideríteni, hogy egyártalán támogatott eszközről van-e szó (például levelező listán vagy fórumon ajánlott megkérdezni).

    • -

    Ne feledd, hogy csak az utolsó pont utal eszköz hibára, azonban más problémát is okozhat egy eszközvezérlő hibája. Ha gyanítod, hogy a hibát egy adott vezérlő okozza, akkor ellenőrizd le, hogy mi változik, ha az eszközt vagy a vezérlőt eltávolítod vagy letiltod. Például, ha a Wifi-re gyanakszol, akkor próbáld meg kideríteni, hogy a BIOS-ban letiltható-e. Ha nem, akkor a gyanús vezérlőt feketelistára rakhatod (további információk a Rendszertöltő fejezetben).

    +

    Ne feledd, hogy csak az utolsó pont utal eszköz hibára, azonban más problémát is okozhat egy eszközvezérlő hibája. Ha gyanítod, hogy a hibát egy adott vezérlő okozza, akkor ellenőrizd le, hogy mi változik, ha az eszközt vagy a vezérlőt eltávolítod vagy letiltod. Például, ha a Wifi-re gyanakszol, akkor próbáld meg kideríteni, hogy a BIOS-ban letiltható-e. Ha nem, akkor a gyanús vezérlőt feketelistára rakhatod (további információk a Rendszertöltő fejezetben).

    index Kernel Debugging Land - KDL (Kernel Hibakereső Felület)

    @@ -140,10 +142,10 @@ A rendszertöltő Debug menu-ben (hibakereső menü) a

    index Hibakeresés a képernyőn

    -

    A képernyőn történő hibakeresés csak egy megadott hiba esetében hasznos, és időigényes. Ne használd, ha nem szükséges.
    -Ez akkor fontos, ha a Haiku nem tud elindulni és a hibakereső naplózás valamiért nem működik. Mielőtt a Haiku logó megjelenik, tartsd lenyomva a SHIFT-et a rendszertöltőbe való belépéshez. Válasszd a Select safe mode options (hibakereső opciók) menüt, majd azon belül az [ ] Enable on screen debug output (képernyőn történő hibakeresés engedélyezése) opciót. (Megjegyzés: több opció is haszálható betöltéskor. Ha a Haiku indításakor egy vagy több opciót is használsz, akkor azokat is említsd meg.)
    -Végül válaszd a Return to main menu (visszatérés a főmenübe), majd a Continue booting (betöltés folytatása) menüpontot.
    -Egy vagy több oldalnyi szöveg is megjelenik majd a képernyőn, amiből csak az utolsó néhány sort szükséges a jelentéshez csatolni. További információk a Rendszertöltő fejezetben.

    +

    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 Eszköz/vezérlő hibák

    diff --git a/welcome/it/bugreports.html b/welcome/it/bugreports.html index 21f03cf1..9c2dd9e1 100644 --- a/welcome/it/bugreports.html +++ b/welcome/it/bugreports.html @@ -99,7 +99,8 @@ After you have established that it's a unique bug, make your information as accu

    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.

    +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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Kernel bugs

    @@ -111,7 +112,7 @@ Besides everything being more ugly and inconvenient, basically the same applies

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

    • -

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    +

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    index Kernel Debugging Land - KDL

    @@ -141,7 +142,7 @@ In the boot loader's Debug menu you should find the en

    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.

    +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

    diff --git a/welcome/jp/bugreports.html b/welcome/jp/bugreports.html index cb96d1ec..08793832 100644 --- a/welcome/jp/bugreports.html +++ b/welcome/jp/bugreports.html @@ -57,6 +57,7 @@
    +
    このページの翻訳はまだ完全ではありません。完成するまでは、未完成の部分はオリジナルの英文を使用します。
    @@ -101,8 +102,9 @@

    index サーバーのバグ

    -

    App server、registrar、input server のような重要なサーバーがクラッシュしたときはよくあるクラッシュアラートを見ることは無いでしょう。スクリーン全体が白で塗りつぶされ、gdb のセッションがスタートします。出力はスクリーンに直接出力されます。たぶん、マウスはまだ動かせでも gdb の出力を上書きするでしょう。アプリケーションも動いたままで、(たとえば、プロセスコントローラーや デスクバーの時計のように) それも gdb の出力を上書きします。
    -さらに、アプリケーションのバグに比べ、すべては見にくく便利ではありません。アプリケーションのバグのようにはいかないでしょう。バックトレースの取得 (bt コマンド) も、テキストのコピーができないためデジタルカメラ等を用いて写真を撮影しないとならないでしょう。

    +

    App server、registrar、input server のような重要なサーバーがクラッシュしたときはよくあるクラッシュアラートを見ることは無いでしょう。その代わりに、スクリーン全体が白で塗りつぶされ、gdb のセッションがスタートします。出力はスクリーンに直接出力されます。たぶん、マウスはまだ動かせでも gdb の出力を上書きするでしょう。アプリケーションも動いたままで、(たとえば、プロセスコントローラーや デスクバーの時計のように) それも gdb の出力を上書きします。
    +さらに、アプリケーションのバグに比べ、すべては見にくく便利ではありません。アプリケーションのバグのようにはいかないでしょう。もっとも重要なバックトレースの取得 (bt コマンド) も、どこでもテキストのコピーができないのでデジタルカメラ等を用いて写真を撮影しないとならないでしょう。
    +実際にクラッシュしているものに応じて、デスクトップに save-report を使ってクラッシュレポートを保存してみてもよいです。それから電源ボタンを一度押して、手際よくシャットダウンしてみることもできます。

    index カーネルのバグ

    @@ -141,10 +143,10 @@ syslog (system log の略称) はシステムに発生した有益な情報を

    index スクリーン上でのデバッグ

    -

    スクリーン上のデバッグ出力は特定の問題とすでにわかっている問題について役立つでしょう。必要でないなら使用しないでください。
    -これは Haiku がうまく起動せず、なおかつ Debug syslog option もうまく動作しないときに使います。Haiku の起動ロゴが現れる前に、SHIFT を押したままにしてブートローダーメニューに入り、Select safe mode options を選びます。下の方にある [ ] Enable on screen debug output を有効にします (ノート: ほかのオプションも Haiku のブートを試みるときに有効になります。Haiku がどのオプションでのみ起動するかを確認してください)。
    -最後に、Return to main menu を選択し Continue booting を選択します。
    -1 ページ以上のテキストがスクリーンに表示されます。最後の数行がチケットに添付する必要がある物でしょう。詳細は、ブートローダーを参照のこと。

    +

    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 ハードウェアとドライバーのバグ

    diff --git a/welcome/pl/bugreports.html b/welcome/pl/bugreports.html index 2400c8b2..c44f614b 100644 --- a/welcome/pl/bugreports.html +++ b/welcome/pl/bugreports.html @@ -99,7 +99,8 @@ After you have established that it's a unique bug, make your information as accu

    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.

    +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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Kernel bugs

    @@ -111,7 +112,7 @@ Besides everything being more ugly and inconvenient, basically the same applies

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

    • -

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    +

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    index Kernel Debugging Land - KDL

    @@ -141,7 +142,7 @@ In the boot loader's Debug menu you should find the en

    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.

    +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

    diff --git a/welcome/pt_BR/bugreports.html b/welcome/pt_BR/bugreports.html index 74cbd5f7..fa3fab15 100644 --- a/welcome/pt_BR/bugreports.html +++ b/welcome/pt_BR/bugreports.html @@ -14,6 +14,7 @@ * Translators: * tiagoms * Adriano Duarte + * Humdinger * --> @@ -101,8 +102,9 @@ Após constatar que é um erro original, torne sua informação a mais acurada p

    index Erros de servidor

    -

    Quando servidores vitais como o servidor de aplicativo, o registrador ou o servidor de entrada travar, não se verá o alerta de travamento usual. Ao invés disso, toda a tela ficará em branco e uma sessão do gdb será iniciada, sua saída aparecendo diretamente na tela. Provavelmente você ainda será capaz de mover o mouse, o que irá sobrescrever o branco e a saída do gdb na tela. Aplicativos ainda em execução (como o Controlador de Processos ou o relógio na Deskbar) podem também aparecer sobre a saída do depurador na tela.
    -Apesar de tudo ser mais feio e inconveniente, basicamente se aplica o mesmo que aos erros de aplicativos. O mais importante é obter um "rastro" (comando bt). Pode-se precisar obter uma imagem da tela com uma câmera digital, uma vez que, de qualquer maneira, não será capaz de copiar o texto.

    +

    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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Erros do Kernel

    @@ -114,7 +116,7 @@ Apesar de tudo ser mais feio e inconveniente, basicamente se aplica o mesmo que

  • O sistema não inicializa corretamente. Ele pode reiniciar espontaneamente ou pára em algum ponto (por exemplo, em algum ícone da tela de inicialização). No último caso tente também ALT SysReq D.

  • O sistema inteiro ou alguma parte do equipamento não se comporta corretamente. Por exemplo, ele pode ficar muito lento, ocorrerem erros ou algo não funcionar absolutamente, a primeira verificação óbvia é se o Haiku já o suporta completamente (por exemplo, perguntando em uma lista de discussão ou num fórum).

    • -

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    +

    Observe que enquanto o último ponto parece indicar uma relação com hardware, todos os outros sintomas podem ser causados também por um erro num driver de dispositivo. Caso tenha uma suspeita de que parte do hardware ou o driver correspondente pode ter algo a ver com o problema, verifique se removendo/desabilitando o dispositivo ou o driver faz alguma diferença. Por exemplo, se há suspeita sobre o Wifi, pode-se procurar na BIOS uma opção para desabilitá-lo. Ou se não, pode remover o driver Wifi responsável a partir da sua instalação do Haiku (em /boot/system/add-ons/kernel/drivers/bin).

    index Terra da Depuração do Kernel - KDL

    @@ -144,7 +146,7 @@ In the boot loader's Debug menu you should find the en

    A saída em tela é útil apenas para depurar problemas muito específicos e é conhecido por ter problemas (de tempo). Não a utilize, se não precisar.
    Isto é relevante apenas quando o Haiku falha ao inicializar na sua máquina e a Opção de relatório de sistema do depurador não funciona por alguma razão. Antes da logo de inicialização do Haiku aparecer, pressione SHIFT para entrar no menu do carregador de inicialização. Selecione Selecionar opções de modo seguro. Próximo do fim, [ ] Habilitar saída de depuração na tela será listada. (Observação: As outras opções podem ser habilitadas numa tentativa de inicializar o Haiku. Se o Haiku inicializar apenas quando uma ou mais opções forem ativadas, assegure-se de mencionar quais são.)
    Finalmente selecione Voltar para o menu principal e então Continuar a inicialização.
    -Uma ou mais páginas de texto serão exibidas na tela, apenas as últimas poucas linhas precisam ser incluídas no seu tíquete. Há mais informações em Carregador de Inicialização.

    +Uma ou mais páginas de texto serão exibidas na tela, apenas as últimas poucas linhas precisam ser incluídas no seu tíquete. Há mais informações em Carregador de Inicialização.

    index Erros de Dispositivo/Driver

    diff --git a/welcome/pt_PT/bugreports.html b/welcome/pt_PT/bugreports.html index d5ae3df4..fc4df35e 100644 --- a/welcome/pt_PT/bugreports.html +++ b/welcome/pt_PT/bugreports.html @@ -99,7 +99,8 @@ After you have established that it's a unique bug, make your information as accu

    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.

    +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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Kernel bugs

    @@ -111,7 +112,7 @@ Besides everything being more ugly and inconvenient, basically the same applies

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

    • -

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    +

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    index Kernel Debugging Land - KDL

    @@ -141,7 +142,7 @@ In the boot loader's Debug menu you should find the en

    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.

    +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

    diff --git a/welcome/ro/bugreports.html b/welcome/ro/bugreports.html index d3f70a3b..230b5630 100644 --- a/welcome/ro/bugreports.html +++ b/welcome/ro/bugreports.html @@ -17,7 +17,7 @@ --> - Raportare defecțiuni + Raportarea de defecțiuni @@ -59,19 +59,19 @@
    目次
    - + Rezultatul depanării pe ecran
    + Defecțiuni hardware/driver
    + Ce urmează?
    Index
    Getting a Trac account
    - Creating a bug report
    - Application bugs
    - Server bugs
    - Kernel bugs
    +
    Obținerea unui cont Trac
    + Crearea unui raport de defecțiune
    + Defecțiuni de aplicație
    + Defecțiuni de server
    + Defecțiuni de kernel
    Kernel Debugging Land - KDL
    Syslog
    - On screen debug output
    - Hardware/Driver bugs
    - What's next?
    -

    Raportare defecțiuni

    +

    Raportarea de defecțiuni

    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.

    @@ -86,8 +86,8 @@ When creating a new account, be certain to provide your email address as

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

      • -

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

      • +

    • Încercați să replicați problema pe o revizie curentă a Haiku. Imaginile pre-compilate în scopul testării sunt disponibile online.

      • +

    • Includeți informații de bază, cum ar fi modul în care testați Haiku (pe hardware real, pe VMWare, pe QEMU, etc.).

    • Mention which revision 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.

      • @@ -101,32 +101,33 @@ After you have established that it's a unique bug, make your information as accu

      index Defecțiuni de server

      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.

      +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.
      +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

      index Defecțiuni de kernel

      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:

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

        • +

      • Sistemul repornește spontan.

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

      -

      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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

      +

      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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

      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:

      +

      KDL în sine este un fel de shell. Se pot executa comenzi care tipăresc informații despre sistem. Următoarele comenzi pot fi de interes:

      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.

      +

      Pentru mai multe informații, vedeți articolul 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).

      You can generate QR codes from KDL output that can then be converted to text using smartphones or similar devices. See the blog post QR Encode your KDL Output on how to get data out of KDL using that feature.

      @@ -139,22 +140,22 @@ If you're not able to boot to get to the previous_syslog, you have to enter the In the boot loader's Debug menu you should 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. Note: Don't accidentally boot any operating system or the data will be lost.

      index -On screen debug output

      +Rezultatul depanării pe ecran

      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.

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

      +Defecțiuni hardware/driver +

      Când aveți de a face cu o defecțiune legată de hardware/driver, ar trebui să atașați următoarele informații ca fișiere text:

      - - + + - - + +
      - 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.
      - listdev O listare detaliată de hardware, care include vânzătorul și id-uri pci, similar cu lshw și lspci din Linux.
      - listusb -v Se presupune că este o problemă legată de USB, similar cu 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.
      - listimage | grep drivers/ Listează toate driverele utilizate.
      - ints Disponibil doar în Kernel Debugging Land (vedeți mai sus). Afișează utilizarea interrupt. Nu ar trebui să fie prea multe care sunt partajate de dispozitive diferite.
      - On screen debug output (a safe mode boot time option).
      diff --git a/welcome/ru/bugreports.html b/welcome/ru/bugreports.html index f2c57849..25ac7af0 100644 --- a/welcome/ru/bugreports.html +++ b/welcome/ru/bugreports.html @@ -15,6 +15,7 @@ * Michael Smirnov * Diver * Rodastahm Islamov + * Humdinger * --> @@ -102,8 +103,9 @@

      index Ошибки серверов

      -

      Когда жизненно важный сервер, такой как app server, registrar или input server падает, вы не увидите обычное сообщение о падении приложения. Вместо этого весь экран станет белым и запустится gdb сессия, ее вывод будет попадать напрямую на экран. Скорее всего вы все еще сможете двигать курсором, что приведет к перезаписи участков белого экрана с выводом. Все еще работающие приложения (например Контроллер процессов или часы в Deskbar) могут также прорисовываться сквозь вывод отладчика на экран.
      -Кроме того, что все более выглядит более страшно и неудобно, применимо все то же самое, что и в случае ошибок приложений. Самое важное в данном случае - это выполнение трассировки коммандой (bt). Скорее всего вам понадобится сфотографировать экран, так как будет невозможно куда либо скопировать текст трассировки.

      +

      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.
      +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

      index Ошибки ядра

      @@ -115,7 +117,7 @@

    • Система не загружается корректно. Она может спонтанно перезагружаться на каком-то моменте или зависать (например на каком-то значке экрана загрузки). В случае зависания попробуйте нажать ALT SysReq D.

    • Система или какое-то устройство не работает нормально. Например если она работает очень медленно, появляются ошибки, или что-то вообще не работает. Если какое-то устройство вообще не работает первое что нужно проверить это поддерживает ли его Haiku в данный момент (например спросить в списке рассылки или на форуме).

    -

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    +

    Заметьте, что хотя только последний пункт указывает на проблему связанную с оборудованием, все остальные симптомы могут также быть вызваны ошибкой в драйвере оборудования. Если вы подозреваете, что какое-то устройство или его драйвер могут быть как-то связаны с наблюдаемой проблемой, то проверьте изменится что-либо после отключения устройства или удаления его драйвера. Например если вы подозреваете Wifi, то вы можете найти опцию в BIOS для его отключения. Если же такой опции нет, то вы можете удалить соответствующий Wifi драйвер (из папки /boot/system/add-ons/kernel/drivers/bin).

    index Царство отладки ядра - KDL @@ -147,7 +149,7 @@ In the boot loader's Debug menu you should find the en

    Функция вывода отладочной информации на экран полезна для отладки только специфичных проблем, она также имеет известные проблемы с таймингами. Используйте ее только если это очень необходимо.
    Ее использование имеет смысл только когда Haiku не загружается на вашем компьютереи функция Debug syslog option по какой-то причине не работает. Перед появлением загрузочного экрана зажмите SHIFT для входа в меню загрузчика. Выберите Select safe mode options. Почти в самом низу будет опция, [ ] Enable on screen debug output. (Имейте в виду, что можно включить остальные опции, чтобы Haiku загрузилась. Если Haiku будет загружаться только при включении одной или более опций, не забудьте указать какие именно.)
    И наконец выбарите Return to main menu, а затем then Continue booting.
    -Одна страница текста или более появятся на экране, только последние несколько строк нужно включать в ваш багрепорт. Дополнительная информация имеется в статье Загрузчик.

    +Одна страница текста или более появятся на экране, только последние несколько строк нужно включать в ваш багрепорт. Дополнительная информация имеется в статье Загрузчик.

    index Аппаратные ошибки/Ошибки в драйверах

    diff --git a/welcome/sk/bugreports.html b/welcome/sk/bugreports.html index a639d655..43eb5ab0 100644 --- a/welcome/sk/bugreports.html +++ b/welcome/sk/bugreports.html @@ -13,6 +13,7 @@ * Humdinger * Translators: * helix84 + * Humdinger * --> @@ -100,8 +101,9 @@ Potom, ako ste sa uistili, že chyba je jedinečná, uveďte čo najpresnejšie

    index Chyby serverov

    -

    Ak havarujú dôležité servery ako aplikačný server, registrátor alebo server vstupu, neuvidíte zvyčajné upozornenie na haváriu. Namiesto toho sa celá obrazovka zmaže na bielu farbu, spustí sa relácia gdb a jej výstup sa objaví priamo na obrazovke. Pravdepodobne budete môcť pohybovať myšou, čo prepíše bielu farbu a výstup gdb na obrazovke. Aplikácie, ktoré ešte bežia (ako ProcessController alebo hodiny v Paneli) tiež možno prekreslia časť ladiaceho výstupu na obrazovke.
    -Okrem toho, že je všetko škaredšie a nepohodlné platí prakticky to isté ako pri chybách aplikácií. Predovšetkým získajte backtrace (príkaz bt). Možno budete musieť odfotiť obrazovku digitálnym fotoaparátom, pretože nebudete môcť text nikam skopírovať.

    +

    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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Chyby jadra

    @@ -113,7 +115,7 @@ Okrem toho, že je všetko škaredšie a nepohodlné platí prakticky to isté a

  • Systém nenaštartuje korektne. Môže spontánne naštartovať alebo v niektorom bode zastaviť (napr. na niektorej ikone štartovacej obrazovky). V druhom prípade tiež skúste ALT SysReq D.

  • Celý systém alebo niektorá časť hardvéru sa nespráva korektne. Napríklad môže byť veľmi pomalý, vyskytnú sa chyby alebo niečo vôbec nefunguje. Ak nejaký hardvér vôbec nefunguje, prvá vec, ktorú treba skontrolovať je, či ho momentálne Haiku vôbec podporuje (napr. spýtať sa v poštovej konferencii alebo na fóre).

    • -

    Pamätajte, že hoci iba posledný bod indikuje súvislosť s hardvérom, všetky ostatné symptómy môžu byť spôsobené aj chybou v ovládači hardvéru. Ak máte podozrenie, ktorá časť hardvéru alebo zodpovedajúci ovládač môže súvisieť s problémom, skontrolujte, či odstránenie alebo vypnutie hardvéru či ovládača pomôže. Napríklad ak podozrievate Wi-Fi, možno zistíte, že váš BIOS umožňuje ju vypnúť. Alebo ak nie, môžete odstrániť príslušný ovládač Wi-Fi z vašej inštalácie Haiku (pozri Zavádzač systému).

    +

    Pamätajte, že hoci iba posledný bod indikuje súvislosť s hardvérom, všetky ostatné symptómy môžu byť spôsobené aj chybou v ovládači hardvéru. Ak máte podozrenie, ktorá časť hardvéru alebo zodpovedajúci ovládač môže súvisieť s problémom, skontrolujte, či odstránenie alebo vypnutie hardvéru či ovládača pomôže. Napríklad ak podozrievate Wi-Fi, možno zistíte, že váš BIOS umožňuje ju vypnúť. Alebo ak nie, môžete odstrániť príslušný ovládač Wi-Fi z vašej inštalácie Haiku (pozri Zavádzač systému).

    index Kernel Debugging Land - KDL

    @@ -143,7 +145,7 @@ V menu Ladenie zavádzača by ste mali nájsť položk

    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.

    +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 Chyby hardvéru/ovládačov

    diff --git a/welcome/sv_SE/bugreports.html b/welcome/sv_SE/bugreports.html index d6dbb41b..8f0c2210 100644 --- a/welcome/sv_SE/bugreports.html +++ b/welcome/sv_SE/bugreports.html @@ -101,7 +101,8 @@ After you have established that it's a unique bug, make your information as accu

    index Serverbuggar

    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.

    +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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Buggar i kärnan

    @@ -113,7 +114,7 @@ Besides everything being more ugly and inconvenient, basically the same applies

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

    • -

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    +

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    index Kernel Debugging Land - KDL

    @@ -143,7 +144,7 @@ In the boot loader's Debug menu you should find the en

    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.

    +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 Hårdvara/drivrutinsbuggar

    diff --git a/welcome/uk/bugreports.html b/welcome/uk/bugreports.html index 84b2705c..33be7037 100644 --- a/welcome/uk/bugreports.html +++ b/welcome/uk/bugreports.html @@ -99,7 +99,8 @@ After you have established that it's a unique bug, make your information as accu

    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.

    +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.
    +Depending on what exactly crashed, you can try to save a crash report on the Desktop with save-report and then press the power button once to try shutting cleanly down.

    index Kernel bugs

    @@ -111,7 +112,7 @@ Besides everything being more ugly and inconvenient, basically the same applies

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

    • -

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    +

    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 blacklist the responsible Wifi driver from your Haiku installation (see Boot Loader).

    index Kernel Debugging Land - KDL

    @@ -141,7 +142,7 @@ In the boot loader's Debug menu you should find the en

    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.

    +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

    diff --git a/welcome/welcome_ca.html b/welcome/welcome_ca.html index 94716a82..46930b94 100644 --- a/welcome/welcome_ca.html +++ b/welcome/welcome_ca.html @@ -4,7 +4,7 @@