FS#64992 - [neovim] zh_CN locale is not used
Attached to Project:
Community Packages
Opened by Kid (kidonng) - Tuesday, 31 December 2019, 07:22 GMT
Last edited by freswa (frederik) - Sunday, 23 February 2020, 18:29 GMT
Opened by Kid (kidonng) - Tuesday, 31 December 2019, 07:22 GMT
Last edited by freswa (frederik) - Sunday, 23 February 2020, 18:29 GMT
|
Details
* $LANG: zh_CN.UTF-8
* $LANGUAGE: zh_CN * Enabled locale in /etc/locale.conf: LANG=zh_CN.UTF-8 * Enabled locales in /etc/locale.gen: en_US.UTF-8 UTF-8, zh_CN.UTF-8 UTF-8 * DE: KDE Plasma 5.17.4 * Kernel: 5.4.6-zen3-1-zencjk Description: The display language of Neovim remains English under zh_CN locale on KDE Plasma. If the locale file is linked to the correct place (ln -s /usr/share/locale/zh_CN.UTF-8/LC_MESSAGES/nvim.mo /usr/share/locale/zh_CN/LC_MESSAGES/), it will show zh_CN translation as expected. Neovim is the only package to put locale file under /usr/share/locale/zh_CN.UTF-8, I assume it's wrong and we should use /usr/share/locale/zh_CN as other packages do. This goes to zh_TW as well. However, Neovim can show the correct translation on GNOME without linking the locale file (other environments are the same as above). |
This task depends upon
Comment by Kid (kidonng) - Tuesday,
31 December 2019, 07:24 GMT
Comment by
Sven-Hendrik Haase (Svenstaro) -
Sunday, 23 February 2020, 13:45 GMT
Comment by Kid (kidonng) - Sunday,
23 February 2020, 18:26 GMT
Append: "Neovim is the only package (on my machine) to put locale
file under /usr/share/locale/zh_CN.UTF-8"
Looking into this a little bit, it seems to be an upstream bug as
they choose the names for the locales and maybe there is some
logic behind that name. Please report it as an upstream bug and
link it here.
Essentially this is not a bug, I find the $LANGUAGE (zh_CN) set by
KDE Plasam locale settings to be the culprit. I think I should
just use /etc/locale.conf only (thus $LANGUAGE will be not set)
and Neovim will behave well.