Re: [be] request to move the focus up

[Wolfgang Stradner]

Hi,

Here is my opinion:
On 5/24/2011 7:56 AM, Wolfgang Stradner wrote: Re: Paratext in Linux: Why not using Bibledit instead?

Hi,

Bibledit is a very powerful Scripture processing tool built for Linux. Why should is a Paratext version in Linux necessary, if Bibledit exists?

On 5/10/2011 4:06 PM, Christoph Unger wrote: Re: [LinuxUser] Paratext (or 'Fully Paratext-Compatible Editor') RE: Balsa Report:
... My position is that BibleEdit is superior to Paratext, and we should promote the use of BibleEdit rather than Paratext. ...

On 5/15/2011 9:09 AM, John Hatton wrote: Re: [LinuxUser] Paratext (or 'Fully Paratext-Compatible Editor') RE: Balsa Report:
... Paratext 7 introduced "Send/Receive" using its own code. SIL and friends came later using SIL's Chorus library to add this capability to WeSay, OurWord, OneStoryEditor, and LiftBridge (FLEx plugin).
Of course, BibleEdit had this feature before all of us :-)

In my opinion, Paratext in Linux in needed simply for the reason, that many cannot live without it. As I understand it, the reason for this are collaboration issues, (as John mentions above) and the wide use of Paratext.

Today I read a mail from Teus (the developer of Bibledit), which reflects his point of view:
On 5/23/2011 10:55 AM, Teus Benschop wrote: Re: [be] request to move the focus up:
..  If Paratext would be ported to Linux, that would be a helpful development.
People on Linux would then have a wider variety of choices as to which translation software they use and which suits them best in their own circumstances.
There is FieldWorks too, running on Linux now.

Greetings
Wolfgang

On 5/23/2011 10:55 AM, Teus Benschop wrote:

Hi Phil,

I hope that your experiments with Door43.org work well. It would be
helpful if this system would be usable for Bible translation work. The
USFM extension sounds interesting.

I do no longer feel attached to or attracted to either Bibledit-Gtk or
Bibledit-Web, or indeed any programming work. Just doing the necessary
parts. We still use Bibledit-* in our two translation projects, and we
have not moved to Paratext.

If Paratext would be ported to Linux, that would be a helpful
development. People on Linux would then have a wider variety of choices
as to which translation software they use and which suits them best in
their own circumstances. There is FieldWorks too, running on Linux now.

In the Lord,

Teus

On Sat, 2011-05-21 at 12:08 -0500, Oreo Warpok wrote:

I have wondered why you are no longer actively developing BE-gtk. Is
this because you have yourself moved to Paratext? Or are you in a
place in your translation program where you don't have time? Or are
you more involved in BE-web? I have also wondered how you felt about
all the discussion about Paratext in various environments where
Bibledit would run.


We have experimented with putting our translation at Door43.org. I
would like to see an on-line translation environment developed, and I
like the philosophy behind Door43. But MediaWiki is not a good editing
environment for a translation and doesn't give us things that we enjoy
with GoogleApps or GoogleDocs. One of my friends is working on an
extension to MediaWiki, such that <usfm> would call the extension, so
that Scripture chapters could be saved in USFM and still would be
displayed nicely formated for editing or viewing. We were thinking
that the USFM might be stored at a separate invisible web site, and we
thought of using Bibledit-web for that. Tim Jore is kind of stuck in
development for Door43 because of lack of programmers.


Thanks for your help!
Phil






On Sat, May 21, 2011 at 11:28 AM, Teus Benschop
<address@hidden> wrote:
        Hi Phil,
        
        
        On Fri, 2011-05-20 at 14:58 -0500, Oreo Warpok wrote:
        
        > Are you still using the Savanah site for feature requests
        for
        > Bibledit?
        
        
        No longer. I've closed these trackers. This is because I am no
        longer
        actively developing Bibledit-Gtk, just maintaining it and
        tweaking it
        here and there. If somebody was going to request a bigger
        thing, I would
        no longer have the time to implement it. But I'd accept
        patches for
        bigger things when these come in.
        
        
        >
        > I would like to ask that the focus in BE formatted view be
        moved from
        > the 50% of the window position to the 33% of the window
        position. I
        > currently have 5 Bible windows open in BE. Each time I move
        to a new
        > verse, the view keeps returning to the middle line of each
        window. So
        > too many times the focused verse doesn't all get displayed
        in the
        > smaller windows. Perhaps an even better way would be for
        each window
        > to try to show all of the verse focussed.
        
        
        Ok, it was changed from 50% to 33% of the window height. Looks
        neater
        indeed. The code is now in the git repository.
        
        Hope it helps,
        
        Teus
        
        
        



-- 
===============
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.
===============