<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 5, 2014 at 7:21 AM, Bastien Nocera <span dir="ltr"><<a href="mailto:bnocera@redhat.com" target="_blank">bnocera@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id=":1p1" class="" style="overflow:hidden">Search providers are all backed by applications. What's the application<br>
to read the docs in /usr/share/help? </div></blockquote><div><br><div>That would depend on the format, I think. A browser for HTML docs, evince for PDF, or Yelp for DocBook/Mallard. <br></div>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id=":1p1" class="" style="overflow:hidden">
It would probably be better to have those docs be converted to something Yelp<br>
can read and integrated in the Help, at least for GNOME and for Workstation.<div class=""><div id=":1t0" class="" tabindex="0"></div></div></div></blockquote></div><br></div><div class="gmail_extra">The release notes, like most of the docs written the Docs team, are already written in DocBook, which Yelp handles just fine. The docs team can also easily convert them to PDF, HTML (multi-page), HTML (single-page), and even Markdown (with the latest release of the Publican tool). In short, I don't think conversion is a problem here -- we simply need to agree on what format(s) we want, and figure out the new workflow.<br><br>--<br></div><div class="gmail_extra">Jared Smith<br></div></div>