On Aug 8, 2016, at 1:58 PM, Chris Forster <[email protected]> wrote:
> You may note that in both these cases, I've removed the splice (@); that's
> because when I include it, we have this situation.
I believe I suggested the `◊(define-meta title ◊@{Markup in ◊em{MetaData}})`
idea to you. But I see that it doesn't quite work. The splice mark should never
show up. I consider this wrong:
> <div class="titleblock">
> <h1><@>Markup in <em>MetaData</em></@></h1>
> <h1>@Markup in emMetaData</h1>
So I'll look into that.
In the meantime, your (perhaps accidental) discovery of `◊(define-meta title
◊{Markup in ◊em{MetaData}})` looks like the better idea anyhow, at least for
metas. When you use `◊{ ... }` without a function name, then it just produces a
list.
To convert that list to vanilla text that LaTeX can use, you can try something
like:
◊(local-require racket/string racket/list)
◊(apply string-append (filter string? (flatten (hash-ref metas 'title))
This will take the X-expression-ish list inside `(hash-ref metas 'title)`,
flatten it (thereby losing all the internal nesting, take out everything but
the strings, and then push them together. (Depending on what's in that meta
field, more elaborate filtering might be required, but that's the general idea.)
--
You received this message because you are subscribed to the Google Groups
"Pollen" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
