[sword-devel] Managing Bible translation
jonmmorgan at gmail.com
Sun Sep 5 06:30:34 MST 2010
I do not have strong opinions on this. However, the last place I have seen
similar things discussed was the Open Scriptures group (
http://groups.google.com/group/open-scriptures). I am not sure whether it
was merely discussion of ideas to work or whether anything was implemented,
but youmay want to ask around there (apart from anything else, I think that
list attracts more people interested in texts and translations and data
generally, while this list attracts more people interested in software and
particularly SWORD software).
On Sun, Sep 5, 2010 at 10:55 PM, Mattias Põldaru <mahfiaz at gmail.com> wrote:
> I am thinking of ways to manage Bible translation well in git/bzr/svn or
> whatever other VCS or DVCS.
> Pros of using (D)VCS:
> Diffing possibilities
> One central repository
> Backtrace of changes
> Deeper learning curve
> The core document would definitely have to be either OSIS or USFM.
> USFM produces better diff
> USFM is simplier to use for computer illiterate
> USFM is supported by bibledit
> OSIS is technically superior
> OSIS is easy to derive other formats from (USFM → OSIS is also
> straightforward conversion)
> OSIS provides wider set of markup possibilities (most notably STRONG
> numbers, if this is needed, USFM is not an option)
> To provide better diff, some prettifying scripts could be used (both for
> OSIS xml and USFM), to standardize whitespace and linebreaks.
> In 2005 it was discussed about OSIS editor, but since this is the only
> mark about the subject, I suppose the project never started.
> I would be glad to hear your thoughts on the subject.
> Thanks in advance
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel