New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| Caching strategy for WP Rest | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| Your Site Icon should be at least 192px. | Je site pictogram moet minimaal 192px zijn. | Details | |
Original current |
|||
| Please select a Site Icon (Favicon). | Selecteer je site pictogram (Favicon). | Details | |
Original current |
|||
| Use the AMP Version of the Start Page if available. | Gebruik de AMP versie van de start pagina, als deze beschikbaar is. | Details | |
Original current
Use the AMP Version of the Start Page if available.
ReferencesYou have to log in to edit this translation. |
|||
| AMP Start Page | AMP start pagina | Details | |
Original current |
|||
| OneSignal Settings | OneSignal instellingen | Details | |
Original current |
|||
| Progressive WordPress is fully compatible with OneSignal! | Progressive WordPress is volledig met OneSignal te gebruiken! | Details | |
Original current
Progressive WordPress is fully compatible with OneSignal!
ReferencesYou have to log in to edit this translation. |
|||
| It looks like you are using %s to send push notifications. | Het lijkt erop dat je %s gebruikt om push berichten te verzenden. | Details | |
Original current
It looks like you are using %s to send push notifications.
ReferencesYou have to log in to edit this translation. |
|||
| This strategy won't chache anything. The network will be used and the response will be passed directly to the browser (That's how the browser would handle the request without the Service Worker). | You have to log in to add a translation. | Details | |
Original untranslated
This strategy won't chache anything. The network will be used and the response will be passed directly to the browser (That's how the browser would handle the request without the Service Worker).
ReferencesYou have to log in to edit this translation. |
|||
| Network Only | You have to log in to add a translation. | Details | |
Original untranslated
Network Only
You have to log in to edit this translation. |
|||
| Add to Homescreen | Toevoegen aan startscherm | Details | |
Original current |
|||
| Caching strategies | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| This strategy will check the cache for a response first and use that if one is available. If the request isn’t in the cache, the network will be used and any valid response will be added to the cache before being passed to the browser. | You have to log in to add a translation. | Details | |
Original untranslated
This strategy will check the cache for a response first and use that if one is available. If the request isn’t in the cache, the network will be used and any valid response will be added to the cache before being passed to the browser.
ReferencesYou have to log in to edit this translation. |
|||
| This will try and get a request from the network first. If it receives a response, it’ll pass that to the browser and also save it to a cache. If the network request fails, the last cached response will be used. | You have to log in to add a translation. | Details | |
Original untranslated
This will try and get a request from the network first. If it receives a response, it’ll pass that to the browser and also save it to a cache. If the network request fails, the last cached response will be used.
ReferencesYou have to log in to edit this translation. |
|||
| This strategy will use a cached response for a request if it is available and update the cache in the background with a response form the network. (If it’s not cached it will wait for the network response and use that). This is a fairly safe strategy as it means users are regularly updating their cache. The downside of this strategy is that it’s always requesting an asset from the network, using up the user’s bandwidth. | You have to log in to add a translation. | Details | |
Original untranslated
This strategy will use a cached response for a request if it is available and update the cache in the background with a response form the network. (If it’s not cached it will wait for the network response and use that). This is a fairly safe strategy as it means users are regularly updating their cache. The downside of this strategy is that it’s always requesting an asset from the network, using up the user’s bandwidth.
ReferencesYou have to log in to edit this translation. |
|||
Export as