I received a nice lecture when I asked "why doesn't Jinja (a template engine I use as an alternative to Django) include an intcomma filter, its very useful" on the fact that intcomma is a [insert a bunch of negative remarks here] name for the filter, and it's an internationalization concept, not a standard.
I still agree, it's extremely useful, but I believe it could be renamed, and (if it doesnt) default to the current locale's correct separator. On Jun 3, 8:11 am, Flavio Curella <[EMAIL PROTECTED]> wrote: > Hi, > > Do you think intcomma should use localized separator? If so, would > still be 'intcomma' a correct name (after all, it wouldn't use commas > in, for example, Italian)? > > I already wrote a patch which gives intcomma an optional argument. But > I don't know if I should submit a ticket about intcomma or about a new > filter in humanize. > > Thanks, > Flavio Curella. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
