Thank you for all your hard work!  Too few bother with documenting anything

On Sun, May 10, 2020 at 7:22 AM Roger Leigh <rle...@codelibre.net> wrote:

> On 10/05/2020 00:21, Roger Leigh wrote:
>
> *
> https://github.com/rleigh-codelibre/xalan-c/tree/XALANC-792_replace_stylebook_documentation
>
>   (see README at bottom of page for example; links through to docs but not
> API reference); docs can be generated with "doc-api" target if doxygen and
> graphviz are installed
>
> This branch has been updated with a number of markdown syntax errors
> fixed, where the GitHub kramdown processor was not liking the variant the
> docs were written with, as well as correcting several syntax errors and
> remaining stylebook fragments that got missed.
>
> And the published documentation is staged here (branch gh-pages):
>
> * https://rleigh-codelibre.github.io/xalan-c/
>
> * https://rleigh-codelibre.github.io/xalan-c/docs/
>
> * https://rleigh-codelibre.github.io/xalan-c/docs/api/index.html
>
> (this would become apache.github.io/xalan-c if adopted)
>
> Those URIs are now https://rleigh-codelibre.github.io/xalan-c/ and
> https://rleigh-codelibre.github.io/xalan-c/api/index.html for the API
> reference (top-level README dropped)
>
> I also pushed the same to the "gh-pages" branch in the main repository.
> This means that these official URIs now work:
>
> * https://apache.github.io/xalan-c/
>
> * https://apache.github.io/xalan-c/api
>
>
> Overall, I'm pretty happy with the documentation and API reference, and I
> hope that this is generally acceptable.
>
>
> Regards,
>
> Roger
>


-- 
“Don’t follow the masses. Sometimes the ‘m’ is silent.”
--
“There are three rules for writing a novel. Unfortunately, no one knows
what they are.” ― W. Somerset Maugham
-- 
  If I'm going to write science fiction I should know SCIENCE!
  Technology trends and prognostications about the future science:
Facebook <https://www.facebook.com/JaySprenkle>  | Twitter
<https://twitter.com/jsprenkle1>
  My personal technology blog <https://jaysprenkle.wordpress.com/>

Reply via email to