2.4 log font

[rejetto]

hi guys, i noticed that with unicode in 2.4 there is a new problem.
The font is set as tahoma, but when a japanese character appears, the font is changed.
I copied the text to a word processor (Writer) and it seems that the new font is 'simsun'.
It's bad because tahoma can show those characters, so the change is unnecessary and ugly.
I don't know how to stop this madness.
Let me know if you find a solution, thanks.

[SilentPliz]

It's strange, here (Windows 2007), with the Japanese characters in the log, if I right click in the window log > font... Tahoma is displayed correctly, in size 12 and Normal.
If I copy the Tahoma Japanese text from the log, and paste it in 'Ms Writer', it tells me 'MS Gothic'.

Otherwise, the display did not seem particularly ugly to me, it must depend on the resolution of the screen (1366*768 here).
However reducing the display in the log to Tahoma size 11 and passing it to Bold seemed prettier ... But it's subjective, I think.

[NaitLee]

The font problem already exists in non-Unicode versions like 2.3m.

It seems that this should not be considered as a true problem, since actually Tahoma does not support Japanese(have a view in Character Map, search it beside Start Menu), and HFS needs to switch fonts to correctly show file names.

Now the problem is: How to switch the font back after chunk of Unicode characters in filenames.
  (log type strings are not affected, according to the log's behavior with the new Chinese translation file.)

Another Unicode problem bro

Hints:
  (N)SimSun ((新)宋体) are ancient serif fonts that support most East Asian characters. But they're pixelified when texts are small.
  MS (P)Gothic is for Korean(Japanese), they are sans-serif, but old too.