Misconfigured plural forms for Turkish locale

@Kartagis: What was your translation string?
1) Make sure it has the placeholder in it.
2) Do not translate placeholder.

e.g. if the original string is Create the directory %translations_directory then your translation string should be Créer le répertoire %translations_directory in french. The position of the placeholder can change.

I succeed to submit multiple variants for this #2412497 string here in the original English language. So I assume it's probably not a validation error.

@Kartagis have you tried to submit only the two placeholders alone?

%translations_directory
:install_txt

If that is accepted, than it's probably some formatting mistake I think.

As @Kartagis reported multiple times (see child issues #3090159: Missing variable @count and #3093548: Missing variable(s): @backends, @handbook_url) I felt the need to move this investigation forward. This issue has the lowest NID among the three of them, so I consider this one the original, and the other two the duplicates.

This situation is not from the beginning: some string IDs with plural form definition has been successfully translated already since 2009.

People with access to approve suggestions should be able to import .po files to fix this AFAIK. Did you try that?

You would only come across this problem if someone imported a broken/incorrect translation file AND that person has high privileges. The combination of those two is not assumed to be commonplace.

Let's discuss this at the Drupal Turkey meeting @Kartagis. People have high privileges should pay attention if such problems occur after the importing process.
IDK "the official plural form definition for Turkish" mention in the problem described above but we can try @Gabor's suggestion first.

"So, what can we do about this? […]"

@Kartagis Afaik recently you gained administrator permissions on the Turkish locale, right? If yes, then here's a list of steps elaborating the process Gábor mentioned in his comment #13. By following them you can try to re-configure the proper plural definition for Turkish locale:

1. Go to the Export tab of your localization group
2. Download the exported file, open it in a plain-text editor and search for the line saying "Plural-Forms: nplurals=1; plural=0;\n"
3. Replace the current definition to one of the options I wrote in the issue description (IS). So your entire line now looks like this: "Plural-Forms: nplurals=2; plural=n>1". Save the file.
4. Go to Import tab of your locale and import the file.
5. At the end visit back the original string ID #77350 and let's see whether this process helped.

Because when I exported again after I imported, it was reverted to the original.

Let's unpack this. The act of exporting broke the plural form? It was good on the UI after you imported the .po file but broke once you exported something?

I am sitting with Burak Ozdemir and Thomas Bailly and FMB and they are all saying again that 2 strings should be it. #2503057: Turkish had wrong default plural setup also proves with sources that the single plural formula setup was not correct. I changed it on the backend for now to

nplurals=2; plural=(n > 1);

. We should also fix #2503057: Turkish had wrong default plural setup separately AND watch if there will be any regressions on localize.drupal.org of this config.

Postponing for more info assuming. we can/should revisit this to see if the new config sticked or we need to fix something else so its not undone accidentally.

Regarding Gabor's answer (#24)

We now have separate strings for singular and plural forms... and we can now save the translation, which was not the case before.

@Tolga I think that this issue needs feedback/more info.

I can confirm that we have 2 separate fields for singular and plural translations and it works!

I can also confirm that the translation for singular/plural situations is now working. Thanks.

There are other people that have tested this.

I also confirm.

@Kartagis: that seems to be a different bug? I think this is sufficienctly resolved.