Many thanks!

With all suggestions from this mailing-lists and some interesting pages I 
found, I have been capable of writing a workaround to this, long live to 
asciidoc and dblatex!

https://gitlab.com/g10h4ck/lime-guifi-interop-internship-report/commit/aa01690c4cb07bf595af42e0c9a6e833156be952

On Tuesday, August 25, 2015 09:30:57 PM ben.guillon wrote:
> Hi,
> 
> There's a weakness when dblatex passes the @language as option to the
> listing macro, so that '[..]' in the language name make a mess. I'll fix
> it in a next release. BTW this language definition is half-done, it should
> contain at least a dialect default like the other languages do.
> 
> Anyway, as a workaround you can put in your user latex style this line:
> 
> \lstdefinelanguage{lua}[5.2]{Lua}{}
> 
> Or if you have not a user latex style, override the parameter in your user
> stylesheet:
> 
> <xsl:param name="latex.begindocument">
>    <xsl:text>
> % Trick to have 'lua' language from one of its dialects.
> \lstdefinelanguage{lua}[5.2]{Lua}{}
> \begin{document}
>    </xsl:text>
> </xsl:param>
> 
> Then you can use directly:
> 
> <programlisting language="lua">
> ...
> </programlisting>
> 
> Regards,
> 
> BG
> 
> On Mon, 24 Aug 2015 22:19:26 +0200, Gioacchino Mazzurco
> 
> <[email protected]> wrote:
> > I am sorry to cross-post but it seems to me that both asciidoc and
> > dblatex are
> > involved in this problem and hope the two community toghether can help
> > me to
> > solve it, moreover i have googled a lot about syntax highlighting with
> > asciidoc + dblatex and I see there is lot of people affected but problems
> > similar to the one i have encountered, maybe it's time to find a common
> > elegant
> > solution
> > 
> > Cheers!

-- 
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/d/optout.

Reply via email to