Created attachment 7125 [details]
An RTF file with many errors in OOo1.1Beta2

this is a very major issue which seemingly affecting many other little
glitches and renders OOo useless for the common GI joe, so I rated it P1.
Please look at it, it seems like a major cause of other problems
(namely formulas)

I did open the document with 1.1 beta 2 and see the problem that you
are talking about. Need to get my permissions from qa people to
confirm this bug.

mehlng->laimis: thanks for the quick confirmation, this is one of the
majorest bugs and needs to be taken care of quickly.

DL->mehlng: Sorry, but this is a prio 2 task.
DL->HDU: Could you please takeover?

I have the hypothesis that a wrong system font is chosen to 
layout and display this doc. If there isn't a font on the system 
that has the exactly same name like e.g. "Arial (Hebrew)" a 
fallback font will be guessed. On my system the fallback font 
seems to be pretty good so the problem doesn't show. 
 
It would be interesting if it looks better on your systems if you 
manually changed the "Arial (Hebrew)" to Arial. Can you 
please test this? 
 

Wrong Hypothesis, the fonts matters as the problems they arise vary
but the problematic display alwas remains.
The david font keeps a problem in the Quotation Marks.
THe aharoni font keeps a problem with a dot.
I'll attach screemshots and another problematic document.
The numbers issue - in which numbers does not fit their grey squares -
always remained.

Created attachment 7147 [details]
we're on david - still question mark overlaps text

Created attachment 7150 [details]
still on david, but two words has very small space between them. On MS it's perfect.

Created attachment 7151 [details]
Gutman Adi, and quotation marks makes it once again!

Created attachment 7152 [details]
another problematic RTF document from which overlapVERED.png was taken.

Created attachment 7153 [details]
in overlap.rtf there are bad tables/columns shown beautifully in MSWord but aren't wide enough in OOo, in any font you choose

Created attachment 7154 [details]
huge spaces between words in a paragraph - where it shouldn't happen.

Created attachment 7155 [details]
we're in Aharoni, still nums are not in their grey square.

Created attachment 7157 [details]
Please note the comma is in TimesNewRomans font! not in Arial!.

Created attachment 7158 [details]
shows stuff shown too big in the OOo-RTF and OK in MS-Word.

Quite an attachment eh? :-)
I'll summarise the problems in the document that I've found:
1) commas and other panctuations are always
distorted/overlapping/passes page delimiters. Always whichever font
you chooses. Always.
2) Commas are occasionally chosen different font or size - which might
specify the problem. Use your powers Duer - use them too eliminate
nasty bugs.
3) Columns and tables does not fit in OOo but they do in OOo.

Please view my attachments - and their comments. they contain INSIDE a
wise and enlightning comment about peculiarity of the problem in a
single spot.

And at last - drop a note/comment if you're on something.

HDU->US: Please try whether you can recreate any of the 
issues in a recent SO build like e.g. >= CWS VCL13. I didn't 
find any, probably the "magnus opus" patch in VCL09 solved 
most of them... 

mehlng->HDU where can I find this builds - I don't mind testing it.
BTW what's the Magnus Opus patch?

Anyhow thanks

if anyone cares - I reproduced this bug in OOo1.1RC

Listen mehlng,
OOo 1.1 is not yet final and sure we appreciate all and every effort
in improving our brand new "technical ability to display and type BiDi". 

In addition we urgently need contributers especially for Hebrew. Did
you know that the "OOo Localization Responsibilities" side is missing
an entry for Hebrew? Nobody officially cares for a hebrew localization
project.
http://l10n.openoffice.org/localization_responsibilities.html
Please subscribe. And contribute OOo with serious bug reports and/or
join the OOo QA Project. (Personally speaking I would be *very* glad
to know some hebrew native speakers, whom to contact with special
hebrew related problems and to work close with. Pls. consider this as
a serious offer) 

But pls. also consider this BiDi technology as work in progress.
Correct me if I'm wrong, but IMHO there is no roadmap that defines
that OOo 1.1 *must* be "Hebrew complete". And maybe, we're far away
from that.

But from what I can see in the attached document, it is a nicely
displayed quite complex hebrew document, that displays correct (for
me) even though I don't have the fonts.

But this issue is almost useless. 
What should QA people do with the following sentence:

> In the Attached RTF file, it's filled with errors.
What is it supposed to be, which errors, what's the reference ...

What is the meaning of the following description?
> Gutman Adi, and quotation marks makes it once again!

And, sorry to contradict DL, this is not even P2 this is P3 (P2 is for
crashes only!).

=> pls. adict to the following rules:
=====================================
1. IssueZilla is a bugtracking tool that works best with concrete,
step-by-step bug descriptions. 
1.1 In which line is the error
1.2 describe the error
1.3 what is it supposed to be/look like
2. IMPORTANT: NEVER, NEVER REPORT MORE THAN ONE PROBLEM IN ONE ISSUE.
No one can handle such task.
Background: QA and development engineers are working with tasks. Every
task is a job, is an ID one checks in code in CVS etc.
More bug handling guide lines can be found at:
http://www.openoffice.org/bugs/bug_writing_guidelines.html

With the above in mind, pls. take the OOo 1.1 RC2 (when available) and
verify your issues, whether they still occur. If so, pls. file
seperate tasks for each and every problem. Thanks.

As said before pls. verify these issues on a current build and file
new seperate tasks if still reproducible.
Closing issue.