Make WordPress Core

#56509 closed defect (bug) (invalid)

RTL direction tag is missing when select Sindhi (سنڌي) Language in WP

Reported by: yaseenperhyar's profile yaseenperhyar Owned by:
Milestone: Priority: normal
Severity: major Version: 6.0.2
Component: I18N Keywords:
Focuses: rtl Cc:

Description

This bug is occur in all wordpress version. Whenever I choose Sindhi (سنڌي) Language in wordpress site it add lang="snd" attribute but don't add dir="rtl" attribute in html tag.

Sindhi language is widely by people of Sindh province of Pakistan, and here people communicate with this language in written and spoken both way.

Kindly help me to solve this bug soon.

Regards,
Yaseen Perhyar.

Change History (5)

#1 @sabernhardt
22 months ago

  • Component changed from Help/About to I18N

Hi and thanks for the report!

The translation is "ltr" (even though the input fields on the following Translating WordPress page are set to RTL):
https://translate.wordpress.org/projects/wp/dev/snd/default/?filters%5Boriginal_id%5D=40305

You could submit "rtl" as a translation, and when it's approved that should change the direction for all Sindhi language sites.

#2 @tobifjellner
22 months ago

In https://meta.svn.wordpress.org/sites/trunk/wordpress.org/public_html/wp-content/mu-plugins/pub/locales/locales.php Sindhi is tagged as RTL. But perhaps there are some issues with the language pack generation.
It would be great if you could join Slack (via https://make.wordpress.org/chat/ ) and discuss this in our channel "meta-i18n", where the right people hang around that can troubleshoot this.

This ticket was mentioned in Slack in #meta-i18n by tobifjellner. View the logs.


22 months ago

#4 @tobifjellner
22 months ago

I have now approved the "translation" of ltr to rtl.

#5 @sabernhardt
22 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Thanks! With the approval of 'rtl' as the translation, I'll close this ticket.

The invalid resolution reflects the similar ticket #55790, "since it's not an issue with core but rather an incorrect translation."

Note: See TracTickets for help on using tickets.