How to provide an audio guide in Dutch
A Dutch guide is added to a guide that already exists rather than built from nothing. The English stops are translated, reviewed by someone who reads Dutch, and narrated, and the Dutch version then sits behind the same QR code the English version already uses. Nothing on the wall changes, and no second sign is printed.
In practice a venue works through it in this order, and the review step is the one most often skipped and most often regretted.
- Settle the regional variant and register before any translation starts
- Translate the English stops, keeping the source text locked while that happens
- Have a Dutch reader review it, ideally someone who knows the collection
- Narrate the reviewed text, checking proper nouns and place names first
- Publish it behind the QR codes already on the wall, with no reprinting
What Dutch needs from your layout
Dutch runs around 15 to 25% longer than English, with long compound nouns.
Dutch compounds nouns like German, producing long words that overflow narrow layouts. The ij digraph behaves as a unit in capitalisation, so IJsselmeer takes two capitals rather than one.
Netherlands and Belgian Dutch
Dutch as written in the Netherlands and in Flanders shares a standard, with modest vocabulary differences. One written version serves both audiences comfortably, which makes Dutch simpler than Portuguese or Spanish in this respect.
Visitor-facing Dutch uses the formal u, though Dutch conventions are somewhat less rigid than German ones.
Getting the Dutch narration right
Narration in Dutch raises questions that do not exist in English, and they are far cheaper to answer before a voice records anything than after.
- Netherlands and Flemish accents are clearly distinguishable, so choose deliberately.
- The Dutch g sound differs markedly between northern and southern speakers.
- Compound stress needs to be correct or long words become hard to follow by ear.
Where Dutch fits in your language plan
Across the New Zealand museums using Journey Pal, between 50% and 60% of guide use is in English. That is our own usage data, and it is worth knowing before committing to a long list of languages: local-language listening is usually the largest share, and translations extend a guide rather than being the reason for one.
That makes Dutch an addition to a working guide rather than a prerequisite for launching. Get the source script right, publish it, then add Dutch where your visitor numbers justify the translation and, just as importantly, where you have someone who can review it.
Frequently asked questions
Can we provide an audio guide in Dutch at our museum?
Yes. The Dutch version is translated from your English stops, reviewed, narrated, and published behind the QR codes you already have on the wall, so adding it does not mean new signage, a new app, or new hardware.
Do we need a separate Dutch version of our signage as well?
Usually not. The physical sign can stay short and carry a QR code, with the full Dutch text and audio behind it, which avoids reprinting signage every time the content changes.
How much longer will the Dutch version be?
Dutch runs around 15 to 25% longer than English, with long compound nouns.
Do visitors need an app to hear the Dutch guide?
No. The guide opens in the visitor's phone browser from a QR code, and phone-language detection can take a Dutch-speaking visitor straight to the right version when it exists.
Make this easier for your visitors
Journey Pal helps museums, heritage sites, zoos, and attractions deliver audio guides and translations through QR codes, with no app download required.