You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I’m not able to reproduce this on any of my Macs. I suspect your terminal may not be using UTF-8 (see #30).
Would you mind running the locale command and pasting the output here?
Also, to be thorough, what terminal emulator and font are you using? It appears to be Lucida Console in macOS stock terminal, though it would be good to verify this.
Hi! I’m not able to reproduce this on any of my Macs. I suspect your terminal may not be using UTF-8 (see #30).
Would you mind running the locale command and pasting the output here?
Also, to be thorough, what terminal emulator and font are you using? It appears to be Lucida Console in macOS stock terminal, though it would be good to verify this.
Okay, that’s good to know. Still, it would be good to figure out why things aren’t rendering properly under zh_CN.UTF-8. If you don't mind I'm going to leave this issue open for now so we can hopefully solve for this.
Okay, that’s good to know. Still, it would be good to figure out why things aren’t rendering properly under zh_CN.UTF-8. If you don't mind I'm going to leave this issue open for now so we can hopefully solve for this.
Encodings like this are very difficult to deal with because there's technically no correct answer to how something should be configured. For such a common failure as this, it makes sense to include a link in the --help of the application and in the readme. Basically just in as many places as the user may be looking at for assistance.
Now that this is known, it may also be worth while to pre-emptively check the value of that environment variable and see if there's a way to provide a warning to the user.
This isn't much different to other tools that, as an example, require a nerd font, in order to correctly display various icons and such.
before executing the main app, but that didn't work, any nice solution?
In the source code of github.com/mattn/go-runewidth, it obtains the RUNEWIDTH_EASTASIAN environment variable using the init() function.
According to the execution order of init() in Golang, you can create a separate conf package in your project, and set the RUNEWIDTH_EASTASIAN environment variable in the init() function within this package. Then, you can import the conf package in the main package.
Just ensure that the conf package is the first in the import list of the main package, and it will take effect.
before executing the main app, but that didn't work, any nice solution?
In the source code of github.com/mattn/go-runewidth, it obtains the RUNEWIDTH_EASTASIAN environment variable using the init() function.
According to the execution order of init() in Golang, you can create a separate conf package in your project, and set the RUNEWIDTH_EASTASIAN environment variable in the init() function within this package. Then, you can import the conf package in the main package.
Just ensure that the conf package is the first in the import list of the main package, and it will take effect.
Activity
meowgorithm commentedon Aug 1, 2021
Hi! I’m not able to reproduce this on any of my Macs. I suspect your terminal may not be using UTF-8 (see #30).
Would you mind running the
localecommand and pasting the output here?Also, to be thorough, what terminal emulator and font are you using? It appears to be Lucida Console in macOS stock terminal, though it would be good to verify this.
greycodee commentedon Aug 2, 2021
locale:greycodee commentedon Aug 2, 2021
my terminal is iTerm2, and the font I use is
Monaco Regulargreycodee commentedon Aug 2, 2021
I solved this issue based on this answer,
The solution is:
export LC_CTYPE="en_US.UTF-8"meowgorithm commentedon Aug 2, 2021
Okay, that’s good to know. Still, it would be good to figure out why things aren’t rendering properly under
zh_CN.UTF-8. If you don't mind I'm going to leave this issue open for now so we can hopefully solve for this.[-]Mac interface typography is messy[/-][+]Rendering Issues with zh_CN.UTF-8[/+]greycodee commentedon Aug 2, 2021
Ok, I'll leave that question open
meowgorithm commentedon Aug 2, 2021
Thanks! Related: mattn/go-runewidth#14
meowgorithm commentedon Aug 2, 2021
Also for reference: setting
LC_CTYPE=zh_CN.UTF-8recreates the behavior. SettingLC_CTYPE=zh_CN.UTF-8 RUNEWIDTH_EASTASIAN=0corrects it.greycodee commentedon Aug 3, 2021
This also works. When I set
export RUNEWIDTH_EASTASIAN=0, it is normal.yechentide commentedon Feb 2, 2022
LC_CTYPE="ja_JP.UTF-8"also causes incorrect rendering.It can also be solved by
export LC_CTYPE="en_US.UTF-8"orexport RUNEWIDTH_EASTASIAN=0Qrnbth commentedon Mar 2, 2022
@meowgorithm
How to force terminal to run with this certain enviroment without configuring environment manually?
I tried
before executing the main app, but that didn't work, any nice solution?
ghostsquad commentedon May 29, 2022
@Qrnbth have you tried
os.Setenv("RUNEWIDTH_EASTASIAN", "0")?Qrnbth commentedon May 29, 2022
ghostsquad commentedon May 29, 2022
Encodings like this are very difficult to deal with because there's technically no correct answer to how something should be configured. For such a common failure as this, it makes sense to include a link in the
--helpof the application and in the readme. Basically just in as many places as the user may be looking at for assistance.Now that this is known, it may also be worth while to pre-emptively check the value of that environment variable and see if there's a way to provide a warning to the user.
This isn't much different to other tools that, as an example, require a nerd font, in order to correctly display various icons and such.
Ice-Mel commentedon Aug 2, 2023
In the source code of
github.com/mattn/go-runewidth, it obtains theRUNEWIDTH_EASTASIANenvironment variable using theinit()function.According to the execution order of
init()in Golang, you can create a separateconfpackage in your project, and set theRUNEWIDTH_EASTASIANenvironment variable in theinit()function within this package. Then, you can import theconfpackage in themainpackage.Just ensure that the
confpackage is the first in the import list of the main package, and it will take effect.Qrnbth commentedon Aug 7, 2023
This do works,thanks