Was hoping to avoid that. One of my backends is whatever O'Reilly do with docbooks xml, so that process is a black box to me... was hoping to do it all earlier on in the processing chain... -- Sent from my BlackBerry. That's right, a phone with a real keyboard. Forget this decade, I'm off back to the naughties. Harry | 07887702511 | @hjwp
Probably best to just use HTML in the value part. It would be backend-specific, so you'd need to define them for each backend you are targeting. -Dan On Feb 23, 2014 8:18 AM, "Harry Percival" <[email protected]> wrote:
--
You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/groups/opt_out. You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/groups/opt_out. | ||
- defining replacements for auto-superscripts on 1st, 2nd, ... Harry Percival
- Re: defining replacements for auto-superscripts on 1... Dan Allen
- Re: defining replacements for auto-superscripts ... harry . percival
- Re: defining replacements for auto-superscripts on 1... Lex Trotman
