[EversonMono] Using Everson Mono in Windows cmd, bash, and PowerShell
lemon at adobe.com
Wed Nov 23 23:59:23 GMT 2016
OK, I’ll agree terminal emulators and code editors are separate use cases, although both require the monospace bit. The Japanese issue I mentioned is a problem with code editors.
Sr Manager, Type Development
From: EversonMono <eversonmono-bounces at evertype.com<mailto:eversonmono-bounces at evertype.com>> on behalf of "tiro at tiro.com<mailto:tiro at tiro.com>" <tiro at tiro.com<mailto:tiro at tiro.com>>
Reply-To: Discussion of the Everson Mono font <eversonmono at evertype.com<mailto:eversonmono at evertype.com>>
Date: Wednesday, November 23, 2016 at 3:54 PM
To: "eversonmono at evertype.com<mailto:eversonmono at evertype.com>" <eversonmono at evertype.com<mailto:eversonmono at evertype.com>>
Subject: Re: [EversonMono] Using Everson Mono in Windows cmd, bash, and PowerShell
On 23/11/16 15:15, David Lemon wrote:
While the work-around John describes should do the trick in this case,
I’d still very much like to see code editors stop requiring the
monospace bit. It seems to me anyone who’s setting code should be a
competent judge of whether his/her font is meeting requirements.
To be clear, the issue is not code editors but terminal emulators. There
are a few things for which terminal emulators are used that rely on
fixed pitch glyphs, notably anything involving box and linedraw
characters. Hence the strict approach to the monospace bit (and also, at
least in the case of the Windows cmd terminal, as I recall, a character
set that includes the linedraw and boxdraw characters; we had to add
these to Consolas to get it to work in that environment).
EversonMono mailing list
EversonMono at evertype.com<mailto:EversonMono at evertype.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the EversonMono