1. These forums have been archived.
    Please switch to using our new GitHub Discussions and Issue Tracker.

Idea class="LEXICON"

Discussion in 'Feature Requests' started by Gabriel, May 25, 2016.

  1. Gabriel

    Gabriel Active Member

    Joined:
    Jun 26, 2015
    Messages:
    189
    Likes Received:
    37
    Like the existing class (class="strongs"), but the class="Lexicon"!)))

    Put the lexicon in an EPUB, with all footnotes and/or references to a file LEXICON, close the application (Too big Epub).

    I would like this idea becomes planned! It would be interesting for other versions that KJV+S.

    Lexicon with:
    1 / Strong numbers
    2 / the word in Greek as it appears in the Greek NT
    3 / a pronunciation model
    4 / Bible verses where the Greek word is (not present in the class=strong)
    5 / English translation
    6 / French translation (not present in the class=strong)

    I just received the revision of the Greek lexicon, with the right to use it. In Excel. With the 6 previous columns.

    Or there is another solution? Or Equipd can recognize another "id" in the "A href" to open a file in an epub with the "a href" like for Strong?
     
    Last edited: May 25, 2016
    Gabriel, May 25, 2016
    #1
  2. iMatt

    iMatt Administrator Staff Member

    Joined:
    Jun 15, 2015
    Messages:
    757
    Likes Received:
    344
    I need to learn more about what a Lexicon is. Can you please post links to more details about this.

    Is that just for you to use? If I have the rights as the developer of the Equipd Bible to include it in the app, then that is likely a better option. Yes, for the same reason I took that approach with the Strong's Concordance.

    If I have the right to use it as well please let me know and I will send you my email address.
     
    iMatt, May 25, 2016
    #2
  3. Gabriel

    Gabriel Active Member

    Joined:
    Jun 26, 2015
    Messages:
    189
    Likes Received:
    37
    "There is no problem for using my Greek lexicon strong. (...) The key is to mention the source and let me know your work. (...) Our wish is to make the lexicon in different formats because there is demand for being integrated in various applications for Bibles, for example. (it is .docx) - Richard Helleme (hochylap@gmail.com).

    The files that I received
     
    Last edited: May 25, 2016
    Gabriel, May 25, 2016
    #3

Share This Page

Loading...