natgillin/translations-raw huggingface dataset:
Moving files or folders to wastebin@option: check Ask for Confirmation When
ફાઇલો અથવા ફોલ્ડરો કચરાપેટીમાં ખસેડતાં હોવ@ option: check Ask for Confirmation When
Deleting files or folders@option: check Ask for Confirmation When
ફાઇલો અથવા ફોલ્ડરો દૂર કરતાં હોવ@ option: check Ask for Confirmation When
Closing windows with multiple tabs@option: check
અનેક ટેબ્સ સાથે વિન્ડોસ બંધ કરી રહ્યા છીએ@ option: check
Show selection markeroption: check
પસંદગી નિશાની બતાવોoption: check
Natural sorting of items@action: button
વસ્તુની મૂળભૂત ગોઠવણી@ action: button
Configure which data should be shown in the tooltip. @title: window
સાધનટીપ્પણીમાં કઈ માહિતી દર્શાવવી છે તે નક્કી કરો. @ title: window
View mode: @item: inlistbox
દેખાવ સ્થિતિ@ item: inlistbox
Sorting: @item: inlistbox Sort
ગોઠવણી: @ item: inlistbox Sort
Ascending@item: inlistbox Sort
ચઢતાં ક્રમમાં@ item: inlistbox Sort
Descending@action: inmenu Sort
ઉતરતા ક્રમનું@ action: inmenu Sort
By Name@item: inlistbox Sort
નામ વડે@ item: inlistbox Sort
By Size@item: inlistbox Sort
માપ વડે@ item: inlistbox Sort
By Date@item: inlistbox Sort
તારીખ વડે@ item: inlistbox Sort
By Permissions@item: inlistbox Sort
પરવાનગીઓ વડે@ item: inlistbox Sort
By Owner@item: inlistbox Sort
માલિક વડે@ item: inlistbox Sort
By Group@item: inlistbox Sort
સમૂહ વડે@ item: inlistbox Sort
By Type@option: check
પ્રકાર વડે@ option: check
Show folders first@option: check
ફોલ્ડરો પ્રથમ દર્શાવો@ option: check
Show in groups@option: check
સમૂહમાં બતાવો@ option: check
Apply View Properties To@option: radio Apply View Properties To
દેખાવ ગુણધર્મોને અહીં અમલમાં મૂકો@ option: radio Apply View Properties To
Current folder@option: radio Apply View Properties To
હાલનું ફોલ્ડર@ option: radio Apply View Properties To
Current folder including all sub folders@option: radio Apply View Properties To
હાલનું ફોલ્ડર તેનાં બધાં ઉપફોલ્ડરો સાથે@ option: radio Apply View Properties To
All folders@option: check
બધાં ફોલ્ડરો@ option: check
Use as default for new folders@info
નવાં ફોલ્ડરો માટે મૂળભૂત તરીકે વાપરો@ info
The view properties of all sub folders will be changed. Do you want to continue? @info
બધાં ઉપફોલ્ડરોનાં દેખાવ ગુણધર્મો બદલાઇ જશે. શું તમે આગળ વધવા માંગો છો? @ info
The view properties of all folders will be changed. Do you want to continue? @option: check
બધાં ફોલ્ડરોનાં દેખાવ ગુણધર્મો બદલાઇ જશે. શું તમે આગળ વધવા માંગો છો? @ option: check
Date@action: inmenu Sort By
તારીખ@ action: inmenu Sort By
Group@action: inmenu Sort By
સમૂહ@ action: inmenu Sort By
Unknown size@info: status Free disk space
અજાણ્યું માપ@ info: status Free disk space
%1 free@action
% 1 મુક્ત@ action
Create Folder... @action: inmenu File
ફોલ્ડર બનાવો... @ action: inmenu File
Delete (using shortcut for Wastebin)@action: inmenu File
દૂર કરો (કચરાપેટીની ટૂંકાણ કળ વાપરીને) @ action: inmenu File
Show preview of files and folders@action: inmenu Sort
ફાઇલો અને ફોલ્ડરોનું પૂર્વદર્શન બતાવો@ action: inmenu Sort
Folders First@action: inmenu View
ફોલ્ડરો પ્રથમ@ action: inmenu View
Show in Groups@action: inmenu View
સમૂહોમાં બતાવો@ action: inmenu View
Adjust View Properties... @action: inmenu Tools
દેખાવ ગુણધર્મો ગોઠવો... @ action: inmenu Tools
Find File... @action: inmenu Additional information
ફાઇલ શોધો... @ action: inmenu Additional information
Name@action: inmenu Sort By
નામ@ action: inmenu Sort By
Icons view mode@action: inmenu View Mode
ચિહ્ન દેખાવ સ્થિતિ@ action: inmenu View Mode
Details view mode@action: inmenu View Mode
વિસ્તૃત દેખાવ સ્થિતિ@ action: inmenu View Mode
Columns view mode@action: inmenu Settings
સ્થંભ દેખાવ સ્થિતિ@ action: inmenu Settings
Navigation Bar@info: tooltip
શોધખોળ પટ્ટી@ info: tooltip
Date Modified@label
બદલેલ: @ item: inlistbox Sort
File Size@info: status
માપ વડે@ info: status
Copy operation completed. @info: status
નકલ પ્રક્રિયા પૂર્ણ થઇ. @ info: status
Move operation completed. @info: status
ખસેડવાની પ્રક્રિયા પૂર્ણ થઇ. @ info: status
Link operation completed. @info: status
કડી બનાવવાની પ્રક્રિયા પૂર્ણ થઇ. @ info: status
Move to wastebin operation completed. @info: status
કચરાપેટીમાં ખસેડવાની પ્રક્રિયા પૂર્ણ થઇ. @ info: status
Renaming operation completed. @title: group
નામ બદલવાની પ્રક્રિયા પૂર્ણ થઇ. @ title: group
Texts
લખાણ
Show comment
ટીપ્પણી બતાવો
Show tags@title: window subtitle to previous message
ટેગ્સ બતાવો@ title: window subtitle to previous message
with optional icon and description@label Indicator when no tags defined
વધારાનાં ચિહ્ન અને વર્ણન સાથે@ label Indicator when no tags defined
No Tags
કોઇ ટેગ્સ નહી
Detailed description (optional): and ss in a logic operator to connect search terms
વિસ્તૃત વર્ણન (વૈકલ્પિક):
& Edit@title: group Tags
ફેરફાર (E) @ title: group Tags
Not yet tagged@action: inmenu
હજી સુધી ટેગ ન કરેલ@ action: inmenu
Move To Wastebin@action: inmenu File
કચરાપેટીમાં ખસેડો
About Bug Reporting - Help@title
ક્ષતિ અહેવાલ વિશે - મદદ@ title
Information about bug reporting@info/ rich
ક્ષતિ અહેવાલ વિશે માહિતી@ info/ rich
You can help us improve this software by filing a bug report. @info/ rich
તમે ક્ષતિ અહેવાલ રજૂ કરીને આ સોફ્ટવેરની ગુણવત્તામાં સુધારો કરવામાં અમને મદદ કરી શકો છો. @ info/ rich
It is safe to close this dialogue. If you do not want to, you do not have to file a bug report. @info/ rich
@ 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
@ title
Bug Reporting Assistant Guide@info/ rich
ક્ષતિ અહેવાલ મદદ માર્ગદર્શિકા@ info/ rich
This assistant will guide you through the crash reporting process for the KDE Bug Reports Database Site. All the information you enter on the bug report must be in English, if possible, as KDE is formed internationally. @title
@ title
What do you know about the crash? @info/ rich
ભંગાણ વિશે તમે શું જાણો છો? @ 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
@ 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
@ info/ rich crash situation example
actions you were taking inside or outside the application@info/ rich crash situation example
@ 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
@ info/ rich crash situation example
widgets that you were running@info/ rich crash situation example
તમે ચલાવી રહ્યા છો તે વિજેટ્સ@ info/ rich crash situation example
the URL of a web site you were browsing@info/ rich crash situation example
તમે જોઈ રહ્યા હતા એ વેબ સાઈટનું URL@ info/ rich crash situation example
configuration details of the application@info/ rich crash situation example
@ info/ rich crash situation example
or other strange things you notice before or after the crash. @info/ rich
@ 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
@ title
Crash Information (backtrace)@info/ rich
ભંગાણ માહિતી (બેકટ્રેસ) @ info/ rich
This page will generate a "backtrace" of the crash. This is information that tells the developers where the application crashed. @info/ rich
@ info/ rich
If the crash information is not detailed enough, you may need to install some debug packages and reload it (if the Install Debug Symbols button is available you can use it to automatically install the missing information). @info/ rich
@ info/ rich
You can find more information about backtraces, what they mean, and how they are useful at %1 @info/ rich
@ info/ rich
Once you get a useful backtrace (or if you do not want to install the missing debugging packages) you can continue. @title
@ title
Conclusions@info/ rich
તારણો@ 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
@ 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. @info/ rich
@ info/ rich
If the crash is listed as being not worth reporting, and you think the assistant has made a mistake, you can still manually report the bug by logging into the bug tracking system. You can also go back and change information and download debug packages. @title
@ title
Login into the bug tracking system@info/ rich
@ info/ rich
We may need to contact you in the future to ask for further information. As we need to keep track of the bug reports, you need to have an account on the KDE bug tracking system. If you do not have one, you can create one here: %1 @info/ rich
@ info/ rich
Then, enter your username and password and press the Login button. You can use this login to directly access the KDE bug tracking system later. @info/ rich
@ info/ rich
The KWallet dialogue may appear when pressing Login to save your password in the KWallet password system. Also, it will prompt you for the KWallet password upon loading to autocomplete the login fields if you use this assistant again. @title
@ title
List of possible duplicate reports@info/ rich
@ info/ rich
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. @info/ rich
@ info/ rich
If you are very sure your bug is the same as another that is previously reported, you can set your information to be attached to the existing report. @info/ rich
@ info/ rich
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. @info/ rich
@ info/ rich
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 limit is not reached). @info/ rich
@ info/ rich
If you do not find any related reports, your crash information is not useful enough, and you really cannot give additional information about the crash context, then it is better to not file the bug report, thereby closing the assistant. @title
@ title
Details of the bug report and your system@info/ rich
ક્ષતિ અહેવાલની વિગતો@ info/ rich
In this case you need to write a title and description of the crash. Explain as best you can. @info/ rich
@ info/ rich
You can also specify your distribution method (GNU/ Linux distribution or packaging system) or if you compiled the KDE Platform from sources. @info/ rich
@ info/ rich
You should write in English. @title
@ title
Sending the Crash Report@info/ rich
ભંગાણ અહેવાલ મોકલો@ info/ rich
The last 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. @info/ rich
@ info/ rich
If the process fails, you can click Retry to try sending the bug report again. If the report cannot be sent because the bug tracking database has a problem, you can save it to a file to manually report later. @info/ rich
@ info/ rich
Thank you for being part of KDE! @info/ rich
KDEનો ભાગ બનવા માટે આભાર! @ info/ rich
If you are interested into helping us to organise bug reports allowing the developers to focus on fixing the real issues, join the BugSquad (#kde-bugs on FreeNode IRC) @action: button
@ action: button
& Reload@info: tooltip
@ info: tooltip
Use this button to reload the crash information (backtrace). This is useful when you have installed the proper debug symbol packages and you want to obtain a better backtrace. @action: button
@ action: button
& Install Debug Symbols@info: tooltip
@ info: tooltip
Use this button to install the missing debug symbols packages. @info: tooltip
@ info: tooltip
Use this button to copy the crash information (backtrace) to the clipboard. @info: tooltip
@ info: tooltip
Use this button to save the crash information (backtrace) to a file. This is useful if you want to take a look at it or to report the bug later. @info: status
@ info: status
Loading... @info: status
લાવે છે... @ info: status
Loading crash information... (this may take some time)@info
@ info
Another debugger is currently debugging the same application. The crash information could not be fetched. @info: status
@ info: status
The crash information could not be fetched. @info/ rich
@ info/ rich
Another debugging process is attached to the crashed application. Therefore, the DrKonqi debugger cannot fetch the backtrace. Please close the other debugger and click Reload Crash Information. @info
@ info
This crash information is useful@info
આ ભંગાણ માહિતી ઉપયોગી છે@ info
This crash information may be useful@info
આ ભંગાણ માહિતી કદાચ ઉપયોગી થઇ શકે છે@ info
This crash information is probably not useful@info
આ ભંગાણ માહિતી કદાચ ઉપયોગી નથી@ info
This crash information is not useful@info
આ ભંગાણ માહિતી ઉપયોગી નથી@ info
The rating of this crash information is invalid. This is a bug in drkonqi itself. @info/ rich
@ info/ rich
You can click the Install Debug Symbols button in order to automatically install the missing debugging information packages. If this method does not work: please read How to create useful crash reports to learn how to get a useful backtrace; install the needed packages and click the Reload Crash Information button. @info: status
@ info: status
The debugger has quit unexpectedly. @info: status
@ info: status
The crash information could not be generated. @info/ rich
ભંગાણ માહિતી બનાવી શકાતી નથી. @ info/ rich
You could try to regenerate the backtrace by clicking the Reload Crash Information button. @info: status
@ info: status
The debugger application is missing or could not be launched. @info/ rich
@ info/ rich
You need to install the debugger package (%1) and click the Reload Crash Information button. @title: window
@ title: window
Error during the installation of debug symbols@info
@ info
Unknown response from the server@info
સર્વર તરફથી અજાણ્યો જવાબ@ info
Invalid bug report: corrupted data@info
@ info
Invalid bug list: corrupted data@info
@ info
Unknown error@info
અજાણી ક્ષતિ@ info
Error while attaching the data to the bug report: %1@info
ક્ષતિ અહેવાલ લાવવામાં ક્ષતિ@ info
Error while adding yourself to the CC list: %1@title: window
ક્ષતિ અહેવાલ લાવવામાં ક્ષતિ@ title: window
Missing debug symbols@info: progress
@ info: progress
Requesting installation of missing debug symbols packages... @info
@ info
Could not find debug symbol packages for this application. @info
@ info
An error was encountered during the installation of the debug symbol packages. @info
@ info
Report saved to %1. @info
અહેવાલ% 1 માં સંગ્રહ થયો.
Could not create a file in which to save the report. @title: window
બેકસ્ટ્રેસ સંગ્રહ કરવા માટે ફાઇલ બનાવી શકાતી નથી@ title: window
& General@title: tab
સામાન્ય (G) @ title: tab
& Developer Information@info
ડેવલોપર માહિતી (D) @ info
We are sorry, %1 closed unexpectedly. @info
@ info
The reporting assistant is disabled because the crash handler dialogue was started in safe mode. You can manually report this bug to %1 (including the backtrace from the Developer Information tab). @info
@ info
You can help us improve KDE Software by reporting this error. Learn more about bug reporting. It is safe to close this dialogue if you do not want to report this bug. @info
@ info
You cannot report this error, because the application does not provide a bug reporting address. @label
@ label
Details: @info
વિગતો: @ info
Executable: %1 PID: %2 Signal: %3 (%4) @action: button
@ action: button
Report Bug@info: tooltip
ક્ષતિ અહેવાલ આપો@ info: tooltip
Starts the bug report assistant. @action: button this is the debug menu button label which contains the debugging applications
ક્ષતિ અહેવાલ વિઝાર્ડ લાવો (L) @ action: button this is the debug menu button label which contains the debugging applications
Debug@info: tooltip
ડીબગ@ info: tooltip
Starts a program to debug the crashed application. @action: button
@ action: button
Restart Application@info: tooltip
કાર્યક્રમ ફરી શરૂ કરો@ info: tooltip
Use this button to restart the crashed application. @info: tooltip
@ info: tooltip
Close this dialogue (you will lose the crash information). @action: inmenu 1 is the debugger name
@ action: inmenu 1 is the debugger name
(C) 2000-2009, The DrKonqi Authors@info: credit
(c) ૨૦૦૦- ૨૦૦૯ ડૉકોન્કી લેખકો@ info: credit
Dario Andres Rodriguez@info: credit
ડેરિઓ એન્ડ્રિઆસ રોડ્રીગુએઝ@ info: credit
George Kiagiadakis@info: credit
જ્યોર્જ કિગિડાકીસ@ info: credit
A. L. Spehr@info: shell
એ. એલ. સ્પેહ્ર@ info: shell
Name of the program@info: shell
કાર્યક્રમનું નામ@ info: shell
The program has already been restartedNAME OF TRANSLATORS
કાર્યક્રમ kdeinit વડે શરૂ કરવામાં આવ્યો હતોNAME OF TRANSLATORS
Aston ClulowEMAIL OF TRANSLATORS
કાર્તિક મિસ્ત્રીEMAIL OF TRANSLATORS
clulow@upnaway. com
kartik. mistry@ gmail. com@ title
Please select which additional information you can provide: @option: check kind of information the user can provide about the crash
@ option: check kind of information the user can provide about the crash
Unusual desktop behaviour I noticed@option: check kind of information the user can provide about the crash
@ option: check kind of information the user can provide about the crash
Custom settings of the application that may be related@label: textbox
@ label: textbox
Backtrace of the crash I am sending: @info/ rich
@ info/ rich
See if your bug has already been reported. Double click a report in the list and compare it to yours. You can suggest that your crash is a duplicate of that report or directly attach your information to it. @title: column
@ title: column
Bug ID@title: column
ક્ષતિ ક્રમાંક@ title: column
Description@label title of a listbox where the possible duplicate bug numbers are put in
વર્ણન@ label title of a listbox where the possible duplicate bug numbers are put in
Possible duplicates: @info/ rich
@ info/ rich
Complete the bug report fields: Use English. @label: textbox
@ label: textbox
Title of the bug report: (examples )@label: textbox
@ title
Information about the crash: @title: group
ક્ષતિ અહેવાલ વિશે માહિતી@ title: group
Distribution method: @option: check
@ option: check
KDE Platform is compiled from sources@info/ rich
@ info/ rich
The crash and system information will be automatically added to the bug report. @label: textbox bugzilla account username
@ label: textbox bugzilla account username
Username: @label: textbox bugzilla account password
વપરાશકર્તાનામ: @ label: textbox bugzilla account password
Password: @option: check
પાસવર્ડ: @ option: check
Save login information using the KDE Wallet system@label
@ label
This is a preview of the report 's contents which will be sent. If you want to modify it go the previous pages. @option: check
@ option: check
Open the bug report page when clicking the Finish button@option: check
@ option: check
Restart the application when clicking the Finish button@info
@ info
Since communication between you and the developers is required for effective debugging, to continue reporting this bug it is required for you to agree that developers may contact you. Feel free to close this dialogue if you do not accept this. @title: window
@ title: window
Crash Reporting Assistant@title
ક્ષતિ અહેવાલીકરણ નિષ્ક્રિય કરો (D) @ title
Welcome to the Reporting Assistant@title
ક્ષતિ અહેવાલીકરણ નિષ્ક્રિય કરો (D) @ title
Crash Information (Backtrace)@title
બેકટ્રેસ શક્ય નથી@ title
Crash Analysis Results@title
પરિણામ આ રીતે સંગ્રહો@ title
KDE Bug Tracking System Login@title
@ title
Bug Report Possible Duplicates List@title
@ title
Details of the Bug Report@title
ક્ષતિ અહેવાલની વિગતો@ title
Preview Report@title
@ title
Send Crash Report@action: button
ભંગાણ અહેવાલ મોકલો@ action: button
Close the assistant@action: button
@ action: button
Cancel@action: button
રદ કરો@ action: button
Save information and close@info
@ info
Do you really want to close the bug reporting assistant? The crash information is still valid, so you can save the report before closing if you want. @title: window
@ title: window
Close the Assistant@info
ક્ષતિ અહેવાલીકરણ નિષ્ક્રિય કરો (D) @ info
Do you really want to close the bug reporting assistant? @info
ક્ષતિ અહેવાલ વિઝાર્ડ લાવો (L) @ info
This crash information is not useful enough, do you want to try to improve it? You will need to install some debugging packages. @title: window
@ title: window
Crash Information is not useful enough@option: check kind of information the user can provide about the crash, %1 is the application name
@ option: check kind of information the user can provide about the crash,% 1 is the application name
What I was doing when the application "%1" crashed@info examples about information the user can provide
@ info examples about information the user can provide
Widgets you have in your desktop and panels (both official and unofficial), desktop settings (wallpaper plugin, themes), activities, and dashboard configuration. @info examples about information the user can provide
@ info examples about information the user can provide
State of Desktop Effects (Compositing), kind of effects enabled, window decoration, and specific window rules and configuration. @info examples about information the user can provide
@ info examples about information the user can provide
sites you were visiting, number of opened tabs, plugins you have installed, and any other non-default setting. @info examples about information the user can provide
@ info examples about information the user can provide
File view mode, grouping and sorting settings, preview settings, and directory you were browsing. @info examples about information the user can provide
@ info examples about information the user can provide
Instant Messaging protocols you use, and plugins you have installed (official and unofficial). @info examples about information the user can provide
@ info examples about information the user can provide
Mail protocols and account-types you use. @info examples about information the user can provide
@ info examples about information the user can provide
Type of the document you were editing. @info examples about information the user can provide
@ info examples about information the user can provide
Type of media (extension and format) you were watching and/ or listening to. @label examples about information the user can provide
@ label examples about information the user can provide
Examples: %1@action: button
@ action: button
Show Contents of the Report@info: tooltip
અહેવાલની વિગતો બતાવો (w) @ info: tooltip
Use this button to show the generated report information about this crash. @info/ plain
@ info/ plain
Report to %1@info/ plain bug resolution
% 1 ને અહેવાલ આપો@ option: check
The automatically generated crash information is useful. @info
@ info
The automatically generated crash information lacks some details but may be still be useful. @info
@ info
The automatically generated crash information lacks important details and it is probably not helpful. @info
@ info: status
The crash information was not generated because it was not needed. @info
ભંગાણ માહિતી બનાવી શકાતી નથી. @ info
The automatically generated crash information does not contain enough information to be helpful. @info
@ info
You can improve it by installing debugging packages and reloading the crash on the Crash Information page. You can get help with the Bug Reporting Guide by clicking on the Help button. @info
@ info
The information you can provide could be considered helpful. @info
@ info
The information you can provide is not considered helpful enough in this case. @info
@ info
This report is considered helpful. @info
@ info
This application 's bugs are reported to the KDE bug tracking system: click Next to start the reporting process. You can manually report at %1 @info
@ info
This application is not supported in the KDE bug tracking system. Click Finish to report this bug to the application maintainer. Also, you can manually report at %1. @info
@ info