Issue 10345 - Can't control directionality when composing HTML documents
Summary: Can't control directionality when composing HTML documents
Status: CLOSED FIXED
Alias: None
Product: Internationalization
Classification: Code
Component: BiDi (show other issues)
Version: current
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-29 16:25 UTC by sforbes
Modified: 2013-08-07 15:02 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description sforbes 2002-12-29 16:25:22 UTC
Althugh my text object toolbar has the directionality control buttons, when
opening OO directly to the HTML editor, they are gone.
Checking the toolbar prefrences shows them as marked.

To repro:
* in OO write, make sure that the text object toolbar has directionality buttons.
* Shout down OO completely, and then open on the HTML editor sirectly
* Notice that there are no directionality control buttons
* check the toolbar setup- note that they are marked
Comment 1 Dieter.Loeschky 2003-01-17 11:03:40 UTC
DL->SBA: Would you please takeover?
Comment 2 thorsten.ziehm 2003-01-31 11:57:07 UTC
=> new
Comment 3 stefan.baltzer 2003-02-03 17:23:11 UTC
SBA: Same as internal #106285. Of course, HTML must provide BIDI too. 
Fix verified for 644 in CWS SW-001. Closing.

Note: The appropriate codepages (Arabic and Hebrew) have to be
selected at "Tools - Options - [$Productname]-General-HTML
Compatibility" to save a BIDI document with Hebrew charaters. UTF-8
would work too, but the introduction of Arabic and Hebrew code pages
is subject of internal #106103 (Already fixed in CWS Calc03).
Comment 4 stefan.baltzer 2003-02-03 17:24:10 UTC
Marked verified.
Comment 5 michael.bemmer 2003-03-13 11:09:47 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.