jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1628) Put HTML version of JCR spec on website (for search indexing)
Date Wed, 28 May 2008 09:17:45 GMT

     [ https://issues.apache.org/jira/browse/JCR-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alexander Klimetschek updated JCR-1628:

    Attachment: jsr-170-html.zip

This is an HTML variant of the PDF generated with pdftohtml (http://pdftohtml.sourceforge.net/).
There are many files in the zip, the start page is "jsr170-jcr-1.0.html".

It contains images and preserves the layout, thus it looks really good. The problem is that
it has one page per PDF and you need the page index (using frames, shown at the left) to browse
through the pages. There should be at least a next and previous page on each site. Much better
would be a real index by section titles, which is only present in the TOC pages at the beginning
(but you don't know where these are, because the page index only says Page 1, Page 2, ...).

> Put HTML version of JCR spec on website (for search indexing)
> -------------------------------------------------------------
>                 Key: JCR-1628
>                 URL: https://issues.apache.org/jira/browse/JCR-1628
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: docs
>            Reporter: Alexander Klimetschek
>         Attachments: jsr-170-html.zip
> It would be good to have the JCR spec online (starting with 1.0 now) in an HTML version.
This has several benefits:
> - no need to go through the many steps needed to download the JCR 1.0 pdf from the JSR
> - more visibility of the one-and-only documentation on JCR
> - less discussion about JCR spec parts because users can inform themselves easier than
> - HTML content will be indexed by search engines, finding JCR information will be much

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message