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

Add Dutch (Nederlands) translation #1909

Merged
merged 2 commits into from
Jan 6, 2025

Conversation

xzrfax
Copy link

@xzrfax xzrfax commented Jan 6, 2025

Relates to

Translation initiative - Adding Dutch (Nederlands) translation

Risks

Low - This PR only adds a new translation file and updates the main README with a link.

Background

What does this PR do?

  • Adds complete Dutch (Nederlands) translation of the README (README_NL.md)
  • Updates main README.md with link to Dutch version in the translations section

What kind of change is this?

Features (non-breaking change which adds functionality)

Documentation changes needed?

My changes are documentation changes themselves, adding a new translation.

Testing

Where should a reviewer start?

  1. Check README_NL.md for completeness and accuracy of translation
  2. Verify the link in main README.md points correctly to README_NL.md
  3. Ensure all formatting, links and images work correctly in the Dutch version

Detailed testing steps

  1. Navigate to the main README.md
  2. Click the "Nederlands" link in the translations section
  3. Verify it leads to README_NL.md
  4. Check that all links and images in README_NL.md are functional
  5. Verify markdown formatting is preserved

Discord username

xzrfax

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @xzrfax! Welcome to the ai16z community. Thanks for submitting your first pull request; your efforts are helping us accelerate towards AGI. We'll review it shortly. You are now a ai16z contributor!

@Mr-Don-Leo
Copy link

Mr-Don-Leo commented Jan 6, 2025

@xzrfax you need to change the merge branch elizaOS:main to elizaOS:api_docs OR elizaOS:develop, for workflow approval

@xzrfax xzrfax changed the base branch from main to api_docs January 6, 2025 13:15
@xzrfax
Copy link
Author

xzrfax commented Jan 6, 2025

@xzrfax you need to change the merge branch elizaOS:main to elizaOS:api_docs OR elizaOS:develop, for workflow approval

Sorry my bad.

@Mr-Don-Leo
Copy link

@xzrfax you need to change the merge branch elizaOS:main to elizaOS:api_docs OR elizaOS:develop, for workflow approval

Sorry my bad.

All good! just letting you know.

It looks all good other than that.

@lalalune lalalune changed the base branch from api_docs to develop January 6, 2025 13:34
@lalalune lalalune merged commit ccbc0b1 into elizaOS:develop Jan 6, 2025
2 of 3 checks passed
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.

3 participants