__group__,ticket,summary,owner,component,_version,priority,severity,milestone,type,_status,workflow,_created,modified,_description,_reporter
Next Release,24105,Twenty Thirteen: Title and Content  RTL in IE8,,Bundled Theme,trunk,normal,normal,,defect (bug),closed,rtl-feedback,2013-04-16T19:27:11Z,2013-04-22T16:26:35Z,"In Windows7 IE8 using RTL the title and content of the post is reduced in width… See screenshot http://cl.ly/image/2k1S1D1Q0T1m 

Further review shows the h1 width to 288px which is not the 604px that the title usually gets from other browsers.

http://cl.ly/image/180Y302z0W0g 

IE9 and IE10 is not effected by this…",RDall
Next Release,24287,Twenty Thirteen: evaluate Genericons and RTL support,lancewillett,Bundled Theme,,normal,normal,3.6,defect (bug),closed,rtl-feedback,2013-05-08T19:10:38Z,2013-05-09T20:08:39Z,"Check each Genericon and its support in the RTL stylesheet and evaluate if we need to switch the {{{:before}}} to {{{:after}}} or if a flipped icon is needed.

From SergeyBiryukov in #24286:

> Also, in RTL we switch :before and :after, so the sign ends up after the message. I don't think we should do that, text direction appears to take care of the correct positioning automatically. We should only fix floating and margins. ",lancewillett
Next Release,19072,TwentyEleven: bug in rtl.css,nacin,Bundled Theme,,normal,normal,3.3,defect (bug),closed,rtl-feedback,2011-10-28T02:32:11Z,2011-11-15T20:20:44Z,"There is a small bug in the TwentyEleven rtl.css file.

`.ltr ul, ol {
	margin: 0 0 1.625em  2.5em;
}`

should be

`.ltr ul, .ltr ol {
	margin: 0 0 1.625em  2.5em;
}`",wpweaver
Next Release,20837,About WordPress: Wrap class/function names into code tags,nacin,Help/About,3.4,low,minor,,defect (bug),closed,rtl-feedback,2012-06-04T19:27:31Z,2012-10-25T20:14:27Z,Just needs some magic from Nacin for GlotPress.,ocean90
Next Release,19598,Text inputs for code or URLs should be LTR,georgestephanis,I18N,,normal,normal,3.4,task (blessed),closed,rtl-feedback,2011-12-18T21:15:05Z,2012-09-17T06:42:33Z,"Various options fields need to be LTR. Some locales (well, at least ug_CN) hardcode these as LTR:

 * upload_url_path and upload_path on options-media.php
 * mailserver_url, mailserver_login, and mailserver_pass on options-writing.php
 * Functions in the docs-list select box on plugin-editor.php and theme-editor.php
 * admin_email, new_admin_email, home, siteurl on options-general.php

If some RTL languages believe these should be RTL (URLs in particular, I'm curious about), we need to know.",nacin
Next Release,24326,Admin RTL bugs,,RTL,trunk,normal,normal,3.6,defect (bug),new,,2013-05-12T18:22:37Z,2013-05-17T16:30:45Z,"Hi, This a list of some RTL style bugs I found it today in the beta 3 update.",alex-ye
Next Release,19024,Help menu issue with RTL,azaozz,RTL,3.3,normal,normal,3.3,defect (bug),closed,rtl-feedback,2011-10-21T16:14:43Z,2011-10-28T23:05:59Z,Help menu doesn't have RTL style! Please look at screenshots.,gonahkar
Next Release,22935,Horizontal scrollbar in RTL media modal,,RTL,3.5,normal,normal,3.6,defect (bug),new,,2012-12-14T11:31:22Z,2013-05-11T16:30:59Z,"The new media tab needs a few RTL adjustments on the UI, check out the screenshot.",ramiy
Next Release,19778,"Plugin installer Description tab LTR in RTL, rest not",nacin,RTL,,normal,normal,3.4,defect (bug),closed,rtl-feedback,2012-01-08T06:14:48Z,2012-04-27T18:52:59Z,"Mainly a consistency thing here, The Plugin Installer info dialogue currently has english-only content due to the return values of the API being english.

As a result (I assume) the RTL styles for the plugin installer specifically set the text direction to LTR for the description tab, however, other tabs (changelog, other notes, etc) are still rtl'd.

For now, until we have translation support for the content there, it seems best to ltr all the sections?

Suggested change; current:
{{{
#section-description {
  direction: ltr;
}
}}}
to
{{{
#plugin-information #section-holder .section {
  direction: ltr;
}
}}}

Upon a second glance, this may cause issues for the translated titles in #16580, so we might want to specifically set the h2 to rtl",dd32
Next Release,22897,RTL on plugin information tab,,RTL,3.5,normal,normal,3.6,defect (bug),new,rtl-feedback,2012-12-12T20:26:28Z,2012-12-15T11:51:32Z,"The plugin information tab needs a few adjustments RTL adjustments, check out the screenshot.",ramiy
Next Release,16834,UI problem in Permalinks SubPanel (on RTL sites),ramiy,RTL,3.1,normal,normal,3.6,enhancement,reopened,rtl-feedback,2011-03-11T15:15:12Z,2013-05-18T07:11:57Z,"hi,
i want to report a UI problem in RTL sites, on the Settings->Permalinks SubPanel.

