Issue 24113

Summary:	Although document language is set to Hebrew text direction is LTR in Writer Web [WAS: althugh the local is set to Hebrew, new HTML documents start as English]
Product:	Internationalization	Reporter:	sforbes <xslf>
Component:	BiDi	Assignee:	AOO issues mailing list <issues>
Status:	CONFIRMED ---	QA Contact:
Severity:	Trivial
Priority:	P3	CC:	alan, issues, kaplanlior, yba
Version:	OOo 2.4.0
Target Milestone:	---
Hardware:	All
OS:	All
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description sforbes 2004-01-05 15:06:28 UTC

Windows 2003/Gentoo Linux/ OOo 1.1 With Hebrew local, and HTML save charset set
as windows-1255:

When starting a new HTML document, the new document starts as LTR and all new
elements are LTR by default.

As the local is set to Hebrew, I would expect everything should start as RTL,
like writer does.

Comment 1 Dieter.Loeschky 2004-04-06 12:48:15 UTC

DL->US: Could you please handle this?

Comment 2 Martin Hollmichel 2005-03-11 13:55:13 UTC

reassign open l10n issue to new default owner.

Comment 3 falko.tesch 2005-03-21 15:44:21 UTC

Re-assigned to owner DL suggested (US)

Comment 4 ulf.stroehler 2005-03-21 16:22:27 UTC

Assuming the following settings: 
 * Tools/Options/Languages/Default languages for documents: Hebrew
 * Tools/options/Load/Save/HTML Compatibility/Character set Hebrew (ISO-8859-8)

With the above settings the html charset and LANG style are ok. Hence the
"Summary" of this issue is at least misleading. Changing.

The only thing missing is the Direction which has to be set manually at the
moment (currently DIR="LTR").

In contradiction to the submitters expectation we shouldn't set the text
direction what ever it is (LTR/RTL) in direct connection to the desktop locale
(that would be a bug) but make it comply to the document language. BTW. that's
how Writer it actually does.

US->AMA: pls. dispatch.

Comment 5 Mathias_Bauer 2005-12-02 14:26:23 UTC

Retargetted due to workload

Comment 6 kaplanlior 2008-04-09 12:06:05 UTC

The bug still exists in 2.4.0. Please update the bug info and reassign/dispatch.
Thanks.