Suggestion: it would be beneficial to allow the "g:transliteration" (or hebrew) for non search functions. Like the TDNT or other books.
yeah, i noticed that too... i use the Logos keyboards, but still on occasion i feel lazy and just want to use the g:text to get where i'm going & it's frustrating having to remember that it only works in search windows
Agreed. This needs to be pretty universal.
Great point, John and LaRosa.
And Logos, PLEASE provide Greek and Hebrew keyboards so we don't have to mess around with g: or h:, which isn't working for me anyway.
Once again, thanks for everything you have already provided!
The same keyboards designed for Libronix DLS can be downloaded as Windows keyboards, so that you can use the same keyboards in Logos 4 as you use for Word or any other Unicode aware application.
http://www.logos.com/support/downloads/keyboards
The same keyboards designed for Libronix DLS can be downloaded as Windows keyboards, so that you can use the same keyboards in Logos 4 as you use for Word or any other Unicode aware application. http://www.logos.com/support/downloads/keyboards
Vincent,
I haven't tried it out yet, but I prefer the Logos layout to the default windows layout. Will these keyboards work ok in Win 7? Does 64bit matter on keyboards since they are essentially software?
The same keyboards designed for Libronix DLS can be downloaded as Windows keyboards, so that you can use the same keyboards in Logos 4 as you use for Word or any other Unicode aware application. http://www.logos.com/support/downloads/keyboards Vincent, I haven't tried it out yet, but I prefer the Logos layout to the default windows layout. Will these keyboards work ok in Win 7? Does 64bit matter on keyboards since they are essentially software?
The keyboards Vincent points to use the Logos keyboard maps.
Yes, we can install and use the keyboards, and I've done so, but I echo everyone's sentimates that the G: H: feature would make a great addition to other windows, especially when trying to enter active references in lexicons. One less thing to install, and more so, I don't have to think about it not being there when I sit down to help someone with their 'how to use' logos questions.
but I echo everyone's sentimates that the G: H: feature would make a great addition to other windows, especially when trying to enter active references in lexicons.
FWIW I much prefer the h: and g: over some sort of keyboard. I see no disadvantage to seeing it in both Greek/Hebrew and English.
EDIT: apparently they are, I opened them up and there's a WOW64 and AMD64 folder. Installing now.
The keyboards Vincent points to use the Logos keyboard maps.Yes, but are they compatible with Win7 64bit?
Yes, they work just fine on a Win7 64bit system (I've been using them on my machine since the Win7 RC (I have Greek & Hebrew installed & working just fine)
Suggestion: it would be beneficial...
Actually, this is not a feature request, it's a bug. I've already put a call in to Logos support on this, and they stated that they are working on a fix. I posted about this in this thread. Otherwise, how ridiculous would it be that in the search window, the user would need to type in g:logos, then from their results open their BDAG, then, activate a different keyboard to type in ἀγάπη, then, go back to the search window to look up "church fathers", switch to an English keyboard, etc., etc. It would defeat any utility having the 'g:' option might have had in the first place. Any resource that is indexed by Greek or Hebrew headwords should accept the g: or h: syntax (also, the Find on any resource should recognize it because you might be looking for a Greek word that exists in a resource, but is not a headword). Actually, any input box should accept the g: and h: syntax. Just as if I type in logos within BDAG it does nothing when I press 'Enter,' the same should happen if I type in g:logos in a resource not indexed by Greek headword.
Matt
Any clue to what happened to the Isaiah book Penner (1st part) en Yingers (2nd part) in the Lexham LXX?
Ton Verdam
Vincent, Any clue to what happened to the Isaiah book Penner (1st part) en Yingers (2nd part) in the Lexham LXX? Ton Verdam
I'm not Vincent, but I do have an answer.
We didn't want to release Isaiah in parts. We have recently received data for the whole book; the next release of the Lexham LXX Interlinear (no estimate yet) should have Isaiah.
Suggestion: it would be beneficial... Actually, this is not a feature request, it's a bug. I've already put a call in to Logos support on this, and they stated that they are working on a fix. I posted about this in this thread. Otherwise, how ridiculous would it be that in the search window, the user would need to type in g:logos, then from their results open their BDAG, then, activate a different keyboard to type in ἀγάπη, then, go back to the search window to look up "church fathers", switch to an English keyboard, etc., etc. It would defeat any utility having the 'g:' option might have had in the first place. Any resource that is indexed by Greek or Hebrew headwords should accept the g: or h: syntax (also, the Find on any resource should recognize it because you might be looking for a Greek word that exists in a resource, but is not a headword). Actually, any input box should accept the g: and h: syntax. Just as if I type in logos within BDAG it does nothing when I press 'Enter,' the same should happen if I type in g:logos in a resource not indexed by Greek headword. Matt
Will we ever see transliteration and using g: or h: in non-search box of the particular resources like lexicons working the same way as in the search box?
P.S. Sorry for reviving this old thread but as far as I know the request is still relevant.
