Re: Re: Not saving header info

Hi,

Torbjorn Tornkvist wrote:
> msgid "PO file info"
> msgstr ""
...
> But the header written by poEdit have an empty msgid string.

That's correct, but even more correct version of that statement is 
that ALL (valid) .po files have empty msgid string for the header. 
And that's where the problem lies: your .po files are broken, 
period. .po file header is stored as msgid "" in .po files, not in 
msgid "PO file info" or msgid "whatever" as your tool does.

> Is it possible to define the msgid string for the header info
> with poEdit? 

No, and it won't, because the header of valid .po file always has 
msgid "".

> Well, since we already have a header entry in the .po file
> it isn't broken.

You don't, you have a string with translation that happens to look 
exactly like a header entry, but *not* a header entry.

> FYI: We are not using the GNU gettext tools to create our
> .po files. But we use the same file format 

You obviously don't, see above. Here's msgfmt validation of the 
"header" you showed me:

[[email protected] tmp] $ msgfmt -c broken.po -o /dev/null
broken.po:1: `msgid' and `msgstr' entries do not both end with '\n'
msgfmt: broken.po: warning: PO file header missing or invalid
                warning: charset conversion will not work
msgfmt: found 2 fatal errors

VS

-- 
PGP key: 0x465264C9, available from http://pgp.mit.edu/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAQw4dxDYa/UZSZMkRApU6AJ9jSdfT9qzsPu/UFP4ABqpfPOaA9wCcD/IM
katP2PUQkuSPJwh/HAPOeLs=
=+oTn
-----END PGP SIGNATURE-----