> I was hoping that I could solve the puzzle directly in AsciiDoc because I can't influence which rendering engine will be used.
That's exactly why we created the extensions API. > I will test if GitLab ... or even better Asciidoctor.js Live Preview understands those macros GitLab (and GitHub for that matter) will not use macros. They will show as unprocessed. You can load extensions into the browser extension. -Dan On Mon, Oct 15, 2018 at 3:19 AM rdp via asciidoc <[email protected]> wrote: > Hello Dan > > Thank you very much for your link to the AsciiDoctor macros! > > I was hoping that I could solve the puzzle directly in AsciiDoc because I > can't influence which rendering engine will be used. (Because the rendered > output in e.g. GitLab looks different than in other tools, I guess that > there are different rendering products.) > > I will test if GitLab ... or even better Asciidoctor.js Live Preview > understands those macros, then I would have a general solution and can try > to create a macro which creates a link to the rendered Document itself with > a slightly modified URL. > > Thanks a lot, kind regards, Thomas > >> -- > 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 https://groups.google.com/group/asciidoc. > For more options, visit https://groups.google.com/d/optout. > -- Dan Allen | @mojavelinux | https://twitter.com/mojavelinux -- 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 https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
