-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would a compound acronym translator be useful? #348
Comments
I think it'd be useful! It reminds me of Department of Veterans Affairs' WTF Bot, where you can enter |
As a fairly recent new person here, yeah! I've been meaning to dig into this bot a bit to see how it works, I could maybe work on adding this unless someone else wants to (or Greg's already done it) |
@julialeague Thanks for the feedback! Do you know if it's possible to write Ruby in this context? Looks like all of the scripts are TypeScript. @geekygirlsarah Thanks for that feedback! I don't think anyone has done it yet. There's a decent overall single-acronym bot, but an agency-specific compound acronym bot would probably require a little bit of lexing & parsing (that's how my Ruby script works, anyway) and a more complex lookup. |
This would be such a great addition. |
@beechnut Is this something you're still interested in fiddling with sometime? (Not asking for a commitment to do anything, just curious.) |
@mgwalker Thanks for asking, but no, not in the foreseeable future |
Background Information
I wrote a small Ruby script to help me translate compound acronyms from my project's partner agencies.
For example:
I'm imagining this could be a useful Slackbot addition, looking something like:
define <agency-acronym> <acronym(s)>
, e.g.define USFS B&F-ASC RACA
.We could have a folder of YAML files that define acronyms for each agency, and having the agency acronym as the first input lets us scope the lookup more precisely.
Questions: Would this be a useful addition to the
define
command? If so, is the usefulness of this idea worth the effort?The text was updated successfully, but these errors were encountered: