Re: [be] Bibledit-Web 1.2 released

[Teus Benschop]

I now understand what you mean, Phil.

It is true that using Sourceforge to host the repository was hard to set up.

The new, easier, and recommended way is to use GitHub to store the USFM books for both Bibledit-Gtk and Bibledit-Web.

If both programs use the same repository, the Bible data in them can be synchronized by just doing Send/Receive.

If the repository is public, it is free on GitHub. if the repository is private, they will charge for it.

Setting it up through github is described on the Bibledit-Web demo.

it's much easier than setting it up through Sourceforge.

I am not intending to set up bibledit-web hosting, wanting to focus on improving the program, not to focus on hosting.

If somebody rises to the challenge to offer Bibledit-Web hosting for Bible translation projects, that would really provide value to the Bible translators. 

They no longer would have to be involved in setting things up. They just would point their browsers to the installation, and start working.

Regards, Teus.

On Tue, Oct 15, 2013 at 2:56 PM, Oreo Warpok <address@hidden> wrote:

Thanks, Teus.

I look forward to getting the new version running soon. Currently I am in Indonesia, so it may take a few more days.

About a repository, what I meant is having an easier way to back up or share a project via a repository. So I am talking about the ease of setting up an Internet repository like Paratext. I used to have a repository working for sharing using Sourceforge. It was not easy to set up, and most users would not want to tackle it. In contrast, setting up the repository in Paratext is simply a matter of giving the project a name and saying that you own the project. Opening a location for this within Bibledit would of course be an expense for you. I would donate something to make that happen.

Thanks,

Phil

===============
Oreo Phil                 479-524-7005

      One King to rule them all, One Son to find them,
      One Blood to cleanse them all, And from the dark unbind them.
===============

On Tue, Oct 15, 2013 at 2:37 PM, Teus Benschop <address@hidden> wrote:

Hi Phil,

Bibledit-Web having its own repository means that the program itself, that is the software, is now stored separately from the other Bibledit programs. I hope that having the source code separately may attract more contributions from other developers.

What do you mean by setting up an automatic way that users can save their project to a web repository for all bibledit-web projects? Do you mean that there are users who work with Bibledit-Gtk, and then can synchronize their Bible texts to Bibledit-Web? Or do you mean something else?

It's true that since Bibledit-Web allows to edit two projects side by side on the screen, there is no need anymore to install to location twice. Another advantage would be that both Bibles always focus the same passage.

I have no experience with converting Bibles to the epub format, but Googling for that came up with this link: http://gbcpreprocessor.codeplex.com/documentation. Would that format assist your Bible translation team doing their work better?

May God bless you.

Teus.

On Mon, Oct 14, 2013 at 9:53 PM, Oreo Warpok <address@hidden> wrote: