Jump to content

Search the Community

Showing results for tags 'search'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


Last Updated

  • Start


Filter by number of...

  1. 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.
  2. Environment Accordance 13.3.2 ( Windows 10 (10.0.19044) Description Accordance accepts and correctly handles a Unicode en dash (U+2013) as part of a verse reference in the search box. However, upon saving and reloading a workspace with search text containing an en dash, Accordance displays an error indicating the search text is invalid and replaces the en dash in the original search text with three garbage characters. 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 "Verses". Enter "Eph. 6:5–8" into the search box. Note that the range character in this verse reference is an en dash (U+2013), not a standard hyphen (U+002D). Press "Enter" to execute the search. Observe that Accordance performs the search without error or any kind of warning about extra characters after the verse reference. Save the workspace. Close the workspace. Open the workspace closed in (7). Expected behavior The workspace should open without error. The text entered in step (4) should be present in the search box (although it would be acceptable if the original en dash was replaced with a standard hyphen). Actual behavior The error message "There are extra characters after the end of the verse reference" is displayed (see attached image open-workspace-error.png). The search box contains the text "Eph. 6:5ÔøΩ8". Analysis Examining the workspace file created in step (6), I observed that the string entered in the search box is stored as a sequence of one-byte characters, and, specifically, the Unicode en dash character (U+2013) in the search string is encoded as the single byte 0xD0, which is the code point for the en dash character in the Mac OS Roman encoding. Therefore, it seems safe to say that, when serializing the search string, Accordance (or the Mac emulation framework it runs within on Windows) encodes the Unicode search string using Mac OS Roman, translating applicable characters during the process (in this case, a Unicode en dash to a Mac OS Roman en dash). However, what happens during deserialization of the search string—from its Mac OS Roman-encoded form in the workspace file to its final display in the search box—is not as clear to me. The three characters "ÔøΩ" displayed in the search box after loading the workspace file are represented on Windows by the sequence of Unicode characters "U+00D4 U+00F8 U+03A9". In the Mac OS Roman encoding, those same three characters are represented by the three-byte sequence "0xEF 0xBF 0xBD". This three-byte sequence also represents the single Unicode character U+FFFD (REPLACEMENT CHARACTER) in the UTF-8 encoding. This is a total guess, but those various encodings seem to suggest something like the following is happening: The raw search string bytes read from the workspace file "0x45 0x70 0x68 0x2E 0x20 0x36 0x3A 0x35 0xD0 0x38" are first UTF-8 decoded. The UTF-8 decoder encounters the invalid two-byte sequence "0xD0 0x38" ["11010000 00111000"] (invalid because the second byte doesn't match the mask "10xxxxxx"), so it replaces the invalid one-byte sequence 0xD0 with U+FFFD, and then moves on to the next byte (0x38), which is a valid one-byte UTF-8 encoding. The resulting Unicode string is "Eph. 6:5�8". The decoded Unicode string is then, for whatever reason, once again UTF-8 encoded, resulting in the byte sequence "0x45 0x70 0x68 0x2E 0x20 0x36 0x3A 0x35 0xEF 0xBF 0xBD 0x38". The encoded byte sequence is now Mac OS Roman decoded. During this process, the Mac characters in the range 0x80-0xFF are translated into their Unicode equivalents (0xEF to U+00D4, 0xBF to U+00F8, and 0xBD to U+03A9). The resulting Unicode string is "Eph. 6:5ÔøΩ8", which is used to initialize the search box. Again, that's just one possible scenario. But, regardless of the actual details, it seems there is some kind of asymmetry in UTF-8 encoding between serialization and deserialization of the search string. Notes The use case that prompted this report was copying a verse reference from an ebook that regularly employs en dashes rather than standard hyphens for ranges. A sample workspace that demonstrates the bug is attached (search-en-dash-bug.accord). Workaround Simply dismiss the error message and reenter the search text, if necessary. However, note that if the invalid characters in the search string ("ÔøΩ" above) with which Accordance initializes the search box are not replaced before the session is autosaved, then, upon exiting Accordance and restarting (assuming the preference is set to restore the previous session), Accordance will crash (see attached crash log Accordance_2022_02_25 09_10_48.txt). search-en-dash-bug.accord Accordance_2022_02_25 09_10_48.txt
  3. I imagine this is something rather basic that I am missing, but I have not discovered an efficient way to do this. Is there an easy way, when reading the Hebrew OT or Greek NT, to do a search for a word through an English translation, like NRSV? My current method is: look up the root in the Strong's dictionary, then do a search for one of the English translations given, find the keyed strong number in NRSV, and then do a "search for number" in that text. I know this is too cumbersome and there must be a simpler way to do this...
  4. Hello Everyone, Sometimes I have a need to exclude the (No Key number) found in my resulting text window. Does anyone know what the syntax should look like to eliminate this from occurring? The benefit for me is it would cut down the number of hits found in both the text module, and Analysis pane. Example: If you select the ESV module and type in the search field: rise up @ [KEY H*] and hit enter the results in the Analysis window will show Rise = 4 H6965 qum קוּם = 1 (No Key number) = 3 rise = 23 (No Key number) = 23 Thank you for your time and expertise. D.
  5. If I open a Note as its own tab to search for a word or phrase, the search box is always defaulted to verse instead of word. I always need it to search for a word, however, as if I needed a verse I would open a Bible. Is there a way to set it to always open to search for a word if I open it as its own tab? Thanks, Kristin p.s. - This is sort of a bonus question which is about Mac Numbers if anyone is game to answer. If I want to write a biblical reference I always have issues with it changing to time. For example, if I write "1 Tim 1:2" it auto corrects to 1h 1m 2s and 2 Tim 6:12 turns into 2h 6m 12s, which is super annoying. So I need to select all and change to text all the time. Is there a way for a new Numbers sheet to open as Text as the default instead of Automatic?
  6. I like to highlight all indicative verbs in NA28 Greek NT with a parallel ESV and NRSV pane. I can do a search for [VERB indicative] for a range say 2 Cor. 5, but this wiill only show 19 out of the 21 verses since only 19 verses have indicative verbs. In the attached screenshot, verse 5 is not shown. Is there a way to show all 21 verses and also highlight the indicative verbs?
  7. Hello, Is there a way to search "caps-sensitive"? Here's what I'd like to do. I want to search for all of the times in my ESV translation that the word "Father" appears, but only when the ESV capitalizes it. That will help me weed through the 979 times it appears referring to any "father" as opposed to specifically God the "Father." Thanks!
  8. I amplified from Tyndale House GNT in parallel with LSB, searching for the lexeme. The word clearly exists, but note the error message: I had a similar experience yesterday amplifying Ἑλληνιστὰς from Acts 11:20 to NA28-T. I had the same experience on my iPhone. I could successfully search for κύριον. Is this an issue for uncommon words? Accordance for iOS 3.2.5 ( , [iOS 14.7 iPhone 12] Accordance for iOS 3.2.5 ( [iOS 10.3.3 iPad 4th generation]
  9. In version 13.1.7 (and earlier — not sure when the behavior/functionality was introduced — when typing in a search, the Quick Entry displayed info in three categories: Commands, Books, and words that if selected would be found. If a Book was selected from Quick Entry (say you entered Job) and search tokens were set to words, Accordance recognized since you had selected the Job Book title - you wanted to do a verse look up and toggled the search token and displayed the book of Job. In 13.2 when one selects the Book of Job from the Quick Entry the search that is executed is for the word job, even though Job (Book) was selected from Quick Entry (as the search token is let reading word word and not changed to verses 13.1.7 did). Request restoring to 13.2 the previous behavior used in 13.1/7 (or at least give a preference allowing a user to select whether to set search token to verse if a book name is selected from the Quick Entry choices).
  10. Hi everyone, After a couple of videos, I still wasn't able to figure out how to search for the association of two words in a specific book. For example, I'm trying to find when the word "שמע " is associated (in a verse) with "יהוה" in the book of deuteronomy. So far, I was only able to find for this command : שמע [RANGE deut] . What am I missing ? Have a great day, Thanks
  11. I understand the necessity for verse references to be properly formatted when running searches. But, it would be nice to have a feature like "flex" that could find references even when not properly formatted or containing "extra characters." This would be especially useful when pasting a list of verses from an external source. For instance, when pasting the following list of verses, I have to delete all the "extra characters" (in bold). Gen. 12:3; 18:18; (see also: Gen. 22:18; 26:4; 28:14); 1 Chr. 13:14ff; Deut. 28:12 cf. Deut 30:1; Ps.72:17; and, Mal. 3:12. Hypothetically a "verses-flex" search would be able to eliminate the extra characters and search for just the scripture references.
  12. Could we get a feature to be able to delete some of the verses after a search result so that only the results that we want are displayed. These can then be exported as desired. In Bible Works you can just un-check the verses that you do not want. Just being able to use the right click and have an option added in that menu to delete that verse would be great.
  13. 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?
  14. Is there a shortcut to change these search options? This would make life easier . Thanks
  15. I am pleased to have gotten the Holmstedt add-on for Christmas, and have been playing a bit with it today. Question. What am I doing wrong that when I search for a parenthetical statement using the Hebrew Construct window, it does find these for me, but as soon as I do the search the Holmstedt Syntax tree add-on disappears from my workspace. How can I have it remain? Or, do I use the add-on to search directly from the add-on? If so, how do I do that? Question. Is there a primer on using the add-on for a complete beginner? Many thanks!
  16. Some months ago a presenter (I can't remember who) gave a webinar and mentioned a comprehensive set of defined search ranges that Accordance could provide. I asked for and got the Search Ranges.apref file. I have just discovered an error in that pre-defined set of search ranges; the error is in the "Aramaic Passages" range. The definition of that range is showing as "Dan 2:4-7:28; Ezra 4:8-68; 7:12-26; Jeremiah 10:11". The error is in the Ezra 4 passage: it should read "Ezra 4:8-6:18". The Search Ranges.apref file in my Accordanace preferences was dated April 27, 2020, so the webinar was on or before then. I've attached a screen shot of a portion of the defined ranges (attached) for easier identification.
  17. I select and copy Bible references from the «Feasting on the Word», Year A, Proper 27: Amos 5:18–24 Joshua 24:1–3a, 14–25 Wisdom of Solomon 6:17–20 Wisdom of Solomon 6:12–16 Psalm 70 Psalm 78:1–7 1 Thessalonians 4:13–18 Matthew 25:1–13 and paste into the search bar, press Enter and get an error message. Turns out, Accordance doesn’t understand "Wisdom of Solomon”. If I shorten it to “Wisdom” it finds referenced text. Please fix this bug.
  18. Is there a "find command" in Accordance? This is a simple function available in any word documents or Internet browsers (usually short cut key is ctrl+F or command+F), not about word search in the Bible or lexicons. What I wish to do is have a specific word highlighted on the screen that is already showing a search result, but ctrl+F doesn't do this in Accordance. Thanks for your help!
  19. When using Accordance in Windows 10 there is no easy way to type the letter Sin in the search pane of Hebrew language modules like the Hebrew Bible (Biblia Hebraica) Tagged. The letter Shin is easy: Shift+A. For the letter Sin one either has to switch to a Hebrew keyboard layout or use the character map. These are only workarounds that slow down the work flow. A simple combination of keys would serve us users. Nota bene: This is problem has existed in the Windows version for a very long time: https://www.accordancebible.com/forums/topic/339-typing-shin-and-sin-in-search-pane/
  20. Today's webinar was great. More webinars please. Please cover Constructs in great detail and the pros and cons of booleans vs. constructs. I've read http://accordancefiles2.com/helpfiles/OSX12/content/topics/06_braa/undrstnd_constrct_vs_srch.htm but still am slow at getting it. Best, Dan
  21. How do I search for me, you, her him, etc. as follows: I am looking for help in searching for object markers with pronominal suffixes, such as ,אֹתִי, אֹתך
  22. Is it possible to do the following embedded search, and if so, what is the best way? Search for all roots in the Hebrew Bible that form adjectives; From that set, search all roots that form verbs in Niphal.
  23. My default workspace has the Greek text separated into verses, and with spaces between verses, and a "parchment" background. (Shown on the LEFT side of my attached screen capture, attached) After I search a word, (I highlighted the Greek word, and used the right-click to select "Search for" and selected "Root") the results displayed, but my desktop now has all of the verses with NO space between them, and "White" background. It stays this way until I close the application and restart it. (Shown on the RIGHT side of my attached screen capture, attached) Any ideas??? -Bill-
  24. Is there a way to search within a reference list?
  25. First of all, I want to THANK Accordance for the way the searches work. For instance, as I search for various verbal roots Accordance yields and clearly labels the verb form and type. I mean to say that the prefixes and suffixes associated with the verb appear in red. This has really been useful as I search for how different verbs are used (I am doing a study of the top 60 verbs and how they appear and are used in the Hebrew Bible). I also love the side-by-side panels and the instant details panel with the specific information on the roots. Question. What is the easiest way to look for verbs in Niphal, Piel, Pual, Hiphil, Hophal, Hithpael, Cohort and other forms, etc. I am interested both in finding any verbs that come up in these forms as well as the possibility of searching for specific roots as they appear in these forms. Many thanks from Chile.
  • Create New...