[
https://issues.apache.org/jira/browse/SOLR-10297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004873#comment-16004873
]
Cassandra Targett commented on SOLR-10297:
------------------------------------------
The cause of these errors is from the fact we're using {{:doctype: book}} (line
146 in build.xml).
We could experiment with {{:doctype: article}}, which is the default and
doesn't have these rules. I did this before, and now that I'm thinking of it I
think it causes some really unfortunate page breaks that we can't control.
I dislike the idea of adding an extra header to very short pages just to avoid
an error that doesn't actually hurt anything. Yes, it's an error according to
the rules of the converter, but it's not a failure, and some future content
reworking may make them go away.
> Resolve Ref Guide build errors
> ------------------------------
>
> Key: SOLR-10297
> URL: https://issues.apache.org/jira/browse/SOLR-10297
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Cassandra Targett
> Attachments: build-errors-HTML-20170315.txt,
> build-errors-PDF-20170315.txt
>
>
> The asciidoctor tools used to build the HTML and PDF versions of the Ref
> Guide validate the pages during the build and throw errors during the build
> when there are problems. Usually these problems are not fatal, but they do
> indicate inconsistencies in the content that should be resolved. Almost all
> of the time they are problems with inconsistent heading levels - a h5 follows
> a h2 for example.
> These errors should be cleaned up so we only see errors we should worry about
> going forward.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
