I must not have been clear: I have not encountered a BIDI (bidirectional, for the uninitiated) problem; the page in question displayed in the correct direction. The only problem was with the assembly of character + diacritic into one visual entity, i.e. into one character space. If that is still not clear, I would be happy to clarify further by email, not to clutter up the NG unnecessarily.
But yes, if Mozilla can't do the same bidirectinal manipulations that Netscape knows how to do, then that needs to be addressed. There are a lot of people in the world that write from right to left, and there are plenty of Websites that use their languages. On Tue, 30 Oct 2001 13:34:09, Michael Kaply <[EMAIL PROTECTED]> opined: > I wasn't thinking. I believe there is a solution to this. > > There are really two issues here and one is probably fixable but I haven't had the > time to do the right stuff on Os/2. > > The Bidi support in Mozilla can order be done by the OS or by Mozilla. > > Currently OS/2 is using the Mozilla support even though it has OS/2 has better Bidi > than Windows. This is mainly because I haven't had the time to do anything about it. > > I'll put this on our growing list of things to do. > > Mike Kaply > IBM > > Stan Goodman wrote: > > > That's very interesting. > > > > On the same page on which the Hebrew problem appears, there is also > > some French text, with properly placed accents. I assume that this is > > because the author used "packaged" characters already containing the > > accents, so that they didn't have to be assembled. > > > > But in all the years that I have been using OS/2, I have never > > observed a case in which diacritics were not properly combined with > > the characters on which they were inteded to operate. My conclusion is > > that OS/2 relies on applications to do this assembly, whereas Windows > > does it in the operating system; simply a different design decision. > > > > I do not think it is an adequate response to dismiss the problem as > > being one for the operating system. The OS is a given, and Mozilla is > > supposed to work with it, not the other way around. We are not going > > to induce a change in any operating system because Mozilla doesn't > > deal with this problem or that. > > > > As long as this problem was thought to be one of Hebrew rendering, it > > was possible to regard it as peripheral: Hebrew is, after all, not a > > world language; and anyway, vowel points are rarely used, except for > > poetry and Biblical text. But French and German certainly are world > > languages, as is Arabic (which has the same need for vowel-point > > diacritics as Hebrew, and uses them more extensively), and their > > writing systems ought to be supported. > > > > On Tue, 30 Oct 2001 03:48:32, Michael Kaply <[EMAIL PROTECTED]> > > opined: > > > > > That would be an operating system issue than. Mozilla does not have code to do > > > the combining. > > > > > > Mike Kaply > > > IBM > > > > > > Henry Sobotka wrote: > > > > > > > Michael Kaply wrote: > > > > > > > > > > We haven't really tested the Hebrew support on Os/2 yet. There is probably > > > > > a lot we could do, but we haven't. > > > > > > > > Not just a Hebrew problem. All the Unicode combining characters display > > > > separately, e.g. A&x308; produces capital A followed by an umlaut, > > > > instead of putting the umlaut on the A. > > > > > > > > h~ > > > > > > > -- > > Stan Goodman > > Qiryat Tiv'on > > Israel > > > > E-mail sent to [EMAIL PROTECTED] will, of course, not reach me. Sorry. > > Send E-mail to: domain: hashkedim dot com, username: stan. > -- Stan Goodman Qiryat Tiv'on Israel E-mail sent to [EMAIL PROTECTED] will, of course, not reach me. Sorry. Send E-mail to: domain: hashkedim dot com, username: stan.
