Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 252816 - Localization - bidi
Summary: Localization - bidi
Status: RESOLVED FIXED
Alias: None
Product: Simultaneous Release
Classification: Eclipse Foundation
Component: Prereq (show other bugs)
Version: Galileo   Edit
Hardware: All All
: P2 normal (vote)
Target Milestone: RC1   Edit
Assignee: Simultaneous Release Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 254366 254367 254369 254370 254371 254372 254373 254374 254375 254376 254377 254378 254379 254380 254381 254382 254383 254384 254385 254386 254387 254388 254389 254390 254391 254815 257310 257646 258620 260131 260132 260160 262493 263351 263379 263407
Blocks:
  Show dependency tree
 
Reported: 2008-10-30 12:51 EDT by Bjorn Freeman-Benson CLA
Modified: 2009-10-09 13:14 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bjorn Freeman-Benson CLA 2008-10-30 12:51:54 EDT 
Should design and test for enabling all languages including bidi, unicode characters, etc.
Comment 1 Ed Merks CLA 2008-11-10 19:26:03 EST 
The bidi requirement, based on past experience, is ill-defined at best.  It's well established that mixing RTL and LTR text generally results in an unusable UIs along with an endless stream of unfixable bugs, e.g., https://bugs.eclipse.org/bugs/show_bug.cgi?id=131711.

To be really clear, I can't personally agree to commit to this blanket "bidi" requirement.  I know this has lead to unsolvable problems in the past.  So if this is a must-do requirement for all projects, unfortunately that puts me in a position of having to push back for my own component.  EMF will not commit to this requirement.
Comment 2 Sean Flanigan CLA 2009-01-19 22:42:59 EST 
Perhaps it would be better to have another bug for Unicode (and other localisation issues), separate from bidi.  Or at least rename this bug to make it obvious that it's not just about bidi.  But splitting the bugs would allow the separate issues to be dealt with separately.

We wouldn't want support for Unicode 4/5 (eg supplementary chars) to slip through the net because of guilt-by-association with bidi!  A project which WONTFIX bidi could still be tested for full Unicode support and so on.
Comment 3 David Williams CLA 2009-10-09 13:14:03 EDT 
THis is a routine mass closing of the previous release umbrella tracking bugs.