Issue

Today, the first version of NVDA including nvaccess/nvda#15013 has been merged to SVN. The translatable strings using ngettext appear in the nvda.po as expected. But the strings using npgettext ("%.1f lignes") don't.

Cause

In PR nvaccess/nvda#15013, the command to build the .pot file has been updated to be able to recognize npgettext as a function operating on translatable strings.
However, the nvda2svn script in the current repository does not use the .pot generated by NVDA's sconstruct; xgettext is called directly in the current repository instead. Thus the command in the nvda2svn script should match the one in NVDA's sconstruct. The change in NVDA's repository had not been duplicated here.

Solution

Update xgettext's parameters as per what was done in NVDA's repo to be able to detect ngettext as a function operating on translatable strings.

Testing

I have no way to test before merging this PR.

@seanbudd, could you test manually this branch on NVAccess server the result of nvda2svn script or merge this PR and trigger nvda2svn?

• The string "%.1f lignes" should appear in the .pot file with a "msgid_plural" field.
• Also the strings "category {categories}" and "with %s item" should still have the msgid_plural field (as today)