Closed Bug 278255 Opened 20 years ago Closed 18 years ago

Chinese button text does not show up

Categories

(Camino Graveyard :: Page Layout, defect)

Product:
Camino Graveyard
Component:
Page Layout
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 175651
Milestone:
Camino1.5

People

(Reporter: yhlien2004, Unassigned)

References

(
URL
)

Details

Attachments

(2 files)

Login boxes in Cm and Fx
(deleted), image/jpeg
Details
Button with missing text in google.com.hk
(deleted), image/jpeg
Details 
The button on the right of page does not show the chinese button text. The page
source does not normally display. Some text of the content overlay on others.
does it look the same in firefox?
Attached image Login boxes in Cm and Fx (deleted) — 
You mean the "login" button, right?  If so, the issue "seems" to be that the
button is being drawn too small for Camino to place text in it.  See comparison
screenshot.

As an aside, that page's HTML is a mess.  Whether that affects the "View
source" issue or not, I don't know; the view source issue is really a separate
bug, anyway.
(In reply to comment #2)

Yes, that is what I mean. The right portion of the attachment shows the expected
result but Camino renders the content as the left portion.
Well, I found Camino seemed failed to show page source if the line contained
both chinese characters and HTML tags. For example, page source of the site
http://www.oikos.com.tw/modules/news/ displayed inproperly if HTML tags and
chinese characters coexist in the same line. On the other hand, other portions
which containd chinese characters are just right.
OK, confirming the button text part for the devs to look at.

Please open a separate bug for the view source part.  Editing summary to get
back to one issue per bug report.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Chinese button text does not show up and viewing page source displays abnormal → Chinese button text does not show up
This bug seems gone in 2005012708 build.
I thought this bug was only partially solved. The chinese characters displayed
normally in the mentioned site but failed in another site
http://www.ee.tku.edu.tw/~rexchen/cdict/cdict.html.
Severity: normal → major
I found something more about this bug. If I pressed reset button in Preferences
-> Appearance -> Fonts -> Traditional Chinese and restart (quit and relaunch)
Camino, the Chinese characters would be displayed properly. If other TC fonts
were chosen, the Chinese characters would not work. However, the default fonts
for TC encoding were not available in standard OS X installation and always
shown as missing.
(In reply to comment #8)
> If other TC fonts
> were chosen, the Chinese characters would not work. However, the default fonts
> for TC encoding were not available in standard OS X installation and always
> shown as missing.

See bug 175651 comment 14...but basically, the true situation is reversed from
what it appears..."missing" fonts are present (at least for CJK) and
user-selected fonts are in fact missing (to Gecko, which is what matters).

This bug probably depends on bug 175651 then.
Setting: Camino 0.8.2
Mac OS X 10.3.8
eMac 1.25GHz

Why I launch google.com.hk, it is rather strange that the button "Google搜尋"
can be display flawlessly. However, the button "好手氣" presented with no text.
Firefox can display both of them with no problem.

    
    

    
  
Google button can now be display in nightly build
2005032305

(In reply to comment #11)
> Created an attachment (id=178445) [edit]
> Button with missing text in google.com.hk
> 



    
    

    
  
(In reply to comment #12)
> Google button can now be display in nightly build
> 2005032305
> 

Have you ever checked the font panel for your font setting? Did it show the font
names ending with (missing) for your encoding? The problem for tradition Chinese
encoding persists in all 0.8+
builds, which includes 2003032308, I have tested.

    
    

    
  
In my case, only Proportional (serif) showed up as missing. But ti can display google.com.hk properly
2005032808

> Have you ever checked the font panel for your font setting? Did it show the font
> names ending with (missing) for your encoding? The problem for tradition Chinese
> encoding persists in all 0.8+
> builds, which includes 2003032308, I have tested.



    
    

    
  
You may try to reset the font panel setting. Both of the font names should end
with (missing). However, the text within the button will show properly in most
cases.

(In reply to comment #14)
> In my case, only Proportional (serif) showed up as missing. But ti can display
google.com.hk properly
> 2005032808
> 

    
    

    
  
*** Bug 275949 has been marked as a duplicate of this bug. ***

    
    

    
  
The bug I just duped to this was targetted for 0.9 while it was UNCO, so I'm
pulling the ? flag here.

I (in my limited understanding) do think this issue would go away if the
Carbon-Cocoa miscommunication in the font prefs were fixed (although there may
be further issues once that is fixed), so adding dependency on bug 175651, too.
Depends on: 175651
Flags: camino0.9?

    
  
Flags: camino0.9? → camino0.9+
Target Milestone: --- → Camino0.9

    
    

    
  
I don't see any problems when I look at the two testcases. Maybe it depends what
fonts you are using? Can someone hack up a testcase?

    
    

    
  
Simon: see comment 8 and comment 9.  

You won't see this if you've left your Chinese fonts to the default values (the
ones Camino erroneously thinks are "missing"--bug 175651), but if you've changed
your fonts to get rid of the "missing" ones--then Gecko doesn't recognize the
Cocoa font names--the bug appears.

IIUC, fixing bug 175651 should fix this, and that's why I asked for camino0.9 on
bug 175651. :-)
Target Milestone: Camino0.9 → Camino1.0

    
    

    
  
Requesting blocking for this bug simply because it had blocking for Camino 0.9.
Flags: camino1.0?

    
    

    
  
This depends on bug 175651, so it will either be fixed if smfr fixes bug 175651, or it won't.  

At some point between this getting blocking for 0.9 and 0.9a2, we discovered this behavior was a symptom of the problem in bug 175651 (which was minused for 1.0, btw).

    
    

    
  
Since the bug this depends on was minused for 1.0, pushing this off as well.
Flags: camino1.0? → camino1.0-
Target Milestone: Camino1.0 → Camino1.1
Assignee: mikepinkerton → nobody
QA Contact: page.layout

    
    

    
  
If this is purely a symptom of bug 175651, there's no reason to track it separately.

*** This bug has been marked as a duplicate of 175651 ***
Status: NEW → RESOLVED
Closed: 18 years ago
No longer depends on: 175651
Resolution: --- → DUPLICATE

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






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: