Mirror of forum.nim-lang.org

7824 :: Unicode string print - the four faces look different when printing - why?

• masiarek2 (orginal) [2021-04-19T02:38:32+02:00] view original

  var s = "Hello 👨‍👩‍👧‍👦"
  echo s
  Run

  See the screenshot at: https://masiarek.blogspot.com/2021/04/blog-post.html

---

• treeform (orginal) [2021-04-19T03:26:52+02:00] view original

  I can think of several reasons:

  • The fonts are different and the terminal font does not have the proper unicode to display that.
  • The terminal does not do the unicode composition thingy needed to display the family emoji.
  • The editor saves the unicode in an odd way so that it does not print correctly.
  • Nim does not support this unicode.

---

• treeform (orginal) [2021-04-19T03:30:13+02:00] view original

  I think its a terminal issue here is how it looks in the terminals I tried:

  None of them can display it and all of them display it differently.

---

• treeform (orginal) [2021-04-19T03:32:54+02:00] view original

  If you write to a file instead of echo:

  var s = "Hello 👨‍👩‍👧‍👦"
  writeFile("foo.txt", s)
  Run

  And open the file it looks correct. I think Nim supports the family emoji but the terminals don't.

---

• juancarlospaco (orginal) [2021-04-19T05:21:24+02:00] view original

  Usually its the fonts that do not have the glyph.

---

• shirleyquirk (orginal) [2021-04-19T05:24:45+02:00] view original

  Nim isn't doing anything other than moving bytes around, it's all about what displays the unicode, and the zero-width joiner is very variously implemented, it varies with os/browser/terminal/font and the newer ones like "👨🏻‍❤️‍💋‍👨🏼" will be one glyph or four depending on what you're seeing it on.

---

• lscrd (orginal) [2021-04-19T10:20:37+02:00] view original

  You are right. I have tried with classic classic emojis which have code from U+1F600 to U+1F64F. And, in my terminal, they are correctly displayed. But the four emojis which have code from U+01F466 to 01F469 are not correctly displayed.

  I tried to display them in a text editor, with no success. It failed in VSCode for instance. But it’s OK in a web browser using the same font! So this is not (or not only) a font issue.

  The Nim compiler is obviously exonerated here.

  It seems that Nim is not guilty here. It’s either a terminal issue or a font issue.

---