After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 767457 - emoji characters overlap in gnome-terminal
emoji characters overlap in gnome-terminal
Status: RESOLVED DUPLICATE of bug 767529
Product: vte
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-06-09 15:20 UTC by Yi EungJun
Modified: 2017-04-30 21:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Overlapped whale emoji (6.61 KB, image/png)
2016-06-09 15:20 UTC, Yi EungJun
Details

Description Yi EungJun 2016-06-09 15:20:53 UTC
Created attachment 329480 [details]
Overlapped whale emoji

Steps to reproduce

1. Launch gnome-terminal
2. Install noto-fonts and noto-fonts-emoji
3. Set the font for gnome-terminal to "Noto Sans Mono CJK KR Regular"
4. echo -e '\xf0\x9f\x90\xb31234'

Actual Results

The whale emoji character overlap with '1' of '1234' as the attached image.

Expected Results

The whale emoji character doesn't overlap the numbers.
Comment 1 Christian Persch 2016-06-11 12:07:32 UTC
U+1F433 currently has the East_Asian_Width property value N in Unicode 8, although it will change to W in Unicode 9.

Also, in your image it looks like the whale is bigger than even 2 cells (partially overlapping the '2') so it seems it's substituted from a different font that isn't compatible with the cell width.

_If_ there's a bug here, it's probably in vte not in pango, where vte should somehow make sure even glyphs substituted from another font obey the grid (maybe by scaling the glyph).
Comment 2 Behdad Esfahbod 2016-06-11 19:12:32 UTC
Agree with Christian.  Don't think scaling is needed.
Comment 3 Christian Persch 2017-04-30 21:02:39 UTC

*** This bug has been marked as a duplicate of bug 767529 ***