Results 1 to 10 of 11

Thread: Creating User Greek database (module) from UTF8 Unicode text

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default Creating User Greek database (module) from UTF8 Unicode text

    Hi, I'm trying to make my first BW database (user Bible module), which is the unaccented Greek WH text from 1881. (The one in BW is from 1885. I want to use WH1881 to compare with the TR and with WH1885.)

    I have the text, and all the references are correct. It compiles correctly. However, it looks like gibberish. I assume this is because it's in Unicode UTF-8.

    Name:  WH1881_sample_gibberish.png
Views: 495
Size:  12.0 KB

    I searched the forums, but can't figure out how to convert this unicode to something BW10 will understand. I tried opening the UTF-8 file in Notepad++ and changing the encoding to ANSI or to some other Greek encoding, but I can't seem to find what works.

    Name:  EncodingOptionsInNotepad++.png
Views: 488
Size:  57.8 KB

    EDIT: I noticed the two options to import: BW Format & CCAT Format. I tried both with no success. I found mention on the forums that BW now supports importing Unicode, but I can't figure out how to do it.

    Do I actually need to run some kind of macro to convert the text? If so, where can I find the tools for that?

    Thank you!
    Eric
    Last edited by ETC; 02-12-2017 at 12:57 PM.

  2. #2

    Default

    hmm... usually the issue has been going from legacy fonts to unicode. Maybe one of the converters I list here will work for you moving from unicode to BW or CCAT.
    Mark G. Vitalis Hoffman
    Glatfelter Professor of Biblical Studies
    United Lutheran Seminary at Gettysburg & Philadelphia
    uls.edu - CrossMarks.com
    Biblical Studies and Technological Tools

  3. #3

    Default Here's what BibleWorks support said

    I asked BW support about this and got this answer:

    In response to your question we can point out that BibleWorks will EXPORT in Unicode, but to import a version, via the Version Database Compiler, the base text must be in ASCII format. For Greek and Hebrew, the database must be in CCAT format. The Version Database Compiler will not support the import of a database in Unicode text.

    Information about creating version databases for use in BibleWorks can be found in Chapter 66 of the BibleWorks Help. A quick way to access this chapter is to open the Version Database Compiler, then moving the mouse pointer into the window and hitting the F1 function key.

    It is hoped that this information will be helpful to you in this matter. We thank you for using BibleWorks.

  4. #4

    Default Thank you, Mark!

    @Mark G. Vitalis Hoffman

    Thank you very much for those links. The Unicode to BWGRKL font macro linked on your site (it's by John Kendall and it's downloadable here: https://www.bibleworks.com/forums/sh...=2176#post2176) worked great to convert the text (as far as I know; I've not checked very thoroughly yet).

    @Anyone

    I do have one problem. In the text there are embedded notes in {curly brackets}. They came through as in the following screenshot. I looked at the BW documentation, and I thought they were formatted correctly.

    Mt 1:9 was originally like this: MAT 1:9 οζιας δε εγεννησεν τον ιωαθαμ ιωαθαμ δε εγεννησεν τον αχας αχας{UBS4: αχαζ αχαζ} δε εγεννησεν τον εζεκιαν
    Mt 1:9 was this way in the imported text (bwgrkl): MAT 1:9 oziaj de egennhsen ton iwaqam iwaqam de egennhsen ton acaj acaj{UBS4: acaz acaz} de egennhsen ton ezekian

    Best I can tell from Help Chapter 66, this is exactly the right way to embed the notes. "Embedded notes" was selected, and the database for compiled in CCAT format.

    Name:  Mt1_9_embedded_note_problem.png
Views: 357
Size:  12.9 KB
    Last edited by ETC; 02-13-2017 at 03:24 PM. Reason: added the bwgrkl text for Mt 1:9 and reference to Help Chapter 66, etc.

  5. #5

    Default Inserting spaces around {embedded note} does not help

    I got to thinking that maybe the problem was because the {embedded note} in the .txt file did not have spaces around it on both sides. So I changed Mt 1:9 in the source .txt file.

    As can be seen in this screenshot, it did not fix the problem. All it did was made the spacing better. The opening { is being interpreted as a rough breathing mark and an accent. The closing } is being interpreted as a Greek full stop.

    Name:  Mt1_9_embedded_note_problem_after_inserting_space.png
Views: 319
Size:  5.3 KB

    I have contacted support again. I sent them the .txt file.

    EDIT: Actually there appears to be another issue. There should be no diacritical marks in this text, but there is also one on the alpha in οζια in Matt. 1:9 rather than presenting it as οζιας. Maybe I didn't do the conversion right. Seems there were several macros in the downloaded file I mentioned above. Maybe I launched the wrong one. Hmm.
    Last edited by ETC; 02-14-2017 at 04:22 AM.

  6. #6
    Join Date
    Apr 2004
    Posts
    701

    Default

    There may be other issues in your text (as indicated by the accent mark that you discussed), but I think that you will have to used End notes instead of Embedded notes for the Greek. I doubt that anyone has ever tried included Embedded notes in Greek. In fact, the ability to add any notes at all to Greek text was only added in the last two BibleWorks versions. You will need to make sure that you use the correct format for the end notes. I suggest exporting a section of the WHT Greek text in CCAT format and see the format, and how the notes are formatted. (There are some notes in the WHT, though not extensively. Mark 15:1 has a brief note, for example.)

    As you have found out, the text must be completely in ANSI, not Unicode format, or the file will not compile correctly. Any deviation from the specifications described in the Help file will likely result in an unstable version, which may result in program crashes. Exporting a similar version and following that pattern is a very helpful approach to creating versions.

    Blessings,
    Glenn
    Glenn Weaver

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •