2. fedora-docs-l10n/quick-docs
3. master/pages/bugzilla-file-a-bug
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:empty

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — German	*Most enhancement requests should be filed upstream.* If the software is missing a feature you think it should have, you generally want to file that in the upstream project's bug tracker. Feature requests in Fedora Linux are generally changing defaults, enabling disabled-by-default features, etc.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Norwegian Nynorsk	*Most enhancement requests should be filed upstream.* If the software is missing a feature you think it should have, you generally want to file that in the upstream project's bug tracker. Feature requests in Fedora Linux are generally changing defaults, enabling disabled-by-default features, etc.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Korean	*Most enhancement requests should be filed upstream.* If the software is missing a feature you think it should have, you generally want to file that in the upstream project's bug tracker. Feature requests in Fedora Linux are generally changing defaults, enabling disabled-by-default features, etc.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — French	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Czech	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Italian	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Japanese	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Brazil)	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Portugal)	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Telugu	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Chinese (Simplified Han script)	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Arabic	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — German	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Norwegian Nynorsk	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Korean	When filing an enhancement request in Bugzilla, add the keyword `Future Feature` to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — French	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Czech	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Italian	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Japanese	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Brazil)	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Portugal)	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Telugu	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Chinese (Simplified Han script)	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Arabic	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — German	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Norwegian Nynorsk	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Korean	The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] page for details about this.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — French	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Czech	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Italian	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Japanese	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Brazil)	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Portugal)	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Telugu	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Chinese (Simplified Han script)	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Arabic	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — German	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Norwegian Nynorsk	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Korean	If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the xref:program_management::changes_policy.adoc[Changes Process].
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — French	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Czech	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Italian	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Japanese	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Brazil)	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Portugal)	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Telugu	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Chinese (Simplified Han script)	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Arabic	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — German	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Norwegian Nynorsk	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Korean	Requests for new packages to be added to Fedora should not be filed in Bugzilla.
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — French	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Czech	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Italian	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Japanese	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Brazil)	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Portugal)	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Telugu	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Chinese (Simplified Han script)	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Arabic	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — German	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Norwegian Nynorsk	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Korean	Graphical User Interfaces
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — French	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Czech	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Italian	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Japanese	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Brazil)	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Portugal)	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Telugu	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Chinese (Simplified Han script)	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Arabic	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — German	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Norwegian Nynorsk	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Korean	If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — French	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Czech	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Italian	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Japanese	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Brazil)	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Portugal)	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Telugu	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Chinese (Simplified Han script)	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Arabic	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — German	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Norwegian Nynorsk	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Korean	Hardware-Specific Bugs
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — French	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Czech	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Italian	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Japanese	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Brazil)	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Portuguese (Portugal)	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Telugu	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Chinese (Simplified Han script)	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Arabic	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — German	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Norwegian Nynorsk	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — Korean	A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can't. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).
	fedora-docs-l10n/quick-docs/master/pages/bugzilla-file-a-bug — French	If you suspect your bug has something to do with the specific hardware you have, it will be necessary to identify the hardware so targeted action can be taken.

• 12 / 16
  / 16