Rosetta Code:Village Pump/Line breaks in templates

I've seen people go back and forth in Template:Works with, Template:Libheader, Template:Trans, and other example-level templates on whether they want the line break in the template or on the page. We should just make a decision and go with it. I vote for one line break in the template (not a <br/>) so that people can type something like this:

{{works with|libraryx|2.1}}
{{works with|language Y|3.4+}}
{{works with|OS Z|8.2}}

and it with show up like this:

Works with: libraryx version 2.1

Works with: language Y version 3.4+

Works with: OS Z version 8.2

If they type this:

{{works with|libraryx|2.1}}{{works with|language Y|3.4+}}{{works with|OS Z|8.2}}

it will show up like this:

Works with: libraryx version 2.1 Works with: language Y version 3.4+ Works with: OS Z version 8.2

Thoughts? --Mwn3d 21:00, 2 November 2010 (UTC)

If you put a leading <br> in, you break (hah!) a lot of simple cases where there's only a single {{works with}} directly below a =={{header}}== line. That's the most important use case right now! While it would be nice to have fancy formatting between a sequence of these, it's far less important than making the basic case work right. Well, IMO anyway. –Donal Fellows 11:03, 3 November 2010 (UTC)

Ok, what if we were to put a <div> around the content? Mwn3d's example would come out as:

Works with: libraryx version 2.1

Works with: language Y version 3.4+

Works with: OS Z version 8.2

(block-level styling to the rescue...) It would also be trivial to add per-template CSS styling, for easier visual recognition of the data. --Michael Mol 12:10, 3 November 2010 (UTC)

That doesn't work so well in the cases where someone's done {{works with|...}}<br>{{works with|...}} but I guess they're less common so we can just fix them. Reasonable trade-off. –Donal Fellows 13:56, 3 November 2010 (UTC)

Done. Also, I added 'examplemeta' CSS classes to each, and an additional CSS class per template. --Michael Mol 16:19, 3 November 2010 (UTC)

You guys are awesome. Thanks for getting this fixed so quickly. --Mwn3d 18:24, 3 November 2010 (UTC)