Closed Bug 309853 Opened 19 years ago Closed 9 years ago

tamil unicode characters are not rendered correctly without pango enabled

Categories

(Core :: Internationalization, defect)

Product:
Core
Component:
Internationalization
Version:
1.0 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: svasudevan, Assigned: smontagu)

References

(
URL
)

Details

(Keywords: regression, testcase)

Attachments

(1 file)

Reporter's testcase from comment 3
245 bytes, text/html
Details 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920 Firefox/1.0.7

Hi,
This defect is probably same as 292429. However, I thought I can provide some
useful information by filing a new defect. Sorry if this is too much!

Ok, until firefox version 1.0.6, the tamil unicode characters were properly
rendered on my linux(fedora core 4) box. However, looks like something in this
area has changed in 1.0.7 (& in 1.5b1). Now the individual characters are
displayed correctly, but not when two unicode 'codes' need to be combined
together to form a single tamil character.

Hopefully, the above URL can show what I am talking about. Otherwise, I think I
can come up with a small test case.

Reproducible: Always

Steps to Reproduce:
1.Please see the above URL in firefox 1.0.7 or firefox 1.5b1
2.
3.

Actual Results:  
Home » forums » Tamil.net
அடிக்கடி கேட்கப்படும் கேள்விகள்

Expected Results:  
Please load the above url in 1.0.6 & look for the first tamil line (which is
immediately after,
Home » forums » Tamil.net.

[ I am not able to cut & paste the correctly rendered tamil text here as I am
filing the defect using 1.0.7. ]


I have tagged this defect as Major as I couldn't see lot of tamil sites.
Mats, the reporter says this is a regression between 1.0.6 and 1.0.7, and it
could be a regression from bug 296134.
Flags: blocking-aviary1.0.8?
Keywords: regression
My debug build does not reach StripZeroWidthJoinControls() for that URL...
do I need a specific font for arabic shaping to kick in?

Reporter, could you please test the following two builds and tell me if they
work or not:
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2005-08-30-11-trunk/seamonkey-1.1a.en-US.linux-i686.tar.gz

http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2005-09-01-09-trunk/seamonkey-1.1a.en-US.linux-i686.tar.gz

I tried the builds & both of them don't display tamil characters correctly.

I thought I can supply a small testcase:

[--------testcase start----------]
<html>
<head>
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
        <title>tamil unicode testcase</title>
</head>
&#2974;&#3015;
<br>&#2974;&#3016;
<br>&#2974;&#3020;
<br>&#2974;&#3007;
<br>&#2974;&#3008;
</html>
[-----------testcase end---------------]

If the above html is loaded in firefox 1.0.6 & any later releases, one will be
able to see the difference. 

For eg, in the html above, '&#2974;&#3015;' gets rendered in 1.0.6 as
'&#3015;&#2974;' as this represents the meaningful character, but the later
versions renders as it is - '&#2974;&#3015;'. 

In this case, it is not a big deal to just enter the 'unicode' in this order
itself. However, it works until 1.0.6 AND there are other problems as well. For
eg, the code '&#2974;&#3007;' should result in displaying the character for
'&#3007;' on top of the character for '&#2974;'. Again, it happens on 1.0.6, but
  not in later releases.

As for the tamil fonts not getting displayed correctly, I have the following 2
tamil font rpms on my box here:

fonts-tamil-1.10-2
kde-i18n-Tamil-3.4.2-0.fc4.1
(In reply to comment #3)
> I tried the builds & both of them don't display tamil characters correctly.

Thanks, bug 296134 didn't cause it then.

  

  


Assignee: nobody → smontagu
Component: General → Internationalization
Product: Firefox → Core
QA Contact: general → amyy
Version: unspecified → 1.0 Branch
Keywords: testcase

    
    

    
  
This can't be a dupe of bug 292429 if this regressed between 1.0.6 and 1.0.7 -- bug 292429 was written against 1.0.3. It was also written on windows and on windows I see the same rendering for the attached testcase in IE6 and Firefox 1.0.2, 1.0.7 and 1.5

Can anyone confirm the bug and that it is a regression? Hard to say it would block anything without those basics.

  

  



    
    

    
  
reporter, what do you get if you enter 'about:buildconfig' in the addressbar? 

Mozilla.org's build of firefox (gtk2 + xft) does not render Tamil correctly because my patch for that is not checked in (see bug 215219). However, Fedora Core has a firefox binary built with 'pango' (gtk2 + pango : bug 214715) that does support Tamil well. I suspect firefox 1.0.6 you tried was built with pango while firefox 1.0.7 you tried was built without pango. 



  

  



    
    

    
  
I have tried firefox 1.0.1.
The same problem exist.
So I believe this is not a regression from 1.0.6.
The reporter's firefox 1.0.6 works well because pango was enabled.
(In reply to comment #7)
> reporter, what do you get if you enter 'about:buildconfig' in the addressbar? 
> 
> Mozilla.org's build of firefox (gtk2 + xft) does not render Tamil correctly
> because my patch for that is not checked in (see bug 215219). However, Fedora
> Core has a firefox binary built with 'pango' (gtk2 + pango : bug 214715) that
> does support Tamil well. I suspect firefox 1.0.6 you tried was built with pango
> while firefox 1.0.7 you tried was built without pango. 
> 

  

  


Flags: blocking-aviary1.0.8? → blocking-aviary1.0.8-

    
    

    
  
You are absolutely right! The 1.0.6 version had pango enabled, but not in any later releases. I have attached the buildconfigs below.

So, what would you recommend w.r.t this defect? Is there some reason why pango is no longer enabled by default? 

Thanks so much for your time.
--

buildconfig for 1.0.6:
---------------------
--disable-ldap --disable-mailnews --enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,gnomevfs,negotiateauth --enable-crypto --disable-composer --enable-single-profile --disable-profilesharing --with-system-jpeg --with-system-zlib --with-system-png --with-pthreads --disable-tests --disable-debug --disable-installer '--enable-optimize=-Os -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables' --enable-xft --enable-xinerama --enable-default-toolkit=gtk2 --enable-official-branding --disable-xprint --disable-strip --enable-pango

buildconfig for 1.0.7:
---------------------
--disable-ldap --disable-mailnews --enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,gnomevfs,negotiateauth --enable-crypto --disable-composer --enable-single-profile --disable-profilesharing --disable-debug '--enable-optimize=-Os -freorder-blocks -fno-reorder-functions -gstabs+' --disable-tests --enable-official-branding --enable-default-toolkit=gtk2 --enable-xft --disable-freetype2 --enable-static --disable-shared

(In reply to comment #7)
> reporter, what do you get if you enter 'about:buildconfig' in the addressbar? 
> 
> Mozilla.org's build of firefox (gtk2 + xft) does not render Tamil correctly
> because my patch for that is not checked in (see bug 215219). However, Fedora
> Core has a firefox binary built with 'pango' (gtk2 + pango : bug 214715) that
> does support Tamil well. I suspect firefox 1.0.6 you tried was built with pango
> while firefox 1.0.7 you tried was built without pango. 
> 

  

  



    
    

    
  
(In reply to comment #9)
> You are absolutely right! The 1.0.6 version had pango enabled, but not in any
> later releases. I have attached the buildconfigs below.
> 
> So, what would you recommend w.r.t this defect? Is there some reason why pango
> is no longer enabled by default? 

It has never been enabled by default in any of mozilla.org's build (afaik). Your 1.0.6 was built by RedHat which has enabled Pango for a while. Why it's not enabled by default probably because enabling Pango leads Mathml rendering not to work UNLESS you installed a relatively new version of Pango (which does what our rendering used to do on its own for Mathml rendering) on your system. (I guess on Fedora Core3 and later and other recent distributions of linux should be Ok with that). 

What can you do? You can build a pango-enabled version of 1.0.7 and contributed it so that it can be hosted in the contributed build directory of mozilla.org

  

  


QA Contact: amyy → i18n

    
    

    
  
tested on:48.0a1 Build ID 20160328030215User Agent 	Mozilla/5.0 (X11; Linux i686; rv:48.0) Gecko/20100101 Firefox/48.0 Ubuntu 14.04x32

Hello Daniel, can you give me a hint on what should we do next with this issue? After passing through the comments and several tamils sites, given the fact I can't confirm that this issue is still actual on a Nightly official build(48) and the fact that the bug is so old, I would incline for a WFM resolution.

  

  


Flags: needinfo?(dveditz)

    
    

    
  
Sure. We've had several big changes in our font rendering code in the last decade that even if we are still doing this wrong it will be for a completely different reason and we ought to file new bugs.

  

  


Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(dveditz)
Resolution: --- → WORKSFORME
Summary: tamil unicode characters are not rendered correctly from firefox version 1.0.7 → tamil unicode characters are not rendered correctly without pango enabled

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: