Jump to content

Search the Community

Showing results for tags 'key'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Official
    • Accordance Announcements
    • Tips for Users
  • Accordance Discussions
    • General Accordance Topics
    • Technical Support
    • Bug Swatters - Mac
    • Bug Swatters - Windows
    • Accordance for iOS
    • Accordance for Android
    • Original Languages
    • Syntax Modules
    • Feature Requests
    • Module Requests
    • Webinars & eAcademy
    • Preaching and Teaching with Accordance
    • Podcasts
    • Obsolete Discussions
  • Spanish Forums/Foros en español
    • Temas generales relacionados con Accordance
    • Ayuda y resolución de problemas
  • General
    • Mainly Macintosh
    • Windows Wisdom
    • Forum Comments, Suggestions & Help
    • Greek in a Year

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 3 results

  1. I am probably missing something obvious, but I am kind of confused. [KEY H6996] has 98 his, but the lex has 54 hits? I see that the word is found in Gen 9:24, as an example, which is not appearing in the lex, though it is there. I had always thought that searching the lex was a way to really find ALL the hits, while the key may or may not. Any clarity would be appreciated. Kristin
  2. Environment Accordance 13.3.3 Windows 10.0.19044 Description When entering a Greek transliteration that contains the characters ē (U+0113, LATIN SMALL LETTER E WITH MACRON) or ō (U+014D, LATIN SMALL LETTER O WITH MACRON) as the argument of a KEY command in the search box (either via direct input or from the clipboard), Accordance expands them to the two-character sequences eœ (U+0065, LATIN SMALL LETTER E followed by U+0153, LATIN SMALL LIGATURE OE) and oœ (U+006F, LATIN SMALL LETTER O followed by U+0153, LATIN SMALL LIGATURE OE), respectively. In most cases, this causes the search to fail if the extra character (œ) is not removed before executing the search. Reproduction frequency Always. Reproduction steps Create a new workspace. If necessary, open a new tab for the ESV with Strong's text. If necessary, change the search type to Words. Enter a KEY command in the search box. For the KEY command argument, enter "hēmera" either via direct input or from the clipboard. Note that the argument is actually displayed as "heœmera". Press ENTER to execute the search. Expected behavior Accordance should display the search results (384 hits with ESVS version 6.5). Actual behavior Accordance emits an error chime and displays the Select Key Numbers dialog with G1438, heautou selected. Notes The use case that prompted this report was copying the transliteration of ἡμέρα from my Mounce Greek Dictionary tab and pasting it as the argument of a KEY command in a text tab search box. I also observed the same behavior exists when pasting the transliteration into the search box of the Mounce Greek Dictionary when the search type is set to English Content. However, if I change the search type to Transliteration, the problematic characters appear correctly. Workaround If directly inputting the transliteration, simply use the corresponding version of the problematic character without the macron (i.e., e or o). If pasting the transliteration from the clipboard, remove the extra character added by Accordance (œ) before executing the search. Accordance appears to execute the search correctly when using the non-macron version of the problematic characters.
  3. Hi Everyone, I'm trying to figure out how to search for a Greek word by a specific translation. For example lets say I want to find all instances/verses where "δοῦλος" is translated as 'bondservant' I can go with [KEY G1401] <NOT> slave <NOT> servant - but having to exclude the translations I'm not looking for individually is quite annoying plus time consuming, especially for words with lots of meanings. Being able to do - [KEY G1401] <ONLY> bondservant - would be great and extremely easy. Does anyone know if there's a way of doing this?
×
×
  • Create New...