bibledit-development
[Top][All Lists]
Advanced

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

[be] [task #8078] New usfm->osis converter


From: INVALID.NOREPLY
Subject: [be] [task #8078] New usfm->osis converter
Date: Sun, 29 Jun 2008 00:54:12 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.14) Gecko/20080418 Ubuntu/7.10 (gutsy) Firefox/2.0.0.14

Follow-up Comment #6, task #8078 (project bibledit):

OSIS paragraph and section - I read your comments in osis.cpp line 150
onwards. and had a look at the overall code and the osis output of 3.3.15

There are two ways of encoding OSIS books - one is to have a module divided
into books, sections and paragraphes (b/s/p) , where chapter and verses are
encoded as milestones <verse sID=x/> <verse eID=x/>, the other one is to
abandon paragraphs and sections and user chapter and verse as containers
(b/c/v/).

You have chosen an approach of chapter and verse as container which is
contrary to what appears best OSIS practice -  but is not wrong. But if you do
this, then you simply can not use sections and paragraphs as you can not have
overlapping containers.

There is good use of b/c/v  modules - they are particularly useful as
starting points for a goBible module (which is a bible for mobile phone), but
they are not so good for Crosswire modules as the best features are only
available with a /b/s/p/ approach. Particularly non canonical content like
titles is better off if in a /b/s/p approach.

I wonder whether it would make sense to have a choice of a /b/s/p or b/c/v
approach before export and only former should get titles etc incorporated.

    _______________________________________________________

Reply to this item at:

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

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





reply via email to

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