Seems this thread is saying a few things: 1) It's already there with slice or using a CSS hack (eek!) 2) You should never truncate text on character boundaries anyways 3) Nobody is asking for it
I'm new to Django and my first order of business was creating a truncate filter because I couldn't find one. I also found it pretty odd that it wasn't supported out of the box. I don't think slice is the same thing since ellipses are important in this case and adding conditionals in templates to accomplish this is cumbersome and sloppy. I also feel the argument that there is no reasonable scenario for wanting to truncate text on character boundaries is pretty arrogant. I've found many situations where this is desirable -- like the long file paths mentioned earlier. I joined this group, just so I can ask for it to be added to core. It doesn't look like I'm alone. I don't understand the argument for not including it. It's pretty obviously wanted and it's not going to turn journalism on it's ear. It would appear there is also very little cost to including it. Eric -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
