Browsing Turkish translation

Don't show this notice anymore
Before translating, be sure to go through Ubuntu Translators instructions and Turkish guidelines.
110 of 46 results
4.
A critical error occurred during %s execution,
and it was not properly reported to our bug tracker. Please,
copy the error message bellow and report it on our bug tracker.

The following error message was NOT reported:
%s
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in zenmap:84
11.
Specify a scan result file in Nmap XML Output or Umit Scan Result file. Can be used more than once to specify several scan result files.
(no translation yet)
Located in zenmapCore/UmitOptionParser.py:47
28.
Entering the text into the search performs a <b>keyword search</b> - the search string is matched against the entire output of each scan.

To refine the search, you can use <b>operators</b> to search only within a specific part of a scan. Operators can be added to the search interactively if you click on the <b>Expressions</b> button, or you can enter them manually into the search field. You can also use <b>operator aliases</b> if you're an experienced user who likes to type in his searches quickly.

<b>profile: (pr:)</b> - Profile used.
<b>target: (t:)</b> - User-supplied target, or a rDNS result.
<b>option: (o:)</b> - Scan options.
<b>date: (d:)</b> - The date when scan was performed. Fuzzy matching is possible using the "~" suffix. Each "~" broadens the search by one day on "each side" of the date. In addition, it is possible to use the "date:-n" notation which means "n days ago".
<b>after: (a:)</b> - Matches scans made after the supplied date (<i>YYYY-MM-DD</i> or <i>-n</i>).
<b>before (b:)</b> - Matches scans made before the supplied date(<i>YYYY-MM-DD</i> or <i>-n</i>).
<b>os:</b> - All OS-related fields.
<b>scanned: (sp:)</b> - Matches a port if it was among those scanned.
<b>open: (op:)</b> - Open ports discovered in a scan.
<b>closed: (cp:)</b> - Closed ports discovered in a scan.
<b>filtered: (fp:)</b> - Filtered ports discovered in scan.
<b>unfiltered: (ufp:)</b> - Unfiltered ports found in a scan (using, for example, an ACK scan).
<b>open|filtered: (ofp:)</b> - Ports in the "open|filtered" state.
<b>closed|filtered: (cfp:)</b> - Ports in the "closed|filtered" state.
<b>service: (s:)</b> - All service-related fields.
<b>inroute: (ir:)</b> - Matches a router in the scan's traceroute output.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in zenmapGUI/SearchGUI.py:250
30.
%s can search results on directories or inside it's own database. Please, select a method by choosing a directory or by checking the search data base option at the 'Search options' tab before start the search
(no translation yet)
Located in zenmapGUI/SearchGUI.py:431
67.
An email address is optional. Sometimes we use it to get more information. If you provide an email address your report will be marked private so only project developers can read it.
(no translation yet)
Located in zenmapGUI/CrashReport.py:59
69.
An unhandled exception has crashed Zenmap. This dialog allows you to tell us what you did to cause the crash and help us to fix it. Submitting the report will open a description of the new bug at the bug tracker. Feel free to edit the report to remove any identifying information such as your home directory.
(no translation yet)
Located in zenmapGUI/CrashReport.py:74
98.
<big><b>How to report a bug</b></big>

Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from <b>%(nmap_web)s</b>. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <b>&lt;nmap-dev@insecure.org&gt;</b>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org are far more likely to be answered than those sent to Fyodor directly.

Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at http://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in zenmapGUI/BugReport.py:56
102.
There was an error parsing the configuration file %s. The specific error was

%s

%s can continue without this file but any information in it will be ignored until it is repaired.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in zenmapGUI/App.py:312
113.
Append a saved scan to the list of scans in this window.
(no translation yet)
Located in zenmapGUI/MainWindow.py:278
138.
There are no scans with results to be saved. Run a scan with the "Scan" button first.
(no translation yet)
Located in zenmapGUI/MainWindow.py:629
110 of 46 results

This translation is managed by Ubuntu'yu Türkçe'ye Çevirenler Takımı, assigned by Ubuntu Translators.

You are not logged in. Please log in to work on translations.

Contributors to this translation: Efe Çiftci, Fatih Bostancı, Kadir Can ÇELİK, Mümin Köykıran, Yusuf ÜLKÜ, afterlife, ergin üresin, irmak, kulkke, meda, ubuntuki, zeugma.