"Translations/YourProject/PartialPOExport" help guide - suggest using the --no-fuzzy-matching option for merges

[David Planella]

On the Translations/YourProject/PartialPOExport page, we give an example of the following command to perform a merge:

  msgmerge -o merged.launchpad.sr.po partial-export.sr.po upstream.sr.po

This type of merge without options presents the following potential problem: msgmerge will take upstream.sr.po as the template and might replace some already translated strings with fuzzy matches.

Here's an example with a real set of PO files (attached):

 msgmerge -o gdm.master.ca.merged-fuzzy-matching.po po_gdm-ca-1.po gdm.master.ca.po

This merge operation is the same as the one in the example in the documentation page. It presents the problem that it changes some already translated (and not touched by the partial PO export) strings in the result. E.g.:

Before the merge (gdm.master.ca.po)
#: ../daemon/gdm-xdmcp-display-factory.c:595
msgid "Could not create socket!"
msgstr "No s'ha pogut crear el sòcol"

After the merge (gdm.master.ca.merged-fuzzy-matching.po)
#: ../daemon/gdm-xdmcp-display-factory.c:595
#, fuzzy
msgid "Could not create socket!"
msgstr "XDMCP: No s'ha pogut crear la memòria intermèdia de l'XDMCP"

This situation can be avoided by adding the '--no-fuzzy-matching' (or '-N' in short) option in the command.

I believe we should either use an example command with the '-N' option or add a short paragraph mentioning that option.

I can go ahead and do this change in the wiki myself, I just wanted to discuss it here before.

[Данило Шеган (danilo)]

Heh, yeah that would be just fine. We can probably come up with even better options, or perhaps provide a msgcat-based command. Since you volunteered to fix this in the wiki, I am assigning it to you. :)