Context Navigation

Changes between Initial Version and Version 1 of Ticket #14844, comment 2

initial	v1
4	4	I'd be inclined to implement the solution proposed by Claude for both 1.2.X and trunk now so to unbreak the i18n workflow (PO -> MO conversion is broken ATM) and target a longer term solution for trunk once the template syntax overhaul dust settles.
5	5
6		That longer term solution might involve to end the full reliance on `verbose_name_plural` when pluralizing model names in Python code and templates, for the benefit of locales with more than two plural forms. I suspect the challenge would be to achieve that without interfering with or complicati~~on English speaking Django core~~ developers normal workflow so to don't get the proposal rejected.
	6	That longer term solution might involve to end the full reliance on `verbose_name_plural` when pluralizing model names in Python code and templates, for the benefit of locales with more than two plural forms. I suspect the challenge would be to achieve that without interfering with or complicating English-speaking [Django core] developers normal workflow so to don't get the proposal rejected.