bibledit-development
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[be] [task #10010] Enhance Bibledit to import from OSIS XML


From: David Haslam
Subject: [be] [task #10010] Enhance Bibledit to import from OSIS XML
Date: Mon, 28 Dec 2009 20:13:19 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 GTB6 (.NET CLR 3.5.30729)

URL:
  <http://savannah.nongnu.org/task/?10010>

                 Summary: Enhance Bibledit to import from OSIS XML
                 Project: Bibledit
            Submitted by: dfh
            Submitted on: Mon 28 Dec 2009 08:13:17 PM GMT
         Should Start On: Mon 28 Dec 2009 12:00:00 AM GMT
   Should be Finished on: Mon 28 Dec 2009 12:00:00 AM GMT
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Currently there are two utilities available elsewhere that can convert from
USFM to OSIS; one is from Snowfall Software, the other is from CrossWire.

AFAIK, there is no tool to convert from OSIS to USFM, and such a process
would probably be inherently lossy for some aspects of XML markup.

Nonetheless, there may be some value in having the ability to import XML
files, especially OSIS.

For example, the Myanmar Bible Society maintains its web-based files in OSIS,
but unlike most other sources, in a separate XML file per book, rather than a
single XML file for the whole Bible.

Now it may be that the translator's actually use Paratext and store files as
USFM, and that what we see from the website is after a multi-stage conversion.
 We know that some of their translations were converted from TeX into OSIS by
bibleTec2osis.pl so the question naturally arises, How did they get into TeX
in the first place?

Having 66 separate XML files makes building a SWORD module somewhat more
tedious, so it would also be nice to have a script to combine the individual
files into a single valid OSIS XML file.






    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?10010>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]