If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I have just finished converting or rather re-transcribing a small Ashkenazi Siddur with vowel points into the CCAT format.
When a 12point font is used it takes about 69 pages in OpenWriter office.
(Sorry, I been busy at work so I am sorry I was a little on the slow side on this project. From now on I should have more time.)

Now, I need help in thinking about how to arrange/organize the text for use with BibleWorks database compiler.

The issue here is the fact that: Prayer Books are usually not numbered/ and versed like Bible texts. However, to import the Siddur text into the database compiler it will need to be versified.

Does, anyone have an suggestions?

This is great news! I can't wait to see it! Thanks for your efforts!

I think I would treat each core piece of the liturgy as a book (like books of the bible), and give each main section within each piece of the liturgy a chapter number. From there, verse numbers. Each Kaddish could be one book, with one chapter, with whatever number of verses. The Shema could be one book, with three chapters, each with so many verses. The Amidah could be one book, with 19 or more chapters, each with so many verses. You will have to come up with some "book names" for the various prayers! However, this could become our standard layout for future projects! There are a few English Siddurim available within the public domain that could easily become B.W. modules.

Just a couple hints about dividing up new databases. When you come up with "book name" abbreviations, they have to have a combination of three letters or numbers each, and they have to be different from any other three-character abbreviation used for any other database in BibleWorks. I think that the BibleWorks blog should have a books name file (ending in .bna) available, which contains all the abbreviations in use thus far for publicly available databases.
Concerning the "verse" number, some of Michael Hanel's classical Greek databases use line numbers instead of coming up with a non-standard verse division. Such line numbers work fine for displaying the text in BW, but if a translation is envisioned to go along with it, sometimes it is difficult to match up the lines of translation exactly with the original. At present verse map file (to allow the user to view multiple verses or lines together) do not work for non-biblical books. But God-willing that can be remedied if the programmers ever have time to branch out farther from the biblical books, which is not their focus.
If you want to bounce your decisions about abbreviations and numbering systems off of other users, just ask.
Mark Eddy

...Concerning the "verse" number, some of Michael Hanel's classical Greek databases use line numbers instead of coming up with a non-standard verse division. Such line numbers work fine for displaying the text in BW, but if a translation is envisioned to go along with it, sometimes it is difficult to match up the lines of translation exactly with the original...
If you want to bounce your decisions about abbreviations and numbering systems off of other users, just ask...

Thanks, Mark and I will take be asking a few questions very soon.

Originally Posted by BigJayOneill

...
I think I would treat each core piece of the liturgy as a book (like books of the bible), and give each main section within each piece of the liturgy a chapter number. From there, verse numbers...

I am still working...

Just to let you(plural) know I haven't abandoned this project.
I am still working on it in my free time. If, anyone wants any of the files I have converted so far let me know and I will either post them here are send them by e-mail.