Opened 4 years ago
Closed 4 years ago
#52110 closed enhancement (fixed)
locale 'de_AT' should be added to 'german' locales in remove_accents()
Reported by: | nonverbla | Owned by: | audrasjb |
---|---|---|---|
Milestone: | 5.7 | Priority: | normal |
Severity: | trivial | Version: | 5.5.3 |
Component: | I18N | Keywords: | good-first-bug has-patch commit |
Focuses: | Cc: |
Description
Hi there! My first WP ticket ever. I just noticed that the locale de_AT
for Austria is not being handled in remove_accents()
. So ü
for example would be converted to the WP default of u
instead of the correct ue
. Here is the code (formatting.php, line 1299):
if ( in_array( $locale, array( 'de_DE', 'de_DE_formal', 'de_CH', 'de_CH_informal' ), true ) ) { ...
Attachments (2)
Change History (12)
This ticket was mentioned in Slack in #accessibility by ryokuhi. View the logs.
4 years ago
#4
@
4 years ago
Hi! First time contributor here learning the ropes of the process.
Added 'de_AT' first to order alphabetically (?)
#6
@
4 years ago
Thank you for the patch! The system needs diff files to be generated against WordPress development files and not built versions of WordPress.
52110.diff refreshes the patch against trunk.
#7
@
4 years ago
The system needs diff files to be generated against WordPress development files and not built versions of WordPress.
Thank you for pointing this out to me. Is there any link or resource I can read more about to understand what to do instead of what I did?
I understand the concept of what you're saying, but not how to achieve it, if that makes sense. Thank you in advance.
#8
@
4 years ago
- Keywords commit added
- Owner set to audrasjb
- Status changed from new to accepted
Welcome @patopaiar ! You can checkout our Core handbook to learn more about working with patches and GIT.
I tested the proposed patch: it still applies cleanly against trunk and it looks good to me.
Marking this for commit
. Thanks all.
Hello @nonverbla, and thanks for the enhancement suggestion.
We discussed this issue today during the accessibility team's weekly bug-scrub.
The team thinks that this is not an accessibility issue, so we are removing the focus.
Some team members think that this might be a good-first-bug, but we are leaving the final decision to the component maintainer.