On Sun, Aug 18, 2013 at 3:57 PM, Wim Feijen <[email protected]> wrote:
> Hi Jacob and Adrian, > > Reading this long thread with many +1s makes me think of truncatechars > which is not a good feeling. > It's important to remember that the truncatechars example wasn't anywhere near as simple as the original proposal suggested (or proponents continual insisted). Most proposals for a truncatechars command implemented "value[:n]", and if you look at the solution that was accepted, the solution acceptable to core was a *lot* more complex than that due to unicode issues. The truncatechars issue is also from a time when the core team was a lot smaller than it is today, so the bandwidth that was available to spend was pretty low; combine this with the fact that the core team members at the time didn't really like the idea from an aesthetic sense, and the idea got stalled. That said -- I hear you: you don't want to see a repeat of truncatechars as an example of the core team interacting with the community. However, I think the example here is different (at least, it is from my perspective). In the case of truncatechars, there was a reasonable solution, the core team indicated what it was, but also indicated they weren't going to spend time building it themselves. End users who *really* wanted to use the value[:n] solution could add it as a custom tag and use it in about 5 lines of code (which was also a big reason why the core team didn't give the issue much thought). In this case, we're discussing a fundamental design decision of the template language. There is no "right" answer here -- there's only the design considerations for both sides of the argument. Allowing multiline tags will have a profound impact on what Django templates look like in the wild, and to date, the core team hasn't been convinced that the cost is exceeded by the benefit that is gained by constraining them. > I wondered if you are using internationalisation? If so have you run into > the same problems or is it easy to circumvent for you? > I'm not using it myself, so can you clarify how multiline tags affects internationalization? Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
