Skip to content

NL translations update v2026.01.00#12300

Merged
tdipisa merged 2 commits into
geosolutions-it:masterfrom
ygodaert:translations-update-NL-v2026.01.00
May 28, 2026
Merged

NL translations update v2026.01.00#12300
tdipisa merged 2 commits into
geosolutions-it:masterfrom
ygodaert:translations-update-NL-v2026.01.00

Conversation

@ygodaert
Copy link
Copy Markdown
Contributor

@ygodaert ygodaert commented Apr 23, 2026

Description

Dutch translation update, based on the latest release v2026.01.00

Please check if the PR fulfills these requirements

What kind of change does this PR introduce? (check one with "x", remove the others)

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe: translations update

Issue

What is the current behavior?
Outdated Dutch translations

What is the new behavior?
Updated Dutch translations

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

  • Yes, and I documented them in migration notes
  • No

Other useful information

@cla-bot
Copy link
Copy Markdown

cla-bot Bot commented Apr 23, 2026

In order to contribute to the MapStore project, the CLA (Contributor License agreement) should be sent signed to GeoSolutions. Please consult contributing rules at: https://github.com/geosolutions-it/MapStore2/wiki/Contributing-to-MapStore#contributing-code

@tdipisa
Copy link
Copy Markdown
Member

tdipisa commented Apr 24, 2026

Thank you so much for this!
As expected by Community Bylaws, we need the CLA signed to accept your contribution. Can you please provide it? Thank you again.

@tdipisa
Copy link
Copy Markdown
Member

tdipisa commented May 22, 2026

Hi @ygodaert is it possible for you to complete this?

@tdipisa tdipisa self-assigned this May 22, 2026
@ygodaert
Copy link
Copy Markdown
Contributor Author

Hi @tdipisa. Severien signed the CLA today in the name of Department Mobility and Public Works. The CLA will be send to you next week. I will let you know when I receive updates about this.

@ygodaert
Copy link
Copy Markdown
Contributor Author

@tdipisa Severien sent the signed CLA doc last Tuesday

@tdipisa
Copy link
Copy Markdown
Member

tdipisa commented May 28, 2026

Hi @ygodaert yes, thanks. Waiting for this to be merged: #12434

In the meantime can you please resolve conflicts?

@tdipisa tdipisa self-requested a review May 28, 2026 08:20
Copy link
Copy Markdown
Member

@tdipisa tdipisa left a comment

Choose a reason for hiding this comment

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

Waiting for conflicts to be resolved on your side @ygodaert . Thanks.

@cla-bot cla-bot Bot added the CLA Ready label May 28, 2026
@ygodaert ygodaert requested a review from tdipisa May 28, 2026 10:09
@tdipisa tdipisa modified the milestones: 2026.02.01, 2026.01.02 May 28, 2026
@tdipisa tdipisa merged commit 71e3cc7 into geosolutions-it:master May 28, 2026
14 checks passed
@offtherailz
Copy link
Copy Markdown
Member

Request failed due to following response errors:

  • Pull request Pull request is a draft

@tdipisa
Copy link
Copy Markdown
Member

tdipisa commented May 28, 2026

@ygodaert many thanks. Please see my comment here.

@ygodaert
Copy link
Copy Markdown
Contributor Author

@tdipisa my bad... There was still a reference to "<<<<<<< HEAD=======" after resolving the merge conflicts. I opened a new pull request to fix this issue >> #12438. I didn't saw a way to add the commit to the pull #12215.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants