Skip to content

[POC] Added JCR specification #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Conversation

dantleech
Copy link
Member

I have written a small script to convert an HTML version of the JCR spec (as exported from libre office using the original doc file) to RST.

Its not perfect, as images are not preserved and the references are broken. I'm sure we could do better.

@dantleech
Copy link
Member Author

@dbu @lsmith77 wdyt? worth having?

@dbu
Copy link
Member

dbu commented Jun 27, 2014

sorry, i have missed the original PR notification.

why would we not include either a pdf or just link to http://www.day.com/maven/jcr/2.0/ ?

@dantleech
Copy link
Member Author

The benefits are:

  • Its referencable from within sphinx
  • It is contained within the PHPCR website (so user can easily navigate without getting lost in the web)

The disadvantages:

  • The conversion is not 100% perfect
  • It is one big page
  • It duplicates the day docs.

I the first two points can be fixed - the last is true, but seeing as day is no longer a company (?) And its a JCR spec which I guess is not affiliated with a company, it gives us an advantage as PHPCR is a canonical place for PHPCR.. if you get what I mean.

David Buchmann notifications@github.com wrote:

sorry, i have missed the original PR notification.

why would we not include either a pdf or just link to
http://www.day.com/maven/jcr/2.0/ ?


Reply to this email directly or view it on GitHub:
#8 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

@dbu
Copy link
Member

dbu commented Jul 1, 2014

okay. i can agree to merge this if you can specify everything we need to re-generate this documentation (maybe in a build.txt file in the same folder as the generated doc, or something like that, and add your script or whatever). so that we can fix and rebuild should a problem be discovered even if you are not available.

@dantleech
Copy link
Member Author

Have written a new converter, which uses the HTML version of the spec:

https://github.com/dantleech/jcr-283-doc-convert

This version splits the chapters, generates a TOC tree and It also pulls in the pictures. Next step is to try and guess the code blocks..

@dbu
Copy link
Member

dbu commented Jul 16, 2014

hm, did you try to ask the jcr people if they somehow have the source of the docs available? probably that would be easier than trying to scrape it.

@dantleech
Copy link
Member Author

Where / who should I ask? But the originals are distributed in a word document and the online HTML reflects this.

@dbu
Copy link
Member

dbu commented Jul 16, 2014

maybe @bdelacretaz knows if the jcr spec "source" document really is a word file?

@dantleech would converting the wordfile then not get you closest to the original data?

@bdelacretaz
Copy link

I don't know myself but I'll ask someone who should know to have a look at this and hopefully comment here.

@dbu
Copy link
Member

dbu commented Jul 16, 2014

thanks bertrand!

@dbu
Copy link
Member

dbu commented Jan 22, 2015

@bdelacretaz any luck with finding the source of the spec document?

@dantleech
Copy link
Member Author

I also wondered if there are any copyright issues with copying the java spec?

@bdelacretaz
Copy link

Looks like I forgot to ask or never got a reply - I have asked again if we can make the spec available in a more structured format than word.

@dantleech dantleech self-assigned this Mar 11, 2015
@lsmith77 lsmith77 added ready and removed in progress labels May 1, 2015
@dbu
Copy link
Member

dbu commented Jun 15, 2023

as this is very old and we did not follow up, i close this now.

@dbu dbu closed this Jun 15, 2023
@dbu dbu deleted the added_jcr_doc branch June 15, 2023 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants