it just wont translate everytime some one chats in global thiss comes up in console. i've tried setting the oxide.lang multiple times. im using microsofts services for translation and have got my Api key from them and have added it to the translation api plugins config.
"Invalid language code" when using Microsoft API
Thanks for the report. I'll test when able and see why it is be doing that. Both language codes should be fine, but Microsoft likely wants a more specific one such as en-US, so would need to handle that.
Wulf
Thanks for the report. I'll test when able and see why it is be doing that. Both language codes should be fine, but Microsoft likely wants a more specific one such as en-US, so would need to handle that.
Any update on this? Issue still persistent.
I honestly haven't had a lot of time, but still planning on it when I get time to sit down and do it.Louwwieee42Any update on this? Issue still persistent.
Im having the same issues. this is all my Console will say:
[Translation API] Invalid language code, please check that it is valid and try again (to: es, from: en)
[Translation API] Invalid language code, please check that it is valid and try again (to: en, from: en)
Any luck finding a solution?
I attempted to get this working with Microsoft's version as well recently and got the same error. I'm pretty sure it's, in part, due to the API being used is deprecated. When I look up the api being used, Microsoft doesn't even reference it any longer in its documentation.
Oddly enough, I'm not quite sure what happened, but it suddenly started working this weekend after I was working on updating the code myself for longer than I care to admit. I'm still running the original code so bit of a head-scratcher there. See if it's working for you as well if you still need it, but sounds like support for the particular MS api is not there and could stop working at any time. I'll continue working on the updated version and will either give it to MrBlue to kick around and incorporate or post a new variant.
suprnova74
I attempted to get this working with Microsoft's version as well recently and got the same error. I'm pretty sure it's, in part, due to the API being used is deprecated. When I look up the api being used, Microsoft doesn't even reference it any longer in its documentation.
Oddly enough, I'm not quite sure what happened, but it suddenly started working this weekend after I was working on updating the code myself for longer than I care to admit. I'm still running the original code so bit of a head-scratcher there. See if it's working for you as well if you still need it, but sounds like support for the particular MS api is not there and could stop working at any time. I'll continue working on the updated version and will either give it to MrBlue to kick around and incorporate or post a new variant.
Did you get this working? I have the same issue. Did you make an updated version? I would appreciate getting ahold of that!
CdiehmDid you get this working? I have the same issue. Did you make an updated version? I would appreciate getting ahold of that!
To be honest, I stopped looking at it once it started working on it's own. However, I just switched to the v3 discord APi and noticed that the invalid language code is back. I don't get non-english speakers too often so didn't notice when it actually stopped working. I'll give it another round to see what can be done as it looks like that pesky Real Life(tm) has gotten to Wulf.
To be honest, I stopped looking at it once it started working on it's own. However, I just switched to the v3 discord APi and noticed that the invalid language code is back. I don't get non-english speakers too often so didn't notice when it actually stopped working. I'll give it another round to see what can be done as it looks like that pesky Real Life(tm) has gotten to Wulf.
In the config if you leave the api key blank and put "google" for translation service it works