Update Dutch translation - #57
Conversation
Want to add the Dutch translation file
|
Hi Alex, thanks tons and sorry I've taken a while to get back. As you'll know, 2.3.0 shipped with your Dutch translation but I've been up to a lot since then and I didn't want to reply until I had everything ready for you. There's quite a lot to tell you. This PR first. Your fork has got out of step: its main is still on 23 July, so when you opened the translation page you were looking at the version from before yours was merged, with the French heading still on it. That heading was fixed on my side in July, so the three lines this changes were already done, and the table itself is unchanged from what you originally sent. That's what GitHub is flagging as a conflict, so I'm going to close this one. Now the part that matters. When your translation came in I merged it as you sent it and then corrected it in a commit of my own, but I never told you what I'd changed. I've now been back through the whole thing, and the two comments below this one show every row where your wording and the app differ, with the English next to them so you can judge for yourself. Of the 348 rows you sent:
And the 162 that differ, by why:
Thirteen rows have been changed back to your wording, and they're inside the 140 above. Klaar rather than Gereed, bekijken rather than zien, behouden, opsommen, Ontvangen, and others. Two things worth pulling out of that table. The 26-row group looks like the biggest change to your work and it's the least arguable: in every one of those you'd used both forms yourself in different places, the file had to settle on one, and the one it settled on is yours. And the only place I made a call about your Dutch rather than about consistency was the je/u question, where I went with you: you'd used je in 35 rows and u in 8, so the u ones were brought into line with your own overall preference. Really there are only twelve rows you might reasonably argue with, the two groups at the bottom, and I'd genuinely like to hear if you disagree with any of it. Where things stand now. The Dutch translation lives in There were 80 strings sitting in English for 3.0.0. I've had them drafted rather than leave them waiting, so you're not faced with a pile of typing. Dutch is now the first language fully translated for the release. If you want to go through them, or through anything else, they're yours and I'd be glad of it. If you do want to make changes, here's the shortest route. First sync your fork: go to your copy of the repo and press "Sync fork", because it's still on 23 July and that's what caused all the confusion above. Then open If you'd rather not use git for it at all, just reply here with the lines you'd change and I'll do it. I'm working towards 3.0.0 and there's a decent amount left before it goes out, so there's a window. If you get back to me before I release 3.0.0, your changes go in. If you'd rather take your time, that's fine too and I'll make a 3.0.1 release just with your changes and anything else that might have cropped up in the meantime. Thanks very much for all of this. |
|
Every row below is one where your wording and the unreleased 3.0.0 differ. Nothing unchanged is repeated, so this is 162 rows out of the 348 you sent, plus the 13 that were changed back to yours at the end. 61 rows have an English source string that has itself changed since you translated it. Those show both in the English column, marked Then: for the sentence you were working from and Now: for the one the app has today. Every other row shows a single English string, unchanged since your submission. The last group, "The English itself changed after you sent it", is in the comment below this one, because the whole thing won't fit in one reply (GitHub character limit). English or French left untranslated in the Dutch (5)The cell still carries a word or a sentence from the page it was copied from.
Typo (1)
Placeholder defect (6)The count placeholder is doubled, or the word after it is capitalised, so the rendered line reads wrongly.
English word order, verb at the front (5)Dutch puts the verb at the end, not the front. It also takes the -e Dutch adds after a number.
Different meaning from the English (19)
Not Dutch as written (7)
Typography (4)Curly quotes in a command people copy and paste, French spacing, or a stray space.
Compound written open or hyphenated (3)Dutch closes these up.
Wider than the command line help screen allows (2)scripts/check-cli-help-width.mjs fails any Cli.Help.* line over 74 terminal columns, because a longer line wraps in an 80-column console instead of sitting in its column.
One form chosen where your file used two (26)These are rows where your own submission used both forms, so I had to settle on one. The one I picked is yours in every case.
The -en form on buttons and screen-reader labels (6)Dutch buttons and labels use the -en form (Verplaatsen) rather than the command form (Verplaats). Your file used both.
A rule that is not visible in the review table (2)
Plainer wording, both correct (6)These are the rows where both readings are correct Dutch and I kept the shorter or plainer one.
Alt-key letter moved, wording unchanged (3)NOT an edit to your Dutch. Two controls on one window may not share an Alt key, and scripts/check-accelerators.mjs enforces it. The words in these three rows are yours, letter for letter; only the underscore moved. Five access letters differ from your file in all. The other two, Action.OpenReleasePage and Action.ScanAgain, appear under the family where their wording changed, and their letter moved as a consequence of that rather than for the dedupe.
Your wording partly restored in this pass (16)
Restored to your wording in this pass (13)These now ship exactly what you wrote. They are listed because they are not visible anywhere else.
|
|
The English itself changed after you sent it (51 rows) The app has been reworded for 3.0.0. These rows answer an English sentence the app no longer has, so I rewrote the Dutch against the new sentence rather than editing yours.
|
What this changes
Why
How it's been tested
dotnet buildsucceedsdotnet testpassesNotes for the reviewer