-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Added nl language #5354
Added nl language #5354
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@berendjan - thank you for your contribution - Dutch localization!
Having not "witnessed" the previous localization additions, it's not entirely clear to me what else is necessary for this. On the surface, everything looks good, but I'd prefer another set of eyes on this particular review.
One reservation I have is that these translations were performed via the Translator Text API. In my experiences with i18n on other projects, this task was typically performed by humans, often with multiple iterations, due to contextual misunderstandings, etc. Assuming you speak/read Dutch, how well do you feel the translations are in preserving the original intent of the given message? It would be good to minimize the number of fixups required because the machine didn't quite interpret intent correctly.
I noticed that the I raised an issue #5356 |
Furthermore, we need more volunteer language checkers to iterate the translations.
For testing at runtime: |
@kevin-bates I checked the translations and changed them where I found necessary, but you are absolutely right and probably iterations are necessary. I changed the commit to a [WIP] and gave some instructions above, I also noticed that the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@berendjan - thank you for making an initial "human" pass on the translations. I think that's sufficient to move this forward. I agree with your "ask" for more spell checkers. However, I believe that might not happen for a while and iterating on these messages, post-release, is probably more likely anyway.
I'm good with where this is, but will likely leave this open for a few more days to allow for other reviews.
Thanks again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should indeed be looked at by a human. A quick glance makes some miss translations clear. Another fundamental question:
- What is the translation of 'notebook'? 'Notitieblok' feels awkward. 'Werkblad' (worksheet) makes more sense. (Or just keep the English 'notebook')
@toonijn - thank you for the great review. I'd like to start down the path of putting together a 6.1.0 release and would love to have this included. @berendjan - would it be possible to respond to Toon's review comments fairly soon? |
@toonijn Thank you for your input, it's much appreciated. I have to agree that 'notitieblok' which is a notepad in English sounds weird. I changed everything to notebook as I presume people who come in contact with Jupyter Notebook will be more familiar with the English name even when their system settings are Dutch. If you have time, please look at the changes and comment away! I'll try to address them asap. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- "cellenuitvoer" is not a real word. I don't really have een alternative maybe "resultaat van cel", or something like that.
- What do we call a cell of type 'raw'? We just could keep 'raw'.
Looks good to me! |
Fantastic - thank you both @berendjan and @toonijn! @toonijn - could you please select approve on your review, then I think we'll merge in a day or so to allow others to chime in one last time. |
Thanks @toonijn. @berendjan - if you're all set, please update the title and we'll take the next step. |
@toonijn @kevin-bates Thanks to you both, I removed [WIP] from the title. |
No description provided.