On Dec 30, 4:46 pm, James Bennett <ubernost...@gmail.com> wrote: > 1. How many filters are we talking about here? At the very least it > seems like two: one for plain text and one for HTML (since you don't > want tags or character entities getting chopped off partway).
Right now what's on the table with #5025 is a single filter: truncate. > 2. How does this interact with internationalization? Not every > language or locale uses an ellipsis for this (and, really, this needs > to be solved regardless so the existing truncate_words can play nice > with non-English use cases). I agree that this is a separate issue that needs to be solved for truncatewords. > 3. Similarly to the above two, how does this interact with languages > which commonly use composed characters in Unicode? Cutting a character > in half (and thus presenting output that's completely wrong) probably > isn't expected behavior, so how would such a filter deal with this? > Would it need to do Unicode normalization as well? Good catch! Quite an edge case, but luckily it turns out the unicodedata module from the standard library can do all of the normalization for us. > 3. Is adding more filters really the way to do this? Could existing > filters have their functionality expanded instead? I think the filter in the patch is the clearest way of expressing this idea. That being said, I'm sure proposals to other filters would be met with consideration. > These types of questions have to have answers before I'll even think > about supporting a change, but so far I don't really see anyone > proposing answers -- just an endless litany of "me too"-type comments > which don't add anything useful to the discussion. It's no use discussing these details if the core committers and influential contributors are against the idea of a truncate filter in general. I'd like to propose that we have BDFL rule on this issue. It seems that most if not all of the arguments have been put on the table. If the decision is yes, let's include some kind of truncate tag, then we can continue on these discussions about the finer details. If the decision is not to include a truncate tag, then we won't have wasted any time arguing about a moot point. Thanks, Eric Florenzano -- 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.
