I'm trying to get rid of google-translate-tts now that this repo has been updated to work with new API, and these language codes are one of the differences that I liked.
But no hard feelings if you don't want the codes in this library, I'll just continue to maintain it separately in google-tts-languages.
Also, happy to change the interface. I'm not good at TS, and I would have preferred googleTTS.languages as the array itself (with the lookup functions bound to it), but I couldn't figure out the correct TS types to make it happen.
To clarify: Not all language codes in the Google TTS documentation are actually supported by the unofficial Google Translate API, which is why the list I have added is not the same as the docs. I've been maintaining my own list for the sake of https://soundoftext.com and the only reason I know to add new ones is because I get emailed from users.
Coverage remained the same at 100.0% when pulling aec0ae3531a7c7af00b60236881609bcae987277 on ncpierson:master into 00c0d6ba6058a4ed7d4a2958795179d4c9f25420 on zlargon:master.
I'm trying to get rid of google-translate-tts now that this repo has been updated to work with new API, and these language codes are one of the differences that I liked.
But no hard feelings if you don't want the codes in this library, I'll just continue to maintain it separately in google-tts-languages.
Also, happy to change the interface. I'm not good at TS, and I would have preferred
googleTTS.languages
as the array itself (with the lookup functions bound to it), but I couldn't figure out the correct TS types to make it happen.To clarify: Not all language codes in the Google TTS documentation are actually supported by the unofficial Google Translate API, which is why the list I have added is not the same as the docs. I've been maintaining my own list for the sake of https://soundoftext.com and the only reason I know to add new ones is because I get emailed from users.