Hello,
I see that my colleagues previously started a support thread regarding Dutch translations.
I regularly come across translations that are not entirely correct, for example punctuation or formatting issues that have not been properly applied, as shown in the screenshot below.
Would it be okay to use this thread to share these improvement points? Or do you want me to create another topic?
In the example above I am logged in to the Express environment via google chrome.
Hi @Rema_Tim, I’ve started a new topic with your new suggestion. The assigned Product team will follow up with you under this topic.
Great thank you, there are a few additional incorrect translations, I will post them here.
If users try to login to Onix Express, following screen is displayed.
Please change: Vergeten je wachtwoord? → Wachtwoord vergeten?
This translated message is quite unclear.
Better translation
Inloghulp van Rema Holland B.V.
Uw e-mailadres is niet gekoppeld aan een account.
Wilt u toegang tot de online portal? Neem dan rechtstreeks contact op met uw leverancier om een account aan te vragen.
Bedankt.
In Dutch we use je and jij for informal conversations. U and uw is the more formal/business approach.
In the above message a lot of Je/jij and U is used without consistency.
Controleer uw e-mail
Controleer het e-mailadres nieuwaccount@gmail.com voor instructies om een account aan te vragen.
Heeft u binnen 15 minuten geen e-mail ontvangen? Controleer dan of u het juiste e-mailadres heeft ingevuld en kijk ook in uw spamfolder.
Terug naar aanmelden
If I go to “Beheer eigenschappen” in the colomn “gegevens type” I see “Kort tekst”. Correct translation is: “Korte tekst”
Next to that the colum Ïnvoertype shows “Gratis text”. In Dutch this means: Text for free. Better translation = Vrije tekst. “Vrije tekst” means that the user can enter any value manually, without being limited to predefined options or a selection list, I assume this is meant for this column.
We often get calls from Dutch users expressing they do understand why we have Norwegian (I guess) prefixes to our documents. See printscreen below:
First item is named: Kontroll and Kontrolldetaljer. If I open the actual document, it is called: “Inspectie Details” and in this case specificly for “Keuringsrapport Takels Lieren en Loopkatten”.
Second item is named: Kontroll. If I open the actual document, it is called: CERTIFICAAT.
Third document has no prefix, wwhich is fine, since document type says: “Origineel certificaat”.
For me all these pre-fixes can also be left away. When I check the express environment, documenttype is clear enough and shows per document what the type is.
Hi @Rema_Tim
We will update the language in this release, which is on Friday - Thank you for letting us know!
As for the changing of the form name, that is a much bigger task, and will require development and testing. We will therefore schedule it for the autumn release.
I will keep you updated.
Great, thanks for the quick follow up. If I encounter further improvements, do you want me to use this topic or should I start a new one?
I will also let my colleagues know, thanks again for your help.
FYI: Sorry, I posted the reply with my “customer/demo” test account.
Hi @Rema_Tim
Keep using this thread.
We will try and gather language updates for releases unless you mean it is urgent, going forward.
Hi @Rema_Tim
Thank you again for your suggestion.
After the latest 2026 Summer release, the suggested language changes have been implemented and are now ready for use.
However, changing the form/file name requires additional development and testing, so this part will be handled separately. Because of that, we will move this topic back to In discussion while we continue following up on the remaining change.
Please give the updated language a try, and feel free to keep using this thread if you have any further feedback.
Once again, thank you for sharing your idea with us!
