The URL for the article should contain those characters transliterated to ASCII
UI accessibility concerns?
Ideally, nothing should change on this front.
Added/updated tests?
[x] Yes
[ ] No, and this is why: please replace this line with details on why tests
have not been included
[ ] I need help with writing tests
[Forem core team only] How will this change be communicated?
Will this PR introduce a change that impacts Forem members or creators, the
development process, or any of our internal teams? If so, please note how you
will share this change with the people who need to know about it.
[ ] This PR changes the Forem platform and our documentation needs to be
updated. I have filled out the
Changes Requested
issue template so Community Success can help update the Admin Docs
appropriately.
[ ] I've updated the README or added inline documentation
[ ] I will share this change internally with the appropriate teams
[ ] I'm not sure how best to communicate this change and need help
[ ] This change does not need to be communicated, and this is why not: please
replace this line with details on why this change doesn't need to be
shared
</div>
<div class="gh-btn-container"><a class="gh-btn" href="https://github.com/forem/forem/pull/15051">View on GitHub</a></div>
this PR might fix things for cases like yours.
For further actions, you may consider blocking this person and/or reporting abuse
Not just legible, If I click on the link xn--8ws00zhy3a.com , the link opened has translated to the Chinese characters in the url
May not be the exact thing I was initially mentioning, but looking for something that could improve the SEO for non-english Forem instances.
This is not resolving to the telugu characters in the url.
It looks like the "sterile" library will do transliteration,
What type of PR is this? (check all applicable)
Description
Article titles written in languages with non-Roman alphabets (Cyrillic, Greek, Hebrew, etc) have the entire title stripped from the slug.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
UI accessibility concerns?
Ideally, nothing should change on this front.
Added/updated tests?
[Forem core team only] How will this change be communicated?
Will this PR introduce a change that impacts Forem members or creators, the development process, or any of our internal teams? If so, please note how you will share this change with the people who need to know about it.
CHANGELOG.mdthis PR might fix things for cases like yours.