View Single Post
Old 09-01-2014, 12:41 PM   #5
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,461
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by BookJunkieLI View Post
Okay, I'm really confused now. In the referenced post you said,
But now you're saying you can't? Aren't composite columns made up of templates? Or is this a case of me confusing terms?
A composite column is in the end a custom column. Its template is evaluated when metadata is saved for whatever purpose, from showing in the GUI through sending to device to building jackets. So yes, you can use a composite column in a jacket.

What you cannot do is use a template function or extended template syntax directly in a jacket. In other words, you can use {foobar} but you cannot use {foobar:function()}, {foobar:|prefix|suffix}, or "program: bla bla". This means you cannot use formatter functions to generate html in templates, for example to create author links.

As far as I can tell any HTML in a column will be displayed as text, not interpreted as HTML. I confess I haven't tried it, but the code "escapes" the contents of custom columns, which I think converts HTML to text.
chaley is offline   Reply With Quote