New issue
Advanced search Search tips

Issue 807007 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 737454
Owner: ----
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

hterm: renders certain Unicode characters too narrow

Project Member Reported by bcmi...@google.com, Jan 29 2018

Issue description

Chrome Version       :
Google Chrome	63.0.3239.140 (Official Build) (64-bit)
Revision	0
Platform	10032.86.0 (Official Build) stable-channel panther
Firmware Version	Google_Panther.4920.24.26

URLs (if applicable) :
https://chrome.google.com/webstore/detail/secure-shell/pnhechapfaindjhompbnflcldabbghjo


What steps will reproduce the problem?
(1) On a ChromeOS device, set the Fixed-width font to `Droid Sans Mono`.
(2) In the Secure Shell extension options, set font-family to `monospace` and all encoding options to `utf-8`.
(3) Open a Secure Shell connection to a system that supports UTF-8 text.
(4) In the SSH connection, run `echo -e '\u2308\u2309X\n  X'`


What is the expected result?
The echo command prints two lines.
The X characters in each line should align vertically.
(They are each the third character in the line, and the terminal font is supposed to be monospaced.)

What happens instead?
The X on the first line is too far to the left.
The two preceding characters, LEFT CEILING and RIGHT CEILING, are rendered narrower than the rest of the characters in the font.
(See the attached screenshot.)


The steps to reproduce the issue here are a reduced example; in practical use, the problem is particularly acute when using split windows (as under emacs, tmux, or screen).

 
Screenshot 2018-01-29 at 16.09.05.png
20.5 KB View Download

Comment 1 by vapier@chromium.org, Jan 29 2018

Labels: allpublic
Mergedinto: 737454
Status: Duplicate (was: Unconfirmed)
Summary: hterm: renders certain Unicode characters too narrow (was: hterm renders certain Unicode characters too narrow)
this is really a bug in the font for not actually being monospace.  feel free to throw a bug at those maintainers while you're at it :).

we have a general bug to address this for all fonts though, so duping over.

Comment 2 by bcmi...@google.com, Jan 29 2018

> this is really a bug in the font for not actually being monospace.

Yeah, unfortunately I can't seem to install custom fonts on ChromeOS ( https://crbug.com/320364 ), so I can't fix the issue by using a different font.
(All of the preinstalled fonts on ChromeOS exhibit this problem.)

At any rate: falling back to a non-monospace glyph without fixing up the spacing seems like a rendering bug, not a font bug...

Comment 4 by vapier@chromium.org, Jan 29 2018

> At any rate: falling back to a non-monospace glyph without fixing up the spacing seems like a rendering bug, not a font bug...

feel free to take that up with the blink guys then.  g'luck convincing them ;).

Comment 5 by bcmi...@google.com, Jan 30 2018

> feel free to take that up with the blink guys then.  g'luck convincing them ;).

Filed as https://crbug.com/807361.

Sign in to add a comment