I export .po file and import it without modifying it and I get the following error:
The translation file fi.po contains an error: "msgstr" was expected but not found on line 6303.

#: modules/menu/menu.admin.inc:503
msgid "The menu name can't be longer than 1 character."
msgid_plural "The menu name can't be longer than @count characters."
<- line 6303

I think this relates to plural forms. The msgstrs are missing after all plural msgids. How this could be fixed?

CommentFileSizeAuthor
#4 proper plurals.po387 bytesnewrooky

Comments

vesapalmu’s picture

vesapalmu commented
Assigned: Unassigned » vesapalmu
Status: Active » Postponed (maintainer needs more info)

Is this still an issue?

merilainen’s picture

merilainen commented

Is this only related to Finnish translation or what? I don't get many hits with google and I've had this problem for ages.

It happens for me when using export from another installation and trying to import it. Would save a lot of work if the problem was solved!

szczym’s picture

szczym commented

I just get the same error while importing polish translation from other website.

newrooky’s picture

newrooky commented
StatusFileSize
new proper plurals.po387 bytes

This issue is related to a plural msgid issue as has been suggested. I am not sure why it happens (it occurs in most languages), but it can be remedied by uploading a clean po file with proper plurals to the site you are going to export from and then re-exporting. You can also manually edit the PO file, but if it is large there are likely to be more than several issues in it.

Once again, to fix this do:
1. Go to site one (the site that you will export the translation from)
2. Import a clean PO file that has proper plurals (such as the one attached) in to the language you will export
3. After it has been properly imported, re-export the PO file.
4. Import into the new site and all should be well.

Brandon

vesapalmu’s picture

vesapalmu commented
Status: Postponed (maintainer needs more info) » Fixed

We've exported the Finnish po a few times after the original issue so I'm assuming this has been fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.