Re: [Bug-gnubg] updated po files

[Petr Kadlec]

Hi!

At 19:51 14.06.2004 +0000, you wrote:
> (a) some illegal byte sequences in ja.po:
>
> ja.po:4739:78: invalid multibyte sequence
> ja.po:4740:18: invalid multibyte sequence
> ja.po:7184:78: invalid multibyte sequence
> ja.po:7185:18: invalid multibyte sequence

Hmmm, strange. I did not change that file manually, I just ran that 
msgmerge on it. So I don't know what could be the problem here. Moreover, I 
tried to compile the file (both in the version in my working copy, and in 
the version I downloaded via Savannah's viewcvs web interface) and it 
compiled OK (1857 translated messages, 100 fuzzy translations, 1410 
untranslated messages.).

> (b) an wrong msgid in cs.po:
>
> cs.po:4637: 'msgstr' is not a valid C format string, unlike 'msgid'

I DID change that file, and I have compiled it as well. No problems. Even 
stranger, line 4637 in the file is the comment line of the following:
#: gnubg.c:5074
msgid "You must specify an TMG file to import (see `help import tmg')."
msgstr ""
"Musíte zadat TMG soubor, který se má importovat (viz ,,help import tmg``)"
"."

(the accented characters would maybe show up damaged; see 
http://savannah.gnu.org/cgi-bin/viewcvs/gnubg/gnubg/po/cs.po?annotate=1.5#4637). 
Obviously, the comment line is fine, and the string does not even contain 
any format specifications.

> I have msgfmt (GNU gettext) 0.11.4.

I have MSGFMT.EXE (GNU gettext) 0.10.35 -- some mingw port, I presume.

So, I am really puzzled. The only ideas I can think of is that cvs somehow 
screws up something during transfer (how? why?), or that there is some 
problem with line breaks, as I use windows.

Petr

--
Art is the lie that enables us to realize the truth. - Pablo Picasso