Last modified: 2014-03-01 13:51:57 UTC
Certain glyphs dont render properly in few places and it occurs randomly.(See attachement) Fonts are not an issue. Most of us who tested across browsers, OS have tamil fonts and a good number of them. This issue is reproducible only on wikimedia sites. Ravi noticed this rendering bug in the search box on Ubuntu 11.10 and FF8 Bala noticed this rendering bug in the search box on Win XP SP3 and FF5,IE7 I notice this rendering bug in the RecentChanges page on Ubuntu 11.10 and Chrome 16
Created attachment 9734 [details] screenshot of recent changes page
Created attachment 9735 [details] screenshot of search box dropdown list (FF5, XP SP2)
this appears to be working for me now. Could you give me the the key sequence necessary to produce a transliterated sequence that produces the screenshot in attachment 9735 [details] ?
I am still getting the broken glyphs. The letters seen in attachment 9735 [details] are ”குவ” (can be reproduced in transliteration typing scheme by keystrokes kuva). Occurs with Narayam input scheme or external input scheme or just copypasting the text
(In reply to comment #3) > this appears to be working for me now. Could you give me the the key sequence > necessary to produce a transliterated sequence that produces the screenshot in > attachment 9735 [details] ? I can confirm this as a bug in search suggestions. To produce - In ta.wiki, select inputmethod as Tamil99, in search box, type k , You will get ம, and suggestions. Here is the code for the first suggestion. <div class="suggestions-result suggestions-result-current" rel="0" title="மீட்டர்"> <span style="white-space: nowrap;"><span class="highlight">ம</span>ீட்டர்</span> </div> To highlight ம, there is a span surrounding it, but the 'ee' vowel sign is outside span. For Indic languages, vowel signs cannot exist independently. And this causes the search suggestion item appears as wrongly rendered. The solution is not straightforward - if we want to highlight the type letter, the span should be applied to the glyph cluster and not to the letter alone. I am not sure if there is any easy way to do this. Browser are aware of these rules anyway, try moving cursor over "மீட்டர்" step by step. You cannot place your cursor between ம and ீ . The problem is not limited to Tamil anyway. I am changing the bug summary.
Ah, i identified the issue in attachment 9734 [details], its something to do with font not having italic glyph. Not sure if something can be done here. Ideally must be reported to a (inactive) upstream since that font is a ASCII font.
(In reply to comment #0) > I notice this rendering bug in the RecentChanges page on Ubuntu 11.10 and > Chrome 16 I can confirm this in my Chromium 15, Debian(Unstable). As far as I can tell, this is a rendering bug in chrome/chromium and need to be reported upstream(http://code.google.com/p/chromium/issues). And need a separate bug report here since rendering issue in search suggestion and this are two different issues.
*** Bug 33548 has been marked as a duplicate of this bug. ***
*** Bug 40300 has been marked as a duplicate of this bug. ***
this is not essential for Wikidata but willing to take this bug as a volunteer to fix on the weekend :)
Created attachment 11130 [details] a simple example of different stlings applied to Tamil cluster parts This is general rendering problem. The behavior in Firefox is slightly less broken - in the row with the colored span it colors the whole cluster, whereas Chromium breaks it. But I'm not sure what is actually correct according to the HTML and Unicode standards.
Do we really need this bold font styling in the first place? If we just remove it, it will fix this bug, and nobody will complain. It will probably fix Bug 26665, too.
As a workaround, I suggest a language blacklist for which autosuggestions does not use highlighting. This can include any language that uses an Arabic script, Tamil and others. (which ones?)
All RTL languages, to fix (In reply to comment #13) > As a workaround, I suggest a language blacklist for which autosuggestions does > not use highlighting. This can include any language that uses an Arabic > script, Tamil and others. (which ones?) All RTL languages, to fix Bug 26665.
(In reply to Aude from comment #13) > As a workaround, I suggest a language blacklist for which autosuggestions > does not use highlighting. This can include any language that uses an > Arabic script, Tamil and others. (which ones?) Any language written in devanagari, and I suspect all other Indic scripts too.
