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

Robert Muir commented on LUCENE-9209:
-------------------------------------

Yes, currently I am fixing solr parts too (so far, but not yet sure what I am 
walking into! So I may need help, lemme see if i can get lucene-core working 
first).

I look at each violation in lucene-core and then fix it across the entire 
source tree.
For example table "summary" attribute is complained about. I look up 
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/table and see that it 
says:
{quote}
This attribute defines an alternative text that summarizes the content of the 
table. Use the <caption> element instead.
{quote}

So then I fix all occurrences in the whole source tree of table "summary" 
attribute by transforming into a caption, like this:
{noformat}
- * <table border="1" summary="comparison of dictionary and hyphenation based 
decompounding">
+ * <table style="border: 1px solid">
+ *  <caption>comparison of dictionary and hyphenation based 
decompounding</caption>
{noformat}

I'll upload a patch with my current state. I still have 16 violations in 
lucene-core.

> fix javadocs to be html5, enable doclint html checks, remove jtidy
> ------------------------------------------------------------------
>
>                 Key: LUCENE-9209
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9209
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>            Priority: Major
>
> Currently doclint is very angry about all the {{<tt>}} elements and similar 
> stuff going on. We claim to be emitting html5 documentation so it is about 
> time to clean it up.
> Then the html check can simply be enabled and we can remove the jtidy stuff 
> completely.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to