jschnarr / neosearch Goto Github PK

Original report by Anonymous.

---

It appears to me that when //-que// is added to the end of a word, that word is not found in a search. For instance, a search for //aspcio// does not return the //aspiciasque// in AC 8871:2. I looked at a few other examples but not many, and I did not look for other enclitics, like //-ne//, but I bet it's true for all enclitics. Understandably.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Whether I searched for gyr* or did a grammar search for gyrus, it failed to highlight the first and third instances in 5182.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Again in the Participles search parameter (under Grammar/Substantives), when you do a Participle-Any search on a verb, you ought to get just participles—maybe gerundives, but not finite verbs. Instead you get all forms of the verb. For instance, if you do a Grammar/Verb search on do, you get 7314 hits. If you do a Grammar/Substantive/Participle-Any search on do, you again get 7314 hits.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

In the Participles search parameter (under Grammar/Substantives), the choices could be listed in logical order:

Participle — Any
Present Active
Present Active — Comparative
Present Active — Superlative
Perfect Passive
Perfect Passive — Comparative
Perfect Passive — Superlative
Future Active
Adverb or Adjective — Comparative
Adverb or Adjective — Superlative
Gerundive

Note that in the above relisting several of the existing categories have been deleted:

Perfect Active (It just returns perfect verbs.)
Present (It just returns present verbs.)
Substantive (It returns nothing.)

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

A search for quae + sunt + illorum, returns 86 hits in 4 volumes. That’s obviously nowhere near the total amount; in fact, NeoSearch 1 yields 269 hits in 19 volumes. This may be mixed up with the proximity control issue? Likewise, herba* + agri misses instances in the Exodus 9 chapter of AC. (This is true of NeoSearch 1, however.)

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

The program actually freaks out now if you try to do a grammar search in the same window in which you previously did a nongrammar search; all the grammar options show up, but the slot in which the search string goes disappears. Before, this action worked some of the time and caused crashes the rest of the time. I //guess// that's an improvement.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

The program should be set so that the window either entirely refreshes when it is reused (currently, old results remain visible during new searches) or so that it is not possible to do a second search in the same window. As Josh has remarked, “Removing a search term doesn’t always remove it from the search properly.”

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Remember this little anomaly? I finally figured it out! Or rather stumbled onto it again. Open two windows, set the grammar in one of them to either Substantive or Verb without entering a search string, and then do a search in the other window - or even just set one of the parameters for a grammar search there. The reason it slows the program down so badly is that the window that's acting as a direct browser reselects every single word in the corpus every time you do anything with the other window.

Original report by Anonymous.

---

Issue raised by Stuart Shotwell; reported by Lisa Hyatt Cooper:

If you initiate a new search after you have already searched for something, the results from the last search stay posted even if the new search fails.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

When a Word Family search is conducted and Verb is clicked on, Mood, Number, Tense, and Person all come up as Any, but Voice comes up as Not Applicable. It should also come up as Any.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

In the Participles search parameter (under Grammar/Substantives), the choices could be listed in logical order:

Participle — Any
Present Active
Present Active — Comparative
Present Active — Superlative
Perfect Passive
Perfect Passive — Comparative
Perfect Passive — Superlative
Future Active
Adverb or Adjective — Comparative
Adverb or Adjective — Superlative
Gerundive

Note that in the above relisting several of the existing categories have been deleted:

Perfect Active (It just returns perfect verbs.)
Present (It just returns present verbs.)
Substantive (It returns nothing.)

Original report by Anonymous.

---

If you do a search for vinco, the results include forms of vixi, which is the perfect of vivo, but do not include forms of vici, which is the real perfect of vinco. The program doesn't recognize forms of vici at all. How the mighty have fallen; Caesar can no longer conquer.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Making this adjustment: The resizability of the windows and the columns within them is great, but it would be nice if, after one does resize the columns, they would stay where one set them as one clicks from volume to volume or section to section. But this is likely determined by the OS and is not easily addressable.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Would be nice to have the cursor show up automatically in the Search String slot rather than having to click on it to get started.

Original report by Anonymous.

---

Issue raised by Stuart Shotwell; reported by Lisa Hyatt Cooper:

I seem to search for things that just don't yield results! For example, search for turba as a nonverb; the search fails. If you search for it as a text string (turba, turbae, etc.), you do get results.

(LHC here. The original NeoSearch would identify the reason for these failures, such as Dictionary Entry Not Found, or External Ambiguity. I think a major reason for may of these problems is that the underlying program has left some legitimate forms out of its dictionary.)

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

