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
Recent comments
GlotPress Trac- Ticket #203 (Replace 'I8N' string with 'Translations') closed
- Ticket #203 (Replace 'I8N' string with 'Translations') created
- Ticket #202 (Add Facebook locales to locales.php) closed
- Changeset [690]: Add Facebook locales, fixes #202, props mdawaffe
- Ticket #202 (Add Facebook locales to locales.php) created
- Ticket #201 (GlotPress files should always be included as absolute paths) closed
- Ticket #201 (GlotPress files should always be included as absolute paths) created
- Ticket #200 (Add Support for Mexican Spanish) created
- Ticket #32 (Reputation System) closed
- Ticket #199 (Order subprojects BY ID DESC) created
- Core i18n Tickets
- #19950: Support the Uyghur translation
- #7837: Localization of numbers should be supported
- #11226: Month name declension case
- #6425: Support for RTL in feeds
- #7098: Multiple entity codes in POT file for the same character
- #10005: Some strings need "no HTML entities" translator comments
- #10373: Proper number formatting related to i18n
- #11740: Sorting tags and towns does not work well for utf-8
- #12477: Search with special characters and similar terms
- #12905: the_title_attribute() is hard to internationalize
geminorum 1:02 am on February 8th, 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.