[Patch] Unique strings for msgid (was: Avoid the translation of strings never shown to any user)

[Hb---]

Currently some strings are marked for translation which will never be shown to any user. They should be taken away from the translation workload.

In #9110 the translation of plural forms was discussed and fixed with r6507. Afterwards the focus shifted and it was noticed that the unneeded singular forms were grammatically wrong. The correct, but unneeded strings were then placed with r6679.

Planned solution:

1. Replace the unneeded singular strings with their plural partners. Modern ​translation software will recognize these as Non-unique segments aka duplicates. So only one translation is needed.

The effect of this can be seen on the source string You are about to combine {0} objects, but the following tags are used conflictingly:<br/>{1}If these objects are combined, the resulting object may have unwanted tags.<br/>If you want to continue, you are shown a dialog to fix the conflicting tags.<br/><br/>Do you want to continue?
This string is a duplicate of two plural forms

2. Comment in java source to inform about the equal strings. This comment is scraped daily from the source and placed as comment in the translation source files.

The already present comments are like
for correct i18n of plural forms - see #9110
or
I18n: plural form for objects, but value < 2 not possible!
with the later one being closer to the solution.

Unneeded strings:

Combine {0} way

Merge {0} node

You are about to launch {0} browser window.<br>This may both clutter your screen with browser windows<br>and take some time to finish.

Dupe into {0} node

You moved more than {0} element. Moving a large number of elements is often an error.
Really move them?

Split way {0} into {1} part

Remove "{0}" for {1} object

Set {0}={1} for {2} object

Deleted {0} tags for {1} object

Set {0} tags for {1} object

You are about to combine {1} object, which is part of {0} relation:<br/>{2}Combining these objects may break this relation. If you are unsure, please cancel this operation.<br/>If you want to continue, you are shown a dialog to decide how to adapt the relation.<br/><br/>Do you want to continue?

You are about to open <b>{0}</b> different relation editor simultaneously.<br/>Do you want to continue?

[stoecker]

PLease learn a bit more about I18n and the translation system used by JOSM before requesting such changes and commenting a lot of tickets.

[Hb---]

Replying to stoecker:

... commenting a lot of tickets.

The comments are partly withdrawn with 18596 (your comment).

Replying to stoecker from ticket/18643

Can you please stop to ask for changes which violate our guidelines.

The points you claim are now written down in the guidelines: DevelopersGuide/StyleGuide Diff 36-34

I18n always has to have full strings independent from the possibly used numbers in the code, ...

The patch to achieve this is attached.

[simon04]

Changing those strings requires re-translation in all languages. I don't think this change is worth that burden placed on the translators.