illegal encoding in zh_CN.cp936.po

2014-05-23 Thread Danek Duvall
After changeset 4303f7b6f72f, I'm seeing this: OLD_PO_FILE_INPUT=yes msgfmt -v -o zh_CN.cp936.mo zh_CN.cp936.po Processing file "zh_CN.cp936.po"... GNU PO file found. Generating the MO file in the GNU MO format. Processing file "zh_CN.cp936.po"... ERROR: Line 2899 (zh_CN.cp

Re: illegal encoding in zh_CN.cp936.po

2014-05-23 Thread Bram Moolenaar
Danek Duvall wrote: > After changeset 4303f7b6f72f, I'm seeing this: > > OLD_PO_FILE_INPUT=yes msgfmt -v -o zh_CN.cp936.mo zh_CN.cp936.po > Processing file "zh_CN.cp936.po"... > GNU PO file found. > Generating the MO file in the GNU MO format. > Processing file "zh_CN.cp936.p

Re: illegal encoding in zh_CN.cp936.po

2014-05-25 Thread lilydjwg
On Fri, May 23, 2014 at 09:05:20PM +0200, Bram Moolenaar wrote: > The file is generated from zh_CN.po with the command: > > iconv -f gb2312 -t cp936 zh_CN.po | \ > sed -e 's/charset=gb2312/charset=gbk/' -e 's/# Original > translations/# Generated from zh_CN.po, DO NOT EDIT/' > zh_CN

Re: illegal encoding in zh_CN.cp936.po

2014-06-02 Thread Danek Duvall
I've applied the attached patch to my build, and just set MSGFMT=gmsgfmt in the environment when I run configure. It's yours if you want it, since it seems like a decent addition to the configurability of the build. It's not complete, though, since it doesn't handle xgettext and msgmerge, but I d

Re: illegal encoding in zh_CN.cp936.po

2014-06-03 Thread Bram Moolenaar
Danek Duvall wrote: > I've applied the attached patch to my build, and just set MSGFMT=gmsgfmt in > the environment when I run configure. It's yours if you want it, since it > seems like a decent addition to the configurability of the build. It's not > complete, though, since it doesn't handle

Re: illegal encoding in zh_CN.cp936.po

2014-06-03 Thread Danek Duvall
Bram Moolenaar wrote: > Danek Duvall wrote: > > > I've applied the attached patch to my build, and just set MSGFMT=gmsgfmt in > > the environment when I run configure. It's yours if you want it, since it > > seems like a decent addition to the configurability of the build. It's not > > complete