Closed Bug 656892 Opened 14 years ago Closed 14 years ago

[ar] Multiple issues concerning Arabic and RTL support

Categories

(Websites Graveyard :: markup.mozilla.org, defect, P1)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: linostar, Assigned: stas)

Details

(Keywords: l12y)

Here is a list of the issues: 1- The font size used is too small to make Arabic content readable. 2- The floating orange box (that appears when hovering over certain items) is mispositioned, in respect to the pointer location, when the mouse hovers the 'community' link or the drawing canvas. Moreover, the arrow of this box should be placed on the left side and not the right side. The localized text corresponding to 'Coming soon' doesn't appear in this box. 3- On the main page, the big 'X' mark is shifted considerably to the right (compare with en-US), and the text on the right is totally floating beyond the right margin where it is no longer visible! 4- As for the control buttons in the drawing canvas (submit, reset, cancel, etc), the icons of those controls should be centered appropriately in respect with the texts below them (some of them are half invisible). 5- The ink amount provided when drawing on the Arabic page is much less than that provided in the English page. Taxes on web ink? :) 6- After submitting a mark, a block for Mark Browsing appears. It needs more RTL care, i.e. the icons should be on the left, the dropdown arrows and the '-' in the title should be on the right. I think that's enough for now :)
Assignee: nobody → stas
Keywords: l12y
Priority: -- → P1
Target Milestone: --- → 1.1
I'm afraid we won't be able to fix these issues before Tuesday's launch. We have two options, 1. launch Arabic as it is right now, fix it in 1.1, or 2. put Arabic on hold for 1.1 and launch it fixed in 1.1. 1.1 is planned for the end of May/beginning of June. Linostar, I'll defer to your judgment.
Priority: P1 → --
Target Milestone: 1.1 → ---
Oops, sorry, didn't mean to mess with the priority etc.
Priority: -- → P1
Target Milestone: --- → 1.1
Since those issues does not directly affect the usability of the app, I will go with option 1.
Status: NEW → ASSIGNED
(In reply to comment #1) > We have two options, > > 1. launch Arabic as it is right now, fix it in 1.1, or > > 2. put Arabic on hold for 1.1 and launch it fixed in 1.1. I meant: > 2. put Arabic on hold for 1.0 and launch it fixed in 1.1. of course. (In reply to comment #3) > status: NEW => ASSIGNEDSince those issues does not directly affect the > usability of the app, I will go with option 1. Cool. I've enabled Arabic for 1.0 in https://github.com/mozilla/markup/commit/1e095e1611a397c88c7c6417109a5a8639b11693. We will work on fixing these issues for the next push. Thanks, Linostar!
Status: ASSIGNED → NEW
Priority: P1 → --
Target Milestone: 1.1 → ---
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → 1.1
Stas - Can we get update?
Hey, I didn't have time to work on this unfortunately, and I know that Linostar has been rather busy lately too. Let's close this bug as wontfix. I'd love to provide better support for RTL, so if anyone can come up with a patch, please reopen. (Also, please comment here before starting working on the patch in case we're close to archiving the site when you do.)
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Laura can you bump this to verified if you agree?
Done.
Status: RESOLVED → VERIFIED
thx lmesa :)
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.