User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:126.96.36.199) Gecko/20060426 Firefox/188.8.131.52 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:184.108.40.206) Gecko/20060426 Firefox/220.127.116.11 if I choose "Palatino" and "Optima" as fonts (I have them), the text gets jammed and words overlap. Reproducible: Always
Reporter, please take a look at mozilla's bug writing guidelines. Can you provide an example URL/reduced test case?
... do you mean a pair of images showing the problem? The problem occurs systematically, so anyone can bump into it.
(In reply to comment #2) > ... do you mean a pair of images showing the problem? The problem occurs > systematically, so anyone can bump into it. > You left to URL field blank in your report. Can you point us to a page where the problem occurs? It is not smart [or feasible] if all of us have to go out searching the internet for a www page with "Optima" as font to reproduce your problem.
No, no. You are on the wrong track. There is no need to seek for one such site. Optima and Palatino cannot be found on websites; they are local fonts on your machine, that you set as default for the non-proportional and proportional font respectively. It does not matter the site, as TB replaces the original font with your specified local font. So, there is no need to seek for a specific site, as any site will do. However, to replicate the problem you do need to have the original Adobe font installed. Optima and Palatino are just an example; I think you can replicate the bug with any professional font other than Times.
I am sorry, there are many things affecting rendering of text. We DO need a [reduced] test case. You say it happens on any site so you should be able to provide us with an URL :) Moreover, your comment 4 adds crucual information not present in your initial bug report. Once more I would like to ask you to read the bug writing guidelines http://www.mozilla.org/quality/bug-writing-guidelines.html and provide us with enough information for us to reproduce this behavior. Otherwise this bug will be closed as WFM "All attempts at reproducing this bug were futile, and reading the code produces no clues as to why the described behavior would occur. If more information appears later, the bug can be reopened."
OK, 1. install Adobe Palatino and Optima in your OSX machine 2. open TB 3. point its RSS reader to your favorite subscription 4. change the preferences of TB so that Palatino is the default proportional font 5. " so that Optima is the default non-proportional font 6. read the RSS feed and you will see that the areas around boldface text slightly overlap with the roman text. Sometimes you even get whole lines overlapped. This occurs systematically, and you will have no problem replicating the error, provided you have the above mentioned professional fonts installed.
I'm sorry your description is still lacking. In TB you can only choose between serif or sans serif for the Proportional font. And THEN you can specify your serif and sans serif fonts in more detail. Please report properly the settings you have in your fonts panel. Thank you.
Thunderbird -> Preferences -> Display -> Fonts, click on "Fonts...", Fonts for: Western Proportional: Serif, size 14 Serif: Palatino Sans-serif: Optima Monospace: Optima, size 13 Display resolution 96dpi minimum font size: 10 allow messages to use other fonts: no -- I observe that the most recent feeds display correctly. I kept using my other reader, Vienna, so I am unable to post an image of a bugged page at this time.
Correction! If you set the minimum font size to 13, and point your rss to the following blog, you will observe the problem. http://www.beppegrillo.it/english.php Depending on the font size, the bold/underlined text overlaps with the roman.
Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 18.104.22.168)
RESO INCO per lack of response to last comment. If you feel this change was made in error, please respond to this bug with your reasons why.