nassh: change default font to Noto/Roboto Mono |
|
Issue descriptionthe default monospace fonts we're using today incorrectly render some combining characters (see issue 212705 and issue 212708 as examples). we should change the default font to Noto Mono as it should handle things properly. bundling it in the extension shouldn't be a big deal due to its size (<100k). we might also consider bundling Roboto Mono so people can switch between them based on their preferences. since we'll be changing the defaults on potentially a lot of users, we should implement issue 718723 first, and then we can list this change there (as well as how to change it back). thread on chromium-hterm discussing the topic: https://groups.google.com/a/chromium.org/d/topic/chromium-hterm/np3PNr2pk5c/discussion
,
May 9 2018
The following revision refers to this bug: https://chromium.googlesource.com/apps/libapps/+/c987705b527c34ca4612810c284f157fa913c396 commit c987705b527c34ca4612810c284f157fa913c396 Author: Mike Frysinger <vapier@chromium.org> Date: Wed May 09 01:16:48 2018 hterm: add Noto Sans Mono to the default font list CrOS is dropping DejaVu in favor of Noto, so add Noto to the search list. We put it behind DejaVu in the list so we don't change the defaults on most users. BUG= chromium:694137 ,chromium:718724 Change-Id: I1fba0109597b293f99d5d77f8a5e14904a1c4563 Reviewed-on: https://chromium-review.googlesource.com/1049412 Reviewed-by: Dan Erat <derat@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> [modify] https://crrev.com/c987705b527c34ca4612810c284f157fa913c396/hterm/js/hterm_preference_manager.js |
|
►
Sign in to add a comment |
|
Comment 1 Deleted