How can we improve Bibles.org?

Abbreviations in other languages

I am interested in Portuguese and in French
How can I contribute to the project so it would happen?
I have a few ideas but I need contact with the developer
Thank you!

5 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Hazael shared this idea  ·   ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • AdminAmanda (American Bible Society, American Bible Society) commented  · 

        Regarding Portuguese, we only have the 1 available.

        The other texts belong to the Portugal Bible Society and have not authorized us to provide it as an API.

        However, if you are able to obtain licenses directly from the Bible Society to use those versions we may be able to make those available to you through our API, given you are able to provide written permission or signed agreement from the rights holder. Please follow the link below to get in touch with them.

        http://www.sociedade-biblica.pt/

      • AdminAmanda (American Bible Society, American Bible Society) commented  · 

        Scripture versions are the intellectual property of various publishers and license owners. To give access to the version via the API, we have to get special permission from the various publishers, and we have not been granted permission to provide those versions as an API. If you already have or can obtain licenses directly from the license holder to use those versions we may be able to make those available to you through the API, given you are able to provide written permission or signed agreement from the rights holder.

        To help build trust with the publishers and intellectual property owners, we've built the Fair Use Management System into the API. This helps us provide an extra layer of data on how Scripture content is being consumed by API users and ultimately your application's end users. We are really trying to emphasize transparency with how Scripture content is used via our API, as that will show publishers and IP owners that we are protecting their content and ensuring it maintains the integrity Scripture deserves.

      Feedback and Knowledge Base