Monospacing broken by Chinese character

[actboy168]

• VSCode Version: Code - Insiders 1.7.0-insider (9d47285, 2016-10-27T06:11:25.272Z)
• OS Version: Windows_NT ia32 10.0.14393
• Extensions:

---

yahei_mono.zip

notepad:

vscode:

Steps to Reproduce:

1.Setup 'Yahei Mono' font.
2.Set to setting.json

{
    "editor.fontFamily": "Yahei Mono"
}

3.Input

中文汉字  KLMN
中文汉字IJKLMN
中文EFGHIJKLMN
ABCDEFGHIJKLMN

[alexdima]

@actboy168 Does it work with "editor.fontFamily": "'Yahei Mono'"

[actboy168]

[alexdima]

I can reproduce the problem, but I'm sorry the ultimate font rendering is done by Chromium. So, feel free to create an issue against Chromium https://bugs.chromium.org/p/chromium/issues/list

Here for example I am using Inconsolata (http://levien.com/type/myfonts/inconsolata.html)

We use 100% the same code to render. When changing fontFamily we simply let Chromium know the desired font family and let it render the text.

[abcfy2]

Same issue here. Chinese fonts does not work with monospace.

Here is my vscode config:

{
    "editor.fontFamily": "'Monaco', 'Source Han Sans'",
    "editor.fontSize": 20,
    "editor.wrappingColumn": 0,
    "editor.wrappingIndent": "indent",
    "editor.formatOnType": true,
    "editor.tabCompletion": true,
    "editor.mouseWheelZoom": true,
    "editor.renderControlCharacters": true,
    "editor.renderIndentGuides": true,
    "files.autoSave": "afterDelay",
    "editor.renderWhitespace": "all",
    "editor.rulers": [80]
}

Chinese fonts are always monospacing.

vim or terminal works very vell.

But vscode doesn't.

[alexdima]

@abcfy2 Please create an issue against Chromium if you believe the font you are trying is monospace and Chromium renders it incorrectly https://bugs.chromium.org/p/chromium/issues/list

In the meantime, the Inconsolata font I link to above is monospace and renders consistent widths for CJK characters.

[yume-chan]

xterm.js creates spans for each CJK characters to adjust their width to be equal to two Latin characters, so they look perfect in the Integrated Terminal.

Can Code do the same thing?

[alexdima]

This is an upstream issue (possibly within Chromium), and there are no known workarounds that we could implement on our side. This means there is no possible code change for us to do in VS Code sources to improve things.

To keep the number of issues in our inbox at a manageable level, we’re closing issues that have been on the backlog for a long time but haven’t gained traction or that are not actionable. Thank you for your time and understanding.