[opensuse] 13.1 - Thunderbird 38.0.2 - Plain Text Shown in Bold Consolas type Fontface?
All, Opening tbird today I was bewildered why my display of plain-text messages was now *bold*. Additionally, while I set the plain-text font to Dejavu Mono, the font face looks like some MS Consolas?? Looking at the message headers, it seems when the header contains a Content-Type of utf-8, then I get that funky bold plain text font. Specifically, when I see this in the header: Content-Type: text/plain; charset=utf-8; format=flowed On the other hand, when Content-Type is just plain ascii, the message is displayed int the proper Dejavu Mono font. The headers contain: Content-Type: text/plain; charset="us-ascii" The only related setting is: Options-> Display-> Formatting-> Advanced-> Character Encodings-> Outgoing Which for outgoing defaults to UTF-8. However, if I change the outgoing type to match the incoming type of *Western (ISO-8859-1)*, then messages I send (to myself as a test), look normal when viewing them. A day or two ago, I took the zypper lock off of thunderbird, and first updated to the version in the Mozilla:/legacy repo, then when running a normal update, allowed it to update to 38.02 in the update repo. Is anybody else seeing this? It is annoying as ..... Looking, I found complaints at mozilla about windows versions doing this, but this is the first time I've seen it happen on Linux. Anybody else noticed this? If so, any fixes? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin composed on 2015-09-22 22:33 (UTC-0500):
Opening tbird today I was bewildered why my display of plain-text messages was now *bold*. Additionally, while I set the plain-text font to Dejavu Mono, the font face looks like some MS Consolas??
Selecting DejaVu Mono instead of monospace might actually work to disadvantage. DejaVu Mono is the first choice for the generic monospace via fontconfig in more Linux distros than all others combined, including every openSUSE release as far back as I can remember DejaVu existing.
Looking at the message headers, it seems when the header contains a Content-Type of utf-8, then I get that funky bold plain text font. Specifically, when I see this in the header:
Content-Type: text/plain; charset=utf-8; format=flowed
On the other hand, when Content-Type is just plain ascii, the message is displayed int the proper Dejavu Mono font. The headers contain:
Content-Type: text/plain; charset="us-ascii"
The only related setting is:
Options-> Display-> Formatting-> Advanced-> Character Encodings-> Outgoing
Which for outgoing defaults to UTF-8.
However, if I change the outgoing type to match the incoming type of *Western (ISO-8859-1)*, then messages I send (to myself as a test), look normal when viewing them. A day or two ago, I took the zypper lock off of thunderbird, and first updated to the version in the Mozilla:/legacy repo, then when running a normal update, allowed it to update to 38.02 in the update repo.
Is anybody else seeing this? It is annoying as ..... Looking, I found complaints at mozilla about windows versions doing this, but this is the first time I've seen it happen on Linux. Anybody else noticed this? If so, any fixes?
I use SM, not TB, but probably this will get you by: https://support.mozilla.org/en-US/questions/989709 I had same problem in SM years ago, but the font prefs UI in TB is different. FWIW, http://fm.no-ip.com/Auth/Font/fonts-face-samplesM.html and http://fm.no-ip.com/Auth/Font/fonts-comps-linuxmono.html provide ways to compare some common monospace fonts, assuming for any specific font they call for you have it installed. Maybe one of them will help you figure out which font is showing up looking bold and you can remove it. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/22/2015 11:03 PM, Felix Miata wrote:
David C. Rankin composed on 2015-09-22 22:33 (UTC-0500):
Opening tbird today I was bewildered why my display of plain-text messages was now *bold*. Additionally, while I set the plain-text font to Dejavu Mono, the font face looks like some MS Consolas??
Selecting DejaVu Mono instead of monospace might actually work to disadvantage. DejaVu Mono is the first choice for the generic monospace via fontconfig in more Linux distros than all others combined, including every openSUSE release as far back as I can remember DejaVu existing.
Looking at the message headers, it seems when the header contains a Content-Type of utf-8, then I get that funky bold plain text font. Specifically, when I see this in the header:
Content-Type: text/plain; charset=utf-8; format=flowed
On the other hand, when Content-Type is just plain ascii, the message is displayed int the proper Dejavu Mono font. The headers contain:
Content-Type: text/plain; charset="us-ascii"
The only related setting is:
Options-> Display-> Formatting-> Advanced-> Character Encodings-> Outgoing
Which for outgoing defaults to UTF-8.
However, if I change the outgoing type to match the incoming type of *Western (ISO-8859-1)*, then messages I send (to myself as a test), look normal when viewing them. A day or two ago, I took the zypper lock off of thunderbird, and first updated to the version in the Mozilla:/legacy repo, then when running a normal update, allowed it to update to 38.02 in the update repo.
Is anybody else seeing this? It is annoying as ..... Looking, I found complaints at mozilla about windows versions doing this, but this is the first time I've seen it happen on Linux. Anybody else noticed this? If so, any fixes?
I use SM, not TB, but probably this will get you by: https://support.mozilla.org/en-US/questions/989709
I had same problem in SM years ago, but the font prefs UI in TB is different.
FWIW, http://fm.no-ip.com/Auth/Font/fonts-face-samplesM.html and http://fm.no-ip.com/Auth/Font/fonts-comps-linuxmono.html provide ways to compare some common monospace fonts, assuming for any specific font they call for you have it installed. Maybe one of them will help you figure out which font is showing up looking bold and you can remove it.
Thanks Felix! Grr!! I found the problem, I still haven't fixed it. Mozilla gave us this little gift in tbird 38: Font Handling on Linux Linux provides system fonts "sans-serif", "serif" and "monospace". These font names conflict with the generic CSS font family names. Therefore and for compatibility with Thunderbirds on other platforms, the ability to compose messages using these three fonts was removed on Linux. Users who had selected one of these fonts as their default composition font have to select a different font. Instead of "sans-serif", "serif" or "monospace" users should select "Helvetica, Arial", "Times" or "Courier" (or "Fixed Width") respectively. The three aforementioned Linux system fonts can still be used as default display fonts. https://support.mozilla.org/en-US/kb/new-thunderbird-38 Share this article: http://mzl.la/1FjbnZo If I can't get this sorted, I'll drop back to 31. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/23/2015 01:53 PM, David C. Rankin wrote:
Font Handling on Linux
Linux provides system fonts "sans-serif", "serif" and "monospace". These font names conflict with the generic CSS font family names. Therefore and for compatibility with Thunderbirds on other platforms, the ability to compose messages using these three fonts was removed on Linux. Users who had selected one of these fonts as their default composition font have to select a different font. Instead of "sans-serif", "serif" or "monospace" users should select "Helvetica, Arial", "Times" or "Courier" (or "Fixed Width") respectively.
The three aforementioned Linux system fonts can still be used as default display fonts.
You will be unhappy to note that this effects both FF and TB. So if you are wonder why file listings like download.opensuse.org/repositories/... are harder to read because they are displayed in some weird windows mono font -- this is the answer. Wolfgang (oh, mozilla wizard), How in the heck do we tell both FF and TB to display messages and plain-text pages in the font chosen in: Options-> Display-> Formatting-> Advanced-> (our font choice)? It seems no matter what they are set to, if the page, or message, has the *charset=utf-8* included somewhere, then you get the ms default font instead of your chosen font? cc: Mozilla Wizard -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/23/2015 02:02 PM, David C. Rankin wrote:
You will be unhappy to note that this effects both FF and TB. So if you are wonder why file listings like download.opensuse.org/repositories/... are harder to read because they are displayed in some weird windows mono font -- this is the answer.
Wolfgang (oh, mozilla wizard),
How in the heck do we tell both FF and TB to display messages and plain-text pages in the font chosen in:
Options-> Display-> Formatting-> Advanced-> (our font choice)?
It seems no matter what they are set to, if the page, or message, has the *charset=utf-8* included somewhere, then you get the ms default font instead of your chosen font?
cc: Mozilla Wizard
After chasing down a solution to this gift in TB38, the solution isn't that difficult at all. With mozilla no longer honoring the default font faces of 'sans', 'sans-serif' and 'monospace', even though you tell FF or TB to use a specific font (e.g DejaVu Sans Mono), when receiving a page or message with *charset=utf-8*, both FF and TB continue to rely on the system-wide default font. (which makes absolutely no sense whatsoever) Regardless, they can be trained to use the proper font by you setting the system-wide font for 'monospace', etc.. to a specific font. First, check what your system thinks the system-wide font is for that typeface: $ fc-match monospace consola.ttf: "Consolas" "Regular" Yuk! If it is not what you want, then you must set the system-wide default for that typeface in /etc/fonts/local.conf (which is just an empty xml shell for fontconfig by default) Edit the file with your favorite editor and add the following between the <fontconfig> tags. (substitute your chosen font where I have 'DejaVu Sans Mono') <match target="pattern"> <test name="family" qual="any"> <string>monospace</string> </test> <edit binding="strong" mode="prepend" name="family"> <string>DejaVu Sans Mono</string> </edit> </match> Save -- that's it. Not both FF and TB 38 will display the plain-text pages/messages in DejaVu Sans Mono regardless of whether charset=utf-8 or charset=us-ascii <refrain from rant> #%#@$ Works fine :p -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin composed on 2015-09-24 16:54 (UTC-0500):
David C. Rankin wrote:
You will be unhappy to note that this effects both FF and TB. So if you are wonder why file listings like download.opensuse.org/repositories/... are harder to read because they are displayed in some weird windows mono font -- this is the answer.
Wolfgang (oh, mozilla wizard),
How in the heck do we tell both FF and TB to display messages and plain-text pages in the font chosen in:
Options-> Display-> Formatting-> Advanced-> (our font choice)?
It seems no matter what they are set to, if the page, or message, has the *charset=utf-8* included somewhere, then you get the ms default font instead of your chosen font?
cc: Mozilla Wizard
After chasing down a solution to this gift in TB38, the solution isn't that difficult at all.
With mozilla no longer honoring the default font faces of 'sans', 'sans-serif' and 'monospace', even though you tell FF or TB to use a specific font (e.g DejaVu Sans Mono), when receiving a page or message with *charset=utf-8*, both FF and TB continue to rely on the system-wide default font. (which makes absolutely no sense whatsoever)
Regardless, they can be trained to use the proper font by you setting the system-wide font for 'monospace', etc.. to a specific font.
First, check what your system thinks the system-wide font is for that typeface:
$ fc-match monospace consola.ttf: "Consolas" "Regular"
Yuk!
In 13.1, that results from line 129 in /usr/share/fontconfig/conf.avail/58-suse-post-user.conf, which places Consolas at the head of the monospace heirarchy.
If it is not what you want, then you must set the system-wide default for that typeface in /etc/fonts/local.conf (which is just an empty xml shell for fontconfig by default)
"Must" isn't accurate. Fontconfig has multiple routes to the same ends.
Edit the file with your favorite editor and add the following between the <fontconfig> tags. (substitute your chosen font where I have 'DejaVu Sans Mono')
<match target="pattern"> <test name="family" qual="any"> <string>monospace</string> </test> <edit binding="strong" mode="prepend" name="family"> <string>DejaVu Sans Mono</string> </edit> </match>
Save -- that's it. Not both FF and TB 38 will display the plain-text pages/messages in DejaVu Sans Mono regardless of whether charset=utf-8 or charset=us-ascii
Alternatively, make a copy of /usr/share/fontconfig/conf.avail/58-suse-post-user.conf, and sort the heirarchies in the order you'd prefer. http://fm.no-ip.com/Share/57-post-user.conf has the order I prefer, where you can see I knocked Consolas down to #8. That file I put in /etc/fonts/conf.d/. On this particular 13.1 installation, I've symlink'd /etc/fonts/conf.d/57-post-user.conf to both 55-post-user.conf and 58-post-user.conf rather than spending the time to figure out which number its filename ought to start with to achieve the desired system-wide results, which here, is thus: # fc-match monospace DroidSansMono.ttf: "Droid Sans Mono" "Regular" If you have Consolas on your system and load http://fm.no-ip.com/Auth/Font/fonts-face-samplesM.html in a browser you might be able to tell why I don't like it - it's smaller at most nominal sizes than most other monospace fonts. Whether any smaller at a given size, and how much, depends on pt-to-px ratio, which depends on browser engine and DE DPI. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/24/2015 07:34 PM, Felix Miata wrote:
Alternatively, make a copy of /usr/share/fontconfig/conf.avail/58-suse-post-user.conf, and sort the heirarchies in the order you'd prefer. http://fm.no-ip.com/Share/57-post-user.conf has the order I prefer, where you can see I knocked Consolas down to #8. That file I put in/etc/fonts/conf.d/. On this particular 13.1 installation, I've symlink'd /etc/fonts/conf.d/57-post-user.conf to both 55-post-user.conf and 58-post-user.conf rather than spending the time to figure out which number its filename ought to start with to achieve the desired system-wide results, which here, is thus:
# fc-match monospace DroidSansMono.ttf: "Droid Sans Mono" "Regular"
If you have Consolas on your system and load http://fm.no-ip.com/Auth/Font/fonts-face-samplesM.html in a browser you might be able to tell why I don't like it - it's smaller at most nominal sizes than most other monospace fonts. Whether any smaller at a given size, and how much, depends on pt-to-px ratio, which depends on browser engine and DE DPI.
Felix, Correct on all points. Yes, I looked at your fonts-face-samplesM.html (great job), and you understand why I say 'Yuk!' when FF and TB suddenly started showing all utf8 flagged charset plain-text messages in Consolas. My system has no: I do have a /usr/share/fontconfig/conf.avail/57-local-post-user.conf which I suspect is what you are referring to. Yes, it has a much better default ordering. Thanks for pointing that method out. I withdraw the mandatory 'must' and substitute the permissive 'may' in its place :p The only reason I gravitated to /etc/fonts/local.conf (aside from it being the first solution tested), it also has the heading: <!-- /etc/fonts/local.conf file for local customizations --> Thanks! -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
David C. Rankin -
Felix Miata