Skip to content

Explain change in abbreviated month name formatting in Dutch locale #9508

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

Open
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

emirmx
Copy link
Contributor

@emirmx emirmx commented May 8, 2025

No description provided.

@@ -42,3 +42,5 @@ The following changes in behavior have been noticed when migrating from Java ver
[Locale data updates in Java version 20](https://www.oracle.com/java/technologies/javase/20-relnote-issues.html#JDK-8284840) mean that [date formatting microflow expressions](/refguide9/parse-and-format-date-function-calls/#format-datetime-utc) return a different result when the format string contains AM or PM.

In Java versions below 20, a space would be included before the AM/PM, but now it will be a Unicode non-breaking space (NBSP or NNBSP, \u202f). In a microflow expression, this non-breaking space can be included in a string using `urlDecode('%E2%80%AF')`—for example `'8:24' + urlDecode('%E2%80%AF') + 'AM'`.

In Java versions below 21, a period would be included at the end of the abbreviated month name (`MMM`) for the Dutch locale. In 21 and up the there will not be a period at the end of abbreviated month name.
Copy link
Contributor

Choose a reason for hiding this comment

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

"In 21 and up the there will"
->
"In 21 and up there will"

@Yiyun333
Copy link
Collaborator

Yiyun333 commented May 9, 2025

@atennapel Thanks for sending us the PR! Does this also apply to Studio Pro 10 and 11 (beta 1)?

@atennapel
Copy link
Contributor

Yes it applies to all versions that support Java 21. That includes 10 and 11.

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