Japanese font overlaps and is not displayed correctly. about console HOT 11 CLOSED

In Console2 or ConsoleZ, rendering or selection use fixed size computation.
In a Unicode fixed size font, each chars in a same same character set seems have the same size. But when multiple character sets are mixed, this assumption is wrong.
Console2 doesn't force the width of each char, but truncate blocks (chars with same colors).
ConsoleZ force the width of each char to guarantee a perfect alignment.

Here a comparison between Console2 (left) and ConsoleZ (right):

You can see chars truncated, wrong alignment and bad selection of the string "employé de magasin".
That's why I fix the rendering.

The font metrics contain average width and max width. The average width is used (max width is really too big).
Japanese chars needs more space to a great display ... so what's size to use? Let the user choose the width?

from console.

I'm using font size "12". ([settings - Appearance - Font].)

from console.

Can you try this version : https://truck.it/p/xtnU0k8bUW
You can configure an extra width added to the fixed width of the font.
Go to Settings/Appearance/Font

from console.

Thank you!
But, the alphabet is also unnaturally wide and it is hard to see it.
I wish to the same display as a "Console Window".

[related Problem]
When the Japanese character is contained in the path, a space enters before a caret. (red line)

1. ConsoleZ Main Window (Extra width "4")
   
2. ConsoleZ Console Window ([View]-[Console Window])
   

[workaround?]
I corrected as follows based on the source code of Console2.
diff: http://pastebin.com/GghztUrz

However, the caret has overlapped with the delimiter(">")...

from console.

ok you use a DBCS code page.
I think I have corrected the DBCS monospace display.
Can you try ? https://truck.it/p/7BX1-2TCNz

DBCS code page 932

SBCS code page 1252

from console.

Thank you for the correspondence.
I think that is displayed correctly most.

[Problem]
a "prolonged sound mark" overlaps and displayed. (red line)
"prolonged sound mark": Cho-On-Pu (Unicode: U+30FC), Wikipedia: http://en.wikipedia.org/wiki/Ch%C5%8Donpu

Main Window (Extra width "0"):

Console Window:

from console.

What is the font of the Console Window ? Raster font ? In this case, try with a true type font.

from console.

At home,
with raster font, DBCS attributes are missing for all chars:

Console Window draws Japanese chars on 2 cells but it does not match the contents of the buffer!

With True Type font, the result is better. But DBCS attributes are missing for some chars (like prolonged sound mark):

Console Window draws this char on 2 cells, but attributes are missing and selection is wrong.
Main Window draws this char on 1 cell and selection is right.

It seems there is a bug in Microsoft console API with DBCS.

from console.

I'm using the TrueType font (MS Gothic) in a console window.

It seems to be difficult if the cause by which a prolonged sound mark is not displayed correctly is a console API bug...
Thank you for your support.

from console.

Hi,

I have successfully used the following workaround under Windows 7 and Windows 8.
Select the true type font and use a size greater than or equal to 20.

disadvantage:
In the console window, the maximum number of rows and columns is limited to the number of displayable characters on the main screen. Therefore, greater the font size is big and the greater the number of row and column is small.

from console.

Thank you for information of the workaround.
I made ​​sure that the problem of "prolonged sound mark" is resolved.

from console.