I'm no html expert, so don't trust anything I say, but:
jdk9 javadoc contains constructs that are clearly invalid html5, so generating html5 output creates invalid web pages; they must be cleaned up first. Someone around here must have the expertise to know how best to write modern html tables with borders. The existing tables have mostly been cargo-culted from file to file (including in java.util.concurrent).
Even if we can generate clean html5, I suspect it's too early to switch; web standards change more slowly than anything else in the universe except IPv6. Whenever we're tempted to switch to a "modern" standard, we should listen to How Many More Years? until the feeling goes away.
On Sun, Apr 23, 2017 at 10:11 AM, Magnus Ihse Bursie <[hidden email]> wrote:
No one disputes that we need to clean up the HTML in our doc comments. There is also a very strong desire to move to HTML 5 for the JDK documentation to be able to make use of the accessibility features that are available.
The only issue is how to get there from here and how quickly can we do it?
Now that Unified docs are in place, we should be able to start
doing experiments to determine the magnitude of the problem.
On 4/24/17 5:00 PM, Martin Buchholz wrote:
On Mon, Apr 24, 2017 at 5:06 PM, Jonathan Gibbons <[hidden email]> wrote:
OK, that's a good reason to do it sooner rather than later!
|Free forum by Nabble||Edit this page|