Need some RTL feedback here: http://core.trac.wordpress.org/ticket/6425. How should be be handling RTL content in RSS feeds?
-
Andrew Nacin
Reply
Unresolved »
Showing 1-10 of 10 unresolved posts
10Recent comments
GlotPress Trac- Changeset [763]: Change test case for changed parity factory function. See #181
- Changeset [762]: Add missings images for #181
- Changeset [761]: Add missing tablesorter plugin. See #181.
- Changeset [760]: Make HTML/CSS changes to have it correctly done. See #239
- Ticket #240 (Change Translation Text Direction fro RTL Languages) closed
- Ticket #240 (Change Translation Text Direction fro RTL Languages) created
- Ticket #239 (Project overview should be 100% width) closed
- Changeset [759]: Make project view 100% width unless there are subprojects. Fixes #239
- Changeset [758]: Make translation sets sortable through the interface. Also fixed ...
- Ticket #100 (Notifications for certain actions) reopened
- Core i18n Tickets
- #24183: MediaElement.js i18n issues
- #23907: Scandinavian ligatures transcribed wrong in remove_accents()
- #23794: load_plugin_textdomain fails if plugin is loaded from mu-plugins
- #23758: Add hook after loading WordPress locale object
- #23721: Better control of textdomains.
- #23503: Post Formats: i18n issues
- #23433: Custom background select needs a contextualized label
- #23341: Spell checker in the editor shows languages not supported by google spellchecker like hebrew
- #23311: Enable internationalization in PHPMailer
- #23056: date_i18n() does not localize dateformat 'r'
geminorum 1:02 am on February 8, 2012 Permalink |
I think there is no need to add direction styles on the feed content. The readers usually support the RTL automatically, such as Google Reader and IE feed reader. Also, we’re usually apply the styles when fetching via code into the content, that is also RTL.
The advantage is only for when mixing RTL and non-RTL feeds together.