kde/drkonqi/drkonqi5 — English @ Fedora Weblate: If you can, describe in as much detail as possible …

Source string Source string

Context

English

If you can, describe in as much detail as possible the crash circumstances, and what you were doing when the application crashed (this information is going to be requested later.) You can mention:

Needs editing

The string is read only.

Skip

	Context	English	Actions
	NAME OF TRANSLATORS	Your names
	EMAIL OF TRANSLATORS	Your emails
	@title title of the dialog	About Bug Reporting - Help
	@title	Information about bug reporting
	@info/rich	You can help us improve this software by filing a bug report.
	@info/rich	<note>It is safe to close this dialog. If you do not want to, you do not have to file a bug report.</note>
	@info/rich	In order to generate a useful bug report we need some information about both the crash and your system. (You may also need to install some debug packages.)
	@title	Bug Reporting Assistant Guide
	@info/rich	This assistant will guide you through the crash reporting process for the KDE bug tracking system. All the information you enter on the bug report <strong>must be written in English</strong>, if possible, as KDE is formed internationally.
	@title	What do you know about the crash?
	@info/rich	In this page you need to describe how much do you know about the desktop and the application state before it crashed.
	@info/rich	If you can, describe in as much detail as possible the crash circumstances, and what you were doing when the application crashed (this information is going to be requested later.) You can mention:
	@info/rich crash situation example	actions you were taking inside or outside the application
	@info/rich crash situation example	documents or images that you were using and their type/format (later if you go to look at the report in the bug tracking system, you can attach a file to the report)
	@info/rich crash situation example	widgets that you were running
	@info/rich crash situation example	the URL of a web site you were browsing
	@info/rich crash situation example	configuration details of the application
	@info/rich crash situation example	or other strange things you notice before or after the crash.
	@info/rich	Screenshots can be very helpful sometimes. You can attach them to the bug report after it is posted to the bug tracking system.
	@title	Crash Information (backtrace)
	@info/rich	This page will generate a "backtrace" of the crash. This is information that tells the developers where the application crashed.
	@info/rich	If the crash information is not detailed enough, you may need to install some debug packages and reload it (if the <interface>Install Debug Symbols</interface> button is available you can use it to automatically install the missing information.)
	@info/rich	You can find more information about backtraces, what they mean, and how they are useful at <link>%1</link>
	@info/rich	Once you get a useful backtrace (or if you do not want to install the missing debugging packages) you can continue.
	@title	Conclusions
	@info/rich	Using the quality of the crash information gathered, and your answers on the previous page, the assistant will tell you if the crash is worth reporting or not.
	@info/rich	If the crash is worth reporting but the application is not supported in the KDE bug tracking system, you will need to directly contact the maintainer of the application.

Loading…

No matching activity found.

Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatched colon: Hebrew, Hebrew

Reset

Glossary

English	English
No related strings found in the glossary.

String information

Context

@info/rich

Flags

kde-kuit-format, read-only

Source string location

aboutbugreportingdialog.cpp:64

String age

3 years ago

Last updated

10 months ago

Source string age

3 years ago

Translation file

templates/drkonqi/drkonqi5.pot, string 12