Right to Left (Hibrow & Arabic) is not supported!

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Web editors do not provide rtl-ltr switching toolbar while it shouldn't
be very complicated.
2. Text aligns are not rtl compatible and changing the dir attr. of body
can not solve it. Labels are still left aligned. would be better to add a
dir attr. to form object.
3. Date object does not support any calendar systems other than Gregorian!  

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
Version 3, 29 June 2007, Win7 with chrome/firefox

Please provide any additional information below.
Jalali calendar is largely used in the middle east and is known to
Microsoft as "Persian Calendar" and fully supported in the .NET Framework,
but not mentioned in date picker!

Original issue reported on code.google.com by estahban...@gmail.com on 11 Apr 2010 at 10:11

[GoogleCodeExporter]

The version used is April 2, 2010, the date above is GNU date!

Original comment by estahban...@gmail.com on 11 Apr 2010 at 10:28

[GoogleCodeExporter]

Hi,

At the moment the class doesn't have any localization, and thus no RTL support.
Localization is a low priority but eventually it will be implemented.

For the datepicker item in jquery there are localized versions available that 
could
be integrated:

http://jqueryui.com/demos/datepicker/localization.html ,

In ckeditor you can switch the editor by a setting in a ckeditor config file

CKEDITOR.config.contentsLangDirection = 'rtl';

This just makes the contents rtl in the editor.

Original comment by moncojhr@gmail.com on 12 Apr 2010 at 2:24

• Added labels: Type-Enhancement, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

Original comment by moncojhr@gmail.com on 12 Apr 2010 at 2:42

• Changed state: Accepted

[GoogleCodeExporter]

Thank you for the suggestions and guides. I checked the localization facilities 
of
JQuery Datepicker and found it funny. You might be interested to know about it:

Talking about date, localization is not only translation of month and day 
names, or
providing local date formats which is available in localization modules. 
Localization
is supporting local date systems. To be more exact, when you localize to a 
Persian
calendar, you have to consider that a Persian year starts at the beginning of 
spring
(Nowrouz) rather than winter (Christmas). Although Persian calendar is much 
older
than the Gregorian one, it is re-initiated with Muslims Hijri date initiator, 
621
years later than Gregorian calendar. So the year 2010, would be year 1388-1389 
in
Persian calendar and year 1431 in Hijri calendar (based on the moon 
orientation).
Months are not starting with Gregorian months and day count of months are not 
the
same as Gregorian calendar. Only weekdays of the three are the same.

"Persian Calendar" (also known as "Jalali Calendar") has it's own calculation 
method
and has to be converted into, to localize JQuery datepicker. Microsoft is fully
supporting it and it stores dates as a standard value so that when you specify a
Persian date and save it in a database, it can be retried with Gregorian 
equivalent
if Persian face not available.

As far as I know, this is not only about Persian Calendar, but there are also 
some
other date systems legally used by governments that need to be localized.

Original comment by estahban...@gmail.com on 18 Apr 2010 at 8:15

[GoogleCodeExporter]

I found a conversion oriented DatePicker localization here:
http://keith-wood.name/calendarsPicker.html
It seems to be working properly with both Islamic and Persian Calendar (but 
needs
translation since uses Latin alphabets.)

Original comment by estahban...@gmail.com on 5 May 2010 at 12:20

[GoogleCodeExporter]

Hi estahbanati,

At the moment for forms you create, what do you use when you need to create a
calendar? And when we start working on localization, would you advise that the
calendar solution at http://keith-wood.name/calendarsPicker.html is good and 
correct?

Original comment by moncojhr@gmail.com on 12 May 2010 at 2:12

[GoogleCodeExporter]

This issue has become stale so I'm closing it.

Original comment by ajporterfield@gmail.com on 14 May 2011 at 3:32

• Changed state: WontFix