Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check / X glyphs don't render in Windows TrueType fonts #12

Open
AdamAndersonFalafelSoftware opened this issue Mar 2, 2016 · 2 comments

Comments

@AdamAndersonFalafelSoftware

Both Powershell and Command Prompt with font set to Consolas or Lucida Console exhibit the same behavior: the check and x glyphs appear as boxes with a question mark inside. Changing the font to Raster Fonts fixes the problem, but now you have the problem that your console is in an ugly font. :)

image

@CervEdin
Copy link

Consolas and Lucida Console don't support the U+2713 or U+2A2F glyphs unfortunately. What you can do is run PowerShell or CMD through ConEmu and use Comic Sans or whatever font floats your boat and supports the glyphs.

@substack the issue could be fixed by using the U+221A √ and U+0078 x instead, which I believe is how the Mocha spec reporter does it. Don't know if these are more common glyphs but that would be a solution.

@matthiasg
Copy link

I switched the console to 'DejaVu Sans Mono' font (which looks like Consolas) and Codepage 65001 (UTF-8 via CHCP 65001) and it works for me now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants