Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: How many Search Steps?

  1. #11

    Default

    Quote Originally Posted by ingosorke
    Hm, copy/paste doesn't to the trick, nor does typing it through the BW keyboard (Greek fonts don't show up Greek in the command line). I'll wait and see how the actual BW7 handles it when I get it.
    With your search version set to BNM (or some Greek version) go to Tools - Keyboard Layouts and make sure the Language is set to Greek.

    Other than that I have no idea!
    Joe Fleener

    jfleener@digitalexegesis.com
    Home Page: www.digitalexegesis.com
    Blog: http://emethaletheia.blogspot.com/

    Annotated Bibliography of Online Research Tools: www.digitalexegesis.com/bibliography

    User Created BibleWorks Modules: www.digitalexegesis.com/bibleworks



    Psalm 46:11
    `#r<a'(B' ~Wra' ~yIAGB; ~Wra' ~yhi_l{a/ ykinOa'-yKi W[d>W WPr>h;

  2. #12
    Join Date
    Apr 2004
    Posts
    215

    Red face

    I'm lost with BW and these searches. The keyboard is set to Greek. I'll ask whoever does the training in Fort Worth next week.

    I can't even construct Ruben's sample (see link below): The GSE does not keep a search entry like kaloj@a*. The GSE changes it to kaloj[@a* and other wild stuff. My second Word Box entry is *@n*, but that gets changed to *[v*@* when I hit o.k.

    Here Ruben's sample (scroll down to the BW example):
    http://www.bsreview.org/weblog/2005/...test-case.html

    Ingo

  3. #13

    Question

    Quote Originally Posted by ingosorke
    I'm lost with BW and these searches. The keyboard is set to Greek. I'll ask whoever does the training in Fort Worth next week.

    I can't even construct Ruben's sample (see link below): The GSE does not keep a search entry like kaloj@a*. The GSE changes it to kaloj[@a* and other wild stuff. My second Word Box entry is *@n*, but that gets changed to *[v*@* when I hit o.k.

    Here Ruben's sample (scroll down to the BW example):
    http://www.bsreview.org/weblog/2005/...test-case.html

    Ingo
    I am not sure what causes this. Maybe, just maybe, it is a faulty language and keyboard configuration. Do you, perhaps, use a German keyboard?

    In the Options > Option Flags > Command Line Configuration Options, you should select "Always Use English Font Maps for Hebrew/Greek" *if* you always use an English keyboard, and deselect it if you use, e.g. a German or Danish keyboard.

    Then you should double-click on the language button in the Status bar and make sure that the Default Keyboard layout is *your* default one (English, Danish, German or whatever; it should be what you have chosen in the Windows configuration, I think).

    You should also - at least this is what I have found to be necessary - keep an eye to the language button, the first time you use a new language. If it says Greek for Greek, you must somehow have a Greek keyboard or a software interface for such a one (unicode, perhaps). I am not sure whether that would work, though. If you have not a Greek keyboard, it should say English, if your keyboard layout is English, German if it is German, and so forth.

    If the keyboard *layout* is said to be *Greek*, then I think you should change it. (Please, backup you ini files, before you follow my advice!). E.g., selecting a Greek version you should double-click on the keyboard layout button in the status bar, make sure that the Default Keyboard Layout is your chosen keyboard layout.

    if you delected the "Always Use English Font Maps for Hebrew/Greek", then you should select Greek in the language box at the top in the dialog box and select German or whatever you keyboard layout is.

    If there is a mismatch somehow, you will not be able to use the command line as intended. But again, I am not sure whether this is the problem, but give it a try. My guess is that the culprit is somewhere in this area.

    Georg
    Dr. Georg S. Adamsen, Denmark
    Specialist in Academic Writing and Biblical Studies
    www.opgavedoktor.dk

  4. #14
    Join Date
    Apr 2004
    Posts
    215

    Default

    Thanks Dr. Adamsen!

    I was able to construct the search through the GSE. I had entered everything in the Word Agreement box instead of splitting it up between "Word" and "Morph"! However, I get 13 verses with 15 hits, with the top Merge Box (AND (BNM): vs: 89 Tot: 13.

    Still haven't figured out the command line issue. Sure would be nice if a GSE construction could be translated back to a Command Line phrase. Keyboard languages are all set correctly from what I can tell. Kein Deutsch!

    Vielen Dank.
    Last edited by ingosorke; 02-26-2006 at 03:18 AM.

  5. #15

    Default

    OK. Then I would suggest that you mail to support and include the command line search you cannot perform as well as all the information you can garner in the Help > About Bibleworks ... > System info; select the Include locale information and text of INI files. Copy the report to Clipboard and from there into a mail to support@bibleworks.com.

    I am pretty sure that it is a configuration issue. They may be able to figure it out.

    Georg

    PS added a little later: I am no longer sure that it is a configuration issue, but do ask Support anyway.
    Last edited by Adamsen; 02-26-2006 at 07:30 AM.
    Dr. Georg S. Adamsen, Denmark
    Specialist in Academic Writing and Biblical Studies
    www.opgavedoktor.dk

  6. #16
    Join Date
    Apr 2004
    Posts
    215

    Default

    Tried it all on my laptop; it works, both Command Line and GSE!

    Restarted my desktop and it works too. So, never mind. Back on track.
    This forum is great though; I thought I was going nuts.

    Thanks to everyone.

    Ingo
    Last edited by ingosorke; 02-26-2006 at 03:51 AM.

Posting Permissions

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