-
Notifications
You must be signed in to change notification settings - Fork 70
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
Translation choices/nomenclature #2510
base: main
Are you sure you want to change the base?
Conversation
This PR looks like it updates the spec to be what we want it to be! However, main is broken right now. I updated the spec to match the current situation (in #2512), and merged it. (so now you'll have to deal with the merge conflict, sorry/not sorry) |
Also, there are now some specs that need to be uncommented in (from 174e9f2 - other changes to fix main) |
54bacc5
to
ea4c8da
Compare
I looked at the spec in |
|
@sethherr it's been a while, I've pushed a couple new translation targets to the config. I'd like to get back to writing tests for these translations before any new translations are merged but in the interim do you think you could run |
Done! Thanks for your work @eld120! |
@sethherr I absolutely don't remember how to get translation.io to auto-populate the translation key/values - I'll track that down and loop you in as well as our contributors. Thanks for the help! |
Wasn't paying close enough attention previously to the translation choices nomenclature. Changed to the following: