Incorrect Dutch translations: “Save” is translated as “Redden”
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- localization
Research direction
Start by locating the Dutch translation dictionary used by @keystatic/core and compare the entries listed in the issue with the expected Dutch labels. Update the incorrect translations for Save, Clear, Branch name, and Pull requests, then verify the labels while using locale "nl-NL" in the described editing flow.
Written by the indexing model from the issue text.
Description
Description
With locale: "nl-NL", the Save button displays “Redden”.
In Dutch, “Redden” means “rescue”. The correct label for saving content is “Opslaan”. This is confusing for nontechnical content editors.
Environment
- @keystatic/core: 0.6.8
- @keystatic/astro: 5.2.0
- Astro integration
Steps to reproduce
- Set
locale: "nl-NL"in the Keystatic configuration. - Open an existing collection entry.
- Edit a field.
- Observe the Save button label.
Expected result
The button displays “Opslaan”.
Actual result
The button displays “Redden”. This translation is present in the installed package’s Dutch translation dictionary.
Other examples
The Dutch dictionary contains several other incorrect translations:
| English | Current Dutch | Suggested Dutch |
|---|---|---|
| Save | Redden | Opslaan |
| Clear | Helder | Wissen |
| Branch name | Filiaal naam | Branchnaam |
| Pull requests | Trek verzoeken | Pull requests |
Workaround
Setting locale: "en-US" avoids these translations, but makes the system interface English.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 164
- Avg merge
- 5h 46m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Thinkmill/keystatic
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Typo/Grammar on Website HomepagePossibly taken @Punith1117 claimed this 126 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
All issues in Thinkmill/keystatic
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
platformatic/mcp#208 ·
Maintainers usually reply within 1 day
-
🐛 bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
margelo/react-native-vision-camera#4211 ·
Maintainers usually reply within 4 days