On Thu, Dec 31, 2009 at 12:54 AM, Jerome Leclanche <adys...@gmail.com> wrote: > On Wed, Dec 30, 2009 at 2:06 PM, Russell Keith-Magee > <freakboy3...@gmail.com> wrote: >> >> Secondly, IMHO raw truncation based on characters is bad practice for >> human readable text. A sentence is composed of words, not characters. >> Truncating a sentence mid-word isn't a typographical practice that I >> particularly want to encourage. > > Please... > Please, please, please, do NEVER assume the use cases on your own websites > are the only ones other users will ever need.
Quoting: """ However, even with this modification - what's the use case for an N character truncation? """ > Are you going to truncatewords on long filenames? > What about on hashes? On Email addresses? > Here is where I use > truncate: http://db.mmo-champion.com/i/35191/schematic-wonderheal-xt68-shades/ > - bottom of the right box. I can't truncate such small names based on words > alone. Fine. Those are some use cases. I'm not sure I agree that tail truncation is the right solution for all of them, but that's a different battle. >> As for why this patch has languished for so long - one major reason is >> that nobody has made an issue of it previously. By my count, this >> thread is only the third time that someone has made the case for a >> built-in truncate filter > Oh NO you don't. PLEASE. grep your irc logs for truncate+filter, I know > you've been on irc long enough. I would ask you to please consider the following: * I made no reference to IRC in my comments. * Some people (including myself) don't keep historical logs of IRC chats, due to the ephemeral nature of IRC conversations. * I don't recall anybody mentioning the truncate filter on django-dev while I was in the room *and* participating in the conversation. * If someone did mention truncate in IRC while I was present, they didn't leave a lasting impression. * The Django core team has *never* used IRC as communication channel of record. There is an official django-dev IRC room, but we don't use it to make announcements or to archive design decisions. If we make an important decision on IRC, it is usually backed up by a message on the django-dev mailing list summarizing and archiving the decision. I would then reiterate my original comment. In the archive of record - the django-dev mailing list - there are *exactly* three mentions of truncate. A truncate filter *wasn't* suggested for inclusion in the 1.2 feature list. I don't deny that people want this feature. However, those people haven't gone out of their way to draw attention to their pony until this thread. The original question was "why has this ticket languished?" The simple reason is that the issue hasn't been raised seriously by those that want it. Yours, Russ Magee %-) -- 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.
