please bring back http://hb.ekfocus.com/OshbParse/ in consulting mode only
Thierry Tchiakpe
the parsing in https://javascripture.org/… is not complete as in http://hb.ekfocus.com/OshbParse/ please bring backhttp://hb.ekfocus.com/OshbParse/ in consulting mode only for more complete parsing.
there is no complete parsing website available on the web like
http://hb.ekfocus.com/OshbParse/ please bring it back we need to consult parsing for our works. thanks in advance.
Jesse Griffin
--
You received this message because you are subscribed to the Google Groups "OpenScriptures Hebrew Bible" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openscriptures...@googlegroups.com.
Visit this group at https://groups.google.com/group/openscriptures-hb.
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures-hb/7bb1c5b8-24a3-4315-b3fc-98c41bb7a8aa%40googlegroups.com.
David Troidl
Jesse,
I was just looking at OSHB Verse this morning, thinking it shouldn't be too hard to add click handlers to the words. Then I could show the interpretation of the morphology code that appears in the popup.
If it's only the morph codes that are needed, they already appear in the OSHB Verse popups. It only displays one verse at a time, but for reference it may already work.
To transition the app to show full chapters, I'd have to look into it a little more. It shouldn't be that hard, though. Personally, I display one verse at a time in my local Verse app. That also has lexicon lookup functionality, though with the two separate Github repos, that may be more of a challenge.
Input about the right decision would be appreciated.
Peace,
David
David, et. al,
I'm wondering if we could setup a page/site that is very similar to the OSHB Verse demo you have written at https://hb.openscriptures.org/structure/OshbVerse/ but instead shows a whole chapter at a time.?? Instead of showing the cantillation structure, it would just be a way to read the text and get the hover over parsing information.?? The huge benefit would be zero maintenance cost as its Javascript being served by Github.
Any idea what it would take to create something like this?
Thank you,Jesse Griffin
On Tue, Jul 16, 2019 at 11:28 AM Thierry Tchiakpe <jtch...@gmail.com> wrote:
the parsing in??https://javascripture.org/?????is not complete as in??http://hb.ekfocus.com/OshbParse/??please bring backhttp://hb.ekfocus.com/OshbParse/??in consulting mode only for more complete parsing.
there is no complete parsing website available on the web like??
??http://hb.ekfocus.com/OshbParse/??please bring it back we need to consult parsing for our works. thanks in advance.
--
You received this message because you are subscribed to the Google Groups "OpenScriptures Hebrew Bible" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openscriptures...@googlegroups.com.
Visit this group at https://groups.google.com/group/openscriptures-hb.
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures-hb/7bb1c5b8-24a3-4315-b3fc-98c41bb7a8aa%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "OpenScriptures Hebrew Bible" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openscriptures...@googlegroups.com.
Visit this group at https://groups.google.com/group/openscriptures-hb.
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures-hb/CAAQgH%2B0Jufyv_1MHiPty%2BZcHAovQWs6mcTskK8sCh2UzxMzyOw%40mail.gmail.com.
Jesse Griffin
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures-hb/655e3349-a2c1-1508-d65c-7e4f6361a864%40aol.com.
David Troidl
The initial release of OSHB Read has been released at https://hb.openscriptures.org/read/. This is a minimal conversion of OSHB Verse to accomplish the goals for reading and accessing morphology. The current version is for testing purposes, and comments are welcome.
Peace,
David
My opinion is that a chapter based view that does not show the cantillation structure would be valuable.?? This would something of a "reader view" with parsing information on hover.
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures-hb/CAAQgH%2B3SWc9%2B%2Br7bziWn7PVb8CUqsAyJCsckuHpK1XNeKhX7QA%40mail.gmail.com.
Jesse Griffin
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures-hb/6b1a5ccd-bd0d-9001-c3ea-089b767a32cf%40aol.com.
David Troidl
Hi Jesse,
Thank you.
It would be good to hear from Thierry.
To get the full verbal form of the parsing, just click on a word.
It seems to me it would be unwieldy to stuff all that into a
popup. In doing this, I encapsulated the whole morphology
interpreter into one JavaScript file, so this will take the place
of a demonstration of that functionality, too.
I started adding the segmentation to the text I submitted for the SWORD module. Though the <seg> element in OSIS doesn't allow @morph, to split up the parsing. This would be a bigger step, something I would have to think about.
Currently, I am pondering, and doing some testing, regarding the question from Rabbi Kadish. If I can get URL references to the selected verse, this would make sharing and bookmarking feasible on OSHB Verse. It could also be applied, later on, to OSHB Read. This seems like another big item on the wish list.
I actually started thinking in this direction on Sunday, before
the email came. I was wondering if we could get Lexicon lookup
working in OSHB Read. Any thoughts?
Thanks again.
David
Hi David,
Excellent work on getting the OSHB Read site put together so quickly!??
Thierry, have you had a chance to check out the new reader site at https://hb.openscriptures.org/read/ ?
I think the most helpful feature to add would be the full name of the parsing codes instead of just the code itself.
It would also be interesting to make multiple pop-ups based on the word dividers too.?? So a word with 3 parts would have 3 pop ups depending on which part of the word you are hovering on.?? Of course, this would surely be more difficult to build!?? However, if you added this then it would also make sense to remove the forward slash ("/") token dividers from the display.
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures-hb/CAAQgH%2B32%2BF%3D5SjT2g5NPG0wyTBRV73AYuY--PMCKHyD%2BaZM0DA%40mail.gmail.com.
Jesse Griffin
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures-hb/dd32b883-8d7f-8d62-7997-bf4239643f0e%40aol.com.
David Troidl
Jesse,
Your popup looks like a lot more sophisticated thing than mine. It also appears that it requires a click to close it. So apparently it's more like my Morphology Display, only on a moveable basis. I suppose I could probably make the Morphology Display work on a hover basis, rather than requiring a click. I'm not sure that's preferable.
The segmentation might also help to reduce the clutter. That, though, would require more thought and more work.
The real question about the Lexicon is the implementation. Right now OSHB Read is reading directly from the source files. To include lexical information, I would have to access the lexicon files, from another repository. If I could find a way of loading at least BDB, in the background, and keeping it available for queries, without repeatedly loading a file bigger than any of the biblical books, that might work.
I found, for some reason, HebrewLexicon is no longer listed under my repos. I can access it through OpenScriptures, but that way I have no access to the Settings. To load any of the lexicon files on the fly, like we do the OSHB, there would have to be a gh-pages branch for the lexicon, too.
More thought, or a good revelation, should help to resolve some of these issues.
Peace,
David
Jesse Griffin
To view this discussion on the web visit https://groups.google.com/d/msgid/openscriptures-hb/a0a5cf75-f87b-f115-2ae5-197bf261d665%40aol.com.