-
Notifications
You must be signed in to change notification settings - Fork 26
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
Translations of core.json really outdated (e.g. german de_DE) #256
Comments
Hi there, and thanks for your interest in helping us with translations! You're right that the translation files in this repository are out of date; that's actually because we've switched to storing translation data in our main Additionally, we've got plenty of other content that we're always accepting translations for. You can find out more about all of our translation needs here |
Thank you for taking the time to point me to the right file location (was core.json, now "de_de.js"). The translation errors in blockly I'm refering to, are also in the current de_de.js and show up in the current german course curriculum (all exercises with variables). It could be the result of a code.org-crowdin issue or of my limited understanding of how crowdin is used by code.org. If you don't mind me going of topic I'll now describe one of the issues in detail. Maybe you can help me understand it or point me to the right place... In the current de_de.js you can find the following strings, which all translate english 'to' to german 'An', but should actually be translated into two different german words depending on context: The problem for me is, that eventhough the whole content of the old code.json is shown in crowdin when I click on Translated File Preview (with all three strings seen above) I can only find one translation of 'An' in crowdin which probably refers to the first two translation strings (as implied by crowdin context). Questions:
Thank you!!! |
I've passed your questions team, and they should be getting in contact with you on Crowdin regarding question 1 (if they haven't already!) and put you in touch with our German proofreaders. For question 2, the answer is a bit complicated. The usual way we recommend to do this is by referencing the |
Hi there,
please point me to the right place, if this isn't appropriate:
I wanted to help with code.org translations, but then noticed, that even the most aggressive translation mistakes, were already corrected up to five years ago in crowdin, though not approved in crowdin.
What can I do help get the blockly/core.json file updated or incorrect translations unapproved in crowdin?
I'd love to contribute by translating code.org blockly core or materials into german, but it doesn't seem worthwhile if files are not updated. Would it be easier if I generate a pull request for german core.json?
Thank you.
The text was updated successfully, but these errors were encountered: