Hi Uri, Regarding your past questions,
If you want I can try to spend some time to help solving this specific > problem. I would start with documenting this issue in the release notes of > Django 2.2. I already opened a new task #30945 > <https://code.djangoproject.com/ticket/30945> for documenting this issue. > How do I proceed from here? I think I never submitted changes directly to > Django Git & documentation. Where are the source code of the release notes > documentation and how do I change them? I think that following articles might be helpful: * Writing documentation [1], * Submitting patches [2]. Source file for 2.2 release notes is docs/releases/2.2.txt [3]. Regards, Maciej [1] https://docs.djangoproject.com/en/stable/internals/contributing/writing-documentation/ [2] https://docs.djangoproject.com/en/stable/internals/contributing/writing-code/submitting-patches/ [3] https://github.com/django/django/blob/master/docs/releases/2.2.txt wt., 26 lis 2019 o 13:55 אורי <u...@speedy.net> napisał(a): > Hi Maciej, > > I would not say the rules are incorrect. It depends on the case. In some > cases they might be correct and there might be 3, 4 or even more plural > forms. But in many other cases, two plural forms are enough. It depends on > the strings being translated. I think in most cases, two plural forms are > correct, like was in Django up to 2.1. > > For example in weeks, there is a word in hebrew for "two weeks" > ("שבועיים"), which is more correct than writing two words for two weeks ("2 > שבועות"). But in other cases, there is not a specific word for "2 > <objects>". In the case of Speedy Net for example, I used > function ngettext_lazy in a validator validating the number of characters > in a password or username. In these cases, only the plain plural form > should be used, and anyway the number given there is probable not 1 and > also not 2. It might be in some specific cases 6, 8 or 120, and there is no > specific plural form for that number of characters. The translation is just > using the Hebrew word for characters ("תווים"). Even if this number was 2, > it would have used the same word, but there is a singular word for 1. > > אורי > u...@speedy.net > > > On Tue, Nov 26, 2019 at 1:29 PM Maciek Olko <maciej.o...@gmail.com> wrote: > >> It looks like Transifex uses [1] Unicode Language Plural Rules [2]. If >> they are incorrect for Hebrew, maybe they should be fixed on Unicode side? >> >> Regards, >> Maciej >> >> [1] >> https://community.transifex.com/t/where-does-the-5-come-from-in-the-json-export-of-pluralized-strings/1389/2?u=m-aciek >> [2] >> http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html >> >> wt., 26 lis 2019 o 08:18 אורי <u...@speedy.net> napisał(a): >> >>> >>> >>> On Tue, Nov 26, 2019 at 8:13 AM Matemática A3K <matematica....@gmail.com> >>> wrote: >>> >>>> >>>> >>>> On Mon, Nov 25, 2019 at 6:26 AM אורי <u...@speedy.net> wrote: >>>> >>>>> >>>>> אורי, >>>> >>>> OK, have in mind that a change of the number of plurals for a language >>>> is kind (if not) of an API change for i18n - now you have to feed a >>>> different input - and should be handled as such. There is no way of >>>> modifying your code on an upgrade by the software distribution (the >>>> package). >>>> >>>> Did the script that I posted not do the job? >>>> >>> >>> No offense, but I didn't try. As a Django user I don't expect Django to >>> send me to install and run third party scripts that will keep my sites >>> working when I upgrade Django. I also don't think there is need for 4 >>> plural forms in my .po files. I would like to keep using 2 plural forms as >>> that makes more sense to me. >>> >>> I decided to keep using Django 2.1. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-developers+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/CABD5YeH%3DwqNcWsu5_Lzab39qmcDPY%2BymGD2k-R1mbr%3DEiCvbnQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/django-developers/CABD5YeH%3DwqNcWsu5_Lzab39qmcDPY%2BymGD2k-R1mbr%3DEiCvbnQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CALYYG818kvK%3DPRxj1C_DS-xB5tKkS2zFiBUL02AT5xyWvUNHLw%40mail.gmail.com >> <https://groups.google.com/d/msgid/django-developers/CALYYG818kvK%3DPRxj1C_DS-xB5tKkS2zFiBUL02AT5xyWvUNHLw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CABD5YeHFx0aTeKOuKyc5To%2BvR%2B61nO6kVbs7HbP4yR8JZqOsbQ%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CABD5YeHFx0aTeKOuKyc5To%2BvR%2B61nO6kVbs7HbP4yR8JZqOsbQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALYYG80jemKnYUmrirWucCor-vJgk-vSoXP8xs2kg81zV27nRw%40mail.gmail.com.
