TL;DR? Skip to the last paragraph. On Wed, 09 Mar 2016, Mauro Carvalho Chehab <mche...@osg.samsung.com> wrote: > I guess the conversion to asciidoc format is now in good shape, > at least to demonstrate that it is possible to use this format for the > media docbook. Still, there are lots of broken references.
Getting references right with asciidoc is a big problem in the kernel-doc side. As I wrote before, the proofs of concept only worked because everything was processed as one big file (via includes). The Asciidoctor inter-document references won't help, because we won't know the target document name while processing kernel-doc. Sphinx is massively better at handling cross references for kernel-doc. We can use domains (C language) and roles (e.g. functions, types, etc.) for the references, which provide kind of namespaces. Sphinx warns for referencing non-existing targets, but doesn't generate broken links in the result like Asciidoctor does. For example, in the documentation for a function that has struct foo as parameter or return type, a cross reference to struct foo is added automagically, but only if documentation for struct foo actually exists. In Asciidoctor, we would have to blindly generate the references ourselves, and try to resolve broken links ourselves by somehow post-processing the result. > Yet, from my side, if we're willing to get rid of DocBook, then > Asciidoctor seems to be the *only* alternative so far to parse the > complex media documents. I think you mean, "get rid of DocBook as source format", not altogether? I'm yet to be convinved we could rely on Asciidoctor's native formats. --- Mauro, I truly appreciate your efforts at evaluating both alternatives. I also appreciate Dan's inputs on Asciidoctor. Despite your evaluation that Asciidoctor is the only alternative for media documents, it is my opinion that we should go with Sphinx. It's an opinion, it's subjective, it's from my perspective, especially from the kernel-doc POV, so please don't take it as a slap in the face after all the work you've done. With that out of the way, here's why. For starters, Jon's Sphinx proof-of-concept at http://static.lwn.net/kerneldoc/ is pretty amazing. It's beautiful and usable. Cross references work, there are no broken links (I hacked a bit more on kernel-doc and it gets even better). There's embedded search (and if this gets exported to https://readthedocs.org/ the search is even better). The API documentation is sensible and the headings aren't mixed up with other headings. It's all there. It's what we've been looking for. The toolchain gets faster, easier to debug and simplified a lot with DocBook out of the equation completely. Sphinx itself is stable, widely available, and well documented. IMO there's sufficient native output format support. There are plenty of really nice extensions available. There's a possibility of doing kernel-doc as an extension in the future (either by calling current kernel-doc from the extension or by rewriting it). Dan keeps bringing up the active community in Asciidoctor, and how they're fixing things up as we speak... which is great, but Sphinx is here now, packaged and shipping in distros ready to use. It seems that of the two, an Asciidoctor based toolchain is currently more in need of hacking and extending to meet our needs. Which brings us to the implementation language, Python vs. Ruby. I won't make the mistake of comparing the relative merits of the languages, but I'll boldly claim the set of kernel developers who know Python is likely larger than the set of kernel developers who know Ruby [citation needed]. AFAICT there are no Ruby tools in the kernel tree, but there is a bunch of Python. My own very limited and subjective experience with other tools around the kernel is that Python is much more popular than Ruby. So my claim here is that we're in a better position to hack on Sphinx extensions ourselves than Asciidoctor. My conclusion is that Sphinx covers the vast majority of the needs of our documentation producers and consumers, in an amazing way, out of the box, better than Asciidoctor. Which brings us to the minority and the parts where Sphinx falls short, media documentation in particular. It's complex documentation, with very specific requirements on the output, especially that many things remain exactly as they are now. It also feels like the target is more to have standalone media documentation, and not so much to be aligned with and be part of the rest of the kernel documentation. I want to question the need to have all kernel documentation use tools that meet the strict requirements of the outlier, when there's a better alternative for the vast majority of the documentation. Especially when Asciidoctor isn't a ready solution for media documentation either. In summary, my proposal is to go with Sphinx, leave media docs as DocBook for now, and see if and how they can be converted to Sphinx/reStructuredText later on when we have everything else in place. It's not the perfect outcome, but IMHO it's the best overall choice. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
