Mirror of forum.nim-lang.org

6587 :: `stdout.write("ああ\n")` works correctly when compiled with `nim c` but not with `nim cpp`

• demotomohiro (orginal) [2020-07-24T18:14:23+02:00] view original

  Couldn't render post #40814.

---

• quetzalb (orginal) [2020-07-24T20:47:55+02:00] view original

  Is it possible C++ standard library initialization is changing the locale? Maybe try building with -nostdlib on the g++ side or call C++ setlocale to validate if it returns the same thing in both cases?

---

• demotomohiro (orginal) [2020-07-24T23:28:26+02:00] view original

  Thank you for your reply!

  I tried following code: test.nim:

  proc setlocale(category: cint; locale: cstring): cstring {.header: "<locale.h>".}
  
  var LC_ALL {.header: "<locale.h>".}: cint
  
  echo setlocale(LC_ALL, "")
  stdout.write("ああ\n")
  Run

  testcpp.nim:

  proc setlocale(category: cint; locale: cstring): cstring {.header: "<clocale>", importc: "std::setlocale".}
  
  var LC_ALL {.header: "<clocale>".}: cint
  
  echo setlocale(LC_ALL, "")
  stdout.write("ああ\n")
  Run

  Output:

  
  f:\temp>nim c -r test.nim
  ....
  Hint: f:\temp\test.exe  [Exec]
  Japanese_Japan.932
  ああ
  
  f:\temp>nim cpp -r testcpp.nim
  ....
  Hint: f:\temp\testcpp.exe  [Exec]
  Japanese_Japan.932
  ������
  Run

  Both c and cpp code are initialized with locale Japanese_Japan.932. My cmd.exe's default code page is 932, but code page was changed to 65001 before I ran test codes. And Nim write "ああ" as utf8 with fprintf. It seems locale is not related to this problem.

---