On 1 March 2012 09:57, Andrew Beekhof <[email protected]> wrote:
> A user has reported the following error with my asciidoc text:
>
>     https://github.com/ClusterLabs/pacemaker/pull/33
>
> Essentially he is getting:
>
> bash-3.2$ asciidoc -b docbook -d book -o Ap-Corosync-Conf.docbook
> Ap-Corosync-Conf.txt
> asciidoc: WARNING: Ap-Corosync-Conf.txt: line 5: missing style:
> [blockdef-literal]: appendix
>
> and suggesting:
>
>  [appendix]
> -= Configuration Recap =
> +Configuration Recap
> +-------------------
>
>
> as a fix (citing http://www.methods.co.nz/asciidoc/userguide.html#X93 ).
>
> However http://www.methods.co.nz/asciidoc/userguide.html#X46 seems to
> suggest the existing syntax is allowed.
>
> Personally I prefer the inline syntax and so I would like to know if this is
> a regression (the same text works fine with asciidoc-8.4.5-6.fc15) or a
> loophole that was closed before I apply the patch.
>

The fix is more likely working because it is moving the heading from a
level 0 to a level 1 heading rather than because it is moving to two
line headings.

Whilst the change is not (AFAIK) deliberate (and is probably due to
the changes in header processing in 8.6.5 ) it is more correct since
the docbook appendix element isn't a level 0 element, only the book
element is.

Cheers
Lex

> -- Andrew
>
> --
> You received this message because you are subscribed to the Google Groups
> "asciidoc" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/asciidoc/-/6DDNZpwFsKsJ.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/asciidoc?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/asciidoc?hl=en.

Reply via email to