Tag: bugs

  • If you’ve been using this website a lot during the last few weeks, you’ve probably noticed changes happening randomly. I’m guessing it’s been fairly annoying. Don’t worry! It’s all for a good cause. I’m modernizing LatLex and fixing bugs. Also, I’m making it slightly more friendly to people and hostile to bots, Artificial Stupidity and all that rotten nonsense.

    If you’re encountering issues, make sure you’ve done your due diligence to try to make it work — clear your cache, clear your cookies, restart your web browser, restart your device, et cetera. If all that fails and you’re interested in Latin as a research topic (not as a data broker, agent, bot farmer or bot), feel free to contact me. I’ll try to help out if I can.

    More changes to come!

    PS – to contact me publicly, leave a comment on this news post; privately, go to the info and contact page.

  • I’ve been updating the site a bit, but you won’t notice most of the changes as a user. The changes are primarily on the back-end of the site to help me manage it more easily and effectively.

    One small change you’ll notice is that the nickname Numen has been retired. The nickname is now LatLex. I won’t change it everywhere — especially not in the YouTube tutorials and historic blog posts — but most everywhere else, the deed is done.

    If you notice weirdness happening — that’s OK. It’s OK. Weird is good. However, if anything is broken, try clearing your cache, your cookies, restarting your browser and restarting your device. If that still doesn’t work and you think you’ve found a bug, let me know. I love squashing bugs. Actually, I don’t. I usually just pick them up and put them in the garden. But you know what I meant!

    Here’s another way of getting in contact with me, in case email is not your thing: Keith on Bluesky

  • Many of you know that Numen provides a beta paradigm feature. The paradigms of most nouns, verbs, adjectives, and pronouns are available. Generally, they work very well with a couple of well known exceptions (Greek nouns, certain verbal forms, and some irregular forms).

    Once upon a time, the pronouns were working fairly well but not so much recently. Over the past few months there has been an uptick in the number of reports of bad pronoun paradigms. After a thorough review, I must note that all pronoun paradigms were broken. Honestly, I’m not sure how that happened. Nonetheless, I took some corrective action this weekend and fixed most of the pronoun paradigms — with the exception of the personal pronouns. Those will take a bit more work because as you probably know, personal pronouns are the only nominal forms in Latin that don’t have explicit gender (i.e., tu does not code for masculine, feminine, or neuter).

    So in the meantime, please feel free to spot-check the paradigms for your favorite pronouns and please feel free to report errors. PS, it’s always helpful to cite your source if you believe that a paradigm has an incorrect form. Sources do vary!

  • You know me pretty well by now if you know that I move the Latin Lexicon server every few months. Hopefully this new home will last for a couple of years.

    If you notice anything isn’t working, please feel free to contact me at admin@latinlexicon.org.

    I should post more news here. It might not be obvious from here, but I’m constantly making updates to the Latin Lexicon — I fix something like 10 reported errors per week. I also add enhancements and fix bugs (and sometimes add new bugs). If there are any particular features you’d like to see on the site, again feel free to contact me. 

  • So the server seems stable. That’s good news. Thanks to all of you for your feedback over the last few weeks.

    I’d like to make small changes to the site and make it more usable? What would you like to see (including big bugs that I’ve missed)?

  • I found myself with plenty of time this week so I’ve been fixing some long neglected bugs on this site.

    The most important bug I fixed was in the way participial paradigms were formed. I discovered the problem when I parsed montium (“of mountains”) and the verb meo came up. Hopefully I fixed the problem without causing too many others.

    Also, it may not look this way, but I’m constantly correcting bad dictionary entries or data-entry errors. I usually fix 10-20 per day. Anytime you notice an error in any dictionary entry, please feel free to report it and it’ll automatically go into my TODO list!

    If you know of a particularly unpleasant or distracting bug that you’d like me to fix, please let me know.

    Tags:

  • In the lower-right corner you should see a “source” box. Sometimes that source box disappears when users sign on. I tracked down that bug and squashed it! Hopefully it’s working better for you, but if it’s not, please let me know.

    Tags:

  • After the server upgrade a few weeks ago, I busted the OpenID login system. I’ve spent a few hours fixing it and improving it, so if you use OpenID to login then it should work now. Feedback is always welcome!

    Tags:

  • I like to keep the news relatively fresh, even if nothing major is happening. But even though this is a somewhat slow time for Numen development, there are still a constant stream of small updates. I’d like to keep everybody apprised of the situation.

    One of the benefits of having students who actively use this dictionary is their feedback. One of the things they noticed was that sometimes an error message pops up saying, “AJAX has timed out”, and it would happen relatively often — especially on the flashcard practice tool. So I dug into the code and found the issue: I designed the site so that — if any request took more than a few hundred milliseconds — it would give an error. Such timeouts always involve a balance between briefness and lengthiness of waiting, and I quickly realized that I had not struck that balance. So I bumped up the timeout duration to something reasonably middle-of-the-road and. Voila! Problem solved! Gratias vobis ago, discipuli.

    More: My big project with Vergil and Livy is still paying off. I continue to correct dozens of tiny mistakes and errors in the data every week, and I was able to run some statistics. Excluding proper names and place names, the parsing engine can analyze and pin down around 98.5% of all the words in these two Augustan authors. So accuracy is definitely improving daily! I can’t yet account for all false positives, but they seem to be less than a fraction of a percent (anecdotally).

    Speaking of accuracy, there is still room for improvement in three key areas:

    1. syncopated forms (laudaverunt => laudarunt), which Livy loves by the way!
    2. irregular forms (bobus, filiabus)
    3. proper and place names (which do not, for the most part, exist as a regular part of the Lewis Elementary dictionary).

    I have been cogitating over solutions for all three issues, but it might take a while to implement them — probably not until December or January (winter holidays, yay!).

    In other news — I guess I have more than I had first assumed — I’ve almost got a word list feature finished. This is for people who prefer to work with formatted word lists as opposed to flashcard decks (which I understand are sometimes referred to as index cards). The only major problem I have with this process is that the Lewis Elementary dictionary does not provide a “core” definition for most words, so the word list would have extremely lengthy definitions. I think one of my best options is to import the data from Whittaker’s Words, which have more simple, more core-like definitions. But this could be problematic as a 1:1 mapping between Lewis’ forms and Whittaker’s forms would be difficult to achieve. Alas, I shall continue to think on this one.

    Okay, so that’s enough for now! Keep using it, and please keep reporting problems and errors! It may take a few days or weeks, but I eventually do fix all the errors!

  • Salvete omnes!

    I fixed a small bug that affected flashcard decks in Internet Explorer 8 (and presumably earlier versions). If you couldn’t create a flashcard deck in that browser, it should be fixed now!

    As a side note, I’ve been working on a big project with Livy and Vergil. I’ve essentially been editing all the mistakes and unfound words in those authors. This is especially useful in Livy because we have a corpus of about 1 million words! So the accuracy of this dictionary is creeping up to the highest possible levels! With the exception of proper names and place names, I’ll ballbark its accuracy with common classical authors at about 95%.

    Also, thanks to the people who have been reporting errors and bugs! It’s really helpful to have your feedback!

Video Tutorials

Would you like to know how to use this site? Watch LatLex’s video tutorials!