Closed
      
        Bug 253533
      
      
        Opened 21 years ago
          Closed 20 years ago
      
        
    
  
Three entries for Thai fonts in fontEncoding.properties file have to be commented out for xft+gtk2 build  
    Categories
(Core Graveyard :: GFX: Gtk, defect)
Tracking
(Not tracked)
        RESOLVED
        FIXED
        
    
  
People
(Reporter: jshin1987, Assigned: jshin1987)
References
()
Details
(Keywords: intl)
Attachments
(1 file)
| 
        
        
         1.60 KB,
          patch         
       | 
      
           smontagu
 :
              
              review+
          roc
 :
              
              superreview+
          chofmann
 :
              
              approval-aviary1.1a2+
           | 
      Details | Diff | Splinter Review | 
fontEncoding.properties file has the following three lines:
encoding.norasi.ttf = x-thaittf-0.wide
encoding.garuda.ttf = x-thaittf-0.wide
encoding.dbthaitext.ttf = x-thaittf-0.wide
In gtk2 + xft build, we don't enable CTL so that 'x-thaittf-0' encoder is not
available. When one of three fonts are specified, it's not used because Mozilla
can't get the encoder for x-thaittf-0 (and thus its coverage is NOT known to
Gfx)  and as a result FindFont('a') fails. 
Therefore, we have to comment three lines above out
| Assignee | ||
          Comment 1•21 years ago
           
         | 
      ||
comment out three entries
| Assignee | ||
          Comment 2•21 years ago
           
         | 
      ||
Below is a part of the email I got from Thep:
-----------
The fonts used in the page are available at linux.thai.net CVS:
  cvs -d :pserver:anonymous@linux.thai.net:/home/cvs \
      co software/thaifonts-scalable
and are built with usual "configure; make; make install" process
With these fonts, I have provided some screenshots (of the page in the URL field
above) from my machine:
   http://linux.thai.net/~thep/tmp/fonttest/img/myshot1.png
   http://linux.thai.net/~thep/tmp/fonttest/img/myshot1.png
Note that not all fonts are actually selected as expected. Failed fonts
are Norasi, Garuda, and DBThaiText.
------------
Thep, as I mentioned in my email, you may want to apply my patch for bug 215219
for a better Thai rendering.  
Status: NEW → ASSIGNED
          Comment 3•20 years ago
           
         | 
      ||
How is this going on? I have to say this bug has caused a major bug for Thai in
most non-local distros, such as Debian, where the only Thai fonts typically
installed are those prohibited by this bug.
Most Thai local distros have to apply this patch. That unfortunately blind most
Thai users from this problem in upstream source, however.
| Assignee | ||
          Comment 4•20 years ago
           
         | 
      ||
Comment on attachment 154646 [details] [diff] [review]
patch
sorry for the delay. let's comment them out
        Attachment #154646 -
        Flags: superreview?(roc)
        Attachment #154646 -
        Flags: review?(smontagu)
          Updated•20 years ago
           
         | 
      
        Attachment #154646 -
        Flags: review?(smontagu) → review+
        Attachment #154646 -
        Flags: superreview?(roc) → superreview+
| Assignee | ||
          Comment 5•20 years ago
           
         | 
      ||
Comment on attachment 154646 [details] [diff] [review]
patch
asking for a to trunk. 
This only affects Thai rendering on Linux and has proven to work well (Thai
Linux community has applied this patch for a while every time a new release is
made)
        Attachment #154646 -
        Flags: approval-aviary1.1a2?
          Comment 6•20 years ago
           
         | 
      ||
Comment on attachment 154646 [details] [diff] [review]
patch
a=chofmann
        Attachment #154646 -
        Flags: approval-aviary1.1a2? → approval-aviary1.1a2+
| Assignee | ||
          Comment 7•20 years ago
           
         | 
      ||
landed on the trunk
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
          Updated•16 years ago
           
         | 
      
Product: Core → Core Graveyard
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•