Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Morse Goodie: Missing results #129

majuscule opened this Issue Oct 5, 2012 · 6 comments


None yet
5 participants

majuscule commented Oct 5, 2012

The following characters don't work with Morse entry:


Original issue:


Looks like these characters (in morse, intended as conversion to text) are being overriden by a "Morse" disambiguation.


loganom commented Jan 24, 2014

Moreover, these characters are the only characters that utilize only periods. They are recognized if they are not by themselves. ex. morse -- .. will return MI, while morse .. returns nothing.


mwmiller commented Feb 10, 2014

As a point of information, these queries work fine on my local server. I believe dzil ensures that my dependencies are the same, so perhaps the '.'s are being stripped before they hit the live servers?

As a perl guy, I imagine some sort of protection against a wildcard character. As a recovering sysadmin, I imagine protection against relative paths.


moollaza commented Feb 11, 2014

@mwmiller confirmed that it does work as it should in DuckPAN Query and DuckPAN Server.

The problem is internal, our Fathead disambiguation is taking precedence for those queries. I think'll we'll have to manually force the goodie to display in those cases.

@moollaza moollaza added the Internal label Feb 11, 2014


jagtalon commented Feb 12, 2014

Yep, that's it. I could make the priority higher on our side. That should work:

screen shot 2014-02-12 at 6 12 00 pm


jagtalon commented Feb 12, 2014

It's a bit dangerous to increase the priority, though. It's going to kill results such as "morse college" which we don't want. I think there are several ways around this--not sure of the best one yet.

@moollaza moollaza added the Tolerated label Mar 17, 2014


moollaza commented Mar 17, 2014

Closing. Marking as Tolerated.

@moollaza moollaza closed this Mar 17, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment