[Indic]Rendering for some character broken unexpectedly (word-splitting code broken??)

NEW
Assigned to

Status

Other Applications
ChatZilla
10 years ago
9 years ago

People

(Reporter: A S Alam, Assigned: Robert Ginda)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

10 years ago
most of time it is working fine for language, but suddenly it break rendering. if same word I use in next line, then it works fine. Attaching screenshot for it

---
unicode text for input=मिलेंगे
---
Version
chatzilla-0.9.83.xpi
I don't see the screenshot, and right now I cannot understand this bugreport. Reporter, could you add some more information?
(Reporter)

Comment 2

10 years ago
Created attachment 336783 [details]
Screenshot

Sorry, forgot to attach it, it is now there
Uh, so, this is unlikely to be ChatZilla's fault... Can you please leave information about your Firefox/SeaMonkey version, and check if there are newer versions available with which things might fare better?
OK, so actually it may still be our fault. We split lines into spans so as to facilitate line breaking that doesn't suck. The weird characters are apparently "glue" characters that get thrown up if we break a word inbetween two specific characters.

In order to tell exactly what's going wrong here, we would need the HTML of the view where such a problem occurs. Reporter, could you please reproduce this bug in a view, and then use the "Save View As..." menuitem in the ChatZilla item to save the HTML for it, and attach that HTML file to the bug? Thanks!
Summary: [Indic]Rendering for some character broken unexpectedly → [Indic]Rendering for some character broken (word-splitting code broken??)

Updated

10 years ago
Summary: [Indic]Rendering for some character broken (word-splitting code broken??) → [Indic]Rendering for some character broken unexpectedly

Updated

10 years ago
Summary: [Indic]Rendering for some character broken unexpectedly → [Indic]Rendering for some character broken unexpectedly (word-splitting code broken??)
Created attachment 341902 [details]
Testcase

FWIW, I can reproduce this on Linux, but not on Mac. Can someone try on win32? This document shows signs of breakage in my Ubuntu VM, similar to those in the reporter's screenshot, but everything looks OK on mac...

Comment 6

10 years ago
I can reproduce the buggy display on xp and linux, both on 3.0.x. Mac is fine for me, too.

I have no idea which of the two is right, but the placement of the wbr's is surely unfortunate. Simon, got an idea?
The rendering on Mac is broken too, it's just harder to spot because ATSUI doesn't insert the dotted circles in the display like Uniscribe and Pango do.

(In reply to comment #4)
> OK, so actually it may still be our fault. We split lines into spans so as to
> facilitate line breaking that doesn't suck. The weird characters are apparently
> "glue" characters that get thrown up if we break a word inbetween two specific
> characters.

The hard way to fix this would be to make your breaking algorithm aware of clusters and only insert the <wbr>s at cluster boundaries. I don't know if we have an API that is callable from JS and can do that. On trunk at least, it should be much easier to use word-wrap: break-word, or maybe roc has a better suggestion.
(In reply to comment #7)
> The rendering on Mac is broken too, it's just harder to spot because ATSUI
> doesn't insert the dotted circles in the display like Uniscribe and Pango do.
> 
> (In reply to comment #4)
> > OK, so actually it may still be our fault. We split lines into spans so as to
> > facilitate line breaking that doesn't suck. The weird characters are apparently
> > "glue" characters that get thrown up if we break a word inbetween two specific
> > characters.
> 
> The hard way to fix this would be to make your breaking algorithm aware of
> clusters and only insert the <wbr>s at cluster boundaries. I don't know if we
> have an API that is callable from JS and can do that. On trunk at least, it
> should be much easier to use word-wrap: break-word, or maybe roc has a better
> suggestion.

I'm assuming that the word-wrap property would be set on the <td> with the text we want wrapped: does that care about all the other random html things we do inside that td? spans with colours/bold/italics etc?

Updated

9 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.