Bug#851629: neovim-runtime: Translation files in wrong path

[Boyuan Yang]

在 2017年4月10日星期一 +08 上午8:56:14，James McCoy 写道：
> On Tue, Jan 17, 2017 at 09:54:55AM +0800, Boyuan Yang wrote:
> > .mo files are placed in wrong directories and is not working correctly.
> > 
> > Examples:
> > 
> > Bad: /usr/share/locale/zh_TW.UTF-8/LC_MESSAGES/nvim.mo
> > Good: /usr/share/locale/zh_TW/LC_MESSAGES/nvim.mo
> > 
> > Bad: /usr/share/locale/zh_CN.UTF-8/LC_MESSAGES/nvim.mo
> > Good: /usr/share/locale/zh_CN/LC_MESSAGES/nvim.mo
> > 
> > Similar problems apply for other translations.
> 
> Can you explain why these are wrong?  I'm not well versed in translation
> handling, but those paths seem to agree with what's described in
> setlocale(3).

In January it seems that my computer won't show any translation strings in 
nvim and I had to copy .mo files from .../zh_CN.UTF-8/... to .../zh_CN/... to 
make things working.

I just tested again under correct locale and found that things are working 
well. Don't know what really happened in this period of time.

After all, I have little idea about vim/nvim's way of dealing with encoding 
problems in gettext PO files. Neovim (actually including Vim) is the *only* 
application on my system that uses /usr/share/locale/xx_yy.{UTF-8,cp1250}, 
which seems hacky. I'm not sure if it should be an upstream issue.

--
Sincerely,
Boyuan Yang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/attachments/20170410/5e816a75/attachment.sig>