I ran across one more small problem with NeoSearch 2, which has to do with the past participle of eximo. The program recognizes exemtus, but it's usually spelled with a p, exemptus, and that goes unrecognized. I don't know whether that's a kind of problem you can solve.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

High-resolution screens and middle-aged eyes can combine to make reading the results a bit of a strain. In fact, there is no longer any reason for the app to open in such a tiny window; it could open in a full-size window the way other apps do.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

I have a feeling I experienced and maybe even wrote about this before, but here's another amusing things about NS 2 - not a problem at all, just funny: I accidentally did a substantive search rather than a verb search on a form of the verb infesto just now, and instead of protesting, it gave me all the verb forms!

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Some features can be added to the toolbar through Customize Toolbar on the View menu, but they don’t “stick” when new windows are opened. Customizing the toolbar (i.e., adding items to the toolbar) seems to require that the cursor be placed in the Search String box first; this seems unnecessary.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

As in NeoSearch 1 (for one thing, it’s possible to miss a highlighted word; for another, it’s time-consuming to scroll through the really, really long sections).

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

In a grammar search on gyrus, one long, irrelevant set of words in 5183 is highlighted. Well, one day that was what happened, anyway. I did the same search weeks later and only gyri was highlighted! Still later, it crashed every time I clicked on 5183.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

This is a riot! Earlier today I did a search for mutuo. I don't think it was a grammar search, but whatever. EVERY search I've done since, I've gotten a message saying that mutuo is externally ambiguous and currently unsupported with a grammar search. When I close that message, the program dutifully gives me whatever I'm asking for. Even though I keep opening new windows, I still get the error message.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

The window is no longer resizable, which isn't all bad, but the third and fourth volumes of AC are hard to read, because the database has a hard return at the end of every line, and many of the lines are longer than the width of the window, so the text is often all chopped up. In NS 2 Alpha 1, you could make the window wide enough to accommodate.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

One of the things that causes crashes is clicking on a section number that's listed but doesn't actually contain the search term. An example is searching for viscerul* and clicking on DLW 343. There's no viscerul* in 343, but there's a viscerulis in 342. The problem is that section 343 is misnumbered in the database as 343 and is included with 341. (The old NeoSearch displays 343 but highlights a string of letters that do not represent the search term. When you click on "direct previous" you get an error message, and when you click on it again you get the combined 341-342, which contains the term, but not highlighted.) Since this is a problem with the database, it may not be something you want to deal with or even can.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Searching for ponere (active) + tempus (accusative singular): If you set ponere and then enter tempus and select one grammatical parameter, the program immediately gives you a list of hits. If you then select a second parameter and hit enter, you get way too small a list of hits. When you actually try to look at the hits, the program crashes.

Original report by Anonymous.

---

NeoSearch1 allowed searches for comparative and superlative adverbs but not for just plain adverbs. Surely the database identifies adverbs as such (especially when they're not just the neuter singular of an adjective). It would be nice to be able to search for adverbs as a grammatical category. I just wanted to see whether ita ever modifies other adverbs, and that would be the way to do it. But this is the first time I remember ever wanting to do it, however many years after I first started using NeoSearch. (Lisa)

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

The database exists and could be added. But in that case it would be good to be able to limit searches to the published or the posthumous or both as desired.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

A question for further consideration here: Should the search for comparatives and superlatives of participles, adjectives, and adverbs perhaps be moved into a category of its own (Comparison), instead of being included under Participles? A new user wouldn’t know the option existed where it does, since comparison is a grammatical category that is not a subset of participles. And perhaps the Participles option should then be labeled Verbals, since it includes gerundives. This would be cleaner, as adverbs and adjectives (compared or not) are not participles.

Original report by Anonymous.

---

Original report by Anonymous.

---

I want to start here by saying that this is the first issue added after the online version of NeoSearch was created. Issue raised by Stuart Shotwell; reported by Lisa Hyatt Cooper.

One problem I have always had with these iterations is that the form doesn't reset properly. I often have to completely reload the website in order to begin another search, especially if I try to search in more than one parameter.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

I searched for regione, and every time I tried to click on AC 5177 or 5178, the program quit. The program also wasn't too happy about letting me see examples of gyrus (grammar search) or gyr* in any of the three passages from the 5180s.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Need to add a user interface for setting this.

Original report by Joshua Schnarr (Bitbucket: 557058:20e9caf7-25df-418b-b853-62a4e57f5154, GitHub: jschnarr).

---

Also, I haven't found "Direct Browsing" anywhere. Is that still to come?