[ 
https://issues.apache.org/jira/browse/SOLR-12746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668030#comment-16668030
 ] 

Alexandre Rafalovitch commented on SOLR-12746:
----------------------------------------------

I tried to get this to work (ant clean build-site) but was not able to.

First, it was missing a gem, but I was able to progress by installing 
asciidoctor-html5s. Except it was refusing to install with normal command, I 
had to use:
{code:java}
sudo gem install asciidoctor-html5s --pre{code}
 

Then it was failing with conversion error on 
'field-type-definitions-and-properties.adoc' due to 'Could not find a converter 
to handle transform: empty'.

 
{code:java}
-build-site:
 [echo] Running Jekyll...
 [exec] Configuration file: 
/home/arafalov/Solr/solr-12746/solr/build/solr-ref-guide/content/_config.yml
 [exec] Source: /home/arafalov/Solr/solr-12746/solr/build/solr-ref-guide/content
 [exec] Destination: ../html-site
 [exec] Incremental build: disabled. Enable with --incremental
 [exec] Generating... Deprecation: The 'gems' configuration option has been 
renamed to 'plugins'. Please update your config file accordingly.
 [exec] 
 [exec] jekyll 3.5.0 | Error: Could not find a converter to handle transform: 
empty
 [exec] Conversion error: Jekyll::AsciiDoc::Converter encountered an error 
while converting 'field-type-definitions-and-properties.adoc':
 [exec] Could not find a converter to handle transform: empty
 [exec] Result: 1
build-site:
 [java] Exception in thread "main" java.lang.NullPointerException
 [java] at CheckLinksAndAnchors.main(CheckLinksAndAnchors.java:156)
{code}
 

 

I was not able to get past that. I am on Ubuntu. My gem list (gem list |grep 
"jekyll\|doctor\|slim"):

 
{noformat}
asciidoctor (1.5.6.2)
asciidoctor-html5s (0.1.0.beta.11)
jekyll (3.5.0)
jekyll-asciidoc (2.1.0)
jekyll-sass-converter (1.5.2)
jekyll-watch (2.1.2, 1.5.1)
slim (3.0.9) 
{noformat}
 

> Ref Guide HTML output should adhere to more standard HTML5
> ----------------------------------------------------------
>
>                 Key: SOLR-12746
>                 URL: https://issues.apache.org/jira/browse/SOLR-12746
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Cassandra Targett
>            Assignee: Cassandra Targett
>            Priority: Major
>
> The default HTML produced by Jekyll/Asciidoctor adds a lot of extra {{<div>}} 
> tags to the content which break up our content into very small chunks. This 
> is acceptable to a casual website reader as far as it goes, but any Reader 
> view in a browser or another type of content extraction system that uses a 
> similar "readability" scoring algorithm is going to either miss a lot of 
> content or fail to display the page entirely.
> To see what I mean, take a page like 
> https://lucene.apache.org/solr/guide/7_4/language-analysis.html and enable 
> Reader View in your browser (I used Firefox; Steve Rowe told me offline 
> Safari would not even offer the option on the page for him). You will notice 
> a lot of missing content. It's almost like someone selected sentences at 
> random.
> Asciidoctor has a long-standing issue to provide a better more 
> semantic-oriented HTML5 output, but it has not been resolved yet: 
> https://github.com/asciidoctor/asciidoctor/issues/242
> Asciidoctor does provide a way to override the default output templates by 
> providing your own in Slim, HAML, ERB or any other template language 
> supported by Tilt (none of which I know yet). There are some samples 
> available via the Asciidoctor project which we can borrow, but it's otherwise 
> unknown as of yet what parts of the output are causing the worst of the 
> problems. This issue is to explore how to fix it to improve this part of the 
> HTML reading experience.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to