From 1cae99d78e268a6449d57bbfd4378208779a1d32 Mon Sep 17 00:00:00 2001 From: Joachim Seemer Date: Thu, 15 Apr 2010 18:02:06 +0000 Subject: [PATCH] Updated welcome page. Thanks to all translators. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36309 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- docs/welcome/images/flags/uk.png | Bin 0 -> 625 bytes docs/welcome/uk/bugreports.html | 105 +++++++++++++++++++++++++ docs/welcome/welcome_de.html | 12 ++- docs/welcome/welcome_en.html | 12 ++- docs/welcome/welcome_es.html | 11 ++- docs/welcome/welcome_fr.html | 15 ++-- docs/welcome/welcome_it.html | 12 ++- docs/welcome/welcome_jp.html | 12 ++- docs/welcome/welcome_ru.html | 16 ++-- docs/welcome/welcome_sv_SE.html | 12 ++- docs/welcome/welcome_uk.html | 129 +++++++++++++++++++++++++++++++ 11 files changed, 300 insertions(+), 36 deletions(-) create mode 100644 docs/welcome/images/flags/uk.png create mode 100644 docs/welcome/uk/bugreports.html create mode 100644 docs/welcome/welcome_uk.html diff --git a/docs/welcome/images/flags/uk.png b/docs/welcome/images/flags/uk.png new file mode 100644 index 0000000000000000000000000000000000000000..b17c44c29a16d31f4f2476fdfdfda08a66d08968 GIT binary patch literal 625 zcmV-%0*?KOP)z@;j(q!3lK=n!AY({UO#lFTB>(_`g8%^e{{R4h=>PzA zFaQARU;qF*m;eA5Z<1fdMgRZ-=Sf6CR47wpXzW;V{N9IYYcI9T1)}p!v(G+!@^N4D z?7fXMfsFjFqj_z|Q|k`Y%s#QPw0Fm;2MmQJ-TybP`uFeu?T23$ZMZ#u{T(3t|CFBp zeXT&oq=lDz=UzB@;_<((nty+P?!Wwm!6mwN&&hZHmoEQ*aPR;B|J$Zr1(N?$Gyf+f z0_l>zOJ5eP`QF_PWY1f5sjBM;NW;Pnck3ozeYo%bpQif%5D*jdKRg1&$j$u!;>CqK zZyi0C7d0IzYdgR&ZRQe?8_+;#=zl*yG%=vEN6$Yolskw0pWN|3CFOs7{Qt9{`6>oA>x#we zK_Tg72zzrx}8?o65}t%tD&@ zlxw*Z%Gl&emaW;HEvB0#q_ud}ZU&(k2Eix>{s;l})WYd&gPbb>BD-nx46I3r00000 LNkvXXu0mjfj1n<0 literal 0 HcmV?d00001 diff --git a/docs/welcome/uk/bugreports.html b/docs/welcome/uk/bugreports.html new file mode 100644 index 0000000000..17bed56ec0 --- /dev/null +++ b/docs/welcome/uk/bugreports.html @@ -0,0 +1,105 @@ + + + + + + + + Reporting bugs + + + + + + +
+
+ + + Welcome +
+
+ +
+
+ +

Reporting bugs

+ +

Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.

+

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

+ +

Getting a Trac account

+

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

+ +

Creating a bug report

+

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

+
    +

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

    • +

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

    • +

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

    • +

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

    • +

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

    • +
+ +

Software Bugs

+

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

+ +

Hardware Bugs

+

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

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

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

+ +

Kernel Debugging Land - KDL

+

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

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

What's next?

+

After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding +non-descriptive comments.

+

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

+ +
+
+ +
+
+ Welcome +
+
+ + + diff --git a/docs/welcome/welcome_de.html b/docs/welcome/welcome_de.html index 1cd30ab734..cfa35478f2 100644 --- a/docs/welcome/welcome_de.html +++ b/docs/welcome/welcome_de.html @@ -4,7 +4,7 @@ @@ -36,6 +36,7 @@
  • Español
  • Svensk
  • 日本語
    • +
  • Українська
  • English
    • @@ -48,7 +49,7 @@

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

    -

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

    +

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

    index @@ -75,8 +76,6 @@ index Установка дополнительных программ

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

    -
    Исключением являются опциональные пакеты (OptionalPackages), которые уже включены в Haiku при её компиляции из исходных кодов, однако их также можно загрузить и добавить в любую установленную копию Haiku. У них одно отличие от обычных архивов с программами: их следует распаковывать в корень загрузочного диска /boot.
    -Для отладочных целей на сайте с опциональными пакетами хранятся их устаревшие версии, которые не совместимы с новыми ревизиями Haiku, и они в первую очередь предназначены для разработчиков, но не для конечных пользователей.

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

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

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

    +

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

    +

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

    diff --git a/docs/welcome/welcome_sv_SE.html b/docs/welcome/welcome_sv_SE.html index 6abf915763..4be39af7f2 100644 --- a/docs/welcome/welcome_sv_SE.html +++ b/docs/welcome/welcome_sv_SE.html @@ -4,7 +4,7 @@ + + + Вітаємо в Haiku! + + + + + + +
    +
    + + +  +
    +
    + +
    +
    + +

    +Вітаємо в Haiku!

    +

    Thank you very much for checking out Haiku! This is our first public release. We hope to attract new developers to our project and give future users a chance to check out Haiku. We realize that this alpha release does not yet fully live up to the goals that we have set for ourselves and doesn't offer all the features and well-rounded end-user experience planned for the final R1 version. However, we hope that this release lets you discover Haiku's great potential and that you share our excitement.

    + +

    +index +Beware of Bugs

    +

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

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

    One of the main reasons for releasing an alpha version is to attract more people to test the system and discover bugs or provide suggestions for future enhancements. Please file bugs and enhancements in our bug tracker after using its search function to avoid duplicates.

    + + +

    +index +Getting to know the system

    +

    The first release(s) of Haiku will be very much like the BeOS R5, the operating system it is reimplementing. If you never experienced it, have a look at these links:

    + + +

    +index +Installing more software

    +

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

    + +

    Popular software repositories are:

    + + +

    There are also so called Optional Packages, which are used by Haiku's build system. It is not intended for end users to manually extract and install them. However, a utility script is provided, installoptionalpackage. This script is meant to bridge the gap while Haiku's package management is still under construction. It will allow you to install most of the available Optional Packages.
    +You'll have to run a command in Terminal:

    +

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

    + +

    +index +Getting to know the API

    +

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

    + +

    There are additional resources that should help you getting started:

    + + +

    +index +Getting in contact

    +

    Get in contact with other developers and users and join the discussions on IRC, in our forums or the mailing lists. When many different people come together, rules have to established to keep communication effective. Please respect our Mailing List Etiquette.

    + + +
    +
    + +
    +
    +  +
    +
    + + +