On 2024-03-19 09:09, Andrei Borzenkov wrote:
...
[CER] == "Carlos E. R." <...> has written:
...
CER> I just solved an issue I had in Thunderbird with your messages. Thunderbird CER> displayed them with a strange font that made reading them CER> harder. I'm writing this OT to the thread info so others that CER> have that issue see it.
I think that's a good idea.
CER> Thunderbird, Settings, General section, Fonts & Colours. Here I CER> have "default font" Dejavu Sans, size 15. Then click on Advanced.
CER> The settings for "Latin" are, and were:
CER> Proportional: Sans Serif size 15 CER> Serif: Dejavu Serif CER> Sans-serif: Dejavu Sans CER> Monospace: Dejavu Sans Mono 13
As long as we are off topic anyway - anyone knows when TB actually uses monospace font? Is it possible to configure TB to display all messages using monospace?
It displays monospace if the mail is plain text for me, not if it is html. The setting is in the same "Fonts $ Colors" zone, button "advanced": Font Control [X] Allow messages to use other fonts [X] Use fixed width font for plain text messages
CER> The trick is selecting for Japanese the same set.
The problem is that Sans-serif is a generic name which may resolve to different fonts for different encodings. Again - anyone knows a good universal font covering most of the UNICODE?
Probably the Dejavu one, but I'm not certain.
Arguably, it is a bug of the mail client. As long as the message does not contain Japanese characters, it should *NOT* mark this message as having Japanese encoding.
But it does. Content-Type: text/plain; charset=ISO-2022-JP Thunderbird has to abide by that.
I had different (I did not CER> record what). I don't know a way to select the same fonts for CER> all languages in a single operation.
In Japan, the Noto Sans and Noto Serif fonts, created in cooperation between Google and Adobe, seem to be well received.
I guess I should look at it, not sure what is used as default right now.
I don't know how, but each of the languages seem to have a different choice; but this is an old TB profile I have.
To us Japanese, Japanese is an ordinary language, but in the computer world, it is a special language, and this continues to create no small problems in various information systems.......
Best Regards.
Computers are a western invention. The IBM PC only contemplated USA ASCII initially. It also caused problems in Europe, apparently all of our languages have a few letters not included in the USA ASCI char set (initially 7 bits).
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp
Ah, OK, so the message does contain Japanese characters. Maybe signature can be reconsidered taking in account the wider audience of this list.
He could just set UTF-8. My own email in reply here is: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 No idea why TB resorts to base64, that is not needed and can cause problems for/with some people. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)