Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix #123531: separate Flemish from Dutch Qt translation #2809

Merged
merged 1 commit into from Sep 6, 2016

Conversation

Jojo-Schmitz
Copy link
Contributor

for the difference in translation of the "Discard" button, 'Verwerpen' vs. 'Niet opslaan'. Also add shortcuts to the Discard and Save buttons.
Also make sure the qt_*.qm files get build by 'make lrelease'

for the difference in translation of the "Discard" button, 'Verwerpen'
vs. 'Niet opslaan'. Also add shortcuts to the Discard and Save buttons.
Also make sure the qt_*.qm files get build by 'make lrelease'
@jeetee
Copy link
Contributor

jeetee commented Sep 4, 2016

+0 from a Flemish voice; our languages share nearly all terms with regards to software linguistics.

Further looking into this specific one, it seems Dutch people mostly see 'Verwerpen' as a dated translation, although it is technically still the correct translation of "Discard" vs "Don't Save" (reference to a similar question (in Dutch) for the OpenOffice project: https://forum.openoffice.org/nl/forum/viewtopic.php?f=16&t=399)
I personally don't find the minor differences between our languages big enough to warrant separate translations. I'm also not opposed to changing the translation to match the modern trend, but looking at that evolution it seems more programs are tending towards a simplified Yes/No/Cancel, rather than Save/Discard/Cancel

@lasconic lasconic merged commit 7dccb92 into musescore:master Sep 6, 2016
@Jojo-Schmitz Jojo-Schmitz deleted the ne_NL-vs-nl_BE branch September 6, 2016 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants