Localization

Thank you so much for the translation.

If you can provide a link to your .po file, I can download it and test it out. There’s some work I need to do on my end to make sure it accounts for the various forms of plural.

I’ve included this link below mostly for my reference:

https://wordpress.stackexchange.com/questions/33312/how-to-translate-plural-forms-for-themes-plugins-with-poedit

Thanks.

https://yadi.sk/d/DBQ768nYgdrgW

Thanks!

This one is going to be a tough one for me to figure out. If it’s just PHP, I can just use the _n function and all is well. But the time is in JavaScript. I’ll ponder this one for a bit.

Again for my reference. One person’s approach to localized Russian time variables.

https://keith-wood.name/js/jquery.countdown-ru.js

https://stackoverflow.com/questions/12121515/multiple-plural-forms-in-gettext

Yes, I understand. I’ll think about this also.

Okay, I’ve thought about this for a bit, and I think I know what I need to do to make this happen.

A lot of countdown scripts with internationalization have a separate JS file that “configures” this script. Which I guess is fine, if you have a pure JS solution, which this is not.

Since there’s a mixture of PHP and JS translations that need to happen, what I can do is generate a JS look-up table for certain localizations that have languages with multiple plurality.

So for Russian, I can look at the locale, and if it’s in Russian, generate a look-up table for the seconds/minutes. For 5 minutes, there’s just 5,4,3,2,1, and seconds (59-0). So for the default time, a look-up table for about roughly 64 instances.

Where it gets weird is I have a filter that allows a person to set the number of minutes of the countdown timer. To ease all sanity, I’m going to limit this to 90 minutes. 90 minutes in itself is a bit excessive, so I think anything above that will be limited.

This will limit the look-up table to (my apologies if my math is wrong), 90 (minute variables) and 59 (second variables).

I’ll save these as a transient every to expire every 24 hours for the explicit locale. All these variables might seem a bit much, but when minimized using JSON, won’t take up that much space. It’ll be more PHP processing, which is the reason for the transient.

When one of the locales is detected, I use the look-up table, if not, then regular minutes vs seconds is used.

I think this is the best short-term solution, and should have the least impact on backwards compatibility, and shouldn’t require the translator any significant extra effort besides using poedit to add all the pluralities (a word I discovered today).

I’ll try to have something testable this weekend on GitHub. If you’d like to help me test it, please let me know.

It’s too difficult for me. I’m not friends with scripts, so wait for a turnkey solution. But if you need help to check something – I’m happy.

I finally got around to adding this in. If you have time, can you test out the translation using this file? https://github.com/ronalfy/simple-comment-editing/archive/master.zip

I also added the scrolling effect you wanted.

Yes, with the translation all the problems resolved. Thank you very much. Fixed Russian translation files:

https://yadi.sk/d/3KDesv8ThKAMH
https://yadi.sk/d/YoCuHF2_hKADV

With scroll effect turned out not the way I wanted. The page still jumps, but smoothly now. In any case it is better than it was. When jumps dramatically – it seems some errors or imperfections, and when smoothly – have effect. )) Thanks.

Cool, thanks for checking!

I’ll try to push out a release with the updates tomorrow or Friday.

Ok.)

Should be resolved with version 1.3.0.

Just in case, my name is Nataliya Zav’yalova (Наталия Завьялова). ??

Ah, cool. I’ll fix the readme with your updated name in a few days. I need to try to get all of the other translations up to date.