Translations by Marsel Pretorius
Marsel Pretorius has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
~ |
This occured during a previous hibernate and prevented it from resuming properly.
|
|
2010-06-29 |
Hierdie het voorgekom gedurende 'n vorige hibernasie sessie en het verhoed dat dit behoorlik kon voortgaan.
|
|
~ |
This occured during a previous suspend and prevented it from resuming properly.
|
|
2010-06-29 |
Hierdie het voorgekom tydens 'n vorige opskorting en het verhoed dat dit behoorlik kon voortgaan.
|
|
3. |
Usage: %s <report> <target directory>
|
|
2010-06-29 |
Gebruik: %s <verslag> <teikengids>
|
|
4. |
Destination directory exists and is not empty.
|
|
2010-06-29 |
Bestemmingsgids bestaan en is nie leeg nie.
|
|
14. |
Report a problem...
|
|
2010-06-29 |
Raporteer 'n probleem...
|
|
15. |
Report a malfunction to the developers
|
|
2010-06-29 |
Rapporteer foutiewe werking an die ontwikkelaars
|
|
16. |
Do not put the new traces into the report, but write them to stdout.
|
|
2010-06-29 |
Moenie die nuwe spore in die verslag inskryf nie, skryf dit na stdout.
|
|
17. |
Start an interactive gdb session with the report's core dump (-o ignored; does not rewrite report)
|
|
2010-06-29 |
Skop 'n interaktiewe gdb sessie af met die verslag se kernstorting (-o geïgnoreerd; herskryf nie verslag nie)
|
|
18. |
Write modified report to given file instead of changing the original report
|
|
2010-06-29 |
Skryf die gewysigde verslag na 'n gegewe lêer in plaas daarvan om die oorspronklike te verander
|
|
19. |
Remove the core dump from the report after stack trace regeneration
|
|
2010-06-29 |
Verwyder die kernstorting vanuit die verslag na die hergenerasie van die stapelspoor
|
|
20. |
Override report's CoreFile
|
|
2010-06-29 |
Oorskryf die verslag se kernlêer
|
|
21. |
Override report's ExecutablePath
|
|
2010-06-29 |
Oorskryf die verslag se ExecutablePath
|
|
22. |
Override report's ProcMaps
|
|
2010-06-29 |
Oorskryf die verslag se ProcMaps
|
|
23. |
Rebuild report's Package information
|
|
2010-06-29 |
Herbou die verslag se pakketinformasie
|
|
30. |
Path to a file with the crash database authentication information. This is used when specifying a crash ID to upload the retraced stack traces (only if neither -g, -o, nor -s are specified)
|
|
2010-06-29 |
Pad na 'n lêer met die ineenstortingsdatabasis se boekstawingsinformasie. Dit word gebruik as 'n ineestortings-ID gespesifiseer word vir die oplaai van die teruglopende stapelspore (slegs as nie een van -g, -o of -s gespesifiseer is nie)
|
|
31. |
Display retraced stack traces and ask for confirmation before sending them to the crash database.
|
|
2010-06-29 |
Vertoon die teruglopende stapelspore en vra vir bevestiging alvorens dit aangestuur word na ineenstortingsdatabasis.
|
|
32. |
Path to the duplicate sqlite database (default: no duplicate checking)
|
|
2010-06-29 |
Pad na die gedupliseerde sqlite databasis(verstek: geen duplikaatkontrole nie)
|
|
34. |
OK to send these as attachments? [y/n]
|
|
2010-06-29 |
Kan hierdie saamgestuur word as bylae? [y/n]
|
|
35. |
Send problem report to the developers?
|
|
2010-06-29 |
Stuur die probleemverslag aan die ontwikkelaars?
|
|
51. |
(binary data)
|
|
2010-06-29 |
(binêre data)
|
|
53. |
Collecting problem information
|
|
2010-06-29 |
Versamel probleeminformasie
|
|
56. |
Uploading problem information
|
|
2010-06-29 |
Laai probleeminformasie op
|
|
57. |
The collected information is being sent to the bug tracking system. This might take a few minutes.
|
|
2010-06-29 |
Die versamelde inligting word tans gestuur aan die foutsporingstelsel. Dit mag 'n paar minute duur.
|
|
61. |
You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:
%s
|
|
2010-06-28 |
Jy het enkele oortollige geïnstalleerde pakketweergawes. Opgradeer asseblief die volgende pakkette en gaan daarna na of die probleem nogsteeds voorkom:
%s
|
|
62. |
unknown program
|
|
2010-06-28 |
onbekende program
|
|
63. |
Sorry, the program "%s" closed unexpectedly
|
|
2010-06-28 |
Jammer, maar die program "%s" het onverwags afgesluit
|
|
64. |
Problem in %s
|
|
2010-06-28 |
Probleem in %s
|
|
65. |
Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers.
|
|
2010-06-28 |
Jou rekenaar beskik nie oor genoegsame ongebruikte geheue om die probleem outomaties te analiseer en te raporteer aan die ontwikkelaars nie.
|
|
66. |
Invalid problem report
|
|
2010-06-28 |
Ongeldige foutverslag
|
|
67. |
You are not allowed to access this problem report.
|
|
2010-06-28 |
Jy is toegang geweier tot hierdie probleemverslag.
|
|
68. |
Error
|
|
2010-06-28 |
Fout
|
|
69. |
There is not enough disk space available to process this report.
|
|
2010-06-28 |
Daar is nie genoeg beskikbare skyfspasie vir die verwerking van die verslag nie.
|
|
70. |
No package specified
|
|
2010-06-28 |
Geen pakket gespesifiseer nie
|
|
71. |
You need to specify a package or a PID. See --help for more information.
|
|
2010-06-28 |
Jy moet ', pakket of PID spesifiseer. Beskou --help vir meer inligting.
|
|
72. |
Permission denied
|
|
2010-06-28 |
Toestemming geweier
|
|
73. |
The specified process does not belong to you. Please run this program as the process owner or as root.
|
|
2010-06-28 |
Die spesifieke proses behoort nie aan jou nie. Laat die program loop as proseseienaar of as root.
|
|
74. |
Invalid PID
|
|
2010-06-28 |
Ongeldige PID
|
|
75. |
The specified process ID does not belong to a program.
|
|
2010-06-28 |
Die gespesifiseerde proses-ID behoort nie aan 'n program nie.
|
|
76. |
Symptom script %s did not determine an affected package
|
|
2010-06-28 |
Simptometeks %s kon geen geaffekteerde pakket bepaal nie
|
|
77. |
Package %s does not exist
|
|
2010-06-28 |
Pakket %s bestaan nie
|
|
78. |
Cannot create report
|
|
2010-06-28 |
Kan nie verslag skep nie
|
|
79. |
Updating problem report
|
|
2010-06-28 |
Opdateer probleemverslag
|
|
80. |
You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed.
Please create a new report using "apport-bug".
|
|
2010-06-28 |
Jy is nie die raporteerder of intekenaar van hierdie probleemverslag nie, of die verslag is 'n duplikaat of reeds afgesluit.
Skep asseblief 'n nuwe verslag met behulp van "apport-bug".
|
|
81. |
You are not the reporter of this problem report. It is much easier to mark a bug as a duplicate of another than to move your comments and attachments to a new bug.
Subsequently, we recommend that you file a new bug report using "apport-bug" and make a comment in this bug about the one you file.
Do you really want to proceed?
|
|
2010-06-28 |
Jy is nie die rapporteerder van hierdie probleemverslag nie. Dit is heelwat makliker om 'n fout as duplikaat van 'n ander te merk as om jou kommentaar en bylae te skuif na 'n nuwe fout.
|
|
82. |
No additional information collected.
|
|
2010-06-28 |
Geen ekstra informasie versamel nie.
|
|
83. |
What kind of problem do you want to report?
|
|
2010-06-28 |
Watter tipe probleem probeer jy rapporteer?
|
|
84. |
Unknown symptom
|
|
2010-06-28 |
Onbekende simptoom
|
|
85. |
The symptom "%s" is not known.
|
|
2010-06-28 |
Die simptoom "%s" is onbekend
|
|
88. |
%prog <report number>
|
|
2010-06-28 |
%prog <verslagnommer>
|
|
91. |
%prog [options] [symptom|pid|package|program path|.apport/.crash file]
|
|
2010-06-28 |
%prog [opsies] [simptoom|pid|pakket|programroete|.apport/.crash lêer]
|