Hallöchen! Carl Meyer writes:
> On 02/17/2012 11:04 PM, Glenn Washburn wrote: > >> I'd like to reopen discussion on the multiline tag issue (see: >> https://code.djangoproject.com/ticket/8652) which was closed 3 >> three years ago as "won't fix". The last comment notes that this >> won't happen as the decision has been made many times. But there >> is no link to any discussion on this topic, so I can only assume >> mtredinnick's point two is the supposed reason for not fixing >> this. > > Here's a discussion linked from #3888 in which Malcolm lays out in > brief why multiline tags have been rejected: > https://groups.google.com/forum/?fromgroups#!topic/django-developers/A17TJWd3YJU Thank you! Still, does anybody have a link where the technical problems (in constrast to the aesthetical ones) are discussed? > Personally I'd be -0 at worst on multiline tags, but I also don't see > any compelling use-cases. I think tags on a single line are > significantly easier to parse visually. I've made the same observations as in the parallel posting: I18n becomes awkward with single-line tags. We have dozens of lines like {% blocktrans with originator=entry.originator|get_really_full_name:"mailto" link=entry.get_metadata.link task_id=entry.task.id process_name=entry.task.process_class|contenttype_name %} Another use case, however less frequent in our code: href="{% url samples.views.sample.export sample_name=sample.sample.name %}?next={{ sample.sample.get_absolute_url|urlquote_plus }}" Tschö, Torsten. -- Torsten Bronger Jabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
