|
|
32.
|
|
|
This is an optional step.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
|
33.
|
|
|
This page will search the bug report database for similar crashes which are possible duplicates of your bug. If there are similar bug reports found, you can double click on them to see details. Then, read the current bug report information so you can check to see if they are similar.
|
| Context: |
|
@info/rich
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
Aquesta pagina recercara dins la basa dels rapòrts de bugs los plantatges potencialament similars al vòstre. Se certans rapòrts similars son trobats, poiretz doble clicar dessús per ne consultar los detalhs. La lectura del rapòrt vos permetrà de definir e de marcar se òc o non los plantatges son similars.
|
|
Translated by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:143
|
|
|
34.
|
|
|
If you are very sure your bug is the same as another that is previously reported, you can open the previously reported crash in the bug tracking program by clicking on <interface>Bug report page at the KDE bug tracking system</interface>. You can then add any new information that you might have.
|
| Context: |
|
@info/rich
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
35.
|
|
|
If you are unsure whether your report is the same, follow the main options to tentatively mark your crash as a duplicate of that report. This is usually the safest thing to do. We cannot uncombine bug reports, but we can easily merge them.
|
| Context: |
|
@info/rich
|
|
|
|
|
Se avètz pas la certitud que vòstre rapòrt siá identic, seguissètz las opcions generalas per provisòriament marcar vòstre plantatge coma duplicata d'aqueste rapòrt. Aqueste metòde es totjorn la mai segura. Podèm pas decopar de rapòrts de bugs mas es simple de los fusionar.
|
|
Translated by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:151
|
|
|
36.
|
|
|
If not enough possible duplicates are found, or you did not find a similar report, then you can force it to search for more bug reports (only if the date range is not reached.)
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:173
|
|
|
37.
|
|
|
Do not worry if you cannot find a similar bug report or you do not know what to look at. The bug report database maintainers will look at it later. It is better to file a duplicate then to not file at all.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
|
38.
|
|
|
Details of the Bug report
|
| Context: |
|
@title
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:183
|
|
|
39.
|
|
|
In this case you need to write a title and description of the crash. Explain as best you can.
|
| Context: |
|
@info/rich
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
Dins aquel cas, picatz un títol e una descripcion per aqueste plantatge. Detalhatz-lo tan plan coma possible.
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:167
|
|
|
40.
|
|
|
Send Crash Report
|
| Context: |
|
@title
|
|
|
|
|
Mandar un rapòrt de plantatge
|
|
Translated and reviewed by
Cédric VALMARY (Tot en òc)
|
|
|
|
Located in
reportassistantdialog.cpp:141
|
|
|
41.
|
|
|
This page will send the bug report to the bug tracking system and will notify you when it is done. It will then show the web address of the bug report in the KDE bug tracking system, so that you can look at the report later.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:194
|