See the  Attached screenshots.",ramiy
Future Releases,9272,Expand human_time_diff()'s abilities,Viper007Bond,Date/Time,2.8,normal,normal,Future Release,enhancement,new,rtl-feedback,2009-03-04T10:42:21Z,2013-03-08T17:21:44Z,"This is partially related to #7250.

Currently `human_time_diff()` can only do days, hours, and minutes. I propose we expand it a bit, to at least weeks and possibly even months and years (although that can be tricky unless PHP has a shortcut).

It should also support the ability to trim to a certain accuracy, i.e. for a 2 year 1 month old post, minutes don't matter.

In short, I propose we integrate Time Since's functionality into the core by expanding the current `human_time_diff()`.",Viper007Bond
Future Releases,6425,Support for RTL in feeds,nbachiyski,I18N,,normal,normal,Awaiting Review,enhancement,assigned,rtl-feedback,2008-03-27T20:56:51Z,2012-02-08T06:07:07Z,"In the current state of most Feed readers, the only surefire way to make RTL content display properly is to have directionality enforced inside the content - that is, either with {{<div dir=""rtl"">}}} tags inside CDATA or with Unicode directionality characters (for e.g., RLE and PDF, or &#8235; and &#8236;, or U+202B and U+202C.) for excerpts or titles.

While we currently have pretty good support for RTL languages, there is no support for RTL in feeds - all is left up up to the feed reader.

I suggest adding a mechanism to automatically insert these tags/characters for blogs that have text_direction set to RTL - much in the same way RTL css style sheets are loaded for these blogs.

I have attached a patch that modifies the feed templates to insert these tags/characters. Note that there is no checking of blog directionality here - this is just an example of how to enforce RTL in feeds, not how to enforce it conditionally.

This relate to a previous ticket I submitted (#5517), regarding adding an option to set the feed language - which currently just defaults to EN. Certain feed readers know to display RTL text in proper directionality according to feed language (for e.g., feeds that have their feed language set to HE (Hebrew), will get displayed from Right to Left). While setting feed language is not a comprehensive solution, it is a step in the right direction.",RanYanivHartstein
Future Releases,13643,"[twentyten] CSS RTL conflict with ""Skip to content"" accessibility link",yoavf,Themes,3.0,normal,normal,WordPress.org,defect (bug),closed,needs-rtl,2010-05-30T19:05:32Z,2010-07-30T19:36:50Z,"While developing a twentyten child theme in Hebrew, I encountered this bug.

When a language such as Hebrew that is written from right to left is used in WordPress, it automatically links to the theme's rtl.css file if available.

In the current twentyten theme, the rtl.css file makes the ""Skip to content"" link clickable.

From twentyten's rtl.css:
{{{
/* Text meant only for screen readers */
.screen-reader-text {
	left: auto;
	text-indent:-9000px;
	overflow:hidden;
}
}}}

This ""left: auto"" property overrides the style.css left property.

From twentyten's style.css:
{{{
/* Text meant only for screen readers */
.screen-reader-text {
	position: absolute;
	left: -9000px;
}
}}}

The link is there and it is clickable but there is no text thanks to the text-indent and overflow properties.

Mouseover screenshot:
http://i50.tinypic.com/25gugk2.jpg

Google chromes inspect element (Chrome's firebug equivalent):
http://i49.tinypic.com/28bsknr.jpg

You can easily reproduce this problem by installing a fresh WP3-RC1, then copying he_IL's language files to wp-content/languages, and editing the WPLANG in wp-config to ""he_IL"".

Solution - delete the following lines from rtl.css:
{{{
/* Text meant only for screen readers */
.screen-reader-text {
	left: auto;
	text-indent:-9000px;
	overflow:hidden;
}
}}}",Ornani
Future Releases,22059,Making the admin bar responsive,,Toolbar,3.4,normal,normal,Awaiting Review,enhancement,new,rtl-feedback,2012-09-30T16:58:12Z,2013-02-28T18:32:30Z,"Hi,

This patch is made to add responsive layout to the admin bar. It comes from the ""Responsive adminbar"" plugin (http://wordpress.org/support/plugin/responsive-adminbar, thanks to skodnik).

Basically, I added some html tags to some menu items in the admin bar (using the ab-icon / ab-label combo) in order to handle the new icons I added to the ""admin-bar-sprite.png"".

I took the images straight from the plugin but some states are missing or some images should be changed as they are not appropriate (a ""heart"" for the network seems weird). I'm also missing the ""View post"" icon which now defaults to the ""Edit post"" one.

the CSS could be refactored I guess in order to avoid using ids.
I have not tested RTL!

Cheers from Hackday Lisbon :)

Jonathan",JoN1oP