Translations by berend

berend has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.

150 of 275 results
~
Generate
2008-10-04
Generearje
~
(C) 2000-2003, Hans Petter Bieker
2008-10-04
(C) 2000-2003, Hans Petter Bieker
~
Could not generate a backtrace as the debugger '%1' was not found.
2008-10-04
Der koe gjin trochslach makke wurde omdat de debugger '%1' net te finnen wie.
~
Backtrace Not Possible
2008-10-04
Trochslach is net mooglik
~
C&opy
2008-10-04
&Kopiearje
~
Cannot create a file to save the backtrace in
2008-10-04
Koe gjin triem oanmeitsje om de trochslach yn te bewarjen
~
Select Filename
2008-10-04
Triemnamme selektearje
~
Application: %progname (%execname), signal %signame
2008-10-04
Applikaasje: %progname (%execname), signal %signame
~
It was not possible to generate a backtrace.
2008-10-04
Der koe gjin trochslach makke wurde.
~
&Overwrite
2008-10-04
&Oerskriuwe
~
Cannot open file <filename>%1</filename> for writing.
2008-10-04
De triem <filename>%1</filename>kin net iepene wurde om nei te skriuwen.
~
Backtrace saved to <filename>%1</filename>.
2008-10-04
Trochslach bewarre as <filename>%1</filename>.
~
This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
2008-10-04
Dizze trochslach is net brûkber. Jo pakketten binne op san wize makke dat 'er gjin backtrace mooglik is, of de trochslach is skansearre yn 'e rin fan it programma.
~
Loading backtrace...
2008-10-04
Laden fan 'e trochslach...
~
The following options are enabled:
2008-10-04
De folgjende opsjes binne ynskeakele:
~
As the usage of these options is not recommended - because they can, in rare cases, be responsible for KDE problems - a backtrace will not be generated. You need to turn these options off and reproduce the problem again in order to get a backtrace.
2008-10-04
Omdat it brûken fan dizze opsjes net oan te riden is, omdat se KDE stoare kinne, wurdt der gjin trochslach makke. Jo moatte de opsjes útsette en dan it probleem op 'e nei feroarsake om in trochslach te meitsjen.
~
Backtrace will not be created.
2008-10-04
Trochslach sil net makke wurde.
~
A file named <filename>%1</filename> already exists. Are you sure you want to overwrite it?
2008-10-04
In triem mei de namme <filename>%1</filename> bestiet al. Binne jo wis dat jo it oerskriuwe wolle?
~
Backtrace loaded.
2008-10-04
Trochslach laden.
~
Do Not Generate
2008-10-04
Net generearje
~
unknown
2008-10-04
ûnbekend
~
<application>%1</application>
2008-10-04
<application>%1</application>
~
<command>%1</command>
2008-10-04
<command>%1</command>
~
<filename>%1</filename>
2008-10-04
<filename>%1</filename>
~
KDE crash handler gives the user feedback if a program crashed
2008-10-04
It KDE-crash programma jout de brûker ynformaasje wannear in programma crasht is.
~
Unable to create a valid backtrace.
2008-10-04
Der koe gjin brûkbere backtrace oanmakke wurde.
~
Hans Petter Bieker
2008-10-04
Hans Petter Bieker
~
The signal number that was caught
2008-10-04
It sinjaal wat opfongen is.
~
Name of the program
2008-10-04
Namme fan it programma
~
Path to the executable
2008-10-04
Paad nei it útfierber triem
~
The version of the program
2008-10-04
Ferzje fan it programma
~
The bug address to use
2008-10-04
It te brûken brek-adres
~
Translated name of the program
2008-10-04
De oersetten namme van it programma
~
The PID of the program
2008-10-04
It PID fan it programma
~
Startup ID of the program
2008-10-04
Opstart-ID fan it programma
~
The program was started by kdeinit
2008-10-04
It programma wurde starte troch kdeinit
~
Disable arbitrary disk access
2008-10-04
Eigenwillige skiiftagong net tastean
~
Loading symbols...
2008-10-04
Laden fan symbolen...
~
System configuration startup check disabled.
2008-10-04
Systeemkonfiguraasje opstartkontrole útskeakele.
~
Overwrite File?
2008-10-04
Triem oerskriuwe?
~
You have to edit the description before the report can be sent.
2008-10-04
Bewurkje de beskriuwing foardat it rapport ferstjoerd wurdt.
~
&Bug Report
2008-10-04
&Brekrapport
~
&Debugger
2008-10-04
&Debugger
~
Show details
2008-10-04
Details sjen litte
~
Please attach the following information to your bug report:
2008-10-04
Graach de folgjende ynformaasje oan jo brekrapport taheakje
~
A Fatal Error Occurred
2008-10-04
Der barde in fatale flater.
~
<p style="margin-bottom: 6px;"><b>Application crashed</b></p><p>The program %appname crashed.</p>
2008-10-04
<p style="margin-bottom: 6px;"><b>Applikaasje ferûngelokke</b></p><p>It programma %appname is ferûngelokke.</p>
~
<p>Do you want to generate a backtrace? This will help the developers to figure out what went wrong.</p> <p>Unfortunately this will take some time on slow machines.</p><p><b>Note: A backtrace is not a substitute for a proper description of the bug and information on how to reproduce it. It is not possible to fix the bug without a proper description.</b></p>
2008-10-04
<p>Wolle jo in trochslach meitsje litte? It kin ûntwikkelders helpe mei de foutherlieding.</p> <p>It kin efkes duorje op trage masines.</p><p><b>Tink derom: In trochslach is gjin goede ferfanging fan in brekrapport. Sûnder brekrapport kinne ûntwikkelders gjin brek reparearje.</b></p>
~
Include Backtrace
2008-10-04
Trochslach taheakje
1.
About Bug Reporting
2009-10-07
Brekrapport, it hoe en het