Translations by Nathan Follens
Nathan Follens has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| ~ |
the second component of route ('%s') is neither a next hop address nor a metric
|
|
| 2022-05-19 |
de tweede component van route (‘%s’) is noch een next hop-adres, noch een metriek
|
|
| 6. |
Error: secret agent initialization failed
|
|
| 2022-05-19 |
Fout: initialisatie van secret agent is mislukt
|
|
| 7. |
Error: polkit agent initialization failed: %s
|
|
| 2022-05-19 |
Fout: initialisatie van polkit agent is mislukt: %s
|
|
| 8. |
nmcli successfully registered as a polkit agent.
|
|
| 2022-05-19 |
nmcli is met succes geregistreerd als een polkit agent.
|
|
| 23. |
default route cannot be added (NetworkManager handles it by itself)
|
|
| 2022-05-19 |
standaardroute kan niet worden toegevoegd (NetworkManager handelt het zelf af)
|
|
| 31. |
connecting (checking IP connectivity)
|
|
| 2022-05-19 |
verbinden (IP-verbinding controleren)
|
|
| 39. |
yes (guessed)
|
|
| 2022-05-19 |
ja (verondersteld)
|
|
| 40. |
no (guessed)
|
|
| 2022-05-19 |
nee (verondersteld)
|
|
| 44. |
Device is now unmanaged
|
|
| 2022-05-19 |
Apparaat wordt nu niet beheerd
|
|
| 45. |
The device could not be readied for configuration
|
|
| 2022-05-19 |
Klaarmaken van apparaat voor configuratie is mislukt
|
|
| 46. |
IP configuration could not be reserved (no available address, timeout, etc.)
|
|
| 2022-05-19 |
Reserveren van de IP-configuratie is mislukt (geen beschikbare adressen, time-out, enz.)
|
|
| 48. |
Secrets were required, but not provided
|
|
| 2022-05-19 |
Geheimen werden vereist, maar niet verstrekt
|
|
| 49. |
802.1X supplicant disconnected
|
|
| 2022-05-19 |
Niet verbonden met 802.1X supplicant
|
|
| 50. |
802.1X supplicant configuration failed
|
|
| 2022-05-19 |
Configuratie 802.1X supplicant mislukt
|
|
| 51. |
802.1X supplicant failed
|
|
| 2022-05-19 |
802.1X supplicant mislukt
|
|
| 52. |
802.1X supplicant took too long to authenticate
|
|
| 2022-05-19 |
802.1X supplicant authenticatie duurde te lang
|
|
| 53. |
PPP service failed to start
|
|
| 2022-05-19 |
Starten van PPP-dienst mislukt
|
|
| 54. |
PPP service disconnected
|
|
| 2022-05-19 |
Niet verbonden met PPP-dienst
|
|
| 55. |
PPP failed
|
|
| 2022-05-19 |
PPP mislukt
|
|
| 56. |
DHCP client failed to start
|
|
| 2022-05-19 |
Starten van DHCP-client mislukt
|
|
| 57. |
DHCP client error
|
|
| 2022-05-19 |
Fout DHCP-client
|
|
| 58. |
DHCP client failed
|
|
| 2022-05-19 |
DHCP-client mislukt
|
|
| 59. |
Shared connection service failed to start
|
|
| 2022-05-19 |
Starten van gedeelde verbinding-dienst mislukt
|
|
| 60. |
Shared connection service failed
|
|
| 2022-05-19 |
Gedeelde verbinding-dienst mislukt
|
|
| 61. |
AutoIP service failed to start
|
|
| 2022-05-19 |
Starten van AutoIP-dienst mislukt
|
|
| 62. |
AutoIP service error
|
|
| 2022-05-19 |
Fout AutoIP-dienst
|
|
| 63. |
AutoIP service failed
|
|
| 2022-05-19 |
AutoIP-dienst mislukt
|
|
| 64. |
The line is busy
|
|
| 2022-05-19 |
Lijn bezet
|
|
| 65. |
No dial tone
|
|
| 2022-05-19 |
Geen kiestoon
|
|
| 66. |
No carrier could be established
|
|
| 2022-05-19 |
Er kon geen carrier worden vastgesteld
|
|
| 67. |
The dialing request timed out
|
|
| 2022-05-19 |
Tijdslimiet bel-aanvraag overschreden
|
|
| 68. |
The dialing attempt failed
|
|
| 2022-05-19 |
Belpoging mislukt
|
|
| 69. |
Modem initialization failed
|
|
| 2022-05-19 |
Initialisatie van modem mislukt
|
|
| 70. |
Failed to select the specified APN
|
|
| 2022-05-19 |
Selecteren van opgegeven APN mislukt
|
|
| 71. |
Not searching for networks
|
|
| 2022-05-19 |
Er wordt niet naar netwerken gezocht
|
|
| 72. |
Network registration denied
|
|
| 2022-05-19 |
Netwerkregistratie geweigerd
|
|
| 73. |
Network registration timed out
|
|
| 2022-05-19 |
Tijdslimiet netwerkregistratie verlopen
|
|
| 74. |
Failed to register with the requested network
|
|
| 2022-05-19 |
Registreren bij het gevraagde netwerk mislukt
|
|
| 75. |
PIN check failed
|
|
| 2022-05-19 |
PIN-controle mislukt
|
|
| 76. |
Necessary firmware for the device may be missing
|
|
| 2022-05-19 |
Mogelijk ontbreekt de firmware voor het apparaat
|
|
| 78. |
NetworkManager went to sleep
|
|
| 2022-05-19 |
NetworkManager is in slaapstand gegaan
|
|
| 79. |
The device's active connection disappeared
|
|
| 2022-05-19 |
De actieve verbinding van het apparaat is verdwenen
|
|
| 80. |
Device disconnected by user or client
|
|
| 2022-05-19 |
Verbinding van apparaat is verbroken door de gebruiker of client
|
|
| 81. |
Carrier/link changed
|
|
| 2022-05-19 |
Carrier/link gewijzigd
|
|
| 82. |
The device's existing connection was assumed
|
|
| 2022-05-19 |
Er werd uitgegaan van de bestaande verbinding
|
|
| 83. |
The supplicant is now available
|
|
| 2022-05-19 |
De aanvrager is nu beschikbaar
|
|
| 84. |
The modem could not be found
|
|
| 2022-05-19 |
De modem kon niet gevonden worden
|
|
| 85. |
The Bluetooth connection failed or timed out
|
|
| 2022-05-19 |
Bluetooth-verbinding mislukt of verlopen
|
|
| 86. |
GSM Modem's SIM card not inserted
|
|
| 2022-05-19 |
SIM-kaart van GSM-modem niet ingebracht
|
|
| 87. |
GSM Modem's SIM PIN required
|
|
| 2022-05-19 |
SIM-pin van GSM-modem vereist
|
|
