On Wednesday, October 12, 2016 at 7:03:47 PM UTC-5, Matthew Butterick wrote:
> On Oct 12, 2016, at 4:19 PM, CJ Gaconnet wrote:
> > 
> > To recap, I'm looking to treat my written output as structured 
> > datums/syntax objects/structs foremost, which I can 
> > traverse/combine/transform into documents as needed; I want to extend my 
> > ontology of datums easily whenever needed; I want to define translations of 
> > new datums into various content-types whenever relevant.
> Scribble is two separate components: the @-expression syntax, and the 
> document model / rendering system.
> If you want to use both, try the full `scribble` dialects, like 
> `scribble/doc`.
> If you only want @-expressions, try the `at-exp` metalanguage, which you can 
> mix in to any Racket language.
> > Finally, something like `(math-term "finite list")`, when embedded into a 
> > document, should be able to render to html as '<span 
> > class="math-term">finite list</span>' and to TeX as "\textbf{finite list}", 
> > and I should be able to define new entity types & their content-type 
> > translations easily whenever needed.
> You can do that with Pollen, which I derived from Scribble. 
> http://docs.racket-lang.org/pollen/

Thank you for the advice, Matthew. Pollen looks quite relevant to my needs 
(that's a great name by the way—evocative!). I will spend time reading through 
its docs and source code. So far, Section 6.2 "Optional reading: the case 
against Markdown" practically read my mind. I also ran across your book 
Beautiful Racket which looks equally relevant for me. I'm sure both of these 
resources will be very useful as I try to build something that works for me, so 
thank you.

You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to