- 🇭🇺Hungary Gábor Hojtsy Hungary
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 may have 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 may have 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.
- 🇹🇷Turkey kburakozdemir İstanbul
Regarding Gabor's answer ( #24 🐛 Misconfigured plural forms for Turkish locale Postponed: needs info )
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.
- 🇹🇷Turkey makbay
I can confirm that we have 2 separate fields for singular and plural translations and it works!
- Status changed to Needs review
about 1 year ago 9:06am 19 October 2023 - 🇹🇷Turkey kburakozdemir İstanbul
I can also confirm that the translation for singular/plural situations is now working. Thanks.
- Status changed to RTBC
about 1 year ago 9:45am 20 October 2023 - 🇹🇷Turkey kburakozdemir İstanbul
There are other people that have tested this.
- 🇹🇷Turkey Kartagis Istanbul
I can also confirm. Thank you to those who have put serious effort in this.
- 🇹🇷Turkey Kartagis Istanbul
I just noticed something. I didn't get any errors like I used to, but when I proceeded to translate https://localize.drupal.org/translate/languages/tr/translate?sid=12830 and hit Save changes, it stays on the screen like nothing has been done. Sure, I get the status message that translation added, but it's like no translation has been added.
- Status changed to Fixed
12 months ago 3:54pm 4 January 2024 - 🇭🇺Hungary Gábor Hojtsy Hungary
@Kartagis: that seems to be a different bug? I think this is sufficienctly resolved.
Automatically closed - issue fixed for 2 weeks with no activity.