Template tag `unlocalize` does not work with `date` and `time` filters.

[Natalia Bidart]

Following #35306, it was noticed that using the date or time template filters would not honor the unlocalize template tag. See regression tests:

tests/i18n/tests.py

@@ -1351 +1351 @@
                 self.assertEqual(template2.render(context), output2)
                 self.assertEqual(template3.render(context), output3)
 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
     def test_localized_off_numbers(self):
         """A string representation is returned for unlocalized numbers."""
         template = Template(

[Claude Paroz]

I'm not yet sure if this can be resolved in the code, or if we should rather complement the template filter docs, telling that if you apply an l10n-sensible filter inside an unlocalized section, you should specify an explicit format argument. The problem being that the way filters are currently implemented, it's not possible to transmit any context. That explains for example that floatformat gained an u parameter to force unlocalization (see #30086).

So in your example in the tests above, you should use |date:settings.DATE_FORMAT and not just DATE_FORMAT. Thoughts?

[Ahmed Nassar]

I'd like to work on this issue if it's still available. Could you confirm if it's unassigned? If so, I will start by reviewing the expected behavior and checking the existing implementation of date and time filters.

Looking forward to contributing!