Description Lynne Kues 2001-10-11 14:23:15 EDT

NOTES:

LK (8/24/01 2:11:24 PM)
	1GI7ALA: SWT:WINNT - GC.stringExtent returns incorrect value
		- Leads to selection cheese when using bold styles in the bidi StyledText widget.
		- For certain TrueType fonts in Arabic, leads to text being rendered improperly (e.g., characters "cut off" and 
		selection cheese) in the StyledText widget.

	1GHP2LB: SWT:WIN - Font is wrong when starting Eclipse in different language (bidi vs. non-bidi) versions
		- When you specify Courier as the font for the Java Editor, save the workspace, and then use the non-bidi
		workspace on a bidi platform (or vice versa).  The font does not get mapped correctly when you move 
		to the different bidi-language platform (i.e., Eclipse thinks the font is something different than what SWT thinks 
		the font is) and this leads to characters being incorrectly rendered in the JavaEditor.  To fix the problem, change 
		the Java Editor font to something other than Courier, then change the font back or do not use the same workspace 
		on bidi and non-bidi platforms.  The problem has only been seen with respect to the Courier font, but it may 
		also occur for other fonts. 

	SWT isBidiPlatform flag
		Currently we are testing the code page to figure out if we are on an Arabic or Hebrew platform, we
		believe SWT should be supplying this method (not StyledText) and that it should be public.

	Performance
		Need to look at the StyledText widget's bidi performance and identify/fix slow areas.  Also need to look 
		into autoscrolling behavior:
			1GIZ7A6: SWT:ALL - StyledText - implement better autoscrolling behavior
		Autoscrolling horizontally in bidi mode is flashy at times.  This also needs to be improved.

	Right Alignment 
		Investigated.  As of now, not committed.  Whether or not it can be done depends on bidi people feedback
		and final dates.  SWT will offer no support to help with this (e.g.,a right aligned canvas), so it's a non-trivial 
		task.  We need SetTextAlign platform support to do this.  Setting the text alignment to RtoL will return the 
		correct order, dx, etc. arrays in GCP.
		 
	Running in bidi mode on non-bidi platform
		Currently this will not work since GCP returns an empty order array for a non-bidi platform
		(since the string doesn't need to be reordered).  We could better handle this scenario if	
		necessary.  Right now our bidi class expects to be called only on a bidi platform.  This is an
		issue if the Eclipse application is the one who sets the bidi flag.


LK (27/08/2001 18:04:02)
	Running in bidi mode on non-bidi platform does work on Win2K.  Need to test this on Win98/WinNT.
	Does NOT work on WinNT, order array is all zeroes.
	
MA (06/09/2001 18:04:39) There is no expectation and no requirement that Bidi mode will run on non-Bidi WinNT 
	or Win98.  Win2k has common executables for all languages, so is always a "Bidi platform".

LK (10/09/2001 11:12:32)
	Bidi Caret Support - to be implemented, need SWT to implement the following PRs first:
		1GIXFA6: SWT:ALL - Need event for when input locale changes for bidi support
		1GIXELI: SWT:ALL - Need Caret to allow bitmaps so bidi caret can be created
		Also need to remember to add an inset to the StyledText widget so that the bidi cursor can be seen
		when the cursor is positioned on the LHS of the screen in front of a RtoL segment.
	Fixed in 1.0/NL stream.

LK (04/10/2001 16:52:49)
	Opened "1GL3AWT: SWT:ALL - StyledText - bidi - partial styling of ligatures" for the ligature problem.